CLNS-MIB :: clnpRouteType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCLNS-MIBclnpRouteType

clnpRouteType

Module: CLNS-MIB

OID (symbolic): CLNS-MIB::clnpRouteType

OID (numeric): 1.3.6.1.3.1.1.22.1.8

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

Description: The type of route.

Setting this object to the value invalid(2) has the effect of invaliding the corresponding entry in the clnpRoutingTable. That is, it effectively dissasociates the destination identified with said entry from the route identified with said entry. It is an implementation-specific matter as to whether the agent removes an invalidated entry from the table. Accordingly, management stations must be prepared to receive tabular information from agents that corresponds to entries not currently in use. Proper interpretation of such entries requires examination of the relevant clnpRouteType object.

What is clnpRouteType?

This read-write object identifies whether a routing table entry represents a directly connected destination or a remote one reached through another system, and setting it to invalid(2) effectively removes that destination-to-route association. An admin managing static routes can use this specifically to deactivate a route without necessarily deleting the row outright, though whether the underlying agent physically removes an invalidated entry from the table is implementation-specific. For example, an admin decommissioning a static route would set this field to invalid(2) rather than assuming the row disappears immediately, and should verify separately whether the agent actually purges it.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.3.1.1.22.1.8
snmpwalk -v2c -c public <target> CLNS-MIB::clnpRouteType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.3.1.1.22.1.8.1
snmpget -v2c -c public <target> CLNS-MIB::clnpRouteType.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.3.1.1.22.1.8.1 i <value>

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::clnpRouteType 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.22clnpRoutingTableCLNS-MIB
1.3.6.1.3.1.1.22.1clnpRouteEntryCLNS-MIB
1.3.6.1.3.1.1.22.1.8clnpRouteTypeCLNS-MIB