Administrator Guide

Table 36. Commands to configure Control Plane redundancy
Command Description
redundancy auto-failover-
limit
Limits the number of failovers for a specific period.
redundancy primary (rpm0
| rpm1)
Select preferred RPM as primary.
redundancy disable-auto-
reboot pe all
Prevents all the PEs from automatically rebooting when the switch fails.
redundancy disable-auto-
reboot pe id stack-unit
Prevents all the PEs in a stack from automatically rebooting when the switch fails.
redundancy disable-auto-
reboot
Prevents the system from automatically rebooting when the switch fails.
show redundancy
Displays the current redundancy configuration.
Control-Plane Failover
Control-plane failover is the process of the standby RPM becoming the primary RPM.
The system automatically fails over to the standby RPM when:
1. Communication is lost between the standby and primary RPM.
2. You remove the primary RPM.
You can perform a manual failover by entering the redundancy force-failover rpm command.
To display the reason for the last control-plane failover on the chassis, enter the show redundancy command in EXEC Privilege mode.
Dell# show redundancy
-- RPM Status --
------------------------------------------------
RPM Slot ID: 0
Control Plane Redundancy Role: Primary
RPM State: Active
RPM SW Version: 1-0(0-4095)
Link to Peer: Up
-- PEER RPM Status --
------------------------------------------------
RPM State: Standby
RPM SW Version: 1-0(0-4095)
-- Control Plane Redundancy Configuration --
------------------------------------------------
Primary RPM: rpm0
Auto Data Sync: Full
Failover Type: Hot Failover
Auto reboot RPM: Enabled
Auto failover limit: 3 times in 60 minutes
-- Control Plane Failover Record --
------------------------------------------------
Failover Count: 0
Last failover timestamp: None
Last failover Reason: None
Last failover type: None
-- Last Data Block Sync Record: --
------------------------------------------------
linecard Config: succeeded Jun 26 2015 22:56:16
Start-up Config: succeeded Jun 26 2015 22:56:16
Runtime Event Log: succeeded Jun 26 2015 22:56:16
Running Config: succeeded Jun 26 2015 22:56:16
378
High Availability (HA)