Reference Guide

Table Of Contents
Example of Boot Failure on Standby RPM
System failed to boot up. Please reboot the chassis !!!
00:12:46: %RPM1-U:CP %TME-0-RPM BRINGUP FAIL: FTOS failed to bring up the system
Communication between RPMs is not up, check the software version and reboot
chassis.
FTOS(standby)(bootfail)#
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.
To display the reason for the last failover, use the show redundancy command from EXEC Privilege mode.
Example of the show redundancy Command
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#
337