Hello,
We got a Virtual-chassis that is made from 6 switches, 4 EX4550 and 2 EX4200
2 EX4550 and 1 EX4200 at our main site.
2 EX4550 and 1 EX4200 at our backup site.
We got 2 10G connection between the site.
We followed Juniper recommandation and didn't disable the split detection.
We configured the master at our main site, and the backup at our backup site.
When we shutdown the switches at the backup site the main site went into linecard role, and our entire communication went down.
We followed Juniper documentation and we discovered that:
Virtual Chassis backup router or switch (VC-B) goes down
|
Enabled
|
- VC-M takes line-card (VC-L) role, which causes all line cards (FPCs) that do not host Virtual Chassis ports to go offline.
- Previous VC-B is out of service.
- The line-card role isolates the master router or switch and removes it from the Virtual Chassis until connectivity is restored. As a result, the Virtual Chassis is left without a master router or switch, which halts interchassis routing and effectively disables the Virtual Chassis configuration.
When the failed router or switch is brought back into service:
- The mastership election algorithm is run to determine whether the router or switch takes a VC-M or VC-B role. The Virtual Chassis then becomes operational.
- All subscribers can log back in to the router or switch.
- Previous subscriber state information is not preserved.
|
The "Enabled" is for a split-active detection.
Is there a way to conifgure "MAD" at Juniper that the discovery of "split-brain" will be more accurate?
Is there any solution to have a split-detection but when our backup site shutdown not our entire network fails?
Thanks,
Omer Shtivi