An EX4300 Virtual Chassis experiences a split-brain condition due to a failure of all stacking cables between members 0/1 and members 2/3. How does Junos handle this scenario by default?
Trap 1: All member switches across both partitions automatically shut down…
Junos does not automatically shut down all data interfaces across a split unless specific MAC-sec or proprietary scripts are used.
Trap 2: The backup routing engine instantly shuts down its control plane…
The backup RE remains active in its partition unless split-brain mitigation actions kick in.
Trap 3: The entire Virtual Chassis reboots simultaneously until stacking…
Rebooting without manual or programmatic triggers does not happen automatically upon a cable break.
- A
Each partition elects its own primary routing engine if dual primary detection is not enabled, leading to potential duplicate IP scenarios.
Without explicit split-brain mitigation or adequate mastership conflict handling, separated partitions may both attempt to operate as primary.
- B
All member switches across both partitions automatically shut down all data interfaces to prevent loops.
Why wrong: Junos does not automatically shut down all data interfaces across a split unless specific MAC-sec or proprietary scripts are used.
- C
The backup routing engine instantly shuts down its control plane daemon permanently.
Why wrong: The backup RE remains active in its partition unless split-brain mitigation actions kick in.
- D
The entire Virtual Chassis reboots simultaneously until stacking cables are re-seated.
Why wrong: Rebooting without manual or programmatic triggers does not happen automatically upon a cable break.