draft-ietf-hubmib-mau-mib-v3-00.txt   draft-ietf-hubmib-mau-mib-v3-01.txt 
skipping to change at page 1, line 22 skipping to change at page 1, line 22
K. de Graaf K. de Graaf
Argon Networks Argon Networks
D. Romascanu D. Romascanu
Avaya Inc. Avaya Inc.
D. McMaster D. McMaster
Cisco Systems, Inc. Cisco Systems, Inc.
K. McCloghrie K. McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
S. Roberts S. Roberts
Farallon Computing, Inc. Farallon Computing, Inc.
June 2001 February 2002
Definitions of Managed Objects for Definitions of Managed Objects for
IEEE 802.3 Medium Attachment Units (MAUs) IEEE 802.3 Medium Attachment Units (MAUs)
<draft-ietf-hubmib-mau-mib-v3-00.txt> <draft-ietf-hubmib-mau-mib-v3-01.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line 7 skipping to change at page 2, line 7
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
To view the list Internet-Draft Shadow Directories, see To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). 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 2668, ''Definitions of Managed Objects for This memo obsoletes RFC 2668, ''Definitions of Managed Objects for
IEEE 802.3 Medium Attachment Units (MAUs)''. This memo extends that IEEE 802.3 Medium Attachment Units (MAUs)''. This memo extends that
specification by including management information useful for the specification by including management information useful for the
management of 10 gigabit per second (Gb/s) MAUs. management of 10 gigabit per second (Gb/s) MAUs. This memo also
obsoletes RFC 1515, ''Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)''.
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
skipping to change at page 2, line 38 skipping to change at page 2, line 40
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
hubmib@ietf.org. hubmib@ietf.org.
Table of Contents Table of Contents
1. Introduction ............................................... 3 1. Introduction ............................................... 3
2. The SNMP Management Framework .............................. 3 2. The SNMP Management Framework .............................. 3
3. Overview ................................................... 4 3. Overview ................................................... 4
3.1. Relationship to RFC 2668 ................................. 4 3.1. Relationship to RFC 2668 ................................. 4
3.2. Relationship to RFC 2239 ................................. 4 3.2. Relationship to RFC 2239 ................................. 5
3.3. Relationship to RFC 1515 ................................. 5 3.3. Relationship to RFC 1515 ................................. 5
3.4. MAU Management ........................................... 5
3.5. Relationship to Other MIBs ............................... 5 3.5. Relationship to Other MIBs ............................... 5
3.5.1. Relationship to the Interfaces MIB ..................... 5 3.5.1. Relationship to the Interfaces MIB ..................... 5
3.5.2. Relationship to the 802.3 Repeater MIB ................. 6 3.5.2. Relationship to the 802.3 Repeater MIB ................. 6
3.6. Management of Internal MAUs .............................. 6 3.6. Management of Internal MAUs .............................. 6
4. Definitions ................................................ 6 3.7. Mapping of IEEE 802.3 Managed Objects .................... 7
5. Intellectual Property ...................................... 51 4. Definitions ................................................ 8
6. Acknowledgements ........................................... 52 5. Intellectual Property ...................................... 55
7. References ................................................. 52 6. Acknowledgements ........................................... 56
8. Security Considerations .................................... 54 7. References ................................................. 56
9. Authors' Addresses ......................................... 55 8. Security Considerations .................................... 59
A. Change Log ................................................. 55 9. Authors' Addresses ......................................... 59
A.1. Changes since RFC 2668 ................................... 55 A. Change Log ................................................. 59
A.2. Changes between RFC 2239 and RFC 2668 .................... 56 A.1. Changes since RFC 2668 ................................... 59
B. Full Copyright Statement ................................... 57 A.2. Changes between RFC 2239 and RFC 2668 .................... 60
B. Full Copyright Statement ................................... 61
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 IEEE 802.3 Medium In particular, it defines objects for managing IEEE 802.3 Medium
Attachment Units (MAUs). Attachment Units (MAUs).
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:
RFC 2668 [23]. RFC 2668 [RFC2668].
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 [22]. document are to be interpreted as described in [RFC2119].
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 2571 [1]. o An overall architecture, described in RFC 2571 [RFC2571].
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 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
The second version, called SMIv2, is described in STD 58, RFC 1215 [RFC1215]. The second version, called SMIv2, is described
2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
STD 58, RFC 2580 [RFC2580].
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 STD 15, RFC 1157 [8]. A second version of the SNMP described in STD 15, RFC 1157 [RFC1157]. A second version of
message protocol, which is not an Internet standards track the SNMP message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9] and track protocol, is called SNMPv2c and described in RFC 1901
RFC 1906 [10]. The third version of the message protocol is [RFC1901] and RFC 1906 [RFC1906]. The third version of the
called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and message protocol is called SNMPv3 and described in RFC 1906
RFC 2574 [12]. [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
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 STD 15, RFC 1157 [8]. A second set of protocol described in STD 15, RFC 1157 [RFC1157]. A second set of
operations and associated PDU formats is described in RFC 1905 protocol operations and associated PDU formats is described in
[13]. RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2573 [14] and o A set of fundamental applications described in RFC 2573
the view-based access control mechanism described in RFC 2575 [RFC2573] and the view-based access control mechanism described
[15]. in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [16]. can be found in RFC 2570 [RFC2570].
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
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
3. Overview 3. Overview
3.1. Relationship to RFC 2668 Instances of these object types represent attributes of an IEEE 802.3
MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD
standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3
repeaters or to 802.3 (Ethernet-like) interfaces. For convenience
this document refers to these devices as "repeater MAUs" and
"interface MAUs."
The definitions presented here are based on Section 30.5, "Layer
Management for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Medium
Attachment Units (MAUs)", Section 30.6, "Management for link Auto-
Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed
object classes" of IEEE Std. 802.3, 2000 edition [IEEE802.3], as
ammended by IEEE Draft P802.3ae/D4.01 [P802.3ae]. That specification
includes definitions for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s
devices. This specification is intended to serve the same purpose: to
provide for management of all types of Ethernet/802.3 MAUs.
3.1. Relationship to RFC 2668
This MIB is intended to be a superset of that defined by RFC 2668 This MIB is intended to be a superset of that defined by RFC 2668
[23], which will go to historic status. This MIB includes all of the [RFC2668], which will go to historic status. This MIB includes all
objects contained in that MIB, with new and updated definitions which of the objects contained in that MIB, with new and updated
provide support for additional capabilities. Implementors are definitions which provide support for additional capabilities.
encouraged to support all applicable conformance groups in order to Implementors are encouraged to support all applicable conformance
make the best use of the new functionality provided by this MIB. The groups in order to make the best use of the new functionality
new and updated definitions provide management support for 10 Gb/s provided by this MIB. The new and updated definitions provide
devices. management support for 10 Gb/s devices.
3.2. Relationship to RFC 2239 3.2. Relationship to RFC 2239
RFC 2668 was a replacement for RFC 2239 [24], which is now historic. RFC 2668 was a replacement for RFC 2239 [RFC2239], which is now
RFC 2668 defined a superset of that defined by RFC 2239 [24], which historic. RFC 2668 defined a superset of that defined by RFC 2239
contained all of the objects defined in RFC 2239, plus several new [RFC2239], which contained all of the objects defined in RFC 2239,
ones which provide additional capabilities. The new objects provided plus several new ones which provide additional capabilities. The new
management support for: objects provided management support for:
o management of 1000 Mb/s devices o management of 1000 Mb/s devices
o management of PAUSE negotiation o management of PAUSE negotiation
o management of remote fault status o management of remote fault status
3.3. Relationship to RFC 1515 3.3. Relationship to RFC 1515
RFC 2239 was a replacement for RFC 1515 [25], which is now historic. RFC 2239 was a replacement for RFC 1515 [RFC1515], which is now
RFC 2239 defined a superset of RFC 1515 which contained all of the historic. RFC 2239 defined a superset of RFC 1515 which contained
objects defined in RFC 1515, plus several new ones which provided all of the objects defined in RFC 1515, plus several new ones which
additional capabilities. The new objects in RFC 2239 provided provided additional capabilities. The new objects in RFC 2239
management support for: provided management support for:
o management of 100 Mb/s devices o management of 100 Mb/s devices
o auto-negotiation on interface MAUs o auto-negotiation on interface MAUs
o jack management o jack management
3.4. MAU Management
Instances of these object types represent attributes of an IEEE 802.3
MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD
standard [17]. These MAUs may be connected to IEEE 802.3 repeaters
or to 802.3 (Ethernet-like) interfaces. For convenience this document
refers to these devices as "repeater MAUs" and "interface MAUs."
The definitions presented here are based on Section 30.5, "Layer
Management for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Medium
Attachment Units (MAUs)", and Annex 30A, "GDMO Specifications for
802.3 managed object classes" of IEEE Std. 802.3, 2000 edition [17],
as ammended by IEEE Draft P802.3ae/D3.0 [18]. That specification
includes definitions for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s
devices. This specification is intended to serve the same purpose: to
provide for management of all types of Ethernet/802.3 MAUs.
3.5. Relationship to Other MIBs 3.5. Relationship to Other MIBs
It is assumed that an agent implementing this MIB will also implement It is assumed that an agent implementing this MIB will also implement
(at least) the 'system' group defined in MIB-II [20]. The following (at least) the 'system' group defined in the SNMPv2 MIB [RFC1907].
sections identify other MIBs that such an agent should implement. The following sections identify other MIBs that such an agent should
implement.
3.5.1. Relationship to the Interfaces MIB. 3.5.1. Relationship to the Interfaces MIB.
The sections of this document that define interface MAU-related The sections of this document that define interface MAU-related
objects specify an extension to the Interfaces MIB [21]. An agent objects specify an extension to the Interfaces MIB [RFC2863]. An
implementing these interface-MAU related objects MUST also implement agent implementing these interface-MAU related objects MUST also
the relevant groups of Interface MIB. The value of the object implement the relevant groups of Interface MIB. The value of the
ifMauIfIndex is the same as the value of 'ifIndex' used to object ifMauIfIndex is the same as the value of 'ifIndex' used to
instantiate the interface to which the given MAU is connected. instantiate the interface to which the given MAU is connected.
It is REQUIRED that an agent implementing the interface-MAU related It is REQUIRED that an agent implementing the interface-MAU related
objects in this MIB will also implement the Ethernet-like Interfaces objects in this MIB will also implement the Ethernet-like Interfaces
MIB, [26]. MIB, [ETHERIF]. Furthermore, when the interface-MAU related objects
are used to manage a 10GBASE-W PHY -- e.e., when ifMauType is equal
to dot2MauType10GigBaseW or any other 10GBASE-W variant -- then the
agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB
[ETHERWIS] and must follow the interface layering model specified
therein. In that case the value of the object ifMauIfIndex is the
same as the value of 'ifIndex' for the layer at the top of the stack,
i.e., for the ifTable entry that has 'ifType' equal to
ethernetCsmacd(6). If the interface-MAU related objects are used to
manage a PHY that allows the MAU type to be changed dynamically, then
the agent SHALL create ifTable, ifStackTable, and ifInvStackTable
entries that pertain to the WIS when ifMauDefaultType is changed to a
10GBASEW variant (i.e., one of dot3MauType10GigBaseW,
dot3MauType10GigBaseEW, dot3MauType10GigBaseLW, or
dot3MauType10GigBaseSW) from any other type, and shall destroy the
WIS-related entries when ifMauDefaultType is changed to a non-
10GBASE-W type. The agent SHALL also change the values of
'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry indexed
by ifMauIfIndex as specified in [ETHERIF] and [ETHERWIS] when
ifMauDefaultType is manipulated in this way but SHALL NOT otherwise
alter that entry.
(Note that repeater ports are not represented as interfaces in the (Note that repeater ports are not represented as interfaces in the
Interface MIB.) Interface MIB.)
3.5.2. Relationship to the 802.3 Repeater MIB 3.5.2. Relationship to the 802.3 Repeater MIB
The section of this document that defines repeater MAU-related The section of this document that defines repeater MAU-related
objects specifies an extension to the 802.3 Repeater MIB defined in objects specifies an extension to the 802.3 Repeater MIB defined in
[19]. An agent implementing these repeater-MAU related objects MUST [RFC2108]. An agent implementing these repeater-MAU related objects
also implement the 802.3 Repeater MIB. MUST also implement the 802.3 Repeater MIB.
The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to
instantiate a repeater MAU variable SHALL be the same as the values instantiate a repeater MAU variable SHALL be the same as the values
of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the
port to which the given MAU is connected. port to which the given MAU is connected.
3.6. Management of Internal MAUs 3.6. Management of Internal MAUs
In some situations, a MAU can be "internal" -- i.e., its In some situations, a MAU can be "internal" -- i.e., its
functionality is implemented entirely within a device. For example, functionality is implemented entirely within a device. For example,
a managed repeater may contain an internal repeater-MAU and/or an a managed repeater may contain an internal repeater-MAU and/or an
internal interface-MAU through which management communications internal interface-MAU through which management communications
originating on one of the repeater's external ports pass in order to originating on one of the repeater's external ports pass in order to
reach the management agent associated with the repeater. Such reach the management agent associated with the repeater. Such
internal MAUs may or may not be managed. If they are managed, internal MAUs may or may not be managed. If they are managed,
objects describing their attributes should appear in the appropriate objects describing their attributes should appear in the appropriate
MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs and MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs and
dot3IfMauBasicGroup for internal interface-MAUs. dot3IfMauBasicGroup for internal interface-MAUs.
3.7. Mapping of IEEE 802.3 Managed Objects
IEEE 802.3 Managed Object Corresponding SNMP Object
oMAU
.aMAUID rpMauIndex or
ifMauIndex or
broadMauIndex
.aMAUType rpMauType or
ifMauType
.aMAUTypeList ifMauTypeListBits
.aMediaAvailable rpMauMediaAvailable or
ifMauMediaAvailable
.aLoseMediaCounter rpMauMediaAvailableStateExits
or
ifMauMediaAvailableStateExits
.aJabber rpMauJabberState and
rpMauJabberingStateEnters or
ifMauJabberState and
ifMauJabberingStateEnters
.aMAUAdminState rpMauStatus or
ifMauStatus
.aBbMAUXmitRcvSplitType broadMauXmtRcvSplitType
.aBroadbandFrequencies broadMauXmtCarrierFreq and
broadMauTranslationFreq
.aFalseCarriers rpMauFalseCarriers or
ifMauFalseCarriers
.acResetMAU rpMauStatus or
ifMauStatus
.acMAUAdminControl rpMauStatus or
ifMauStatus
.nJabber rpMauJabberTrap or
ifMauJabberTrap
oAutoNegotiation
.aAutoNegID ifMauIndex
.aAutoNegAdminState ifMauAutoNegAdminStatus
.aAutoNegRemoteSignalling ifMauAutoNegRemoteSignalling
.aAutoNegAutoConfig ifMauAutoNegConfig
.aAutoNegLocalTechnologyAbility ifMauAutoNegCapabilityBits
.aAutoNegAdvertisedTechnologyAbility ifMauAutoNegAdvertisedBits and
ifMauAutoNegRemoteFaultAdvertised
.aAutoNegReceivedTechnologyAbility ifMauAutoNegReceivedBits and
ifMauAutoNegRemoteFaultReceived
.acAutoNegRestartAutoConfig ifMauAutoNegRestart
.acAutoNegAdminControl ifMauAutoNegAdminStatus
The following IEEE 802.3 managed objects have not been included in
this MIB for the following reasons.
IEEE 802.3 Managed Object Corresponding SNMP Object
oMAU
.aIdleErrorCount Only useful for 100BaseT2,
which is not widely
implemented.
oAutoNegotiation
.aAutoNegLocalSelectorAbility Only needed for support of
.aAutoNegAdvertisedSelectorAbility isoethernet (802.9a), which is
.aAutoNegReceivedSelectorAbility not supported by this MIB.
4. Definitions 4. Definitions
MAU-MIB DEFINITIONS ::= BEGIN MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter32, Integer32, Counter32, Integer32, Counter64,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE,
OBJECT-IDENTITY, mib-2 OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue, TEXTUAL-CONVENTION TruthValue, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
InterfaceIndex InterfaceIndex
FROM IF-MIB; FROM IF-MIB;
mauMod MODULE-IDENTITY mauMod MODULE-IDENTITY
LAST-UPDATED "200106260024Z" -- June 26, 2001 LAST-UPDATED "200202280000Z" -- February 28, 2002
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@ietf.org "WG E-mail: hubmib@ietf.org
To subscribe: hubmib-request@ietf.org To subscribe: hubmib-request@ietf.org
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Avaya Inc. Postal: Avaya Inc.
Atidim Technology Park, Bldg. 3 Atidim Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
skipping to change at page 7, line 42 skipping to change at page 9, line 36
[IEEE 802.3 Std] refers to [IEEE 802.3 Std] refers to
IEEE Std 802.3, 2000 Edition: 'IEEE Standard IEEE Std 802.3, 2000 Edition: 'IEEE Standard
for Information technology - for Information technology -
Telecommunications and information exchange Telecommunications and information exchange
between systems - Local and metropolitan between systems - Local and metropolitan
area networks - Specific requirements - area networks - Specific requirements -
Part 3: Carrier sense multiple access with Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method collision detection (CSMA/CD) access method
and physical layer specifications', as and physical layer specifications', as
ammended by IEEE Draft P802.3ae/D3.0: ammended by IEEE Draft P802.3ae/D4.01:
'Supplement to Carrier Sense Multiple Access 'Supplement to Carrier Sense Multiple Access
with Collision Detection (CSMA/CD) Access with Collision Detection (CSMA/CD) Access
Method & Physica Layer Specifications - Method & Physica Layer Specifications -
Media Access Control (MAC) Parameters, Media Access Control (MAC) Parameters,
Physical Layer, and Management Parameters Physical Layer, and Management Parameters
for 10 Gb/s Operation', March 2001. for 10 Gb/s Operation', February 2002.
Of particular interest is Clause 30, '10Mb/s, Of particular interest is Clause 30, '10Mb/s,
100Mb/s, 1000Mb/s and 10 Gb/s Management'." 100Mb/s, 1000Mb/s and 10 Gb/s Management'."
REVISION "200106260024Z" -- June 26, 2001
REVISION "200202280000Z" -- February 28, 2002
DESCRIPTION "This version published as RFC XXXX. Updated DESCRIPTION "This version published as RFC XXXX. Updated
to include support for 10 Gb/s MAUs." to include support for 10 Gb/s MAUs."
REVISION "9908240400Z" -- August 24, 1999 REVISION "9908240400Z" -- August 24, 1999
DESCRIPTION "This version published as RFC 2668. Updated DESCRIPTION "This version published as RFC 2668. Updated
to include support for 1000 Mb/sec to include support for 1000 Mb/sec
MAUs and flow control negotiation." MAUs and flow control negotiation."
REVISION "9710310000Z" -- October 31, 1997 REVISION "9710310000Z" -- October 31, 1997
DESCRIPTION "Version published as RFC 2239." DESCRIPTION "Version published as RFC 2239."
skipping to change at page 8, line 42 skipping to change at page 10, line 37
rj45S(3), -- rj45 shielded rj45S(3), -- rj45 shielded
db9(4), db9(4),
bnc(5), bnc(5),
fAUI(6), -- female aui fAUI(6), -- female aui
mAUI(7), -- male aui mAUI(7), -- male aui
fiberSC(8), fiberSC(8),
fiberMIC(9), fiberMIC(9),
fiberST(10), fiberST(10),
telco(11), telco(11),
mtrj(12), -- fiber MT-RJ mtrj(12), -- fiber MT-RJ
hssdc(13) -- fiber channel style-2 hssdc(13), -- fiber channel style-2
fiberLC(14)
} }
dot3RpMauBasicGroup dot3RpMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
dot3IfMauBasicGroup dot3IfMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
dot3BroadMauBasicGroup dot3BroadMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
dot3IfMauAutoNegGroup dot3IfMauAutoNegGroup
skipping to change at page 23, line 18 skipping to change at page 25, line 16
ifMauType OBJECT IDENTIFIER, ifMauType OBJECT IDENTIFIER,
ifMauStatus INTEGER, ifMauStatus INTEGER,
ifMauMediaAvailable INTEGER, ifMauMediaAvailable INTEGER,
ifMauMediaAvailableStateExits Counter32, ifMauMediaAvailableStateExits Counter32,
ifMauJabberState INTEGER, ifMauJabberState INTEGER,
ifMauJabberingStateEnters Counter32, ifMauJabberingStateEnters Counter32,
ifMauFalseCarriers Counter32, ifMauFalseCarriers Counter32,
ifMauTypeList Integer32, ifMauTypeList Integer32,
ifMauDefaultType OBJECT IDENTIFIER, ifMauDefaultType OBJECT IDENTIFIER,
ifMauAutoNegSupported TruthValue, ifMauAutoNegSupported TruthValue,
ifMauTypeListBits BITS ifMauTypeListBits BITS,
ifMauHCFalseCarriers Counter64
} }
ifMauIfIndex OBJECT-TYPE ifMauIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This variable uniquely identifies the interface DESCRIPTION "This variable uniquely identifies the interface
to which the MAU described by this entry is to which the MAU described by this entry is
connected." connected."
REFERENCE "RFC 1213, ifIndex" REFERENCE "RFC 2863, ifIndex"
::= { ifMauEntry 1 } ::= { ifMauEntry 1 }
ifMauIndex OBJECT-TYPE ifMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This variable uniquely identifies the MAU DESCRIPTION "This variable uniquely identifies the MAU
described by this entry from among other MAUs described by this entry from among other MAUs
connected to the same interface (ifMauIfIndex)." connected to the same interface (ifMauIfIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
skipping to change at page 26, line 20 skipping to change at page 28, line 20
DESCRIPTION "If the MAU is a link or fiber type (FOIRL, DESCRIPTION "If the MAU is a link or fiber type (FOIRL,
10BASE-T, 10BASE-F) then this is equivalent to 10BASE-T, 10BASE-F) then this is equivalent to
the link test fail state/low light function. the link test fail state/low light function.
For an AUI or a coax (including broadband) MAU For an AUI or a coax (including broadband) MAU
this indicates whether or not loopback is this indicates whether or not loopback is
detected on the DI circuit. The value of this detected on the DI circuit. The value of this
attribute persists between packets for MAU types attribute persists between packets for MAU types
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
The value other(1) is returned if the The value other(1) is returned if the
mediaAvailable state is not one of 2 through 11. mediaAvailable state is not one of 2 through 18.
The value unknown(2) is returned when the MAU's The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is true state is unknown; for example, when it is
being initialized. At power-up or following a being initialized. At power-up or following a
reset, the value of this attribute will be reset, the value of this attribute will be
unknown for AUI, coax, and 10BASE-FP MAUs. For unknown for AUI, coax, and 10BASE-FP MAUs. For
these MAUs loopback will be tested on each these MAUs loopback will be tested on each
transmission during which no collision is transmission during which no collision is
detected. If DI is receiving input when DO detected. If DI is receiving input when DO
returns to IDL after a transmission and there returns to IDL after a transmission and there
skipping to change at page 28, line 29 skipping to change at page 30, line 29
DESCRIPTION "A count of the number of times that DESCRIPTION "A count of the number of times that
ifMauMediaAvailable for this MAU instance leaves ifMauMediaAvailable for this MAU instance leaves
the state available(3). the state available(3).
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management occur at re-initialization of the management
system, and at other times as indicated by the system, and at other times as indicated by the
value of ifCounterDiscontinuityTime." value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5,
aLoseMediaCounter. aLoseMediaCounter.
RFC 2233, ifCounterDiscontinuityTime." RFC 2863, ifCounterDiscontinuityTime."
::= { ifMauEntry 6 } ::= { ifMauEntry 6 }
ifMauJabberState OBJECT-TYPE ifMauJabberState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
noJabber(3), noJabber(3),
jabbering(4) jabbering(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 29, line 25 skipping to change at page 31, line 25
state jabbering(4). This counter will always state jabbering(4). This counter will always
indicate zero for MAUs of type dot1MauTypeAUI indicate zero for MAUs of type dot1MauTypeAUI
and those of speeds above 10Mbps. and those of speeds above 10Mbps.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management occur at re-initialization of the management
system, and at other times as indicated by the system, and at other times as indicated by the
value of ifCounterDiscontinuityTime." value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberCounter. aJabber.jabberCounter.
RFC 2233, ifCounterDiscontinuityTime." RFC 2863, ifCounterDiscontinuityTime."
::= { ifMauEntry 8 } ::= { ifMauEntry 8 }
ifMauFalseCarriers OBJECT-TYPE ifMauFalseCarriers OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of the number of false carrier events DESCRIPTION "A count of the number of false carrier events
during IDLE in 100BASE-X and 1000BASE-X links. during IDLE in 100BASE-X and 1000BASE-X links.
For all other MAU types, this counter will For all other MAU types, this counter will
always indicate zero. This counter does not always indicate zero. This counter does not
increment at the symbol rate. increment at the symbol rate.
It can increment after a valid carrier It can increment after a valid carrier
completion at a maximum rate of once per 100 ms completion at a maximum rate of once per 100 ms
for 100BASE-X and once per 10us for 1000BASE-X for 100BASE-X and once per 10us for 1000BASE-X
until the next CarrierEvent. until the next CarrierEvent.
This counter can roll over very quickly. A
management station is advised to poll the
ifMauHCFalseCarriers instead of this counter in
order to avoid loss of information.
Discontinuities in the value of this counter can Discontinuities in the value of this counter can
occur at re-initialization of the management occur at re-initialization of the management
system, and at other times as indicated by the system, and at other times as indicated by the
value of ifCounterDiscontinuityTime." value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers.
RFC 2233, ifCounterDiscontinuityTime." RFC 2863, ifCounterDiscontinuityTime."
::= { ifMauEntry 9 } ::= { ifMauEntry 9 }
ifMauTypeList OBJECT-TYPE ifMauTypeList OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
A value that uniquely identifies the set of A value that uniquely identifies the set of
possible IEEE 802.3 types that the MAU could be. possible IEEE 802.3 types that the MAU could be.
The value is a sum which initially takes the The value is a sum which initially takes the
value zero. Then, for each type capability of value zero. Then, for each type capability of
skipping to change at page 33, line 24 skipping to change at page 35, line 28
If auto-negotiation is present on this MAU, this If auto-negotiation is present on this MAU, this
object will map to ifMauAutoNegCapability. object will map to ifMauAutoNegCapability.
Note that this MAU may be capable of operating Note that this MAU may be capable of operating
as a MAU type that is beyond the scope of this as a MAU type that is beyond the scope of this
MIB. This is indicated by returning the MIB. This is indicated by returning the
bit value bOther in addition to any bit values bit value bOther in addition to any bit values
for capabilities that are listed above." for capabilities that are listed above."
::= { ifMauEntry 13 } ::= { ifMauEntry 13 }
ifMauHCFalseCarriers OBJECT-TYPE
SYNTAX Counter64
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of false carrier events
during IDLE in 100BASE-X and 1000BASE-X links.
For all other MAU types, this counter will
always indicate zero. This counter does not
increment at the symbol rate.
This counter is a 64 bit version of
ifMauFalseCarriers. Since the 32 bit version of
this counter can roll over very quickly,
management stations are advised to poll the
64 bit version instead in order to avoid loss
of information.
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.5.1.1.10, aFalseCarriers.
RFC 2863, ifCounterDiscontinuityTime."
::= { ifMauEntry 14 }
-- The ifJackTable applies to MAUs attached to interfaces -- The ifJackTable applies to MAUs attached to interfaces
-- which have one or more external jacks (connectors). -- which have one or more external jacks (connectors).
ifJackTable OBJECT-TYPE ifJackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfJackEntry SYNTAX SEQUENCE OF IfJackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "Information about the external jacks attached DESCRIPTION "Information about the external jacks attached
to MAUs attached to an interface." to MAUs attached to an interface."
::= { dot3IfMauBasicGroup 2 } ::= { dot3IfMauBasicGroup 2 }
skipping to change at page 43, line 19 skipping to change at page 45, line 50
broadMauIfIndex OBJECT-TYPE broadMauIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
This variable uniquely identifies the interface This variable uniquely identifies the interface
to which the MAU described by this entry is to which the MAU described by this entry is
connected." connected."
REFERENCE "Reference RFC 1213, ifIndex." REFERENCE "Reference RFC 2863, ifIndex."
::= { broadMauBasicEntry 1 } ::= { broadMauBasicEntry 1 }
broadMauIndex OBJECT-TYPE broadMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
This variable uniquely identifies the MAU This variable uniquely identifies the MAU
connected to interface broadMauIfIndex that is connected to interface broadMauIfIndex that is
described by this entry." described by this entry."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
skipping to change at page 48, line 37 skipping to change at page 51, line 19
mauIfGrpAutoNeg1000Mbps OBJECT-GROUP mauIfGrpAutoNeg1000Mbps OBJECT-GROUP
OBJECTS { ifMauAutoNegRemoteFaultAdvertised, OBJECTS { ifMauAutoNegRemoteFaultAdvertised,
ifMauAutoNegRemoteFaultReceived ifMauAutoNegRemoteFaultReceived
} }
STATUS current STATUS current
DESCRIPTION "Conformance group for 1000Mbps MAUs attached to DESCRIPTION "Conformance group for 1000Mbps MAUs attached to
interfaces with managed auto-negotiation." interfaces with managed auto-negotiation."
::= { mauModObjGrps 11 } ::= { mauModObjGrps 11 }
mauIfGrpHCStats OBJECT-GROUP
OBJECTS { ifMauHCFalseCarriers }
STATUS current
DESCRIPTION "Conformance for high capacity statistics for
MAUs attached to interfaces"
::= { mauModObjGrps 12 }
-- Notification groups -- Notification groups
rpMauNotifications NOTIFICATION-GROUP rpMauNotifications NOTIFICATION-GROUP
NOTIFICATIONS { rpMauJabberTrap } NOTIFICATIONS { rpMauJabberTrap }
STATUS current STATUS current
DESCRIPTION "Notifications for repeater MAUs." DESCRIPTION "Notifications for repeater MAUs."
::= { mauModNotGrps 1 } ::= { mauModNotGrps 1 }
ifMauNotifications NOTIFICATION-GROUP ifMauNotifications NOTIFICATION-GROUP
NOTIFICATIONS { ifMauJabberTrap } NOTIFICATIONS { ifMauJabberTrap }
skipping to change at page 50, line 26 skipping to change at page 53, line 16
GROUP mauBroadBasic GROUP mauBroadBasic
DESCRIPTION "Implementation of this group is mandatory DESCRIPTION "Implementation of this group is mandatory
for broadband MAUs." for broadband MAUs."
GROUP ifMauNotifications GROUP ifMauNotifications
DESCRIPTION "Implementation of this group is recommended DESCRIPTION "Implementation of this group is recommended
for MAUs attached to interfaces." for MAUs attached to interfaces."
::= { mauModCompls 2 } ::= { mauModCompls 2 }
mauModIfCompl2 MODULE-COMPLIANCE mauModIfCompl2 MODULE-COMPLIANCE
STATUS current STATUS deprecated
DESCRIPTION "Compliance for MAUs attached to interfaces." DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
Compliance for MAUs attached to interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { mauIfGrpBasic } MANDATORY-GROUPS { mauIfGrpBasic }
GROUP mauIfGrpHighCapacity GROUP mauIfGrpHighCapacity
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have 100Mb/s recommended for MAUs which have 100Mb/s
or greater capability." or greater capability."
GROUP mauIfGrpJack GROUP mauIfGrpJack
skipping to change at page 51, line 40 skipping to change at page 54, line 33
GROUP rpMauNotifications GROUP rpMauNotifications
DESCRIPTION "Implementation of this group is recommended DESCRIPTION "Implementation of this group is recommended
for MAUs attached to repeater ports." for MAUs attached to repeater ports."
OBJECT rpMauStatus OBJECT rpMauStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
::= { mauModCompls 4 } ::= { mauModCompls 4 }
mauModIfCompl3 MODULE-COMPLIANCE
STATUS current
DESCRIPTION "Compliance for MAUs attached to interfaces."
MODULE -- this module
MANDATORY-GROUPS { mauIfGrpBasic }
GROUP mauIfGrpHighCapacity
DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have 100Mb/s
or greater capability."
GROUP mauIfGrpHCStats
DESCRIPTION "Implemention of this group is mandatory
for MAUs which have 1000Mb/s capacity, and
is recommended for MAUs which have 100Mb/s
capacity."
GROUP mauIfGrpJack
DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."
GROUP mauIfGrpAutoNeg2
DESCRIPTION "Implementation of this group is mandatory
for MAUs which support managed
auto-negotiation."
GROUP mauIfGrpAutoNeg1000Mbps
DESCRIPTION "Implementation of this group is mandatory
for MAUs which have 1000Mb/s or greater
capability and support managed
auto-negotiation."
GROUP ifMauNotifications
DESCRIPTION "Implementation of this group is recommended
for MAUs attached to interfaces."
OBJECT ifMauStatus
MIN-ACCESS read-only
DESCRIPTION "Write access is not required."
::= { mauModCompls 5 }
END END
5. Intellectual Property 5. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
skipping to change at page 52, line 23 skipping to change at page 56, 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:
Mike Ayers
Mike Heard
Chuck Black Chuck Black
John Flick John Flick
Jeff Johnson Jeff Johnson
Kam Lam
Leon Leong Leon Leong
Mike Lui Mike Lui
Kerry McDonald
K.C. Norseth
Dave Perkins Dave Perkins
Dan Romascanu
Andrew Smith
Kaj Tesink
Geoff Thompson Geoff Thompson
Maurice Turcotte Maurice Turcotte
Paul Woodruff Paul Woodruff
Special thanks as well to Dave Perkins for his excellent work on the
SMICng compiler, which made it easy to take advantage of the latest
SNMPv2 constructs in this MIB.
7. References 7. References
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for Normative References
Describing SNMP Management Frameworks", RFC 2571, May 1999.
[2] Rose, M. and K. McCloghrie, "Structure and Identification of [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
Management Information for TCP/IP-based Internets", STD 16, J., Rose, M. and S. Waldbusser, "Structure of Management
RFC 1155, May 1990. Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
RFC 1212, March 1991. J., Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999.
[4] Rose, M., "A Convention for Defining Traps for use with the [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
SNMP", RFC 1215, March 1991. J., Rose, M. and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999.
[5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [IEEE802.3] IEEE, IEEE Std 802.3, 2000 Edition: "Information
M. and S. Waldbusser, "Structure of Management Information technology - Telecommunications and information exchange
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. between systems - Local and metropolitan area networks -
Specific requirements - Part 3: Carrier sense multiple
access with collision detection (CSMA/CD) access method
and physical layer specifications", (Adopted by ISO/IEC
and redesignated as ISO/IEC 8802-3:2000(E), 2000.
[6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3,
M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, IEEE Draft P802.3ae/D4.01, February 2002, work in
RFC 2579, April 1999. progress.
[7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
M. and S. Waldbusser, "Conformance Statements for SMIv2", STD MIB using SMIv2", RFC 2863, June 2000.
58, RFC 2580, April 1999.
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple [RFC2108] de Graaf, K., D. Romascanu, D. McMaster, and K.
Network Management Protocol", STD 15, RFC 1157, May 1990. McCloghrie, "Definitions of Managed Objects for IEEE
802.3 Repeater Devices using SMIv2", RFC 2108, February
1997.
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [ETHERIF] Flick, J., "Definitions of Managed Objects for the
"Introduction to Community-based SNMPv2", RFC 1901, January Ethernet-like Interface Types", work in progress,
1996. draft-ietf-hubmib-etherif-mib-v3-01.txt, February, 2002.
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport Non-Normative References
Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, January 1996.
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An
Processing and Dispatching for the Simple Network Management Architecture for Describing SNMP Management Frameworks",
Protocol (SNMP)", RFC 2572, May 1999. RFC 2571, April 1999.
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) [RFC1155] Rose, M. and K. McCloghrie, "Structure and
for version 3 of the Simple Network Management Protocol Identification of Management Information for
(SNMPv3)", RFC 2574, May 1999. TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
Operations for Version 2 of the Simple Network Management STD 16, RFC 1212, March 1991.
Protocol (SNMPv2)", RFC 1905, January 1996.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC [RFC1215] Rose, M., "A Convention for Defining Traps for use with
2573, May 1999. the SNMP", RFC 1215, March 1991.
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin,
Control Model (VACM) for the Simple Network Management Protocol "Simple Network Management Protocol", STD 15, RFC 1157,
(SNMP)", RFC 2575, May 1999. May 1990.
[16] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Version 3 of the Internet-Standard Network "Introduction to Community-based SNMPv2", RFC 1901,
Management Framework", RFC 2570, April 1999. January 1996.
[17] IEEE, IEEE Std 802.3, 2000 Edition: "Information technology - [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Telecommunications and information exchange between systems - "Transport Mappings for Version 2 of the Simple Network
Local and metropolitan area networks - Specific requirements - Management Protocol (SNMPv2)", RFC 1906, January 1996.
Part 3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications",
(Adopted by ISO/IEC and redesignated as ISO/IEC 8802-3:2000(E),
2000.
[18] IEEE, IEEE Draft P802.3ae/D3.0: "Supplement to Carrier Sense [RFC2572] Case, J., Harrington, D., Presuhn R. and B. Wijnen,
Multiple Access with Collision Detection (CSMA/CD) Access "Message Processing and Dispatching for the Simple
Method & Physical Layer Specifications - Media Access Control Network Management Protocol (SNMP)", RFC 2572, May 1999.
(MAC) Parameters, Physical Layer, and Management Parameters
for 10 Gb/s Operation", March 2001.
[19] de Graaf, K., D. Romascanu, D. McMaster, and K. McCloghrie, [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
"Definitions of Managed Objects for IEEE 802.3 Repeater Devices (USM) for version 3 of the Simple Network Management
using SMIv2", RFC 2108, February 1997. Protocol (SNMPv3)", RFC 2574, May 1999.
[20] McCloghrie, K. and M. Rose, Editors, "Management Information [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Base for Network Management of TCP/IP-based internets: MIB-II", "Protocol Operations for Version 2 of the Simple Network
STD 17, RFC 1213, March 1991. Management Protocol (SNMPv2)", RFC 1905, January 1996.
[21] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3
using SMIv2", RFC 2863, June 2000. Applications", RFC 2573, May 1999.
[22] Bradner, S., "Key words for use in RFCs to Indicate [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, May 1999.
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-Standard
Network Management Framework", RFC 2570, April 1999.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997. Requirements Levels", BCP 14, RFC 2119, March 1997.
[23] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster, D., [RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
McCloghrie, K. and S. Roberts, "Definitions of Managed Objects "Management Information Base for Version 2 of the
for IEEE 802.3 Medium Attachment Units (MAUs)", RFC 2668, August Simple Network Management Protocol (SNMPv2)", RFC 1907,
1999. January 1996.
[24] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K. and S. [RFC2668] Smith, A., Flick, J., deGraaf, K., Romascanu, D.,
Roberts, "Definitions of Managed Objects for IEEE 802.3 Medium McMaster, D., McCloghrie, K. and S. Roberts,
Attachment Units (MAUs) using SMIv2", RFC 2239, November 1997. "Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs)", RFC 2668, August 1999.
[25] McMaster, D., McCloghrie, K. and S. Roberts, "Definitions of [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie,
Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)", K. and S. Roberts, "Definitions of Managed Objects for
RFC 1515, September 1993. IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2",
RFC 2239, November 1997.
[26] Flick, J., and J. Johnson, "Definitions of Managed Objects for [RFC1515] McMaster, D., McCloghrie, K. and S. Roberts,
the Ethernet-like Interface Types", work in progress, "Definitions of Managed Objects for IEEE 802.3 Medium
draft-ietf-hubmib-etherif-mib-v3-00.txt, June, 2001. Attachment Units (MAUs)", RFC 1515, September 1993.
[ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald,
K., Norseth, K. C., and K. Tesink, "Definitions of
Managed Objects for the Ethernet WAN Interface
Sublayer", work in progress,
draft-ietf-hubmib-wis-mib-02.txt, February 2002.
8. Security Considerations 8. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write. Setting these objects can have a MAX-ACCESS clause of read-write. Setting these objects can
have a serious effect on the operation of the network, including: have a serious effect on the operation of the network, including:
enabling or disabling a MAU enabling or disabling a MAU
changing a MAU's default type changing a MAU's default type
enabling, disabling or restarting autonegotiation enabling, disabling or restarting autonegotiation
modifying the capabilities that a MAU advertizes during modifying the capabilities that a MAU advertizes during
autonegotiation. autonegotiation.
skipping to change at page 55, line 27 skipping to change at page 59, line 30
network operations. network operations.
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/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB. MIB.
It is recommended that the implementers consider the security It is recommended that the implementers 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 2574 [12] and the View-based of the User-based Security Model RFC 2574 [RFC2574] and the View-
Access Control Model RFC 2575 [15] is recommended. based Access Control Model RFC 2575 [RFC2575] 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. Authors' Addresses 9. Authors' Addresses
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
skipping to change at page 56, line 33 skipping to change at page 60, line 35
(7) ifMauTypeListBits has been extended with bits for the (7) ifMauTypeListBits has been extended with bits for the
10 Gb/s MAU types. 10 Gb/s MAU types.
(8) The MODULE-IDENTITY clause has been updated to (8) The MODULE-IDENTITY clause has been updated to
reflect the changes in the MIB module. reflect the changes in the MIB module.
(9) MIB boilerplate in section 2 has been updated to the (9) MIB boilerplate in section 2 has been updated to the
latest approved text. latest approved text.
(10) Added 64-bit version of ifMauFalseCarriers, and updated
compliances accordingly.
(11) Added section on mapping of IEEE managed objects to the
objects in this MIB module.
A.2. Changes between RFC 2239 and RFC 2668 A.2. Changes between RFC 2239 and RFC 2668
This section enumerates the changes made to RFC 2239 to produce RFC This section enumerates the changes made to RFC 2239 to produce RFC
2668. 2668.
(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) OBJECT-IDENTITY definitions have been added for gigabit MAU (2) OBJECT-IDENTITY definitions have been added for gigabit MAU
types. types.
skipping to change at page 57, line 39 skipping to change at page 61, line 47
(12) Refer to the Interfaces MIB, rather than the interfaces (12) Refer to the Interfaces MIB, rather than the interfaces
group of MIB-II. group of MIB-II.
(13) Updated references to refer to latest edition of IEEE 802.3. (13) Updated references to refer to latest edition of IEEE 802.3.
(14) An intellectual property notice was added, as required by (14) An intellectual property notice was added, as required by
RFC 2026. RFC 2026.
B. Full Copyright Statement B. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). 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
 End of changes. 

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