Dell Force10 S4810P

444 | High Availability
www.dell.com | support.dell.com
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. Refer to:
• C-Series Debugging and Diagnostics, C-Series Debugging and Diagnostics
• E-Series TeraScale Debugging and Diagnostics, Inter-CPU timeouts
Support for RPM redundancy by FTOS version
FTOS supports increasing levels of RPM redundancy (warm and hot) as described in Table 21-3, "Support
for RPM Redundancy by FTOS Version," in High Availability.
e
RP IPC timeout for a non-task
crash reason on the primary 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.
c e
Hardware error detected on the
primary 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.
c e
Forced failover via the CLI 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.
c e
Primary RPM is removed The standby RPM detects the removal and initiates a failover. FTOS
collects no system information.
Table 21-3. Support for RPM Redundancy by FTOS Version
Failover Type Failover Behavior Platform
Warm Failover The new primary RPM remains online, while the failed RPM, all line cards, and all
SFMs reboot.
c e
Hot Failover 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.
c e
s
Table 21-2. Failover Behaviors
Platform Failover Trigger Failover Behavior