This article describes about how to perform an automatic failover of redundancy groups to the other node.

If the chassis cluster encounters any issues with link connected on the primary node, or if the internet is not reachable via the primary link, we can configure event options to perform an automatic failover to the secondary node.

Below is the configuration for the automatic failover:

set services rpm probe Failover-Test test Probe-Test probe-type icmp-ping

set services rpm probe Failover-Test test Probe-Test target address 10.219.56.1

set services rpm probe Failover-Test test Probe-Test probe-count 3

set services rpm probe Failover-Test test Probe-Test probe-interval 3

set services rpm probe Failover-Test test Probe-Test test-interval 1

set services rpm probe Failover-Test test Probe-Test thresholds successive-loss 3

set services rpm probe Failover-Test test Probe-Test thresholds total-loss 3

set event-options policy Probe-Test-Failure events ping_probe_failed

set event-options policy Probe-Test-Failure events ping_test_failed

set event-options policy Probe-Test-Failure within 10 trigger on

set event-options policy Probe-Test-Failure within 10 trigger 3

set event-options policy Probe-Test-Failure attributes-match ping_probe_failed.test-name matches Probe-Test

set event-options policy Probe-Test-Failure attributes-match ping_probe_failed.test-owner matches Failover-Test

set event-options policy Probe-Test-Failure then change-configuration commands "set chassis cluster redundancy-group 1 node 0 priority 1"

set event-options policy Probe-Test-Failure then change-configuration commands "set chassis cluster redundancy-group 1 node 1 priority 100"

set event-options policy Probe-Test-Failure then change-configuration commands "deactivate event-options policy Probe-Test-Failure"

To make this work, preempt should be enabled on the cluster.