GBNDeviceSWAPI-MIB :: sEtherStatsCollisions

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › GBNDeviceSWAPI-MIB › sEtherStatsCollisions

sEtherStatsCollisions

Module: GBNDeviceSWAPI-MIB

OID (symbolic): GBNDeviceSWAPI-MIB::sEtherStatsCollisions

OID (numeric): 1.3.6.1.4.1.13464.1.2.2.2.5.1.1.1.13

Node type: OBJECT-TYPE

Type: Counter32

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

Estimates Ethernet collisions seen on this segment. On a modern full-duplex switched port this should stay at zero, so any nonzero value flags a stuck half-duplex link or a duplex mismatch.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.13464.1.2.2.2.5.1.1.1.13
snmpwalk -v2c -c public <target> GBNDeviceSWAPI-MIB::sEtherStatsCollisions

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.13464.1.2.2.2.5.1.1.1.13.1
snmpget -v2c -c public <target> GBNDeviceSWAPI-MIB::sEtherStatsCollisions.1

Start monitoring Ethernet switch driver/OEM switch silicon (100Mb/1000Mb queue scheduling) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the GBNDeviceSWAPI-MIB::sEtherStatsCollisions OID value, configure state conditions and alerts, and monitor any Ethernet switch driver/OEM switch silicon (100Mb/1000Mb queue scheduling) 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.13464adminADMIN-MASTER-MIB
1.3.6.1.4.1.13464.1dataComADMIN-MASTER-MIB
1.3.6.1.4.1.13464.1.2gbnADMIN-MASTER-MIB
1.3.6.1.4.1.13464.1.2.2gbnDeviceADMIN-MASTER-MIB
Numeric OIDNameModule
1.3.6.1.4.1.13464.1.2.2.2bcmSwapiGBNDeviceSWAPI-MIB
1.3.6.1.4.1.13464.1.2.2.2.5sRFC1757MIBGBNDeviceSWAPI-MIB
1.3.6.1.4.1.13464.1.2.2.2.5.1sRFC1757StatisticsGBNDeviceSWAPI-MIB
1.3.6.1.4.1.13464.1.2.2.2.5.1.1sEtherStatsTableGBNDeviceSWAPI-MIB
1.3.6.1.4.1.13464.1.2.2.2.5.1.1.1sEtherStatsEntryGBNDeviceSWAPI-MIB
1.3.6.1.4.1.13464.1.2.2.2.5.1.1.1.13sEtherStatsCollisionsGBNDeviceSWAPI-MIB