RFC1398-MIB

MIB Reference — IPNetwork Monitor

All MIBsRFC1398-MIB

Category: IETF Standards

Description:

Defines Ethernet-like interface management objects for MAC statistics and error counters per RFC 1398.

Imported Objects

From RFC-1212

OBJECT-TYPE

From RFC1155-SMI

Counter
Gauge

From RFC1213-MIB

transmission

What Is RFC1398-MIB?

RFC1398-MIB, widely known as the EtherLike-MIB, is a vendor-neutral, IETF standards-based module defining management objects for Ethernet-like (CSMA/CD) network interfaces. It exposes MAC-layer statistics per interface such as alignment errors, FCS (frame check sequence) errors, single/multiple collision frame counts, deferred transmissions, and carrier-sense errors, extending the base interfaces group. It is a link-health hardware-monitoring MIB — administrators use its per-interface error and collision counters to detect duplex mismatches, bad cabling, or a failing NIC/switch port well before an interface goes fully down. It complements and is indexed against the standard IF-MIB (ifTable), sharing ifIndex values with each Ethernet interface. It's deployed on essentially every Ethernet-capable router, switch, and host that supports SNMP. Engineers implementing or auditing this functionality typically reference the RFC1398-MIB RFC/standard documentation for the authoritative specification.

IPNetwork Monitor allows you to monitor SNMP objects defined in RFC1398-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

What Can Be Monitored

  • FCS/checksum errors
  • alignment errors
  • single/multiple collision frame counts
  • deferred transmissions
  • carrier-sense errors

Supported Devices

  • vendor-neutral, standards-based MIB, not tied to a specific manufacturer — applies to any Ethernet-capable network device

Monitoring Examples

The dot3StatsTable/dot3StatsEntry rows would be polled per Ethernet interface for FCS and alignment error counts; a rising count on one port while others stay flat typically points to a bad cable or transceiver on that specific link. Climbing single/multiple collision-frame counts alongside deferred-transmission counts on a port is a classic signature of a duplex mismatch between a switch and its connected device.

