Reference Guide

Failover Count: 0
Last failover timestamp: None
Last failover Reason: None
Last failover type: None
-- Last Data Block Sync Record: --
------------------------------------------------
Line Card Config: succeeded May 19 2008 11:34:06
Start-up Config: succeeded May 19 2008 11:34:06
Runtime Event Log: succeeded May 19 2008 11:34:06
Running Config: succeeded May 19 2008 11:34:07
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 28. 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.
RPM Synchronization
Data between the two RPMs is synchronized immediately after bootup.
After the two RPMs 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.
Table 29. RPM Synchronized Data by Platform
Platform Failover Type Synchronized Data
S8410 S4820T Warm Failover Some NVRAM information,
startup-configuration, line card
configurations, and user-access
configurations.
S8410 S4820T Hot Failover Some NVRAM information,
startup-config, line card
configurations, user-access
configurations, running-config,
SFM and datapath states, run-
time event log and configuration,
and interface state.
388
High Availability (HA)