CISCO-L4L7MODULE-REDUNDANCY-MIB

All MIBs › CISCO-L4L7MODULE-REDUNDANCY-MIB

Organization: Cisco Systems, Inc.

Last Updated: 2008-04-04

Category: Cisco Devices, Hardware and Environment, Web and Application Servers

Description: Manages redundancy and failover configuration for Cisco Layer 4-7 service modules.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is CISCO-L4L7MODULE-REDUNDANCY-MIB?

The CISCO-L4L7MODULE-REDUNDANCY-MIB manages redundancy and failover configuration for Cisco Layer 4-7 service modules that provide server load balancing, firewall, SSL offload, and intrusion detection services. It exposes peer configuration and status tables describing redundant peer relationships, including heartbeat intervals/counts and interface assignments used to detect peer failure. Administrators rely on it to monitor the operational health of the redundancy pairing, tracking clrPeerOperStatus to see whether a peer service module is up or down, and heartbeat counters to detect missed heartbeats that signal an impending or occurred failover. It works alongside the underlying L4-7 service module MIBs, such as SLB or firewall-specific MIBs, that it complements rather than replaces. It is deployed in data center and service-provider environments where pairs or groups of Cisco service modules are configured for high-availability load balancing, firewalling, or SSL termination. Engineers can download the CISCO-L4L7MODULE-REDUNDANCY-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in CISCO-L4L7MODULE-REDUNDANCY-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Cisco Layer 4-7 service module (SLB/firewall/SSL appliance)

Monitoring Examples

clrPeerConfigTable/clrPeerConfigEntry list each configured redundant peer via clrPeerId, clrPeerInterface, and clrPeerBackupInterface, while clrPeerHeartBeatTime and clrPeerHeartBeatCount define the failure-detection timing. An admin monitors clrPeerInfoTable's clrPeerOperStatus to confirm the peer is Active or Standby as expected; an unexpected status change combined with a spike in missed heartbeats indicates the backup module has taken over due to a hardware or link failure on the primary.

What Can Be Monitored

peer operational status
heartbeat interval and count
redundant interface assignment
failover/redundancy notifications

Imported Objects

From CISCO-SMI

ciscoMgmt

OBJECT-IDENTITY

From ENTITY-MIB

entPhysicalIndex

OBJECT-TYPE

From IF-MIB

InterfaceIndex
InterfaceIndexOrZero

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-SMI

Counter64
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE
Unsigned32

From SNMPv2-TC

RowStatus
StorageType
TEXTUAL-CONVENTION
TimeStamp
TruthValue

How to Use in IPNetwork Monitor

Example using clrLBStatsSharedStickyEntries OID:

Select a Cisco Layer 4-7 service module (SLB/firewall/SSL appliance) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type clrLBStatsSharedStickyEntries into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. This object indicates the number of sticky entries that the local device sent to the peer. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter64-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OIDs

