CISCO-L4L7MODULE-REDUNDANCY-MIB :: clrLBStatsSharedStickyEntries

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-L4L7MODULE-REDUNDANCY-MIB › clrLBStatsSharedStickyEntries

clrLBStatsSharedStickyEntries

Module: CISCO-L4L7MODULE-REDUNDANCY-MIB

OID (symbolic): CISCO-L4L7MODULE-REDUNDANCY-MIB::clrLBStatsSharedStickyEntries

OID (numeric): 1.3.6.1.4.1.9.9.650.1.2.1.1.1

Node type: OBJECT-TYPE

Type: Counter64

Access: read-only

Description: 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.

What is clrLBStatsSharedStickyEntries?

Counts the number of load-balancer sticky session entries the local device has shared with its redundancy peer, so that connections from the same client keep going to the same server after a failover.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.650.1.2.1.1.1
snmpwalk -v2c -c public <target> CISCO-L4L7MODULE-REDUNDANCY-MIB::clrLBStatsSharedStickyEntries

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.650.1.2.1.1.1.1
snmpget -v2c -c public <target> CISCO-L4L7MODULE-REDUNDANCY-MIB::clrLBStatsSharedStickyEntries.1

Start monitoring Cisco Layer 4-7 service module (SLB/firewall/SSL appliance) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-L4L7MODULE-REDUNDANCY-MIB::clrLBStatsSharedStickyEntries OID value, configure state conditions and alerts, and monitor any Cisco Layer 4-7 service module (SLB/firewall/SSL appliance) from a single console.

How to Use in IPNetwork Monitor

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.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.650ciscoL4L7moduleRedundancyMIBCISCO-L4L7MODULE-REDUNDANCY-MIB
1.3.6.1.4.1.9.9.650.1ciscoLmRedundancyMIBObjectsCISCO-L4L7MODULE-REDUNDANCY-MIB
1.3.6.1.4.1.9.9.650.1.2clrStatsCISCO-L4L7MODULE-REDUNDANCY-MIB
1.3.6.1.4.1.9.9.650.1.2.1clrLBStatsTableCISCO-L4L7MODULE-REDUNDANCY-MIB
1.3.6.1.4.1.9.9.650.1.2.1.1clrLBStatsEntryCISCO-L4L7MODULE-REDUNDANCY-MIB
1.3.6.1.4.1.9.9.650.1.2.1.1.1clrLBStatsSharedStickyEntriesCISCO-L4L7MODULE-REDUNDANCY-MIB