Relinquishing Primary Status

Before relinquishing primary status and initiating failover, review the section Synchronizing Nodes to confirm that your platform and both installed MSMs/MMs or master-capable nodes are running software that supports the synchronize command.
You can cause the primary to failover to the backup, thereby relinquishing its primary status.
  1. Use the show switch {detail} command on the primary or the backup node to confirm that the nodes are synchronized and have identical software and switch configurations before failover.
    A node may not be synchronized because checkpointing did not occur, incompatible software is running on the primary and backup, or the backup is down.
    If the nodes are not synchronized and both nodes are running a version of ExtremeXOS that supports synchronization, proceed to step 2.
    If the nodes are synchronized, proceed to step 3.
    The output displays the status of the nodes, with the primary node showing MASTER and the backup node showing BACKUP (InSync).
  2. If the nodes are not synchronized because of incompatible software, use the synchronize command to ensure that the backup has the same software in flash as the primary.
    The synchronize command:
    • Reboots the backup node to prepare it for synchronizing with the primary node.
    • Copies both the primary and secondary software images.
    • Copies both the primary and secondary configurations.
    • Reboots the backup node after replication is complete.
    After you confirm the nodes are synchronized, proceed to step 3.
  3. If the nodes are synchronized, use the run failover {force} command to initiate failover from the primary node to the backup node.
    The backup node then becomes the primary node and the original primary node reboots.