I'm having some problems with qinq and "rewrite ingress tag push dot1q"
on the ME3600X, running version 15.3(2)S. The problem seems to be that
the range match of vlans and push of a tag works until the device is
reloaded. Has anyone else seen this happen?
ME3600X config
This config works until reload.
--------------------------
interface GigabitEthernet0/11
description ACCESS_SWITCH
switchport trunk allowed vlan none
switchport mode trunk
mtu 2000
service instance 1000 ethernet
encapsulation dot1q 101-122
rewrite ingress tag push dot1q 2011 symmetric
xconnect 1.1.1.2 2211100 encapsulation mpls
!
Workaround
----------
ME3600X-01(config)#int gi0/11
ME3600X-01(config-if)# service instance 1000 ethernet
ME3600X-01(config-if-srv)#encapsulation dot1q 666
ME3600X-01(config-if-srv)#encapsulation dot1q 101-122
Another workaround could be to do 1 service instance per vlan match,
since that does not seem to trigger the problem...
Trigger error at when running
-----------------------------
ME3600X-01(config)#interface GigabitEthernet0/11
ME3600X-01(config-if)# service instance 1000 ethernet
ME3600X-01(config-if-srv)#rewrite ingress tag push dot1q 2011
# This will not recover the problem
ME3600X-01(config-if-srv)# rewrite ingress tag push dot1q 2011 symmetric
The only way to recover seems to be to change from a range match to a
single vlan (ie 666) and then back to a range (101-122).
The xconnect is then connected to a ASR9K bridge-domain which is then
looped back to an interface configured with EFP/subints for each
customer (outer+inner tag). AFAIK this is the only way since you cannot
run IPSG and DHCP snooping on pw's in BD's on the ASR9K yet... Or if
there is a better way to do this, please let me know :-)
Tnx!
//Claes
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
