CLNS-MIB :: clnpReasmReqds

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCLNS-MIBclnpReasmReqds

clnpReasmReqds

Module: CLNS-MIB

OID (symbolic): CLNS-MIB::clnpReasmReqds

OID (numeric): 1.3.6.1.3.1.1.15

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: The number of CLNP segments received which needed to be reassembled at this entity.

What is clnpReasmReqds?

This read-only counter tracks the number of CLNP segments received that needed to be reassembled at this entity because the original PDU had been fragmented in transit. An admin uses this to gauge how much of the incoming traffic arrives fragmented, which matters because reassembly consumes buffer memory and CPU relative to unfragmented traffic. For example, an unusually high count here relative to total received PDUs might prompt the admin to investigate whether an upstream device is unnecessarily fragmenting CLNP packets that could otherwise be sent whole.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.3.1.1.15
snmpwalk -v2c -c public <target> CLNS-MIB::clnpReasmReqds

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.3.1.1.15.1
snmpget -v2c -c public <target> CLNS-MIB::clnpReasmReqds.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::clnpReasmReqds 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 OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.3experimentalAXON-MIB
Numeric OIDNameModule
1.3.6.1.3.1clnsCLNS-MIB
1.3.6.1.3.1.1clnpCLNS-MIB
1.3.6.1.3.1.1.15clnpReasmReqdsCLNS-MIB