All MIBs › CLNS-MIB › clnpInErrHops
clnpInErrHops
Module: CLNS-MIB
OID (symbolic): CLNS-MIB::clnpInErrHops
OID (numeric): 1.3.6.1.3.1.2.17
Node type: OBJECT-TYPE
Type: Counter
Access: read-only
Description: The number of hop count exceeded CLNP Error PDUs received by this entity.
What is clnpInErrHops?
This read-only Counter counts hop-count-exceeded CLNP Error PDUs received by this entity. An admin cares because it means a PDU from this device exceeded the maximum hop count before reaching its destination, often a sign of a routing loop or an overly short lifetime setting. For example, hop-count-exceeded errors that grow whenever a specific remote NSAP is targeted suggest a routing loop on the path to that address.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.3.1.2.17 snmpwalk -v2c -c public <target> CLNS-MIB::clnpInErrHops
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.3.1.2.17.1 snmpget -v2c -c public <target> CLNS-MIB::clnpInErrHops.1
Start monitoring OSI CLNP/CLNS-capable router (vendor-neutral) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CLNS-MIB::clnpInErrHops OID value, configure state conditions and alerts, and monitor any OSI CLNP/CLNS-capable router (vendor-neutral) from a single console.
OID Breakdown
Upper-level ancestors (5 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.3 | experimental | AXON-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.3.1 | clns | CLNS-MIB |
| 1.3.6.1.3.1.2 | error | CLNS-MIB |
| 1.3.6.1.3.1.2.17 | clnpInErrHops | CLNS-MIB |