Dell Force10 C150 Configuration Manual page 384

Table 18-2. Failover Behaviors
Platform Failover Trigger
e
RP task or kernel crash on the
primary RPM
e
RP IPC timeout for a non-task
crash reason on the primary RPM
c e
Hardware error detected on the
primary RPM
c e
Forced failover via the CLI
c e
Primary RPM is removed
After a failover, the new primary RPM prompts you for a username and password if authentication
methods was configured and that data was synchronized. The standby RPM does not use authentication
methods involving client/server protocols, such as RADIUS and TACACS+.
FTOS logs information about IPC timeouts in a log file that you can access. See:
• Chapter 60, C-Series Debugging and Diagnostics, C-Series Debugging and Diagnostics on page 1167
• Chapter 61, E-Series TeraScale Debugging and Diagnostics, Inter-CPU timeouts on page 1206
Support for RPM redundancy by FTOS version
FTOS supports increasing levels of RPM redundancy (warm and hot) as described in
Table 18-3. Support for RPM Redundancy by FTOS Version
Failover Type
Warm Failover
Hot Failover
384 | High Availability
Failover Behavior
The new primary RPM remains online, while the failed RPM, all line cards, and all
SFMs reboot.
Only the failed RPM reboots.
All 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.
Failover Behavior
CP on the primary RPM detects the RP IPC timeout and notifies the
standby RPM. The standby RPM initiates a failover. FTOS saves an
RP application or kernel core dump, the CP trace log, and the CP
IPC-related system status. Then the new primary RPM reboots the
failed RPM.
CP on primary RPM detects the RP IPC timeout and notifies standby
RPM. Standby RPM initiates a failover. FTOS saves an RP
application core dump, RP IPC-related system status, a CP trace log
record, and the CP IPC-related system status. Then the new primary
RPM reboots the failed RPM.
FTOS detects the hardware error on the primary RPM and notifies the
standby RPM. The standby RPM initiates a failover. FTOS saves a
CP trace log, and a CP hardware nvtrace log. Then the new primary
RPM reboots the failed RPM.
CP on primary RPM notifies standby RPM and the standby RPM
initiates a failover. FTOS collects no system information. The former
primary RPM immediately reboots after failover.
The standby RPM detects the removal and initiates a failover. FTOS
collects no system information.
Table 18-3.
Platform
c e
c e
s