CISCO-LWAPP-MESH-MIB :: clMeshNodeHops

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-LWAPP-MESH-MIBclMeshNodeHops

clMeshNodeHops

Module: CISCO-LWAPP-MESH-MIB

OID (symbolic): CISCO-LWAPP-MESH-MIB::clMeshNodeHops

OID (numeric): 1.3.6.1.4.1.9.9.616.1.1.1.1.12

Node type: OBJECT-TYPE

Type: Gauge32

Access: read-only

Description: This object represents the number of hops a MAP mesh node is from RAP. When the clMeshNodeRole is set to 'RAP' this object will return a value of zero.

What is clMeshNodeHops?

Reports how many hops (relay nodes) this mesh access point is away from its root access point (RAP); a RAP itself always reports zero.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.616.1.1.1.1.12
snmpwalk -v2c -c public <target> CISCO-LWAPP-MESH-MIB::clMeshNodeHops

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.616.1.1.1.1.12.1
snmpget -v2c -c public <target> CISCO-LWAPP-MESH-MIB::clMeshNodeHops.1

Start monitoring Cisco wireless access points and controllers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-LWAPP-MESH-MIB::clMeshNodeHops OID value, configure state conditions and alerts, and monitor any Cisco wireless access points and controllers from a single console.

How to Use in IPNetwork Monitor

Select a Cisco wireless access point or controller 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 clMeshNodeHops 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 represents the number of hops a MAP mesh node is from RAP. 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 Gauge32-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 (in hops), 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.616ciscoLwappMeshMIBCISCO-LWAPP-MESH-MIB
1.3.6.1.4.1.9.9.616.1ciscoLwappMeshMIBObjectsCISCO-LWAPP-MESH-MIB
1.3.6.1.4.1.9.9.616.1.1ciscoLwappMeshConfigCISCO-LWAPP-MESH-MIB
1.3.6.1.4.1.9.9.616.1.1.1clMeshNodeTableCISCO-LWAPP-MESH-MIB
1.3.6.1.4.1.9.9.616.1.1.1.1clMeshNodeEntryCISCO-LWAPP-MESH-MIB
1.3.6.1.4.1.9.9.616.1.1.1.1.12clMeshNodeHopsCISCO-LWAPP-MESH-MIB