Definitions of Managed Objects for the Ethernet-Like Interface Types
obsoleted by
- rfc-1623 — Definitions of Managed Objects for the Ethernet-like Interface Types
obsoletes
- rfc-1284 — Definitions of Managed Objects for the Ethernet-like Interface Types
Extracted elements (26)
Chipset OIDs for vendors not enumerated in this MIB should be assigned within the enterprise registration tree per RFC 1155, rather than requiring updates to this document for each new chipset.
Multiple error conditions on a single received frame are counted exclusively according to the first error status presented to the LLC, following the conventions of IEEE 802.3 Layer Management. This prevents double-counting across error counters.
The Generic Ethernet-like group (dot3Index, dot3InitializeMac, dot3MacSubLayerStatus, dot3MulticastReceiveStatus, dot3TxEnabled, dot3TestTdrValue) and objects dot3StatsInRangeLengthErrors and dot3StatsOutOfRangeLengthFields were deprecated and removed based on implementation experience presented at the San Diego IETF meeting.
Attributes already represented in MIB-II (RFC 1213) or the Generic Interface Extensions MIB (RFC 1229) — such as octet counts, frame counts, promiscuous status, MAC address, and multicast information — are not redundantly defined in this MIB to avoid duplication.
The relationship between an ethernet-like interface and an MIB-II ifIndex is one-to-one; the same ifIndex value directly indexes the objects defined in this MIB.
Implementation of the Ethernet-like Collision Statistics Group (dot3CollTable) is optional; it is appropriate for systems that have the necessary metering capability.
Implementation of the Ethernet-like Statistics Group (dot3StatsTable) is mandatory for all ethernet-like interfaces.
dot3ChipSets provides OBJECT IDENTIFIERs identifying specific 802.3 MAC hardware chipsets, including AMD 7990/79900, Intel 82586/82596, Seeq 8003, National 8390/SONIC, and Fujitsu 86950/86960. Used as values for ifExtnsChipSet from RFC 1229.
dot3CollTable provides a collision histogram indexed by interface (dot3CollIndex) and per-frame collision count (dot3CollCount, range 1..16). dot3CollFrequencies gives the count of frames transmitted with exactly that many collisions.
dot3ErrorInitError and dot3ErrorLoopbackError are OBJECT IDENTIFIERs used as values for ifExtnsTestCode (RFC 1229) to indicate, respectively, failure to initialize the MAC chip and failure to receive expected loopback data during a test.
dot3StatsAlignmentErrors counts frames received that are not an integral number of octets and fail the FCS check. Incremented when the alignmentError status is returned by the MAC to the LLC; frames with multiple error conditions are counted exclusively by the first error status presented.
dot3StatsCarrierSenseErrors counts times the carrier sense condition was lost or never asserted during a transmission attempt. The counter is incremented at most once per transmission attempt regardless of how many times carrier sense fluctuates.
dot3StatsDeferredTransmissions counts frames whose first transmission attempt is delayed because the medium is busy. Frames involved in collisions are not included in this count.
dot3StatsExcessiveCollisions counts frames for which transmission fails due to excessive collisions.
dot3StatsFCSErrors counts frames received that are an integral number of octets but fail the FCS check. Incremented when the frameCheckError status is returned by the MAC to the LLC.
dot3StatsFrameTooLongs counts frames received that exceed the maximum permitted frame size, incremented when the frameTooLong status is returned by the MAC to the LLC.
dot3StatsIndex uniquely identifies an ethernet-like interface; its value is identical to the corresponding ifIndex value from MIB-II.
dot3StatsInternalMacReceiveErrors counts frames for which reception fails due to an internal MAC sublayer receive error, excluding frames already counted by dot3StatsFrameTooLongs, dot3StatsAlignmentErrors, or dot3StatsFCSErrors. The precise meaning is implementation-specific.
dot3StatsInternalMacTransmitErrors counts frames for which transmission fails due to an internal MAC sublayer transmit error, excluding frames already counted by dot3StatsLateCollisions, dot3StatsExcessiveCollisions, or dot3StatsCarrierSenseErrors. The precise meaning is implementation-specific.
dot3StatsLateCollisions counts collisions detected later than 512 bit-times (51.2 microseconds on a 10 Mbit/s system) into a transmission. Late collisions are also counted in generic collision statistics.
dot3StatsMultipleCollisionFrames counts successfully transmitted frames for which transmission was inhibited by more than one collision. Mutually exclusive with dot3StatsSingleCollisionFrames.
dot3StatsSingleCollisionFrames counts successfully transmitted frames for which transmission was inhibited by exactly one collision. Such frames are also counted in ifOutUcastPkts or ifOutNUcastPkts and are mutually exclusive with dot3StatsMultipleCollisionFrames.
dot3StatsSQETestErrors counts times the SQE TEST ERROR message is generated by the PLS sublayer, as defined in ANSI/IEEE 802.3-1985 section 7.2.2.2.4.
dot3TestTdr is a TDR (Time-domain Reflectometry) test identifier under dot3Tests. On completion, the result is the time interval in 10 MHz ticks (100 ns units) between the start of TDR transmission and detection of a collision or carrier deassertion. Not applicable to 10BaseT or 10BaseF interfaces.
The full-duplex loopback test (testFullDuplexLoopBack, defined in RFC 1229) configures the MAC chip and executes an internal loopback test of memory and MAC logic. It can only run while the interface is offline, and the interface should remain offline after test completion.
Security issues are not discussed in this memo.