SNMP MIB Search

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.

The current state of RF on this unit.

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.

The current state of RF on the peer unit.

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

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.

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.

The reason for the last switch of activity.

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.

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

An entry containing the device implementation specific
terminology associated with the redundancy mode that can be
supported on the device.

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.

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.

The minimum acceptable value for the cRFCfgKeepaliveThresh
object.

The maximum acceptable value for the cRFCfgKeepaliveThresh
object.

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.

The minimum acceptable value for the cRFCfgKeepaliveTimer
object.

The maximum acceptable value for the cRFCfgKeepaliveTimer
object.

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.

The minimum acceptable value for the cRFCfgNotifTimer
object.

The maximum acceptable value for the cRFCfgNotifTimer
object.

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

Allows enabling/disabling of RF subsystem notifications.

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.

Indicates the redundancy mode configured on the device.

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

Indicate the operational redundancy mode of the device.

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

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.

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.

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

The redundancy mode that can be supported on the device.

The description of the device implementation specific
terminology associated with its supported redundancy mode.

A monotonically increasing integer for the purpose of
indexing history table. After reaching maximum value,
it wraps around to 1.

Indicates the primary redundant unit that went down.

Indicates the secondary redundant unit that took
over as active.

Indicates the reason for the switchover.

Indicates the Date & Time when switchover occured.

This table containing a list of redundancy modes that can be
supported on the device.

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.

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:
standbyCold
standbyHot
active
activeExtraload

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.

The collection of global RF status objects.

The collection of RF configuration objects.

The collection of notifications used to indicate RF state
information.

The collection of RF configuration objects.

The collection of global RF status objects.

The collection of RF History objects.

An optional group with a collection of objects providing
the information of the operational redundancy mode on the
device.

An optional group with a collection of objects
providing the information of redundancy mode capability
on the device.