draft-ietf-hubmib-etherif-mib-v2-03.txt   rfc2665.txt 
Hub MIB Working Group J. Flick Network Working Group J. Flick
INTERNET DRAFT Hewlett-Packard Company Request for Comments: 2665 Hewlett-Packard Company
J. Johnson Obsoletes: 2358 J. Johnson
RedBack Networks Category: Standards Track RedBack Networks
February 1999 August 1999
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-v2-03.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet-Drafts are working Internet community, and requests discussion and suggestions for
documents of the Internet Engineering Task Force (IETF), its areas, improvements. Please refer to the current edition of the "Internet
and its working groups. Note that other groups may also distribute Official Protocol Standards" (STD 1) for the standardization state
working documents as Internet-Drafts. and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
This memo obsoletes RFC 2358 ''Definitions of Managed Objects for the This memo obsoletes RFC 2358, "Definitions of Managed Objects for the
Ethernet-like Interface Types''. This memo extends that Ethernet-like Interface Types". This memo extends that specification
specification by including management information useful for the by including management information useful for the management of 1000
management of 1000 Mb/s and full-duplex Ethernet interfaces. Mb/s and full-duplex Ethernet interfaces.
Ethernet technology, as defined by the 802.3 Working Group of the Ethernet technology, as defined by the 802.3 Working Group of the
IEEE, continues to evolve, with scalable increases in speed, new IEEE, continues to evolve, with scalable increases in speed, new
types of cabling and interfaces, and new features. This evolution types of cabling and interfaces, and new features. This evolution
may require changes in the managed objects in order to reflect this may require changes in the managed objects in order to reflect this
new functionality. This document, as with other documents issued by new functionality. This document, as with other documents issued by
this working group, reflects a certain stage in the evolution of this working group, reflects a certain stage in the evolution of
Ethernet technology. In the future, this document might be revised, Ethernet technology. In the future, this document might be revised,
or new documents might be issued by the Ethernet Interfaces and Hub or new documents might be issued by the Ethernet Interfaces and Hub
MIB Working Group, in order to reflect the evolution of Ethernet MIB Working Group, in order to reflect the evolution of Ethernet
technology. technology.
Distribution of this memo is unlimited. Please forward comments to
hubmib@hprnd.rose.hp.com.
Table of Contents Table of Contents
1. Introduction ................................................ 2 1. Introduction ................................................ 2
2. The SNMP Management Framework .............................. 3 2. The SNMP Management Framework .............................. 3
3. Overview ................................................... 4 3. Overview ................................................... 4
3.1. Relation to MIB-2 ........................................ 4 3.1. Relation to MIB-2 ........................................ 4
3.2. Relation to the Interfaces MIB ........................... 5 3.2. Relation to the Interfaces MIB ........................... 5
3.2.1. Layering Model ......................................... 5 3.2.1. Layering Model ......................................... 5
3.2.2. Virtual Circuits ....................................... 5 3.2.2. Virtual Circuits ....................................... 5
3.2.3. ifTestTable ............................................ 5 3.2.3. ifTestTable ............................................ 5
3.2.4. ifRcvAddressTable ...................................... 6 3.2.4. ifRcvAddressTable ...................................... 6
3.2.5. ifPhysAddress .......................................... 6 3.2.5. ifPhysAddress .......................................... 6
3.2.6. ifType ................................................. 7 3.2.6. ifType ................................................. 6
3.2.7. Specific Interface MIB Objects ......................... 7 3.2.7. Specific Interface MIB Objects ......................... 7
3.3. Relation to the 802.3 MAU MIB ............................ 11 3.3. Relation to the 802.3 MAU MIB ............................ 11
3.4. dot3StatsEtherChipSet .................................... 11 3.4. dot3StatsEtherChipSet .................................... 11
3.5. Mapping of IEEE 802.3 Managed Objects .................... 11 3.5. Mapping of IEEE 802.3 Managed Objects .................... 12
4. Definitions ................................................ 14 4. Definitions ................................................ 16
5. Intellectual Property ...................................... 36 5. Intellectual Property ...................................... 39
6. Acknowledgements ........................................... 36 6. Acknowledgements ........................................... 40
7. References ................................................. 37 7. References ................................................. 41
8. Security Considerations .................................... 40 8. Security Considerations .................................... 43
9. Author's Addresses ......................................... 41 9. Authors' Addresses ......................................... 44
A. Change Log ................................................. 41 A. Change Log ................................................. 45
A.1. Changes since RFC 2358 ................................... 41 A.1. Changes since RFC 2358 ................................... 45
A.2. Changes between RFC 1650 and RFC 2358 .................... 42 A.2. Changes between RFC 1650 and RFC 2358 .................... 46
B. Full Copyright Statement ................................... 43 B. Full Copyright Statement ................................... 47
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines objects for managing Ethernet-like In particular, it defines objects for managing Ethernet-like
interfaces. interfaces.
This memo also includes a MIB module. This MIB module extends the This memo also includes a MIB module. This MIB module extends the
list of managed objects specified in the earlier version of this MIB: list of managed objects specified in the earlier version of this MIB:
skipping to change at page 3, line 18 skipping to change at page 3, line 10
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [26]. document are to be interpreted as described in [26].
2. The SNMP Management Framework 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in STD
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC second version, called SMIv2, is described in STD 58, RFC 2578
1904 [7]. [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [8]. A second version of the SNMP
protocol, which is not an Internet standards track protocol, is message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
The third version of the message protocol is called SNMPv3 and 1906 [10]. The third version of the message protocol is called
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations described in STD 15, RFC 1157 [8]. A second set of protocol
and associated PDU formats is described in RFC 1905 [13]. operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2273 [14] and o A set of fundamental applications described in RFC 2573 [14] and
the view-based access control mechanism described in RFC 2275 the view-based access control mechanism described in RFC 2575
[15]. [15].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
skipping to change at page 7, line 40 skipping to change at page 7, line 29
Interfaces with any of the supported ifType values map to the Interfaces with any of the supported ifType values map to the
EtherLike-MIB in the same manner. There are no implementation EtherLike-MIB in the same manner. There are no implementation
differences. differences.
3.2.7. Specific Interface MIB Objects 3.2.7. Specific Interface MIB Objects
The following table provides specific implementation guidelines for The following table provides specific implementation guidelines for
applying the interface group objects to ethernet-like media. applying the interface group objects to ethernet-like media.
Object Object Guidelines
ifIndex Each ethernet-like interface is ifIndex Each ethernet-like interface is
represented by an ifEntry. The represented by an ifEntry. The
dot3StatsTable in this MIB module is dot3StatsTable in this MIB module is
indexed by dot3StatsIndex. The interface indexed by dot3StatsIndex. The interface
identified by a particular value of identified by a particular value of
dot3StatsIndex is the same interface as dot3StatsIndex is the same interface as
identified by the same value of ifIndex. identified by the same value of ifIndex.
ifDescr Refer to [25]. ifDescr Refer to [25].
ifType Refer to section 3.2.6. ifType Refer to section 3.2.6.
ifMtu 1500 octets. NOTE: This is the MTU as ifMtu 1500 octets. NOTE: This is the MTU as
seen by the MAC client. When a higher seen by the MAC client. When a higher
layer protocol, like IP, is running over layer protocol, like IP, is running over
Ethernet, this is the MTU that will be Ethernet, this is the MTU that will be
seen by that higher layer protocol. seen by that higher layer protocol.
However, when using the IEEE 802.2 LLC However, when using the IEEE 802.2 LLC
protocol, higher layer protocols will protocol, higher layer protocols will
see a different MTU. In particular, an see a different MTU. In particular, an
LLC type 1 client protocol will see LLC type 1 client protocol will see
an MTU of 1497 octets, and a protocol an MTU of 1497 octets, and a protocol
running over SNAP will see an MTU of running over SNAP will see an MTU of
1492 octets. 1492 octets.
ifSpeed The current operational speed of the ifSpeed The current operational speed of the
interface in bits per second. For interface in bits per second. For
current ethernet-like interfaces, this current ethernet-like interfaces, this
will be equal to 1,000,000 (1 million), will be equal to 1,000,000 (1 million),
10,000,000 (10 million), 100,000,000 10,000,000 (10 million), 100,000,000
(100 million), or 1,000,000,000 (1 (100 million), or 1,000,000,000 (1
billion). If the interface implements billion). If the interface implements
auto-negotiation, auto-negotiation is auto-negotiation, auto-negotiation is
enabled for this interface, and the enabled for this interface, and the
interface has not yet negotiated to an interface has not yet negotiated to an
operational speed, this object SHOULD operational speed, this object SHOULD
reflect the maximum speed supported by reflect the maximum speed supported by
the interface. Note that this object the interface. Note that this object
MUST NOT indicate a doubled value when MUST NOT indicate a doubled value when
operating in full-duplex mode. It MUST operating in full-duplex mode. It MUST
indicate the correct line speed indicate the correct line speed
regardless of the current duplex mode. regardless of the current duplex mode.
The duplex mode of the interface may The duplex mode of the interface may
be determined by examining either the be determined by examining either the
dot3StatsDuplexStatus object in this dot3StatsDuplexStatus object in this
MIBmodule, or the ifMauType object in MIBmodule, or the ifMauType object in
the 802.3 MAU MIB. the 802.3 MAU MIB.
ifPhysAddress Refer to section 3.2.5. ifPhysAddress Refer to section 3.2.5.
ifAdminStatus Write access is not required. Support ifAdminStatus Write access is not required. Support
for 'testing' is not required. for 'testing' is not required.
ifOperStatus The operational state of the interface. ifOperStatus The operational state of the interface.
Support for 'testing' is not required. Support for 'testing' is not required.
The value 'dormant' has no meaning for The value 'dormant' has no meaning for
an ethernet-like interface. an ethernet-like interface.
ifLastChange Refer to [25]. ifLastChange Refer to [25].
ifInOctets The number of octets in valid MAC frames ifInOctets The number of octets in valid MAC
received on this interface, including frames received on this interface,
the MAC header and FCS. including the MAC header and FCS.
This does include the number of octets
in valid MAC Control frames received on
this interface.
ifInUcastPkts Refer to [25]. ifInUcastPkts Refer to [25]. Note that this does
not include MAC Control frames, since
MAC Control frames are consumed by the
interface layer and are not passed to
any higher layer protocol.
ifInDiscards Refer to [25]. ifInDiscards Refer to [25].
ifInErrors The sum for this interface of ifInErrors The sum for this interface of
dot3StatsAlignmentErrors, dot3StatsAlignmentErrors,
dot3StatsFCSErrors, dot3StatsFCSErrors,
dot3StatsFrameTooLongs, dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors and dot3StatsInternalMacReceiveErrors and
dot3StatsSymbolErrors. dot3StatsSymbolErrors.
ifInUnknownProtos Refer to [25]. ifInUnknownProtos Refer to [25].
ifOutOctets The number of octets transmitted in ifOutOctets The number of octets transmitted in
valid MAC frames on this interface, valid MAC frames on this interface,
including the MAC header and FCS. including the MAC header and FCS.
This does include the number of octets
in valid MAC Control frames transmitted
on this interface.
ifOutUcastPkts Refer to [25]. ifOutUcastPkts Refer to [25]. Note that this does
not include MAC Control frames, since
MAC Control frames are generated by the
interface layer, and are not passed
from any higher layer protocol.
ifOutDiscards Refer to [25]. ifOutDiscards Refer to [25].
ifOutErrors The sum for this interface of: ifOutErrors The sum for this interface of:
dot3StatsSQETestErrors, dot3StatsSQETestErrors,
dot3StatsLateCollisions, dot3StatsLateCollisions,
dot3StatsExcessiveCollisions, dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors and dot3StatsInternalMacTransmitErrors and
dot3StatsCarrierSenseErrors. dot3StatsCarrierSenseErrors.
ifName Locally-significant textual name for the ifName Locally-significant textual name for
interface (e.g. lan0). the interface (e.g. lan0).
ifInMulticastPkts Refer to [25]. ifInMulticastPkts Refer to [25]. Note that this does
not include MAC Control frames, since
MAC Control frames are consumed by the
interface layer and are not passed to
any higher layer protocol.
ifInBroadcastPkts Refer to [25]. ifInBroadcastPkts Refer to [25]. Note that this does
not include MAC Control frames, since
MAC Control frames are generated by
the interface layer, and are not passed
from any higher layer protocol.
ifOutMulticastPkts Refer to [25]. ifOutMulticastPkts Refer to [25]. Note that this does
not include MAC Control frames, since
MAC Control frames are consumed by the
interface layer and are not passed to
any higher layer protocol.
ifOutBroadcastPkts Refer to [25]. ifOutBroadcastPkts Refer to [25]. Note that this does
not include MAC Control frames, since
MAC Control frames are generated by
the interface layer, and are not passed
from any higher layer protocol.
ifHCInOctets 64-bit versions of counters. Required ifHCInOctets 64-bit versions of counters. Required
ifHCOutOctets for ethernet-like interfaces that are ifHCOutOctets for ethernet-like interfaces that are
capable of operating at 20Mbit/sec or capable of operating at 20Mbit/sec or
faster, even if the interface is faster, even if the interface is
currently operating at less than currently operating at less than
20Mbit/sec. 20Mbit/sec.
ifHCInUcastPkts 64-bit versions of packet counters. ifHCInUcastPkts 64-bit versions of packet counters.
ifHCInMulticastPkts Required for ethernet-like interfaces ifHCInMulticastPkts Required for ethernet-like interfaces
ifHCInBroadcastPkts that are capable of operating at ifHCInBroadcastPkts that are capable of operating at
ifHCOutUcastPkts 640Mbit/sec or faster, even if the ifHCOutUcastPkts 640Mbit/sec or faster, even if the
ifHCOutMulticastPkts interface is currently operating at ifHCOutMulticastPkts interface is currently operating at
ifHCOutBroadcastPkts less than 640Mbit/sec. ifHCOutBroadcastPkts less than 640Mbit/sec.
ifLinkUpDownTrapEnable Refer to [25]. Default is 'enabled' ifLinkUpDownTrapEnable Refer to [25]. Default is 'enabled'
ifHighSpeed The current operational speed of the ifHighSpeed The current operational speed of the
interface in millions of bits per interface in millions of bits per
second. For current ethernet-like second. For current ethernet-like
interfaces, this will be equal to 1, 10, interfaces, this will be equal to 1,
100, or 1,000. If the interface 10, 100, or 1,000. If the interface
implements auto-negotiation, implements auto-negotiation,
auto-negotiation is enabled for this auto-negotiation is enabled for this
interface, and the interface has not yet interface, and the interface has not
negotiated to an operational speed, this yet negotiated to an operational speed,
object SHOULD reflect the maximum speed this object SHOULD reflect the maximum
supported by the interface. Note that speed supported by the interface. Note
this object MUST NOT indicate a doubled that this object MUST NOT indicate a
value when operating in full-duplex doubled value when operating in full-
mode. It MUST indicate the correct line duplex mode. It MUST indicate the
speed regardless of the current duplex correct line speed regardless of the
mode. The duplex mode of the interface current duplex mode. The duplex mode
may be determined by examining either of the interface may be determined
the dot3StatsDuplexStatus object in this by examining either the
MIB module, or the ifMauType object in dot3StatsDuplexStatus object in this
the 802.3 MAU MIB. MIB module, or the ifMauType object in
the 802.3 MAU MIB.
ifPromiscuousMode Refer to [25]. ifPromiscuousMode Refer to [25].
ifConnectorPresent This will normally be 'true'. ifConnectorPresent This will normally be 'true'.
ifAlias Refer to [25]. ifAlias Refer to [25].
ifCounterDiscontinuityTime Refer to [25]. ifCounterDiscontinuityTime Refer to [25]. Note that a
discontinuity in the Interface MIB
counters may also indicate a
discontinuity in some or all of the
counters in this MIB that are
associated with that interface.
ifStackHigherLayer Refer to section 3.2.1. ifStackHigherLayer Refer to section 3.2.1.
ifStackLowerLayer ifStackLowerLayer
ifStackStatus ifStackStatus
ifRcvAddressAddress Refer to section 3.2.4.
ifRcvAddressStatus ifRcvAddressAddress Refer to section 3.2.4.
ifRcvAddressType ifRcvAddressStatus
ifRcvAddressType
3.3. Relation to the 802.3 MAU MIB 3.3. Relation to the 802.3 MAU MIB
Support for the mauModIfCompl2 compliance statement of the MAU-MIB Support for the mauModIfCompl2 compliance statement of the MAU-MIB
[27] is REQUIRED for Ethernet-like interfaces. This MIB is needed in [27] is REQUIRED for Ethernet-like interfaces. This MIB is needed in
order to allow applications to determine the current MAU type in use order to allow applications to determine the current MAU type in use
by the interface, and to control autonegotiation and duplex mode for by the interface, and to control autonegotiation and duplex mode for
the interface. Implementing this MIB module without implementing the the interface. Implementing this MIB module without implementing the
MAU-MIB would leave applications with no standard way to determine MAU-MIB would leave applications with no standard way to determine
the media type in use, and no standard way to control the duplex mode the media type in use, and no standard way to control the duplex mode
skipping to change at page 12, line 4 skipping to change at page 12, line 27
Implementations which continue to support this object for the purpose Implementations which continue to support this object for the purpose
of backwards compatability may continue to use the values defined in of backwards compatability may continue to use the values defined in
[28]. For chipsets not listed in [28], implementors should assign [28]. For chipsets not listed in [28], implementors should assign
OBJECT IDENTIFIERS within that part of the registration tree OBJECT IDENTIFIERS within that part of the registration tree
delegated to individual enterprises. delegated to individual enterprises.
3.5. Mapping of IEEE 802.3 Managed Objects 3.5. Mapping of IEEE 802.3 Managed Objects
IEEE 802.3 Managed Object Corresponding SNMP Object IEEE 802.3 Managed Object Corresponding SNMP Object
oMacEntity oMacEntity
.aMACID dot3StatsIndex or .aMACID dot3StatsIndex or
IF-MIB - ifIndex IF-MIB - ifIndex
.aFramesTransmittedOK IF-MIB - ifOutUCastPkts + .aFramesTransmittedOK IF-MIB - ifOutUCastPkts +
ifOutMulticastPkts + ifOutMulticastPkts +
ifOutBroadcastPkts ifOutBroadcastPkts*
.aSingleCollisionFrames dot3StatsSingleCollisionFrames .aSingleCollisionFrames dot3StatsSingleCollisionFrames
.aMultipleCollisionFrames dot3StatsMultipleCollisionFrames .aMultipleCollisionFrames dot3StatsMultipleCollisionFrames
.aFramesReceivedOK IF-MIB - ifInUcastPkts + .aFramesReceivedOK IF-MIB - ifInUcastPkts +
ifInMulticastPkts + ifInMulticastPkts +
ifInBroadcastPkts ifInBroadcastPkts*
.aFrameCheckSequenceErrors dot3StatsFCSErrors .aFrameCheckSequenceErrors dot3StatsFCSErrors
.aAlignmentErrors dot3StatsAlignmentErrors .aAlignmentErrors dot3StatsAlignmentErrors
.aOctetsTransmittedOK IF-MIB - ifOutOctets* .aOctetsTransmittedOK IF-MIB - ifOutOctets*
.aFramesWithDeferredXmissions dot3StatsDeferredTransmissions .aFramesWithDeferredXmissions dot3StatsDeferredTransmissions
.aLateCollisions dot3StatsLateCollisions .aLateCollisions dot3StatsLateCollisions
.aFramesAbortedDueToXSColls dot3StatsExcessiveCollisions .aFramesAbortedDueToXSColls dot3StatsExcessiveCollisions
.aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors .aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors
.aCarrierSenseErrors dot3StatsCarrierSenseErrors .aCarrierSenseErrors dot3StatsCarrierSenseErrors
.aOctetsReceivedOK IF-MIB - ifInOctets* .aOctetsReceivedOK IF-MIB - ifInOctets*
.aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors .aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors
.aPromiscuousStatus IF-MIB - ifPromiscuousMode .aPromiscuousStatus IF-MIB - ifPromiscuousMode
.aReadMulticastAddressList IF-MIB - ifRcvAddressTable .aReadMulticastAddressList IF-MIB - ifRcvAddressTable
.aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts .aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts*
.aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts .aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts*
.aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts .aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts*
.aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts .aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts*
.aFrameTooLongErrors dot3StatsFrameTooLongs .aFrameTooLongErrors dot3StatsFrameTooLongs
.aReadWriteMACAddress IF-MIB - ifPhysAddress .aReadWriteMACAddress IF-MIB - ifPhysAddress
.aCollisionFrames dot3CollFrequencies .aCollisionFrames dot3CollFrequencies
.aDuplexStatus dot3StatsDuplexStatus .aDuplexStatus dot3StatsDuplexStatus
.acAddGroupAddress IF-MIB - ifRcvAddressTable .acAddGroupAddress IF-MIB - ifRcvAddressTable
.acDeleteGroupAddress IF-MIB - ifRcvAddressTable .acDeleteGroupAddress IF-MIB - ifRcvAddressTable
.acExecuteSelfTest dot3TestLoopBack .acExecuteSelfTest dot3TestLoopBack
oPHYEntity oPHYEntity
.aPHYID dot3StatsIndex or .aPHYID dot3StatsIndex or
skipping to change at page 13, line 17 skipping to change at page 13, line 40
.aPAUSEMACCtrlFramesReceived dot3InPauseFrames .aPAUSEMACCtrlFramesReceived dot3InPauseFrames
* Note that the octet counters in IF-MIB do not exactly match the * Note that the octet counters in IF-MIB do not exactly match the
definition of the octet counters in IEEE 802.3. aOctetsTransmittedOK definition of the octet counters in IEEE 802.3. aOctetsTransmittedOK
and aOctetsReceivedOK count only the octets in the clientData and Pad and aOctetsReceivedOK count only the octets in the clientData and Pad
fields, whereas ifInOctets and ifOutOctets include the entire MAC fields, whereas ifInOctets and ifOutOctets include the entire MAC
frame, including MAC header and FCS. However, the IF-MIB counters frame, including MAC header and FCS. However, the IF-MIB counters
can be derived from the IEEE 802.3 counters as follows: can be derived from the IEEE 802.3 counters as follows:
ifInOctets = aOctetsReceivedOK + (18 * aFramesReceivedOK) ifInOctets = aOctetsReceivedOK + (18 * aFramesReceivedOK)
ifOutOctets = aOctetsTransmittedOK + (18 * aFramesTransmittedOK) ifOutOctets = aOctetsTransmittedOK + (18 * aFramesTransmittedOK)
Also note that the packet counters in the IF-MIB do not exactly match
the definition of the frame counters in IEEE 802.3.
aFramesTransmittedOK counts the number of frames successfully
transmitted on the interface, whereas ifOutUcastPkts,
ifOutMulticastPkts and ifOutBroadcastPkts count the number of
transmit requests made from a higher layer, whether or not the
transmit attempt was successful. This means that packets counted by
ifOutErrors or ifOutDiscards are also be counted by ifOut*castPkts,
but are not be counted by aFramesTransmittedOK. This also means
that, since MAC Control frames are generated by a sublayer internal
to the interface layer rather than by a higher layer, they are not
counted by ifOut*castPkts, but are counted by aFramesTransmittedOK.
Similarly, aFramesReceivedOK counts the number of frames received
successfully by the interface, whether or not they are passed to a
higher layer, whereas ifInUcastPkts, ifInMulticastPkts and
ifInBroadcastPkts count only the number of packets passed to a higher
layer. This means that packets counted by ifInDiscards or
ifInUnknownProtos are also counted by aFramesReceivedOK, but are not
counted by ifIn*castPkts. This also menas that, since MAC Control
frames are consumed by a sublayer internal to the interface layer and
not passed to a higher layer, they are not counted by ifIn*castPkts,
but are counted by aFramesReceivedOK.
Another difference to keep in mind between the IF-MIB counters and
IEEE 802.3 counters is that in the IEEE 802.3 document, the frame
counters and octet counters are always incremented together.
aOctetsTransmittedOK counts the number of octets in frames that were
counted by aFramesTransmittedOK. aOctetsReceivedOK counts the number
of octets in frames that were counted by aFramesReceivedOK. This is
not the case with the IF-MIB counters. The IF-MIB octet counters
count the number of octets sent to or received from the layer below
this interface, whereas the packet counters count the number of
packets sent to or received from the layer above. Therefore,
received MAC Control frames, ifInDiscards, and ifInUnknownProtos are
counted by ifInOctets, but not ifIn*castPkts. Transmitted MAC
Control frames are counted by ifOutOctets, but not ifOut*castPkts.
ifOutDiscards and ifOutErrors are counted by ifOut*castPkts, but not
ifOutOctets.
The following IEEE 802.3 managed objects have been removed from this The following IEEE 802.3 managed objects have been removed from this
MIB module as a result of implementation feedback: MIB module as a result of implementation feedback:
oMacEntity oMacEntity
.aFramesWithExcessiveDeferral .aFramesWithExcessiveDeferral
.aInRangeLengthErrors .aInRangeLengthErrors
.aOutOfRangeLengthField .aOutOfRangeLengthField
.aMACEnableStatus .aMACEnableStatus
.aTransmitEnableStatus .aTransmitEnableStatus
.aMulticastReceiveStatus .aMulticastReceiveStatus
skipping to change at page 14, line 37 skipping to change at page 16, line 11
oPAUSEEntity oPAUSEEntity
.aPAUSELinkDelayAllowance Not considered useful. .aPAUSELinkDelayAllowance Not considered useful.
4. Definitions 4. Definitions
EtherLike-MIB DEFINITIONS ::= BEGIN EtherLike-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Unsigned32, mib-2, transmission Counter32, mib-2, transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
ifIndex, InterfaceIndex ifIndex, InterfaceIndex
FROM IF-MIB; FROM IF-MIB;
etherMIB MODULE-IDENTITY etherMIB MODULE-IDENTITY
LAST-UPDATED "9902120223Z" -- February 12, 1999 LAST-UPDATED "9908240400Z" -- August 24, 1999
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-mail: hubmib@hprnd.rose.hp.com "WG E-mail: hubmib@hprnd.rose.hp.com
To subscribe: hubmib-request@hprnd.rose.hp.com To subscribe: hubmib-request@hprnd.rose.hp.com
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Lucent Technologies Postal: Lucent Technologies
Atidum Technology Park, Bldg. 3 Atidum Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
Israel Israel
Tel: +972 3 645 8414 Tel: +972 3 645 8414
E-mail: dromasca@lucent.com E-mail: dromasca@lucent.com
Editor: John Flick Editor: John Flick
Postal: Hewlett-Packard Company Postal: Hewlett-Packard Company
skipping to change at page 15, line 50 skipping to change at page 17, line 23
Local and metropolitan area networks - Local and metropolitan area networks -
Specific requirements - Part 3: Carrier Specific requirements - Part 3: Carrier
sense multiple access with collision sense multiple access with collision
detection (CSMA/CD) access method and detection (CSMA/CD) access method and
physical layer specifications', physical layer specifications',
September 1998. September 1998.
Of particular interest is Clause 30, '10Mb/s, Of particular interest is Clause 30, '10Mb/s,
100Mb/s and 1000Mb/s Management'." 100Mb/s and 1000Mb/s Management'."
REVISION "9902120223Z" -- February 12, 1999 REVISION "9908240400Z" -- August 24, 1999
DESCRIPTION "Updated to include support for 1000 Mb/sec DESCRIPTION "Updated to include support for 1000 Mb/sec
interfaces and full-duplex interfaces." interfaces and full-duplex interfaces.
This version published as RFC 2665."
REVISION "9806032150Z" -- June 3, 1998 REVISION "9806032150Z"
DESCRIPTION "Updated to include support for 100 Mb/sec DESCRIPTION "Updated to include support for 100 Mb/sec
interfaces. Published as RFC 2358." interfaces.
This version published as RFC 2358."
REVISION "9402030400Z"
DESCRIPTION "Initial version, published as RFC 1650."
REVISION "9402030400Z" -- February 3, 1994
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 "Statistics for a collection of ethernet-like DESCRIPTION "Statistics for a collection of ethernet-like
interfaces attached to a particular system." interfaces attached to a particular system.
There will be one row in this table for each
ethernet-like interface in the 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 "Statistics for a particular interface to an DESCRIPTION "Statistics for a particular interface to an
ethernet-like medium." ethernet-like medium."
INDEX { dot3StatsIndex } INDEX { dot3StatsIndex }
::= { dot3StatsTable 1 } ::= { dot3StatsTable 1 }
skipping to change at page 17, line 39 skipping to change at page 19, line 18
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.
This counter does not increment for 8-bit wide This counter does not increment for 8-bit wide
group encoding schemes." group encoding schemes.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7,
aAlignmentErrors" aAlignmentErrors"
::= { 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 "A count of frames received on a particular DESCRIPTION "A count of frames received on a particular
interface that are an integral number of octets interface that are an integral number of octets
skipping to change at page 18, line 17 skipping to change at page 19, line 49
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.
Note: Coding errors detected by the physical Note: Coding errors detected by the physical
layer for speeds above 10 Mb/s will cause the layer for speeds above 10 Mb/s will cause the
frame to fail the FCS check." frame to fail the FCS check.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6,
aFrameCheckSequenceErrors." aFrameCheckSequenceErrors."
::= { 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 "A count of successfully transmitted frames on DESCRIPTION "A count of successfully transmitted frames on
a particular interface for which transmission a particular interface for which transmission
skipping to change at page 18, line 39 skipping to change at page 20, line 27
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.
This counter does not increment when the This counter does not increment when the
interface is operating in full-duplex mode." interface is operating in full-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.3, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.3,
aSingleCollisionFrames." aSingleCollisionFrames."
::= { 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 "A count of successfully transmitted frames on DESCRIPTION "A count of successfully transmitted frames on
a particular interface for which transmission a particular interface for which transmission
skipping to change at page 19, line 14 skipping to change at page 21, line 6
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.
This counter does not increment when the This counter does not increment when the
interface is operating in full-duplex mode." interface is operating in full-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.4, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.4,
aMultipleCollisionFrames." aMultipleCollisionFrames."
::= { 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 "A count of times that the SQE TEST ERROR DESCRIPTION "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
is set in accordance with the rules for is set in accordance with the rules for
verification of the SQE detection mechanism in verification of the SQE detection mechanism in
the PLS Carrier Sense Function as described in the PLS Carrier Sense Function as described in
IEEE Std. 802.3, 1998 Edition, section 7.2.4.6. IEEE Std. 802.3, 1998 Edition, section 7.2.4.6.
This counter does not increment on interfaces This counter does not increment on interfaces
operating at speeds greater than 10 Mb/s, or on operating at speeds greater than 10 Mb/s, or on
interfaces operating in full-duplex mode." interfaces operating in full-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4, REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4,
aSQETestErrors." aSQETestErrors."
::= { 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 "A count of frames for which the first DESCRIPTION "A count of frames for which the first
transmission attempt on a particular interface transmission attempt on a particular interface
skipping to change at page 19, line 45 skipping to change at page 21, line 47
aSQETestErrors." aSQETestErrors."
::= { 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 "A count of frames for which the first DESCRIPTION "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.
This counter does not increment when the This counter does not increment when the
interface is operating in full-duplex mode." interface is operating in full-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.9, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.9,
aFramesWithDeferredXmissions." aFramesWithDeferredXmissions."
::= { 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 "The number of times that a collision is DESCRIPTION "The number of times that a collision is
detected on a particular interface later than detected on a particular interface later than
one slotTime into the transmission of a packet. one slotTime into the transmission of a packet.
A (late) collision included in a count A (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.
This counter does not increment when the This counter does not increment when the
interface is operating in full-duplex mode." interface is operating in full-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.10, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.10,
aLateCollisions." aLateCollisions."
::= { 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 "A count of frames for which transmission on a DESCRIPTION "A count of frames for which transmission on a
particular interface fails due to excessive particular interface fails due to excessive
skipping to change at page 20, line 36 skipping to change at page 22, line 45
aLateCollisions." aLateCollisions."
::= { 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 "A count of frames for which transmission on a DESCRIPTION "A count of frames for which transmission on a
particular interface fails due to excessive particular interface fails due to excessive
collisions. collisions.
This counter does not increment when the This counter does not increment when the
interface is operating in full-duplex mode." interface is operating in full-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.11, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.11,
aFramesAbortedDueToXSColls." aFramesAbortedDueToXSColls."
::= { 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 "A count of frames for which transmission on a DESCRIPTION "A count of frames for which transmission on a
particular interface fails due to an internal particular interface fails due to an internal
skipping to change at page 21, line 12 skipping to change at page 23, line 25
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.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12,
aFramesLostDueToIntMACXmitError." aFramesLostDueToIntMACXmitError."
::= { 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 "The number of times that the carrier sense DESCRIPTION "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.
This counter does not increment when the This counter does not increment when the
interface is operating in full-duplex mode." interface is operating in full-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.13, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.13,
aCarrierSenseErrors." aCarrierSenseErrors."
::= { 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
skipping to change at page 22, line 7 skipping to change at page 24, line 30
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.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25,
aFrameTooLongErrors." aFrameTooLongErrors."
::= { 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
skipping to change at page 22, line 34 skipping to change at page 25, line 13
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.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15,
aFramesLostDueToIntMACRcvError." aFramesLostDueToIntMACRcvError."
::= { 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 deprecated STATUS deprecated
DESCRIPTION "******** THIS OBJECT IS DEPRECATED ******** DESCRIPTION "******** THIS OBJECT IS DEPRECATED ********
skipping to change at page 23, line 47 skipping to change at page 26, line 31
media is non-idle a carrier event) for a period media is non-idle a carrier event) for a period
of time equal to or greater than minFrameSize, of time equal to or greater than minFrameSize,
and during which there was at least one and during which there was at least one
occurrence of an event that causes the PHY to occurrence of an event that causes the PHY to
indicate 'Data reception error' on the GMII. indicate 'Data reception error' on the GMII.
The count represented by an instance of this The count represented by an instance of this
object is incremented at most once per carrier object is incremented at most once per carrier
event, even if multiple symbol errors occur event, even if multiple symbol errors occur
during the carrier event. This count does during the carrier event. This count does
not increment if a collision is present." not increment if a collision is present.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5,
aSymbolErrorDuringCarrier." aSymbolErrorDuringCarrier."
::= { dot3StatsEntry 18 } ::= { dot3StatsEntry 18 }
dot3StatsDuplexStatus OBJECT-TYPE dot3StatsDuplexStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
halfDuplex(2), halfDuplex(2),
fullDuplex(3) fullDuplex(3)
} }
skipping to change at page 24, line 26 skipping to change at page 27, line 14
Management control of the duplex mode is Management control of the duplex mode is
accomplished through the MAU MIB. When accomplished through the MAU MIB. When
an interface does not support autonegotiation, an interface does not support autonegotiation,
or when autonegotiation is not enabled, the or when autonegotiation is not enabled, the
duplex mode is controlled using duplex mode is controlled using
ifMauDefaultType. When autonegotiation is ifMauDefaultType. When autonegotiation is
supported and enabled, duplex mode is controlled supported and enabled, duplex mode is controlled
using ifMauAutoNegAdvertisedBits. In either using ifMauAutoNegAdvertisedBits. In either
case, the currently operating duplex mode is case, the currently operating duplex mode is
reflected both in this object and in ifMauType." reflected both in this object and in ifMauType.
Note that this object provides redundant
information with ifMauType. Normally, redundant
objects are discouraged. However, in this
instance, it allows a management application to
determine the duplex status of an interface
without having to know every possible value of
ifMauType. This was felt to be sufficiently
valuable to justify the redundancy."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32,
aDuplexStatus." aDuplexStatus."
::= { dot3StatsEntry 19 } ::= { dot3StatsEntry 19 }
-- 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
skipping to change at page 25, line 50 skipping to change at page 28, line 45
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.
No other instance of dot3CollFrequencies would No other instance of dot3CollFrequencies would
be incremented in this example. be incremented in this example.
This counter does not increment when the This counter does not increment when the
interface is operating in full-duplex mode." interface is operating in full-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
::= { dot3CollEntry 3 } ::= { dot3CollEntry 3 }
dot3ControlTable OBJECT-TYPE dot3ControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ControlEntry SYNTAX SEQUENCE OF Dot3ControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "A table of descriptive and status information DESCRIPTION "A table of descriptive and status information
about the MAC Control sublayer on the about the MAC Control sublayer on the
ethernet-like interfaces attached to a ethernet-like interfaces attached to a
particular system." particular system. There will be one row in
this table for each ethernet-like interface in
the system which implements the MAC Control
sublayer. If some, but not all, of the
ethernet-like interfaces in the system implement
the MAC Control sublayer, there will be fewer
rows in this table than in the dot3StatsTable."
::= { dot3 9 } ::= { dot3 9 }
dot3ControlEntry OBJECT-TYPE dot3ControlEntry OBJECT-TYPE
SYNTAX Dot3ControlEntry SYNTAX Dot3ControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An entry in the table, containing information DESCRIPTION "An entry in the table, containing information
about the MAC Control sublayer on a single about the MAC Control sublayer on a single
ethernet-like interface." ethernet-like interface."
INDEX { dot3StatsIndex } INDEX { dot3StatsIndex }
::= { dot3ControlTable 1 } ::= { dot3ControlTable 1 }
Dot3ControlEntry ::= Dot3ControlEntry ::=
SEQUENCE { SEQUENCE {
dot3ControlFunctionsSupported BITS, dot3ControlFunctionsSupported BITS,
dot3ControlInUnknownOpcodes Counter32 dot3ControlInUnknownOpcodes Counter32
} }
dot3ControlFunctionsSupported OBJECT-TYPE dot3ControlFunctionsSupported OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
pause(0) pause(0) -- 802.3x flow control
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A list of the possible MAC Control functions DESCRIPTION "A list of the possible MAC Control functions
implemented for this interface." implemented for this interface."
REFERENCE "[IEEE 802.3 Std.], 30.3.3.2, REFERENCE "[IEEE 802.3 Std.], 30.3.3.2,
aMACControlFunctionsSupported." aMACControlFunctionsSupported."
::= { dot3ControlEntry 1 } ::= { dot3ControlEntry 1 }
dot3ControlInUnknownOpcodes OBJECT-TYPE dot3ControlInUnknownOpcodes OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of MAC Control frames received on this DESCRIPTION "A count of MAC Control frames received on this
interface that contain an opcode that is not interface that contain an opcode that is not
supported by this device." supported by this device.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.3.5, REFERENCE "[IEEE 802.3 Std.], 30.3.3.5,
aUnsupportedOpcodesReceived" aUnsupportedOpcodesReceived"
::= { dot3ControlEntry 2 } ::= { dot3ControlEntry 2 }
dot3PauseTable OBJECT-TYPE dot3PauseTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3PauseEntry SYNTAX SEQUENCE OF Dot3PauseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "A table of descriptive and status information DESCRIPTION "A table of descriptive and status information
about the MAC Control PAUSE function on the about the MAC Control PAUSE function on the
ethernet-like interfaces attached to a ethernet-like interfaces attached to a
particular system." particular system. There will be one row in
this table for each ethernet-like interface in
the system which supports the MAC Control PAUSE
function (i.e., the 'pause' bit in the
corresponding instance of
dot3ControlFunctionsSupported is set). If some,
but not all, of the ethernet-like interfaces in
the system implement the MAC Control PAUSE
function (for example, if some interfaces only
support half-duplex), there will be fewer rows
in this table than in the dot3StatsTable."
::= { dot3 10 } ::= { dot3 10 }
dot3PauseEntry OBJECT-TYPE dot3PauseEntry OBJECT-TYPE
SYNTAX Dot3PauseEntry SYNTAX Dot3PauseEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An entry in the table, containing information DESCRIPTION "An entry in the table, containing information
about the MAC Control PAUSE function on a single about the MAC Control PAUSE function on a single
ethernet-like interface." ethernet-like interface."
INDEX { dot3StatsIndex } INDEX { dot3StatsIndex }
skipping to change at page 29, line 20 skipping to change at page 32, line 37
dot3InPauseFrames OBJECT-TYPE dot3InPauseFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of MAC Control frames received on this DESCRIPTION "A count of MAC Control frames received on this
interface with an opcode indicating the PAUSE interface with an opcode indicating the PAUSE
operation. operation.
This counter does not increment when the This counter does not increment when the
interface is operating in half-duplex mode." interface is operating in half-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.3, REFERENCE "[IEEE 802.3 Std.], 30.3.4.3,
aPAUSEMACCtrlFramesReceived." aPAUSEMACCtrlFramesReceived."
::= { dot3PauseEntry 3 } ::= { dot3PauseEntry 3 }
dot3OutPauseFrames OBJECT-TYPE dot3OutPauseFrames OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of MAC Control frames transmitted on DESCRIPTION "A count of MAC Control frames transmitted on
this interface with an opcode indicating the this interface with an opcode indicating the
PAUSE operation. PAUSE operation.
This counter does not increment when the This counter does not increment when the
interface is operating in half-duplex mode." interface is operating in half-duplex mode.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.4.2, REFERENCE "[IEEE 802.3 Std.], 30.3.4.2,
aPAUSEMACCtrlFramesTransmitted." aPAUSEMACCtrlFramesTransmitted."
::= { dot3PauseEntry 4 } ::= { dot3PauseEntry 4 }
-- 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 }
skipping to change at page 31, line 11 skipping to change at page 34, line 34
STATUS current STATUS current
DESCRIPTION "Couldn't initialize MAC chip for test." DESCRIPTION "Couldn't initialize MAC chip for test."
::= { dot3Errors 1 } ::= { dot3Errors 1 }
dot3ErrorLoopbackError OBJECT-IDENTITY dot3ErrorLoopbackError OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Expected data not received (or not received DESCRIPTION "Expected data not received (or not received
correctly) in loopback test." correctly) in loopback test."
::= { dot3Errors 2 } ::= { dot3Errors 2 }
-- { dot3 8 }, the dot3ChipSets tree, is defined in [28]
-- 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
skipping to change at page 36, line 33 skipping to change at page 40, line 11
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
6. Acknowledgements 6. Acknowledgements
This document was produced by the IETF Ethernet Interfaces and Hub This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people: contributions of the following people:
Lynn Kubinec Lynn Kubinec
Steve McRobert Steve McRobert
Dan Romascanu Dan Romascanu
Andrew Smith Andrew Smith
Geoff Thompson Geoff Thompson
This document is based on the Proposed Standard Ethernet MIB, RFC This document is based on the Proposed Standard Ethernet MIB, RFC
2358 [23], edited by John Flick of Hewlett-Packard and Jeffrey 2358 [23], edited by John Flick of Hewlett-Packard and Jeffrey
Johnson of RedBack Networks and produced by the 802.3 Hub MIB Working Johnson of RedBack Networks and produced by the 802.3 Hub MIB Working
Group. It extends that document by providing support for full-duplex Group. It extends that document by providing support for full-duplex
Ethernet interfaces and 1000 Mb/sec Ethernet interfaces as outlined Ethernet interfaces and 1000 Mb/sec Ethernet interfaces as outlined
in [16]. in [16].
RFC 2358, in turn, is almost completely based on both the Standard RFC 2358, in turn, is almost completely based on both the Standard
Ethernet MIB, RFC 1643 [21], and the Proposed Standard Ethernet MIB Ethernet MIB, RFC 1643 [21], and the Proposed Standard Ethernet MIB
skipping to change at page 37, line 32 skipping to change at page 41, line 11
Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN
Systems, contributed to later drafts of this memo. Marshall Rose of Systems, contributed to later drafts of this memo. Marshall Rose of
Performance Systems International, Inc. converted the document into Performance Systems International, Inc. converted the document into
RFC 1212 [3] concise format. Anil Rijsinghani of DEC contributed RFC 1212 [3] concise format. Anil Rijsinghani of DEC contributed
text that more adequately describes the TDR test. Thanks to Frank text that more adequately describes the TDR test. Thanks to Frank
Kastenholz of Interlan and Louis Steinberg of IBM for their Kastenholz of Interlan and Louis Steinberg of IBM for their
experimentation. experimentation.
7. References 7. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron Describing SNMP Management Frameworks", RFC 2571, May 1999.
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, Management Information for TCP/IP-based Internets", STD 16, RFC
RFC 1155, Performance Systems International, Hughes LAN Systems, 1155, May 1990.
May 1990
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, Performance Systems International, Hughes LAN Systems, RFC 1212, March 1991.
March 1991
[4] M. Rose, "A Convention for Defining Traps for use with the [4] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC 1215, Performance Systems International, March 1991 SNMP", RFC 1215, March 1991.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
"Structure of Management Information for Version 2 of the Simple M. and S. Waldbusser, "Structure of Management Information
Network Management Protocol (SNMPv2)", RFC 1902, SNMP Research, Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
Conventions for Version 2 of the Simple Network Management M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco RFC 2579, April 1999.
Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
"Conformance Statements for Version 2 of the Simple Network M. and S Waldbusser, "Conformance Statements for SMIv2", STD 58,
Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., RFC 2580, April 1999.
Cisco Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, SNMP Research, Network Management Protocol", STD 15, RFC 1157, May 1990.
Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP "Introduction to Community-based SNMPv2", RFC 1901, January
Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1996.
Inc., International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
"Transport Mappings for Version 2 of the Simple Network Mappings for Version 2 of the Simple Network Management Protocol
Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., (SNMPv2)", RFC 1906, January 1996.
Cisco Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Protocol (SNMP)", RFC 2572, May 1999.
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. (SNMPv3)", RFC 2574, May 1999.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Protocol (SNMPv2)", RFC 1905, January 1996.
Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 2573, May 1999.
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, (SNMP)", RFC 2575, May 1999.
Inc., Cisco Systems, Inc., January 1998
[16] IEEE, IEEE Std 802.3, 1998 Edition: "Information technology - [16] IEEE, IEEE Std 802.3, 1998 Edition: "Information technology -
Telecommunications and information exchange between systems - Telecommunications and information exchange between systems -
Local and metropolitan area networks - Specific requirements - Local and metropolitan area networks - Specific requirements -
Part 3: Carrier sense multiple access with collision detection Part 3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications" (CSMA/CD) access method and physical layer specifications"
(incorporating ANSI/IEEE Std. 802.3, 1996 Edition, IEEE Std. (incorporating ANSI/IEEE Std. 802.3, 1996 Edition, IEEE Std.
802.3r-1996, 802.3u-1995, 802.3x&y-1997, 802.3z-1998, and 802.3r-1996, 802.3u-1995, 802.3x&y-1997, 802.3z-1998, and
802.3aa-1998), September 1998. 802.3aa-1998), September 1998.
[17] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible [17] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible
MIB 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.
[18] Cook, J., "Definitions of Managed Objects for Ethernet-Like [18] Cook, J., "Definitions of Managed Objects for Ethernet-Like
Interface Types", RFC 1284, Chipcom Corporation, December 1991. Interface Types", RFC 1284, December 1991.
[19] Kastenholz, F., "Implementation Notes and Experience for The [19] Kastenholz, F., "Implementation Notes and Experience for The
Internet Ethernet MIB", RFC 1369, FTP Software, October 1992. Internet Ethernet MIB", RFC 1369, October 1992.
[20] Kastenholz, F., "Definitions of Managed Objects for the [20] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 1398, FTP Software, Inc., Ethernet-like Interface Types", RFC 1398, January 1993.
January 1993.
[21] Kastenholz, F., "Definitions of Managed Objects for the [21] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types", STD 50, RFC 1643, FTP Software, Ethernet-like Interface Types", STD 50, RFC 1643, July 1994.
Inc., July 1994.
[22] Kastenholz, F., "Definitions of Managed Objects for the [22] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types using SMIv2", RFC 1650, Ethernet-like Interface Types using SMIv2", RFC 1650, August
FTP Software, Inc., August 1994. 1994.
[23] Flick, J., and J. Johnson, "Definitions of Managed Objects [23] Flick, J. and J. Johnson, "Definitions of Managed Objects for
for the Ethernet-like Interface Types", RFC 2358, the Ethernet-like Interface Types", RFC 2358, June 1998.
Hewlett-Packard Company, RedBack Networks, June 1998.
[24] McCloghrie, K., and M. Rose, Editors, "Management Information [24] McCloghrie, K. and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets: MIB-II", Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, Hughes LAN Systems, Performance Systems STD 17, RFC 1213, March 1991.
International, March 1991.
[25] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB [25] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB
using SMIv2", RFC 2233, Cisco Systems, FTP Software, using SMIv2", RFC 2233, November 1997.
November 1997.
[26] Bradner, S., "Key words for use in RFCs to Indicate [26] Bradner, S., "Key words for use in RFCs to Indicate Requirements
Requirements Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[27] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster, [27] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster, D.,
D., McCloghrie, K., and S. Roberts, "Definitions of Managed McCloghrie, K. and S. Roberts, "Definitions of Managed Objects
Objects for IEEE 802.3 Medium Attachment Units (MAUs) using for IEEE 802.3 Medium Attachment Units (MAUs)", RFC 2668, August
SMIv2", work in progress, draft-ietf-hubmib-mau-mib-v2-02.txt, 1999.
Extreme Networks, Inc., Hewlett-Packard Company, Argon Networks,
LANNET Ltd., Cisco Systems, Inc., Cisco Systems Inc., Farallon
Computing Inc., January 1999.
[28] Flick, J., "Definitions of Object Identifiers for Identifying [28] Flick, J., "Definitions of Object Identifiers for Identifying
Ethernet Chip Sets", work in progress, Ethernet Chip Sets", RFC 2666, August 1999.
draft-ietf-hubmib-ether-chipsets-00.txt, Hewlett-Packard
Company, January 1999.
8. Security Considerations 8. Security Considerations
There are two management objects defined in this MIB that have a There are two management objects defined in this MIB that have a
MAX-ACCESS clause of read-write. Such objects may be considered MAX-ACCESS clause of read-write. Such objects may be considered
sensitive or vulnerable in some network environments. The support sensitive or vulnerable in some network environments. The support
for SET operations in a non-secure environment without proper for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
There are a number of managed objects in this MIB that may be There are a number of managed objects in this MIB that may be
skipping to change at page 41, line 5 skipping to change at page 43, line 51
these objects when sending them over the network via SNMP. Not all these objects when sending them over the network via SNMP. Not all
versions of SNMP provide features for such a secure environment. versions of SNMP provide features for such a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the SNMPv1 by itself is such an insecure environment. Even if the
network itself is secure (for example by using IPSec), even then, network itself is secure (for example by using IPSec), even then,
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET (read) the objects in this MIB. access and GET (read) the objects in this MIB.
It is recommended that the implementors consider the security It is recommended that the implementors consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2274 [12] and the View-based of the User-based Security Model RFC 2574 [12] and the View-based
Access Control Model RFC 2275 [15] is recommended. Access Control Model RFC 2575 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to those objects only to those principals configured to give access to those objects only to those principals
(users) that have legitimate rights to access them. (users) that have legitimate rights to access them.
9. Author's Addresses 9. Authors' Addresses
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557 Roseville, CA 95747-5557
Phone: +1 916 785 4018 Phone: +1 916 785 4018
Email: johnf@rose.hp.com EMail: johnf@rose.hp.com
Jeffrey Johnson Jeffrey Johnson
RedBack Networks RedBack Networks
2570 North First Street, Suite 410 2570 North First Street, Suite 410
San Jose, CA, 95131, USA San Jose, CA, 95131, USA
Phone: +1 408 571 2699 Phone: +1 408 571 2699
EMail: jeff@redbacknetworks.com EMail: jeff@redbacknetworks.com
A. Change Log A. Change Log
A.1. Changes since RFC 2358 A.1. Changes since RFC 2358
This section enumerates changes made to RFC 2358 to produce this This section enumerates changes made to RFC 2358 to produce this
document. document.
(1) Section 2 has been replaced with the current SNMP (1) Section 2 has been replaced with the current SNMP
Management Framework boilerplate. Management Framework boilerplate.
(2) The ifMtu mapping has been clarified. (2) The ifMtu mapping has been clarified.
(3) The relationship between the IEEE 802.3 octet counters (3) The relationship between the IEEE 802.3 octet counters
and the IF-MIB octet counters has been clarified. and the IF-MIB octet counters has been clarified.
(4) REFERENCE clauses have been updated to reflect the (4) REFERENCE clauses have been updated to reflect the
actual IEEE 802.3 managed object that each MIB object actual IEEE 802.3 managed object that each MIB object
is based on. is based on.
(5) The following object DESCRIPTION clauses have been (5) The following object DESCRIPTION clauses have been
updated to reflect that they do not increment in updated to reflect that they do not increment in
full-duplex mode: dot3StatsSingleCollisionFrames, full-duplex mode: dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames, dot3StatsSQETestErrors, dot3StatsMultipleCollisionFrames, dot3StatsSQETestErrors,
dot3StatsDeferredTransmissions, dot3StatsLateCollisions, dot3StatsDeferredTransmissions, dot3StatsLateCollisions,
dot3StatsExcessiveCollisions, dot3StatsCarrierSenseErrors, dot3StatsExcessiveCollisions, dot3StatsCarrierSenseErrors,
dot3CollFrequencies. dot3CollFrequencies.
(6) The following object DESCRIPTION clauses have been (6) The following object DESCRIPTION clauses have been
updated to reflect behaviour on full-duplex and updated to reflect behaviour on full-duplex and
1000 Mb/s interfaces: dot3StatsAlignmentErrors, 1000 Mb/s interfaces: dot3StatsAlignmentErrors,
dot3StatsFCSErrors, dot3StatsSQETestErrors, dot3StatsFCSErrors, dot3StatsSQETestErrors,
dot3StatsLateCollisions, dot3StatsSymbolErrors. dot3StatsLateCollisions, dot3StatsSymbolErrors.
(7) Two new tables, dot3ControlTable and dot3PauseTable, (7) Two new tables, dot3ControlTable and dot3PauseTable,
have been added. have been added.
(8) A new object, dot3StatsDuplexStatus, has been added. (8) A new object, dot3StatsDuplexStatus, has been added.
(9) The object groups and compliances have been restructured. (9) The object groups and compliances have been restructured.
(10) The dot3StatsEtherChipSet object has been deprecated. (10) The dot3StatsEtherChipSet object has been deprecated.
(11) The dot3ChipSets have been moved to a separate document. (11) The dot3ChipSets have been moved to a separate document.
A.2. Changes between RFC 1650 and RFC 2358 A.2. Changes between RFC 1650 and RFC 2358
This section enumerates changes made to RFC 1650 to produce RFC 2358. This section enumerates changes made to RFC 1650 to produce RFC 2358.
(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.
(3) The definition of the object dot3StatsIndex has been (3) The definition of the object dot3StatsIndex has been
converted to use the SMIv2 OBJECT-TYPE macro. converted to use the SMIv2 OBJECT-TYPE macro.
(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. (7) The discussion of ifType has been expanded.
(8) A section on mapping of Interfaces MIB objects has (8) A section on mapping of Interfaces MIB objects has
been added. been added.
(9) A section defining the relationship of this MIB to (9) A section defining the relationship of this MIB to
the MAU MIB has been added. the MAU MIB has been added.
(10) A section on the mapping of IEEE 802.3 managed objects (10) A section on the mapping of IEEE 802.3 managed objects
to this MIB and the Interfaces MIB has been added. to this MIB and the Interfaces MIB has been added.
(11) Converted the dot3Tests, dot3Errors, and dot3ChipSets (11) Converted the dot3Tests, dot3Errors, and dot3ChipSets
OIDs to use the OBJECT-IDENTITY macro. OIDs to use the OBJECT-IDENTITY macro.
(12) Added to the list of registered dot3ChipSets. (12) Added to the list of registered dot3ChipSets.
(13) An intellectual property notice and copyright notice (13) An intellectual property notice and copyright notice
were added, as required by RFC 2026. were added, as required by RFC 2026.
B. Full Copyright Statement B. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
skipping to change at line 2027 skipping to change at page 47, line 32
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 143 change blocks. 
337 lines changed or deleted 485 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/