Setup Guide

-- 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
RPM Synchronization
Data between the primary (management) and standby RPMs is synchronized immediately after bootup.
After the two RPMs have performed an initial full synchronization (block sync), the system automatically updates only changed data
(incremental sync). The data that is synchronized consists of conguration data, operational data, state and status, and statistics
depending on the version of the Dell Networking OS.
You can manually synchronize the primary and standby RPMs at any time by entering the redundancy synchronize full
command.
Forcing an RPM Failover
To force an RPM failover, use the following command.
Use this feature when you are replacing an RPM and when you are performing a warm upgrade.
• To trigger an RPM failover.
EXEC Privilege mode
redundancy force-failover rpm
NOTE
: You can also force the port extender to failover from the RPM, using the redundancy force-failover pe
pe-id command in EXEC Privilege mode.
Example of the redundancy force-failover rpm Command
Dell#redundancy force-failover rpm
Dell#redundancy force-failover pe
pe-id
High Availability (HA)
425