Page 1 of 1

CRS - Lost management after Service-Vlan Lookup mode

Posted: Fri Jul 29, 2016 5:55 pm
by arturportella
Hello folks!

I was able to do customer vlan very well yesterday between three CRS226. What I did in my setup was setting ether2 as an access port to vlan 100 (ingress-vlan-translation) and took cpu to vlan100 to get management vlan in trunk port + local management access to switch, and in both switchs, accessing management of both switchs in the same interface. The problem was when I was trying to achieve Q-in-Q setup, that told me in the tutorial to put both CRS in service-vid-used-as-lookup-vid mode. I have a console cable and can get things back to normal mode, but let me explain my scenario with a picture:
Qinqq.png
CRS-1, CRS-2 and CRS-3 have switch1-cpu attached to VLAN 100, each one with unique ip address to the same subnet. It worked before changing bridge mode in switch configuration, after that it stopped.

CRS-1 and CRS-3 have an access port to ingress-vlan-translation the SW-1 and SW-3 vlan with ID 150. (Ex: ether10 in both)
CRS-1 and CRS-3 have an access port with two tagged VLAN inside (Ex: ether20 in both)
CRS-2 is in the middle of the "trunk" thus, need to see all those vlans with each port learning all SVLANs and CVLANs.

From my (limited) knowledge, a Q-in-Q scenario with CRS need to have a "service" tag (802.1ad). To reach this, I've used " > interface ethernet switch set bridge-type=service-vid-used-as-lookup-vid"

After that, my management access was gone. And well, I don't know what to do hahaha.

Do CRS support stacked tags? Like "well, let me put an access port and tag an already tagged access" to make a SW-2 and SW-4 Lan2Lan?

Bests,

Artur Portella