Failover Count: 0
Last failover timestamp: None
Last failover Reason: None
Last failover type: None
-- Last Data Block Sync Record: --
------------------------------------------------
Stack Unit Config: no block sync done
Start-up Config: no block sync done
Runtime Event Log: no block sync done
Running Config: no block sync done
ACL Mgr: no block sync done
LACP: no block sync done
STP: no block sync done
SPAN: no block sync done
Dell#
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 31. 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
configuration 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
configuration data, operational data, state and status, and statistics depending on the Dell Networking OS
version.
Configuring 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
400
High Availability (HA)