Hello,
I need to transport some double-tagged customers from SiteA to SiteB through a GbE link and to rewrite S-VLANs so that those I use on the
aggregation-side interface are different from those I receive on the customer facing port.
customers aggregation
(S-VLAN, C-VLAN) (S-VLAN, C-VLAN)
(10,100-199)\ /(20,100-199)
(11,100-199) -- [ A901-siteA ] ---- [ A901-siteB ] -- (21,100-199)
(12,100-199)/ \(22,100-199)
I was considering to use ASR-901s with EVC xconnect, something similar to the following config...
Site-A:
interface GigabitEthernet0/1
description Customer facing port
service instance 10 ethernet
encapsulation dot1q 10
rewrite ingress tag pop 1 symmetric
xconnect 10.0.0.1 1 encapsulation mpls
service instance 11 ethernet
encapsulation dot1q 11
rewrite ingress tag pop 1 symmetric
xconnect 10.0.0.1 2 encapsulation mpls
...
Site-B:
interface GigabitEthernet0/1
description Aggregation facing port
service instance 10 ethernet
encapsulation dot1q 20
rewrite ingress tag pop 1 symmetric
xconnect 10.0.0.2 1 encapsulation mpls
service instance 11 ethernet
encapsulation dot1q 21
rewrite ingress tag pop 1 symmetric
xconnect 10.0.0.2 2 encapsulation mpls
...
... but on the "Configuring EoMPLS" guide [1] I found this:
Restrictions for EoMPLS
- EoMPLS xconnect port with double-tagged encapsulation is not supported
Now I'm wondering whether my idea is really feasible with ASR-901 or not.
If it's not, any hint on which low budget platform can I use? ASR-920?
1]
http://www.cisco.com/c/en/us/td/docs/wireless/asr_901/Configuration/Guide/b_asr901-scg/b_asr901-scg_chapter_010100.html