OIDs
OID symbolicOID numericTypeAccessDescription
dot31.3.6.1.2.1.10.7
dot3StatsTable1.3.6.1.2.1.10.7.2not-accessibleStatistics for a collection of ethernet-like interfaces attached to a particular system.
dot3StatsEntry1.3.6.1.2.1.10.7.2.1not-accessibleStatistics for a particular interface to an ethernet-like medium.
INT dot3StatsIndex1.3.6.1.2.1.10.7.2.1.1INTEGERread-onlyAn index value that uniquely identifies an interface to an ethernet-like medium. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
CTR dot3StatsAlignmentErrors1.3.6.1.2.1.10.7.2.1.2Counterread-onlyA count of frames received on a particular interface that are not an integral number of octets in length and do not pass the FCS check. The count represented by an instance of this object is incremented when the alignmentError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.
CTR dot3StatsFCSErrors1.3.6.1.2.1.10.7.2.1.3Counterread-onlyA count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS check. The count represented by an instance of this object is incremented when the frameCheckError status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.
CTR dot3StatsSingleCollisionFrames1.3.6.1.2.1.10.7.2.1.4Counterread-onlyA count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision. A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts or ifOutNUcastPkts object and is not counted by the corresponding instance of the dot3StatsMultipleCollisionFrames object.
CTR dot3StatsMultipleCollisionFrames1.3.6.1.2.1.10.7.2.1.5Counterread-onlyA count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collision. A frame that is counted by an instance of this object is also counted by the corresponding instance of either the ifOutUcastPkts or ifOutNUcastPkts object and is not counted by the corresponding instance of the dot3StatsSingleCollisionFrames object.
CTR dot3StatsSQETestErrors1.3.6.1.2.1.10.7.2.1.6Counterread-onlyA count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface. The SQE TEST ERROR message is defined in section 7.2.2.2.4 of ANSI/IEEE 802.3-1985 and its generation is described in section 7.2.4.6 of the same document.
CTR dot3StatsDeferredTransmissions1.3.6.1.2.1.10.7.2.1.7Counterread-onlyA count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. The count represented by an instance of this object does not include frames involved in collisions.
CTR dot3StatsLateCollisions1.3.6.1.2.1.10.7.2.1.8Counterread-onlyThe number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a packet. Five hundred and twelve bit-times corresponds to 51.2 microseconds on a 10 Mbit/s system. A (late) collision included in a count represented by an instance of this object is also considered as a (generic) collision for purposes of other collision-related statistics.
CTR dot3StatsExcessiveCollisions1.3.6.1.2.1.10.7.2.1.9Counterread-onlyA count of frames for which transmission on a particular interface fails due to excessive collisions.
CTR dot3StatsInternalMacTransmitErrors1.3.6.1.2.1.10.7.2.1.10Counterread-onlyA 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.
CTR dot3StatsCarrierSenseErrors1.3.6.1.2.1.10.7.2.1.11Counterread-onlyThe number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particular interface. The count represented by an instance of this object is incremented at most once per transmission attempt, even if the carrier sense condition fluctuates during a transmission attempt.
CTR dot3StatsFrameTooLongs1.3.6.1.2.1.10.7.2.1.13Counterread-onlyA count of frames received on a particular interface that exceed the maximum permitted frame size. The count represented by an instance of this object is incremented when the frameTooLong status is returned by the MAC service to the LLC (or other MAC user). Received frames for which multiple error conditions obtain are, according to the conventions of IEEE 802.3 Layer Management, counted exclusively according to the error status presented to the LLC.
CTR dot3StatsInternalMacReceiveErrors1.3.6.1.2.1.10.7.2.1.16Counterread-onlyA count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A frame is only counted by an instance of this object if it is not counted by the corresponding instance of either the dot3StatsFrameTooLongs object, the dot3StatsAlignmentErrors object, or the dot3StatsFCSErrors 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 receive errors on a particular interface that are not otherwise counted.
dot3CollTable1.3.6.1.2.1.10.7.5not-accessibleA collection of collision histograms for a particular set of interfaces.
dot3CollEntry1.3.6.1.2.1.10.7.5.1not-accessibleA cell in the histogram of per-frame collisions for a particular interface. An instance of this object represents the frequency of individual MAC frames for which the transmission (successful or otherwise) on a particular interface is accompanied by a particular number of media collisions.
INT dot3CollIndex1.3.6.1.2.1.10.7.5.1.1INTEGERread-onlyThe index value that uniquely identifies the interface to which a particular collision histogram cell pertains. The interface identified by a particular value of this index is the same interface as identified by the same value of ifIndex.
INT dot3CollCount1.3.6.1.2.1.10.7.5.1.2INTEGERread-onlyThe number of per-frame media collisions for which a particular collision histogram cell represents the frequency on a particular interface.
CTR dot3CollFrequencies1.3.6.1.2.1.10.7.5.1.3Counterread-onlyA count of individual MAC frames for which the transmission (successful or otherwise) on a particular interface is accompanied by a particular number of media collisions.
dot3Tests1.3.6.1.2.1.10.7.6
dot3TestTdr1.3.6.1.2.1.10.7.6.1
dot3Errors1.3.6.1.2.1.10.7.7
dot3ErrorInitError1.3.6.1.2.1.10.7.7.1
dot3ErrorLoopbackError1.3.6.1.2.1.10.7.7.2
dot3ChipSets1.3.6.1.2.1.10.7.8
dot3ChipSetAMD1.3.6.1.2.1.10.7.8.1
dot3ChipSetAMD79901.3.6.1.2.1.10.7.8.1.1
dot3ChipSetAMD799001.3.6.1.2.1.10.7.8.1.2
dot3ChipSetIntel1.3.6.1.2.1.10.7.8.2
dot3ChipSetIntel825861.3.6.1.2.1.10.7.8.2.1
dot3ChipSetIntel825961.3.6.1.2.1.10.7.8.2.2
dot3ChipSetSeeq1.3.6.1.2.1.10.7.8.3
dot3ChipSetSeeq80031.3.6.1.2.1.10.7.8.3.1
dot3ChipSetNational1.3.6.1.2.1.10.7.8.4
dot3ChipSetNational83901.3.6.1.2.1.10.7.8.4.1
dot3ChipSetNationalSonic1.3.6.1.2.1.10.7.8.4.2
dot3ChipSetFujitsu1.3.6.1.2.1.10.7.8.5
dot3ChipSetFujitsu869501.3.6.1.2.1.10.7.8.5.1
dot3ChipSetFujitsu869601.3.6.1.2.1.10.7.8.5.2

RFC description

Defined in RFC 1398, provides SNMP MIB for managing and monitoring SNMP protocol statistics and operations.

Start monitoring vendor-neutral, standards-based EtherLike-MIB, any Ethernet-capable network device with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download RFC1398-MIB