Cisco Cisco IOS Software Release 12.0(23)S
Stateful Switchover
Configuration Examples
33
Cisco IOS Release 12.0(23)S
Note
On the Cisco 10000 series Internet router, if the router images are not the same the router will recover
in RPR+ mode as long as the images are SSO-capable. If both images are not SSO-capable, the router
will recover in RPR mode.
in RPR+ mode as long as the images are SSO-capable. If both images are not SSO-capable, the router
will recover in RPR mode.
Reloading the device disrupts SSO operation.
The SSO feature introduces a number of commands, including commands to manually cause a
switchover. The reload command is not an SSO command. This command causes a full reload of the box,
removing all table entries, resetting all line cards, and thereby interrupting network traffic forwarding.
To avoid reloading the box unintentionally, use the redundancy force-switchover command.
switchover. The reload command is not an SSO command. This command causes a full reload of the box,
removing all table entries, resetting all line cards, and thereby interrupting network traffic forwarding.
To avoid reloading the box unintentionally, use the redundancy force-switchover command.
During a software upgrade, the networking device appears to be in a mode other than SSO.
During the software upgrade process, the show redundancy command indicates that the device is running
in a mode other than SSO.
in a mode other than SSO.
This is normal behavior. Until the FSU procedure is complete, each RP will be running a different
software version. While the RPs are running different software versions, the mode will change to either
RPR or RPR+, depending on the device. The device will change to SSO mode once the upgrade has
completed.
software version. While the RPs are running different software versions, the mode will change to either
RPR or RPR+, depending on the device. The device will change to SSO mode once the upgrade has
completed.
On the Cisco 7500 series router, the previously active processor is being reset and reloaded before the core dump
completes.
completes.
Use the crashdump-timeout command to set the maximum time that the newly active processor waits
before resetting and reloading the previously active processor.
before resetting and reloading the previously active processor.
On the Cisco 7500 series router, issuing a “send break” does not cause a system switchover.
This is normal operation on the Cisco 7500 series router. Using “send break” to break or pause the
system is not recommended and may cause unpredictable results. To initiate a manual switchover, use
the redundancy force-switchover command.
system is not recommended and may cause unpredictable results. To initiate a manual switchover, use
the redundancy force-switchover command.
In Cisco IOS software, you can enter ROM monitor mode by restarting the router and then pressing the
Break key or issuing a “send break” command from a telnet session during the first 60 seconds of
startup.The send break function can be useful for experienced users or for users under the direction of a
Cisco Technical Assistance Center (TAC) representative to recover from certain system problems or to
evaluate the cause of system problems.
Break key or issuing a “send break” command from a telnet session during the first 60 seconds of
startup.The send break function can be useful for experienced users or for users under the direction of a
Cisco Technical Assistance Center (TAC) representative to recover from certain system problems or to
evaluate the cause of system problems.
On Cisco 10000 and 12000 series Internet routers, if a standby RP is present, the system will detect the
break and complete a switchover; however, this is not the recommended procedure for initiating a
switchover. To initiate a manual switchover, use the redundancy force-switchover command.
break and complete a switchover; however, this is not the recommended procedure for initiating a
switchover. To initiate a manual switchover, use the redundancy force-switchover command.
Configuration Examples
This section provides the following configuration examples:
•
•
•
•
Configuring Autosync LMI Sequence Numbers Example