EtherLike-MIB :: dot3StatsInternalMacTransmitErrors

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsEtherLike-MIBdot3StatsInternalMacTransmitErrors

dot3StatsInternalMacTransmitErrors

Module: EtherLike-MIB

OID (symbolic): EtherLike-MIB::dot3StatsInternalMacTransmitErrors

OID (numeric): 1.3.6.1.2.1.10.7.2.1.10

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsLateCollisions object, the dot3StatsExcessiveCollisions object, or the dot3StatsCarrierSenseErrors object.

The precise meaning of the count represented by an instance of this object is implementation- specific. In particular, an instance of this object may represent a count of transmission errors on a particular interface that are not otherwise counted.

For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsInternalMacTransmitErrors object for 10 Gb/s or faster interfaces.

Discontinuities in the value of this counter can

occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime.

What is dot3StatsInternalMacTransmitErrors?

This counter counts frames that failed to transmit on this interface because of an internal MAC-sublayer transmit error, excluding any failures already counted as late collisions, excessive collisions, or carrier sense errors. Admins treat a nonzero or growing count here as a catch-all sign of Ethernet chip-level transmit trouble that isn't explained by the more specific collision-related counters. For example, if this counter climbs on a port with no matching rise in collision counters, it suggests a hardware-level MAC fault rather than a cabling or duplex mismatch issue.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.10.7.2.1.10
snmpwalk -v2c -c public <target> EtherLike-MIB::dot3StatsInternalMacTransmitErrors

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.10.7.2.1.10.1
snmpget -v2c -c public <target> EtherLike-MIB::dot3StatsInternalMacTransmitErrors.1

Start monitoring Vendor-neutral Ethernet interface, any manufacturer (IEEE 802.3 EtherLike statistics) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EtherLike-MIB::dot3StatsInternalMacTransmitErrors OID value, configure state conditions and alerts, and monitor any Vendor-neutral Ethernet interface, any manufacturer (IEEE 802.3 EtherLike statistics) from a single console.

OID Breakdown

Upper-level ancestors (7 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.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
1.3.6.1.2.1.10transmissionCHECKPOINT-MIB-2
Numeric OIDNameModule
1.3.6.1.2.1.10.7dot3EtherLike-MIB
1.3.6.1.2.1.10.7.2dot3StatsTableEtherLike-MIB
1.3.6.1.2.1.10.7.2.1dot3StatsEntryEtherLike-MIB
1.3.6.1.2.1.10.7.2.1.10dot3StatsInternalMacTransmitErrorsEtherLike-MIB