This article describes the procedure and lists the commands to verify whether the backup switch is ready to become primary in case of a failover in EX Series switches.
When there are problems with graceful Routing Engine switchover (GRES) synchronization, the device will show the following status:
show system switchover (Backup Routing Engine - Not Ready) user@switch> show system switchover Graceful switchover: On Configuration database: Ready Kernel database: Ready Peer state: Steady State Switchover Status: Not Ready >>> Indicates that primary switchover may be performed with potential issues
To test failover or to know whether the VC can perform a clean master switchover automatically, it is necessary to make sure that synchronization between the primary and backup members is ready.
Perform the following steps:
Verify whether graceful-switchover is configured on the virtual chassis:
user@switch# show chassis redundancy graceful-switchover; >>>> Indicates GRES is configured
show system switchover
user@switch> request session member 1 --- JUNOS 12.3R6.6 built 2014-03-13 06:58:47 UTC {backup:1} user@switch> show system switchover Graceful switchover: On Configuration database: Ready Kernel database: Ready Peer state: Steady State
The above output shows that the configuration and kernel database of the backup is in sync with the primary, which indicates that it is ready for failover of mastership.
Note: Issue the show system switchover command only on the backup Routing Engine. This command is not supported on the primary Routing Engine because the kernel-replication process daemon does not run on the primary Routing Engine. This process runs only on the backup Routing Engine.
2020-02-26: Modified the article for clarity and added symptoms