DKT-RMON-MIB :: rmonCPUPortGetJabber

MIB Reference — IPNetwork Monitor · Updated September 26, 2026

All MIBs › DKT-RMON-MIB › rmonCPUPortGetJabber

rmonCPUPortGetJabber

Module: DKT-RMON-MIB

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

OID (numeric): 1.3.6.1.4.1.27304.13.4.1.28

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: Total frames received with a length more than MaxSize octets and an invalid FCS

What is rmonCPUPortGetJabber?

Counts frames received on the CPU port longer than the maximum frame size and with an invalid CRC, the classic 'jabbering' network-adapter symptom. A nonzero count points to a faulty NIC on that segment that needs to be tracked down and replaced.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.27304.13.4.1.28
snmpwalk -v2c -c public <target> DKT-RMON-MIB::rmonCPUPortGetJabber

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.27304.13.4.1.28.1
snmpget -v2c -c public <target> DKT-RMON-MIB::rmonCPUPortGetJabber.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::rmonCPUPortGetJabber 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.28rmonCPUPortGetJabberDKT-RMON-MIB