CISCO-RF-MIB

All MIBs › CISCO-RF-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2005-09-01

Category: Cisco Devices, Device Management

Description: Provides configuration control and status for the Redundancy Framework (RF) subsystem, supporting 1:1 redundancy on processor cards.

IPNetwork Monitor uses several OIDs from this MIB in network discovery and polling the applicable devices. Start monitoring CISCO-RF-MIB with a free 30-day trial of IPNetwork Monitor.

What Is CISCO-RF-MIB?

CISCO-RF-MIB provides configuration control and status for Cisco's Redundancy Framework (RF), the software subsystem that supports 1:1 stateful redundancy between duplicate processor/supervisor cards in Cisco routers and switches. It exposes status data on the active and standby unit roles, their operational states, the redundancy mode (primary/duplex), and details of any switchover (swact) events including the reason code and timing. This MIB is central to monitoring high-availability software status: it lets an operator confirm which unit is currently active versus standby, detect unexpected or manually forced switchovers, and measure failover time to validate that stateful switchover (SSO) is meeting service-level targets. Since the RF subsystem explicitly excludes redundant hardware such as power supplies, it complements rather than depends on separate hardware-redundancy MIBs while underlying higher-level Cisco HA features. It is typically deployed on Cisco platforms with dual route processor or supervisor cards, such as core routers and Catalyst switches running NSF/SSO for high availability. This is a heavily searched Cisco MIB, since cisco-rf-mib governs Cisco IOS Redundancy Framework state monitoring across dual-supervisor/dual-RP platforms.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-RF-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco routers/switches with dual route processor or supervisor cards

Monitoring Examples

An admin would poll cRFStatusUnitId and cRFStatusUnitState against cRFStatusPeerUnitId and cRFStatusPeerUnitState to confirm one unit is ACTIVE and its peer is STANDBY-HOT, then check cRFStatusPrimaryMode and cRFStatusDuplexMode to verify the redundancy configuration is correct. If cRFStatusLastSwactReasonCode indicates an unexpected reset rather than a manual switchover, combined with a large cRFStatusFailoverTime, that flags an unplanned failover event worth investigating. The cRFStatusRFModeCapsTable/Entry can also be checked to confirm which redundancy modes the platform actually supports.

What Can Be Monitored

active/standby unit role
peer unit state
redundancy mode (primary/duplex)
last switchover reason
failover time
manual switchover inhibit setting

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-MIB

sysUpTime

OBJECT-TYPE

From SNMPv2-SMI

Counter32
Integer32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

DateAndTime
TEXTUAL-CONVENTION
TimeInterval
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using cRFHistoryColdStarts OID:

