CLNS-MIB :: clnpOutErrCksums

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCLNS-MIBclnpOutErrCksums

clnpOutErrCksums

Module: CLNS-MIB

OID (symbolic): CLNS-MIB::clnpOutErrCksums

OID (numeric): 1.3.6.1.3.1.2.27

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: The number of checksum CLNP Error PDUs sent by this entity.

What is clnpOutErrCksums?

This read-only Counter counts checksum CLNP Error PDUs sent by this entity. An admin cares because it means this device is finding checksum failures in PDUs it receives and reporting them, pointing to corruption occurring upstream of this node. For example, outbound checksum errors concentrated on one incoming interface suggest that link, rather than the sender's software, is corrupting frames.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.3.1.2.27
snmpwalk -v2c -c public <target> CLNS-MIB::clnpOutErrCksums

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.3.1.2.27.1
snmpget -v2c -c public <target> CLNS-MIB::clnpOutErrCksums.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> clnpOutErrCksums.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::clnpOutErrCksums 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.2errorCLNS-MIB
1.3.6.1.3.1.2.27clnpOutErrCksumsCLNS-MIB