CHIPCOMMIB :: chipRptrMonitorPortRunts

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCHIPCOMMIBchipRptrMonitorPortRunts

chipRptrMonitorPortRunts

Module: CHIPCOMMIB

OID (symbolic): CHIPCOMMIB::chipRptrMonitorPortRunts

OID (numeric): 1.3.6.1.4.1.49.2.3.1.5.2.5.2.3.1.1.11

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.

An event whose length is greater than 74 bit times

but less than 82 bit times shall increment either

the shortEvents counter or the runts counter but

not both. A CarrierEvent greater than or equal to

552 bit times but less than 565 bit times may or

may not be counted as a runt.

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 runts may exceed ValidPacketMinTime.

The approximate minimum time for rollover of this

counter is 16 hours.

What is chipRptrMonitorPortRunts?

Counts carrier events on this port that qualify as runt frames - activity longer than a short event but shorter than a valid minimum packet time, indicating undersized or truncated frames.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.49.2.3.1.5.2.5.2.3.1.1.11
snmpwalk -v2c -c public <target> CHIPCOMMIB::chipRptrMonitorPortRunts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.49.2.3.1.5.2.5.2.3.1.1.11.1
snmpget -v2c -c public <target> CHIPCOMMIB::chipRptrMonitorPortRunts.1

Start monitoring Chipcom (3Com) Ethernet/Token Ring switching hub or LAN concentrator (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CHIPCOMMIB::chipRptrMonitorPortRunts OID value, configure state conditions and alerts, and monitor any Chipcom (3Com) Ethernet/Token Ring switching hub or LAN concentrator (legacy) from a single console.

OID Breakdown

Upper-level ancestors (12 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.49chipcomCHIPAGENT-MIB
1.3.6.1.4.1.49.2chipmib02CHIPAGENT-MIB
1.3.6.1.4.1.49.2.3chipProductsCHIPAGENT-MIB
1.3.6.1.4.1.49.2.3.1onlineCHIPAGENT-MIB
1.3.6.1.4.1.49.2.3.1.5olNetsCHIPAGENT-MIB
1.3.6.1.4.1.49.2.3.1.5.2olEnetCHIPAGENT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.49.2.3.1.5.2.5chipSnmpDot3RptrMgtCHIPCOMMIB
1.3.6.1.4.1.49.2.3.1.5.2.5.2chipRptrMonitorPackageCHIPCOMMIB
1.3.6.1.4.1.49.2.3.1.5.2.5.2.3chipRptrMonitorPortInfoCHIPCOMMIB
1.3.6.1.4.1.49.2.3.1.5.2.5.2.3.1chipRptrMonitorPortTableCHIPCOMMIB
1.3.6.1.4.1.49.2.3.1.5.2.5.2.3.1.1chipRptrMonitorPortEntryCHIPCOMMIB
1.3.6.1.4.1.49.2.3.1.5.2.5.2.3.1.1.11chipRptrMonitorPortRuntsCHIPCOMMIB