CISCO-RF-SUPPLEMENTAL-MIB

All MIBs › CISCO-RF-SUPPLEMENTAL-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2019-02-22

Category: Cisco Devices, Device Management

Description: Provides supplemental objects for Cisco Redundancy Framework stateful switchover and HA configuration.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) 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.

What Is CISCO-RF-SUPPLEMENTAL-MIB?

CISCO-RF-SUPPLEMENTAL-MIB is a Cisco module that complements the Redundancy Framework (CISCO-RF-MIB) by providing additional optional status and configuration-control objects for redundant-CPU platforms such as dual Route Processor or dual Supervisor routers and switches. It exposes data about switchover history and timing, and about synchronization state between the active and standby processor for the running configuration, startup configuration, and boot image. This makes it a direct tool for monitoring the software/hardware health of high-availability platforms: administrators can watch switchover counts and elapsed switchover time to detect unplanned failovers, and check config/boot-image sync status and sync timestamps to confirm the standby processor is ready to take over cleanly. The module deliberately avoids referencing CISCO-RF-MIB objects or RF states directly, so it can be used even on redundant platforms that don't use the RF Redundancy Framework software. It is typically deployed on core/distribution-layer Cisco routers and Catalyst switches configured with redundant supervisors for high availability. Engineers can download the CISCO-RF-SUPPLEMENTAL-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-RF-SUPPLEMENTAL-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 router with redundant supervisors/RP
Cisco Catalyst switch with dual supervisors

Monitoring Examples

An operator would poll cRfSupSysSwitchovers and cRfSupSysSwitchoverTime to detect how many stateful switchovers have occurred and when the last one happened, which is a strong signal of supervisor instability if the count increases unexpectedly. Alongside that, cRfSupSysRunningConfigSyncTime, cRfSupSysRunningConfigAdmin/Oper and the equivalent cRfSupSysStartupConfigSyncTime and cRfSupSysBootImageSyncTime/Admin/Oper objects reveal whether the standby unit's configuration and boot image are actually synchronized with the active unit. If cRfSupSysBootImageOper shows out-of-sync while cRfSupSysAvailableStartTime shows the standby has been up for a long time, that flags a redundancy configuration problem needing attention before a real failover is needed.

What Can Be Monitored

switchover count and timing
running-config sync status
startup-config sync status
boot image sync status
standby processor availability start time

Imported Objects

From CISCO-CONFIG-COPY-MIB

ConfigCopyState

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From ENTITY-MIB

PhysicalIndex

From IF-MIB

ifAdminStatus	OBJECT-TYPE
ifIndex	OBJECT-TYPE
ifOperStatus	OBJECT-TYPE

From SNMP-FRAMEWORK-MIB

SnmpAdminString

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter32
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

DateAndTime
TEXTUAL-CONVENTION
TruthValue

How to Use in IPNetwork Monitor

Example using cRfSupSysSwitchovers OID:

