The best estimate of the total number of collisions
on this Ap64ethernet 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.
Parsed from file ap64Stats.mib.txt
Company: None
Module: AP64STATS-MIB
The best estimate of the total number of collisions
on this Ap64ethernet 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.
Parsed from file AP64STATS-MIB.mib
Module: AP64STATS-MIB
Vendor: ArrowPoint Communications Inc.
Module: AP64STATS-MIB
[Automatically extracted from oidview.com]
ap64etherStatsCollisions OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The best estimate of the total number of collisions on this Ap64ethernet 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." ::= { ap64etherStatsEntry 13 }
ap64etherStatsCollisions OBJECT-TYPE SYNTAX Counter64 MAX-ACCESS read-only STATUS current DESCRIPTION "The best estimate of the total number of collisions on this Ap64ethernet 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." ::= { ap64etherStatsEntry 13 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2467.1.44.4.1.1 | ap64etherStatsIndex | 0 | 0 | The value of this object uniquely identifies this etherStats entry. |
| 1.3.6.1.4.1.2467.1.44.4.1.2 | ap64etherStatsDataSource | 0 | 0 | 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.4.1.2467.1.44.4.1.3 | ap64etherStatsDropEvents | 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.4.1.2467.1.44.4.1.4 | ap64etherStatsOctets | 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.4.1.2467.1.44.4.1.5 | ap64etherStatsPkts | 0 | 0 | The total number of packets (including bad packets, broadcast packets, and multicast packets) received. |
| 1.3.6.1.4.1.2467.1.44.4.1.6 | ap64etherStatsBroadcastPkts | 0 | 0 | The total number of good packets received that were directed to the broadcast address. Note that this does not include multicast… |
| 1.3.6.1.4.1.2467.1.44.4.1.7 | ap64etherStatsMulticastPkts | 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.4.1.2467.1.44.4.1.8 | ap64etherStatsCRCAlignErrors | 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.4.1.2467.1.44.4.1.9 | ap64etherStatsUndersizePkts | 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.4.1.2467.1.44.4.1.10 | ap64etherStatsOversizePkts | 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.4.1.2467.1.44.4.1.11 | ap64etherStatsFragments | 0 | 0 | The total number of packets received that were less than 64 octets in length (excluding framing bits but including FCS octets) an… |
| 1.3.6.1.4.1.2467.1.44.4.1.12 | ap64etherStatsJabbers | 0 | 0 | The total number of packets received that were longer than 1518 octets (excluding framing bits, but including FCS octets), and ha… |
| 1.3.6.1.4.1.2467.1.44.4.1.14 | ap64etherStatsPkts64Octets | 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.4.1.2467.1.44.4.1.15 | ap64etherStatsPkts65to127Octets | 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.4.1.2467.1.44.4.1.16 | ap64etherStatsPkts128to255Octets | 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.4.1.2467.1.44.4.1.17 | ap64etherStatsPkts256to511Octets | 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.4.1.2467.1.44.4.1.18 | ap64etherStatsPkts512to1023Octets | 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.4.1.2467.1.44.4.1.19 | ap64etherStatsPkts1024to1518Octets | 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.4.1.2467.1.44.4.1.20 | ap64etherStatsOwner | 0 | 0 | The entity that configured this entry and is therefore using the resources assigned to it. |
| 1.3.6.1.4.1.2467.1.44.4.1.21 | ap64etherStatsStatus | 0 | 0 | The status of this ap64etherStats entry. |