CISCO-RF-MIB

RFUnitIdentifierA unique identifier for Active/Standby unit. (0..2147483647) · Integer32

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.

RFState1 = notKnown2 = disabled3 = initialization4 = negotiation5 = standbyCold6 = standbyColdConfig7 = standbyColdFileSys8 = standbyColdBulk9 = standbyHot10 = activeFast11 = activeDrain12 = activePreconfig13 = activePostconfig14 = active15 = activeExtraload16 = activeHandbackThe current state of the RF subsystem. notKnown - state is unknown disabled - RF is not operational on this unit initialization - establish necessary system services negotiation - peer unit discovery and negotiation standbyCold - client notification on standby unit *standbyColdConfig - standby configuration is updated from active configuration *standbyColdFileSys - standby file system (FS) is updated from the active FS *standbyColdBulk - clients sync data from active to standby standbyHot - incremental client data sync continues. This unit is ready to take over activity. activeFast - call maintenance efforts during a SWACT activeDrain - client clean-up phase activePreconfig - unit is active but has not read its configuration activePostconfig - unit is active and is post-processing its configuration active - unit is active and processing calls activeExtraload - unit is active and processing calls for all feature boards in the system activeHandback - unit is active, processing calls and is in the process of handing some resources to the other unit in the system * Sub-state of 'standbyCold' · Integer32

The current state of RF on this unit.

RFUnitIdentifierA unique identifier for Active/Standby unit. (0..2147483647) · Integer32

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.

RFState1 = notKnown2 = disabled3 = initialization4 = negotiation5 = standbyCold6 = standbyColdConfig7 = standbyColdFileSys8 = standbyColdBulk9 = standbyHot10 = activeFast11 = activeDrain12 = activePreconfig13 = activePostconfig14 = active15 = activeExtraload16 = activeHandbackThe current state of the RF subsystem. notKnown - state is unknown disabled - RF is not operational on this unit initialization - establish necessary system services negotiation - peer unit discovery and negotiation standbyCold - client notification on standby unit *standbyColdConfig - standby configuration is updated from active configuration *standbyColdFileSys - standby file system (FS) is updated from the active FS *standbyColdBulk - clients sync data from active to standby standbyHot - incremental client data sync continues. This unit is ready to take over activity. activeFast - call maintenance efforts during a SWACT activeDrain - client clean-up phase activePreconfig - unit is active but has not read its configuration activePostconfig - unit is active and is post-processing its configuration active - unit is active and processing calls activeExtraload - unit is active and processing calls for all feature boards in the system activeHandback - unit is active, processing calls and is in the process of handing some resources to the other unit in the system * Sub-state of 'standbyCold' · Integer32

The current state of RF on the peer unit.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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.

RFSwactReasonType1 = unsupported2 = none3 = notKnown4 = userInitiated5 = userForced6 = activeUnitFailed7 = activeUnitRemoved8 = activeGWdown9 = activeRMIportdownReason codes for the switch of activity from an active redundant unit to its standby peer unit. unsupported - the 'reason code' is an unsupported feature none - no SWACT has occurred notKnown - reason is unknown userInitiated - a safe, manual SWACT was initiated by user userForced - a manual SWACT was forced by user; ignoring pre-conditions, warnings and safety checks activeUnitFailed - active unit failure caused an auto SWACT activeUnitRemoved - active unit removal caused an auto SWACT activeGWdown - SWACT due to active losing gateway connectivity activeRMIportdown - SWACT due to RMI port going down on active · Integer32

The reason for the last switch of activity.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

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.

TimeStampThe value of the sysUpTime object at which a specific occurrence happened. The specific occurrence must be defined in the description of any object defined using this type. If sysUpTime is reset to zero as a result of a re- initialization of the network management (sub)system, then the values of all TimeStamp objects are also reset. However, after approximately 497 days without a re- initialization, the sysUpTime object will reach 2^^32-1 and then increment around to zero; in this case, existing values of TimeStamp objects do not change. This can lead to ambiguities in the value of TimeStamp objects. · TimeTicks

The value of sysUpTime when the peer redundant unit entered the standbyHot state. The value will be 0 on system initialization.

