JUNIPER CHASSIS

CLUSTERS
Cluster Failover
 Failover Events
What triggers our cluster to failover from
primary to secondary node?

Failover can be triggered by various events in our cluster. These

events can be broken up into 2 groups:

⬜ Control Plane events (Redundancy Group 0)

⬜ Data Plane events (Redundancy Group 1 and any others)
 Control Plane (RG0) Events
The Control Plane can be manually or automatically triggered to
cause a failover.

⬜ Manual - forced by using the following command:

■ >request chassis cluster failover redundancy-group 0 node X
(Where X is the node you want to make primary)
⬜ Automatic - critical hardware or software failure, complete
power loss.
**Has a hold time of 5 mins to prevent continues failover.
 Data Plane (RG1+) Events
The Data Plane can be triggered to failover manually,
automatically or use configured triggers.
⬜ Manual - forced by using the following command:
■ > request chassis cluster failover redundancy-group 1 node X
(Where X is the node you want to make primary)
⬜ Automatic - critical hardware or software failure, complete
power loss, spc (service processing card) failure and
memory leaks.
⬜ Configured triggers - Interface monitoring, IP monitoring
and preempt.
 Reset Manual Failover & Preempt
⬜ During a manual failover the new primary node will have a
priority set to 255
⬜ If preempt is configured, and we manually failover the RG
preempt will no longer work until we “reset” our failover.
⬜ To reset the cluster after manual failover issue:
■> request chassis cluster failover reset redudancy group 0
■ > request chassis cluster failover reset redudancy group 1
Failover Testing Diagram
Reth1.0 - 10.23.0.1/24
UNTRUST-ZONE

Redundancy Group 1
Node0 - Secondary Node1 - Primary
o s s
w e rL
P o

Reth0.0 - 192.168.1.1/24
TRUST-ZONE
Verify Failover

⬜ Issue a continuos ping from PC located on our LAN to

the WAN IP while removing power from Node1 Primary
(for RG1)
⬜ Perform a manual failover on Node1 Primary (in RG1)

■ > show chassis cluster status