The best estimate of the total number of collisions
on this Ethernet segment during this sampling
interval.
The value returned will depend on the location of
the RMON probe. Section 8.2.1.3 (10BASE-5) and
section 10.3.1.3 (10BASE-2) of IEEE standard 802.3
states that a station must detect a collision, in
the receive mode, if three or more stations are
transmitting simultaneously. A repeater port must
detect a collision when two or more stations are
transmitting simultaneously. Thus a probe placed on
a repeater port could record more collisions than a
probe connected to a station on the same segment
would.
Probe location plays a much smaller role when
considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE
standard 802.3 defines a collision as the
simultaneous presence of signals on the DO and RD
circuits (transmitting and receiving at the same
time). A 10BASE-T station can only detect
collisions when it is transmitting. Thus probes
placed on a station and a repeater, should report
the same number of collisions.
Note also that an RMON probe inside a repeater
should ideally report collisions between the
repeater and one or more other hosts (transmit
collisions as defined by IEEE 802.3k) plus receiver
collisions observed on any coax segments to which
the repeater is connected.
Parsed from file RMON-MIB.mib
Module: RMON-MIB
The best estimate of the total number of collisions
on this Ethernet segment during this sampling
interval.
The value returned will depend on the location of the
RMON probe. Section 8.2.1.3 (10BASE-5) and section
10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a
station must detect a collision, in the receive mode, if
three or more stations are transmitting simultaneously. A
repeater port must detect a collision when two or more
stations are transmitting simultaneously. Thus a probe
placed on a repeater port could record more collisions
than a probe connected to a station on the same segment
would.
Probe location plays a much smaller role when considering
10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3
defines a collision as the simultaneous presence of signals
on the DO and RD circuits (transmitting and receiving
at the same time). A 10BASE-T station can only detect
collisions when it is transmitting. Thus probes placed on
a station and a repeater, should report the same number of
collisions.
Note also that an RMON probe inside a repeater should
ideally report collisions between the repeater and one or
more other hosts (transmit collisions as defined by IEEE
802.3k) plus receiver collisions observed on any coax
segments to which the repeater is connected.
etherHistoryCollisions OBJECT-TYPE
SYNTAX Counter32
UNITS "Collisions"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The best estimate of the total number of collisions
on this Ethernet segment during this sampling
interval.
The value returned will depend on the location of the
RMON probe. Section 8.2.1.3 (10BASE-5) and section
10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a
station must detect a collision, in the receive mode, if
three or more stations are transmitting simultaneously. A
repeater port must detect a collision when two or more
stations are transmitting simultaneously. Thus a probe
placed on a repeater port could record more collisions
than a probe connected to a station on the same segment
would.
Probe location plays a much smaller role when considering
10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3
defines a collision as the simultaneous presence of signals
on the DO and RD circuits (transmitting and receiving
at the same time). A 10BASE-T station can only detect
collisions when it is transmitting. Thus probes placed on
a station and a repeater, should report the same number of
collisions.
Note also that an RMON probe inside a repeater should
ideally report collisions between the repeater and one or
more other hosts (transmit collisions as defined by IEEE
802.3k) plus receiver collisions observed on any coax
segments to which the repeater is connected."
View at oid-info.com
The best estimate of the total number of collisions
on this Ethernet segment during this interval.
Parsed from file rfc1271.mib.txt
Company: None
Module: RFC1271-MIB
The best estimate of the total number of collisions
on this Ethernet segment during this sampling
interval.
The value returned will depend on the location of the
RMON probe. Section 8.2.1.3 (10BASE-5) and section
10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a
station must detect a collision, in the receive mode, if
three or more stations are transmitting simultaneously. A
repeater port must detect a collision when two or more
stations are transmitting simultaneously. Thus a probe
placed on a repeater port could record more collisions
than a probe connected to a station on the same segment
would.
Probe location plays a much smaller role when considering
10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3
defines a collision as the simultaneous presence of signals
on the DO and RD circuits (transmitting and receiving
at the same time). A 10BASE-T station can only detect
collisions when it is transmitting. Thus probes placed on
a station and a repeater, should report the same number of
collisions.
Note also that an RMON probe inside a repeater should
ideally report collisions between the repeater and one or
more other hosts (transmit collisions as defined by IEEE
802.3k) plus receiver collisions observed on any coax
segments to which the repeater is connected.
etherHistoryCollisions OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The best estimate of the total number of collisions on this Ethernet segment during this sampling interval. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected." ::= { etherHistoryEntry 14 }
etherHistoryCollisions OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The best estimate of the total number of collisions on this Ethernet segment during this sampling interval. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected." ::= { etherHistoryEntry 14 }
Automatically extracted from RFC2819
etherHistoryCollisions OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The best estimate of the total number of collisions on this Ethernet segment during this interval." ::= { etherHistoryEntry 14 }
etherHistoryCollisions OBJECT-TYPE SYNTAX Counter32 UNITS "Collisions" MAX-ACCESS read-only STATUS current DESCRIPTION "The best estimate of the total number of collisions on this Ethernet segment during this sampling interval. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected." ::= { etherHistoryEntry 14 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.16.2.2.1.1 | etherHistoryIndex | 6 | 6 | The history of which this entry is a part. The history identified by a particular value of this index is the same history as ide… |
| 1.3.6.1.2.1.16.2.2.1.2 | etherHistorySampleIndex | 0 | 0 | An index that uniquely identifies the particular sample this entry represents among all samples associated with the same historyC… |
| 1.3.6.1.2.1.16.2.2.1.3 | etherHistoryIntervalStart | 0 | 0 | The value of sysUpTime at the start of the interval over which this sample was measured. If the probe keeps track of the time of… |
| 1.3.6.1.2.1.16.2.2.1.4 | etherHistoryDropEvents | 0 | 0 | The total number of events in which packets were dropped by the probe due to lack of resources during this interval. Note that t… |
| 1.3.6.1.2.1.16.2.2.1.5 | etherHistoryOctets | 0 | 0 | The total number of octets of data (including those in bad packets) received on the network (excluding framing bits but including… |
| 1.3.6.1.2.1.16.2.2.1.6 | etherHistoryPkts | 0 | 0 | The number of packets (including bad packets) received during this sampling interval. |
| 1.3.6.1.2.1.16.2.2.1.7 | etherHistoryBroadcastPkts | 0 | 0 | The number of good packets received during this sampling interval that were directed to the broadcast address. |
| 1.3.6.1.2.1.16.2.2.1.8 | etherHistoryMulticastPkts | 0 | 0 | The number of good packets received during this sampling interval that were directed to a multicast address. Note that this numb… |
| 1.3.6.1.2.1.16.2.2.1.9 | etherHistoryCRCAlignErrors | 0 | 0 | The number of packets received during this sampling interval that had a length (excluding framing bits but including FCS octets) … |
| 1.3.6.1.2.1.16.2.2.1.10 | etherHistoryUndersizePkts | 0 | 0 | The number of packets received during this interval that were less than 64 octets long (excluding framing bits but including FCS o… |
| 1.3.6.1.2.1.16.2.2.1.11 | etherHistoryOversizePkts | 0 | 0 | The number of packets received during this interval that were longer than 1518 octets (excluding framing bits but including FCS oc… |
| 1.3.6.1.2.1.16.2.2.1.12 | etherHistoryFragments | 0 | 0 | The total number of packets received during this sampling interval that were not an integral number of octets in length or that ha… |
| 1.3.6.1.2.1.16.2.2.1.13 | etherHistoryJabbers | 0 | 0 | The number of packets received during this interval that were longer than 1518 octets (excluding framing bits but including FCS o… |
| 1.3.6.1.2.1.16.2.2.1.15 | etherHistoryUtilization | 0 | 0 | The best estimate of the mean physical layer network utilization on this interface during this interval, in hundredths of a perce… |