Select a Cisco router/Catalyst switch with redundant supervisors/RP 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 cRfSupSysSwitchovers into the Find box to locate it in the OID tree, then select it and click OK. The number of times that switchovers have occurred since cRfSupSysAvailableStartTime. 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 sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoRfSupMIB	1.3.6.1.4.1.9.9.198			This MIB was designed to complement the CISCO-RF-MIB by providing additional optional status and configuration control for redundant CPU platforms. However, the MIB should also be applicable to redundant platforms which don't use the RF Redundancy Framework software since it makes no direct references to any CISCO-RF-MIB objects or textual conventions and no direct reference to any RF states, RF events or internal information. Glossary of terms used in this document: Active - A redundant CPU which is actively controlling the system. Running configuration - The runtime configuration of a system which reflects current configured hardware or software settings. Runtime configuration which is not stored in non-volatile memory may be lost if the system loses power. Standby - A redundant CPU which is not currently controlling the system, but which can take over control if the Active CPU fails. Startup configuration - A copy of system configuration stored in non-volatile memory which can be applied following a system powerup. For platforms where all runtime configuration is automatically stored in a non-volatile manner, the running and startup configurations are always identical. Switchover - The transfer of control from one CPU to a redundant CPU. Sync - The mirroring (or synchronizing) of system state, configuration, statistics or other information from the Active CPU to a Standby CPU to allow it to maintain full system control following a switchover.
ciscoRfSupMIBNotifs	1.3.6.1.4.1.9.9.198.0
NTF ciscoRfSupTimeChangeEvent	1.3.6.1.4.1.9.9.198.0.1			This notification is sent on the event of system clock modification causing a change in the values of cRfSupSysAvailableStartTime or cRfSupSysSwitchoverTime objects, if cRfSupNotificationsEnabled object has value 'true'. If the system clock change is a result of a time zone change event,this notification will not be sent.
NTF ciscoRfSupTimeZoneChangeEvent	1.3.6.1.4.1.9.9.198.0.2			This notification is sent on the event of system time zone modification causing a change in the values of cRfSupSysAvailableStartTime or cRfSupSysSwitchoverTime objects, if cRfSupNotificationsEnabled object has value 'true'.
NTF ciscoRfSupHAFailureEvent	1.3.6.1.4.1.9.9.198.0.3			This notification is sent on the event of a generic failure between the active and standby unit
NTF ciscoRfSupPeerLinkStateChangeEvent	1.3.6.1.4.1.9.9.198.0.4			This notification is sent on the event of a Standby Port state change
ciscoRfSupMIBObjects	1.3.6.1.4.1.9.9.198.1
cRfSupSystem	1.3.6.1.4.1.9.9.198.1.1
DAT cRfSupSysAvailableStartTime	1.3.6.1.4.1.9.9.198.1.1.1	DateAndTime	read-only	The date and time when this system began providing uninterrupted operation. This includes the time while either redundant unit was Active, but may also include brief intervals during switchover where the new Active unit was operational, but not yet reachable for network management purposes. It may also include intervals where no Standby unit was offering protection, as long as the Active unit was still operational. It normally changes only if an unprotected system restart occurs or if a Standby unit was forced to take over before the initial database sync was completed. However, it may also change if the system's Time of Day clock is changed or adjusted. This object will be inaccurate if the system's Time of Day clock has not been set accurately. However, it should be implemented in such a way that when the system's Time of Day clock is adjusted to an accurate setting, cRfSupSysAvailableStartTime will also adjust to show the accurate available start time.
DAT cRfSupSysSwitchoverTime	1.3.6.1.4.1.9.9.198.1.1.2	DateAndTime	read-only	The date and time when the last CPU switchover took place. This object will remain uninstantiated if no switchovers have taken place since the current Active CPU was initialized.
C32 cRfSupSysSwitchoversEx	1.3.6.1.4.1.9.9.198.1.1.3	Counter32	read-only	The number of times that switchovers have occurred since cRfSupSysAvailableStartTime. This object will remain uninstantiated if no switchovers have taken place since the current Active CPU was initialized or if a Standby unit was forced to take over before the initial database sync was completed.
DAT cRfSupSysRunningConfigSyncTime	1.3.6.1.4.1.9.9.198.1.1.4	DateAndTime	read-only	The date and time when the running configuration was last successfully synced from the current Active unit to the Standby unit. This object will remain uninstantiated if no sync has yet taken place since the current Active CPU was initialized or if a Standby unit was forced to take over before the initial database sync was completed. Since automatic running configuration syncs are event driven and can be disabled by configuration, this time doesn't directly indicate whether Standby software reflects the running configuration of the Active unit. Instead, see the cRfSupSysRunningConfigOper object to determine whether Standby running configuration is in sync with the Active CPU.
RFS cRfSupSysRunningConfigAdmin	1.3.6.1.4.1.9.9.198.1.1.5	RfSupSyncAdminState	read-write	Enables/Disables automatic running configuration syncs only. Doesn't affect other types of sync activity. If set to the default value enableAutoSync, the Active unit will send the full current running configuration following any operation that changes the running configuration. Setting disableAutoSync may be useful for some maintenance and debugging operations.
RFS cRfSupSysRunningConfigOper	1.3.6.1.4.1.9.9.198.1.1.6	RfSupSyncOperState	read-only	The current operational state of running configuration syncs. When the value inSync is returned, it indicates that the Standby running configuration is being kept actively in sync with the Active unit.
DAT cRfSupSysStartupConfigSyncTime	1.3.6.1.4.1.9.9.198.1.1.7	DateAndTime	read-only	The date and time when the startup configuration was last successfully synced from the current Active unit to the Standby unit(s). This object will remain uninstantiated if no sync has yet taken place since the current Active CPU was initialized or if a Standby unit was forced to take over before the initial database sync was completed. For platforms where running configuration is always stored in a non-volatile manner, this object should be identical to cRfSupSysRunningConfigSyncTime. Since automatic startup configuration syncs are event driven and may be disabled by configuration, this time doesn't directly reflect whether Standby startup configuration is in sync with the Active unit. Instead, see the cRfSupSysStartupConfigOper object to determine whether Standby startup configuration is in sync with the Active unit.
RFS cRfSupSysStartupConfigAdmin	1.3.6.1.4.1.9.9.198.1.1.8	RfSupSyncAdminState	read-write	Enables/Disables automatic startup configuration syncs only. Doesn't affect other types of sync activity. If set to the default value enableAutoSync, the Active unit will send the full current startup configuration to the Standby unit(s) after any operation that changes the startup configuration in non-volatile memory. This object is not applicable to systems where running configuration is always stored in non-volatile memory. Setting disableAutoSync may be useful for some maintenance and debugging operations.
RFS cRfSupSysStartupConfigOper	1.3.6.1.4.1.9.9.198.1.1.9	RfSupSyncOperState	read-only	The current operational state of startup configuration syncs. When the value inSync is returned, it indicates that the Standby startup configuration is being kept actively in sync with the Active unit.
DAT cRfSupSysBootImageSyncTime	1.3.6.1.4.1.9.9.198.1.1.10	DateAndTime	read-only	The date and time when the boot image memory was last successfully synced from the current Active unit to the Standby unit(s). This object will remain uninstantiated if no sync has yet taken place since the current Active CPU was initialized or if a Standby unit was forced to take over before the initial database sync was completed. Since automatic boot image memory syncs are event driven and may be disabled by configuration, this time doesn't directly reflect whether Standby boot image memory is in sync with the Active unit. Instead, see the cRfSupSysBootImageOper object to determine whether Standby boot image memory is in sync with the Active unit.
RFS cRfSupSysBootImageAdmin	1.3.6.1.4.1.9.9.198.1.1.11	RfSupSyncAdminState	read-write	Enables/Disables automatic boot image memory syncs only. Doesn't affect other types of sync activity. If set to the default value enableAutoSync, the Active unit will send the full current boot image memory to the Standby unit(s) after any operation that affects the boot image. This object is not applicable for systems that don't support automatic boot image memory mirroring. Setting disableAutoSync is necessary during software upgrades for the case where the boot image memory space is too small to simultaneously hold both the old and new images.
RFS cRfSupSysBootImageOper	1.3.6.1.4.1.9.9.198.1.1.12	RfSupSyncOperState	read-only	The current operational state of boot image memory syncs. When the value inSync is returned, it indicates that Standby boot image memory is being actively mirrored from the Active unit.
STR cRfSupSysStandbyBootFile	1.3.6.1.4.1.9.9.198.1.1.13	SnmpAdminString	read-write	Allow Standby unit(s) to automatically load a boot image which differs from the image specified for the Active unit. The string should be of the form :. Specifying a null value indicates that Standby unit(s) should not use a different image than the Active unit. This is used during software upgrade/downgrade procedures, for platforms that support automatic syncs for boot image memory.
T/F cRfSupNotificationsEnabled	1.3.6.1.4.1.9.9.198.1.1.14	TruthValue	read-write	This specifies whether ciscoRfSupTimeChangeEvent, ciscoRfSupTimeZoneChangeEvent notifications shall be sent when the system's clock or time zone is changed causing a change in the values of cRfSupSysAvailableStartTime or cRfSupSysSwitchoverTime objects. Notifications will be sent only if this object is set to 'true'.
T/F cRfSupSysIfCounterSync	1.3.6.1.4.1.9.9.198.1.1.15	TruthValue	read-write	This object configures the synchronization of Interface Statistics information from Active CPU to the Standby CPU. When this object is set to 'true', synchronization is enabled. When this object is set to 'false', synchronization is disabled.
OCT cRfSupSysFailureReason	1.3.6.1.4.1.9.9.198.1.1.16	OCTET STRING	read-only	This object represents the reason code for a generic failure between Active and redundant unit. The generic failure can be a sync failure, upload and download issue. Failure reason is a texual description of the failure.
INT cRfSupSysSeverity	1.3.6.1.4.1.9.9.198.1.1.17	INTEGER	read-only	This object represents the severity for a generic failure between Active and redundant unit. The generic failure can be a sync failure, upload and download issue. critical - Critical severity alarm has to be raised for cRfSupSysErrorType major - Major failure that occured during sync/upload/download. minor - Minor failure that occured during sync/upload/download. Informational - warning during sync/upload/download. clear - Critical severity alarm to be cleared for the cRfSupSysErrorType.
INT cRfSupSysErrorType	1.3.6.1.4.1.9.9.198.1.1.18	INTEGER	read-only	This object represents the error type for a generic failure between Active and redundant unit. The generic failure can be a sync failure, upload and download issue. Notification will be sent if the object has a valid error type. A value of download-config indicates that, config download is failed. A value of download-code indicates that, code download is failed. A value of download-icon indicates that, icon download is failed. A value of download-image indicates that, image download is failed. A value of download-signature indicates that, signature download is failed. A value of download-webadmincert indicates that, webadmincert download is failed. A value of download-webauthcert indicates that, webauthcert download is failed. A value of download-webauthbundle indicates that, webauthbundle download is failed. A value of download-eapdevcert indicates that, eapdevcert download is failed. A value of download-eapcacert indicates that, eapcacert download is failed. A value of download-login-banner indicates that, login banner download is failed. A value of upload-config indicates that, config upload is failed. A value of upload-debug-file indicates that, debug file upload is failed. A value of upload-crashfile indicates that, crash file upload is failed. A value of upload-watchdog-crash-file indicates that, watchdog crash file upload is failed. A value of upload-panic-crash-file indicates that, panic crash file upload is failed. A value of upload-coredump indicates that, coredump upload is failed. A value of upload-errorlog indicates that, errorlog upload is failed. A value of upload-invalid-config indicates that, invalid config upload is failed. A value of upload-pac indicates that, pac upload is failed. A value of upload-radio-core-dump that, radio core dump upload is failed. A value of upload-ap-crash-data indicates that, ap crash data upload is failed. A value of upload-signature indicates that, signature upload is failed. A value of upload-systemtrace indicates that, system trace upload is failed. A value of upload-packet-capture indicates that, packet capture upload is failed. A value of upload-traplog indicates that, trap log upload is failed. A value of route-add indicates that, addition of route is failed. A value of route-del indicates that, deletion of route is failed. A value of interface-service-port indicates that, service port interface is failed. A value of reset indicates that, reset is failed. A value of other indicates that, other reason for failed. A value of config-sync-fail indicates that, config sync is failed. A value of peer-maintenance indicates that, maintenance of peer is failed. A value of peer-loss indicates that, peer connection losed. A value of rfTrapClearTemplist indicates that, rf trap clear temp list is failed.
cRfSupCpu	1.3.6.1.4.1.9.9.198.1.2
cRfSupCpuTable	1.3.6.1.4.1.9.9.198.1.2.1		not-accessible	A table containing redundancy-related information for individual CPU cards.
cRfSupCpuEntry	1.3.6.1.4.1.9.9.198.1.2.1.1		not-accessible	Information which can differ for each of the redundant CPU units in the system.
PHY cRfSupCpuUniqueIndex	1.3.6.1.4.1.9.9.198.1.2.1.1.1	PhysicalIndex	not-accessible	A table index which always has a unique platform-assigned value for each physical redundant unit within a particular system. This index should refer to a particular physical unit rather than a logically Active or Standby unit.
INT cRfSupCpuActiveSeverity	1.3.6.1.4.1.9.9.198.1.2.1.1.2	INTEGER	read-only	The fault severity of a redundant unit, as calculated by software. The value zero represents a good unit with no detected faults. Higher values represent progressively more serious faults. If it's not possible to determine any current or prior severity information about a unit, the value unknown should be returned. Unlike some severity definitions, cRfSupCpuActiveSeverity should not be downgraded when it switches from being Active. The severity for a faulty Standby unit should correspond to the system impact it would have if it were made to be the Active unit, assuming the severity can be determined while Standby. The severity can be affected by either hardware or software faults with the CPU itself. It can also be affected by faults which prevent this CPU from interacting with one or more other system components (such as linecards), even when the actual faulty Field Replaceable Unit (FRU) is not the CPU itself. As a minimum, the nonFaulty and fullyTrafficAffectingFault values should be supported on any platform supporting this object. Support of the other severity values is preferred, but optional.
DAT cRfSupCpuInitTime	1.3.6.1.4.1.9.9.198.1.2.1.1.3	DateAndTime	read-only	The date and time when this redundant unit was last initialized. If the unit started out in the Standby state, this will also include the time while running as Standby.
cRfSupAction	1.3.6.1.4.1.9.9.198.1.3
INT cRfSupActionManualSync	1.3.6.1.4.1.9.9.198.1.3.1	INTEGER	read-write	This variable is set to invoke a one-time manual copy of the specified information type from the Active to one or more Standby units. When read, this object returns the last command written or noAction if no action has been written to the Active unit since it was initialized. The value noAction can not be used in a write request. The result of the last requested action can be determined by reading the value of cRfSupActionLastSyncResult. The value of the cRfSupActionManualSync object can not be changed until the cRfSupActionLastSyncResult transitions to the successful or failed state.
CON cRfSupActionLastSyncResult	1.3.6.1.4.1.9.9.198.1.3.2	ConfigCopyState	read-only	Contains the result of the last Manual Sync action request. This object is instantiated only after the cRfSupActionManualSync object has been set to a value other than noAction.
ciscoRfSupMibConformance	1.3.6.1.4.1.9.9.198.2
ciscoRfSupMibCompliances	1.3.6.1.4.1.9.9.198.2.1
ciscoRfSupMibCompliance	1.3.6.1.4.1.9.9.198.2.1.1			The compliance statement for entities which implement the Cisco RF SUPPLEMENTAL MIB. Note: Platforms which implement the Cisco RF MIB are not required to support the RF SUPPLEMENTAL MIB.
ciscoRfSupMibComplianceRev1	1.3.6.1.4.1.9.9.198.2.1.2			The compliance statement for entities which implement the Cisco RF SUPPLEMENTAL MIB. Note: Platforms which implement the Cisco RF MIB are not required to support the RF SUPPLEMENTAL MIB.
ciscoRfSupMibComplianceRev2	1.3.6.1.4.1.9.9.198.2.1.3			The compliance statement for entities which implement the Cisco RF SUPPLEMENTAL MIB. Note: Platforms which implement the Cisco RF MIB are not required to support the RF SUPPLEMENTAL MIB.
ciscoRfSupMibComplianceRev3	1.3.6.1.4.1.9.9.198.2.1.4			The compliance statement for entities which implement the Cisco RF SUPPLEMENTAL MIB. Note: Platforms which implement the Cisco RF MIB are not required to support the RF SUPPLEMENTAL MIB.
ciscoRfSupMibGroups	1.3.6.1.4.1.9.9.198.2.2
ciscoRfSupSysGroup	1.3.6.1.4.1.9.9.198.2.2.1			The collection of RF SUPPLEMENTAL system-wide objects.
ciscoRfSupCpuGroup	1.3.6.1.4.1.9.9.198.2.2.2			The collection of RF SUPPLEMENTAL per-CPU objects.
ciscoRfSupActionGroup	1.3.6.1.4.1.9.9.198.2.2.3			The collection of RF SUPPLEMENTAL execution actions.
ciscoRfSupSysOptionalGroup	1.3.6.1.4.1.9.9.198.2.2.4			The collection of optional RF SUPPLEMENTAL system-wide objects.
ciscoRfSupNotifGroup	1.3.6.1.4.1.9.9.198.2.2.5			The collection of optional notifications issued on system time/time zone modifications. ciscoRfSupNotifGroup object is superseded by ciscoRfSupNotifGroupRev1.
ciscoRfSupSysOptionalSyncGroup	1.3.6.1.4.1.9.9.198.2.2.6			The collection of optional RF SUPPLEMENTAL system wide objects that control and monitor the synchronization of information between the redundant system units.
ciscoRfSupNotifGroupRev1	1.3.6.1.4.1.9.9.198.2.2.7			The collection of optional notifications issued on system time/time zone modifications.

RFC description

Supplements CISCO-RF-MIB with additional status and configuration control for redundant CPU platforms.

Start monitoring Cisco router/Catalyst switch with redundant supervisors/RP 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-SUPPLEMENTAL-MIB