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.
Parsed from file repeater_private.mib.txt
Company: None
Module: VERTICAL-SNMP-REPEATER-MIB
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.
Parsed from file VERTICAL-SNMP-REPEATER-MIB.mib
Module: VERTICAL-SNMP-REPEATER-MIB
Vendor: Vertical Networks, Inc.
Module: VERTICAL-SNMP-REPEATER-MIB
[Automatically extracted from oidview.com]
vrptrMonitorPortDataRateMismatches OBJECT-TYPE SYNTAX INTEGER { notSupported(-1), supported(0) } ACCESS read-only STATUS mandatory 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." REFERENCE "[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches." ::= { vrptrMonitorPortEntry 13 }
vrptrMonitorPortDataRateMismatches OBJECT-TYPE SYNTAX INTEGER { notSupported(-1), supported(0) } ACCESS read-only STATUS mandatory 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." REFERENCE "[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches." ::= { vrptrMonitorPortEntry 13 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2338.4.2.3.1.1.1 | vrptrMonitorPortGroupIndex | 0 | 0 | This object identifies the group containing the port for which this entry contains information. |
| 1.3.6.1.4.1.2338.4.2.3.1.1.2 | vrptrMonitorPortIndex | 0 | 0 | This object identifies the port within the group for which this entry contains information. |
| 1.3.6.1.4.1.2338.4.2.3.1.1.3 | vrptrMonitorPortReadableFrames | 0 | 0 | This object is the number of frames of valid frame length that have been received on this port. This counter is incremented by on… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.4 | vrptrMonitorPortReadableOctets | 0 | 0 | This object is the number of octets contained in valid frames that have been received on this port. This counter is incremented b… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.5 | vrptrMonitorPortFCSErrors | 0 | 0 | This counter is incremented by one for each frame received on this port with the FCSError signal asserted and the FramingError an… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.6 | vrptrMonitorPortAlignmentErrors | 0 | 0 | This counter is incremented by one for each frame received on this port with the FCSError and FramingError signals asserted and C… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.7 | vrptrMonitorPortFrameTooLongs | 0 | 0 | This counter is incremented by one for each frame received on this port whose OctetCount is greater than maxFrameSize (Ref: 4.4.2… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.8 | vrptrMonitorPortShortEvents | 0 | 0 | This counter is incremented by one for each CarrierEvent on this port with ActivityDuration less than ShortEventMaxTime. ShortEv… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.9 | vrptrMonitorPortRunts | 0 | 0 | This counter is incremented by one for each CarrierEvent on this port that meets one of the following two conditions. Only one t… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.10 | vrptrMonitorPortCollisions | 0 | 0 | For a clause 9 repeater, this counter is incremented by one for any CarrierEvent signal on any port for which the CollisionEvent … |
| 1.3.6.1.4.1.2338.4.2.3.1.1.11 | vrptrMonitorPortLateEvents | 0 | 0 | For a clause 9 repeater port, this counter is incremented by one for each CarrierEvent on this port in which the CollIn(X) variabl… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.12 | vrptrMonitorPortVeryLongEvents | 0 | 0 | For a clause 9 repeater port, this counter is incremented by one for each CarrierEvent whose ActivityDuration is greater than the… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.14 | vrptrMonitorPortAutoPartitions | 0 | 0 | This counter is incremented by one for each time the repeater has automatically partitioned this port. The conditions that cause a… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.15 | vrptrMonitorPortTotalErrors | 0 | 0 | The total number of errors which have occurred on this port. This counter is the summation of the values of other error counters… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.16 | vrptrMonitorPortLastChange | 0 | 0 | The value of sysUpTime when the last of the following occurred: 1) the agent cold- or warm-started; 2) the row for the port was cr… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.17 | vrptrMonitorPortSentFrames | 0 | 0 | This object is the number of frames of valid frame length that have been sent on this port. This counter is incremented by one fo… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.18 | vrptrMonitorPortSentOctets | 0 | 0 | This object is the number of octets contained in valid frames that have been sent on this port. This counter is incremented by Oc… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.19 | vrptrMonitorPortDroppedFrames | 0 | 0 | This counter is incremented by one for each time the switch had dropped a frame due a buffer full event. A discontinuity may occur… |
| 1.3.6.1.4.1.2338.4.2.3.1.1.20 | vrptrMonitorPortOtherErrors | 1 | 1 | This counter is incremented by one for each time the repeater has detected an error which is not reported in any other error count… |