VERTICAL-SNMP-REPEATER-MIB :: vrptrMonitorPortShortEvents

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsVERTICAL-SNMP-REPEATER-MIBvrptrMonitorPortShortEvents

vrptrMonitorPortShortEvents

Module: VERTICAL-SNMP-REPEATER-MIB

OID (symbolic): VERTICAL-SNMP-REPEATER-MIB::vrptrMonitorPortShortEvents

OID (numeric): 1.3.6.1.4.1.2338.4.2.3.1.1.8

Node type: OBJECT-TYPE

Type: Counter

Access: read-only

Description: This counter is incremented by one for each CarrierEvent on this port with ActivityDuration less than ShortEventMaxTime. ShortEventMaxTime is greater than 74 bit times and less than 82 bit times. ShortEventMaxTime has tolerances included to provide for circuit losses between a conformance test point at the AUI and the measurement point within the state machine.

Notes:

ShortEvents may indicate externally generated noise hits which will cause the repeater to transmit Runts to its other ports, or propagate a collision (which may be late) back to the transmitting DTE and damaged frames to the rest of the network.

Implementors may wish to consider selecting the ShortEventMaxTime towards the lower end of the allowed tolerance range to accommodate bit losses suffered through physical channel devices not budgeted for within this standard.

The significance of this attribute is different in 10 and 100 Mb/s collision domains. Clause 9 repeaters perform fragment extension of short events which would be counted as runts on the interconnect ports of other repeaters. Clause 27 repeaters do not perform fragment extension.

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 vrptrMonitorPortShortEvents?

A count of carrier events on this port shorter than the minimum valid-frame time (roughly 74-82 bit times), often caused by externally-generated electrical noise hits; these can propagate as runts to other ports or a (possibly late) collision back to the sending device. Note 10Mb/s (clause 9) repeaters extend short fragments, which would otherwise be counted as runts on other repeaters' interconnect ports.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2338.4.2.3.1.1.8
snmpwalk -v2c -c public <target> VERTICAL-SNMP-REPEATER-MIB::vrptrMonitorPortShortEvents

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2338.4.2.3.1.1.8.1
snmpget -v2c -c public <target> VERTICAL-SNMP-REPEATER-MIB::vrptrMonitorPortShortEvents.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::vrptrMonitorPortShortEvents 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 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.2338verticalVERTICAL-EVENTLOG-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2338.4vsnmpDot3RptrMgtVERTICAL-SNMP-REPEATER-MIB
1.3.6.1.4.1.2338.4.2vrptrMonitorPackageVERTICAL-SNMP-REPEATER-MIB
1.3.6.1.4.1.2338.4.2.3vrptrMonitorPortInfoVERTICAL-SNMP-REPEATER-MIB
1.3.6.1.4.1.2338.4.2.3.1vrptrMonitorPortTableVERTICAL-SNMP-REPEATER-MIB
1.3.6.1.4.1.2338.4.2.3.1.1vrptrMonitorPortEntryVERTICAL-SNMP-REPEATER-MIB
1.3.6.1.4.1.2338.4.2.3.1.1.8vrptrMonitorPortShortEventsVERTICAL-SNMP-REPEATER-MIB