RFIssuState0 = unset1 = init2 = loadVersion3 = runVersion4 = commitVersionISSU state represents the current system state. unset - unset state; if the system is booted from tftp or from ROMMON such that the image is not the first in BOOT init - init state; the first ISSU state that the system will move to after the unset state, when the ISSU process has just been kicked off. The first CLI that is executed to make this happen is the loadversion CLI. loadVersion - Once the loadversion CLI has been executed, the state of the system is changed to reflect this, and this state is called the loadVersion state. The boot variable on the Standby is updated to point to the new image that the Standby needs to load and then it is reset. runVersion - runVersion state; When the system is in the loadversion state, the Active is running the old image and the Standby is running the new image. When the runversion CLI is executed, a switchover occurs, and the Standby running the new image takes over as the Active. The state of the system at this stage is updated to runversion. commitVersion - in the runversion state, the Active is running the new image, and the Standby is running the old image. When the user is satisfied with the functioning of the system, they execute the commitversion CLI, which will prepend the boot variable on the Standby with the new image, and then the Standby is reset. After this, the Standby comes up with the new image, and the state of the system is updated to reflect the commitVersion state. · Integer32

The current ISSU state of the system.

RFIssuStateRev10 = init1 = systemReset3 = loadVersion4 = loadVersionSwitchover6 = runVersion7 = runVersionSwitchover9 = commitVersionISSU state represents the current system state. init - This state represents the initial state of the system. The ISSU process is not running at this stage. The only CLI for ISSU process that can be executed in this state is the loadversion CLI. systemReset - If a system reset occurs, or the abortversion CLI is executed, the state of the system is pushed to this state. loadVersion - When the Standby signs in after the loadversion CLI is executed, the state of the system is changed to loadVersion. loadVersionSwitchover - If a switchover occurs in the loadVersion state, by the user, or because the Active crashes, the new state of the system will be loadVersionSwitchover. It is analogous to the runVersion state, except that the runversion CLI was not executed. runVersion - When the Standby signs in after executing the runversion CLI, the state of the system is changed to runVersion. runVersionSwitchover - if a switchover occurs while the system is in the runVersion state, the new state will be called runVersionSwitchover. It is analogous to the loadVersion state. commitVersion - When the Standby signs in after the commitversion CLI is executed, the state of the system is changed to commitVersion. · Integer32

The current ISSU state of the system.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

The IOS version from with the user is upgrading

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

The IOS version to with the user is upgrading

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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.

Unsigned32

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.

Unsigned32

The minimum acceptable value for the cRFCfgKeepaliveThresh object.

Unsigned32

The maximum acceptable value for the cRFCfgKeepaliveThresh object.

Unsigned32 · milliseconds

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.

Unsigned32 · milliseconds

The minimum acceptable value for the cRFCfgKeepaliveTimer object.

Unsigned32 · milliseconds

The maximum acceptable value for the cRFCfgKeepaliveTimer object.

Unsigned32 · milliseconds

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.

Unsigned32 · milliseconds

The minimum acceptable value for the cRFCfgNotifTimer object.

Unsigned32 · milliseconds

The maximum acceptable value for the cRFCfgNotifTimer object.

RFAction0 = noAction1 = reloadPeer2 = reloadShelf3 = switchActivity4 = forceSwitchActivityAdministrative commands to invoke in the RF subsystem. noAction - no action (do nothing) reloadPeer - reset the redundant peer unit reloadShelf - reset the entire shelf switchActivity - safely SWACT to peer unit and go standby forceSwitchActivity - switch activity; ignoring pre-conditions, system warnings and safety checks. When the value is set to 'noAction' no operation is performed. When read, the value 'noAction' is always returned. · Integer32

This variable is set to invoke RF subsystem action commands. The commands are useful for maintenance and software upgrade activities.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

Allows enabling/disabling of RF subsystem notifications.

TruthValue1 = true2 = falseRepresents a boolean value. · Integer32

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.

