draft-ietf-hubmib-mau-mib-v3-02.txt   draft-ietf-hubmib-mau-mib-v3-03.txt 
Ethernet Interfaces and Hub MIB Working Group Editor of this version: Ethernet Interfaces and Hub MIB Working Group J. Flick
INTERNET DRAFT J. Flick INTERNET DRAFT Hewlett-Packard Company
Hewlett-Packard Company March 2003
Editors of previous versions:
A. Smith
Allegro Networks
J. Flick
Hewlett-Packard Company
K. de Graaf
Argon Networks
D. Romascanu
Avaya Inc.
D. McMaster
Cisco Systems, Inc.
K. McCloghrie
Cisco Systems, Inc.
S. Roberts
Farallon Computing, Inc.
May 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-02.txt> <draft-ietf-hubmib-mau-mib-v3-03.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 13 skipping to change at page 1, line 41
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). 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 In particular, it defines objects for managing IEEE 802.3 Medium
IEEE 802.3 Medium Attachment Units (MAUs)''. This memo extends that Attachment Units (MAUs).
specification by including management information useful for the
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 This memo obsoletes RFC 2668. This memo extends that specification
IEEE, continues to evolve, with scalable increases in speed, new by including management information useful for the management of 10
types of cabling and interfaces, and new features. This evolution gigabit per second (Gb/s) MAUs. This memo also obsoletes RFC 1515.
may require changes in the managed objects in order to reflect this
new functionality. This document, as with other documents issued by
this working group, reflects a certain stage in the evolution of
Ethernet technology. In the future, this document might be revised,
or new documents might be issued by the Ethernet Interfaces and Hub
MIB Working Group, in order to reflect the evolution of Ethernet
technology.
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 ............................................... 2
2. The SNMP Management Framework .............................. 3 2. The Internet-Standard Management Framework ................. 3
3. Overview ................................................... 4 3. Overview ................................................... 3
3.1. Relationship to RFC 2668 ................................. 4 3.1. Relationship to RFC 2668 ................................. 3
3.2. Relationship to RFC 2239 ................................. 5 3.2. Relationship to RFC 2239 ................................. 4
3.3. Relationship to RFC 1515 ................................. 5 3.3. Relationship to RFC 1515 ................................. 4
3.5. Relationship to Other MIBs ............................... 5 3.4. Relationship to Other MIBs ............................... 4
3.5.1. Relationship to the Interfaces MIB ..................... 5 3.4.1. Relationship to the Interfaces MIB ..................... 4
3.5.2. Relationship to the 802.3 Repeater MIB ................. 6 3.4.2. Relationship to the 802.3 Repeater MIB ................. 5
3.6. Management of Internal MAUs .............................. 6 3.5. Management of Internal MAUs .............................. 5
3.7. Mapping of IEEE 802.3 Managed Objects .................... 7 3.6. Mapping of IEEE 802.3 Managed Objects .................... 6
4. Definitions ................................................ 8 4. Definitions ................................................ 7
5. Intellectual Property ...................................... 55 5. Intellectual Property ...................................... 56
6. Acknowledgements ........................................... 56 6. Acknowledgements ........................................... 56
7. References ................................................. 56 7. Normative References ....................................... 57
8. Security Considerations .................................... 59 8. Informative References ..................................... 58
9. Authors' Addresses ......................................... 59 9. Security Considerations .................................... 58
A. Change Log ................................................. 59 10. Authors' Addresses ........................................ 59
A.1. Changes since RFC 2668 ................................... 59 A. Change Log ................................................. 60
A.1. Changes since RFC 2668 ................................... 60
A.2. Changes between RFC 2239 and RFC 2668 .................... 60 A.2. Changes between RFC 2239 and RFC 2668 .................... 60
B. Full Copyright Statement ................................... 61 B. Full Copyright Statement ................................... 62
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 [RFC2668]. module, RFC 2668 [RFC2668].
Ethernet technology, as defined by the 802.3 Working Group of the
IEEE, continues to evolve, with scalable increases in speed, new
types of cabling and interfaces, and new features. This evolution
may require changes in the managed objects in order to reflect this
new functionality. This document, as with other documents issued by
this working group, reflects a certain stage in the evolution of
Ethernet technology. In the future, this document might be revised,
or new documents might be issued by the Ethernet Interfaces and Hub
MIB Working Group, in order to reflect the evolution of Ethernet
technology.
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
2. The SNMP Management Framework 2. The Internet-Standard Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described
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
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of
the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906
[RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism described
in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework For a detailed overview of the documents that describe the current
can be found in RFC 2570 [RFC2570]. Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410].
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. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
This memo specifies a MIB module that is compliant to the SMIv2. A Structure of Management Information (SMI). This memo specifies a MIB
MIB conforming to the SMIv1 can be produced through the appropriate module that is compliant to the SMIv2, which is described in STD 58,
translations. The resulting translated MIB must be semantically RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
equivalent, except where objects or events are omitted because no [RFC2580].
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3. Overview 3. Overview
Instances of these object types represent attributes of an IEEE 802.3 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 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 standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3
repeaters or to 802.3 (Ethernet-like) interfaces. For convenience repeaters or to 802.3 (Ethernet-like) interfaces. For convenience
this document refers to these devices as "repeater MAUs" and this document refers to these devices as "repeater MAUs" and
"interface MAUs." "interface MAUs."
The definitions presented here are based on Section 30.5, "Layer 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 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- Attachment Units (MAUs)", Section 30.6, "Management for link Auto-
Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed
object classes" of IEEE Std. 802.3, 2000 edition [IEEE802.3], as object classes" of IEEE Std. 802.3, 2002 edition [IEEE802.3], as
amended by IEEE Draft P802.3ae/D4.3 [P802.3ae]. That specification amended by IEEE Std. 802.3ae-2002 [IEEE802.3ae]. That specification
includes definitions for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s 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 devices. This specification is intended to serve the same purpose: to
provide for management of all types of Ethernet/802.3 MAUs. provide for management of all types of Ethernet/802.3 MAUs.
3.1. Relationship to RFC 2668 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
[RFC2668], which will go to historic status. This MIB includes all [RFC2668]. This MIB includes all of the objects contained in that
of the objects contained in that MIB, with new and updated MIB, with new and updated definitions which provide support for
definitions which provide support for additional capabilities. additional capabilities. Implementors are encouraged to support all
Implementors are encouraged to support all applicable conformance applicable conformance groups in order to make the best use of the
groups in order to make the best use of the new functionality new functionality provided by this MIB. The new and updated
provided by this MIB. The new and updated definitions provide definitions provide management support for 10 Gb/s 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 [RFC2239], which is now RFC 2668 was a replacement for RFC 2239 [RFC2239]. RFC 2668 defined
historic. RFC 2668 defined a superset of that defined by RFC 2239 a superset of that defined by RFC 2239, which contained all of the
[RFC2239], which contained all of the objects defined in RFC 2239, objects defined in RFC 2239, plus several new ones which provide
plus several new ones which provide additional capabilities. The new additional capabilities. The new objects provided management support
objects provided management support for: 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 [RFC1515], which is now RFC 2239 was a replacement for RFC 1515 [RFC1515]. RFC 2239 defined
historic. RFC 2239 defined a superset of RFC 1515 which contained a superset of RFC 1515 which contained all of the objects defined in
all of the objects defined in RFC 1515, plus several new ones which RFC 1515, plus several new ones which provided additional
provided additional capabilities. The new objects in RFC 2239 capabilities. The new objects in RFC 2239 provided management
provided management support for: 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.5. Relationship to Other MIBs 3.4. 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 the SNMPv2 MIB [RFC1907]. (at least) the 'system' group defined in the SNMPv2 MIB [RFC3418].
The following sections identify other MIBs that such an agent should The following sections identify other MIBs that such an agent should
implement. implement.
3.5.1. Relationship to the Interfaces MIB. 3.4.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 [RFC2863]. An objects specify an extension to the Interfaces MIB [RFC2863]. An
agent implementing these interface-MAU related objects MUST also agent implementing these interface-MAU related objects MUST also
implement the relevant groups of Interface MIB. The value of the implement the relevant groups of the ifCompliance3 MODULE-COMPLIANCE
object ifMauIfIndex is the same as the value of 'ifIndex' used to statement of the Interface MIB. The value of the object ifMauIfIndex
instantiate the interface to which the given MAU is connected. is the same as the value of 'ifIndex' used to 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 fully comply with the dot3Compliance2
MIB, [ETHERIF]. Furthermore, when the interface-MAU related objects MODULE-COMPLIANCE statement of the Ethernet-like Interfaces MIB,
are used to manage a 10GBASE-W PHY -- i.e., when ifMauType is equal [ETHERIF]. Furthermore, when the interface-MAU related objects are
to dot3MauType10GigBaseW or any other 10GBASE-W variant -- then the used to manage a 10GBASE-W PHY -- i.e., when ifMauType is equal to
dot3MauType10GigBaseW or any other 10GBASE-W variant -- then the
agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB
[ETHERWIS] and must follow the interface layering model specified [ETHERWIS] and must follow the interface layering model specified
therein. In that case the value of the object ifMauIfIndex is the 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, 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 i.e., for the ifTable entry that has 'ifType' equal to
ethernetCsmacd(6). If the interface-MAU related objects are used 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 manage a PHY that allows the MAU type to be changed dynamically, then
the agent SHALL create ifTable, ifStackTable, and ifInvStackTable the agent SHALL create ifTable, ifStackTable, and ifInvStackTable
entries that pertain to the WIS when ifMauDefaultType is changed to a entries that pertain to the WIS when ifMauDefaultType is changed to a
10GBASEW variant (i.e., one of dot3MauType10GigBaseW, 10GBASEW variant (i.e., one of dot3MauType10GigBaseW,
skipping to change at page 6, line 37 skipping to change at page 5, line 35
WIS-related entries when ifMauDefaultType is changed to a non- WIS-related entries when ifMauDefaultType is changed to a non-
10GBASE-W type. The agent SHALL also change the values of 10GBASE-W type. The agent SHALL also change the values of
'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry indexed 'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry indexed
by ifMauIfIndex as specified in [ETHERIF] and [ETHERWIS] when by ifMauIfIndex as specified in [ETHERIF] and [ETHERWIS] when
ifMauDefaultType is manipulated in this way but SHALL NOT otherwise ifMauDefaultType is manipulated in this way but SHALL NOT otherwise
alter that entry. 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.4.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
[RFC2108]. An agent implementing these repeater-MAU related objects [RFC2108]. An agent implementing these repeater-MAU related objects
MUST also implement the 802.3 Repeater MIB. MUST also comply with the snmpRptrModCompl compliance statement of
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.5. 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 3.6. Mapping of IEEE 802.3 Managed Objects
IEEE 802.3 Managed Object Corresponding SNMP Object IEEE 802.3 Managed Object Corresponding SNMP Object
oMAU oMAU
.aMAUID rpMauIndex or .aMAUID rpMauIndex or
ifMauIndex or ifMauIndex or
broadMauIndex broadMauIndex
.aMAUType rpMauType or .aMAUType rpMauType or
ifMauType ifMauType
.aMAUTypeList ifMauTypeListBits .aMAUTypeList ifMauTypeListBits
skipping to change at page 8, line 38 skipping to change at page 7, line 37
4. Definitions 4. Definitions
MAU-MIB DEFINITIONS ::= BEGIN MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter32, Integer32, Counter64, 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, AutonomousType, 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 "200205100000Z" -- May 10, 2002 LAST-UPDATED "200302280000Z" -- February 28, 2003
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
Israel Israel
Tel: +972 3 645 8414 Tel: +972 3 645 8414
E-mail: dromasca@avaya.com E-mail: dromasca@avaya.com
Editor: John Flick Editor: John Flick
Postal: Hewlett-Packard Company Postal: Hewlett-Packard Company
skipping to change at page 9, line 27 skipping to change at page 8, line 25
Roseville, CA 95747-5557 Roseville, CA 95747-5557
USA USA
Tel: +1 916 785 4018 Tel: +1 916 785 4018
Fax: +1 916 785 1199 Fax: +1 916 785 1199
E-mail: johnf@rose.hp.com" E-mail: johnf@rose.hp.com"
DESCRIPTION "Management information for 802.3 MAUs. DESCRIPTION "Management information for 802.3 MAUs.
The following reference is used throughout The following reference is used throughout
this MIB module: this MIB module:
[IEEE 802.3 Std] refers to [IEEE 802.3 Std] refers to:
IEEE Std 802.3, 2000 Edition: 'IEEE Standard IEEE Std 802.3, 2002 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
amended by IEEE Draft P802.3ae/D4.3: amended by IEEE Std 802.3ae-2002:
'Supplement to Carrier Sense Multiple Access 'Amendment: Media Access Control (MAC)
with Collision Detection (CSMA/CD) Access Parameters, Physical Layer, and Management
Method & Physica Layer Specifications - Parameters for 10 Gb/s Operation', August,
Media Access Control (MAC) Parameters, 2002.
Physical Layer, and Management Parameters
for 10 Gb/s Operation', April 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 "200205100000Z" -- May 10, 2002 Copyright (C) The Internet Society (2003). This
DESCRIPTION "This version published as RFC XXXX. Updated version of this MIB module is part of RFC XXXX;
to include support for 10 Gb/s MAUs." see the RFC itself for full legal notices."
-- RFC Ed.: Replace XXXX with the actual RFC number & remove
-- this note
REVISION "9908240400Z" -- August 24, 1999 REVISION "200302280000Z" -- February 28, 2003
DESCRIPTION "Updated to include support for 10 Gb/s MAUs.
This resulted in the following revisions:
- Added OBJECT-IDENTITY definitions for
10 gigabit MAU types
- Added fiberLC jack type to JackType TC
- Extended ifMauTypeListBits with bits for
the 10 gigabit MAU types
- Added enumerations to ifMauMediaAvailable,
and updated its DESCRIPTION to reflect
behaviour at 10 Gb/s
- Added 64-bit version of ifMauFalseCarriers
and added mauIfGrpHCStats object group to
contain the new object
- Deprecated mauModIfCompl2 and replaced it
with mauModIfCompl3, which includes the new
object group
This version published as RFC XXXX."
-- RFC Ed.: Replace XXXX with the actual RFC number & remove
-- this note
REVISION "199908240400Z" -- 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 "199710310000Z" -- October 31, 1997
DESCRIPTION "Version published as RFC 2239." DESCRIPTION "Version published as RFC 2239."
REVISION "9309300000Z" -- September30, 1993 REVISION "199309300000Z" -- September30, 1993
DESCRIPTION "Initial version, published as RFC 1515." DESCRIPTION "Initial version, published as RFC 1515."
::= { snmpDot3MauMgt 6 } ::= { snmpDot3MauMgt 6 }
snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 }
-- textual conventions -- textual conventions
JackType ::= TEXTUAL-CONVENTION JackType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
skipping to change at page 11, line 4 skipping to change at page 10, line 23
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
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
-- object identities for MAU types -- object identities for MAU types
-- (see rpMauType and ifMauType for usage) -- (see rpMauType and ifMauType for usage)
dot3MauType dot3MauType
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 }
dot3MauTypeAUI OBJECT-IDENTITY dot3MauTypeAUI OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "no internal MAU, view from AUI" DESCRIPTION "no internal MAU, view from AUI"
REFERENCE "[IEEE 802.3 Std.], Section 7"
::= { dot3MauType 1 } ::= { dot3MauType 1 }
dot3MauType10Base5 OBJECT-IDENTITY dot3MauType10Base5 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "thick coax MAU (per 802.3 section 8)" DESCRIPTION "thick coax MAU"
REFERENCE "[IEEE 802.3 Std.], Section 7"
::= { dot3MauType 2 } ::= { dot3MauType 2 }
dot3MauTypeFoirl OBJECT-IDENTITY dot3MauTypeFoirl OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "FOIRL MAU (per 802.3 section 9.9)" DESCRIPTION "FOIRL MAU"
REFERENCE "[IEEE 802.3 Std.], Section 9.9"
::= { dot3MauType 3 } ::= { dot3MauType 3 }
dot3MauType10Base2 OBJECT-IDENTITY dot3MauType10Base2 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "thin coax MAU (per 802.3 section 10)" DESCRIPTION "thin coax MAU"
REFERENCE "[IEEE 802.3 Std.], Section 10"
::= { dot3MauType 4 } ::= { dot3MauType 4 }
dot3MauType10BaseT OBJECT-IDENTITY dot3MauType10BaseT OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "UTP MAU (per 802.3 section 14). DESCRIPTION "UTP MAU.
Note that it is strongly recommended that Note that it is strongly recommended that
agents return either dot3MauType10BaseTHD or agents return either dot3MauType10BaseTHD or
dot3MauType10BaseTFD if the duplex mode is dot3MauType10BaseTFD if the duplex mode is
known. However, management applications should known. However, management applications should
be prepared to receive this MAU type value from be prepared to receive this MAU type value from
older agent implementations." older agent implementations."
REFERENCE "[IEEE 802.3 Std.], Section 14"
::= { dot3MauType 5 } ::= { dot3MauType 5 }
dot3MauType10BaseFP OBJECT-IDENTITY dot3MauType10BaseFP OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "passive fiber MAU (per 802.3 section 16)" DESCRIPTION "passive fiber MAU"
REFERENCE "[IEEE 802.3 Std.], Section 16"
::= { dot3MauType 6 } ::= { dot3MauType 6 }
dot3MauType10BaseFB OBJECT-IDENTITY dot3MauType10BaseFB OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "sync fiber MAU (per 802.3 section 17)" DESCRIPTION "sync fiber MAU"
REFERENCE "[IEEE 802.3 Std.], Section 17"
::= { dot3MauType 7 } ::= { dot3MauType 7 }
dot3MauType10BaseFL OBJECT-IDENTITY dot3MauType10BaseFL OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "async fiber MAU (per 802.3 section 18) DESCRIPTION "async fiber MAU.
Note that it is strongly recommended that Note that it is strongly recommended that
agents return either dot3MauType10BaseFLHD or agents return either dot3MauType10BaseFLHD or
dot3MauType10BaseFLFD if the duplex mode is dot3MauType10BaseFLFD if the duplex mode is
known. However, management applications should known. However, management applications should
be prepared to receive this MAU type value from be prepared to receive this MAU type value from
older agent implementations." older agent implementations."
REFERENCE "[IEEE 802.3 Std.], Section 18"
::= { dot3MauType 8 } ::= { dot3MauType 8 }
dot3MauType10Broad36 OBJECT-IDENTITY dot3MauType10Broad36 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "broadband DTE MAU (per 802.3 section 11). DESCRIPTION "broadband DTE MAU.
Note that 10BROAD36 MAUs can be attached to Note that 10BROAD36 MAUs can be attached to
interfaces but not to repeaters." interfaces but not to repeaters."
REFERENCE "[IEEE 802.3 Std.], Section 11"
::= { dot3MauType 9 } ::= { dot3MauType 9 }
------ new since RFC 1515: ------ new since RFC 1515:
dot3MauType10BaseTHD OBJECT-IDENTITY dot3MauType10BaseTHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "UTP MAU (per 802.3 section 14), half duplex DESCRIPTION "UTP MAU, half duplex mode"
mode" REFERENCE "[IEEE 802.3 Std.], Section 14"
::= { dot3MauType 10 } ::= { dot3MauType 10 }
dot3MauType10BaseTFD OBJECT-IDENTITY dot3MauType10BaseTFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "UTP MAU (per 802.3 section 14), full duplex DESCRIPTION "UTP MAU, full duplex mode"
mode" REFERENCE "[IEEE 802.3 Std.], Section 14"
::= { dot3MauType 11 } ::= { dot3MauType 11 }
dot3MauType10BaseFLHD OBJECT-IDENTITY dot3MauType10BaseFLHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "async fiber MAU (per 802.3 section 18), half DESCRIPTION "async fiber MAU, half duplex mode"
duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 18"
::= { dot3MauType 12 } ::= { dot3MauType 12 }
dot3MauType10BaseFLFD OBJECT-IDENTITY dot3MauType10BaseFLFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "async fiber MAU (per 802.3 section 18), full DESCRIPTION "async fiber MAU, full duplex mode"
duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 18"
::= { dot3MauType 13 } ::= { dot3MauType 13 }
dot3MauType100BaseT4 OBJECT-IDENTITY dot3MauType100BaseT4 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "4 pair categ. 3 UTP (per 802.3 section 23)" DESCRIPTION "4 pair category 3 UTP"
REFERENCE "[IEEE 802.3 Std.], Section 23"
::= { dot3MauType 14 } ::= { dot3MauType 14 }
dot3MauType100BaseTXHD OBJECT-IDENTITY dot3MauType100BaseTXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), DESCRIPTION "2 pair category 5 UTP, half duplex mode"
half duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 25"
::= { dot3MauType 15 } ::= { dot3MauType 15 }
dot3MauType100BaseTXFD OBJECT-IDENTITY dot3MauType100BaseTXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), DESCRIPTION "2 pair category 5 UTP, full duplex mode"
full duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 25"
::= { dot3MauType 16 } ::= { dot3MauType 16 }
dot3MauType100BaseFXHD OBJECT-IDENTITY dot3MauType100BaseFXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X fiber over PMT (per 802.3 section 26), half DESCRIPTION "X fiber over PMT, half duplex mode"
duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 26"
::= { dot3MauType 17 } ::= { dot3MauType 17 }
dot3MauType100BaseFXFD OBJECT-IDENTITY dot3MauType100BaseFXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X fiber over PMT (per 802.3 section 26), full DESCRIPTION "X fiber over PMT, full duplex mode"
duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 26"
::= { dot3MauType 18 } ::= { dot3MauType 18 }
dot3MauType100BaseT2HD OBJECT-IDENTITY dot3MauType100BaseT2HD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32), DESCRIPTION "2 pair category 3 UTP, half duplex mode"
half duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 32"
::= { dot3MauType 19 } ::= { dot3MauType 19 }
dot3MauType100BaseT2FD OBJECT-IDENTITY dot3MauType100BaseT2FD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32), DESCRIPTION "2 pair category 3 UTP, full duplex mode"
full duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 32"
::= { dot3MauType 20 } ::= { dot3MauType 20 }
------ new since RFC 2239: ------ new since RFC 2239:
dot3MauType1000BaseXHD OBJECT-IDENTITY dot3MauType1000BaseXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, DESCRIPTION "PCS/PMA, unknown PMD, half duplex mode"
half duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 36"
::= { dot3MauType 21 } ::= { dot3MauType 21 }
dot3MauType1000BaseXFD OBJECT-IDENTITY dot3MauType1000BaseXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, DESCRIPTION "PCS/PMA, unknown PMD, full duplex mode"
full duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 36"
::= { dot3MauType 22 } ::= { dot3MauType 22 }
dot3MauType1000BaseLXHD OBJECT-IDENTITY dot3MauType1000BaseLXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over long-wavelength laser (per 802.3 DESCRIPTION "Fiber over long-wavelength laser, half duplex
section 38), half duplex mode" mode"
REFERENCE "[IEEE 802.3 Std.], Section 38"
::= { dot3MauType 23 } ::= { dot3MauType 23 }
dot3MauType1000BaseLXFD OBJECT-IDENTITY dot3MauType1000BaseLXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over long-wavelength laser (per 802.3 DESCRIPTION "Fiber over long-wavelength laser, full duplex
section 38), full duplex mode" mode"
REFERENCE "[IEEE 802.3 Std.], Section 38"
::= { dot3MauType 24 } ::= { dot3MauType 24 }
dot3MauType1000BaseSXHD OBJECT-IDENTITY dot3MauType1000BaseSXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over short-wavelength laser (per 802.3 DESCRIPTION "Fiber over short-wavelength laser, half
section 38), half duplex mode" duplex mode"
REFERENCE "[IEEE 802.3 Std.], Section 38"
::= { dot3MauType 25 } ::= { dot3MauType 25 }
dot3MauType1000BaseSXFD OBJECT-IDENTITY dot3MauType1000BaseSXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over short-wavelength laser (per 802.3 DESCRIPTION "Fiber over short-wavelength laser, full
section 38), full duplex mode" duplex mode"
REFERENCE "[IEEE 802.3 Std.], Section 38"
::= { dot3MauType 26 } ::= { dot3MauType 26 }
dot3MauType1000BaseCXHD OBJECT-IDENTITY dot3MauType1000BaseCXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 DESCRIPTION "Copper over 150-Ohm balanced cable, half
section 39), half duplex mode" duplex mode"
REFERENCE "[IEEE 802.3 Std.], Section 39"
::= { dot3MauType 27 } ::= { dot3MauType 27 }
dot3MauType1000BaseCXFD OBJECT-IDENTITY dot3MauType1000BaseCXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 DESCRIPTION "Copper over 150-Ohm balanced cable, full
section 39), full duplex mode" duplex mode"
REFERENCE "[IEEE 802.3 Std.], Section 39"
::= { dot3MauType 28 } ::= { dot3MauType 28 }
dot3MauType1000BaseTHD OBJECT-IDENTITY dot3MauType1000BaseTHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section DESCRIPTION "Four-pair Category 5 UTP, half duplex mode"
40), half duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 40"
::= { dot3MauType 29 } ::= { dot3MauType 29 }
dot3MauType1000BaseTFD OBJECT-IDENTITY dot3MauType1000BaseTFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section DESCRIPTION "Four-pair Category 5 UTP, full duplex mode"
40), full duplex mode" REFERENCE "[IEEE 802.3 Std.], Section 40"
::= { dot3MauType 30 } ::= { dot3MauType 30 }
------ new since RFC 2668: ------ new since RFC 2668:
dot3MauType10GigBaseX OBJECT-IDENTITY dot3MauType10GigBaseX OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X PCS/PMA (per 802.3 section 48), unknown PMD." DESCRIPTION "X PCS/PMA, unknown PMD."
REFERENCE "[IEEE 802.3 Std.], Section 48"
::= { dot3MauType 31 } ::= { dot3MauType 31 }
dot3MauType10GigBaseLX4 OBJECT-IDENTITY dot3MauType10GigBaseLX4 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X fiber over WWDM optics (per 802.3 section DESCRIPTION "X fiber over WWDM optics"
53)" REFERENCE "[IEEE 802.3 Std.], Section 53"
::= { dot3MauType 32 } ::= { dot3MauType 32 }
dot3MauType10GigBaseR OBJECT-IDENTITY dot3MauType10GigBaseR OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "R PCS/PMA (per 802.3 section 49), unknown PMD." DESCRIPTION "R PCS/PMA, unknown PMD."
REFERENCE "[IEEE 802.3 Std.], Section 49"
::= { dot3MauType 33 } ::= { dot3MauType 33 }
dot3MauType10GigBaseER OBJECT-IDENTITY dot3MauType10GigBaseER OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "R fiber over 1550 nm optics (per 802.3 section DESCRIPTION "R fiber over 1550 nm optics"
52)" REFERENCE "[IEEE 802.3 Std.], Section 52"
::= { dot3MauType 34 } ::= { dot3MauType 34 }
dot3MauType10GigBaseLR OBJECT-IDENTITY dot3MauType10GigBaseLR OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "R fiber over 1310 nm optics (per 802.3 section DESCRIPTION "R fiber over 1310 nm optics"
52)" REFERENCE "[IEEE 802.3 Std.], Section 52"
::= { dot3MauType 35 } ::= { dot3MauType 35 }
dot3MauType10GigBaseSR OBJECT-IDENTITY dot3MauType10GigBaseSR OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "R fiber over 850 nm optics (per 802.3 section DESCRIPTION "R fiber over 850 nm optics"
52)" REFERENCE "[IEEE 802.3 Std.], Section 52"
::= { dot3MauType 36 } ::= { dot3MauType 36 }
dot3MauType10GigBaseW OBJECT-IDENTITY dot3MauType10GigBaseW OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "W PCS/PMA (per 802.3 section 49 and 50), DESCRIPTION "W PCS/PMA, unknown PMD."
unknown PMD." REFERENCE "[IEEE 802.3 Std.], Section 49 and 50"
::= { dot3MauType 37 } ::= { dot3MauType 37 }
dot3MauType10GigBaseEW OBJECT-IDENTITY dot3MauType10GigBaseEW OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "W fiber over 1550 nm optics (per 802.3 section DESCRIPTION "W fiber over 1550 nm optics"
52)" REFERENCE "[IEEE 802.3 Std.], Section 52"
::= { dot3MauType 38 } ::= { dot3MauType 38 }
dot3MauType10GigBaseLW OBJECT-IDENTITY dot3MauType10GigBaseLW OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "W fiber over 1310 nm optics (per 802.3 section DESCRIPTION "W fiber over 1310 nm optics"
52)" REFERENCE "[IEEE 802.3 Std.], Section 52"
::= { dot3MauType 39 } ::= { dot3MauType 39 }
dot3MauType10GigBaseSW OBJECT-IDENTITY dot3MauType10GigBaseSW OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "W fiber over 850 nm optics (per 802.3 section DESCRIPTION "W fiber over 850 nm optics"
52)" REFERENCE "[IEEE 802.3 Std.], Section 52"
::= { dot3MauType 40 } ::= { dot3MauType 40 }
-- --
-- The Basic Repeater MAU Table -- The Basic Repeater MAU Table
-- --
rpMauTable OBJECT-TYPE rpMauTable OBJECT-TYPE
SYNTAX SEQUENCE OF RpMauEntry SYNTAX SEQUENCE OF RpMauEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 16, line 48 skipping to change at page 16, line 40
rpMauPortIndex, rpMauPortIndex,
rpMauIndex rpMauIndex
} }
::= { rpMauTable 1 } ::= { rpMauTable 1 }
RpMauEntry ::= RpMauEntry ::=
SEQUENCE { SEQUENCE {
rpMauGroupIndex Integer32, rpMauGroupIndex Integer32,
rpMauPortIndex Integer32, rpMauPortIndex Integer32,
rpMauIndex Integer32, rpMauIndex Integer32,
rpMauType OBJECT IDENTIFIER, rpMauType AutonomousType,
rpMauStatus INTEGER, rpMauStatus INTEGER,
rpMauMediaAvailable INTEGER, rpMauMediaAvailable INTEGER,
rpMauMediaAvailableStateExits Counter32, rpMauMediaAvailableStateExits Counter32,
rpMauJabberState INTEGER, rpMauJabberState INTEGER,
rpMauJabberingStateEnters Counter32, rpMauJabberingStateEnters Counter32,
rpMauFalseCarriers Counter32 rpMauFalseCarriers Counter32
} }
rpMauGroupIndex OBJECT-TYPE rpMauGroupIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current STATUS current
DESCRIPTION "This variable uniquely identifies the group DESCRIPTION "This variable uniquely identifies the group
containing the port to which the MAU described containing the port to which the MAU described
by this entry is connected. by this entry is connected.
Note: In practice, a group will generally be Note: In practice, a group will generally be
a field-replaceable unit (i.e., module, card, a field-replaceable unit (i.e., module, card,
or board) that can fit in the physical system or board) that can fit in the physical system
enclosure, and the group number will correspond enclosure, and the group number will correspond
to a number marked on the physical enclosure. to a number marked on the physical enclosure.
The group denoted by a particular value of this The group denoted by a particular value of this
object is the same as the group denoted by the object is the same as the group denoted by the
same value of rptrGroupIndex." same value of rptrGroupIndex."
REFERENCE "Reference RFC 2108, rptrGroupIndex." REFERENCE "Reference RFC 2108, rptrGroupIndex."
::= { rpMauEntry 1 } ::= { rpMauEntry 1 }
rpMauPortIndex OBJECT-TYPE rpMauPortIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current STATUS current
DESCRIPTION "This variable uniquely identifies the repeater DESCRIPTION "This variable uniquely identifies the repeater
port within group rpMauGroupIndex to which the port within group rpMauGroupIndex to which the
MAU described by this entry is connected." MAU described by this entry is connected."
REFERENCE "Reference RFC 2108, rptrPortIndex." REFERENCE "Reference RFC 2108, rptrPortIndex."
::= { rpMauEntry 2 } ::= { rpMauEntry 2 }
rpMauIndex OBJECT-TYPE rpMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
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 described by this entry from among other
MAUs connected to the same port MAUs connected to the same port
(rpMauPortIndex)." (rpMauPortIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 } ::= { rpMauEntry 3 }
rpMauType OBJECT-TYPE rpMauType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies the MAU type. An DESCRIPTION "This object identifies the MAU type. An
initial set of MAU types are defined above. The initial set of MAU types are defined above. The
assignment of OBJECT IDENTIFIERs to new types of assignment of OBJECT IDENTIFIERs to new types of
MAUs is managed by the IANA. If the MAU type is MAUs is managed by the IANA. If the MAU type is
unknown, the object identifier unknown, the object identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
skipping to change at page 20, line 35 skipping to change at page 20, line 30
returns to IDL after a transmission and there returns to IDL after a transmission and there
has been no collision during the transmission has been no collision during the transmission
then loopback will be detected. The value of then loopback will be detected. The value of
this attribute will only change during this attribute will only change during
non-collided transmissions for AUI, coax, and non-collided transmissions for AUI, coax, and
10BASE-FP MAUs. 10BASE-FP MAUs.
For 100Mbps and 1000Mbps MAUs, the enumerations For 100Mbps and 1000Mbps MAUs, the enumerations
match the states within the respective link match the states within the respective link
integrity state diagrams, fig 32-16, 23-12 and integrity state diagrams, fig 32-16, 23-12 and
24-15 of sections 32, 23 and 24 of [16]. Any 24-15 of sections 32, 23 and 24 of [IEEE802.3].
MAU which implements management of Any MAU which implements management of
auto-negotiation will map remote fault auto-negotiation will map remote fault
indication to remote fault. indication to remote fault.
The value available(3) indicates that the link, The value available(3) indicates that the link,
light, or loopback is normal. The value light, or loopback is normal. The value
notAvailable(4) indicates link loss, low light, notAvailable(4) indicates link loss, low light,
or no loopback. or no loopback.
The value remoteFault(5) indicates that a fault The value remoteFault(5) indicates that a fault
has been detected at the remote end of the link. has been detected at the remote end of the link.
This value applies to 10BASE-FB, 100BASE-T4 Far This value applies to 10BASE-FB, 100BASE-T4 Far
End Fault Indication and non-specified remote End Fault Indication and non-specified remote
faults from a system running auto-negotiation. faults from a system running auto-negotiation.
The values remoteJabber(7), remoteLinkLoss(8), The values remoteJabber(7), remoteLinkLoss(8),
and remoteTest(9) SHOULD be used instead of and remoteTest(9) SHOULD be used instead of
remoteFault(5) where the reason for remote fault remoteFault(5) where the reason for remote fault
is identified in the remote signaling protocol. is identified in the remote signaling protocol.
The value invalidSignal(6) indicates that an The value invalidSignal(6) indicates that an
invalid signal has been received from the other invalid signal has been received from the other
end of the link. InvalidSignal(6) applies only end of the link. invalidSignal(6) applies only
to MAUs of type 10BASE-FB. to MAUs of type 10BASE-FB.
Where an IEEE Std 802.3u-1995 clause 22 MII Where an IEEE Std 802.3-2002 clause 22 MII
is present, a logic one in the remote fault bit is present, a logic one in the remote fault bit
(reference section 22.2.4.2.8 of that document) (reference section 22.2.4.2.8 of that document)
maps to the value remoteFault(5), and a logic maps to the value remoteFault(5), and a logic
zero in the link status bit (reference section zero in the link status bit (reference section
22.2.4.2.10 of that document) maps to the value 22.2.4.2.10 of that document) maps to the value
notAvailable(4). The value notAvailable(4) notAvailable(4). The value notAvailable(4)
takes precedence over the value remoteFault(5). takes precedence over the value remoteFault(5).
Any MAU that implements management of clause 37 Any MAU that implements management of clause 37
Auto-Negotiation will map the received Remote Auto-Negotiation will map the received Remote
skipping to change at page 25, line 6 skipping to change at page 24, line 48
about a single MAU." about a single MAU."
INDEX { ifMauIfIndex, INDEX { ifMauIfIndex,
ifMauIndex ifMauIndex
} }
::= { ifMauTable 1 } ::= { ifMauTable 1 }
IfMauEntry ::= IfMauEntry ::=
SEQUENCE { SEQUENCE {
ifMauIfIndex InterfaceIndex, ifMauIfIndex InterfaceIndex,
ifMauIndex Integer32, ifMauIndex Integer32,
ifMauType OBJECT IDENTIFIER, ifMauType AutonomousType,
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 AutonomousType,
ifMauAutoNegSupported TruthValue, ifMauAutoNegSupported TruthValue,
ifMauTypeListBits BITS, ifMauTypeListBits BITS,
ifMauHCFalseCarriers Counter64 ifMauHCFalseCarriers Counter64
} }
ifMauIfIndex OBJECT-TYPE ifMauIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
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 2863, 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 -- read-only since originally an
-- SMIv1 index
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."
::= { ifMauEntry 2 } ::= { ifMauEntry 2 }
ifMauType OBJECT-TYPE ifMauType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies the MAU type. An DESCRIPTION "This object identifies the MAU type. An
initial set of MAU types are defined above. The initial set of MAU types are defined above. The
assignment of OBJECT IDENTIFIERs to new types of assignment of OBJECT IDENTIFIERs to new types of
MAUs is managed by the IANA. If the MAU type is MAUs is managed by the IANA. If the MAU type is
unknown, the object identifier unknown, the object identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is a is returned. Note that unknownMauType is a
syntactically valid object identifier, and any syntactically valid object identifier, and any
conformant implementation of ASN.1 and the BER conformant implementation of ASN.1 and the BER
must be able to generate and recognize this must be able to generate and recognize this
value. value.
This object represents the operational type of This object represents the operational type of
the MAU, as determined by either (1) the result the MAU, as determined by either (1) the result
of the auto-negotiation function or (2) if of the auto-negotiation function or (2) if
auto-negotiation is not enabled or is not auto-negotiation is not enabled or is not
skipping to change at page 28, line 40 skipping to change at page 28, line 37
returns to IDL after a transmission and there returns to IDL after a transmission and there
has been no collision during the transmission has been no collision during the transmission
then loopback will be detected. The value of then loopback will be detected. The value of
this attribute will only change during this attribute will only change during
non-collided transmissions for AUI, coax, and non-collided transmissions for AUI, coax, and
10BASE-FP MAUs. 10BASE-FP MAUs.
For 100Mbps and 1000Mbps MAUs, the enumerations For 100Mbps and 1000Mbps MAUs, the enumerations
match the states within the respective link match the states within the respective link
integrity state diagrams, fig 32-16, 23-12 and integrity state diagrams, fig 32-16, 23-12 and
24-15 of sections 32, 23 and 24 of [16]. Any 24-15 of sections 32, 23 and 24 of [IEEE802.3].
MAU which implements management of Any MAU which implements management of
auto-negotiation will map remote fault auto-negotiation will map remote fault
indication to remote fault. indication to remote fault.
The value available(3) indicates that the link, The value available(3) indicates that the link,
light, or loopback is normal. The value light, or loopback is normal. The value
notAvailable(4) indicates link loss, low light, notAvailable(4) indicates link loss, low light,
or no loopback. or no loopback.
The value remoteFault(5) indicates that a fault The value remoteFault(5) indicates that a fault
has been detected at the remote end of the link. has been detected at the remote end of the link.
skipping to change at page 29, line 4 skipping to change at page 28, line 49
auto-negotiation will map remote fault auto-negotiation will map remote fault
indication to remote fault. indication to remote fault.
The value available(3) indicates that the link, The value available(3) indicates that the link,
light, or loopback is normal. The value light, or loopback is normal. The value
notAvailable(4) indicates link loss, low light, notAvailable(4) indicates link loss, low light,
or no loopback. or no loopback.
The value remoteFault(5) indicates that a fault The value remoteFault(5) indicates that a fault
has been detected at the remote end of the link. has been detected at the remote end of the link.
This value applies to 10BASE-FB, 100BASE-T4 Far This value applies to 10BASE-FB, 100BASE-T4 Far
End Fault Indication and non-specified remote End Fault Indication and non-specified remote
faults from a system running auto-negotiation. faults from a system running auto-negotiation.
The values remoteJabber(7), remoteLinkLoss(8), The values remoteJabber(7), remoteLinkLoss(8),
and remoteTest(9) SHOULD be used instead of and remoteTest(9) SHOULD be used instead of
remoteFault(5) where the reason for remote fault remoteFault(5) where the reason for remote fault
is identified in the remote signaling protocol. is identified in the remote signaling protocol.
The value invalidSignal(6) indicates that an The value invalidSignal(6) indicates that an
invalid signal has been received from the other invalid signal has been received from the other
end of the link. InvalidSignal(6) applies only end of the link. invalidSignal(6) applies only
to MAUs of type 10BASE-FB. to MAUs of type 10BASE-FB.
Where an IEEE Std 802.3u-1995 clause 22 MII Where an IEEE Std 802.3-2002 clause 22 MII
is present, a logic one in the remote fault bit is present, a logic one in the remote fault bit
(reference section 22.2.4.2.8 of that document) (reference section 22.2.4.2.8 of that document)
maps to the value remoteFault(5), and a logic maps to the value remoteFault(5), and a logic
zero in the link status bit (reference section zero in the link status bit (reference section
22.2.4.2.10 of that document) maps to the value 22.2.4.2.10 of that document) maps to the value
notAvailable(4). The value notAvailable(4) notAvailable(4). The value notAvailable(4)
takes precedence over the value remoteFault(5). takes precedence over the value remoteFault(5).
Any MAU that implements management of clause 37 Any MAU that implements management of clause 37
Auto-Negotiation will map the received RF1 and Auto-Negotiation will map the received RF1 and
skipping to change at page 32, line 15 skipping to change at page 32, line 12
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers.
RFC 2863, 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 **********
This object has been deprecated in favour of
ifMauTypeListBits.
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
this MAU, 2 raised to the power noted below is this MAU, 2 raised to the power noted below is
added to the sum. For example, a MAU which has added to the sum. For example, a MAU which has
the capability to be only 10BASE-T would have a the capability to be only 10BASE-T would have a
value of 512 (2**9). In contrast, a MAU which value of 512 (2**9). In contrast, a MAU which
supports both 10Base-T (full duplex) and supports both 10Base-T (full duplex) and
100BASE-TX (full duplex) would have a value of 100BASE-TX (full duplex) would have a value of
skipping to change at page 33, line 5 skipping to change at page 33, line 5
12 10BASE-FL half duplex mode 12 10BASE-FL half duplex mode
13 10BASE-FL full duplex mode 13 10BASE-FL full duplex mode
14 100BASE-T4 14 100BASE-T4
15 100BASE-TX half duplex mode 15 100BASE-TX half duplex mode
16 100BASE-TX full duplex mode 16 100BASE-TX full duplex mode
17 100BASE-FX half duplex mode 17 100BASE-FX half duplex mode
18 100BASE-FX full duplex mode 18 100BASE-FX full duplex mode
19 100BASE-T2 half duplex mode 19 100BASE-T2 half duplex mode
20 100BASE-T2 full duplex mode 20 100BASE-T2 full duplex mode
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."
This object has been deprecated in favour of
ifMauTypeListBits."
::= { ifMauEntry 10 } ::= { ifMauEntry 10 }
ifMauDefaultType OBJECT-TYPE ifMauDefaultType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX AutonomousType
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION "This object identifies the default DESCRIPTION "This object identifies the default
administrative baseband MAU type, to be used in administrative baseband MAU type, to be used in
conjunction with the operational MAU type conjunction with the operational MAU type
denoted by ifMauType. denoted by ifMauType.
The set of possible values for this object is The set of possible values for this object is
the same as the set defined for the ifMauType the same as the set defined for the ifMauType
object. object.
skipping to change at page 35, line 19 skipping to change at page 35, line 16
b10GbaseW(37), -- 10GBASE-W b10GbaseW(37), -- 10GBASE-W
b10GbaseEW(38), -- 10GBASE-EW b10GbaseEW(38), -- 10GBASE-EW
b10GbaseLW(39), -- 10GBASE-LW b10GbaseLW(39), -- 10GBASE-LW
b10GbaseSW(40) -- 10GBASE-SW b10GbaseSW(40) -- 10GBASE-SW
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A value that uniquely identifies the set of DESCRIPTION "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.
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 ifMauAutoNegCapabilityBits.
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 ifMauHCFalseCarriers OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
skipping to change at page 37, line 6 skipping to change at page 36, line 50
::= { ifJackEntry 1 } ::= { ifJackEntry 1 }
ifJackType OBJECT-TYPE ifJackType OBJECT-TYPE
SYNTAX JackType SYNTAX JackType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The jack connector type, as it appears on the DESCRIPTION "The jack connector type, as it appears on the
outside of the system." outside of the system."
::= { ifJackEntry 2 } ::= { ifJackEntry 2 }
-- The ifMauAutoNegTable applies to systems in which --
-- auto-negotiation is supported on one or more MAUs -- The MAU Auto-Negotiation Table
-- attached to interfaces. Note that if auto-negotiation --
-- is present and enabled, the ifMauType object reflects
-- the result of the auto-negotiation function.
ifMauAutoNegTable OBJECT-TYPE ifMauAutoNegTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfMauAutoNegEntry SYNTAX SEQUENCE OF IfMauAutoNegEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "Configuration and status objects for the DESCRIPTION "Configuration and status objects for the
auto-negotiation function of MAUs attached to auto-negotiation function of MAUs attached to
interfaces." interfaces.
The ifMauAutoNegTable applies to systems in
which auto-negotiation is supported on one or
more MAUs attached to interfaces. Note that if
auto-negotiation is present and enabled, the
ifMauType object reflects the result of the
auto-negotiation function."
::= { dot3IfMauAutoNegGroup 1 } ::= { dot3IfMauAutoNegGroup 1 }
ifMauAutoNegEntry OBJECT-TYPE ifMauAutoNegEntry OBJECT-TYPE
SYNTAX IfMauAutoNegEntry SYNTAX IfMauAutoNegEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An entry in the table, containing configuration DESCRIPTION "An entry in the table, containing configuration
and status information for the auto-negotiation and status information for the auto-negotiation
function of a particular MAU." function of a particular MAU."
INDEX { ifMauIfIndex, INDEX { ifMauIfIndex,
skipping to change at page 39, line 28 skipping to change at page 39, line 29
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4, REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4,
aAutoNegAutoConfig." aAutoNegAutoConfig."
::= { ifMauAutoNegEntry 4 } ::= { ifMauAutoNegEntry 4 }
ifMauAutoNegCapability OBJECT-TYPE ifMauAutoNegCapability 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 **********
This object has been deprecated in favour of
ifMauAutoNegCapabilityBits.
A value that uniquely identifies the set of A value that uniquely identifies the set of
capabilities of the local auto-negotiation capabilities of the local auto-negotiation
entity. The value is a sum which initially entity. The value is a sum which initially
takes the value zero. Then, for each capability takes the value zero. Then, for each capability
of this interface, 2 raised to the power noted of this interface, 2 raised to the power noted
below is added to the sum. For example, an below is added to the sum. For example, an
interface which has the capability to support interface which has the capability to support
only 100Base-TX half duplex would have a value only 100Base-TX half duplex would have a value
of 32768 (2**15). In contrast, an interface of 32768 (2**15). In contrast, an interface
which supports both 100Base-TX half duplex and which supports both 100Base-TX half duplex and
skipping to change at page 40, line 13 skipping to change at page 40, line 17
14 100BASE-T4 14 100BASE-T4
15 100BASE-TX half duplex mode 15 100BASE-TX half duplex mode
16 100BASE-TX full duplex mode 16 100BASE-TX full duplex mode
17 (reserved) 17 (reserved)
18 (reserved) 18 (reserved)
19 100BASE-T2 half duplex mode 19 100BASE-T2 half duplex mode
20 100BASE-T2 full duplex mode 20 100BASE-T2 full duplex mode
Note that interfaces that support this MIB may Note that interfaces that support this MIB may
have capabilities that extend beyond the scope have capabilities that extend beyond the scope
of this MIB. of this MIB."
This object has been deprecated in favour of
ifMauAutoNegCapabilityBits"
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility." aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 5 } ::= { ifMauAutoNegEntry 5 }
ifMauAutoNegCapAdvertised OBJECT-TYPE ifMauAutoNegCapAdvertised OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS deprecated STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
This object has been deprecated in favour of
ifMauAutoNegCapAdvertisedBits.
A value that uniquely identifies the set of A value that uniquely identifies the set of
capabilities advertised by the local capabilities advertised by the local
auto-negotiation entity. Refer to auto-negotiation entity. Refer to
ifMauAutoNegCapability for a description of the ifMauAutoNegCapability for a description of the
possible values of this object. possible values of this object.
Capabilities in this object that are not Capabilities in this object that are not
available in ifMauAutoNegCapability cannot be available in ifMauAutoNegCapability cannot be
enabled. enabled."
This object has been deprecated in favour of
ifMauAutoNegCapAdvertisedBits"
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility." aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 6 } ::= { ifMauAutoNegEntry 6 }
ifMauAutoNegCapReceived OBJECT-TYPE ifMauAutoNegCapReceived 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 **********
This object has been deprecated in favour of
ifMauAutoNegCapReceivedBits.
A value that uniquely identifies the set of A value that uniquely identifies the set of
capabilities received from the remote capabilities received from the remote
auto-negotiation entity. Refer to auto-negotiation entity. Refer to
ifMauAutoNegCapability for a description of the ifMauAutoNegCapability for a description of the
possible values of this object. possible values of this object.
Note that interfaces that support this MIB may Note that interfaces that support this MIB may
be attached to remote auto-negotiation entities be attached to remote auto-negotiation entities
which have capabilities beyond the scope of this which have capabilities beyond the scope of this
MIB. MIB."
This object has been deprecated in favour of
ifMauAutoNegCapReceivedBits"
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility." aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 7 } ::= { ifMauAutoNegEntry 7 }
ifMauAutoNegRestart OBJECT-TYPE ifMauAutoNegRestart OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
restart(1), restart(1),
norestart(2) norestart(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
skipping to change at page 45, line 14 skipping to change at page 45, line 14
-- --
-- The Basic Broadband MAU Table -- The Basic Broadband MAU Table
-- --
broadMauBasicTable OBJECT-TYPE broadMauBasicTable OBJECT-TYPE
SYNTAX SEQUENCE OF BroadMauBasicEntry SYNTAX SEQUENCE OF BroadMauBasicEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
This entire table has been deprecated. There
have been no reported implementations of this
table, and it is unlikely that there ever will
be. IEEE recommends that broadband MAU types
should not be used for new installations.
Table of descriptive and status information Table of descriptive and status information
about the broadband MAUs connected to about the broadband MAUs connected to
interfaces." interfaces."
::= { dot3BroadMauBasicGroup 1 } ::= { dot3BroadMauBasicGroup 1 }
broadMauBasicEntry OBJECT-TYPE broadMauBasicEntry OBJECT-TYPE
SYNTAX BroadMauBasicEntry SYNTAX BroadMauBasicEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS deprecated STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
skipping to change at page 45, line 43 skipping to change at page 45, line 49
SEQUENCE { SEQUENCE {
broadMauIfIndex InterfaceIndex, broadMauIfIndex InterfaceIndex,
broadMauIndex Integer32, broadMauIndex Integer32,
broadMauXmtRcvSplitType INTEGER, broadMauXmtRcvSplitType INTEGER,
broadMauXmtCarrierFreq Integer32, broadMauXmtCarrierFreq Integer32,
broadMauTranslationFreq Integer32 broadMauTranslationFreq Integer32
} }
broadMauIfIndex OBJECT-TYPE broadMauIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
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 2863, 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 -- read-only since originally an
-- SMIv1 index
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."
::= { broadMauBasicEntry 2 } ::= { broadMauBasicEntry 2 }
broadMauXmtRcvSplitType OBJECT-TYPE broadMauXmtRcvSplitType OBJECT-TYPE
skipping to change at page 53, line 19 skipping to change at page 53, line 27
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 deprecated STATUS deprecated
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
Compliance for MAUs attached to interfaces." Compliance for MAUs attached to interfaces.
This compliance is deprecated and replaced by
mauModIfCompl3."
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 54, line 9 skipping to change at page 54, line 20
for MAUs attached to interfaces." for MAUs attached to interfaces."
OBJECT ifMauStatus OBJECT ifMauStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
::= { mauModCompls 3 } ::= { mauModCompls 3 }
mauModRpCompl2 MODULE-COMPLIANCE mauModRpCompl2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "Compliance for MAUs attached to repeater DESCRIPTION "Compliance for MAUs attached to repeater
ports." ports.
Note that compliance with this compliance
statement requires compliance with the
snmpRptrModCompl MODULE-COMPLIANCE statement of
the SNMP-REPEATER-MIB [RFC2108]."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { mauRpGrpBasic } MANDATORY-GROUPS { mauRpGrpBasic }
GROUP mauRpGrp100Mbs GROUP mauRpGrp100Mbs
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have 100Mb/s or recommended for MAUs which have 100Mb/s or
greater capability." greater capability."
GROUP mauRpGrpJack GROUP mauRpGrpJack
skipping to change at page 54, line 35 skipping to change at page 54, line 51
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 mauModIfCompl3 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "Compliance for MAUs attached to interfaces." DESCRIPTION "Compliance for MAUs attached to interfaces.
Note that compliance with this compliance
statement requires compliance with the
ifCompliance3 MODULE-COMPLIANCE statement of the
IF-MIB [RFC2863] and the dot3Compliance2
MODULE-COMPLIANCE statement of the
EtherLike-MIB [ETHERIF]."
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 mauIfGrpHCStats GROUP mauIfGrpHCStats
skipping to change at page 56, line 29 skipping to change at page 56, line 51
Kerry McDonald Kerry McDonald
K.C. Norseth K.C. Norseth
Dave Perkins Dave Perkins
Dan Romascanu Dan Romascanu
Andrew Smith Andrew Smith
Kaj Tesink Kaj Tesink
Geoff Thompson Geoff Thompson
Maurice Turcotte Maurice Turcotte
Paul Woodruff Paul Woodruff
7. References This document is based on the Proposed Standard MAU MIB, RFC 2668
[RFC2668], edited by John Flick of Hewlett-Packard and Andrew Smith,
then of Extreme Networks, and produced by the Ethernet Interfaces and
Hub MIB Working Group. It extends that document by providing
suppport for 10 Gb/s MAUs as defined in [IEEE802.3ae].
Normative References RFC 2668, in turn, was based on the Proposed Standard MAU MIB, RFC
2239 [RFC2239], edited by Kathryn de Graaf, then of 3Com, and Dan
Romascanu, then of Madge Networks, and produced by the Ethernet
Interfaces and Hub MIB Working Group. It extended that document by
providing support for 1000 Mb/sec MAUs as defined in [IEEE802.3].
RFC 2239, in turn, was based on the Proposed Standard MAU MIB, RFC
1515 [RFC1515], edited by Donna McMaster, then of SynOptics
Communications, Keith McCloghrie, then of Hughes LAN Systems, and Sam
Roberts, then of Farallon Computing, and produced by the Hub MIB
Working Group. It extends that document by providing support for 100
Mb/sec MAUs, full duplex MAUs, and auto-negotiation, as defined in
[IEEE802.3].
7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Structure of Management J., Rose, M. and S. Waldbusser, "Structure of
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Management Information Version 2 (SMIv2)", STD 58, RFC
1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Textual Conventions for J., Rose, M. and S. Waldbusser, "Textual Conventions
SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Conformance Statements J., Rose, M. and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999. for SMIv2", STD 58, RFC 2580, April 1999.
[IEEE802.3] IEEE, IEEE Std 802.3, 2000 Edition: "Information [IEEE802.3] IEEE, IEEE Std 802.3, 2002 Edition: "Carrier Sense
technology - Telecommunications and information exchange Multiple Access with Collision Detection (CSMA/CD)
between systems - Local and metropolitan area networks - Access Method and Physical Layer Specifications",
Specific requirements - Part 3: Carrier sense multiple March 2002.
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.
[P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, [IEEE802.3ae] IEEE, IEEE Std 802.3ae-2002, "Amendment: Media
IEEE Draft P802.3ae/D4.3, April 2002, work in Access Control (MAC) Parameters, Physical Layers,
progress. and Management Parameters for 10 Gb/s Operation",
August, 2002.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
MIB using SMIv2", RFC 2863, June 2000. Group MIB using SMIv2", RFC 2863, June 2000.
[RFC2108] de Graaf, K., D. Romascanu, D. McMaster, and K. [RFC2108] de Graaf, K., D. Romascanu, D. McMaster, and K.
McCloghrie, "Definitions of Managed Objects for IEEE McCloghrie, "Definitions of Managed Objects for IEEE
802.3 Repeater Devices using SMIv2", RFC 2108, February 802.3 Repeater Devices using SMIv2", RFC 2108, February
1997. 1997.
[ETHERIF] Flick, J., "Definitions of Managed Objects for the [ETHERIF] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", work in progress, Ethernet-like Interface Types", work in progress,
draft-ietf-hubmib-etherif-mib-v3-02.txt, May, 2002. draft-ietf-hubmib-etherif-mib-v3-02.txt, March, 2003.
Non-Normative References
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 1999.
[RFC1155] Rose, M. and K. McCloghrie, "Structure and
Identification of Management Information for
TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991.
[RFC1215] Rose, M., "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2572] Case, J., Harrington, D., Presuhn R. and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, May 1999.
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, May 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3
Applications", RFC 2573, May 1999.
[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, 8. Informative References
"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 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
Requirements Levels", BCP 14, RFC 2119, March 1997. "Introduction and Applicability Statements for
Internet-Standard Network Management Framework",
RFC 3410, December 2002.
[RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [RFC3418] Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S.
"Management Information Base for Version 2 of the Waldbusser, "Management Information Base (MIB) for the
Simple Network Management Protocol (SNMPv2)", RFC 1907, Simple Network Management Protocol (SNMP)", RFC 3418,
January 1996. December 2002.
[RFC2668] Smith, A., Flick, J., deGraaf, K., Romascanu, D., [RFC2668] Smith, A., Flick, J., deGraaf, K., Romascanu, D.,
McMaster, D., McCloghrie, K. and S. Roberts, McMaster, D., McCloghrie, K. and S. Roberts,
"Definitions of Managed Objects for IEEE 802.3 Medium "Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs)", RFC 2668, August 1999. Attachment Units (MAUs)", RFC 2668, August 1999.
[RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie,
K. and S. Roberts, "Definitions of Managed Objects for K. and S. Roberts, "Definitions of Managed Objects for
IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2",
RFC 2239, November 1997. RFC 2239, November 1997.
skipping to change at page 59, line 5 skipping to change at page 58, line 49
[RFC1515] McMaster, D., McCloghrie, K. and S. Roberts, [RFC1515] McMaster, D., McCloghrie, K. and S. Roberts,
"Definitions of Managed Objects for IEEE 802.3 Medium "Definitions of Managed Objects for IEEE 802.3 Medium
Attachment Units (MAUs)", RFC 1515, September 1993. Attachment Units (MAUs)", RFC 1515, September 1993.
[ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald, [ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald,
K., Norseth, K. C., and K. Tesink, "Definitions of K., Norseth, K. C., and K. Tesink, "Definitions of
Managed Objects for the Ethernet WAN Interface Managed Objects for the Ethernet WAN Interface
Sublayer", work in progress, Sublayer", work in progress,
draft-ietf-hubmib-wis-mib-04.txt, May 2002. draft-ietf-hubmib-wis-mib-04.txt, May 2002.
8. Security Considerations 9. 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.
Such objects may be considered sensitive or vulnerable in some Such objects may be considered sensitive or vulnerable in some
network environments. The support for SET operations in a non-secure network environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. network operations.
SNMPv1 by itself is such an insecure environment. Even if the Some of the readable objects in this MIB module (i.e., objects with a
network itself is secure (for example by using IPSec), even then, MAX-ACCESS other than not-accessible) may be considered sensitive or
there is no control as to who on the secure network is allowed to vulnerable in some network environments. In some environments it may
access and GET/SET (read/change/create/delete) the objects in this be undesirable to allow unauthorized parties to access statistics or
MIB. status information about individual links in a network. It is thus
important to control even GET and/or NOTIFY access to these objects
and possibly to even encrypt the values of these objects when sending
them over the network via SNMP.
It is recommended that the implementers consider the security SNMP versions prior to SNMPv3 did not include adequate security.
features as provided by the SNMPv3 framework. Specifically, the use Even if the network itself is secure (for example by using IPSec),
of the User-based Security Model RFC 2574 [RFC2574] and the View- even then, there is no control as to who on the secure network is
based Access Control Model RFC 2575 [RFC2575] is recommended. allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is then a customer/user responsibility to ensure that the SNMP It is recommended that the implementors consider the security
entity giving access to an instance of this MIB, is properly features as provided by the SNMPv3 framework (see [RFC3410], section
configured to give access to those objects only to those principals 8), including full support for the SNMPv3 cryptographic mechanisms
(users) that have legitimate rights to access them. (for authentication and privacy).
9. Authors' Addresses Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
10. 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
E-mail: johnf@rose.hp.com E-mail: johnf@rose.hp.com
A. Change Log A. Change Log
 End of changes. 

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