CLNS-MIB :: clnpInUnknownULPs

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCLNS-MIBclnpInUnknownULPs

clnpInUnknownULPs

Module: CLNS-MIB

OID (symbolic): CLNS-MIB::clnpInUnknownULPs

OID (numeric): 1.3.6.1.3.1.1.8

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: The number of locally-addressed PDUs successfully received but discarded because the upper layer protocol was unknown or unsupported (e.g., not TP4).

What is clnpInUnknownULPs?

This read-only counter tracks locally addressed PDUs that were successfully received but discarded because their upper-layer protocol was unrecognized or unsupported, such as something other than TP4. An admin watching this counter rise would suspect an application or peer is attempting to use an upper-layer transport protocol this entity does not implement over CLNS. For example, if a legacy application on a peer system tried using an unsupported transport protocol over CLNP, packets destined for this entity would be counted here rather than delivered.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.3.1.1.8
snmpwalk -v2c -c public <target> CLNS-MIB::clnpInUnknownULPs

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.3.1.1.8.1
snmpget -v2c -c public <target> CLNS-MIB::clnpInUnknownULPs.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::clnpInUnknownULPs 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.8clnpInUnknownULPsCLNS-MIB