DKT-RMON-MIB :: rmonCPUPortGetFragments

MIB Reference — IPNetwork Monitor · Updated September 26, 2026

All MIBs › DKT-RMON-MIB › rmonCPUPortGetFragments

rmonCPUPortGetFragments

Module: DKT-RMON-MIB

OID (symbolic): DKT-RMON-MIB::rmonCPUPortGetFragments

OID (numeric): 1.3.6.1.4.1.27304.13.4.1.26

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: Total frames received with a length of less than 64 octets and an invalid FCS

What is rmonCPUPortGetFragments?

Counts frames received on the CPU port shorter than 64 octets with an invalid CRC, i.e. true collision fragments or corrupted runt frames. A high fragment count is a classic sign of excessive collisions or a bad cable or connector on that segment.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.27304.13.4.1.26
snmpwalk -v2c -c public <target> DKT-RMON-MIB::rmonCPUPortGetFragments

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.27304.13.4.1.26.1
snmpget -v2c -c public <target> DKT-RMON-MIB::rmonCPUPortGetFragments.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> rmonCPUPortGetFragments.1

Start monitoring DKT A/S Ethernet switch (RMON statistics) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DKT-RMON-MIB::rmonCPUPortGetFragments OID value, configure state conditions and alerts, and monitor any DKT A/S Ethernet switch (RMON statistics) from a single console.

OID Breakdown

Upper-level ancestors (7 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.27304dktDKT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.27304.13rmonMIBDKT-RMON-MIB
1.3.6.1.4.1.27304.13.4rmonPortsDKT-RMON-MIB
1.3.6.1.4.1.27304.13.4.1rmonCPUPortDKT-RMON-MIB
1.3.6.1.4.1.27304.13.4.1.26rmonCPUPortGetFragmentsDKT-RMON-MIB