As per Relevance of the word identifier, we have this rfc below:
Network Working Group J.
Request for Comments: 2358 Hewlett-Packard
Obsoletes: 1650 J.
Category: Standards Track RedBack
June 1998
Definitions of Managed Objects
the Ethernet-like Interface
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1998). All Rights Reserved
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
This memo obsoletes RFC 1650 "Definitions of Managed Objects for
Ethernet-like Interface Types using SMIv2". This memo extends
specification by including management information useful for
management of 100 Mb/s Ethernet interfaces
Ethernet technology, as defined by the 802.3 Working Group of
IEEE, continues to evolve, with scalable increases in speed,
types of cabling and interfaces, and new features. This
may require changes in the managed objects in order to reflect
new functionality. This document, as with other documents issued
this working group, reflect a certain stage in the evolution
Ethernet technology. In the future, this document might be revised
or new documents might be issued by the Ethernet Interfaces and
MIB Working Group, in order to reflect the evolution of
technology
Flick & Johnson Standards Track [Page 1]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
Table of
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 ................................... 39
1.
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it defines objects for managing ethernet-
interfaces
This memo also includes a MIB module. This MIB module extends
list of managed objects specified in 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
document are to be interpreted as described in [13].
2. The SNMP Network Management
The SNMP Network Management Framework consists of several components
For the purpose of this specification, the applicable components
the Framework are the SMI and related documents [2, 3, 4],
define the mechanisms used for describing and naming objects for
purpose of management
Flick & Johnson Standards Track [Page 2]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
2.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1) [1]
defined in the SMI [2]. In particular, each object object type
named by an OBJECT IDENTIFIER, an administratively assigned name
The object type together with an object instance serves to
identify a specific instantiation of the object. For
convenience, we often use a textual string, termed the descriptor,
refer to the object type
3.
Instances of these object types represent attributes of an
to an ethernet-like communications medium. At present, ethernet-
media are identified by the following values of the ifType object
the Interfaces MIB [12]:
ethernetCsmacd(6)
iso88023Csmacd(7)
starLan(11)
The definitions presented here are based on the IEEE 802.3
Management Specification [5], as originally interpreted by
Kastenholz then of Interlan in [7]. Implementors of these
objects should note that the IEEE document explicitly describes (
the form of Pascal pseudocode) when, where, and how various
attributes are measured. The IEEE document also describes
effects of MAC actions that may be invoked by manipulating
of the MIB objects defined here
To the extent that some of the attributes defined in [5]
represented by previously defined objects in MIB-2 [16] or in
Interfaces MIB [12], such attributes are not redundantly
by objects defined in this memo. Among the attributes represented
objects defined in other memos are the number of octets
or received on a particular interface, the number of
transmitted or received on a particular interface, the
status of an interface, the MAC address of an interface,
multicast information associated with an interface
Flick & Johnson Standards Track [Page 3]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
3.1. Relation to MIB-2
This section applies only when this MIB is used in conjunction
the "old" (RFC 1213) [16] interface group
The relationship between an ethernet-like interface and an
in the context of the Internet-standard MIB is one-to-one. As such
the value of an ifIndex object instance can be directly used
identify corresponding instances of the objects defined herein
For agents which implement the (now deprecated) ifSpecific object,
instance of that object that is associated with an ethernet-
interface has the OBJECT IDENTIFIER value
dot3 OBJECT IDENTIFER ::= { transmission 7 }
3.2. Relation to the Interfaces
The Interface MIB [12] requires that any MIB which is an adjunct
the Interface MIB clarify specific areas within the Interface MIB
These areas were intentionally left vague in the Interface MIB
avoid over constraining the MIB, thereby precluding management
certain media-types
Section 3.3 of [12] enumerates several areas which a media-
MIB must clarify. Each of these areas is addressed in a
subsection. The implementor is referred to [12] in order
understand the general intent of these areas
3.2.1. Layering
This MIB does not provide for layering. There are no sublayers
EDITOR'S NOTE
One could foresee the development of an 802.2 and enet-
MIB. They could be higher and lower sublayers, respectively.
that THIS document should do is allude to the possibilities and
the implementor to be aware of the possibility and that they may
requirements which supersede the requirements in this document
3.2.2. Virtual
This medium does not support virtual circuits and this area is
applicable to this MIB
Flick & Johnson Standards Track [Page 4]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
3.2.3.
This MIB defines two tests for media which are instrumented with
MIB; TDR and Loopback. Implementation of these tests is
required. Many common interface chips do not support one or both
these tests
These two tests are provided as a convenience, allowing a
method to invoke the test
Standard MIBs do not include objects in which to return the
of the TDR test. Any needed objects MUST be provided in the
specific MIB
Note that the ifTestTable is now deprecated. Work is underway
define a replacement MIB for system and interface testing. It
expected that the tests defined in this document will be usable
this replacement MIB
3.2.4.
This table contains all IEEE 802.3 addresses, unicast, multicast,
broadcast, for which this interface will receive packets and
them up to a higher layer entity for local consumption. The
of the address, contained in ifRcvAddressAddress, is the same as
ifPhysAddress
In the event that the interface is part of a MAC bridge, this
does not include unicast addresses which are accepted for
forwarding out some other port. This table is explicitly
intended to provide a bridge address filtering mechanism
3.2.5.
This object contains the IEEE 802.3 address which is placed in
source-address field of any Ethernet, Starlan, or IEEE 802.3
that originate at this interface. Usually this will be kept in
on the interface hardware. Some systems may set this address
software
In a system where there are several such addresses the designer has
tougher choice. The address chosen should be the one most likely
be of use to network management (e.g. the address placed in
responses for systems which are primarily IP systems).
If the designer truly can not chose, use of the factory- provided
address is suggested
Flick & Johnson Standards Track [Page 5]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
If the address can not be determined, an octet string of zero
should be returned
The address is stored in binary in this object. The address
stored in "canonical" bit order, that is, the Group Bit is
as the low-order bit of the first octet. Thus, the first byte of
multicast address would have the bit 0x01 set
3.2.6.
This MIB applies to interfaces which have any of the following
values
ethernetCsmacd(6)
iso88023Csmacd(7)
starLan(11)
It is RECOMMENDED that all Ethernet-like interfaces use an ifType
ethernetCsmacd(6) regardless of the speed that the interface
running or the link-layer encapsulation in use. iso88023Csmacd(7)
and starLan(11) are supported for backwards compatability
There are two other interface types defined in the IANAifType-MIB
100 Mbit Ethernet. They are fastEther(62), and fastEtherFX(69).
This document takes the position that an Ethernet is an Ethernet,
Ethernet interfaces SHOULD always have the same value of ifType
Information on the particular flavor of Ethernet that an interface
running is available from ifSpeed in the Interfaces MIB,
ifMauType in the 802.3 MAU MIB. An Ethernet-like interface
NOT use the fastEther(62) or fastEtherFX(69) ifTypes
Interfaces with any of the supported ifType values map to
EtherLike-MIB in the same manner. Which compliance statement
interface should implement is dependent on the maximum
supported on the interface. The EtherLike-MIB
compliance statement applies to all Ethernet-like interfaces
maximum supported speed is 10 Mbit/sec or less. There are
implementation differences. Similarly, the EtherLike-
ether100MbsCompliance compliance statement applies to all Ethernet
like interfaces whose maximum supported speed is 100Mbit/sec
An interface that is capable of operating at 100Mbit/sec
implement the ether100MbsCompliance compliance statement, even if
is currently operating at a lower speed. Counters in
ether100MbsCompliance compliance statement that only apply to 100
Mbit interfaces would simply not increment when the interface
operating at a lower speed
Flick & Johnson Standards Track [Page 6]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
3.2.7. Specific Interface MIB
The following table provides specific implementation guidelines
applying the interface group objects to ethernet-like media
ifIndex Each ethernet-like interface
represented by an ifEntry.
dot3StatsTable in this MIB module
indexed by dot3StatsIndex. The
identified by a particular value
dot3StatsIndex is the same interface
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
interface in bits per second.
current ethernet-like interfaces,
will be equal to 1,000,000 (1 million),
10,000,000 (10 million), or 100,000,000
(100 million). If the
implements auto-negotiation
auto-negotiation is enabled for
interface, and the interface has not
negotiated to an operational speed,
object SHOULD reflect the maximum
supported by the interface. Note
this object MUST NOT indicate a
value when operating in full-
mode. It MUST indicate the
line speed regardless of the
duplex mode. The correct object to
to determine the duplex mode of
interface is the ifMauType object in
802.3 MAU MIB
ifPhysAddress Refer to section 3.2.5.
ifAdminStatus Write access is not required.
for 'testing' is not required
Flick & Johnson Standards Track [Page 7]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
ifOperStatus The operational state of the interface
Support for 'testing' is not required
The value 'dormant' has no meaning
an ethernet-like interface
ifLastChange Refer to [12].
ifInOctets The number of octets in valid MAC
received on this interface,
the MAC header and FCS
ifInUcastPkts Refer to [12].
ifInDiscards Refer to [12].
ifInErrors The sum for this interface
dot3StatsAlignmentErrors
dot3StatsFCSErrors
dot3StatsFrameTooLongs
dot3StatsInternalMacReceiveErrors
dot3StatsSymbolErrors
ifInUnknownProtos Refer to [12].
ifOutOctets The number of octets transmitted
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
dot3StatsCarrierSenseErrors
ifName Locally-significant textual name for
interface (e.g. lan0).
ifInMulticastPkts Refer to [12].
ifInBroadcastPkts Refer to [12].
ifOutMulticastPkts Refer to [12].
Flick & Johnson Standards Track [Page 8]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
ifOutBroadcastPkts Refer to [12].
ifHCInOctets 64-bit versions of counters.
ifHCOutOctets for ethernet-like interfaces that
capable of operating at 20Mbit/sec
faster, even if the interface
currently operating at less
20Mbit/sec
ifHCInUcastPkts 64-bit versions of packet counters
ifHCInMulticastPkts Support for these counters is
ifHCInBroadcastPkts required for the interface
ifHCOutUcastPkts supported by this MIB. They are
ifHCOutMulticastPkts required for interfaces capable
ifHCOutBroadcastPkts operating at 640Mbit/sec or faster
Note that a future revision of
document may support faster interfaces
and therefore may require support
these counters
ifLinkUpDownTrapEnable Refer to [12]. Default is 'enabled
ifHighSpeed The current operational speed of
interface in millions of bits
second. For current ethernet-
interfaces, this will be equal to 1, 10,
or 100. If the interface
auto-negotiation, auto-negotiation
enabled for this interface, and
interface has not yet negotiated to
operational speed, this object
reflect the maximum speed supported
the interface. Note that this
MUST NOT indicate a doubled value
operating in full-duplex mode. It
indicate the correct line
regardless of the current duplex mode
The correct object to use to
the duplex mode of the interface is
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].
Flick & Johnson Standards Track [Page 9]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
ifStackHigherLayer Refer to section 3.2.1.
ifRcvAddressAddress Refer to section 3.2.4.
3.3. Relation to the 802.3 MAU
Support for the mauModIfCompl compliance statement of the MAU-
[14] is REQUIRED for Ethernet-like interfaces. This MIB is needed
order to allow applications to determine the current MAU type in
by the interface. The MAU type indicates not only the media type
use, but also indicates whether the interface is operating in half
duplex or full-duplex mode. Implementing this MIB module
implementing the MAU-MIB would leave applications with no
way to determine the duplex mode of the interface
3.4. Mapping of IEEE 802.3 Managed
IEEE 802.3 Managed Object Corresponding SNMP
.aMACID dot3StatsIndex
IF-MIB -
.aFramesTransmittedOK IF-MIB - ifOutUCastPkts +
ifOutMulticastPkts +
.aSingleCollisionFrames dot3
.aMultipleCollisionFrames dot3
.aFramesReceivedOK IF-MIB - ifInUcastPkts +
ifInMulticastPkts +
.aFrameCheckSequenceErrors dot3
.aAlignmentErrors dot3
.aOctetsTransmittedOK IF-MIB -
.aFramesWithDeferredXmissions dot3
.aLateCollisions dot3
.aFramesAbortedDueToXSColls dot3
.aFramesLostDueToIntMACXmitError dot3
.aCarrierSenseErrors dot3
.aOctetsReceivedOK IF-MIB -
.aFramesLostDueToIntMACRcvError dot3
.aPromiscuousStatus IF-MIB -
.aReadMulticastAddressList IF-MIB -
.aMulticastFramesXmittedOK IF-MIB -
.aBroadcastFramesXmittedOK IF-MIB -
Flick & Johnson Standards Track [Page 10]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
.aMulticastFramesReceivedOK IF-MIB -
.aBroadcastFramesReceivedOK IF-MIB -
.aFrameTooLongErrors dot3
.aReadWriteMACAddress IF-MIB -
.aCollisionFrames dot3
.acAddGroupAddress IF-MIB -
.acDeleteGroupAddress IF-MIB -
.acExecuteSelfTest dot3
.aSQETestErrors dot3
.aSymbolErrorDuringCarrier dot3
The following IEEE 802.3 managed objects have been removed from
MIB module as a result of implementation feedback
.
.
.
.
.
.
.
Please see [15] for the detailed reasoning on why these objects
removed
4.
EtherLike-MIB DEFINITIONS ::=
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY
Counter32, mib-2,
FROM SNMPv2-
MODULE-COMPLIANCE, OBJECT-
FROM SNMPv2-
ifIndex,
FROM IF-MIB
etherMIB MODULE-
LAST-UPDATED "9806032150Z" -- June 3, 1998
ORGANIZATION "IETF 802.3 Hub MIB Working Group
CONTACT-
"WG E-mail: hubmib@hprnd.rose.hp.
To subscribe: hubmib-request@hprnd.rose.hp.
Flick & Johnson Standards Track [Page 11]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
Chair: Dan
Postal: LANNET Ltd
Atidum Technology Park, Bldg. 3
Tel Aviv 61131
Tel: +972 3 645 8414
E-mail: dromasca@lannet.
Editor: John
Postal: Hewlett-Packard
8000 Foothills Blvd. M/S 5556
Roseville, CA 95747-5556
Tel: +1 916 785 4018
Fax: +1 916 785 3583
E-mail: johnf@hprnd.rose.hp.
Editor: Jeffrey
Postal: RedBack
2570 North First Street, Suite 410
San Jose, CA, 95131
Tel: +1 408 571 2699
Fax: +1 408 571 2698
E-Mail: jeff@redbacknetworks.com
DESCRIPTION "The MIB module to describe generic objects
Ethernet-like network interfaces. This MIB is
updated version of the Ethernet-like MIB in
1650."
REVISION "9806032150Z
DESCRIPTION "Updated to include support for 100 Mb/
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
dot3StatsTable OBJECT-
SYNTAX SEQUENCE OF Dot3
MAX-ACCESS not-
Flick & Johnson Standards Track [Page 12]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
STATUS
DESCRIPTION "Statistics for a collection of ethernet-
interfaces attached to a particular system."
::= { dot3 2 }
dot3StatsEntry OBJECT-
SYNTAX Dot3
MAX-ACCESS not-
STATUS
DESCRIPTION "Statistics for a particular interface to
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-
SYNTAX
MAX-ACCESS read-
STATUS
DESCRIPTION "An index value that uniquely identifies
interface to an ethernet-like medium.
interface identified by a particular value
this index is the same interface as
by the same value of ifIndex."
::= { dot3StatsEntry 1 }
dot3StatsAlignmentErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
Flick & Johnson Standards Track [Page 13]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
DESCRIPTION "A count of frames received on a
interface that are not an integral number
octets in length and do not pass the FCS check
The count represented by an instance of
object is incremented when the
status is returned by the MAC service to
LLC (or other MAC user). Received frames
which multiple error conditions obtain are
according to the conventions of IEEE 802.3
Layer Management, counted exclusively
to the error status presented to the LLC."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 2 }
dot3StatsFCSErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of frames received on a
interface that are an integral number of
in length but do not pass the FCS check
The count represented by an instance of
object is incremented when the
status is returned by the MAC service to
LLC (or other MAC user). Received frames
which multiple error conditions obtain are
according to the conventions of IEEE 802.3
Layer Management, counted exclusively
to the error status presented to the LLC."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 3 }
dot3StatsSingleCollisionFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of successfully transmitted frames
a particular interface for which
is inhibited by exactly one collision
A frame that is counted by an instance of
object is also counted by the
instance of either the ifOutUcastPkts
ifOutMulticastPkts, or ifOutBroadcastPkts
and is not counted by the
instance of the dot3
Flick & Johnson Standards Track [Page 14]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
object."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 4 }
dot3StatsMultipleCollisionFrames OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of successfully transmitted frames
a particular interface for which
is inhibited by more than one collision
A frame that is counted by an instance of
object is also counted by the
instance of either the ifOutUcastPkts
ifOutMulticastPkts, or ifOutBroadcastPkts
and is not counted by the
instance of the dot3
object."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 5 }
dot3StatsSQETestErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of times that the SQE TEST
message is generated by the PLS sublayer for
particular interface. The SQE TEST
message is defined in section 7.2.2.2.4
ANSI/IEEE 802.3-1985 and its generation
described in section 7.2.4.6 of the
document."
REFERENCE "ANSI/IEEE Std 802.3-1985 Carrier
Multiple Access with Collision Detection
Method and Physical Layer Specifications
::= { dot3StatsEntry 6 }
dot3StatsDeferredTransmissions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of frames for which the
transmission attempt on a particular
is delayed because the medium is busy
Flick & Johnson Standards Track [Page 15]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
The count represented by an instance of
object does not include frames involved
collisions."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 7 }
dot3StatsLateCollisions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "The number of times that a collision
detected on a particular interface later
512 bit-times into the transmission of
packet
Five hundred and twelve bit-times
to 51.2 microseconds on a 10 Mbit/s system.
(late) collision included in a
represented by an instance of this object
also considered as a (generic) collision
purposes of other collision-
statistics."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 8 }
dot3StatsExcessiveCollisions OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of frames for which transmission on
particular interface fails due to
collisions."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 9 }
dot3StatsInternalMacTransmitErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of frames for which transmission on
particular interface fails due to an
MAC sublayer transmit error. A frame is
counted by an instance of this object if it
not counted by the corresponding instance
either the dot3StatsLateCollisions object,
dot3StatsExcessiveCollisions object, or
dot3StatsCarrierSenseErrors object
Flick & Johnson Standards Track [Page 16]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
The precise meaning of the count represented
an instance of this object is implementation
specific. In particular, an instance of
object may represent a count of
errors on a particular interface that are
otherwise counted."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 10 }
dot3StatsCarrierSenseErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "The number of times that the carrier
condition was lost or never asserted
attempting to transmit a frame on a
interface
The count represented by an instance of
object is incremented at most once
transmission attempt, even if the carrier
condition fluctuates during a
attempt."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 11 }
-- { dot3StatsEntry 12 } is not
dot3StatsFrameTooLongs OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of frames received on a
interface that exceed the maximum
frame size
The count represented by an instance of
object is incremented when the
status is returned by the MAC service to
LLC (or other MAC user). Received frames
which multiple error conditions obtain are
according to the conventions of IEEE 802.3
Layer Management, counted exclusively
to the error status presented to the LLC."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 13 }
-- { dot3StatsEntry 14 } is not
Flick & Johnson Standards Track [Page 17]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
-- { dot3StatsEntry 15 } is not
dot3StatsInternalMacReceiveErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of frames for which reception on
particular interface fails due to an
MAC sublayer receive error. A frame is
counted by an instance of this object if it
not counted by the corresponding instance
either the dot3StatsFrameTooLongs object,
dot3StatsAlignmentErrors object, or
dot3StatsFCSErrors object
The precise meaning of the count represented
an instance of this object is implementation
specific. In particular, an instance of
object may represent a count of receive
on a particular interface that are
otherwise counted."
REFERENCE "IEEE 802.3 Layer Management
::= { dot3StatsEntry 16 }
dot3StatsEtherChipSet OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
DESCRIPTION "This object contains an OBJECT
which identifies the chipset used
realize the interface. Ethernet-
interfaces are typically built out
several different chips. The MIB
is presented with a decision of which
to identify via this object. The
should identify the chip which is
called the Medium Access Control chip
If no such chip is easily identifiable
the implementor should identify the
which actually gathers the
and receive statistics and
indications. This would allow
manager station to correlate
statistics and the chip
them, giving it the ability to
into account any known
in the chip."
::= { dot3StatsEntry 17 }
Flick & Johnson Standards Track [Page 18]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
dot3StatsSymbolErrors OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "The number of times there was an invalid
symbol when a valid carrier was present on
particular interface
The count represented by an instance of
object is incremented at most once per
event, even if multiple symbol errors
during the carrier event."
REFERENCE "IEEE 802.3u-1995 10 & 100 Mb/s Management
::= { dot3StatsEntry 18 }
-- the Ethernet-like Collision Statistics
-- Implementation of this group is optional; it is
-- for all systems which have the necessary
dot3CollTable OBJECT-
SYNTAX SEQUENCE OF Dot3
MAX-ACCESS not-
STATUS
DESCRIPTION "A collection of collision histograms for
particular set of interfaces."
::= { dot3 5 }
dot3CollEntry OBJECT-
SYNTAX Dot3
MAX-ACCESS not-
STATUS
DESCRIPTION "A cell in the histogram of per-
collisions for a particular interface.
instance of this object represents
frequency of individual MAC frames for
the transmission (successful or otherwise) on
particular interface is accompanied by
particular number of media collisions."
INDEX { ifIndex, dot3CollCount }
::= { dot3CollTable 1 }
Dot3CollEntry ::=
SEQUENCE {
dot3CollCount INTEGER
dot3CollFrequencies Counter32
}
Flick & Johnson Standards Track [Page 19]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
-- { dot3CollEntry 1 } is no longer in
dot3CollCount OBJECT-
SYNTAX INTEGER (1..16)
MAX-ACCESS not-
STATUS
DESCRIPTION "The number of per-frame media collisions
which a particular collision histogram
represents the frequency on a
interface."
::= { dot3CollEntry 2 }
dot3CollFrequencies OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of individual MAC frames for which
transmission (successful or otherwise) on
particular interface occurs after
frame has experienced exactly the
of collisions in the
dot3CollCount object
For example, a frame which is
on interface 77 after
exactly 4 collisions would be
by incrementing only dot3CollFrequencies.77.4.
No other instance of dot3CollFrequencies
be incremented in this example."
::= { dot3CollEntry 3 }
-- 802.3
dot3Tests OBJECT IDENTIFIER ::= { dot3 6 }
dot3Errors OBJECT IDENTIFIER ::= { dot3 7 }
-- TDR
dot3TestTdr OBJECT-
STATUS
DESCRIPTION "The Time-Domain Reflectometry (TDR) test
specific to ethernet-like interfaces of
10Base5 and 10Base2. The TDR value may
useful in determining the approximate
to a cable fault. It is advisable to
Flick & Johnson Standards Track [Page 20]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
this test to check for a consistent
TDR value, to verify that there is a fault
A TDR test returns as its result the
interval, measured in 10 MHz ticks or 100
units, between the start of TDR
transmission and the subsequent detection of
collision or deassertion of carrier.
successful completion of a TDR test, the
is stored as the value of an
instance of an appropriate vendor specific
object, and the OBJECT IDENTIFIER of
instance is stored in the appropriate
of the appropriate test result code
(thereby indicating where the result has
stored)."
::= { dot3Tests 1 }
-- Loopback
dot3TestLoopBack OBJECT-
STATUS
DESCRIPTION "This test configures the MAC chip and
an internal loopback test of memory, data paths
and the MAC chip logic. This loopback test
only be executed if the interface is offline
Once the test has completed, the MAC chip
be reinitialized for network operation, but
should remain offline
If an error occurs during a test,
appropriate test result object will be
to indicate a failure. The two
IDENTIFIER values dot3ErrorInitError
dot3ErrorLoopbackError may be used to
more information as values for an
test result code object."
::= { dot3Tests 2 }
dot3ErrorInitError OBJECT-
STATUS
DESCRIPTION "Couldn't initialize MAC chip for test."
::= { dot3Errors 1 }
dot3ErrorLoopbackError OBJECT-
STATUS
DESCRIPTION "Expected data not received (or not
correctly) in loopback test."
Flick & Johnson Standards Track [Page 21]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
::= { dot3Errors 2 }
-- 802.3 Hardware
-- The object dot3StatsEtherChipSet is provided
-- identify the MAC hardware used to communicate on
-- interface. The following hardware chipsets
-- registered
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
dot3ChipSetAMD7990 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am7990 Local Area
Controller for Ethernet (LANCE)."
::= { dot3ChipSetAMD 1 }
dot3ChipSetAMD79900 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79900 chip."
::= { dot3ChipSetAMD 2 }
dot3ChipSetAMD79C940 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C940 Media Access
for Ethernet (MACE)."
::= { dot3ChipSetAMD 3 }
dot3ChipSetAMD79C90 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C90 CMOS Local Area
Controller for Ethernet (C-LANCE)."
::= { dot3ChipSetAMD 4 }
dot3ChipSetAMD79C960 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C960 PCnet-ISA Single
Ethernet Controller for ISA."
::= { dot3ChipSetAMD 5 }
Flick & Johnson Standards Track [Page 22]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
dot3ChipSetAMD79C961 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C961 PCnet-ISA+ Single
Plug & Play Full-Duplex Ethernet
for ISA."
::= { dot3ChipSetAMD 6 }
dot3ChipSetAMD79C961A OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C961A PCnet-ISA II Single
Plug & Play Full-Duplex Ethernet
for ISA."
::= { dot3ChipSetAMD 7 }
dot3ChipSetAMD79C965 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C965 PCnet-32 Single
Ethernet Controller for PCI."
::= { dot3ChipSetAMD 8 }
dot3ChipSetAMD79C970 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C970 PCnet PCI Single
Ethernet Controller for PCI Local Bus."
::= { dot3ChipSetAMD 9 }
dot3ChipSetAMD79C970A OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices AM79C970A PCnet PCI II Single
Full-Duplex Ethernet Controller for PCI
Bus."
::= { dot3ChipSetAMD 10 }
dot3ChipSetAMD79C971 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C971 PCnet-FAST Single
Full-Duplex 10/100 Mbps Ethernet Controller
PCI Local Bus."
::= { dot3ChipSetAMD 11 }
dot3ChipSetAMD79C972 OBJECT-
Flick & Johnson Standards Track [Page 23]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
STATUS
DESCRIPTION "The authoritative identifier for the
Micro Devices Am79C972 PCnet-FAST+
10/100 Mbps PCI Ethernet Controller with
Support."
::= { dot3ChipSetAMD 12 }
dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
dot3ChipSetIntel82586 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82586 IEEE 802.3 Ethernet LAN Coprocessor."
::= { dot3ChipSetIntel 1 }
dot3ChipSetIntel82596 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82596 High-Performance 32-Bit Local Area
Coprocessor."
::= { dot3ChipSetIntel 2 }
dot3ChipSetIntel82595 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82595 High Integration Ethernet Controller."
::= { dot3ChipSetIntel 3 }
dot3ChipSetIntel82557 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82557 Fast Ethernet PCI Bus Lan Controller."
::= { dot3ChipSetIntel 4 }
dot3ChipSetIntel82558 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
82558 Fast Ethernet PCI Bus LAN Controller
Integrated PHY."
::= { dot3ChipSetIntel 5 }
dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
dot3ChipSetSeeq8003 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
8003 chip set."
::= { dot3ChipSetSeeq 1 }
Flick & Johnson Standards Track [Page 24]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
dot3ChipSetSeeq80C03 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
80C03 Full-Duplex CMOS Ethernet Data
Controller (MAC)."
::= { dot3ChipSetSeeq 2 }
dot3ChipSetSeeq84C30 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 84C30 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 3 }
dot3ChipSetSeeq8431 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 8431 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 4 }
dot3ChipSetSeeq80C300 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
80C300 Full-Duplex CMOS Ethernet 10/100
Mbit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 5 }
dot3ChipSetSeeq84C300 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 84C300 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 6 }
dot3ChipSetSeeq84301 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 84301 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 7 }
dot3ChipSetSeeq84302 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
4-Port 84302 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 8 }
dot3ChipSetSeeq8100 OBJECT-
STATUS
Flick & Johnson Standards Track [Page 25]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
DESCRIPTION "The authoritative identifier for the
8100 Gigabit Ethernet Controller (MAC & PCS)."
::= { dot3ChipSetSeeq 9 }
dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
dot3ChipSetNational8390 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP8390 Network
Controller."
::= { dot3ChipSetNational 1 }
dot3ChipSetNationalSonic OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83932 Systems-Oriented
Interface Controller (SONIC)."
::= { dot3ChipSetNational 2 }
dot3ChipSetNational83901 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83901 Serial Network
Controller (SNIC)."
::= { dot3ChipSetNational 3 }
dot3ChipSetNational83902 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83902 Serial Network
Controller for Twisted Pair (ST-NIC)."
::= { dot3ChipSetNational 4 }
dot3ChipSetNational83905 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83905 AT Local Area
Twisted-Pair Interface (AT/LANTIC)."
::= { dot3ChipSetNational 5 }
dot3ChipSetNational83907 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83907 AT Twisted-Pair
Coaxial Network Interface
(AT/LANTIC II)."
::= { dot3ChipSetNational 6 }
Flick & Johnson Standards Track [Page 26]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
dot3ChipSetNational83916 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83916 Systems-Oriented
Interface Controller (SONIC-16)."
::= { dot3ChipSetNational 7 }
dot3ChipSetNational83934 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83934 Systems-Oriented
Interface Controller with Twisted Pair
(SONIC-T)."
::= { dot3ChipSetNational 8 }
dot3ChipSetNational83936 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DP83936AVUL Full-Duplex Systems
Oriented Network Interface Controller
Twisted Pair Interface (SONIC-T)."
::= { dot3ChipSetNational 9 }
dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
dot3ChipSetFujitsu86950 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
86950 chip."
::= { dot3ChipSetFujitsu 1 }
dot3ChipSetFujitsu86960 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
MB86960 Network Interface Controller
Encoder/Decoder (NICE)."
::= { dot3ChipSetFujitsu 2 }
dot3ChipSetFujitsu86964 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
MB86964 Ethernet Controller with 10BASE-
Tranceiver."
::= { dot3ChipSetFujitsu 3 }
dot3ChipSetFujitsu86965A OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Flick & Johnson Standards Track [Page 27]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
MB86965A EtherCoupler Single-Chip
Controller."
::= { dot3ChipSetFujitsu 4 }
dot3ChipSetFujitsu86965B OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
MB86965B EtherCoupler Single-Chip
Controller (supports full-duplex)."
::= { dot3ChipSetFujitsu 5 }
dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 }
dot3ChipSetDigitalDC21040 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor DC21040 chip."
::= { dot3ChipSetDigital 1 }
dot3ChipSetDigital21041 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21041 PCI Ethernet
Controller."
::= { dot3ChipSetDigital 2 }
dot3ChipSetDigital21140 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21140 PCI Fast Ethernet
Controller."
::= { dot3ChipSetDigital 3 }
dot3ChipSetDigital21143 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21143 PCI/CardBus 10/100-Mb/
Ethernet LAN Controller."
::= { dot3ChipSetDigital 4 }
dot3ChipSetDigital21340 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21340 10/100-MB/s managed
port switch."
::= { dot3ChipSetDigital 5 }
dot3ChipSetDigital21440 OBJECT-
Flick & Johnson Standards Track [Page 28]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21440 Multiport 10/100
Ethernet Controller."
::= { dot3ChipSetDigital 6 }
dot3ChipSetDigital21540 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Semiconductor 21540 PCI/CardBus Ethernet
Controller with Modem Interface."
::= { dot3ChipSetDigital 7 }
dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 }
dot3ChipSetTIE100 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETE100 ThunderLAN PCI
Ethernet Controller."
::= { dot3ChipSetTI 1 }
dot3ChipSetTIE110 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETE110 ThunderLAN PCI 10BASE-
Ethernet Adapter."
::= { dot3ChipSetTI 2 }
dot3ChipSetTIX3100 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETX3100 Desktop
8/2."
::= { dot3ChipSetTI 3 }
dot3ChipSetTIX3150 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETX3150 ThunderSWITCH 12/3."
::= { dot3ChipSetTI 4 }
dot3ChipSetTIX3270 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Instruments TNETX3270 ThunderSWITCH 24/3."
::= { dot3ChipSetTI 5 }
Flick & Johnson Standards Track [Page 29]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 }
dot3ChipSetToshibaTC35815F OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
TC35815F PCI-Based 100/10Mbps
Controller."
::= { dot3ChipSetToshiba 1 }
dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 }
dot3ChipSetLucentATT1MX10 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technologies ATT1MX10 (Spinnaker) Quad MAC
Tranceiver for Ethernet Frame Switching."
::= { dot3ChipSetLucent 1 }
dot3ChipSetLucentLUC3M08 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technologies LUC3M08 Eight Ethernet MACs
10/100 Mbits/s Frame Switching."
::= { dot3ChipSetLucent 2 }
dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 }
dot3ChipSetGalileoGT48001 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48001A Switched
Controller."
::= { dot3ChipSetGalileo 1 }
dot3ChipSetGalileoGT48002 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48002A Switched Fast
Controller."
::= { dot3ChipSetGalileo 2 }
dot3ChipSetGalileoGT48004 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48004A Four Port Fast
Switch for Multiport 10/100BASE-X Systems."
::= { dot3ChipSetGalileo 3 }
Flick & Johnson Standards Track [Page 30]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
dot3ChipSetGalileoGT48207 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48207 Low-Cost 10 Port
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 4 }
dot3ChipSetGalileoGT48208 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48208 Advanced 10 Port
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 5 }
dot3ChipSetGalileoGT48212 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technology GT-48212 Advanced 14 Port
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 6 }
dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 }
dot3ChipSetJatoJT1001 OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
Technologies JT1001 GigEMAC
10/100/1000Mbps Ethernet Controller with
interface."
::= { dot3ChipSetJato 1 }
dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 }
dot3ChipSetXaQtiXQ11800FP OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
XQ11800FP XMAC II Gigabit Ethernet Media
Controller."
::= { dot3ChipSetXaQti 1 }
dot3ChipSetXaQtiXQ18110FP OBJECT-
STATUS
DESCRIPTION "The authoritative identifier for the
XQ18110FP GigaPower Protocol Accelerator."
::= { dot3ChipSetXaQti 2 }
-- For those chipsets not represented above, OBJECT
-- assignment is required in other documentation, e.g.,
Flick & Johnson Standards Track [Page 31]
RFC 2358 MIB for Ethernet-like Interface Types June 1998
-- assignment within that part of the registration
-- delegated to individual enterprises (see RFC 1155
-- RFC 1902).
--
-- In the future, management of chipset registrations may
-- delegated to the Internet Assigned Numbers Authority (IANA).
-- conformance
etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 }
etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 }
etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 }
-- 