RFMode1 = nonRedundant2 = staticLoadShareNonRedundant3 = dynamicLoadShareNonRedundant4 = staticLoadShareRedundant5 = dynamicLoadShareRedundant6 = coldStandbyRedundant7 = warmStandbyRedundant8 = hotStandbyRedundantThe characterization of the redundancy subsystem. nonRedundant - the system is not redundant. staticLoadShareNonRedundant - the system is *not* redundant but is load sharing. The load sharing is *not* based on operational load (i.e. number of calls, etc). dynamicLoadShareNonRedundant - the system is *not* redundant but is load sharing. Load sharing is based on operational load. staticLoadShareRedundant - the system is redundant and is load sharing. The load sharing is *not* based on operational load. dynamicLoadShareRedundant - the system is redundant and is load sharing. Load sharing is based on operational load. coldStandbyRedundant - the system is redundant but the redundant peer unit is not fully initialized and is not able to retain established calls. warmStandbyRedundant - the system is redundant and the redundant peer unit is immediately able to handle new calls. The redundant unit is unable to retain established calls. hotStandbyRedundant - the system is redundant and the redundant peer unit is able to 'instantaneously' retain established calls and immediately able to handle new calls. · Integer32

Indicates the redundancy mode configured on the device.

SnmpAdminStringAn octet string containing administrative information, preferably in human-readable form. To facilitate internationalization, this information is represented using the ISO/IEC IS 10646-1 character set, encoded as an octet string using the UTF-8 transformation format described in [RFC2279]. Since additional code points are added by amendments to the 10646 standard from time to time, implementations must be prepared to encounter any code point from 0x00000000 to 0x7fffffff. Byte sequences that do not correspond to the valid UTF-8 encoding of a code point or are outside this range are prohibited. The use of control codes should be avoided. When it is necessary to represent a newline, the control code sequence CR LF should be used. The use of leading or trailing white space should be avoided. For code points not directly supported by user interface hardware or software, an alternative means of entry and display, such as hexadecimal, may be provided. For information encoded in 7-bit US-ASCII, the UTF-8 encoding is identical to the US-ASCII encoding. UTF-8 may require multiple bytes to represent a single character / code point; thus the length of this object in octets may be different from the number of characters encoded. Similarly, size constraints refer to the number of encoded octets, not the number of characters represented by an encoding. Note that when this TC is used for an object that is used or envisioned to be used as an index, then a SIZE restriction MUST be specified so that the number of sub-identifiers for any object instance does not exceed the limit of 128, as defined by [RFC3416]. Note that the size of an SnmpAdminString object is measured in octets, not characters. SIZE (0..255) · OCTET STRING · hint 255t

Further clarifies or describes the redundancy mode indicated by cRFCfgRedundancyMode. Implementation-specific terminology associated with the current redundancy mode may be presented here.

RFMode1 = nonRedundant2 = staticLoadShareNonRedundant3 = dynamicLoadShareNonRedundant4 = staticLoadShareRedundant5 = dynamicLoadShareRedundant6 = coldStandbyRedundant7 = warmStandbyRedundant8 = hotStandbyRedundantThe characterization of the redundancy subsystem. nonRedundant - the system is not redundant. staticLoadShareNonRedundant - the system is *not* redundant but is load sharing. The load sharing is *not* based on operational load (i.e. number of calls, etc). dynamicLoadShareNonRedundant - the system is *not* redundant but is load sharing. Load sharing is based on operational load. staticLoadShareRedundant - the system is redundant and is load sharing. The load sharing is *not* based on operational load. dynamicLoadShareRedundant - the system is redundant and is load sharing. Load sharing is based on operational load. coldStandbyRedundant - the system is redundant but the redundant peer unit is not fully initialized and is not able to retain established calls. warmStandbyRedundant - the system is redundant and the redundant peer unit is immediately able to handle new calls. The redundant unit is unable to retain established calls. hotStandbyRedundant - the system is redundant and the redundant peer unit is able to 'instantaneously' retain established calls and immediately able to handle new calls. · Integer32

Indicate the operational redundancy mode of the device.

Unsigned32 (0..50)

Maximum number of entries permissible in the history table. A value of 0 will result in no history being maintained.

Counter32

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.

TimeIntervalA period of time, measured in units of 0.01 seconds. (0..2147483647) · Integer32

Indicates the cumulative time that a standby redundant unit has been available since last system initialization.

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.

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

An ISSU notification to indicate the new state of the system.

An ISSU notification to indicate the new state of the system.