Reference Guide

To view which RPM is the primary, use the show running-config redundancy command from EXEC Privilege
mode, as shown in the example in the Forcing an RPM Failover.
Forcing an RPM Failover
To force an RPM failover, use the following command.
Use this feature when you are replacing an RPM and when you are performing a warm upgrade.
• To trigger an RPM failover between RPMs.
EXEC Privilege mode
redundancy force-failover rpm
Example of the redundancy force-failover rpm Command
FTOS#redundancy force-failover rpm
Peer RPM's SW version is different but HA compatible.
Failover can be done by warm or hitless upgrade.
All linecards will be reset during warm upgrade.
Specify hitless upgrade or warm upgrade [confirm hitless/warm]:hitless
Proceed with warm upgrade [confirm yes/no]:
Specifying an Auto-Failover Limit
When a non-recoverable fatal error is detected, an automatic failover occurs.
However, FTOS is configured to auto-failover only three times within any 60 minute period. You may specify a different
auto-failover count.
To re-enable the auto-failover-limit with its default parameters, use the redundancy auto-failover-limit
command without parameters.
• Set a different auto-failover count.
CONFIGURATION mode
redundancy auto-failover-limit
• Re-Enable the auto-failover-limit with its default parameters.
CONFIGURATION mode
redundancy auto-failover-limit
(no parameters)
Disabling Auto-Reboot
To disable auto-reboot, use the following command.
• Prevent a failed RPM from rebooting after a failover.
CONFIGURATION mode
redundancy disable-auto-reboot
Manually Synchronizing RPMs
To manually synchronize RPMs at any time, use the following command.
• Manually synchronize RPMs.
EXEC Privilege mode
redundancy synchronize full
337