Virtual Chassis redundance test-loop failure

[muga]

hi,

we´ve a virtual chassis of 4x 6900 (24 ports) in a network with 4 ERP-Rings. The VC is our routing-instance.
After a redundance test (shutdown Unit 4 and restart Unit 4) we got big trouble in our network with loops. We also opened a SR at Alcatel Lucent.


So my question:

Our Business Partner told us we don´t need to tagg the service-vlan to the ERP involved ports on the VC.

-> show configuration snapshot erp
! ERP:
erp-ring 1 port1 2/1/17 port2 4/1/17 service-vlan 601 level 5
erp-ring 2 port1 2/1/18 port2 4/1/18 service-vlan 602 level 5
erp-ring 3 port1 2/1/19 port2 4/1/19 service-vlan 603 level 5
erp-ring 4 port1 2/1/20 port2 4/1/20 service-vlan 604 level 5

-> show vlan 601 members
port type status
----------+-----------+---------------

-> show vlan 602 members
port type status
----------+-----------+---------------
-> show vlan 603 members
port type status
----------+-----------+---------------

-> show vlan 604 members
port type status
----------+-----------+---------------



is that right or wrong? I thought on the service-vlan other switches in the ERP-Ring becomes the informationen of the RPL-Port is blocked or open...

thanks for help and sorry for my bad english.....

greetings

muga

[cedric1]

Hello

In production ERP I implement, service-vlan is tagged on ERP member port.
All vans you want to protect need to be tagged on ERP member port.
RPL-port need to be manually configured on one port of global ring.
In R7 doc service-vlan is tagged in setup example .

Hope it helps

Cedric