All MIBs › CLNS-MIB › clnpInErrHopReassms
clnpInErrHopReassms
Module: CLNS-MIB
OID (symbolic): CLNS-MIB::clnpInErrHopReassms
OID (numeric): 1.3.6.1.3.1.2.18
Node type: OBJECT-TYPE
Type: Counter
Access: read-only
Description: The number of hop count exceeded while reassembling CLNP Error PDUs received by this entity.
What is clnpInErrHopReassms?
This read-only Counter counts hop-count-exceeded-during-reassembly CLNP Error PDUs received by this entity. An admin cares because it shows fragments of a PDU from this device aged out before all pieces could be reassembled at the destination. For example, this counter rising for large fragmented transfers points to fragments arriving too slowly or via inconsistent paths to be reassembled in time.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.3.1.2.18 snmpwalk -v2c -c public <target> CLNS-MIB::clnpInErrHopReassms
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.3.1.2.18.1 snmpget -v2c -c public <target> CLNS-MIB::clnpInErrHopReassms.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> clnpInErrHopReassms.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::clnpInErrHopReassms 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.18 | clnpInErrHopReassms | CLNS-MIB |