CISCO-RF-SUPPLEMENTAL-MIB: View SNMP OID List / Download MIB

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.

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.

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'.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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'.

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.

A table containing redundancy-related information for individual CPU cards.

Information which can differ for each of the redundant CPU units in the system.

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.

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. Enumeration: 'unknown': 4, 'partialTrafficAffectingFault': 2, 'nonFaulty': 0, 'fullyTrafficAffectingFault': 3, 'nonTrafficAffectingFault': 1.

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.

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. Enumeration: 'runningConfig': 2, 'startupConfig': 3, 'bootImage': 4, 'noAction': 1.

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.

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.

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.

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.

The collection of RF SUPPLEMENTAL system-wide objects.

The collection of RF SUPPLEMENTAL per-CPU objects.

The collection of RF SUPPLEMENTAL execution actions.

The collection of optional RF SUPPLEMENTAL system-wide objects.

The collection of optional notifications issued on system time/time zone modifications.

The collection of optional RF SUPPLEMENTAL system wide objects that control and monitor the synchronization of information between the redundant system units.