RFC 2358
Definitions of Managed Objects for the Ethernet-like Interface Types
RFC 2358: Definitions of Managed Objects for the Ethernet-like Interface Types 🎀
Network Working Group 🌸 This is the group that put it out.
Authors: J. Flick (Hewlett-Packard Company) and J. Johnson (RedBack Networks) 💖
Category: Standards Track ✨ This is a real standard, not just an idea floating around.
Date: June 1998 🦋
Obsoletes: RFC 1650 💅 This one replaces it. It doesn't list anything it updates.
Status of this Memo ✨
Okay so this doc is an Internet standards track protocol for the Internet community, and it's asking for discussion and suggestions for improvements 🫶 If you want to know where it stands in the official lineup, check the current edition of the "Internet Official Protocol Standards" (STD 1). Distribution of this memo is unlimited, so share it with everyone 🌈
Copyright Notice 💜
Copyright (C) The Internet Society (1998). All Rights Reserved. 🎀
Abstract 🦋
This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. It obsoletes RFC 1650 "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2" 💅 It also extends that spec by adding management info for 100 Mb/s Ethernet interfaces. Iconic upgrade, no cap 🔥
Ethernet tech, as defined by the 802.3 Working Group of the IEEE, keeps evolving. We're getting faster speeds, new cabling and interfaces, and new features ✨ That evolution might mean the managed objects need changes too, so they reflect the new stuff. This document reflects one stage of Ethernet's evolution, the way the other docs from this working group do. Later on, this document might get revised, or the Ethernet Interfaces and Hub MIB Working Group might issue new documents, so the MIB keeps up with Ethernet 💖
Table of Contents 🧚
1. Introduction ................................................ 2
2. The SNMP Network Management Framework ...................... 2
2.1. Object Definitions ....................................... 3
3. Overview ................................................... 3
3.1. Relation to MIB-2 ........................................ 4
3.2. Relation to the Interfaces MIB ........................... 4
3.2.1. Layering Model ......................................... 4
3.2.2. Virtual Circuits ....................................... 4
3.2.3. ifTestTable ............................................ 5
3.2.4. ifRcvAddressTable ...................................... 5
3.2.5. ifPhysAddress .......................................... 5
3.2.6. ifType ................................................. 6
3.2.7. Specific Interface MIB Objects ......................... 7
3.3. Relation to the 802.3 MAU MIB ............................ 10
3.4. Mapping of IEEE 802.3 Managed Objects .................... 10
4. Definitions ................................................ 11
5. Intellectual Property ...................................... 34
6. Acknowledgements ........................................... 34
7. References ................................................. 35
8. Security Considerations .................................... 36
9. Authors' Addresses ......................................... 37
A. Change Log ................................................. 38
B. Full Copyright Statement ................................... 391. Introduction ✨
Okay bestie, this memo defines a piece of the Management Information Base (MIB) for network management protocols in the Internet community 💅 Specifically, it covers objects for managing ethernet-like interfaces.
This memo also includes a MIB module, and that module extends the list of managed objects from the earlier version of this MIB: RFC1650 [11] 🌸
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [13] 🫶
2. The SNMP Network Management Framework 🎀
The SNMP Network Management Framework is made of several components. For this spec, the parts that matter are the SMI and related documents [2, 3, 4]. They define how objects get described and named for management purposes 💖
The Framework lets people define new objects for experimentation and evaluation 🧪✨
2.1. Object Definitions 🦋
Managed objects get accessed through a virtual information store called the Management Information Base, or MIB 💜 Objects in the MIB are defined with a subset of Abstract Syntax Notation One (ASN.1) [1], the one defined in the SMI [2]. Each object type gets named by an OBJECT IDENTIFIER, which is an administratively assigned name 🌈 The object type plus an object instance uniquely identifies one specific instantiation of the object. For human convenience, people often use a textual string, called the descriptor, to refer to the object type 💅
3. Overview 🧚
Instances of these object types represent attributes of an interface to an ethernet-like communications medium. Right now, ethernet-like media are identified by these values of the ifType object in the Interfaces MIB [12] 👑
ethernetCsmacd(6)
iso88023Csmacd(7)
starLan(11)The definitions here are based on the IEEE 802.3 Layer Management Specification [5], as originally interpreted by Frank Kastenholz then of Interlan in [7] ✨ If you're implementing these MIB objects, note that the IEEE document explicitly describes, in Pascal pseudocode, when, where, and how various MAC attributes are measured 🤓 It also describes the effects of MAC actions that can be invoked by manipulating instances of the MIB objects defined here. Main character energy 💅
Some of the attributes defined in [5] are already represented by previously defined objects in MIB-2 [16] or in the Interfaces MIB [12]. Those attributes are not represented again by objects in this memo, because that would be redundant 🙈 Other memos define objects for attributes like the number of octets transmitted or received on a particular interface, the number of frames transmitted or received on a particular interface, the promiscuous status of an interface, the MAC address of an interface, and multicast information associated with an interface 🦋
3.1. Relation to MIB-2 🌸
This section only applies when this MIB is used together with the "old" (RFC 1213) [16] interface group 💖
An ethernet-like interface and an interface in the context of the Internet-standard MIB have a one-to-one relationship. So the value of an ifIndex object instance can be used directly to identify the matching instances of the objects defined here 🫶
For agents that implement the (now deprecated) ifSpecific object, an instance of that object associated with an ethernet-like interface has this OBJECT IDENTIFIER value:
dot3 OBJECT IDENTIFER ::= { transmission 7 }3.2. Relation to the Interfaces MIB 🧚
The Interface MIB [12] requires that any MIB which is an adjunct of the Interface MIB clarify specific areas within the Interface MIB 💅 Those areas were left vague on purpose in the Interface MIB, so it wouldn't over-constrain the MIB and rule out managing certain media types.
Section 3.3 of [12] lists several areas a media-specific MIB has to clarify. Each one gets its own subsection below. If you want the general intent behind these areas, go read [12] 📚✨
3.2.1. Layering Model 🎀
This MIB doesn't do layering. There are no sublayers 🌈
EDITOR'S NOTE: One could foresee the development of an 802.2 and enet-transceiver MIB. They could be higher and lower sublayers, respectively. All that THIS document should do is allude to those possibilities and urge the implementor to be aware of them, and to know that they may have requirements which supersede the requirements in this document.
3.2.2. Virtual Circuits 💜
This medium doesn't support virtual circuits, so this area doesn't apply to this MIB 🙅♀️
3.2.3. ifTestTable 🍓
This MIB defines two tests for media that are instrumented with it: TDR and Loopback 🧪 Implementing these tests is not required. Lots of common interface chips don't support one or both of them 💀
These two tests are provided as a convenience, so there's one common way to invoke them ✨
Standard MIBs don't include objects to hold the results of the TDR test. Any needed objects MUST be provided in the vendor-specific MIB 🫶
Heads up: the ifTestTable is now deprecated 😭 Work is underway on a replacement MIB for system and interface testing, and the tests defined here are expected to be usable in that replacement MIB 🔥
3.2.4. ifRcvAddressTable 🦋
This table holds all IEEE 802.3 addresses (unicast, multicast, and broadcast) that this interface will receive packets for and forward up to a higher-layer entity for local consumption 💖 The address format, in ifRcvAddressAddress, is the same as for ifPhysAddress.
If the interface is part of a MAC bridge, this table doesn't include unicast addresses that are accepted for possible forwarding out some other port 🌸 This table is explicitly not meant to be a bridge address filtering mechanism. Not me being the bridge filter 🙈
3.2.5. ifPhysAddress 🌈
This object holds the IEEE 802.3 address that gets placed in the source-address field of any Ethernet, Starlan, or IEEE 802.3 frames that originate at this interface 🫶 Usually it's kept in ROM on the interface hardware. Some systems may set this address via software 💅
If a system has several of these addresses, the designer has a tougher choice 😤 The address picked should be the one most likely to be useful to network management, like the address placed in ARP responses for systems that are mainly IP systems 🧠
If the designer truly can't choose, using the factory-provided ROM address is suggested ✨
If the address can't be determined, an octet string of zero length should be returned 🙃
The address is stored in binary in this object, in "canonical" bit order. That means the Group Bit sits as the low-order bit of the first octet. So the first byte of a multicast address would have the bit 0x01 set 💖
3.2.6. ifType 🦋
okay bestie, this MIB applies to interfaces that have any of these ifType values 👀
ethernetCsmacd(6)
iso88023Csmacd(7)
starLan(11)so the vibe is that every Ethernet-like interface is RECOMMENDED to use ethernetCsmacd(6), no matter what speed it's running or what link-layer encapsulation it's using 💅 iso88023Csmacd(7) and starLan(11) are still supported for backwards compatability 🕰️
there are two other interface types in the IANAifType-MIB for 100 Mbit Ethernet: fastEther(62) and fastEtherFX(69) 🚗 but this doc is literally like "an Ethernet is an Ethernet" 😤 so Ethernet interfaces SHOULD always have the same value of ifType. if you wanna know which flavor of Ethernet an interface is running, check ifSpeed in the Interfaces MIB and ifMauType in the 802.3 MAU MIB 🔍 an Ethernet-like interface SHOULD NOT use the fastEther(62) or fastEtherFX(69) ifTypes, periodt 💀
interfaces with any of the supported ifType values map to the EtherLike-MIB the same way ✨ which compliance statement an interface should implement depends on the maximum speed it supports. the EtherLike-MIB etherCompliance compliance statement applies to all Ethernet-like interfaces whose maximum supported speed is 10 Mbit/sec or less. there are no implementation differences 🙌 and the EtherLike-MIB ether100MbsCompliance compliance statement applies to all Ethernet-like interfaces whose maximum supported speed is 100Mbit/sec.
okay the main character rule 👑 an interface that is capable of operating at 100Mbit/sec MUST implement the ether100MbsCompliance compliance statement, even if it's currently running at a lower speed. the counters in that statement that only apply to 100 Mbit interfaces would just not increment while the interface is running slower 🌸 no drama, just vibes.
3.2.7. Specific Interface MIB Objects 📋
this table is basically your cheat sheet for applying the interface group objects to ethernet-like media 🍓
Object
ifIndex Each ethernet-like interface is
represented by an ifEntry. The
dot3StatsTable in this MIB module is
indexed by dot3StatsIndex. The interface
identified by a particular value of
dot3StatsIndex is the same interface as
identified by the same value of ifIndex.
ifDescr Refer to [12].
ifType Refer to section 3.2.6.
ifMtu 1500 octets.
ifSpeed The current operational speed of the
interface in bits per second. For
current ethernet-like interfaces, this
will be equal to 1,000,000 (1 million),
10,000,000 (10 million), or 100,000,000
(100 million). If the interface
implements auto-negotiation,
auto-negotiation is enabled for this
interface, and the interface has not yet
negotiated to an operational speed, this
object SHOULD reflect the maximum speed
supported by the interface. Note that
this object MUST NOT indicate a doubled
value when operating in full-duplex
mode. It MUST indicate the correct
line speed regardless of the current
duplex mode. The correct object to use
to determine the duplex mode of the
interface is the ifMauType object in the
802.3 MAU MIB.
ifPhysAddress Refer to section 3.2.5.
ifAdminStatus Write access is not required. Support
for 'testing' is not required.
ifOperStatus The operational state of the interface.
Support for 'testing' is not required.
The value 'dormant' has no meaning for
an ethernet-like interface.
ifLastChange Refer to [12].
ifInOctets The number of octets in valid MAC frames
received on this interface, including
the MAC header and FCS.
ifInUcastPkts Refer to [12].
ifInDiscards Refer to [12].
ifInErrors The sum for this interface of
dot3StatsAlignmentErrors,
dot3StatsFCSErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors and
dot3StatsSymbolErrors.
ifInUnknownProtos Refer to [12].
ifOutOctets The number of octets transmitted in
valid MAC frames on this interface,
including the MAC header and FCS.
ifOutUcastPkts Refer to [12].
ifOutDiscards Refer to [12].
ifOutErrors The sum for this interface of:
dot3StatsSQETestErrors,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors and
dot3StatsCarrierSenseErrors.
ifName Locally-significant textual name for the
interface (e.g. lan0).
ifInMulticastPkts Refer to [12].
ifInBroadcastPkts Refer to [12].
ifOutMulticastPkts Refer to [12].
ifOutBroadcastPkts Refer to [12].
ifHCInOctets 64-bit versions of counters. Required
ifHCOutOctets for ethernet-like interfaces that are
capable of operating at 20Mbit/sec or
faster, even if the interface is
currently operating at less than
20Mbit/sec.
ifHCInUcastPkts 64-bit versions of packet counters.
ifHCInMulticastPkts Support for these counters is not
ifHCInBroadcastPkts required for the interface types
ifHCOutUcastPkts supported by this MIB. They are only
ifHCOutMulticastPkts required for interfaces capable of
ifHCOutBroadcastPkts operating at 640Mbit/sec or faster.
Note that a future revision of this
document may support faster interfaces,
and therefore may require support for
these counters.
ifLinkUpDownTrapEnable Refer to [12]. Default is 'enabled'
ifHighSpeed The current operational speed of the
interface in millions of bits per
second. For current ethernet-like
interfaces, this will be equal to 1, 10,
or 100. If the interface implements
auto-negotiation, auto-negotiation is
enabled for this interface, and the
interface has not yet negotiated to an
operational speed, this object SHOULD
reflect the maximum speed supported by
the interface. Note that this object
MUST NOT indicate a doubled value when
operating in full-duplex mode. It MUST
indicate the correct line speed
regardless of the current duplex mode.
The correct object to use to determine
the duplex mode of the interface is the
ifMauType object in the 802.3 MAU MIB.
ifPromiscuousMode Refer to [12].
ifConnectorPresent This will normally be 'true'.
ifAlias Refer to [12].
ifCounterDiscontinuityTime Refer to [12].
ifStackHigherLayer Refer to section 3.2.1.
ifStackLowerLayer
ifStackStatus
ifRcvAddressAddress Refer to section 3.2.4.
ifRcvAddressStatus
ifRcvAddressType3.3. Relation to the 802.3 MAU MIB 🎀
last one, and it's a big one 😤 Support for the mauModIfCompl compliance statement of the MAU-MIB [14] is REQUIRED for Ethernet-like interfaces, no debate. this MIB is needed so apps can figure out the current MAU type the interface is using 🔌 and the MAU type tells you not just the media type, but also whether the interface is in half-duplex or full-duplex mode 🌓 if you implement this MIB without the MAU-MIB, apps are left with no standard way to determine the duplex mode of the interface, and that is so not it 😭
3.4. Mapping of IEEE 802.3 Managed Objects ✨
okay bestie, this table is basically a cheat sheet 🍓 It lines up each IEEE 802.3 managed object with the SNMP object that covers it. Some rows point to the IF-MIB, and some point to objects in this MIB. 💅
IEEE 802.3 Managed Object Corresponding SNMP Object
oMacEntity
.aMACID dot3StatsIndex or
IF-MIB - ifIndex
.aFramesTransmittedOK IF-MIB - ifOutUCastPkts +
ifOutMulticastPkts +
ifOutBroadcastPkts
.aSingleCollisionFrames dot3StatsSingleCollisionFrames
.aMultipleCollisionFrames dot3StatsMultipleCollisionFrames
.aFramesReceivedOK IF-MIB - ifInUcastPkts +
ifInMulticastPkts +
ifInBroadcastPkts
.aFrameCheckSequenceErrors dot3StatsFCSErrors
.aAlignmentErrors dot3StatsAlignmentErrors
.aOctetsTransmittedOK IF-MIB - ifOutOctets
.aFramesWithDeferredXmissions dot3StatsDeferredTransmissions
.aLateCollisions dot3StatsLateCollisions
.aFramesAbortedDueToXSColls dot3StatsExcessiveCollisions
.aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors
.aCarrierSenseErrors dot3StatsCarrierSenseErrors
.aOctetsReceivedOK IF-MIB - ifInOctets
.aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors
.aPromiscuousStatus IF-MIB - ifPromiscuousMode
.aReadMulticastAddressList IF-MIB - ifRcvAddressTable
.aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts
.aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts
.aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts
.aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts
.aFrameTooLongErrors dot3StatsFrameTooLongs
.aReadWriteMACAddress IF-MIB - ifPhysAddress
.aCollisionFrames dot3CollFrequencies
.acAddGroupAddress IF-MIB - ifRcvAddressTable
.acDeleteGroupAddress IF-MIB - ifRcvAddressTable
.acExecuteSelfTest dot3TestLoopBack
oPHYEntity
.aSQETestErrors dot3StatsSQETestErrors
.aSymbolErrorDuringCarrier dot3StatsSymbolErrorsNow the plot twist 😭 The following IEEE 802.3 managed objects have been removed from this MIB module because of implementation feedback. Bye bye, babies 🫠
oMacEntity.aFramesWithExcessiveDeferral.aInRangeLengthErrors.aOutOfRangeLengthField.aMACEnableStatus.aTransmitEnableStatus.aMulticastReceiveStatus.acInitializeMAC
If you want the full tea on why these got cut, check out [15] 🧚 It has all the details.
4. Definitions ✨
Here's the actual MIB module, the part where the magic happens 🪄
EtherLike-MIB DEFINITIONS ::= BEGIN
IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, mib-2, transmission
FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
ifIndex, InterfaceIndex
FROM IF-MIB;
etherMIB MODULE-IDENTITY
LAST-UPDATED "9806032150Z" -- June 3, 1998
ORGANIZATION "IETF 802.3 Hub MIB Working Group"
CONTACT-INFO
"WG E-mail: hubmib@hprnd.rose.hp.com
To subscribe: hubmib-request@hprnd.rose.hp.com
Chair: Dan Romascanu
Postal: LANNET Ltd.
Atidum Technology Park, Bldg. 3
Tel Aviv 61131
Israel
Tel: +972 3 645 8414
E-mail: dromasca@lannet.com
Editor: John Flick
Postal: Hewlett-Packard Company
8000 Foothills Blvd. M/S 5556
Roseville, CA 95747-5556
USA
Tel: +1 916 785 4018
Fax: +1 916 785 3583
E-mail: johnf@hprnd.rose.hp.com
Editor: Jeffrey Johnson
Postal: RedBack Networks
2570 North First Street, Suite 410
San Jose, CA, 95131
USA
Tel: +1 408 571 2699
Fax: +1 408 571 2698
E-Mail: jeff@redbacknetworks.com"
DESCRIPTION "The MIB module to describe generic objects for
Ethernet-like network interfaces. This MIB is an
updated version of the Ethernet-like MIB in RFC
1650."
REVISION "9806032150Z"
DESCRIPTION "Updated to include support for 100 Mb/sec
interfaces."
REVISION "9402030400Z"
DESCRIPTION "Version published as RFC 1650."
::= { mib-2 35 }
etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 }
dot3 OBJECT IDENTIFIER ::= { transmission 7 }
-- the Ethernet-like Statistics group
dot3StatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3StatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Statistics for a collection of ethernet-like
interfaces attached to a particular system."
::= { dot3 2 }
dot3StatsEntry OBJECT-TYPE
SYNTAX Dot3StatsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "Statistics for a particular interface to an
ethernet-like medium."
INDEX { dot3StatsIndex }
::= { dot3StatsTable 1 }
Dot3StatsEntry ::=
SEQUENCE {
dot3StatsIndex InterfaceIndex,
dot3StatsAlignmentErrors Counter32,
dot3StatsFCSErrors Counter32,
dot3StatsSingleCollisionFrames Counter32,
dot3StatsMultipleCollisionFrames Counter32,
dot3StatsSQETestErrors Counter32,
dot3StatsDeferredTransmissions Counter32,
dot3StatsLateCollisions Counter32,
dot3StatsExcessiveCollisions Counter32,
dot3StatsInternalMacTransmitErrors Counter32,
dot3StatsCarrierSenseErrors Counter32,
dot3StatsFrameTooLongs Counter32,
dot3StatsInternalMacReceiveErrors Counter32,
dot3StatsEtherChipSet OBJECT IDENTIFIER,
dot3StatsSymbolErrors Counter32
}
dot3StatsIndex OBJECT-TYPE
SYNTAX InterfaceIndex
MAX-ACCESS read-only
STATUS current
DESCRIPTION "An 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."
::= { dot3StatsEntry 1 }
dot3StatsAlignmentErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 2 }
dot3StatsFCSErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 3 }
dot3StatsSingleCollisionFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A 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,
ifOutMulticastPkts, or ifOutBroadcastPkts,
and is not counted by the corresponding
instance of the dot3StatsMultipleCollisionFrames
object."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 4 }
dot3StatsMultipleCollisionFrames OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A 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,
ifOutMulticastPkts, or ifOutBroadcastPkts,
and is not counted by the corresponding
instance of the dot3StatsSingleCollisionFrames
object."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 5 }
dot3StatsSQETestErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A 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."
REFERENCE "ANSI/IEEE Std 802.3-1985 Carrier Sense
Multiple Access with Collision Detection Access
Method and Physical Layer Specifications"
::= { dot3StatsEntry 6 }okay bestie, let's keep going with the dot3Stats counters 💅✨
dot3StatsDeferredTransmissions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 7 }
dot3StatsLateCollisions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 8 }
dot3StatsExcessiveCollisions OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of frames for which transmission on a
particular interface fails due to excessive
collisions."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 9 }
dot3StatsInternalMacTransmitErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 10 }
dot3StatsCarrierSenseErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 11 }
-- { dot3StatsEntry 12 } is not assigned
dot3StatsFrameTooLongs OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 13 }
-- { dot3StatsEntry 14 } is not assigned
-- { dot3StatsEntry 15 } is not assigned
dot3StatsInternalMacReceiveErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A 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."
REFERENCE "IEEE 802.3 Layer Management"
::= { dot3StatsEntry 16 }
dot3StatsEtherChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This object contains an OBJECT IDENTIFIER
which identifies the chipset used to
realize the interface. Ethernet-like
interfaces are typically built out of
several different chips. The MIB implementor
is presented with a decision of which chip
to identify via this object. The implementor
should identify the chip which is usually
called the Medium Access Control chip.
If no such chip is easily identifiable,
the implementor should identify the chip
which actually gathers the transmit
and receive statistics and error
indications. This would allow a
manager station to correlate the
statistics and the chip generating
them, giving it the ability to take
into account any known anomalies
in the chip."
::= { dot3StatsEntry 17 }
dot3StatsSymbolErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The number of times there was an invalid data
symbol when a valid carrier was present on a
particular interface.
The count represented by an instance of this
object is incremented at most once per carrier
event, even if multiple symbol errors occur
during the carrier event."
REFERENCE "IEEE 802.3u-1995 10 & 100 Mb/s Management"
::= { dot3StatsEntry 18 }Next up is the collision statistics group, and it's giving "optional but super useful if your box can meter it" 📊🎀
-- the Ethernet-like Collision Statistics group
-- Implementation of this group is optional; it is appropriate
-- for all systems which have the necessary metering
dot3CollTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3CollEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A collection of collision histograms for a
particular set of interfaces."
::= { dot3 5 }
dot3CollEntry OBJECT-TYPE
SYNTAX Dot3CollEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "A 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."
INDEX { ifIndex, dot3CollCount }
::= { dot3CollTable 1 }
Dot3CollEntry ::=
SEQUENCE {
dot3CollCount INTEGER,
dot3CollFrequencies Counter32
}
-- { dot3CollEntry 1 } is no longer in use
dot3CollCount OBJECT-TYPE
SYNTAX INTEGER (1..16)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "The number of per-frame media collisions for
which a particular collision histogram cell
represents the frequency on a particular
interface."
::= { dot3CollEntry 2 }
dot3CollFrequencies OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of individual MAC frames for which the
transmission (successful or otherwise) on a
particular interface occurs after the
frame has experienced exactly the number
of collisions in the associated
dot3CollCount object.
For example, a frame which is transmitted
on interface 77 after experiencing
exactly 4 collisions would be indicated
by incrementing only dot3CollFrequencies.77.4.
No other instance of dot3CollFrequencies would
be incremented in this example."
::= { dot3CollEntry 3 }Last bit for now: the 802.3 test and error OIDs, plus the start of the TDR test 🧪🦋
-- 802.3 Tests
dot3Tests OBJECT IDENTIFIER ::= { dot3 6 }
dot3Errors OBJECT IDENTIFIER ::= { dot3 7 }
-- TDR Test
dot3TestTdr OBJECT-IDENTITY
STATUS current
DESCRIPTION "The Time-Domain Reflectometry (TDR) test is
specific to ethernet-like interfaces of type
10Base5 and 10Base2. The TDR value may be
useful in determining the approximate distance
to a cable fault. It is advisable to repeat
this test to check for a consistent resulting
TDR value, to verify that there is a fault.Okay, the TDR test is giving precision! 🔬✨ It measures the time, in 10 MHz ticks (100 nsec units), from when the test transmission starts until a collision or carrier deassertion shows up. Then the result gets stored in a vendor-specific MIB object, and that object's OBJECT IDENTIFIER goes into the test result code object so everyone knows where to find it 🧚
A TDR test returns as its result the time
interval, measured in 10 MHz ticks or 100 nsec
units, between the start of TDR test
transmission and the subsequent detection of a
collision or deassertion of carrier. On
successful completion of a TDR test, the result
is stored as the value of an appropriate
instance of an appropriate vendor specific MIB
object, and the OBJECT IDENTIFIER of that
instance is stored in the appropriate instance
of the appropriate test result code object
(thereby indicating where the result has been
stored)."
::= { dot3Tests 1 }
-- Loopback Test
dot3TestLoopBack OBJECT-IDENTITY
STATUS current
DESCRIPTION "This test configures the MAC chip and executes
an internal loopback test of memory, data paths,
and the MAC chip logic. This loopback test can
only be executed if the interface is offline.
Once the test has completed, the MAC chip should
be reinitialized for network operation, but it
should remain offline.
If an error occurs during a test, the
appropriate test result object will be set
to indicate a failure. The two OBJECT
IDENTIFIER values dot3ErrorInitError and
dot3ErrorLoopbackError may be used to provided
more information as values for an appropriate
test result code object."
::= { dot3Tests 2 }
dot3ErrorInitError OBJECT-IDENTITY
STATUS current
DESCRIPTION "Couldn't initialize MAC chip for test."
::= { dot3Errors 1 }
dot3ErrorLoopbackError OBJECT-IDENTITY
STATUS current
DESCRIPTION "Expected data not received (or not received
correctly) in loopback test."
::= { dot3Errors 2 }Next up are the 802.3 hardware chipsets 🍓 The dot3StatsEtherChipSet object is how an interface says which MAC hardware it's talking through, and these are the registered chipsets. Let's go, bestie!
-- 802.3 Hardware Chipsets
-- The object dot3StatsEtherChipSet is provided to
-- identify the MAC hardware used to communicate on an
-- interface. The following hardware chipsets are
-- registered:
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
dot3ChipSetAMD7990 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am7990 Local Area Network
Controller for Ethernet (LANCE)."
::= { dot3ChipSetAMD 1 }
dot3ChipSetAMD79900 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79900 chip."
::= { dot3ChipSetAMD 2 }
dot3ChipSetAMD79C940 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C940 Media Access Controller
for Ethernet (MACE)."
::= { dot3ChipSetAMD 3 }
dot3ChipSetAMD79C90 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C90 CMOS Local Area Network
Controller for Ethernet (C-LANCE)."
::= { dot3ChipSetAMD 4 }
dot3ChipSetAMD79C960 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C960 PCnet-ISA Single Chip
Ethernet Controller for ISA."
::= { dot3ChipSetAMD 5 }
dot3ChipSetAMD79C961 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C961 PCnet-ISA+ Single Chip
Plug & Play Full-Duplex Ethernet Controller
for ISA."
::= { dot3ChipSetAMD 6 }
dot3ChipSetAMD79C961A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C961A PCnet-ISA II Single Chip
Plug & Play Full-Duplex Ethernet Controller
for ISA."
::= { dot3ChipSetAMD 7 }
dot3ChipSetAMD79C965 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C965 PCnet-32 Single Chip
Ethernet Controller for PCI."
::= { dot3ChipSetAMD 8 }
dot3ChipSetAMD79C970 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C970 PCnet PCI Single Chip
Ethernet Controller for PCI Local Bus."
::= { dot3ChipSetAMD 9 }
dot3ChipSetAMD79C970A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices AM79C970A PCnet PCI II Single Chip
Full-Duplex Ethernet Controller for PCI Local
Bus."
::= { dot3ChipSetAMD 10 }
dot3ChipSetAMD79C971 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C971 PCnet-FAST Single Chip
Full-Duplex 10/100 Mbps Ethernet Controller for
PCI Local Bus."
::= { dot3ChipSetAMD 11 }
dot3ChipSetAMD79C972 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C972 PCnet-FAST+ Enhanced
10/100 Mbps PCI Ethernet Controller with OnNow
Support."
::= { dot3ChipSetAMD 12 }
dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
dot3ChipSetIntel82586 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82586 IEEE 802.3 Ethernet LAN Coprocessor."
::= { dot3ChipSetIntel 1 }
dot3ChipSetIntel82596 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82596 High-Performance 32-Bit Local Area Network
Coprocessor."
::= { dot3ChipSetIntel 2 }
dot3ChipSetIntel82595 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82595 High Integration Ethernet Controller."
::= { dot3ChipSetIntel 3 }
dot3ChipSetIntel82557 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82557 Fast Ethernet PCI Bus Lan Controller."
::= { dot3ChipSetIntel 4 }
dot3ChipSetIntel82558 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82558 Fast Ethernet PCI Bus LAN Controller with
Integrated PHY."
::= { dot3ChipSetIntel 5 }
dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
dot3ChipSetSeeq8003 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
8003 chip set."
::= { dot3ChipSetSeeq 1 }
dot3ChipSetSeeq80C03 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
80C03 Full-Duplex CMOS Ethernet Data Link
Controller (MAC)."
::= { dot3ChipSetSeeq 2 }
dot3ChipSetSeeq84C30 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84C30 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 3 }
dot3ChipSetSeeq8431 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 8431 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 4 }
dot3ChipSetSeeq80C300 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
80C300 Full-Duplex CMOS Ethernet 10/100
Mbit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 5 }
dot3ChipSetSeeq84C300 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84C300 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 6 }
dot3ChipSetSeeq84301 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84301 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 7 }
dot3ChipSetSeeq84302 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84302 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 8 }
dot3ChipSetSeeq8100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
8100 Gigabit Ethernet Controller (MAC & PCS)."
::= { dot3ChipSetSeeq 9 }
dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
dot3ChipSetNational8390 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP8390 Network Interface
Controller."
::= { dot3ChipSetNational 1 }
dot3ChipSetNationalSonic OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83932 Systems-Oriented Network
Interface Controller (SONIC)."
::= { dot3ChipSetNational 2 }
dot3ChipSetNational83901 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83901 Serial Network Interface
Controller (SNIC)."
::= { dot3ChipSetNational 3 }
dot3ChipSetNational83902 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83902 Serial Network Interface
Controller for Twisted Pair (ST-NIC)."
::= { dot3ChipSetNational 4 }That's the chipset list wrapped up for this part, so the next bit keeps going from right here 💜
Okay bestie, this part is all chipset IDs and conformance stuff, and it's giving serious networking-hardware lore 💻✨
dot3ChipSetNational83905 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83905 AT Local Area Network
Twisted-Pair Interface (AT/LANTIC)."
::= { dot3ChipSetNational 5 }
dot3ChipSetNational83907 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83907 AT Twisted-Pair Enhanced
Coaxial Network Interface Controller
(AT/LANTIC II)."
::= { dot3ChipSetNational 6 }
dot3ChipSetNational83916 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83916 Systems-Oriented Network
Interface Controller (SONIC-16)."
::= { dot3ChipSetNational 7 }
dot3ChipSetNational83934 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83934 Systems-Oriented Network
Interface Controller with Twisted Pair Interface
(SONIC-T)."
::= { dot3ChipSetNational 8 }
dot3ChipSetNational83936 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83936AVUL Full-Duplex Systems-
Oriented Network Interface Controller with
Twisted Pair Interface (SONIC-T)."
::= { dot3ChipSetNational 9 }
dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
dot3ChipSetFujitsu86950 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
86950 chip."
::= { dot3ChipSetFujitsu 1 }
dot3ChipSetFujitsu86960 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86960 Network Interface Controller with
Encoder/Decoder (NICE)."
::= { dot3ChipSetFujitsu 2 }
dot3ChipSetFujitsu86964 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86964 Ethernet Controller with 10BASE-T
Tranceiver."
::= { dot3ChipSetFujitsu 3 }
dot3ChipSetFujitsu86965A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86965A EtherCoupler Single-Chip Ethernet
Controller."
::= { dot3ChipSetFujitsu 4 }
dot3ChipSetFujitsu86965B OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86965B EtherCoupler Single-Chip Ethernet
Controller (supports full-duplex)."
::= { dot3ChipSetFujitsu 5 }
dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 }
dot3ChipSetDigitalDC21040 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor DC21040 chip."
::= { dot3ChipSetDigital 1 }
dot3ChipSetDigital21041 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21041 PCI Ethernet LAN
Controller."
::= { dot3ChipSetDigital 2 }
dot3ChipSetDigital21140 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21140 PCI Fast Ethernet LAN
Controller."
::= { dot3ChipSetDigital 3 }
dot3ChipSetDigital21143 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21143 PCI/CardBus 10/100-Mb/s
Ethernet LAN Controller."
::= { dot3ChipSetDigital 4 }
dot3ChipSetDigital21340 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21340 10/100-MB/s managed buffered
port switch."
::= { dot3ChipSetDigital 5 }
dot3ChipSetDigital21440 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21440 Multiport 10/100Mbps
Ethernet Controller."
::= { dot3ChipSetDigital 6 }
dot3ChipSetDigital21540 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21540 PCI/CardBus Ethernet LAN
Controller with Modem Interface."
::= { dot3ChipSetDigital 7 }
dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 }
dot3ChipSetTIE100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETE100 ThunderLAN PCI Fast
Ethernet Controller."
::= { dot3ChipSetTI 1 }
dot3ChipSetTIE110 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETE110 ThunderLAN PCI 10BASE-T
Ethernet Adapter."
::= { dot3ChipSetTI 2 }
dot3ChipSetTIX3100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3100 Desktop ThunderSWITCH
8/2."
::= { dot3ChipSetTI 3 }
dot3ChipSetTIX3150 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3150 ThunderSWITCH 12/3."
::= { dot3ChipSetTI 4 }
dot3ChipSetTIX3270 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3270 ThunderSWITCH 24/3."
::= { dot3ChipSetTI 5 }
dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 }
dot3ChipSetToshibaTC35815F OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Toshiba
TC35815F PCI-Based 100/10Mbps Ethernet
Controller."
::= { dot3ChipSetToshiba 1 }
dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 }
dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Lucent
Technologies ATT1MX10 (Spinnaker) Quad MAC and
Tranceiver for Ethernet Frame Switching."
::= { dot3ChipSetLucent 1 }
dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Lucent
Technologies LUC3M08 Eight Ethernet MACs for
10/100 Mbits/s Frame Switching."
::= { dot3ChipSetLucent 2 }
dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 }
dot3ChipSetGalileoGT48001 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48001A Switched Ethernet
Controller."
::= { dot3ChipSetGalileo 1 }
dot3ChipSetGalileoGT48002 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48002A Switched Fast Ethernet
Controller."
::= { dot3ChipSetGalileo 2 }
dot3ChipSetGalileoGT48004 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48004A Four Port Fast Ethernet
Switch for Multiport 10/100BASE-X Systems."
::= { dot3ChipSetGalileo 3 }
dot3ChipSetGalileoGT48207 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48207 Low-Cost 10 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 4 }
dot3ChipSetGalileoGT48208 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48208 Advanced 10 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 5 }
dot3ChipSetGalileoGT48212 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48212 Advanced 14 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 6 }
dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 }
dot3ChipSetJatoJT1001 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Jato
Technologies JT1001 GigEMAC Server
10/100/1000Mbps Ethernet Controller with PCI
interface."
::= { dot3ChipSetJato 1 }
dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 }
dot3ChipSetXaQtiXQ11800FP OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the XaQTI
XQ11800FP XMAC II Gigabit Ethernet Media Access
Controller."
::= { dot3ChipSetXaQti 1 }
dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the XaQTI
XQ18110FP GigaPower Protocol Accelerator."
::= { dot3ChipSetXaQti 2 }
-- For those chipsets not represented above, OBJECT IDENTIFIER
-- assignment is required in other documentation, e.g.,
-- assignment within that part of the registration tree
-- delegated to individual enterprises (see RFC 1155 and
-- RFC 1902).
--
-- In the future, management of chipset registrations may be
-- delegated to the Internet Assigned Numbers Authority (IANA).
-- conformance information
etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 }
etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 }
etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 }
-- compliance statements
etherCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The compliance statement for managed network
entities which have ethernet-like network
interfaces."
MODULE -- this module
MANDATORY-GROUPS { etherStatsGroup }Okay so the big takeaway here 🎀 is that each chipset gets its own authoritative OBJECT-IDENTITY, numbered under its vendor's branch of dot3ChipSets 💜. The vendors with unlisted chips? Their OBJECT IDENTIFIERs are supposed to be assigned in other documentation, like inside the part of the registration tree handed out to individual enterprises (the comment points at RFC 1155 and RFC 1902 for that 📚). Then there's a note that chipset registrations may end up being delegated to IANA someday 🦋. Not me being a crystal ball, that's just what the comment says 🙈
And then the conformance bit 👑: etherConformance hangs off etherMIB, with etherGroups and etherCompliances underneath it. The compliance statement is for managed network entities that have ethernet-like interfaces, and the only MANDATORY group listed here is etherStatsGroup 🌸💅
GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate
for all systems which have the necessary
metering. Implementation in such systems is
highly recommended."
::= { etherCompliances 1 }
ether100MbsCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION "The compliance statement for managed network
entities which have 100 Mb/sec ethernet-like
network interfaces."
MODULE -- this module
MANDATORY-GROUPS { etherStats100MbsGroup }
GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate
for all systems which have the necessary
metering. Implementation in such systems is
highly recommended."
::= { etherCompliances 2 }
-- units of conformance
etherStatsGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsSQETestErrors,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors,
dot3StatsEtherChipSet
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to all ethernet-like network
interfaces."
::= { etherGroups 1 }
etherCollisionTableGroup OBJECT-GROUP
OBJECTS { dot3CollFrequencies
}
STATUS current
DESCRIPTION "A collection of objects providing a histogram
of packets successfully transmitted after
experiencing exactly N collisions."
::= { etherGroups 2 }
etherStats100MbsGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors,
dot3StatsEtherChipSet,
dot3StatsSymbolErrors
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to 100 Mb/sec ethernet-like network
interfaces."
::= { etherGroups 3 }
END5. Intellectual Property ⚖️
okay so the IETF is basically saying "we don't take a side" 🙅♀️ on whether any intellectual property or other rights that someone might claim over the tech in this doc are valid, how far they reach, or whether you can even get a license for them. they also haven't gone hunting for any of those rights, so don't assume they've checked. if you want the IETF's rules on rights for standards-track and standards-related docs, look at BCP-11 📜. copies of claimed rights that were made available for publication, any promised licenses, or the result of trying to get a general license or permission for implementers or users can be requested from the IETF Secretariat 💌.
the IETF also really wants to hear about any copyrights, patents, patent applications, or other proprietary rights that might cover tech you'd need to implement this standard 🫶. send that info to the IETF Executive Director 💼.
6. Acknowledgements 🎀
this doc was made by the 802.3 Hub MIB Working Group 🌸, and honestly it's giving "built on the shoulders of giants" energy 🧚. it's almost completely based on the Standard Ethernet MIB, RFC 1643 [10], and the Proposed Standard Ethernet MIB using the SNMPv2 SMI, RFC 1650 [11]. both were edited by Frank Kastenholz of FTP Software and produced by the Ethernet MIB Working Group. this doc extends them by adding support for 100 Mb/sec ethernet interfaces as outlined in [6] 🔥.
RFC 1643 and RFC 1650 are themselves based on the Draft Standard Ethernet MIB, RFC 1398 [9], also edited by Frank Kastenholz and produced by the Ethernet MIB Working Group 💅.
RFC 1398 is based on the Proposed Standard Ethernet MIB, RFC 1284 [8], which John Cook of Chipcom edited and the Transmission MIB Working Group produced 🦋. the Ethernet MIB Working Group gathered implementation experience with the variables in RFC 1284 and used it to develop this revised MIB 📊.
RFC 1284 is based on a document Frank Kastenholz wrote back when he was at Interlan, called IEEE 802.3 Layer Management Draft M compatible MIB for TCP/IP Networks [7] ✨. the SNMP Working Group and then the Transmission Working Group gave it a modest rework so it matches the current conventions for defining objects for MIB interfaces 🛠️. James Davin of the MIT Laboratory for Computer Science and Keith McCloghrie of Hughes LAN Systems helped with later drafts 🙌. Marshall Rose of Performance Systems International, Inc. turned the document into its current concise format 💖. Anil Rijsinghani of DEC wrote the text that describes the TDR test more accurately 🧠. and a big thanks to Frank Kastenholz of Interlan and Louis Steinberg of IBM for their experiments 🥹💜.
7. References 📚
[1] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization, International Standard 8824, December 1987.
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Management Information for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for Version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996.
[5] IEEE, IEEE 802.3 Layer Management, November 1988.
[6] IEEE, IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, Supplement to IEEE Std 802.3, October 26, 1995.
[7] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible MIB for TCP/IP Networks", electronic mail message to mib-wg@nnsc.nsf.net, 9 June 1989.
[8] Cook, J., "Definitions of Managed Objects for Ethernet-Like Interface Types", RFC 1284, December 1991.
[9] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 1398, January 1993.
[10] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types", RFC 1643, July 1994.
[11] Kastenholz, F., "Definitions of Managed Objects for the Ethernet-like Interface Types using SMIv2", RFC 1650, August 1994.
[12] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB using SMIv2", RFC 2233, Cisco Systems, November 1997.
[13] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997.
[14] deGraaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and S. Roberts, "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", RFC 2239, November 1997.
[15] Kastenholz, F., "Implementation Notes and Experience for The Internet Ethernet MIB", RFC 1369, October 1992.
[16] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, March 1991.
[17] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2274, January 1998.
[18] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access Control Model for the Simple Network Management Protocol (SNMP)", RFC 2275, January 1998.
8. Security Considerations 🔐
okay this section is serious bestie, so listen up 👀💀. there are no management objects in this MIB with a MAX-ACCESS clause of read-write and/or read-create. so if this MIB is implemented correctly, an intruder has no way to change or create any management objects in this MIB with direct SNMP SET operations 🛡️.
a bunch of managed objects in this MIB could be seen as sensitive 😳. the big one is dot3StatsEtherChipSet, which could be super sensitive in lots of environments, because it would let an intruder figure out which vendor's equipment is on the network 🕵️♀️.
so in some environments it could be really important to control read access to these objects, and maybe even encrypt their values when they go over the network via SNMP 🔒. not every version of SNMP has features for a secure setup like that 😭.
SNMPv1 by itself is an insecure environment, full stop 🙅♀️. even if the network itself is secure (for example by using IPSec), there's still no control over who on that secure network can access and GET (read) the objects in this MIB 💀.
the implementors should really look at the security features in the SNMPv3 framework 🌈. specifically, the User-based Security Model in RFC 2274 [17] and the View-based Access Control Model in RFC 2275 [18] are recommended 💜.
and then it's on the customer/user to make sure the SNMP entity that gives access to an instance of this MIB is set up properly, so only the principals (users) with legitimate rights can reach those objects 🫶✨.
bestie, this part is not optional. lock down your read access before you ship 🚨💅
9. Authors' Addresses 🦋
John Flick
Hewlett-Packard Company
8000 Foothills Blvd. M/S 5556
Roseville, CA 95747-5556
Phone: +1 916 785 4018
EMail: johnf@hprnd.rose.hp.com
Jeffrey Johnson
RedBack Networks
2570 North First Street, Suite 410
San Jose, CA, 95131, USA
Phone: +1 408 571 2699
EMail: jeff@redbacknetworks.comA. Change Log 🦋
okay this is the receipts 📜 bestie, it lists every single change made to RFC 1650 to get this document. glow-up arc fr ✨
- (1) The MODULE-IDENTITY has been updated to reflect the changes in the MIB. 💅
- (2) A new object,
dot3StatsSymbolErrors, has been added. 🌸 - (3) The definition of the object
dot3StatsIndexhas been converted to use the SMIv2 OBJECT-TYPE macro. 🧚 - (4) A new conformance group,
etherStats100MbsGroup, has been added. 🎀 - (5) A new compliance statement,
ether100MbsCompliance, has been added. 👑 - (6) The Acknowledgements were extended to provide a more complete history of the origin of this document. 🫶
- (7) The discussion of
ifTypehas been expanded. ✨ - (8) A section on mapping of Interfaces MIB objects has been added. 🦋
- (9) A section defining the relationship of this MIB to the MAU MIB has been added. 💖
- (10) A section on the mapping of IEEE 802.3 managed objects to this MIB and the Interfaces MIB has been added. 🍓
- (11) Converted the
dot3Tests,dot3Errors, anddot3ChipSetsOIDs to use the OBJECT-IDENTITY macro. 💜 - (12) Added to the list of registered
dot3ChipSets. 🌈 - (13) An intellectual property notice and copyright notice were added, as required by RFC 2026. 🔥
B. Full Copyright Statement 💜
okay this is the legal part, but it's giving very clear permissions, so let me explain it in plain speak 🔒
Anyone can copy this document and share it, and translations of it too. You can also make derivative works that comment on or explain it, or that help people implement it. You can publish and distribute all of that, in whole or in part, with no restrictions of any kind. The one condition is that the above copyright notice and this paragraph stay on all those copies and derivative works. 🫶
BUT the document itself can't be modified in any way. That means you can't remove the copyright notice or the references to the Internet Society or other Internet organizations. The only exceptions are when it's needed for developing Internet standards (then you have to follow the copyright procedures in the Internet Standards process), or when you're translating it into languages other than English. 🌸
The limited permissions above are perpetual, so they will not be revoked by the Internet Society or its successors or assigns. Forever and ever 💖
Now the disclaimer, which is in all caps for a reason 😭
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 🙈
📦 where this page comes from
- ietf: rfc2358 1998-06
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms