Verifying That Graceful Routing Engine Switchover Is Working in the Virtual Chassis Configuration
Purpose
Verify that graceful Routing Engine switchover is working in the Virtual Chassis configuration.
Action
On the master switch, verify the member ID of the backup Routing Engine:
{master:0}
user@switch> show virtual-chassis statusVirtual Chassis ID: 5efa.4b7a.aae6
Mastership Neighbor List
Member ID Status Serial No Model priority Role ID Interface
0 (FPC 0) Prsnt BM0208105281 ex4200-24t 255 Master* 1 vcp-0
1 (FPC 1) Prsnt BP0208192350 ex4200-48t 255 Backup 0 vcp-0
Member ID for next new member: 2 (FPC 2)
Connect to the backup Routing Engine:
{master:0}
user@switch> request session member 1
{backup:1}
user@switch>
Verify that the backup Routing Engine is ready for switchover on member ID 1:
{backup:1}
user@switch> show system switchoverGraceful switchover: On Configuration database: Ready Kernel database: Ready Peer state: Steady State
Switch the current backup Routing Engine to master Routing Engine:
 | Note: You must wait a minimum of two minutes between Routing Engine failovers for the Routing Engines to synchronize. |
{backup:1}
user@switch> request chassis routing-engine master acquireVerify that the master and backup Routing Engines have switched roles:
| Note: Member ID 1 is now the master and member ID 0 is now the backup. |
{master:1}
user@switch> show virtual-chassis status
Virtual Chassis ID: 5efa.4b7a.aae6
Mastership Neighbor List
Member ID Status Serial No Model priority Role ID Interface
0 (FPC 0) Prsnt BM0208105281 ex4200-24t 255 Backup 1 vcp-0
1 (FPC 1) Prsnt BP0208192350 ex4200-48t 255 Master* 0 vcp-0
Member ID for next new member: 2 (FPC 2)
Meaning
With graceful Routing Engine switchover enabled, when you initiated a switchover from the backup Routing Engine, the backup Routing Engine became the master and the master Routing Engine became the backup.
