The objects described here can be monitored with the IPHost Network Monitor.
You can start SNMP monitoring using free 30-day trial version of IPHost right now.
OID list for statistics collisions
- ether Statistics Collisions
- etherStatsCollisions 1.3.6.1.2.1.16.1.1.1.13 (defined in RMON-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. - dot3 Statistics Late Collisions
- dot3StatsLateCollisions 1.3.6.1.2.1.10.7.2.1.8 (defined in EtherLike-MIB)
detected on a particular interface later than one slotTime into the transmission of a packet. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. - dot3 Statistics Excessive Collisions
- dot3StatsExcessiveCollisions 1.3.6.1.2.1.10.7.2.1.9 (defined in EtherLike-MIB)
particular interface fails due to excessive collisions. This counter does not increment when the interface is operating in full-duplex mode. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime. - ether Statistics Collisions
- etherStatsCollisions 1.3.6.1.2.1.16.1.1.1.13 (defined in rfc1271)
The best estimate of the total number of collisions on this Ethernet segment. - dot3 Statistics Late Collisions
- dot3StatsLateCollisions 1.3.6.1.2.1.10.7.2.1.8 (defined in rfc1398)
The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet. Five hundred and twelve bit-times corresponds to 51.2 microseconds on a 10 Mbit/s system. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics. - dot3 Statistics Excessive Collisions
- dot3StatsExcessiveCollisions 1.3.6.1.2.1.10.7.2.1.9 (defined in rfc1398)
A count of frames for which transmission on a particular interface fails due to excessive collisions. - dot3 Statistics Late Collisions
- dot3StatsLateCollisions 1.3.6.1.2.1.10.7.2.1.8 (defined in rfc1650)
The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet. Five hundred and twelve bit-times corresponds to 51.2 microseconds on a 10 Mbit/s system. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics. - dot3 Statistics Excessive Collisions
- dot3StatsExcessiveCollisions 1.3.6.1.2.1.10.7.2.1.9 (defined in rfc1650)
A count of frames for which transmission on a particular interface fails due to excessive collisions. - ether Statistics Collisions
- etherStatsCollisions 1.3.6.1.2.1.16.1.1.1.13 (defined in rfc1757)
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. - dot3 Statistics Late Collisions
- dot3StatsLateCollisions 1.3.6.1.2.1.10.7.2.1.8 (defined in ETHER)
The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet. Five hundred and twelve bit-times corresponds to 51.2 microseconds on a 10 Mbit/s system. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics. - dot3 Statistics Excessive Collisions
- dot3StatsExcessiveCollisions 1.3.6.1.2.1.10.7.2.1.9 (defined in ETHER)
A count of frames for which transmission on a particular interface fails due to excessive collisions. - sfps Block Source Statistics Number Collisions
- sfpsBlockSourceStatsNumCollisions 1.3.6.1.4.1.52.4.2.4.2.2.14.6.2 (defined in ctron-sfps-base-mib)
The number of hash collisions resulting in a chain of nodes. (diagnostic only.) - sfps Topology Directory Statistics Node Collisions
- sfpsTopologyDirStatsNodeCollisions 1.3.6.1.4.1.52.4.2.4.2.2.3.11.20 (defined in ctron-sfps-directory-mib)
Total number of collisions - Node Table. - sfps Topology Directory Statistics Alias Collisions
- sfpsTopologyDirStatsAliasCollisions 1.3.6.1.4.1.52.4.2.4.2.2.3.11.22 (defined in ctron-sfps-directory-mib)
Total number of collisions - Alias Table.
