OPTIX-RMON-MIB :: etherHistoryCollisions

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › OPTIX-RMON-MIB › etherHistoryCollisions

etherHistoryCollisions

Module: OPTIX-RMON-MIB

OID (symbolic): OPTIX-RMON-MIB::etherHistoryCollisions

OID (numeric): 1.3.6.1.4.1.2011.2.25.3.35.20.2.1.14

Node type: OBJECT-TYPE

Type: Counter64

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 etherHistoryCollisions?

The best estimate of total collisions on this Ethernet segment during this specific historical sampling interval, with the same probe-location caveats described for the live etherStatsCollisions object (a repeater-port probe may see more collisions than a station probe on the same segment). Trending this across buckets over time reveals whether contention on the segment is getting better or worse.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.2011.2.25.3.35.20.2.1.14
snmpwalk -v2c -c public <target> OPTIX-RMON-MIB::etherHistoryCollisions

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.2011.2.25.3.35.20.2.1.14.1
snmpget -v2c -c public <target> OPTIX-RMON-MIB::etherHistoryCollisions.1

Start monitoring Huawei OptiX optical transport platform (RMON-style interface statistics/history) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the OPTIX-RMON-MIB::etherHistoryCollisions OID value, configure state conditions and alerts, and monitor any Huawei OptiX optical transport platform (RMON-style interface statistics/history) from a single console.

OID Breakdown

Upper-level ancestors (10 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.2011huaweiEXPERTV2-MIB
1.3.6.1.4.1.2011.2productsEXPERTV2-MIB
1.3.6.1.4.1.2011.2.25transmissionHUAWEI-MIB
1.3.6.1.4.1.2011.2.25.3optixCommonOPTIX-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.2011.2.25.3.35optixRmonMibOPTIX-RMON-MIB
1.3.6.1.4.1.2011.2.25.3.35.20historyOPTIX-RMON-MIB
1.3.6.1.4.1.2011.2.25.3.35.20.2etherHistoryTableOPTIX-RMON-MIB
1.3.6.1.4.1.2011.2.25.3.35.20.2.1etherHistoryEntryOPTIX-RMON-MIB
1.3.6.1.4.1.2011.2.25.3.35.20.2.1.14etherHistoryCollisionsOPTIX-RMON-MIB