Users Guide

Support for RPM Redundancy by Dell Networking OS Version
Dell Networking OS supports increasing levels of RPM redundancy (warm and hot) as described in the table below.
Table 33. Support for RPM Redundancy by Dell Networking OS Version
Platform Failover Type Failover Behavior
S4820T Hot Failover Only the failed RPM reboots. All the line
cards and SFMs remain online. All application
tasks are spawned on the secondary RPM
before failover. The running conguration is
synchronized at runtime so it does not need
to be reapplied during failover.
Synchronization between Management and Standby Units
Data between the Management and Standby units is synchronized immediately after bootup.
After the Management and Standby units have done an initial full synchronization (block sync), Dell Networking OS only updates changed
data (incremental sync). The data that is synchronized consists of conguration data, operational data, state and status, and statistics
depending on the Dell Networking OS version.
Conguring RPM Redundancy
To select a primary RPM, use the following command. The RPM in slot 0 is the primary RPM by default.
• Manually select the primary RPM.
CONFIGURATION mode
redundancy primary
Example of Viewing RPM Redundancy Conguration
Dell#show running-config redundancy
!
redundancy auto-failover-limit count 3 period 60
redundancy auto-synchronize full
redundancy primary rpm0
Dell#
To view which RPM is the primary, use the show running-config redundancy command from EXEC Privilege mode, as shown in
the example in the
Forcing an RPM Failover.
Forcing an Stack Unit Failover
To force an Stack unit failover, use the following command.
Use this feature when you are replacing a stack unit and when you are performing a warm upgrade.
• To trigger a stack unit failover.
EXEC Privilege mode
redundancy force-failover stack-unit
332
High Availability (HA)