DKT-RMON-MIB :: rmonLAN4PortGetExcessive

MIB Reference — IPNetwork Monitor · Updated September 26, 2026

All MIBs › DKT-RMON-MIB › rmonLAN4PortGetExcessive

rmonLAN4PortGetExcessive

Module: DKT-RMON-MIB

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

OID (numeric): 1.3.6.1.4.1.27304.13.4.6.18

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: The number of frames dropped in the transmit MAC due to excessive collision condition. The counter is application in half-duplex mode only

What is rmonLAN4PortGetExcessive?

Counts frames dropped by the LAN4 port's transmit MAC because of an excessive-collision condition, meaning a frame hit the retry limit; only meaningful in half-duplex mode. Persistent excessive-collision drops usually point to a duplex mismatch or an overloaded, heavily-contended half-duplex segment.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.27304.13.4.6.18
snmpwalk -v2c -c public <target> DKT-RMON-MIB::rmonLAN4PortGetExcessive

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.27304.13.4.6.18.1
snmpget -v2c -c public <target> DKT-RMON-MIB::rmonLAN4PortGetExcessive.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::rmonLAN4PortGetExcessive 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.6rmonLAN4PortDKT-RMON-MIB
1.3.6.1.4.1.27304.13.4.6.18rmonLAN4PortGetExcessiveDKT-RMON-MIB