08-15-2020 10:08 AM - edited 08-15-2020 10:08 AM
Below is a sample layout of my network, i currently have a few locations connected via L3 VPN, these services are typically
delivered via a pruned trunk link to the client location with VLAN 100 being my management VLAN to gain access and to monitor the device located at the client location.
I recently acquired a NCS 540 and I realize that the ability to extend a management VLAN does not exist, can you point me in the right direction to be able to deliver the mpls services to the customer while having access to the demarc switch.
Solved! Go to Solution.
08-20-2020 08:55 PM
Hi Jose,
NCS540 is an IOS-XR based routing platform and it doesn't have the IOS/L2 configuration similar concept, you need l2transport services to achieve a similar outcome.
This is the URL for the configuration guides
l2 ethernet services guide can be located from the above
https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5xx/l2vpn/72x/b-l2vpn-cg-72x-ncs540.html
This is the high-level concept for your requirement
interface TenGigE0/0/0/23/1.100 l2transport
desc -- towards PE --
encapsulation dot1q 100
rewrite ingress tag pop 1 symmetric <-- you may not need this command, it depends on your use-case
!
interface TenGigE0/0/0/23/2.100 l2transport
rewrite ingress tag pop 1 symmetric
!
interface TenGigE0/0/0/23/3.100 l2transport
rewrite ingress tag pop 1 symmetric
!
l2vpn
bridge group MGNT-VL100
bridge-domain MGMT-VL100
interface TenGigE0/0/0/23/1.100
!
interface TenGigE0/0/0/23/2.100
!
interface TenGigE0/0/0/23/3.100
!
!
routed interface bvi 1234 <== if you need l3 interface in this b'cast domain
!
end
Hope this helps
Sanjeewa
08-20-2020 08:55 PM
Hi Jose,
NCS540 is an IOS-XR based routing platform and it doesn't have the IOS/L2 configuration similar concept, you need l2transport services to achieve a similar outcome.
This is the URL for the configuration guides
l2 ethernet services guide can be located from the above
https://www.cisco.com/c/en/us/td/docs/iosxr/ncs5xx/l2vpn/72x/b-l2vpn-cg-72x-ncs540.html
This is the high-level concept for your requirement
interface TenGigE0/0/0/23/1.100 l2transport
desc -- towards PE --
encapsulation dot1q 100
rewrite ingress tag pop 1 symmetric <-- you may not need this command, it depends on your use-case
!
interface TenGigE0/0/0/23/2.100 l2transport
rewrite ingress tag pop 1 symmetric
!
interface TenGigE0/0/0/23/3.100 l2transport
rewrite ingress tag pop 1 symmetric
!
l2vpn
bridge group MGNT-VL100
bridge-domain MGMT-VL100
interface TenGigE0/0/0/23/1.100
!
interface TenGigE0/0/0/23/2.100
!
interface TenGigE0/0/0/23/3.100
!
!
routed interface bvi 1234 <== if you need l3 interface in this b'cast domain
!
end
Hope this helps
Sanjeewa
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide