04-15-2016 06:32 PM - edited 03-05-2019 03:49 AM
Dear all,
Currently we've obtained ASR1001X and the new redudancy configuration requires us to pass dot1q traffic through 2 interfaces. It seems we cannot familiarize ourself with trunking and vlan interface when it comes to pure L3 devices.
A diagram of the implementation is as attached.
Thankyou for your help in advance
Solved! Go to Solution.
04-16-2016 04:54 AM
Hi,
To do this I would use EVC's (http://www.cisco.com/c/en/us/td/docs/ios/ios_xe/cether/configuration/guide/xe_3s/ce_xe_3s_book/ce_evc-infra_xe.pdf)
I'm assuming the config is similar to the ASR900 implementation, which would be as follows:
bridge-domain 10
bridge-domain 20
bridge-domain 30
interface BDI10
ip address 10.0.1.1 255.255.255.0
!
interface BDI20
ip address 10.0.2.1 255.255.255.0
!
interface BDI30
ip address 10.0.3.1 255.255.255.0
!
interface Ten0/0/0
service instance 10 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
bridge-domain 10
service instance 20 ethernet
encapsulation dot1q 20
rewrite ingress tag pop 1 symmetric
bridge-domain 20
service instance 30 ethernet
encapsulation dot1q 30
rewrite ingress tag pop 1 symmetric
bridge-domain 30
interface Ten0/0/1
service instance 10 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
bridge-domain 10
service instance 20 ethernet
encapsulation dot1q 20
rewrite ingress tag pop 1 symmetric
bridge-domain 20
service instance 30 ethernet
encapsulation dot1q 30
rewrite ingress tag pop 1 symmetric
bridge-domain 30
!
That should do it. Read up on EVC's and how they are implemented so you understand what is going on above, and can adjust the functionality of the interfaces as you need to. The service provider/EVC functionality is very powerful and you can do some very interesting stuff with L2/L3 traffic traffic.
Regards,
Elliott
04-16-2016 04:54 AM
Hi,
To do this I would use EVC's (http://www.cisco.com/c/en/us/td/docs/ios/ios_xe/cether/configuration/guide/xe_3s/ce_xe_3s_book/ce_evc-infra_xe.pdf)
I'm assuming the config is similar to the ASR900 implementation, which would be as follows:
bridge-domain 10
bridge-domain 20
bridge-domain 30
interface BDI10
ip address 10.0.1.1 255.255.255.0
!
interface BDI20
ip address 10.0.2.1 255.255.255.0
!
interface BDI30
ip address 10.0.3.1 255.255.255.0
!
interface Ten0/0/0
service instance 10 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
bridge-domain 10
service instance 20 ethernet
encapsulation dot1q 20
rewrite ingress tag pop 1 symmetric
bridge-domain 20
service instance 30 ethernet
encapsulation dot1q 30
rewrite ingress tag pop 1 symmetric
bridge-domain 30
interface Ten0/0/1
service instance 10 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
bridge-domain 10
service instance 20 ethernet
encapsulation dot1q 20
rewrite ingress tag pop 1 symmetric
bridge-domain 20
service instance 30 ethernet
encapsulation dot1q 30
rewrite ingress tag pop 1 symmetric
bridge-domain 30
!
That should do it. Read up on EVC's and how they are implemented so you understand what is going on above, and can adjust the functionality of the interfaces as you need to. The service provider/EVC functionality is very powerful and you can do some very interesting stuff with L2/L3 traffic traffic.
Regards,
Elliott
05-06-2024 11:04 AM
So I have a 1001-X and I want to trunk 3 vlans on my Lan interface to a fortinet switch. The scenario above looks like it keeps all vlans segmented across both sides of the ASR which would be great if we had vlans on the wan side of the ASR. It connect via a 10G layer 2 network with no vlans assigned. Doesnt seem like this scenario above would work for that.
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