INTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB :: switchEtherStatsCollisions

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › INTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB › switchEtherStatsCollisions

switchEtherStatsCollisions

Module: INTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB

OID (symbolic): INTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB::switchEtherStatsCollisions

OID (numeric): 1.3.6.1.4.1.343.2.19.1.2.10.203.5.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 switchEtherStatsCollisions?

The best estimate of total collisions detected on this Ethernet segment; the exact value depends on where the probe sits (e.g. on a repeater port versus an end station) per the IEEE 802.3 detection rules cited in the DESCRIPTION. On a modern full-duplex switch port this should normally read zero, so any nonzero value flags a duplex or hub-mode issue.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.343.2.19.1.2.10.203.5.1.13
snmpwalk -v2c -c public <target> INTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB::switchEtherStatsCollisions

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.343.2.19.1.2.10.203.5.1.13.1
snmpget -v2c -c public <target> INTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB::switchEtherStatsCollisions.1

Start monitoring Intel Multi-Flex Server blade chassis (embedded switch fabric module) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the INTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB::switchEtherStatsCollisions OID value, configure state conditions and alerts, and monitor any Intel Multi-Flex Server blade chassis (embedded switch fabric module) 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.343intelAOLAN-MIB
1.3.6.1.4.1.343.2productsAOLAN-MIB
1.3.6.1.4.1.343.2.19modularsystemsINTELCORPORATION-MULTI-FLEX-SERVER-REG
1.3.6.1.4.1.343.2.19.1multiFlexServerINTELCORPORATION-MULTI-FLEX-SERVER-REG
1.3.6.1.4.1.343.2.19.1.2componentsINTELCORPORATION-MULTI-FLEX-SERVER-REG
1.3.6.1.4.1.343.2.19.1.2.10chassisINTELCORPORATION-MULTI-FLEX-SERVER-MIB
Numeric OIDNameModule
1.3.6.1.4.1.343.2.19.1.2.10.203switchesINTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB
1.3.6.1.4.1.343.2.19.1.2.10.203.5switchEtherStatsTableINTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB
1.3.6.1.4.1.343.2.19.1.2.10.203.5.1switchEtherStatsEntryINTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB
1.3.6.1.4.1.343.2.19.1.2.10.203.5.1.13switchEtherStatsCollisionsINTELCORPORATION-MULTI-FLEX-SERVER-SWITCH-MIB