In scaled EVPN deployments it can be wise to name ESI that way to represent the site/physical port/etc it is attached to. Thus on some remote location you can easily verify where particular route/MAC is coming from. Similar to phone numbers, where you can locate the country/area/possibly a company of the caller. Thus we identified couple of ideas for it. That should ease support and structure deployments or new site integrations.
Q. What is the best practice creating ESI?
A. That is flexible however we can propose choosing smth like:
ZZ.ZZ = Bundle ID 7777
YY.YY = rack number
XX.XX = Site ID
identifier type 0 aa.aa.aa.03.33.11.22.11.77
XX = REGION
YY = DC Number from Router Target in VRF Identifier
ZZ.ZZ = Bundle-Ethernet ID
P.S. Let us know your thoughts and ideas on how to do it better.
Hello Everyone,I am trying to configure EVPN service on QinQ double tagged sub-interface. So is such configuration supported? interface Bundle-Ether1.999 l2transportencapsulation dot1q 999 second-dot1q 99rewrite ingress tag pop 2 symmetric!evpnevi 10...
HiI am searching about different types of SFC for ASR99K. In the datasheet it was mentioned this module provides 230Gbps Fabric Capacity and SFC3 provides 600Gbps...There are some questions here:1- Is this value half-duplex or Full-Duplex? I mean does thi...
Hi all, I'm looking for a solution / howto configuration for setting up a SIP trunk between CUCM 11.0 and a SIP-VoIP provider.Got SIP username, password and SIP-proxy IP from the provider. I am not sure how to do it, can I do it without CUBE ( d...