The best estimate of the total number of collisions
on this Ethernet segment.
Parsed from file ITOUCHHUB.mib
Module: ITOUCHHUB
The best estimate of the total number of collisions
on this Ethernet segment.
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.
etherStatsCollisions 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.
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.
Parsed from file rfc1271.mib.txt
Company: None
Module: RFC1271-MIB
The best estimate of the total number of collisions
on this Ethernet segment.
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.
etherStatsCollisions OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The best estimate of the total number of collisions on this Ethernet segment." ::= { etherStatsEntry 13 }
etherStatsCollisions OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The best estimate of the total number of collisions on this Ethernet segment. 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." ::= { etherStatsEntry 13 }
Automatically extracted from RFC2819
etherStatsCollisions OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "The best estimate of the total number of collisions on this Ethernet segment." ::= { etherStatsEntry 13 }
etherStatsCollisions 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. 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." ::= { etherStatsEntry 13 }
Internet Assigned Numbers Authority
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.2.1.16.1.1.1.1 | etherStatsIndex | 10 | 10 | The value of this object uniquely identifies this etherStats entry. |
| 1.3.6.1.2.1.16.1.1.1.2 | etherStatsDataSource | 2 | 2 | This object identifies the source of the data that this etherStats entry is configured to analyze. This source can be any ethern… |
| 1.3.6.1.2.1.16.1.1.1.3 | etherStatsDropEvents | 0 | 0 | The total number of events in which packets were dropped by the probe due to lack of resources. Note that this number is not nece… |
| 1.3.6.1.2.1.16.1.1.1.4 | etherStatsOctets | 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.1.1.1.5 | etherStatsPkts | 0 | 0 | The total number of packets (including error packets) received. |
| 1.3.6.1.2.1.16.1.1.1.6 | etherStatsBroadcastPkts | 0 | 0 | The total number of good packets received that were directed to the broadcast address. |
| 1.3.6.1.2.1.16.1.1.1.7 | etherStatsMulticastPkts | 0 | 0 | The total number of good packets received that were directed to a multicast address. Note that this number does not include pack… |
| 1.3.6.1.2.1.16.1.1.1.8 | etherStatsCRCAlignErrors | 0 | 0 | The total number of packets received that had a length (excluding framing bits, but including FCS octets) of between 64 and 1518 o… |
| 1.3.6.1.2.1.16.1.1.1.9 | etherStatsUndersizePkts | 0 | 0 | The total number of packets received that were less than 64 octets long (excluding framing bits, but including FCS octets) and we… |
| 1.3.6.1.2.1.16.1.1.1.10 | etherStatsOversizePkts | 0 | 0 | The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets) and wer… |
| 1.3.6.1.2.1.16.1.1.1.11 | etherStatsFragments | 0 | 0 | The total number of packets received that were not an integral number of octets in length or that had a bad Frame Check Sequence … |
| 1.3.6.1.2.1.16.1.1.1.12 | etherStatsJabbers | 0 | 0 | The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and we… |
| 1.3.6.1.2.1.16.1.1.1.14 | etherStatsPkts64Octets | 0 | 0 | The total number of packets (including bad packets) received that were 64 octets in length (excluding framing bits but including … |
| 1.3.6.1.2.1.16.1.1.1.15 | etherStatsPkts65to127Octets | 0 | 0 | The total number of packets (including bad packets) received that were between 65 and 127 octets in length inclusive (excluding fr… |
| 1.3.6.1.2.1.16.1.1.1.16 | etherStatsPkts128to255Octets | 0 | 0 | The total number of packets (including bad packets) received that were between 128 and 255 octets in length inclusive (excluding f… |
| 1.3.6.1.2.1.16.1.1.1.17 | etherStatsPkts256to511Octets | 0 | 0 | The total number of packets (including bad packets) received that were between 256 and 511 octets in length inclusive (excluding f… |
| 1.3.6.1.2.1.16.1.1.1.18 | etherStatsPkts512to1023Octets | 0 | 0 | The total number of packets (including bad packets) received that were between 512 and 1023 octets in length inclusive (excluding … |
| 1.3.6.1.2.1.16.1.1.1.19 | etherStatsPkts1024to1518Octets | 0 | 0 | The total number of packets (including bad packets) received that were between 1024 and 1518 octets in length inclusive (excluding… |
| 1.3.6.1.2.1.16.1.1.1.20 | etherStatsOwner | 0 | 0 | The entity that configured this entry and is therefore using the resources assigned to it. |
| 1.3.6.1.2.1.16.1.1.1.21 | etherStatsStatus | 0 | 0 | The status of this etherStats entry. |
| 1.3.6.1.2.1.16.1.1.1.22 | ethStatsTxTotalErrors | 0 | 0 | ethStatsTxTotalErrors OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "Tx total errors" |
| 1.3.6.1.2.1.16.1.1.1.23 | ethStatsTimePeriod | 0 | 0 | ethStatsTimePeriod OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Time period over which stats w… |