MODULES-MIB :: fethPortRunts

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › MODULES-MIB › fethPortRunts

fethPortRunts

Module: MODULES-MIB

OID (symbolic): MODULES-MIB::fethPortRunts

OID (numeric): 1.3.6.1.4.1.81.12.6.1.1.1.20

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: This counter is incremented by one for each CarrierEvent on this port that meets one of the following two conditions. Only one test need be made. a) The ActivityDuration is greater than ShortEventMaxTime and less than validPacketMinTime and the CollisionEvent signal is deasserted. b) The OctetCount is less than 64, the ActivityDuration is greater than ShortEventMaxTime and the CollisionEvent signal is deasserted. ValidPacketMinTime is greater than or equal to 552 bit times and less than 565 bit times.

ValidPacketMinTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine.

Runts usually indicate collision fragments, a normal network event. In certain situations associated with large diameter networks a percentage of collision fragments may exceed ValidPacketMinTime. REFERENCE Reference IEEE Draft Std 802.3u/D4 Rptr Mgt, 30.4.1.3.10, aRunts. Reference IETF 100Base-T Repeater MIB, rptr100MonitorPortRunts.

What is fethPortRunts?

Counts undersized carrier events on this fast-Ethernet port that fall between the short-event and valid-frame thresholds, the same runts concept as ethPortRunts; these usually reflect normal collision fragments, though a high sustained rate on one port is worth checking for cabling or NIC issues.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.81.12.6.1.1.1.20
snmpwalk -v2c -c public <target> MODULES-MIB::fethPortRunts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.81.12.6.1.1.1.20.1
snmpget -v2c -c public <target> MODULES-MIB::fethPortRunts.1

Start monitoring Legacy multi-protocol Ethernet/token-ring hub or concentrator chassis with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MODULES-MIB::fethPortRunts OID value, configure state conditions and alerts, and monitor any Legacy multi-protocol Ethernet/token-ring hub or concentrator chassis from a single console.

OID Breakdown

Upper-level ancestors (8 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.81lannetGEN-MIB
1.3.6.1.4.1.81.12ethLANNET-MIB
Numeric OIDNameModule
1.3.6.1.4.1.81.12.6fethMODULES-MIB
1.3.6.1.4.1.81.12.6.1fethPortMODULES-MIB
1.3.6.1.4.1.81.12.6.1.1fethPortTableMODULES-MIB
1.3.6.1.4.1.81.12.6.1.1.1fethPortEntryMODULES-MIB
1.3.6.1.4.1.81.12.6.1.1.1.20fethPortRuntsMODULES-MIB