JUNIPER CHASSIS

CLUSTERS
Cluster Failover - IP Monitoring
 IP Monitoring
Often it is not possible to detect an outage just by monitoring the
status of an interface. We need to do IP monitoring instead.

⬜ IP monitoring allows us to monitor upstream IP reachability. Can

be multiple upstream routers.
⬜ Ping an upstream IP and monitor if we get a response back.
⬜ If no response detected in a predefined time period, failover the
redundancy group.
⬜ Can monitor from our primary and secondary node at the same
time.
IP Monitoring Diagram
WAN ROUTER: 10.23.0.254

Reth1.0 - 10.23.0.1/24 ping 10.23.0.254 every 2 seconds, if

no response then trigger failover.

Node0 - Secondary Node1 - Primary

RG 1
Reth0.0 - 192.168.1.1/24
 Secondary Node IP Monitoring
Monitoring the upstream IP address from our secondary node is
very useful, because we can tell if upstream is reachable or not
from the secondary node, if the upstream IP is not reachable then
the cluster will not failover. There is no need to.
⬜ Same or different upstream IP can be monitored from
primary/secondary node.
⬜ Because secondary node interfaces are inactive, we need to
define a special secondary-ip-address, pings are sourced from
this address.
 Secondary Node IP Monitoring
WAN ROUTER: 10.23.0.254
ping 10.23.0.254 every 2 seconds, if
no response mark priority 0 - so no ping 10.23.0.254 every 2 seconds, if
failover occurs, source packets no response then trigger failover.
from 10.23.0.X
Reth1.0 - 10.23.0.1/24

Node0 - Secondary Node1 - Primary

RG 1
Reth0.0 - 192.168.1.1/24
 Configuration
IP monitoring allows for a very granular configuration and is more
involved then simply monitoring the interface.
# edit chassis cluster redundancy-group 1
# set ip-monitoring global-weight 255 (if global-threshold =< 0, RG priority 255 minus global-weight)
# set ip-monitoring global-threshold 100 (global-threshold minus interface weight)
# set ip-monitoring retry-interval 1 (how ofter to ping)
# set ip-monitoring retry-count 5 (how many pings can fail)
# set ip-monitoring family inet 10.23.0.254 weight 100 (how much to minus from global-threshold)
# set ip-monitoring family inet 10.23.0.254 interface reth1.0 secondary-ip-address
10.23.0.20 (must be in the same subnet as reth0.0)
Verify Failover (Using IP mon.)

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

the WAN IP while removing WAN cable from Node1
(Primary for RG1)

■ > show chassis cluster status

■ > show chassis cluster ip-monitoring status