VERTICAL-SNMP-REPEATER-MIB :: vrptrMonitorPortDataRateMismatches

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsVERTICAL-SNMP-REPEATER-MIBvrptrMonitorPortDataRateMismatches

vrptrMonitorPortDataRateMismatches

Module: VERTICAL-SNMP-REPEATER-MIB

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

OID (numeric): 1.3.6.1.4.1.2338.4.2.3.1.1.13

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: This counter is incremented by one for each frame received by this port that meets all of the conditions required by only one of the following two measurement methods:

Measurement method A: 1) The CollisionEvent signal is not asserted (10Mb/s operation) or the Collision Count Increment state of the partition state diagram (fig 27-8 of [IEEE 802.3 Std]) has not been entered (100Mb/s operation). 2) The ActivityDuration is greater than ValidPacketMinTime. 3) The frequency (data rate) is detectably mismatched from the local transmit frequency.

Measurement method B: 1) The CollisionEvent signal is not asserted (10Mb/s operation) or the Collision Count Increment state of the partition state diagram (fig 27-8 of [IEEE 802.3 Std]) has not been entered (100Mb/s operation). 2) The OctetCount is greater than 63. 3) The frequency (data rate) is detectably mismatched from the local transmit frequency. The exact degree of mismatch is vendor specific and is to be defined by the vendor for conformance testing.

When this event occurs, other counters whose increment conditions were satisfied may or may not also be incremented, at the implementor's discretion. Whether or not the repeater was able to maintain data integrity is beyond the scope of this standard.

A discontinuity may occur in the value when the value of object rptrMonitorPortLastChange changes.

What is vrptrMonitorPortDataRateMismatches?

A count of frames received on this port whose data rate (clock frequency) is detectably mismatched from the repeater's own transmit frequency (encoded as notSupported(-1)/supported(0) per this MIB's revised syntax), pointing to a clocking problem on the attached device rather than a wiring or collision issue.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2338.4.2.3.1.1.13
snmpwalk -v2c -c public <target> VERTICAL-SNMP-REPEATER-MIB::vrptrMonitorPortDataRateMismatches

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2338.4.2.3.1.1.13.1
snmpget -v2c -c public <target> VERTICAL-SNMP-REPEATER-MIB::vrptrMonitorPortDataRateMismatches.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::vrptrMonitorPortDataRateMismatches 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.13vrptrMonitorPortDataRateMismatchesVERTICAL-SNMP-REPEATER-MIB