SNMP-REPEATER-MIB :: rptrMonitorPortDataRateMismatches

MIB Reference — IPNetwork Monitor

All MIBsSNMP-REPEATER-MIBrptrMonitorPortDataRateMismatches

rptrMonitorPortDataRateMismatches

Module: SNMP-REPEATER-MIB

OID (symbolic): SNMP-REPEATER-MIB::rptrMonitorPortDataRateMismatches

OID (numeric): 1.3.6.1.2.1.22.2.3.1.1.13

Node type: OBJECT-TYPE

Type: Counter32

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

This counter accumulates the number of frames received by a repeater port that meet only one of two specific collision detection measurement methods, indicating a data rate mismatch condition. Operators monitor this metric to diagnose physical layer timing problems and mixed-speed cable segments. Increasing values suggest hardware incompatibility or port configuration errors.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.22.2.3.1.1.13
snmpwalk -v2c -c public <target> SNMP-REPEATER-MIB::rptrMonitorPortDataRateMismatches

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.22.2.3.1.1.13.1
snmpget -v2c -c public <target> SNMP-REPEATER-MIB::rptrMonitorPortDataRateMismatches.1

OID Breakdown

Numeric OIDNameModule
1isoLANART-AGENT
1.3orgBIANCA-BRICK-PPP-MIB
1.3.6dodBIANCA-BRICK-PPP-MIB
1.3.6.1internetBIANCA-BRICK-PPP-MIB
1.3.6.1.2mgmtBKTEL-HFC862-BASE-MIB
1.3.6.1.2.1mib_2CHECKPOINT-MIB-2
1.3.6.1.2.1.22snmpDot3RptrMgtLANART-AGENT
1.3.6.1.2.1.22.2rptrMonitorPackageLANART-AGENT
1.3.6.1.2.1.22.2.3rptrMonitorPortInfoLANART-AGENT
1.3.6.1.2.1.22.2.3.1rptrMonitorPortTableLANART-AGENT
1.3.6.1.2.1.22.2.3.1.1rptrMonitorPortEntryLANART-AGENT
1.3.6.1.2.1.22.2.3.1.1.13rptrMonitorPortDataRateMismatchesSNMP-REPEATER-MIB