| RFState |
|
| The 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' |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
notKnown(1), disabled(2), initialization(3), negotiation(4), standbyCold(5), standbyColdConfig(6), standbyColdFileSys(7), standbyColdBulk(8), standbyHot(9), activeFast(10), activeDrain(11), activePreconfig(12), activePostconfig(13), active(14), activeExtraload(15), activeHandback(16) |
|
| RFIssuState |
|
| ISSU 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. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
unset(0), init(1), loadVersion(2), runVersion(3), commitVersion(4) |
|
| RFIssuStateRev1 |
|
| ISSU 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. |
| TEXTUAL-CONVENTION |
|
|
|
| |
INTEGER |
init(0), systemReset(1), loadVersion(3), loadVersionSwitchover(4), runVersion(6), runVersionSwitchover(7), commitVersion(9) |
|
| CRFStatusRFModeCapsEntry |
|
| SEQUENCE |
|
|
|
| |
cRFStatusRFModeCapsMode |
RFMode |
|
| |
cRFStatusRFModeCapsModeDescr |
SnmpAdminString |
|
| CRFHistorySwitchOverEntry |
|
| SEQUENCE |
|
|
|
| |
cRFHistorySwitchOverIndex |
Unsigned32 |
|
| |
cRFHistoryPrevActiveUnitId |
RFUnitIdentifier |
|
| |
cRFHistoryCurrActiveUnitId |
RFUnitIdentifier |
|
| |
cRFHistorySwitchOverReason |
RFSwactReasonType |
|
| |
cRFHistorySwactTime |
DateAndTime |
|
| cRFStatusPeerStandByEntryTime |
1.3.6.1.4.1.9.9.176.1.1.10 |
| The value of sysUpTime when the peer redundant unit entered the
standbyHot state. The value will be 0 on system initialization. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TimeStamp |
|
|
| cRFStatusRFModeCapsEntry |
1.3.6.1.4.1.9.9.176.1.1.11.1 |
| An entry containing the device implementation specific
terminology associated with the redundancy mode that can be
supported on the device. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
CRFStatusRFModeCapsEntry |
|
|
| cRFStatusRFClientEntry |
1.3.6.1.4.1.9.9.176.1.4.1.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
CRFStatusRFClientEntry |
|
|
| cRFCfgMaintenanceMode |
1.3.6.1.4.1.9.9.176.1.2.13 |
| 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. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
TruthValue |
|
|
| cRFHistoryTableMaxLength |
1.3.6.1.4.1.9.9.176.1.3.1 |
| Maximum number of entries permissible in the history
table. A value of 0 will result in no history being
maintained. |
| Status: current |
Access: read-write |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
0..50 |
|
| cRFHistorySwitchOverTable |
1.3.6.1.4.1.9.9.176.1.3.2 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
SEQUENCE OF |
|
|
| |
|
CRFHistorySwitchOverEntry |
|
| cRFHistorySwitchOverEntry |
1.3.6.1.4.1.9.9.176.1.3.2.1 |
| 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. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
CRFHistorySwitchOverEntry |
|
|
| cRFHistorySwitchOverIndex |
1.3.6.1.4.1.9.9.176.1.3.2.1.1 |
| A monotonically increasing integer for the purpose of
indexing history table. After reaching maximum value,
it wraps around to 1. |
| Status: current |
Access: not-accessible |
| OBJECT-TYPE |
|
|
|
| |
Unsigned32 |
1..4294967295 |
|
| cRFHistoryPrevActiveUnitId |
1.3.6.1.4.1.9.9.176.1.3.2.1.2 |
| Indicates the primary redundant unit that went down. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
RFUnitIdentifier |
|
|
| cRFHistoryCurrActiveUnitId |
1.3.6.1.4.1.9.9.176.1.3.2.1.3 |
| Indicates the secondary redundant unit that took
over as active. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
RFUnitIdentifier |
|
|
| cRFHistorySwitchOverReason |
1.3.6.1.4.1.9.9.176.1.3.2.1.4 |
| Indicates the reason for the switchover. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
RFSwactReasonType |
|
|
| cRFHistorySwactTime |
1.3.6.1.4.1.9.9.176.1.3.2.1.5 |
| Indicates the Date & Time when switchover occurred. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
DateAndTime |
|
|
| cRFHistoryColdStarts |
1.3.6.1.4.1.9.9.176.1.3.3 |
| 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. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
Counter32 |
|
|
| cRFHistoryStandByAvailTime |
1.3.6.1.4.1.9.9.176.1.3.4 |
| Indicates the cumulative time that a standby redundant
unit has been available since last system initialization. |
| Status: current |
Access: read-only |
| OBJECT-TYPE |
|
|
|
| |
TimeInterval |
|
|
| ciscoRFHistoryGroup |
1.3.6.1.4.1.9.9.176.3.2.6 |
| The collection of RF History objects. |
| Status: current |
Access: read-only |
| OBJECT-GROUP |
|
|
|
