A3COM-HUAWEI-EPON-UNI-MIB :: h3cEponUniOutStatsCollisions

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsA3COM-HUAWEI-EPON-UNI-MIBh3cEponUniOutStatsCollisions

h3cEponUniOutStatsCollisions

Module: A3COM-HUAWEI-EPON-UNI-MIB

OID (symbolic): A3COM-HUAWEI-EPON-UNI-MIB::h3cEponUniOutStatsCollisions

OID (numeric): 1.3.6.1.4.1.43.45.1.10.2.42.5.1.2.1.17

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-only

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 could. 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 h3cEponUniOutStatsCollisions?

This metric estimates the total number of Ethernet collisions detected on the network segment. Collisions are normal in half-duplex mode but rare in full-duplex, indicating problematic shared media or misconfiguration. Zero collisions in duplex mode is expected; 100+ collisions suggests a duplex mismatch.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.43.45.1.10.2.42.5.1.2.1.17
snmpwalk -v2c -c public <target> A3COM-HUAWEI-EPON-UNI-MIB::h3cEponUniOutStatsCollisions

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.43.45.1.10.2.42.5.1.2.1.17.1
snmpget -v2c -c public <target> A3COM-HUAWEI-EPON-UNI-MIB::h3cEponUniOutStatsCollisions.1

Start monitoring H3C EPON ONU devices with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the A3COM-HUAWEI-EPON-UNI-MIB::h3cEponUniOutStatsCollisions OID value, configure state conditions and alerts, and monitor any H3C EPON ONU devices from a single console.

OID Breakdown

Upper-level ancestors (12 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.43a3ComA3COM-BRIDGE-R3-MIB
1.3.6.1.4.1.43.45jv_mibA3COM-HUAWEI-OID-MIB
1.3.6.1.4.1.43.45.1huaweiA3COM-HUAWEI-OID-MIB
1.3.6.1.4.1.43.45.1.10h3cA3COM-HUAWEI-OID-MIB
1.3.6.1.4.1.43.45.1.10.2h3cCommonA3COM-HUAWEI-OID-MIB
1.3.6.1.4.1.43.45.1.10.2.42h3cEponA3COM-HUAWEI-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.43.45.1.10.2.42.5h3cEponUniA3COM-HUAWEI-EPON-UNI-MIB
1.3.6.1.4.1.43.45.1.10.2.42.5.1h3cEponUniSysManA3COM-HUAWEI-EPON-UNI-MIB
1.3.6.1.4.1.43.45.1.10.2.42.5.1.2h3cEponUniCountTableA3COM-HUAWEI-EPON-UNI-MIB
1.3.6.1.4.1.43.45.1.10.2.42.5.1.2.1h3cEponUniCountEntryA3COM-HUAWEI-EPON-UNI-MIB
1.3.6.1.4.1.43.45.1.10.2.42.5.1.2.1.17h3cEponUniOutStatsCollisionsA3COM-HUAWEI-EPON-UNI-MIB