All MIBs › VERTICAL-SNMP-REPEATER-MIB › vrptrMonitorPortRunts
vrptrMonitorPortRunts
Module: VERTICAL-SNMP-REPEATER-MIB
OID (symbolic): VERTICAL-SNMP-REPEATER-MIB::vrptrMonitorPortRunts
OID (numeric): 1.3.6.1.4.1.2338.4.2.3.1.1.9
Node type: OBJECT-TYPE
Type: INTEGER
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 collision fragments may exceed ValidPacketMinTime. A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes.
The approximate minimum time for rollover of this counter is 16 hours in a 10Mb/s repeater.
What is vrptrMonitorPortRunts?
A count of carrier events on this port meeting the runt criteria — longer than a short event but shorter than a valid packet, or under 64 octets, with no collision signal — encoded as notSupported(-1)/supported(0) per this MIB's revised syntax. Runts are usually normal collision fragments, though on large-diameter networks some legitimately-sized collision fragments may register here.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2338.4.2.3.1.1.9 snmpwalk -v2c -c public <target> VERTICAL-SNMP-REPEATER-MIB::vrptrMonitorPortRunts
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.2338.4.2.3.1.1.9.1 snmpget -v2c -c public <target> VERTICAL-SNMP-REPEATER-MIB::vrptrMonitorPortRunts.1
Start monitoring Vertical Networks SNMP repeater/hub (per-port status/collision-count status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the VERTICAL-SNMP-REPEATER-MIB::vrptrMonitorPortRunts OID value, configure state conditions and alerts, and monitor any Vertical Networks SNMP repeater/hub (per-port status/collision-count status) from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.2338 | vertical | VERTICAL-EVENTLOG-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.2338.4 | vsnmpDot3RptrMgt | VERTICAL-SNMP-REPEATER-MIB |
| 1.3.6.1.4.1.2338.4.2 | vrptrMonitorPackage | VERTICAL-SNMP-REPEATER-MIB |
| 1.3.6.1.4.1.2338.4.2.3 | vrptrMonitorPortInfo | VERTICAL-SNMP-REPEATER-MIB |
| 1.3.6.1.4.1.2338.4.2.3.1 | vrptrMonitorPortTable | VERTICAL-SNMP-REPEATER-MIB |
| 1.3.6.1.4.1.2338.4.2.3.1.1 | vrptrMonitorPortEntry | VERTICAL-SNMP-REPEATER-MIB |
| 1.3.6.1.4.1.2338.4.2.3.1.1.9 | vrptrMonitorPortRunts | VERTICAL-SNMP-REPEATER-MIB |