Select a Cisco routers/switch as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cRFHistoryColdStarts into the Find box to locate it in the OID tree, then select it and click OK. Indicates the number of system cold starts. This includes the number of system cold starts due to switchover failure and the number of manual restarts. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases between polls, since a rising count of errors, failures, or discards often points to a real underlying problem. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoRFConfigGroup	1.3.6.1.4.1.9.9.176.3.2.2			The collection of RF configuration objects.
ciscoRFConfigGroupRev1	1.3.6.1.4.1.9.9.176.3.2.4			The collection of RF configuration objects.
ciscoRFConfigRFOperModeGroup	1.3.6.1.4.1.9.9.176.3.2.7			An optional group with a collection of objects providing the information of the operational redundancy mode on the device.
ciscoRFHistoryGroup	1.3.6.1.4.1.9.9.176.3.2.6			The collection of RF History objects.
NTF ciscoRFIssuStateNotif	1.3.6.1.4.1.9.9.176.2.0.3			An ISSU notification to indicate the new state of the system.
ciscoRFIssuStateNotifGroup	1.3.6.1.4.1.9.9.176.3.2.9			The collection of notifications used to indicate ISSU state of the system.
ciscoRFIssuStateNotifGroupRev1	1.3.6.1.4.1.9.9.176.3.2.10			The collection of notifications used to indicate ISSU state of the system.
NTF ciscoRFIssuStateNotifRev1	1.3.6.1.4.1.9.9.176.2.0.4			An ISSU notification to indicate the new state of the system.
ciscoRFIssuStateObjGroup	1.3.6.1.4.1.9.9.176.3.2.11			An optional group with a collection of objects providing the information on the current ISSU state of the system.
ciscoRFIssuStateObjGroupRev1	1.3.6.1.4.1.9.9.176.3.2.12			An optional group with a collection of objects providing the information on the current ISSU state of the system.
ciscoRFMIB	1.3.6.1.4.1.9.9.176			This MIB provides configuration control and status for the Redundancy Framework (RF) subsystem. RF provides a mechanism for logical redundancy of software functionality and is designed to support 1:1 redundancy on processor cards. RF is not intended to solve all redundancy schemes. Nor is RF designed to support redundant hardware, such as power supplies. Redundancy is concerned with the duplication of data elements and software functions to provide an alternative in case of failure. It is a key component to meeting 99.999% availability requirements for Class 5 carrier solutions. In the scope of this MIB definition, peer software elements are redundant and redundant software elements are peers.
ciscoRFMIBCompliance	1.3.6.1.4.1.9.9.176.3.1.1			The compliance statement for entities which implement the Cisco RF MIB.
ciscoRFMIBComplianceRev1	1.3.6.1.4.1.9.9.176.3.1.2			The compliance statement for entities which implement the Cisco RF MIB
ciscoRFMIBComplianceRev2	1.3.6.1.4.1.9.9.176.3.1.3			The compliance statement for entities which implement the Cisco RF MIB.
ciscoRFMIBComplianceRev3	1.3.6.1.4.1.9.9.176.3.1.4			The compliance statement for entities which implement the Cisco RF MIB.
ciscoRFMIBComplianceRev4	1.3.6.1.4.1.9.9.176.3.1.5			The compliance statement for entities which implement the Cisco RF MIB.
ciscoRFMIBComplianceRev5	1.3.6.1.4.1.9.9.176.3.1.6			The compliance statement for entities which implement the Cisco RF MIB.
ciscoRFMIBCompliances	1.3.6.1.4.1.9.9.176.3.1
ciscoRFMIBConformance	1.3.6.1.4.1.9.9.176.3
ciscoRFMIBGroups	1.3.6.1.4.1.9.9.176.3.2
ciscoRFMIBNotifications	1.3.6.1.4.1.9.9.176.2.0
ciscoRFMIBNotificationsPrefix	1.3.6.1.4.1.9.9.176.2
ciscoRFMIBObjects	1.3.6.1.4.1.9.9.176.1
ciscoRFNotifGroup	1.3.6.1.4.1.9.9.176.3.2.3			The collection of notifications used to indicate RF state information.
NTF ciscoRFProgressionNotif	1.3.6.1.4.1.9.9.176.2.0.2			A progression notification is sent by the active redundant unit whenever its RF state changes or the RF state of the peer unit changes. To avoid a flurry of notifications for all state transitions, notifications will only be sent for transitions to the following RF states: disabled (for the peer state) standbyCold standbyHot active activeExtraload
ciscoRFStatusClientGroup	1.3.6.1.4.1.9.9.176.3.2.13			A group of objects providing information regarding the various clients registered with the RF.
ciscoRFStatusGroup	1.3.6.1.4.1.9.9.176.3.2.1			The collection of global RF status objects.
ciscoRFStatusGroupRev1	1.3.6.1.4.1.9.9.176.3.2.5			The collection of global RF Status objects.
ciscoRFStatusRFModeCapsGroup	1.3.6.1.4.1.9.9.176.3.2.8			An optional group with a collection of objects providing the information of redundancy mode capability on the device.
NTF ciscoRFSwactNotif	1.3.6.1.4.1.9.9.176.2.0.1			A SWACT notification is sent by the newly active redundant unit whenever a switch of activity occurs. In the case where a SWACT event may be indistinguishable from a reset event, a network management station should use this notification to differentiate the activity. sysUpTime is the same sysUpTime defined in the RFC-1213 MIB.
cRFCfg	1.3.6.1.4.1.9.9.176.1.2
RFA cRFCfgAdminAction	1.3.6.1.4.1.9.9.176.1.2.11	RFAction	read-write	This variable is set to invoke RF subsystem action commands. The commands are useful for maintenance and software upgrade activities.
U32 cRFCfgKeepaliveThresh	1.3.6.1.4.1.9.9.176.1.2.2	Unsigned32	read-write	On platforms that support keep-alives, the keep-alive threshold value designates the number of lost keep-alives tolerated before a failure condition is declared. If this occurs, a SWACT notification is sent. On platforms that do not support keep-alives, this object has no purpose or effect.
U32 cRFCfgKeepaliveThreshMax	1.3.6.1.4.1.9.9.176.1.2.4	Unsigned32	read-only	The maximum acceptable value for the cRFCfgKeepaliveThresh object.
U32 cRFCfgKeepaliveThreshMin	1.3.6.1.4.1.9.9.176.1.2.3	Unsigned32	read-only	The minimum acceptable value for the cRFCfgKeepaliveThresh object.
U32 cRFCfgKeepaliveTimer	1.3.6.1.4.1.9.9.176.1.2.5	Unsigned32	read-write	On platforms that support keep-alives, the keep-alive timer value is used to guard against lost keep-alives. The RF subsystem expects to receive a keep-alive within this period. If a keep-alive is not received within this time period, a SWACT notification is sent. On platforms that do not support keep-alives, this object has no purpose or effect.
U32 cRFCfgKeepaliveTimerMax	1.3.6.1.4.1.9.9.176.1.2.7	Unsigned32	read-only	The maximum acceptable value for the cRFCfgKeepaliveTimer object.
U32 cRFCfgKeepaliveTimerMin	1.3.6.1.4.1.9.9.176.1.2.6	Unsigned32	read-only	The minimum acceptable value for the cRFCfgKeepaliveTimer object.
T/F cRFCfgMaintenanceMode	1.3.6.1.4.1.9.9.176.1.2.13	TruthValue	read-write	Indicates whether redundant units may communicate synchronization messages with each other. If communication is not permitted, this object is set to 'true'. If communication is permitted, this object is set to 'false'. If the value of this object is 'true', the redundant system is considered to be in a maintenance mode of operation. If the value of this object is 'false', the redundant system is considered to be in a normal (non-maintenance) mode of operation. In maintenance mode (true), the active unit will not communicate with the standby unit. The standby unit progression will not occur. When maintenance mode is disabled (false), the standby unit is reset to recover. Maintenance mode (true) is useful for maintenance-type operations.
T/F cRFCfgNotifsEnabled	1.3.6.1.4.1.9.9.176.1.2.12	TruthValue	read-write	Allows enabling/disabling of RF subsystem notifications.
U32 cRFCfgNotifTimer	1.3.6.1.4.1.9.9.176.1.2.8	Unsigned32	read-write	Note that the term 'notification' here refers to an RF notification and not an SNMP notification. As the standby unit progresses to the 'standbyHot' state, asynchronous messages are sent from the active unit to the standby unit which must then be acknowledged by the standby unit. If the active unit receives the acknowledgement during the time period specified by this object, progression proceeds as normal. If the timer expires and an acknowledgement was not received by the active unit, a switch of activity occurs.
U32 cRFCfgNotifTimerMax	1.3.6.1.4.1.9.9.176.1.2.10	Unsigned32	read-only	The maximum acceptable value for the cRFCfgNotifTimer object.
U32 cRFCfgNotifTimerMin	1.3.6.1.4.1.9.9.176.1.2.9	Unsigned32	read-only	The minimum acceptable value for the cRFCfgNotifTimer object.
RFM cRFCfgRedundancyMode	1.3.6.1.4.1.9.9.176.1.2.14	RFMode	read-write	Indicates the redundancy mode configured on the device.
STR cRFCfgRedundancyModeDescr	1.3.6.1.4.1.9.9.176.1.2.15	SnmpAdminString	read-only	Further clarifies or describes the redundancy mode indicated by cRFCfgRedundancyMode. Implementation-specific terminology associated with the current redundancy mode may be presented here.
RFM cRFCfgRedundancyOperMode	1.3.6.1.4.1.9.9.176.1.2.16	RFMode	read-only	Indicate the operational redundancy mode of the device.
T/F cRFCfgSplitMode	1.3.6.1.4.1.9.9.176.1.2.1	TruthValue	read-write	Indicates whether redundant units may communicate synchronization messages with each other. If communication is not permitted, this object is set to true. If communication is permitted, this object is set to false. In split mode (true), the active unit will not communicate with the standby unit. The standby unit progression will not occur. When split mode is disabled (false), the standby unit is reset to recover. Split mode (true) is useful for maintenance operations.
cRFClient	1.3.6.1.4.1.9.9.176.1.4
cRFHistory	1.3.6.1.4.1.9.9.176.1.3
C32 cRFHistoryColdStartsEx	1.3.6.1.4.1.9.9.176.1.3.3	Counter32	read-only	Indicates the number of system cold starts. This includes the number of system cold starts due to switchover failure and the number of manual restarts.
OID cRFHistoryCurrActiveUnitId	1.3.6.1.4.1.9.9.176.1.3.2.1.3	RFUnitIdentifier	read-only	Indicates the secondary redundant unit that took over as active.
OID cRFHistoryPrevActiveUnitId	1.3.6.1.4.1.9.9.176.1.3.2.1.2	RFUnitIdentifier	read-only	Indicates the primary redundant unit that went down.
NUM cRFHistoryStandByAvailTime	1.3.6.1.4.1.9.9.176.1.3.4	TimeInterval	read-only	Indicates the cumulative time that a standby redundant unit has been available since last system initialization.
DAT cRFHistorySwactTime	1.3.6.1.4.1.9.9.176.1.3.2.1.5	DateAndTime	read-only	Indicates the Date & Time when switchover occurred.
cRFHistorySwitchOverEntry	1.3.6.1.4.1.9.9.176.1.3.2.1		not-accessible	The entries in this table contain the switchover information. Each entry in the table is indexed by cRFHistorySwitchOverIndex. The index wraps around to 1 after reaching the maximum value.
U32 cRFHistorySwitchOverIndex	1.3.6.1.4.1.9.9.176.1.3.2.1.1	Unsigned32	not-accessible	A monotonically increasing integer for the purpose of indexing history table. After reaching maximum value, it wraps around to 1.
RFS cRFHistorySwitchOverReason	1.3.6.1.4.1.9.9.176.1.3.2.1.4	RFSwactReasonType	read-only	Indicates the reason for the switchover.
cRFHistorySwitchOverTable	1.3.6.1.4.1.9.9.176.1.3.2		not-accessible	A table that tracks the history of all switchovers that have occurred since system initialization. The maximum number of entries permissible in this table is defined by cRFHistoryTableMaxLength. When the number of entries in the table reaches the maximum limit, the next entry would replace the oldest existing entry in the table.
U32 cRFHistoryTableMaxLength	1.3.6.1.4.1.9.9.176.1.3.1	Unsigned32	read-write	Maximum number of entries permissible in the history table. A value of 0 will result in no history being maintained.
cRFStatus	1.3.6.1.4.1.9.9.176.1.1
T/F cRFStatusDuplexMode	1.3.6.1.4.1.9.9.176.1.1.6	TruthValue	read-only	Indicates whether the redundant peer unit has been detected or not. If the redundant peer unit is detected, this object is true. If the redundant peer unit is not detected, this object is false.
TIM cRFStatusFailoverTime	1.3.6.1.4.1.9.9.176.1.1.9	TimeStamp	read-only	The value of sysUpTime when the primary redundant unit took over as active. The value of this object will be 0 till the first switchover.
STR cRFStatusIssuFromVersion	1.3.6.1.4.1.9.9.176.1.1.14	SnmpAdminString	read-only	The IOS version from with the user is upgrading
RFI cRFStatusIssuState	1.3.6.1.4.1.9.9.176.1.1.12	RFIssuState	read-only	The current ISSU state of the system.
RFI cRFStatusIssuStateRev1	1.3.6.1.4.1.9.9.176.1.1.13	RFIssuStateRev1	read-only	The current ISSU state of the system.
STR cRFStatusIssuToVersion	1.3.6.1.4.1.9.9.176.1.1.15	SnmpAdminString	read-only	The IOS version to with the user is upgrading
RFS cRFStatusLastSwactReasonCode	1.3.6.1.4.1.9.9.176.1.1.8	RFSwactReasonType	read-only	The reason for the last switch of activity.
T/F cRFStatusManualSwactInhibit	1.3.6.1.4.1.9.9.176.1.1.7	TruthValue	read-only	Indicates whether a manual switch of activity is permitted. If a manual switch of activity is allowed, this object is false. If a manual switch of activity is not allowed, this object is true. Note that the value of this object is the inverse of the status of manual SWACTs. This object does not indicate whether a switch of activity is or has occurred. This object only indicates if the user-controllable capability is enabled or not. A switch of activity is the event in which the standby redundant unit becomes active and the previously active unit becomes standby.
TIM cRFStatusPeerStandByEntryTime	1.3.6.1.4.1.9.9.176.1.1.10	TimeStamp	read-only	The value of sysUpTime when the peer redundant unit entered the standbyHot state. The value will be 0 on system initialization.
OID cRFStatusPeerUnitId	1.3.6.1.4.1.9.9.176.1.1.3	RFUnitIdentifier	read-only	A unique identifier for the redundant peer unit. This identifier is implementation-specific but the method for selecting the id must remain consistent throughout the redundant system. Some example identifiers include: slot id, physical or logical entity id, or a unique id assigned internally by the RF subsystem.
RFS cRFStatusPeerUnitState	1.3.6.1.4.1.9.9.176.1.1.4	RFState	read-only	The current state of RF on the peer unit.
T/F cRFStatusPrimaryMode	1.3.6.1.4.1.9.9.176.1.1.5	TruthValue	read-only	Indicates whether this is the primary redundant unit or not. If this unit is the primary unit, this object is true. If this unit is the secondary unit, this object is false. Note that the terms 'primary/secondary' are not synonymous with the terms 'active/standby'. At any given time, the primary unit may be the active unit, or the primary unit may be the standby unit. Likewise, the secondary unit, at any given time, may be the active unit, or the secondary unit may be the standby unit. The primary unit is given a higher priority or precedence over the secondary unit. In a race condition (usually at initialization time) or any situation where the redundant units are unable to successfully negotiate activity between themselves, the primary unit will always become the active unit and the secondary unit will fall back to standby. Only one redundant unit can be the primary unit at any given time. The algorithm for determining the primary unit is system dependent, such as 'the redundant unit with the lower numeric unit id is always the primary unit.'
STR cRFStatusRFClientDescr	1.3.6.1.4.1.9.9.176.1.4.1.1.2	SnmpAdminString	read-only	The description of the client which has registered with the Redundancy Facility.
cRFStatusRFClientEntry	1.3.6.1.4.1.9.9.176.1.4.1.1		not-accessible	An entry containing information on various clients registered with the Redundancy Facility (RF). Entries in this table are always created by the system. An entry is created in this table when a redundancy aware application registers with the Redundancy Facility. The entry is destroyed when that application deregisters from the Redundancy Facility.
U32 cRFStatusRFClientID	1.3.6.1.4.1.9.9.176.1.4.1.1.1	Unsigned32	not-accessible	A unique identifier for the client which registered with the Redundancy Facility.
U32 cRFStatusRFClientRedTime	1.3.6.1.4.1.9.9.176.1.4.1.1.4	Unsigned32	read-only	Time taken for this client to become Redundant. This value is meaningful when the value of cRFStatusRFClientStatus is not 'noStatus'.
U32 cRFStatusRFClientSeq	1.3.6.1.4.1.9.9.176.1.4.1.1.3	Unsigned32	read-only	The sequence number of the client. The system assigns the sequence numbers based on the order of registration of the Redundancy Facility clients. This is used for deciding order of RF events sent to clients.
RFC cRFStatusRFClientStatus	1.3.6.1.4.1.9.9.176.1.4.1.1.5	RFClientStatus	read-only	This object provides the status of the Redundancy Facility client.
cRFStatusRFClientTable	1.3.6.1.4.1.9.9.176.1.4.1		not-accessible	This table contains a list of RF clients that are registered on the device. RF clients are applications that have registered with the Redundancy Facility (RF) to receive RF events and notifications. The purpose of RF clients is to synchronize any relevant data with the standby unit.
cRFStatusRFModeCapsEntry	1.3.6.1.4.1.9.9.176.1.1.11.1		not-accessible	An entry containing the device implementation specific terminology associated with the redundancy mode that can be supported on the device.
RFM cRFStatusRFModeCapsMode	1.3.6.1.4.1.9.9.176.1.1.11.1.1	RFMode	not-accessible	The redundancy mode that can be supported on the device.
STR cRFStatusRFModeCapsModeDescr	1.3.6.1.4.1.9.9.176.1.1.11.1.2	SnmpAdminString	read-only	The description of the device implementation specific terminology associated with its supported redundancy mode.
cRFStatusRFModeCapsTable	1.3.6.1.4.1.9.9.176.1.1.11		not-accessible	This table containing a list of redundancy modes that can be supported on the device.
OID cRFStatusUnitId	1.3.6.1.4.1.9.9.176.1.1.1	RFUnitIdentifier	read-only	A unique identifier for this redundant unit. This identifier is implementation-specific but the method for selecting the id must remain consistent throughout the redundant system. Some example identifiers include: slot id, physical or logical entity id, or a unique id assigned internally by the RF subsystem.
RFS cRFStatusUnitState	1.3.6.1.4.1.9.9.176.1.1.2	RFState	read-only	The current state of RF on this unit.

RFC description

Redundancy Framework subsystem for Cisco devices, managing 1:1 redundancy of processor cards and software failover.

Start monitoring Cisco routers/switches with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-RF-MIB