CISCO-L4L7MODULE-REDUNDANCY-MIB
AI MIB Summary
The CISCO-L4L7MODULE-REDUNDANCY-MIB monitors and manages High Availability (HA) and Fault Tolerance (FT) configurations for Cisco Catalyst L4-7 Server Load Balancers, specifically tracking redundancy group states, Heartbeat (HB) status, and failover statistics across active and standby devices.
The L4-7 SLB devices are used for scaling websites, building web enabled applications, and migrating to web services. The following services ( but not limited to ) can be provided by L4-7 slb devices: SLB ( Server Load Balancing ) FW ( Firewall ) SSL ( Secure Socket Layer ) IDS ( Intrusion Detection System ) .
This MIB provides the tables/objects that support redundancy configuration and redundancy statistics.
The redundancy model supported by this MIB allows two or more SLB devices to be configured with one or more redundancy group. Each redundancy group is identified by a unique group ID. Two or more devices are redundant to each other if they use the same redundancy Group ID.
Acronyms and terms: HB Heart Beat FT Fault Tolerant HA High Availability VLAN Virtual Local Area Network LB Load Balance
Main OID:
ciscoL4L7moduleRedundancyMIB.1.3.6.1.4.1.9.9.650
64
Objects
Active
Status
7
Dependencies
Imported Objects
Objects
64 total| Object Name |
|---|
ciscoL4L7moduleRedundancyMIBThe L4-7 SLB devices are used
for scaling websites, building web
enabled applications, and migrating
to web services. The following services
( but not limited to ) can be provided by
L4-7 slb devices:
SLB ( Server Load Balancing )
FW ( Firewall )
SSL ( Secure Socket Layer )
IDS ( Intrusion Detection System ) .
This MIB provides the tables/objects that
support redundancy configuration and
redundancy statistics.
The redundancy model supported by this MIB
allows two or more SLB devices to be
configured with one or more redundancy
group. Each redundancy group is identified by
a unique group ID. Two or more devices are
redundant to each other if they use the
same redundancy Group ID.
Acronyms and terms:
HB Heart Beat
FT Fault Tolerant
HA High Availability
VLAN Virtual Local Area Network
LB Load Balance MODULE-IDENTITY .1.3.6.1.4.1.9.9.650 |
ciscoLmRedundancyMIBNotifs OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.650.0 |
clrRedundancyStateChangeThe notification generated when the redundancy state
is changed. NOTIFICATION-TYPE .1.3.6.1.4.1.9.9.650.0.1 |
ciscoLmRedundancyMIBObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.650.1 |
clrConfig OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.650.1.1 |
clrPeerConfigTableThis table is for configuring peer groups that are
part of redundancy configuration. The peer configuration
specifies the information used for exchanging High
Availability information related to redundancy groups. SEQUENCE OF ClrPeerConfigEntry .1.3.6.1.4.1.9.9.650.1.1.1 |
clrPeerConfigEntryAn entry in clrPeerConfigTable. Each entry contains information
about peer interface, query interface, heart beat
count and heart beat time. ClrPeerConfigEntry .1.3.6.1.4.1.9.9.650.1.1.1.1 |
clrPeerIdThis object identifies unique id for the peer.
The peer is used in redundancy configuration. Unsigned32 (1..65535 ) .1.3.6.1.4.1.9.9.650.1.1.1.1.1 |
clrPeerInterfaceThis object specifies the interface used by the
peers to exchange High Availability ( HA ) protocol
information.rw InterfaceIndex (IF-MIB) .1.3.6.1.4.1.9.9.650.1.1.1.1.2 |
clrPeerBackupInterfaceThis object specifies the backup interface used by the
peer. The backup interface is used in case the heart beat
message is not received. This interface is used to
send the heart beat message. If the message sent is not
successful, then it is assumed peer is down and switchover
will be initiated. If the message sent is successful
on this interface, the peer transitions to standbyCold
and continue to monitor peer.rw InterfaceIndexOrZero (IF-MIB) .1.3.6.1.4.1.9.9.650.1.1.1.1.3 |
clrPeerHeartBeatTimeThe time interval between heartbeat/keep-alive
messages exchanged between the peers.rw Unsigned32 UNITS "milliseconds" .1.3.6.1.4.1.9.9.650.1.1.1.1.4 |
clrPeerHeartBeatCountThis object is used in conjunction with
'clrPeerHeartBeatTime' to switch over the active
redundancy unit or not. Switch over occurs if
heartbeats are not received from the peer
during a specific time period, which
is equal to ( clrPeerHeartBeatTime *
clrPeerHeartBeatCount ) .rw Unsigned32 .1.3.6.1.4.1.9.9.650.1.1.1.1.5 |
clrPeerStorageTypeThe storage type for this conceptual row.rw StorageType (SNMPv2-TC) .1.3.6.1.4.1.9.9.650.1.1.1.1.6 |
clrPeerRowStatusThis object is used for adding/deleting
entries from the table.
An entry MUST NOT exist in the active state unless all
objects in the entry have an appropriate value, as described
in the description clause for each writable object.
This object may be modified if the associated
instance of this object is equal to active(1),
notInService(2), or notReady(3). All other writable objects
may be modified if the associated instance of this object is
equal to notInService(2) or notReady(3).rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.650.1.1.1.1.7 |
clrPeerInfoTableThis table contains information of the redundancy peer. SEQUENCE OF ClrPeerInfoEntry .1.3.6.1.4.1.9.9.650.1.1.2 |
clrPeerInfoEntryAn entry in peer information table. An entry will get created
whenever an entry is created in clrPeerConfigTable. Each entry
contains information such as peer state, peer ip address,
software and license compatibility. The entPhysicalIndex
specifies an entry in entPhysicalTable with entPhysicalClass
representing the value of 'module'. ClrPeerInfoEntry .1.3.6.1.4.1.9.9.650.1.1.2.1 |
clrPeerOperStatusThis object identifies the current status of the peer. The
possible values are
init(1) : The initial state of the peer.
localIPaddr(2) : The local device IP address is missing.
Waiting for the local IP address
to be configured.
peerIPAddr(3) : The peer IP address is missing. Waiting
for the peer IP address to be configured.
startHB(4) : The peer configuration is complete.
Starting the heartbeat to see if there
is a peer device.
tcpSetUp(5) : The heartbeat has detected the presence
of the peer device. Redundancy is in
the process of establishing a TCP
connection to the peer.
srgCheck(6) : Checking for software version
compatibility with the peer device.
licCheck(7) : Checking for license compatibility with
the peer device.
compatible(8) : Version and license checks indicate that
the peer is compatible for redundancy.
peerInterfaceDown(9): The peer interface ( used for transmitting
and receiving HB messages ) is down,
but, through the query interface,
the local device has determined that
the peer is still alive.
down(10) : The peer device is down.
error(11) : Indicates that an error has occurred
with the peer. Possible errors are:
version mismatch, license mismatch,
or failure to establish a TCP connection
to the peer. A syslog message appears
with more detailed information.ro Enumeration .1.3.6.1.4.1.9.9.650.1.1.2.1.1 |
clrPeerIpAddressTypeThe type of internet address by which the
peer is reachable.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.650.1.1.2.1.2 |
clrPeerIpAddressThis Internet address for the redundant peer.
The type of this address is determined by the
value of the clrPeerIpAddressType object.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.650.1.1.2.1.3 |
clrPeerSoftwareCompatibiltyIndicates whether the software version of the local device
and the software version of the peer are compatible. The
possible values are:
init(1) : initialization state.
compatible(2) : software version of the local and peer
device are compatible.
inCompatible(3) : software version of the local and peer
device are not compatible.
warmCompatible(4) : When the software version check of the
local and the peer device returns
'supersedes' or 'superseded_by'
then the clrPeerSoftwarecompatibility of
the peer device is set to 'warmCompatible'.ro Enumeration .1.3.6.1.4.1.9.9.650.1.1.2.1.4 |
clrPeerLicenseCompatibilityIndicates whether the license of the local device and the
license of the peer device are compatible. The possible
values are:
init(1) : initialization state.
compatible(2) : license version of the local and peer
device are compatible.
inCompatible(3) : license version of the local and peer
device are not compatible.ro Enumeration .1.3.6.1.4.1.9.9.650.1.1.2.1.5 |
clrPeerRedGroupsThis object refers to the number of redundancy groups the peer
is associated with.ro Unsigned32 .1.3.6.1.4.1.9.9.650.1.1.2.1.6 |
clrRedundancyConfigTableThis table is used for configuring
redundancy groups. The redundancy group
is configured by specifying the same
value of 'clrRedGroupId' in multiple devices. SEQUENCE OF ClrRedundancyConfigEntry .1.3.6.1.4.1.9.9.650.1.1.3 |
clrRedundancyConfigEntryAn entry in redundancy table.
Each entry contains information such
as priority, preempt. Preemption
ensures that the group member with high priority
always becomes active. The entPhysicalIndex
specifies the entry in entPhysicalTable with
entPhysicalClass representing the value of 'module'. ClrRedundancyConfigEntry .1.3.6.1.4.1.9.9.650.1.1.3.1 |
clrRedGroupIdThis object specifies the redundancy group
identifier. This is the unique id of the
redundancy group. Unsigned32 (1..4096 ) .1.3.6.1.4.1.9.9.650.1.1.3.1.1 |
clrRedPeerIdThe peer ID to which this group belongs.
There must be an entry in clrPeerConfigTable
with this value. This object cannot be modified
if the associated clrRedRowStatus object is equal
to 'active'.rw Unsigned32 (1..65535 ) .1.3.6.1.4.1.9.9.650.1.1.3.1.2 |
clrRedPriorityThe priority value of the redundancy group.
This value is used in selecting the active
and standby peer.
The devices that belong to the same
redundancy group must be configured with a different
priority. The redundancy group with a highest
priority will become active unit during
negotiation phase of the redundancy.
If two (or more) devices in a group have
the same priority, the one with the highest IP address
of the interface is the active device.
If a redundancy group with high priority
value is online after its peer has become
active, then the group with high priority
will become standby. This behavior can be
changed by setting clrRedPreempt object to
'true'.rw Unsigned32 (1..255 ) .1.3.6.1.4.1.9.9.650.1.1.3.1.3 |
clrRedPreemptThis specifies whether a high priority
redundancy device can become active irrespective
of the time at which it is online.
The value 'true' specifies that the redundancy
group with higher priority will always become active.
The value 'false' specifies that the redundacy
device which becomes active will remain active
even if another redundancy device comes online
with higher priority.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.650.1.1.3.1.4 |
clrRedFailOverTimeThe time to wait before standby redundancy
group become active. This represents the amount
of time a module need to wait after the last
keep-alive message is received before assuming
the peer is not operating.rw Unsigned32 .1.3.6.1.4.1.9.9.650.1.1.3.1.5 |
clrRedStateThe current redundancy state.ro CiscoL4L7RedState .1.3.6.1.4.1.9.9.650.1.1.3.1.6 |
clrRedStateChangeTimeThe time of the last change in the current
redundancy state.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.650.1.1.3.1.7 |
clrRedContextThis object refers to the context name to which the redundant
group is associated with. The context refers to the logical
partitioning within a device. The context can be identified
by a unique name in a device.rw OCTET STRING .1.3.6.1.4.1.9.9.650.1.1.3.1.8 |
clrRedStorageTypeThe storage type for this conceptual row.rw StorageType (SNMPv2-TC) .1.3.6.1.4.1.9.9.650.1.1.3.1.9 |
clrRedRowStatusThis object is used for adding/deleting
entries from the table.
An entry MUST NOT exist in the active state unless all
objects in the entry have an appropriate value, as described
in the description clause for each writable object.
This object may be modified if the associated
instance of this object is equal to active(1),
notInService(2), or notReady(3). All other writable objects
may be modified if the associated instance of this object is
equal to notInService(2) or notReady(3).rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.9.9.650.1.1.3.1.10 |
clrRedundancyInfoTableThis table contains information on the
devices that are part of redundancy group. SEQUENCE OF ClrRedundancyInfoEntry .1.3.6.1.4.1.9.9.650.1.1.4 |
clrRedundancyInfoEntryAn entry in redundancy information table.
An entry will get created whenever an
entry is created in clrRedundancyConfigTable.
Each entry contains information such
as priority, state and last time
when the redundancy state got changed.
The entPhysicalIndex specifies an entry in
entPhysicalTable with entPhysicalClass representing
the value of 'module'. ClrRedundancyInfoEntry .1.3.6.1.4.1.9.9.650.1.1.4.1 |
clrRedundancyPriorityThe priority value of this redundancy
entry. This value is same as the
value configured in 'clrRedPriority'
for a redundancy group.ro Unsigned32 (1..255 ) .1.3.6.1.4.1.9.9.650.1.1.4.1.1 |
clrRedundancyStateThe current redundancy state.ro CiscoL4L7RedState .1.3.6.1.4.1.9.9.650.1.1.4.1.2 |
clrRedundancyStateChangeTimeThe time of the last change in the current
redundancy state.ro TimeStamp (SNMPv2-TC) .1.3.6.1.4.1.9.9.650.1.1.4.1.3 |
clrRedundancyIpAddressTypeThe type of internet address by which
this redundant device reachable.ro InetAddressType (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.650.1.1.4.1.4 |
clrRedundancyIpAddressThis object identifies the Internet address by which
this redundant device is reachable. The type of this
address is determined by the value of the
clrRedundancyIpAddressType object.ro InetAddress (INET-ADDRESS-MIB) .1.3.6.1.4.1.9.9.650.1.1.4.1.5 |
clrStats OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.650.1.2 |
clrLBStatsTableThis table contains the load balance statistics
related to a redundancy group. SEQUENCE OF ClrLBStatsEntry .1.3.6.1.4.1.9.9.650.1.2.1 |
clrLBStatsEntryEach entry represents the load balance statistics
applicable for a redundancy group. The entPhysicalIndex
specifies the entry in entPhysicalTable.
The entries will get created in this table
by way of adding entries in clrRedundancyConfigTable.
The entries will be deleted from this table
by way of removing entries in clrRedundancyConfigTable. ClrLBStatsEntry .1.3.6.1.4.1.9.9.650.1.2.1.1 |
clrLBStatsSharedStickyEntriesThis object indicates the number of sticky entries that the
local device sent to the peer. Sticky entries is a LB
configuration which allows multiple connections from the same
client to be sent to the same server. Stickiness can be
configured based on source IP address, HTTP cookies, SSL session
ID ( for SSL traffic only ) , etc.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.1.1.1 |
clrLBStatsSentPacketsThis object contains the number of valid packets that the local
device sent to the peer.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.1.1.2 |
clrLBStatsSendFailuresThis object contains the number of packets that the local
device attempted to send to the peer, but failed.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.1.1.3 |
clrLBStatsDroppedEntriesThis object contains the number of sticky entries that the peer
sent to the local device, but the local device discarded them.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.1.1.4 |
clrLBStatsReceivedPacketsThis object contains the number of valid packets that the local
device received from the peer.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.1.1.5 |
clrLBStatsReceiveFailuresThis object contains the number of packets that the peer sent
to the local device, but the local device failed to receive
them.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.1.1.6 |
clrHAStatsTableThis table contains the statistics related to
a redundant peer. SEQUENCE OF ClrHAStatsEntry .1.3.6.1.4.1.9.9.650.1.2.2 |
clrHAStatsEntryEach entry represents the statistics
applicable for a redundant peer.
The entPhysicalIndex specifies the
entry in entPhysicalTable .
The entries will get created in this table
by way of adding entries in clrPeerConfigTable.
The entries will be deleted from this table
by way of removing entries in clrPeerConfigTable. ClrHAStatsEntry .1.3.6.1.4.1.9.9.650.1.2.2.1 |
clrHAStatsTxHeartBeatMsgsThis object refers to the number of heart beat messages sent
to the peer.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.2.1.1 |
clrHAStatsRxHeartBeatMsgsThis object refers to the number of heart beat messages
received from the peer.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.2.1.2 |
clrHAStatsMissedHeartBeatMsgsThis object refers to the number of missed heart
beat messages.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.2.1.3 |
clrHAStatsRxUniDirectionalHeartBeatMsgsThis object indicates that the heartbeat messages from a peer
is unidirectional. That is, the peer cannot receive ( only send
) heartbeats.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.2.1.4 |
clrHAStatsHeartBeatTimeoutMismatchesEach HB packet contains the configured interval in the packet.
When a peer receives a HB packet, it checks to see if the
interval in the HB packet matches the interval configured
locally. This object indicates the number of HB that the local
device received from the remote peer with a mismatched HB
interval.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.2.1.5 |
clrHAStatsPeerUpEventsThis object contains the number of peer up messages that the
local device sent to the remote peer.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.2.1.6 |
clrHAStatsPeerDownEventsThis object contains the number of peer down messages that the
local device sent to the remote peer.ro Counter64 .1.3.6.1.4.1.9.9.650.1.2.2.1.7 |
clrNotifObjects OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.650.1.3 |
clrStateChangeNotifEnabledThis object controls the generation of
clrRedundancyStateChange notification.
'true' : Indicates that clrRedundancyStateChange
notification is to be generated when the state
changes. That is, notification generation
is enabled.
'false' : Indicates that clrRedundancyStateChange
notification generation is disabled.rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.9.9.650.1.3.1 |
ciscoLmRedundancyMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.650.2 |
ciscoLmRedundancyMIBCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.650.2.1 |
ciscoLmRedundancyMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.9.9.650.2.2 |