Cisco Cisco IOS Software Release 12.0(22)S
E F T 2 D R A F T - C I S C O C O N F I D E N T I A L
SNMP for Stateful Switchover
Feature Overview
4
Cisco IOS Release 12.0(22)S
•
The cRFHistorySwitchOverTable has been added. This new table tracks the history of switchovers
that have occurred since system initialization. New objects that have been added as part of this table
are as follows:
that have occurred since system initialization. New objects that have been added as part of this table
are as follows:
–
cRFHistoryPrevActiveUnitId—A read-only object that indicates the active RP that went down.
The value of this object is the unique ID of the active RP that has gone down. The ID can be the
slot ID, the physical or logical entity ID, or a unique ID assigned by the RF.
The value of this object is the unique ID of the active RP that has gone down. The ID can be the
slot ID, the physical or logical entity ID, or a unique ID assigned by the RF.
–
cRFHistoryCurrActiveUnitId—A read-only object that indicates the standby RP that took over
as the active RP. The value of this object is the unique ID of the active RP. The ID can be the
slot ID, the physical or logical entity ID, or a unique ID assigned by the RF.
as the active RP. The value of this object is the unique ID of the active RP. The ID can be the
slot ID, the physical or logical entity ID, or a unique ID assigned by the RF.
–
cRFHistorySwitchOverReason—A read-only object that indicates the reason for the
switchover. The reasons for the switchover from the active RP to the standby RP can be any of
the following:
switchover. The reasons for the switchover from the active RP to the standby RP can be any of
the following:
- unsupported—This feature is unsupported.
- none—No switchover has occurred.
- notKnown—The reason is unknown.
- userInitiated—A safe, manual switchover was initiated by the user.
- userForced—A manual switchover was forced by the user. Preconditions, warnings, and safety
checks were ignored.
checks were ignored.
- activeUnitFailed—An active RP fault caused an automatic switchover.
- activeUnitRemoved—The active RP was removed, which caused an automatic switchover.
–
cRFHistorySwactTime—A read-only object that indicates the date and time the switchover
occurred. The value of this object is a time stamp with the date and time the switchover
occurred.
occurred. The value of this object is a time stamp with the date and time the switchover
occurred.
•
cRFHistoryTableMaxLength—A read-write object that indicates the maximum number of entries
permissible in the history table. The value of this object is an integer that is more than 0. A value of
0 results in no history being maintained.
permissible in the history table. The value of this object is an integer that is more than 0. A value of
0 results in no history being maintained.
•
cRFHistoryColdStarts—A read-only object that indicates the number of system cold starts including
the number of system cold starts due to switchover fault and the number of manual restarts.
the number of system cold starts due to switchover fault and the number of manual restarts.
•
cRFHistoryStandByAvailTime—A read-only object that indicates the cumulative time that a
standby redundant unit has been available since the last system initialization.
standby redundant unit has been available since the last system initialization.
Two objects related to switchover status have been added:
•
cRFStatusFailoverTime—A read-only object that indicates the sysUpTime value when the primary
redundant unit took over as active. The value of this object is 0 until the first switchover.
redundant unit took over as active. The value of this object is 0 until the first switchover.
•
cRFStatusPeerStandByEntryTime—A read-only object that indicates the sysUpTime value when
the peer redundant unit entered the standbyHot state. The value of this object is 0 on system
initialization.
the peer redundant unit entered the standbyHot state. The value of this object is 0 on system
initialization.
Benefits
SNMP network management with SSO functionality ensures an uninterrupted management interface to
the end user. The network administrator can differentiate a switchover from a system restart based on the
notification type (for example, ciscoRFSwactNotif for switchover and coldStart or warmStart for system
restarts). Uninterrupted service also includes synchronizing the SNMP configuration and data from core
MIBs such as IF-MIB and ENTITY-MIB to the standby RP.
the end user. The network administrator can differentiate a switchover from a system restart based on the
notification type (for example, ciscoRFSwactNotif for switchover and coldStart or warmStart for system
restarts). Uninterrupted service also includes synchronizing the SNMP configuration and data from core
MIBs such as IF-MIB and ENTITY-MIB to the standby RP.