All MIBs › GBNServiceRMON-MIB › rEtherHistoryCollisions
rEtherHistoryCollisions
Module: GBNServiceRMON-MIB
OID (symbolic): GBNServiceRMON-MIB::rEtherHistoryCollisions
OID (numeric): 1.3.6.1.4.1.13464.1.2.3.2.2.2.1.14
Node type: OBJECT-TYPE
Type: Counter
Access: read-only
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.
What is rEtherHistoryCollisions?
This counter estimates the collisions observed on the segment during this one sampling interval, the archived counterpart to rEtherStatsCollisions. Admins trend this across buckets to correlate collision spikes with specific times of day or events.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.13464.1.2.3.2.2.2.1.14 snmpwalk -v2c -c public <target> GBNServiceRMON-MIB::rEtherHistoryCollisions
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.13464.1.2.3.2.2.2.1.14.1 snmpget -v2c -c public <target> GBNServiceRMON-MIB::rEtherHistoryCollisions.1
SNMPv3 example:
snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> rEtherHistoryCollisions.1
Start monitoring Greentech network monitoring appliance/probe (RMON extension) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the GBNServiceRMON-MIB::rEtherHistoryCollisions OID value, configure state conditions and alerts, and monitor any Greentech network monitoring appliance/probe (RMON extension) from a single console.
OID Breakdown
Upper-level ancestors (11 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.13464 | admin | ADMIN-MASTER-MIB |
| 1.3.6.1.4.1.13464.1 | dataCom | ADMIN-MASTER-MIB |
| 1.3.6.1.4.1.13464.1.2 | gbn | ADMIN-MASTER-MIB |
| 1.3.6.1.4.1.13464.1.2.3 | gbnService | ADMIN-MASTER-MIB |
| 1.3.6.1.4.1.13464.1.2.3.2 | rmonMib | ADMIN-MASTER-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.13464.1.2.3.2.2 | rHistory | GBNServiceRMON-MIB |
| 1.3.6.1.4.1.13464.1.2.3.2.2.2 | rEtherHistoryTable | GBNServiceRMON-MIB |
| 1.3.6.1.4.1.13464.1.2.3.2.2.2.1 | rEtherHistoryEntry | GBNServiceRMON-MIB |
| 1.3.6.1.4.1.13464.1.2.3.2.2.2.1.14 | rEtherHistoryCollisions | GBNServiceRMON-MIB |