draft-ietf-hubmib-etherif-mib-01.txt   draft-ietf-hubmib-etherif-mib-02.txt 
Hub MIB Working Group J. Johnson Hub MIB Working Group J. Flick
INTERNET DRAFT cisco Systems, Inc. INTERNET DRAFT Hewlett-Packard Company
November 1996 J. Johnson
RedBack Networks
F. Kastenholz
FTP Software, Inc.
November 1997
Definitions of Managed Objects for Definitions of Managed Objects for
the Ethernet-like Interface Types the Ethernet-like Interface Types
<draft-ietf-hubmib-etherif-mib-01.txt> <draft-ietf-hubmib-etherif-mib-02.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas,
its working groups. Note that other groups may also distribute working and its working groups. Note that other groups may also distribute
documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material time. It is inappropriate to use Internet-Drafts as reference
or to cite them other than as ``work in progress.'' material or to cite them other than as ``work in progress.''
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Copyright Notice
Copyright (C) The Internet Society (1997). All Rights Reserved.
Abstract Abstract
This memo is an extension to the SNMP MIB. It specifies an IAB This memo is an extension to the SNMP MIB. It specifies an IAB
standards track protocol for the Internet community, and requests standards track protocol for the Internet community, and requests
discussion and suggestions for improvements. The origin of this memo is discussion and suggestions for improvements. The origin of this memo
from RFC 1650 "Definitions of Managed Objects for the Ethernet-like is from RFC 1650 ''Definitions of Managed Objects for the Ethernet-
Interface Types using SMIv2." This memo extends that specification by like Interface Types using SMIv2.'' This memo extends that
including management information useful for the management of 100-BaseT specification by including management information useful for the
ethernet interfaces. management of 100BaseT ethernet interfaces.
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
hubmib@hprnd.rose.hp.com. hubmib@hprnd.rose.hp.com.
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) for This memo defines a portion of the Management Information Base (MIB)
use with network management protocols in the Internet community. In for use with network management protocols in the Internet community.
particular, it defines objects for managing ethernet-like interfaces. In particular, it defines objects for managing ethernet-like
interfaces.
This memo also includes a MIB module. This MIB module extends the list This memo also includes a MIB module. This MIB module extends the
of managed objects specified in the earlier version of this MIB: RFC1650 list of managed objects specified in the earlier version of this MIB:
[11]. 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 2. The SNMP Network Management Framework
The SNMP Network Management Framework consists of several components. The SNMP Network Management Framework consists of several components.
For the purpose of this specification, the applicable components of the For the purpose of this specification, the applicable components of
Framework are the SMI and related documents [2, 3, 4], which define the the Framework are the SMI and related documents [2, 3, 4], which
mechanisms used for describing and naming objects for the purpose of define the mechanisms used for describing and naming objects for the
management. purpose of management.
The Framework permits new objects to be defined for the purpose of The Framework permits new objects to be defined for the purpose of
experimentation and evaluation. experimentation and evaluation.
2.1. Object Definitions 2.1. Object Definitions
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. Objects in the MIB are defined the Management Information Base or MIB. Objects in the MIB are
using the subset of Abstract Syntax Notation One (ASN.1) [1] defined in defined using the subset of Abstract Syntax Notation One (ASN.1) [1]
the SMI [2]. In particular, each object object type is named by an defined in the SMI [2]. In particular, each object object type is
OBJECT IDENTIFIER, an administratively assigned name. The object type named by an OBJECT IDENTIFIER, an administratively assigned name.
together with an object instance serves to uniquely identify a specific The object type together with an object instance serves to uniquely
instantiation of the object. For human convenience, we often use a identify a specific instantiation of the object. For human
textual string, termed the descriptor, to refer to the object type. convenience, we often use a textual string, termed the descriptor, to
refer to the object type.
3. Change Log 3. Change Log
This section enumerates changes made to RFC 1650 to produce this This section enumerates changes made to RFC 1650 to produce this
document. document.
(1) The MODULE-IDENTITY has been updated to reflect the changes (1) The MODULE-IDENTITY has been updated to reflect the changes
in the MIB. in the MIB.
(2) A new object, dot3StatsSymbolErrors, has been added. (2) A new object, dot3StatsSymbolErrors, has been added.
skipping to change at page 3, line 14 skipping to change at page 3, line 19
(4) A new conformance group, etherStats100MbsGroup, has been (4) A new conformance group, etherStats100MbsGroup, has been
added. added.
(5) A new compliance statement, ether100MbsCompliance, has (5) A new compliance statement, ether100MbsCompliance, has
been added. been added.
(6) The Acknowledgements were extended to provide a more (6) The Acknowledgements were extended to provide a more
complete history of the origin of this document. complete history of the origin of this document.
(7) The discussion of ifType has 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) Comverted the dot3Tests, dot3Errors, and dot3ChipSets
OIDs to use the OBJECT-IDENTITY macro.
(12) An intellectual property notice and copyright notice
were added, as required by RFC 2026.
4. Overview 4. Overview
Instances of these object types represent attributes of an interface to Instances of these object types represent attributes of an interface
an ethernet-like communications medium. At present, ethernet-like media to an ethernet-like communications medium. At present, ethernet-like
are identified by the following values of the ifType object in the media are identified by the following values of the ifType object in
Interfaces MIB [12]: the Interfaces MIB [12]:
ethernet-csmacd(6) ethernetCsmacd(6)
iso88023-csmacd(7) iso88023Csmacd(7)
starLan(11) starLan(11)
fastEther(62)
fastEtherFX(69)
The definitions presented here are based on the IEEE 802.3 Layer The definitions presented here are based on the IEEE 802.3 Layer
Management Specification [5], as originally interpreted by Frank Management Specification [5], as originally interpreted by Frank
Kastenholz then of Interlan in [7]. Implementors of these MIB objects Kastenholz then of Interlan in [7]. Implementors of these MIB
should note that the IEEE document explicitly describes (in the form of objects should note that the IEEE document explicitly describes (in
Pascal pseudocode) when, where, and how various MAC attributes are the form of Pascal pseudocode) when, where, and how various MAC
measured. The IEEE document also describes the effects of MAC actions attributes are measured. The IEEE document also describes the
that may be invoked by manipulating instances of the MIB objects defined effects of MAC actions that may be invoked by manipulating instances
here. of the MIB objects defined here.
To the extent that some of the attributes defined in [5] are represented To the extent that some of the attributes defined in [5] are
by previously defined objects in the Internet-standard MIB or in the represented by previously defined objects in the Internet-standard
Interfaces Group Evolution MIB [12], such attributes are not redundantly MIB or in the Interfaces Group Evolution MIB [12], such attributes
represented by objects defined in this memo. Among the attributes are not redundantly represented by objects defined in this memo.
represented by objects defined in other memos are the number of octets Among the attributes represented by objects defined in other memos
transmitted or received on a particular interface, the number of frames are the number of octets transmitted or received on a particular
transmitted or received on a particular interface, the promiscuous interface, the number of frames transmitted or received on a
status of an interface, the MAC address of an interface, and multicast particular interface, the promiscuous status of an interface, the MAC
information associated with an interface. address of an interface, and multicast information associated with an
interface.
4.1. Relation to RFC 1213 4.1. Relation to MIB-2
This section applies only when this MIB is used in conjunction with the This section applies only when this MIB is used in conjunction with
"old" (i.e., pre-RFC 1573) interface group. the "old" (RFC 1213) interface group.
The relationship between an ethernet-like interface and an interface in The relationship between an ethernet-like interface and an interface
the context of the Internet-standard MIB is one-to-one. As such, the in the context of the Internet-standard MIB is one-to-one. As such,
value of an ifIndex object instance can be directly used to identify the value of an ifIndex object instance can be directly used to
corresponding instances of the objects defined herein. identify corresponding instances of the objects defined herein.
For agents which implement the (now deprecated) ifSpecific object, an For agents which implement the (now deprecated) ifSpecific object, an
instance of that object that is associated with an ethernet-like instance of that object that is associated with an ethernet-like
interface has the OBJECT IDENTIFIER value: interface has the OBJECT IDENTIFIER value:
dot3 OBJECT IDENTIFER ::= { transmission 7 } dot3 OBJECT IDENTIFER ::= { transmission 7 }
4.2. Relation to RFC 1573 4.2. Relation to the Interfaces MIB
RFC 1573, the Interface MIB Evolution, requires that any MIB which is an The Interface MIB [12] requires that any MIB which is an adjunct of
adjunct of the Interface MIB, clarify specific areas within the the Interface MIB clarify specific areas within the Interface MIB.
Interface MIB. These areas were intentionally left vague in RFC 1573 to These areas were intentionally left vague in the Interface MIB to
avoid over constraining the MIB, thereby precluding management of avoid over constraining the MIB, thereby precluding management of
certain media-types. certain media-types.
Section 3.3 of RFC 1573 enumerates several areas which a media- specific Section 3.3 of [12] enumerates several areas which a media-specific
MIB must clarify. Each of these areas is addressed in a following MIB must clarify. Each of these areas is addressed in a following
subsection. The implementor is referred to RFC 1573 in order to subsection. The implementor is referred to [12] in order to
understand the general intent of these areas. understand the general intent of these areas.
4.2.1. Layering Model 4.2.1. Layering Model
This MIB does not provide for layering. There are no sublayers. This MIB does not provide for layering. There are no sublayers.
EDITOR'S NOTE: EDITOR'S NOTE:
One could foresee the development of an 802.2 and enet-transceiver MIB. One could foresee the development of an 802.2 and enet-transceiver
They could be higher and lower sublayers, respectively. All that THIS MIB. They could be higher and lower sublayers, respectively. All
document should do is allude to the possibilities and urge the that THIS document should do is allude to the possibilities and urge
implementor to be aware of the possibility and that they may have the implementor to be aware of the possibility and that they may have
requirements which supersede the requirements in this document. requirements which supersede the requirements in this document.
4.2.2. Virtual Circuits 4.2.2. Virtual Circuits
This medium does not support virtual circuits and this area is not This medium does not support virtual circuits and this area is not
applicable to this MIB. applicable to this MIB.
4.2.3. ifTestTable 4.2.3. ifTestTable
This MIB defines two tests for media which are instrumented with this This MIB defines two tests for media which are instrumented with this
MIB; TDR and Loopback. Implementation of these tests is not required. MIB; TDR and Loopback. Implementation of these tests is not
Many common interface chips do not support one or both of these tests. required. Many common interface chips do not support one or both of
these tests.
These two tests are provided as a convenience, allowing a common method These two tests are provided as a convenience, allowing a common
to invoke the test. method to invoke the test.
Standard MIBs do not include objects in which to return the results of Standard MIBs do not include objects in which to return the results
the TDR test. Any needed objects MUST be provided in the vendor of the TDR test. Any needed objects MUST be provided in the vendor
specific MIB. specific MIB.
Note that the ifTestTable is now deprecated. Work is underway to
define a replacement MIB for system and interface testing. It is
expected that the tests defined in this document will be usable in
this replacement MIB.
4.2.4. ifRcvAddressTable 4.2.4. ifRcvAddressTable
This table contains all IEEE 802.3 addresses, unicast, multicast, and This table contains all IEEE 802.3 addresses, unicast, multicast, and
broadcast, for which this interface will receive packets and forward broadcast, for which this interface will receive packets and forward
them up to a higher layer entity for local consumption. The format of them up to a higher layer entity for local consumption. The format
the address, contained in ifRcvAddressAddress, is the same as for of the address, contained in ifRcvAddressAddress, is the same as for
ifPhysAddress. ifPhysAddress.
In the event that the interface is part of a MAC bridge, this table does In the event that the interface is part of a MAC bridge, this table
not include unicast addresses which are accepted for possible forwarding does not include unicast addresses which are accepted for possible
out some other port. This table is explicitly not intended to provide a forwarding out some other port. This table is explicitly not
bridge address filtering mechanism. intended to provide a bridge address filtering mechanism.
4.2.5. ifPhysAddress 4.2.5. ifPhysAddress
This object contains the IEEE 802.3 address which is placed in the This object contains the IEEE 802.3 address which is placed in the
source-address field of any Ethernet, Starlan, or IEEE 802.3 frames that source-address field of any Ethernet, Starlan, or IEEE 802.3 frames
originate at this interface. Usually this will be kept in ROM on the that originate at this interface. Usually this will be kept in ROM
interface hardware. Some systems may set this address via software. on the interface hardware. Some systems may set this address via
software.
In a system where there are several such addresses the designer has a In a system where there are several such addresses the designer has a
tougher choice. The address chosen should be the one most likely to be tougher choice. The address chosen should be the one most likely to
of use to network management (e.g. the address placed in ARP responses be of use to network management (e.g. the address placed in ARP
for systems which are primarily IP systems). responses for systems which are primarily IP systems).
If the designer truly can not chose, use of the factory- provided ROM If the designer truly can not chose, use of the factory- provided ROM
address is suggested. address is suggested.
If the address can not be determined, an octet string of zero length If the address can not be determined, an octet string of zero length
should be returned. should be returned.
The address is stored in binary in this object. The address is stored The address is stored in binary in this object. The address is
in "canonical" bit order, that is, the Group Bit is positioned as the stored in "canonical" bit order, that is, the Group Bit is positioned
low-order bit of the first octet. Thus, the first byte of a multicast as the low-order bit of the first octet. Thus, the first byte of a
address would have the bit 0x01 set. multicast address would have the bit 0x01 set.
4.2.6. ifType 4.2.6. ifType
This MIB applies to interfaces which have any of the following ifType This MIB applies to interfaces which have any of the following ifType
values: values:
ethernet-csmacd(6) ethernetCsmacd(6)
iso88023-csmacd(7) iso88023Csmacd(7)
starLan(11) starLan(11)
fastEther(62)
fastEtherFX(69)
Interfaces with any of the first three ifType values map to the It is RECOMMENDED that all Ethernet-like interfaces use an ifType of
EtherLike-MIB in the same manner. The EtherLike-MIB etherCompliance ethernetCsmacd(6) regardless of the speed that the interface is
compliance statement applies equally to all three types; there are no running or the link-layer encapsulation in use. iso88023Csmacd(7)
implementation differences. Similarly, interfaces with either of the and starLan(11) are supported for backwards compatability.
last two ifType values map to the EtherLike-MIB in the same manner. The
EtherLike-MIB ether100MbsCompliance compliance statement applies equally There are two other interface types defined in the IANAifType-MIB for
to both types; there are no implementation differences. 100 Mbit Ethernet. They are fastEther(62), and fastEtherFX(69).
This document takes the position that an Ethernet is an Ethernet, and
Ethernet interfaces SHOULD always have the same value of ifType.
Information on the particular flavor of Ethernet that an interface is
running is available from 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.
Interfaces with any of the supported ifType values map to the
EtherLike-MIB in the same manner. Which compliance statement an
interface should implement is dependent on the maximum speed
supported on the interface. 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. Similarly, the EtherLike-MIB
ether100MbsCompliance compliance statement applies to all Ethernet-
like interfaces whose maximum supported speed of 100Mbit/sec.
An interface that is capable of operating at 100Mbit/sec MUST
implement the ether100MbsCompliance compliance statement, even if it
is currently operating at a lower speed. Counters in the
ether100MbsCompliance compliance statement that only apply to 100
Mbit interfaces would simply not increment when the interface is
operating at a lower speed.
4.2.7. Specific Interface MIB Objects
The following table provides specific implementation guidelines 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 4.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 4.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 4.2.1.
ifStackLowerLayer
ifStackStatus
ifRcvAddressAddress Refer to section 4.2.4.
ifRcvAddressStatus
ifRcvAddressType
4.3. Relation to the 802.3 MAU MIB
Support for the mauModIfCompl compliance statement of the MAU-MIB
[14] is REQUIRED for Ethernet-like interfaces. This MIB is needed in
order to allow applications to determine the current MAU type in use
by the interface. The MAU type indicates not only the media type in
use, but also indicates whether the interface is operating in half-
duplex or full-duplex mode. Implementing this MIB module without
implementing the MAU-MIB would leave applications with no standard
way to determine the duplex mode of the interface.
4.4. Mapping of IEEE 802.3 Managed Objects
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 dot3StatsSymbolErrors
The following IEEE 802.3 managed objects have been removed from this
MIB module as a result of implementation feedback:
oMacEntity
.aFramesWithExcessiveDeferral
.aInRangeLengthErrors
.aOutOfRangeLengthField
.aMACEnableStatus
.aTransmitEnableStatus
.aMulticastReceiveStatus
.acInitializeMAC
Please see [15] for the detailed reasoning on why these objects were
removed.
5. Definitions 5. Definitions
EtherLike-MIB DEFINITIONS ::= BEGIN EtherLike-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Counter32, mib-2 FROM SNMPv2-SMI MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF Counter32, mib-2, transmission
ifIndex, InterfaceIndex FROM IF-MIB; FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF
ifIndex, InterfaceIndex
FROM IF-MIB;
etherMIB MODULE-IDENTITY etherMIB MODULE-IDENTITY
LAST-UPDATED "9606052300Z" LAST-UPDATED "9711102157Z" -- November 10, 1997
ORGANIZATION "IETF 802.3 Hub MIB Working Group" ORGANIZATION "IETF 802.3 Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-mail: hubmib@hprnd.rose.hp.com "WG E-mail: hubmib@hprnd.rose.hp.com
Chair: Dan Romascanu
Postal: Madge Networks
Atidum Technology Park, Bldg. 3
Tel Aviv 61131
Israel
Tel: +972 3 645 8414
E-mail: dromasca@madge.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 Editor: Jeffrey Johnson
Postal: cisco Systems, Inc. Postal: RedBack Networks
170 W.Tasman Drive 2570 North First Street, Suite 410
San Jose, CA, 94015 San Jose, CA, 95131
USA USA
Tel: +1 408 526 7789 Tel: +1 408 571 2699
E-Mail: jjohnson@cisco.com" Fax: +1 408 571 2698
DESCRIPTION E-Mail: jeff@redbacknetworks.com"
"The MIB module to describe generic objects for
DESCRIPTION "The MIB module to describe generic objects for
Ethernet-like network interfaces. This MIB is an Ethernet-like network interfaces. This MIB is an
updated version of the Ethernet-like MIB in RFC updated version of the Ethernet-like MIB in RFC
1650." 1650."
REVISION "9606052300Z"
DESCRIPTION REVISION "9711102157Z"
"Updated to include support for 100 Mb/sec interfaces." DESCRIPTION "Updated to include support for 100 Mb/sec
interfaces."
REVISION "9402030400Z"
DESCRIPTION "Version published as RFC 1650."
::= { mib-2 35 } ::= { mib-2 35 }
etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 } etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 }
dot3 OBJECT IDENTIFIER ::= { transmission 7 } dot3 OBJECT IDENTIFIER ::= { transmission 7 }
-- the Ethernet-like Statistics group -- the Ethernet-like Statistics group
dot3StatsTable OBJECT-TYPE dot3StatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3StatsEntry SYNTAX SEQUENCE OF Dot3StatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION "Statistics for a collection of ethernet-like
"Statistics for a collection of ethernet-like
interfaces attached to a particular system." interfaces attached to a particular system."
::= { dot3 2 } ::= { dot3 2 }
dot3StatsEntry OBJECT-TYPE dot3StatsEntry OBJECT-TYPE
SYNTAX Dot3StatsEntry SYNTAX Dot3StatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION "Statistics for a particular interface to an
"Statistics for a particular interface to an
ethernet-like medium." ethernet-like medium."
INDEX { dot3StatsIndex } INDEX { dot3StatsIndex }
::= { dot3StatsTable 1 } ::= { dot3StatsTable 1 }
Dot3StatsEntry ::= SEQUENCE { Dot3StatsEntry ::=
SEQUENCE {
dot3StatsIndex InterfaceIndex, dot3StatsIndex InterfaceIndex,
dot3StatsAlignmentErrors Counter32, dot3StatsAlignmentErrors Counter32,
dot3StatsFCSErrors Counter32, dot3StatsFCSErrors Counter32,
dot3StatsSingleCollisionFrames Counter32, dot3StatsSingleCollisionFrames Counter32,
dot3StatsMultipleCollisionFrames Counter32, dot3StatsMultipleCollisionFrames Counter32,
dot3StatsSQETestErrors Counter32, dot3StatsSQETestErrors Counter32,
dot3StatsDeferredTransmissions Counter32, dot3StatsDeferredTransmissions Counter32,
dot3StatsLateCollisions Counter32, dot3StatsLateCollisions Counter32,
dot3StatsExcessiveCollisions Counter32, dot3StatsExcessiveCollisions Counter32,
dot3StatsInternalMacTransmitErrors Counter32, dot3StatsInternalMacTransmitErrors Counter32,
skipping to change at page 8, line 36 skipping to change at page 15, line 12
dot3StatsFrameTooLongs Counter32, dot3StatsFrameTooLongs Counter32,
dot3StatsInternalMacReceiveErrors Counter32, dot3StatsInternalMacReceiveErrors Counter32,
dot3StatsEtherChipSet OBJECT IDENTIFIER, dot3StatsEtherChipSet OBJECT IDENTIFIER,
dot3StatsSymbolErrors Counter32 dot3StatsSymbolErrors Counter32
} }
dot3StatsIndex OBJECT-TYPE dot3StatsIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "An index value that uniquely identifies an
"An index value that uniquely identifies an
interface to an ethernet-like medium. The interface to an ethernet-like medium. The
interface identified by a particular value of interface identified by a particular value of
this index is the same interface as identified this index is the same interface as identified
by the same value of ifIndex." by the same value of ifIndex."
::= { dot3StatsEntry 1 } ::= { dot3StatsEntry 1 }
dot3StatsAlignmentErrors OBJECT-TYPE dot3StatsAlignmentErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of frames received on a particular
"A count of frames received on a particular
interface that are not an integral number of interface that are not an integral number of
octets in length and do not pass the FCS check. octets in length and do not pass the FCS check.
The count represented by an instance of this The count represented by an instance of this
object is incremented when the alignmentError object is incremented when the alignmentError
status is returned by the MAC service to the status is returned by the MAC service to the
LLC (or other MAC user). Received frames for LLC (or other MAC user). Received frames for
which multiple error conditions obtain are, which multiple error conditions obtain are,
according to the conventions of IEEE 802.3 according to the conventions of IEEE 802.3
Layer Management, counted exclusively according Layer Management, counted exclusively according
to the error status presented to the LLC." to the error status presented to the LLC."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 2 } ::= { dot3StatsEntry 2 }
dot3StatsFCSErrors OBJECT-TYPE dot3StatsFCSErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of frames received on a particular
"A count of frames received on a particular
interface that are an integral number of octets interface that are an integral number of octets
in length but do not pass the FCS check. in length but do not pass the FCS check.
The count represented by an instance of this The count represented by an instance of this
object is incremented when the frameCheckError object is incremented when the frameCheckError
status is returned by the MAC service to the status is returned by the MAC service to the
LLC (or other MAC user). Received frames for LLC (or other MAC user). Received frames for
which multiple error conditions obtain are, which multiple error conditions obtain are,
according to the conventions of IEEE 802.3 according to the conventions of IEEE 802.3
Layer Management, counted exclusively according Layer Management, counted exclusively according
to the error status presented to the LLC." to the error status presented to the LLC."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 3 } ::= { dot3StatsEntry 3 }
dot3StatsSingleCollisionFrames OBJECT-TYPE dot3StatsSingleCollisionFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of successfully transmitted frames on
"A count of successfully transmitted frames on
a particular interface for which transmission a particular interface for which transmission
is inhibited by exactly one collision. is inhibited by exactly one collision.
A frame that is counted by an instance of this A frame that is counted by an instance of this
object is also counted by the corresponding object is also counted by the corresponding
instance of either the ifOutUcastPkts, instance of either the ifOutUcastPkts,
ifOutMulticastPkts, or ifOutBroadcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts,
and is not counted by the corresponding and is not counted by the corresponding
instance of the dot3StatsMultipleCollisionFrames instance of the dot3StatsMultipleCollisionFrames
object." object."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 4 } ::= { dot3StatsEntry 4 }
dot3StatsMultipleCollisionFrames OBJECT-TYPE dot3StatsMultipleCollisionFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of successfully transmitted frames on
"A count of successfully transmitted frames on
a particular interface for which transmission a particular interface for which transmission
is inhibited by more than one collision. is inhibited by more than one collision.
A frame that is counted by an instance of this A frame that is counted by an instance of this
object is also counted by the corresponding object is also counted by the corresponding
instance of either the ifOutUcastPkts, instance of either the ifOutUcastPkts,
ifOutMulticastPkts, or ifOutBroadcastPkts, ifOutMulticastPkts, or ifOutBroadcastPkts,
and is not counted by the corresponding and is not counted by the corresponding
instance of the dot3StatsSingleCollisionFrames instance of the dot3StatsSingleCollisionFrames
object." object."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 5 } ::= { dot3StatsEntry 5 }
dot3StatsSQETestErrors OBJECT-TYPE dot3StatsSQETestErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of times that the SQE TEST ERROR
"A count of times that the SQE TEST ERROR
message is generated by the PLS sublayer for a message is generated by the PLS sublayer for a
particular interface. The SQE TEST ERROR particular interface. The SQE TEST ERROR
message is defined in section 7.2.2.2.4 of message is defined in section 7.2.2.2.4 of
ANSI/IEEE 802.3-1985 and its generation is ANSI/IEEE 802.3-1985 and its generation is
described in section 7.2.4.6 of the same described in section 7.2.4.6 of the same
document." document."
REFERENCE REFERENCE "ANSI/IEEE Std 802.3-1985 Carrier Sense
"ANSI/IEEE Std 802.3-1985 Carrier Sense
Multiple Access with Collision Detection Access Multiple Access with Collision Detection Access
Method and Physical Layer Specifications" Method and Physical Layer Specifications"
::= { dot3StatsEntry 6 } ::= { dot3StatsEntry 6 }
dot3StatsDeferredTransmissions OBJECT-TYPE dot3StatsDeferredTransmissions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of frames for which the first
"A count of frames for which the first
transmission attempt on a particular interface transmission attempt on a particular interface
is delayed because the medium is busy. is delayed because the medium is busy.
The count represented by an instance of this The count represented by an instance of this
object does not include frames involved in object does not include frames involved in
collisions." collisions."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 7 } ::= { dot3StatsEntry 7 }
dot3StatsLateCollisions OBJECT-TYPE dot3StatsLateCollisions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "The number of times that a collision is
"The number of times that a collision is
detected on a particular interface later than detected on a particular interface later than
512 bit-times into the transmission of a 512 bit-times into the transmission of a
packet. packet.
Five hundred and twelve bit-times corresponds Five hundred and twelve bit-times corresponds
to 51.2 microseconds on a 10 Mbit/s system. A to 51.2 microseconds on a 10 Mbit/s system. A
(late) collision included in a count (late) collision included in a count
represented by an instance of this object is represented by an instance of this object is
also considered as a (generic) collision for also considered as a (generic) collision for
purposes of other collision-related purposes of other collision-related
statistics." statistics."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 8 } ::= { dot3StatsEntry 8 }
dot3StatsExcessiveCollisions OBJECT-TYPE dot3StatsExcessiveCollisions OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of frames for which transmission on a
"A count of frames for which transmission on a
particular interface fails due to excessive particular interface fails due to excessive
collisions." collisions."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 9 } ::= { dot3StatsEntry 9 }
dot3StatsInternalMacTransmitErrors OBJECT-TYPE dot3StatsInternalMacTransmitErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of frames for which transmission on a
"A count of frames for which transmission on a
particular interface fails due to an internal particular interface fails due to an internal
MAC sublayer transmit error. A frame is only MAC sublayer transmit error. A frame is only
counted by an instance of this object if it is counted by an instance of this object if it is
not counted by the corresponding instance of not counted by the corresponding instance of
either the dot3StatsLateCollisions object, the either the dot3StatsLateCollisions object, the
dot3StatsExcessiveCollisions object, or the dot3StatsExcessiveCollisions object, or the
dot3StatsCarrierSenseErrors object. dot3StatsCarrierSenseErrors object.
The precise meaning of the count represented by The precise meaning of the count represented by
an instance of this object is implementation- an instance of this object is implementation-
specific. In particular, an instance of this specific. In particular, an instance of this
object may represent a count of transmission object may represent a count of transmission
errors on a particular interface that are not errors on a particular interface that are not
otherwise counted." otherwise counted."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 10 } ::= { dot3StatsEntry 10 }
dot3StatsCarrierSenseErrors OBJECT-TYPE dot3StatsCarrierSenseErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "The number of times that the carrier sense
"The number of times that the carrier sense
condition was lost or never asserted when condition was lost or never asserted when
attempting to transmit a frame on a particular attempting to transmit a frame on a particular
interface. interface.
The count represented by an instance of this The count represented by an instance of this
object is incremented at most once per object is incremented at most once per
transmission attempt, even if the carrier sense transmission attempt, even if the carrier sense
condition fluctuates during a transmission condition fluctuates during a transmission
attempt." attempt."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 11 } ::= { dot3StatsEntry 11 }
-- { dot3StatsEntry 12 } is not assigned -- { dot3StatsEntry 12 } is not assigned
dot3StatsFrameTooLongs OBJECT-TYPE dot3StatsFrameTooLongs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of frames received on a particular
"A count of frames received on a particular
interface that exceed the maximum permitted interface that exceed the maximum permitted
frame size. frame size.
The count represented by an instance of this The count represented by an instance of this
object is incremented when the frameTooLong object is incremented when the frameTooLong
status is returned by the MAC service to the status is returned by the MAC service to the
LLC (or other MAC user). Received frames for LLC (or other MAC user). Received frames for
which multiple error conditions obtain are, which multiple error conditions obtain are,
according to the conventions of IEEE 802.3 according to the conventions of IEEE 802.3
Layer Management, counted exclusively according Layer Management, counted exclusively according
to the error status presented to the LLC." to the error status presented to the LLC."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 13 } ::= { dot3StatsEntry 13 }
-- { dot3StatsEntry 14 } is not assigned -- { dot3StatsEntry 14 } is not assigned
-- { dot3StatsEntry 15 } is not assigned -- { dot3StatsEntry 15 } is not assigned
dot3StatsInternalMacReceiveErrors OBJECT-TYPE dot3StatsInternalMacReceiveErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of frames for which reception on a
"A count of frames for which reception on a
particular interface fails due to an internal particular interface fails due to an internal
MAC sublayer receive error. A frame is only MAC sublayer receive error. A frame is only
counted by an instance of this object if it is counted by an instance of this object if it is
not counted by the corresponding instance of not counted by the corresponding instance of
either the dot3StatsFrameTooLongs object, the either the dot3StatsFrameTooLongs object, the
dot3StatsAlignmentErrors object, or the dot3StatsAlignmentErrors object, or the
dot3StatsFCSErrors object. dot3StatsFCSErrors object.
The precise meaning of the count represented by The precise meaning of the count represented by
an instance of this object is implementation- an instance of this object is implementation-
specific. In particular, an instance of this specific. In particular, an instance of this
object may represent a count of receive errors object may represent a count of receive errors
on a particular interface that are not on a particular interface that are not
otherwise counted." otherwise counted."
REFERENCE REFERENCE "IEEE 802.3 Layer Management"
"IEEE 802.3 Layer Management"
::= { dot3StatsEntry 16 } ::= { dot3StatsEntry 16 }
dot3StatsEtherChipSet OBJECT-TYPE dot3StatsEtherChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "This object contains an OBJECT IDENTIFIER
"This object contains an OBJECT IDENTIFIER
which identifies the chipset used to which identifies the chipset used to
realize the interface. Ethernet-like realize the interface. Ethernet-like
interfaces are typically built out of interfaces are typically built out of
several different chips. The MIB implementor several different chips. The MIB implementor
is presented with a decision of which chip is presented with a decision of which chip
to identify via this object. The implementor to identify via this object. The implementor
should identify the chip which is usually should identify the chip which is usually
called the Medium Access Control chip. called the Medium Access Control chip.
If no such chip is easily identifiable, If no such chip is easily identifiable,
the implementor should identify the chip the implementor should identify the chip
skipping to change at page 14, line 29 skipping to change at page 20, line 28
statistics and the chip generating statistics and the chip generating
them, giving it the ability to take them, giving it the ability to take
into account any known anomalies into account any known anomalies
in the chip." in the chip."
::= { dot3StatsEntry 17 } ::= { dot3StatsEntry 17 }
dot3StatsSymbolErrors OBJECT-TYPE dot3StatsSymbolErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "The number of times there was an invalid data
"The number of times there was an invalid data symbol symbol when a valid carrier was present on a
when a valid carrier was present on a particular particular interface.
interface.
The count represented by an instance of this The count represented by an instance of this
object is incremented at most once per object is incremented at most once per carrier
carrier event, even if multiple symbol event, even if multiple symbol errors occur
errors occur during the carrier event." during the carrier event."
REFERENCE REFERENCE "IEEE 802.3u-1995 10 & 100 Mb/s Management"
"IEEE 802.3u-1995 10 & 100 Mb/s Management"
::= { dot3StatsEntry 18 } ::= { dot3StatsEntry 18 }
-- the Ethernet-like Collision Statistics group -- the Ethernet-like Collision Statistics group
-- Implementation of this group is optional; it is appropriate -- Implementation of this group is optional; it is appropriate
-- for all systems which have the necessary metering -- for all systems which have the necessary metering
dot3CollTable OBJECT-TYPE dot3CollTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3CollEntry SYNTAX SEQUENCE OF Dot3CollEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A collection of collision histograms for a
"A collection of collision histograms for a
particular set of interfaces." particular set of interfaces."
::= { dot3 5 } ::= { dot3 5 }
dot3CollEntry OBJECT-TYPE dot3CollEntry OBJECT-TYPE
SYNTAX Dot3CollEntry SYNTAX Dot3CollEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A cell in the histogram of per-frame
"A cell in the histogram of per-frame
collisions for a particular interface. An collisions for a particular interface. An
instance of this object represents the instance of this object represents the
frequency of individual MAC frames for which frequency of individual MAC frames for which
the transmission (successful or otherwise) on a the transmission (successful or otherwise) on a
particular interface is accompanied by a particular interface is accompanied by a
particular number of media collisions." particular number of media collisions."
INDEX { ifIndex, dot3CollCount } INDEX { ifIndex, dot3CollCount }
::= { dot3CollTable 1 } ::= { dot3CollTable 1 }
Dot3CollEntry ::= SEQUENCE { Dot3CollEntry ::=
SEQUENCE {
dot3CollCount INTEGER, dot3CollCount INTEGER,
dot3CollFrequencies Counter32 dot3CollFrequencies Counter32
} }
-- { dot3CollEntry 1 } is no longer in use -- { dot3CollEntry 1 } is no longer in use
dot3CollCount OBJECT-TYPE dot3CollCount OBJECT-TYPE
SYNTAX INTEGER (1..16) SYNTAX INTEGER (1..16)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION "The number of per-frame media collisions for
"The number of per-frame media collisions for
which a particular collision histogram cell which a particular collision histogram cell
represents the frequency on a particular represents the frequency on a particular
interface." interface."
::= { dot3CollEntry 2 } ::= { dot3CollEntry 2 }
dot3CollFrequencies OBJECT-TYPE dot3CollFrequencies OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A count of individual MAC frames for which the
"A count of individual MAC frames for which the
transmission (successful or otherwise) on a transmission (successful or otherwise) on a
particular interface occurs after the particular interface occurs after the
frame has experienced exactly the number frame has experienced exactly the number
of collisions in the associated of collisions in the associated
dot3CollCount object. dot3CollCount object.
For example, a frame which is transmitted For example, a frame which is transmitted
on interface 77 after experiencing on interface 77 after experiencing
exactly 4 collisions would be indicated exactly 4 collisions would be indicated
by incrementing only dot3CollFrequencies.77.4. by incrementing only dot3CollFrequencies.77.4.
skipping to change at page 16, line 23 skipping to change at page 22, line 17
::= { dot3CollEntry 3 } ::= { dot3CollEntry 3 }
-- 802.3 Tests -- 802.3 Tests
dot3Tests OBJECT IDENTIFIER ::= { dot3 6 } dot3Tests OBJECT IDENTIFIER ::= { dot3 6 }
dot3Errors OBJECT IDENTIFIER ::= { dot3 7 } dot3Errors OBJECT IDENTIFIER ::= { dot3 7 }
-- TDR Test -- TDR Test
-- The Time-Domain Reflectometry (TDR) test is specific dot3TestTdr OBJECT-IDENTITY
-- to ethernet-like interfaces with the exception of STATUS current
-- 10BaseT and 10BaseF. The TDR value may be useful DESCRIPTION "The Time-Domain Reflectometry (TDR) test is
-- in determining the approximate distance to a cable fault. specific to ethernet-like interfaces of type
-- It is advisable to repeat this test to check for a 10Base5 and 10Base2. The TDR value may be
-- consistent resulting TDR value, to verify that there useful in determining the approximate distance
-- is a fault. to a cable fault. It is advisable to repeat
this test to check for a consistent resulting
dot3TestTdr OBJECT IDENTIFIER ::= { dot3Tests 1 } TDR value, to verify that there is a fault.
-- A TDR test returns as its result the time interval, A TDR test returns as its result the time
-- measured in 10 MHz ticks or 100 nsec units, between interval, measured in 10 MHz ticks or 100 nsec
-- the start of TDR test transmission and the subsequent units, between the start of TDR test
-- detection of a collision or deassertion of carrier. On transmission and the subsequent detection of a
-- successful completion of a TDR test, the result is collision or deassertion of carrier. On
-- stored as the value of the appropriate instance of the successful completion of a TDR test, the result
-- MIB object dot3TestTdrValue, and the OBJECT IDENTIFIER is stored as the value of an appropriate
-- of that instance is stored in the corresponding instance instance of an appropriate vendor specific MIB
-- of ifExtnsTestCode (thereby indicating where the object, and the OBJECT IDENTIFIER of that
-- result has been stored). 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 -- Loopback Test
-- Another test is the full-duplex loopback test. dot3TestLoopBack OBJECT-IDENTITY
-- This test configures the MAC chip and executes STATUS current
-- an internal loopback test of memory, data paths, DESCRIPTION "This test configures the MAC chip and executes
-- and the MAC chip logic. This loopback test can an internal loopback test of memory, data paths,
-- only be executed if the interface is offline. and the MAC chip logic. This loopback test can
-- Once the test has completed, the MAC chip should only be executed if the interface is offline.
-- be reinitialized for network operation, but it Once the test has completed, the MAC chip should
-- should remain offline. be reinitialized for network operation, but it
should remain offline.
dot3TestLoopBack OBJECT IDENTIFIER ::= { dot3Tests 2 }
-- If an error occurs during a test, the object If an error occurs during a test, the
-- ifTestResult (defined in RFC1573) will be set appropriate test result object will be set
-- to failed(7). The following two OBJECT to indicate a failure. The two OBJECT
-- IDENTIFIERs may be used to provided more IDENTIFIER values dot3ErrorInitError and
-- information as values for ifTestCode. dot3ErrorLoopbackError may be used to provided
more information as values for an appropriate
test result code object."
::= { dot3Tests 2 }
-- couldn't initialize MAC chip for test dot3ErrorInitError OBJECT-IDENTITY
dot3ErrorInitError OBJECT IDENTIFIER ::= { dot3Errors 1 } STATUS current
DESCRIPTION "Couldn't initialize MAC chip for test."
::= { dot3Errors 1 }
-- expected data not received (or not dot3ErrorLoopbackError OBJECT-IDENTITY
-- received correctly) in loopback test STATUS current
dot3ErrorLoopbackError OBJECT IDENTIFIER ::= { dot3Errors 2 } DESCRIPTION "Expected data not received (or not received
correctly) in loopback test."
::= { dot3Errors 2 }
-- RFC1573 does away with the interface chipset object.
-- The following OBJECT IDENTIFIER definitions are
-- retained for purposes of backwards compatibility
-- with pre-RFC1573 systems.
-- 802.3 Hardware Chipsets -- 802.3 Hardware Chipsets
-- The object ifExtnsChipSet is provided in RFC1229 to -- The object dot3StatsEtherChipSet is provided to
-- identify the MAC hardware used to communicate on an -- identify the MAC hardware used to communicate on an
-- interface. The following hardware chipsets are -- interface. The following hardware chipsets are
-- provided for 802.3: -- provided:
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 } dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 } dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
dot3ChipSetAMD7990 OBJECT IDENTIFIER ::= { dot3ChipSetAMD 1 }
dot3ChipSetAMD79900 OBJECT IDENTIFIER ::= { dot3ChipSetAMD 2 } dot3ChipSetAMD7990 OBJECT-IDENTITY
dot3ChipSetAMD79C940 OBJECT IDENTIFIER ::= { dot3ChipSetAMD 3 } 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 }
dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 } dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
dot3ChipSetIntel82586 OBJECT IDENTIFIER ::= { dot3ChipSetIntel 1 }
dot3ChipSetIntel82596 OBJECT IDENTIFIER ::= { dot3ChipSetIntel 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 }
dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 } dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
dot3ChipSetSeeq8003 OBJECT IDENTIFIER ::= { dot3ChipSetSeeq 1 }
dot3ChipSetSeeq8003 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
8003 chip set."
::= { dot3ChipSetSeeq 1 }
dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 } dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
dot3ChipSetNational8390 OBJECT IDENTIFIER ::=
{ dot3ChipSetNational 1 } dot3ChipSetNational8390 OBJECT-IDENTITY
dot3ChipSetNationalSonic OBJECT IDENTIFIER ::= STATUS current
{ dot3ChipSetNational 2 } 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 }
dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 } dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
dot3ChipSetFujitsu86950 OBJECT IDENTIFIER ::=
{ dot3ChipSetFujitsu 1 } dot3ChipSetFujitsu86950 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
86950 chip."
::= { dot3ChipSetFujitsu 1 }
dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 } dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 }
dot3ChipSetDigitalDC21040 OBJECT IDENTIFIER ::=
{ dot3ChipSetDigital 1 } dot3ChipSetDigitalDC21040 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
DC21040 chip."
::= { dot3ChipSetDigital 1 }
-- For those chipsets not represented above, OBJECT IDENTIFIER -- For those chipsets not represented above, OBJECT IDENTIFIER
-- assignment is required in other documentation, e.g., assignment -- assignment is required in other documentation, e.g.,
-- within that part of the registration tree delegated to -- assignment within that part of the registration tree
-- individual enterprises (see RFC1155). -- deletaged to individual enterprises (see RFC1155).
-- conformance information -- conformance information
etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 } etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 }
etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 } etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 }
etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 } etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 }
-- compliance statements -- compliance statements
etherCompliance MODULE-COMPLIANCE etherCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION "The compliance statement for managed network
"The compliance statement for SNMPv2 entities which entities which have ethernet-like network
have ethernet-like network interfaces." interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { etherStatsGroup } MANDATORY-GROUPS { etherStatsGroup }
GROUP etherCollisionTableGroup GROUP etherCollisionTableGroup
DESCRIPTION DESCRIPTION "This group is optional. It is appropriate
"This group is optional. It is appropriate for for all systems which have the necessary
all systems which have the necessary metering. metering Implementation in such systems is
Implementation in such systems is highly highly recommended."
recommended."
::= { etherCompliances 1 } ::= { etherCompliances 1 }
ether100MbsCompliance MODULE-COMPLIANCE ether100MbsCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION "The compliance statement for managed network
"The compliance statement for SNMPv2 entities which entities which have 100 Mb/sec ethernet-like
have 100 Mb/sec ethernet-like network interfaces." network interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { etherStats100MbsGroup } MANDATORY-GROUPS { etherStats100MbsGroup }
GROUP etherCollisionTableGroup GROUP etherCollisionTableGroup
DESCRIPTION DESCRIPTION "This group is optional. It is appropriate
"This group is optional. It is appropriate for for all systems which have the necessary
all systems which have the necessary metering. metering Implementation in such systems is
Implementation in such systems is highly highly recommended."
recommended."
::= { etherCompliances 2 } ::= { etherCompliances 2 }
-- units of conformance -- units of conformance
etherStatsGroup OBJECT-GROUP etherStatsGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex, dot3StatsAlignmentErrors, OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors, dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames, dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames, dot3StatsMultipleCollisionFrames,
dot3StatsSQETestErrors, dot3StatsSQETestErrors,
dot3StatsDeferredTransmissions, dot3StatsDeferredTransmissions,
dot3StatsLateCollisions, dot3StatsLateCollisions,
dot3StatsExcessiveCollisions, dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors, dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors, dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs, dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors, dot3StatsInternalMacReceiveErrors,
dot3StatsEtherChipSet} dot3StatsEtherChipSet
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A collection of objects providing information
"A collection of objects providing information applicable to all ethernet-like network
applicable to all ethernet-like network interfaces." interfaces."
::= { etherGroups 1 } ::= { etherGroups 1 }
etherCollisionTableGroup OBJECT-GROUP etherCollisionTableGroup OBJECT-GROUP
OBJECTS { dot3CollCount, dot3CollFrequencies } OBJECTS { dot3CollFrequencies
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A collection of objects providing a histogram
"A collection of objects providing a histogram
of packets successfully transmitted after of packets successfully transmitted after
experiencing exactly N collisions." experiencing exactly N collisions."
::= { etherGroups 2 } ::= { etherGroups 2 }
etherStats100MbsGroup OBJECT-GROUP etherStats100MbsGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex, dot3StatsAlignmentErrors, OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors, dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames, dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames, dot3StatsMultipleCollisionFrames,
dot3StatsDeferredTransmissions, dot3StatsDeferredTransmissions,
dot3StatsLateCollisions, dot3StatsLateCollisions,
dot3StatsExcessiveCollisions, dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors, dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors, dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs, dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors, dot3StatsInternalMacReceiveErrors,
dot3StatsEtherChipSet, dot3StatsEtherChipSet,
dot3StatsSymbolErrors} dot3StatsSymbolErrors
}
STATUS current STATUS current
DESCRIPTION DESCRIPTION "A collection of objects providing information
"A collection of objects providing information
applicable to 100 Mb/sec ethernet-like network applicable to 100 Mb/sec ethernet-like network
interfaces." interfaces."
::= { etherGroups 3 } ::= { etherGroups 3 }
END END
6. Acknowledgements 6. Intellectual Property
This document was produced by the 802.3 Hub MIB Working Group. The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
This document is almost completely based on both the Standard Ethernet The IETF invites any interested party to bring to its attention any
MIB, RFC 1623 [10], and the Proposed Standard Ethernet MIB using the copyrights, patents or patent applications, or other proprietary
SNMPv2 SMI, RFC 1650 [11], both of which were edited by Frank Kastenholz rights which may cover technology that may be required to practice
of FTP Software and produced by the Ethernet MIB Working Group. This this standard. Please address the information to the IETF Executive
document extends those documents by providing support for 100 Mb/sec Director.
ethernet interfaces as outlined in [6].
RFC 1623 and RFC 1650, in turn, are based on the Draft Standard Ethernet 7. Acknowledgements
MIB, RFC 1398 [9], also edited by Frank Kastenholz and produced by the
Ethernet MIB Working Group.
RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, RFC This document was produced by the 802.3 Hub MIB Working Group.
1284 [8], which was edited by John Cook of Chipcom and produced by the
Transmission MIB Working Group. The Ethernet MIB Working Group gathered
implementation experience of the variables specified in RFC 1284 and
used that information to develop this revised MIB.
RFC 1284, in turn, is based on a document written by Frank Kastenholz, This document is almost completely based on both the Standard
then of Interlan, entitled IEEE 802.3 Layer Management Draft M Ethernet MIB, RFC 1623 [10], and the Proposed Standard Ethernet MIB
compatible MIB for TCP/IP Networks [7]. This document has been modestly using the SNMPv2 SMI, RFC 1650 [11], both of which were edited by
reworked, initially by the SNMP Working Group, and then by the Frank Kastenholz of FTP Software and produced by the Ethernet MIB
Transmission Working Group, to reflect the current conventions for Working Group. This document extends those documents by providing
defining objects for MIB interfaces. James Davin, of the MIT Laboratory support for 100 Mb/sec ethernet interfaces as outlined in [6].
for Computer Science, and Keith McCloghrie of Hughes LAN Systems, RFC 1623 and RFC 1650, in turn, are based on the Draft Standard
contributed to later drafts of this memo. Marshall Rose of Performance Ethernet MIB, RFC 1398 [9], also edited by Frank Kastenholz and
Systems International, Inc. converted the document into its current produced by the Ethernet MIB Working Group.
concise format. Anil Rijsinghani of DEC contributed text that more
adequately describes the TDR test. Thanks to Frank Kastenholz of
Interlan and Louis Steinberg of IBM for their experimentation.
7. References RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB,
RFC 1284 [8], which was edited by John Cook of Chipcom and produced
by the Transmission MIB Working Group. The Ethernet MIB Working
Group gathered implementation experience of the variables specified
in RFC 1284 and used that information to develop this revised MIB.
RFC 1284, in turn, is based on a document written by Frank
Kastenholz, then of Interlan, entitled IEEE 802.3 Layer Management
Draft M compatible MIB for TCP/IP Networks [7]. This document has
been modestly reworked, initially by the SNMP Working Group, and then
by the Transmission Working Group, to reflect 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, contributed to later drafts of this memo. Marshall Rose of
Performance Systems International, Inc. converted the document into
its current concise format. Anil Rijsinghani of DEC contributed text
that more adequately describes the TDR test. Thanks to Frank
Kastenholz of Interlan and Louis Steinberg of IBM for their
experimentation.
8. References
[1] Information processing systems - Open Systems Interconnection - [1] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1), Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization, International International Organization for Standardization, International
Standard 8824, December 1987. Standard 8824, December 1987.
[2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Structure of Management Information for Version 2 S. Waldbusser, "Structure of Management Information for Version
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996. January 1996.
[3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Textual Conventions for Version 2 of the Simple S. Waldbusser, "Textual Conventions for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1903, January 1996. Network Management Protocol (SNMPv2)", RFC 1903, January 1996.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and
S. Waldbusser, "Conformance Statements for Version 2 of the S. Waldbusser, "Conformance Statements for Version 2 of the
Simple Network Management Protocol (SNMPv2)", RFC 1904, Simple Network Management Protocol (SNMPv2)", RFC 1904,
January 1996. January 1996.
[5] IEEE, IEEE 802.3 Layer Management, November 1988. [5] IEEE, IEEE 802.3 Layer Management, November 1988.
[6] IEEE, IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, [6] IEEE, IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30,
Supplement to IEEE Std 802.3, October 26, 1995. Supplement to IEEE Std 802.3, October 26, 1995.
[7] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible MIB [7] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible
for TCP/IP Networks", electronic mail message to mib- MIB for TCP/IP Networks", electronic mail message to mib-
wg@nnsc.nsf.net, 9 June 1989. wg@nnsc.nsf.net, 9 June 1989.
[8] Cook, J., "Definitions of Managed Objects for Ethernet-Like [8] Cook, J., "Definitions of Managed Objects for Ethernet-Like
Interface Types", RFC 1284, Chipcom Corporation, December 1991. Interface Types", RFC 1284, Chipcom Corporation, December 1991.
[9] Kastenholz, F., "Definitions of Managed Objects for the [9] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 1398, FTP Software, Inc., Ethernet-like Interface Types", RFC 1398, FTP Software, Inc.,
January 1993. January 1993.
[10] Kastenholz, F., "Definitions of Managed Objects for the [10] Kastenholz, F., "Definitions of Managed Objects for the
skipping to change at page 22, line 14 skipping to change at page 30, line 17
May 1994. May 1994.
[11] Kastenholz, F., "Definitions of Managed Objects for the [11] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types using SMIv2", RFC 1650, Ethernet-like Interface Types using SMIv2", RFC 1650,
FTP Software, Inc., August 1994. FTP Software, Inc., August 1994.
[12] McCloghrie, K., and F. Kastenholz, "Evolution of the Interfaces [12] McCloghrie, K., and F. Kastenholz, "Evolution of the Interfaces
Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software,
January 1994. January 1994.
8. Security Considerations [13] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997.
Security issues are not discussed in this memo. [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", RFCXXXX,
3Com Corporation, Madge Networks (Israel) Ltd., Cisco Systems
Inc., Cisco Systems Inc., Farallon Computing Inc., October 1997.
9. Author's Addresses [15] Kastenholz, F., "Implementation Notes and Experience for The
Internet Ethernet MIB", RFC 1369, FTP Software, October 1992.
9. Security Considerations
Certain management information defined in this MIB may be considered
sensitive in some network environments. Therefore, authentication of
received SNMP requests and controlled access to management
information should be employed in such environments. The method for
this authentication is a function of the SNMP Administrative
Framework, and has not been expanded by this MIB.
10. Author's 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 Jeffrey Johnson
cisco Systems, Inc. RedBack Networks
170 W.Tasman Drive 2570 North First Street, Suite 410
San Jose, CA, 94015, USA San Jose, CA, 95131, USA
Phone: +1-408-526-7789 Phone: +1 408 571 2699
EMail: jjohnson@cisco.com EMail: jeff@redbacknetworks.com
Frank Kastenholz
FTP Software, Inc.
2 High Street
North Andover, Mass, USA 01845
Phone: +1 508 685 4000
EMail: kasten@ftp.com
11. Full Copyright Statement
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
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.
Table of Contents
1. Introduction ................................................ 2
2. The SNMP Network Management Framework ...................... 2
2.1. Object Definitions ....................................... 2
3. Change Log ................................................. 2
4. Overview ................................................... 3
4.1. Relation to MIB-2 ........................................ 4
4.2. Relation to the Interfaces MIB ........................... 4
4.2.1. Layering Model ......................................... 5
4.2.2. Virtual Circuits ....................................... 5
4.2.3. ifTestTable ............................................ 5
4.2.4. ifRcvAddressTable ...................................... 5
4.2.5. ifPhysAddress .......................................... 6
4.2.6. ifType ................................................. 6
4.2.7. Specific Interface MIB Objects ......................... 7
4.3. Relation to the 802.3 MAU MIB ............................ 10
4.4. Mapping of IEEE 802.3 Managed Objects .................... 10
5. Definitions ................................................ 13
6. Intellectual Property ...................................... 28
7. Acknowledgements ........................................... 28
8. References ................................................. 29
9. Security Considerations .................................... 30
10. Author's Addresses ........................................ 30
11. Full Copyright Statement .................................. 31
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/