Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Retired after 40+ years experience in IT / Computer Networking, including:
- 24 years as Cisco SE
- 19 years Enterprise IT, as both customer and Cisco SE
- 22 years SP experience, as both customer and Cisco SE
CCIExpired #5286
https://www.linkedin.com/in/jimberg/
Retired after 40+ years experience in IT / Computer Networking, including:
- 24 years as Cisco SE
- 19 years Enterprise IT, as both customer and Cisco SE
- 22 years SP experience, as both customer and Cisco SE
CCIExpired #5286
https://www.linkedin.com/in/jimberg/ ...
XRv9K has long had a very limited L2VPN data-plane and I doubt that will ever change, as dev data-plane resources are more likely to be directed toward the XRd Router (as opposed to the XRd Control Plane flavor). While EoMPLS data-plane does work on ...
Identifying a candidate release for production deployment is something of an art form that is entirely dependent on information that has not been fully provided: your specific use-case. By use-case I mean your feature requirements (as expressed by yo...
In MEF-speak, an EVC is an abstract construct that associates multiple UNIs with each other in the same L2 broadcast domain. A P2P EVC associates 2 UNIs, while a MP EVC associates 2+ UNIs. The EVC concept is independent of the underlying implementati...
If a QoS config is working on actual 9K hardware, but throwing an error on XRv9K, the issue is almost certainly a less-than-complete emulation of the hardware’s data plane. When the XR control plane tries to program a QoS policy that is unsupported b...
The data plane of the XRv9K is, of course, implemented in software, but in order to re-use as much of the ASR9K's code as possible, the XRv9K software data plane emulates the A9K forwarding hardware to some degree (allows re-use of the API calls to t...