OID symbolic	OID numeric	Type	Access	Description
ciscoL4L7moduleRedundancyMIB	1.3.6.1.4.1.9.9.650			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
ciscoLmRedundancyMIBNotifs	1.3.6.1.4.1.9.9.650.0
NTF clrRedundancyStateChange	1.3.6.1.4.1.9.9.650.0.1			The notification generated when the redundancy state is changed.
ciscoLmRedundancyMIBObjects	1.3.6.1.4.1.9.9.650.1
clrConfig	1.3.6.1.4.1.9.9.650.1.1
clrPeerConfigTable	1.3.6.1.4.1.9.9.650.1.1.1		not-accessible	This 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.
clrPeerConfigEntry	1.3.6.1.4.1.9.9.650.1.1.1.1		not-accessible	An entry in clrPeerConfigTable. Each entry contains information about peer interface, query interface, heart beat count and heart beat time.
U32 clrPeerId	1.3.6.1.4.1.9.9.650.1.1.1.1.1	Unsigned32	not-accessible	This object identifies unique id for the peer. The peer is used in redundancy configuration.
NUM clrPeerInterface	1.3.6.1.4.1.9.9.650.1.1.1.1.2	InterfaceIndex	read-create	This object specifies the interface used by the peers to exchange High Availability ( HA ) protocol information.
NUM clrPeerBackupInterface	1.3.6.1.4.1.9.9.650.1.1.1.1.3	InterfaceIndexOrZero	read-create	This 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.
U32 clrPeerHeartBeatTime	1.3.6.1.4.1.9.9.650.1.1.1.1.4	Unsigned32	read-create	The time interval between heartbeat/keep-alive messages exchanged between the peers.
U32 clrPeerHeartBeatCount	1.3.6.1.4.1.9.9.650.1.1.1.1.5	Unsigned32	read-create	This 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 ) .
STO clrPeerStorageType	1.3.6.1.4.1.9.9.650.1.1.1.1.6	StorageType	read-create	The storage type for this conceptual row.
ROW clrPeerRowStatus	1.3.6.1.4.1.9.9.650.1.1.1.1.7	RowStatus	read-create	This 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).
clrPeerInfoTable	1.3.6.1.4.1.9.9.650.1.1.2		not-accessible	This table contains information of the redundancy peer.
clrPeerInfoEntry	1.3.6.1.4.1.9.9.650.1.1.2.1		not-accessible	An 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'.
INT clrPeerOperStatus	1.3.6.1.4.1.9.9.650.1.1.2.1.1	INTEGER	read-only	This 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.
IPt clrPeerIpAddressType	1.3.6.1.4.1.9.9.650.1.1.2.1.2	InetAddressType	read-only	The type of internet address by which the peer is reachable.
IP clrPeerIpAddress	1.3.6.1.4.1.9.9.650.1.1.2.1.3	InetAddress	read-only	This Internet address for the redundant peer. The type of this address is determined by the value of the clrPeerIpAddressType object.
INT clrPeerSoftwareCompatibilty	1.3.6.1.4.1.9.9.650.1.1.2.1.4	INTEGER	read-only	Indicates 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'.
INT clrPeerLicenseCompatibility	1.3.6.1.4.1.9.9.650.1.1.2.1.5	INTEGER	read-only	Indicates 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.
U32 clrPeerRedGroups	1.3.6.1.4.1.9.9.650.1.1.2.1.6	Unsigned32	read-only	This object refers to the number of redundancy groups the peer is associated with.
clrRedundancyConfigTable	1.3.6.1.4.1.9.9.650.1.1.3		not-accessible	This table is used for configuring redundancy groups. The redundancy group is configured by specifying the same value of 'clrRedGroupId' in multiple devices.
clrRedundancyConfigEntry	1.3.6.1.4.1.9.9.650.1.1.3.1		not-accessible	An 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'.
U32 clrRedGroupId	1.3.6.1.4.1.9.9.650.1.1.3.1.1	Unsigned32	not-accessible	This object specifies the redundancy group identifier. This is the unique id of the redundancy group.
U32 clrRedPeerId	1.3.6.1.4.1.9.9.650.1.1.3.1.2	Unsigned32	read-create	The 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'.
U32 clrRedPriority	1.3.6.1.4.1.9.9.650.1.1.3.1.3	Unsigned32	read-create	The 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'.
T/F clrRedPreempt	1.3.6.1.4.1.9.9.650.1.1.3.1.4	TruthValue	read-create	This 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.
U32 clrRedFailOverTime	1.3.6.1.4.1.9.9.650.1.1.3.1.5	Unsigned32	read-create	The 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.
CIS clrRedState	1.3.6.1.4.1.9.9.650.1.1.3.1.6	CiscoL4L7RedState	read-only	The current redundancy state.
TIM clrRedStateChangeTime	1.3.6.1.4.1.9.9.650.1.1.3.1.7	TimeStamp	read-only	The time of the last change in the current redundancy state.
OCT clrRedContext	1.3.6.1.4.1.9.9.650.1.1.3.1.8	OCTET STRING	read-create	This 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.
STO clrRedStorageType	1.3.6.1.4.1.9.9.650.1.1.3.1.9	StorageType	read-create	The storage type for this conceptual row.
ROW clrRedRowStatus	1.3.6.1.4.1.9.9.650.1.1.3.1.10	RowStatus	read-create	This 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).
clrRedundancyInfoTable	1.3.6.1.4.1.9.9.650.1.1.4		not-accessible	This table contains information on the devices that are part of redundancy group.
clrRedundancyInfoEntry	1.3.6.1.4.1.9.9.650.1.1.4.1		not-accessible	An 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'.
U32 clrRedundancyPriority	1.3.6.1.4.1.9.9.650.1.1.4.1.1	Unsigned32	read-only	The priority value of this redundancy entry. This value is same as the value configured in 'clrRedPriority' for a redundancy group.
CIS clrRedundancyState	1.3.6.1.4.1.9.9.650.1.1.4.1.2	CiscoL4L7RedState	read-only	The current redundancy state.
TIM clrRedundancyStateChangeTime	1.3.6.1.4.1.9.9.650.1.1.4.1.3	TimeStamp	read-only	The time of the last change in the current redundancy state.
IPt clrRedundancyIpAddressType	1.3.6.1.4.1.9.9.650.1.1.4.1.4	InetAddressType	read-only	The type of internet address by which this redundant device reachable.
IP clrRedundancyIpAddress	1.3.6.1.4.1.9.9.650.1.1.4.1.5	InetAddress	read-only	This 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.
clrStats	1.3.6.1.4.1.9.9.650.1.2
clrLBStatsTable	1.3.6.1.4.1.9.9.650.1.2.1		not-accessible	This table contains the load balance statistics related to a redundancy group.
clrLBStatsEntry	1.3.6.1.4.1.9.9.650.1.2.1.1		not-accessible	Each 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.
C64 clrLBStatsSharedStickyEntriesEx	1.3.6.1.4.1.9.9.650.1.2.1.1.1	Counter64	read-only	This 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.
C64 clrLBStatsSentPackets	1.3.6.1.4.1.9.9.650.1.2.1.1.2	Counter64	read-only	This object contains the number of valid packets that the local device sent to the peer.
C64 clrLBStatsSendFailures	1.3.6.1.4.1.9.9.650.1.2.1.1.3	Counter64	read-only	This object contains the number of packets that the local device attempted to send to the peer, but failed.
C64 clrLBStatsDroppedEntries	1.3.6.1.4.1.9.9.650.1.2.1.1.4	Counter64	read-only	This object contains the number of sticky entries that the peer sent to the local device, but the local device discarded them.
C64 clrLBStatsReceivedPackets	1.3.6.1.4.1.9.9.650.1.2.1.1.5	Counter64	read-only	This object contains the number of valid packets that the local device received from the peer.
C64 clrLBStatsReceiveFailures	1.3.6.1.4.1.9.9.650.1.2.1.1.6	Counter64	read-only	This object contains the number of packets that the peer sent to the local device, but the local device failed to receive them.
clrHAStatsTable	1.3.6.1.4.1.9.9.650.1.2.2		not-accessible	This table contains the statistics related to a redundant peer.
clrHAStatsEntry	1.3.6.1.4.1.9.9.650.1.2.2.1		not-accessible	Each 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.
C64 clrHAStatsTxHeartBeatMsgs	1.3.6.1.4.1.9.9.650.1.2.2.1.1	Counter64	read-only	This object refers to the number of heart beat messages sent to the peer.
C64 clrHAStatsRxHeartBeatMsgs	1.3.6.1.4.1.9.9.650.1.2.2.1.2	Counter64	read-only	This object refers to the number of heart beat messages received from the peer.
C64 clrHAStatsMissedHeartBeatMsgs	1.3.6.1.4.1.9.9.650.1.2.2.1.3	Counter64	read-only	This object refers to the number of missed heart beat messages.
C64 clrHAStatsRxUniDirectionalHeartBeatMsgs	1.3.6.1.4.1.9.9.650.1.2.2.1.4	Counter64	read-only	This object indicates that the heartbeat messages from a peer is unidirectional. That is, the peer cannot receive ( only send ) heartbeats.
C64 clrHAStatsHeartBeatTimeoutMismatches	1.3.6.1.4.1.9.9.650.1.2.2.1.5	Counter64	read-only	Each 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.
C64 clrHAStatsPeerUpEvents	1.3.6.1.4.1.9.9.650.1.2.2.1.6	Counter64	read-only	This object contains the number of peer up messages that the local device sent to the remote peer.
C64 clrHAStatsPeerDownEvents	1.3.6.1.4.1.9.9.650.1.2.2.1.7	Counter64	read-only	This object contains the number of peer down messages that the local device sent to the remote peer.
clrNotifObjects	1.3.6.1.4.1.9.9.650.1.3
T/F clrStateChangeNotifEnabled	1.3.6.1.4.1.9.9.650.1.3.1	TruthValue	read-write	This 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.
ciscoLmRedundancyMIBConformance	1.3.6.1.4.1.9.9.650.2
ciscoLmRedundancyMIBCompliances	1.3.6.1.4.1.9.9.650.2.1
ciscoLmRedundancyMIBCompliance	1.3.6.1.4.1.9.9.650.2.1.1			The compliance statement for entities which implement the L4L7 Switch Redundancy.
ciscoLmRedundancyMIBGroups	1.3.6.1.4.1.9.9.650.2.2
clrPeerConfigGroup	1.3.6.1.4.1.9.9.650.2.2.1			This group contains the peer configuration objects.
clrRedConfigGroup	1.3.6.1.4.1.9.9.650.2.2.2			This group contains the redundancy configuration objects.
clrRedInfoGroup	1.3.6.1.4.1.9.9.650.2.2.3			This group contains the redundancy information objects.
cslbxNotifControlGroup	1.3.6.1.4.1.9.9.650.2.2.4			The collection of objects to control the notifications for state changed in a L4 redundancy configuration.
cslbxNotifGroup	1.3.6.1.4.1.9.9.650.2.2.5			This group contains the notifications related to redundancy.
clrRedundancyStatsGroup	1.3.6.1.4.1.9.9.650.2.2.6			This group contains objects related to redundant peer and load balacing statistics.

RFC description

Redundancy management for Cisco Layer 4-7 Service Modules used in server load balancing, firewalls, and intrusion detection systems.

Start monitoring Cisco Layer 4-7 service module (SLB/firewall/SSL appliance) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download CISCO-L4L7MODULE-REDUNDANCY-MIB