442 | High Availability
www.dell.com | support.dell.com
Automatic and manual RPM failover
RPM failover is the process of the standby RPM becoming the primary RPM. FTOS fails over to the
standby RPM when:
1. Communication is lost between the standby and primary RPMs
2. You request a failover via the CLI
3. You remove the primary RPM
Use the command
show redundancy from EXEC Privilege mode to display the reason for the last failover.
FTOS#show redundancy
-- RPM Status --
------------------------------------------------
RPM Slot ID: 0
RPM Redundancy Role: Primary
RPM State: Active
RPM SW Version: 7.6.1.0
Link to Peer: Up
-- PEER RPM Status --
------------------------------------------------
RPM State: Standby
RPM SW Version: 7.6.1.0
-- RPM Redundancy Configuration --
------------------------------------------------
Primary RPM: rpm0
Auto Data Sync: Full
Failover Type: Hot Failover
Auto reboot RPM: Enabled
Auto failover limit: 3 times in 60 minutes
-- RPM Failover Record --
------------------------------------------------
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
FTOS#
Communication between RPMs
E-Series RPMs have three CPUs: Control Processor (CP), Routing Processor 1 (RP1), and Routing
Processor 2 (RP2). The CPUs use Fast Ethernet connections to communicate to each other and to the line
card CPUs (LP) using Inter-Processor Communication (IPC). The CP monitors the health status of the
other processors by sending a heartbeat message. If any CPU fails to acknowledge a consecutive number
of heartbeat messages, or the CP itself fails to send heartbeat messages (IPC timeout), the primary RPM
requests a failover to the standby RPM, and FTOS displays a message similar to Message 4.