draft-ietf-hubmib-rfc3636bis-05.txt   rfc4836.txt 
Network Working Group E. Beili Network Working Group E. Beili
Internet-Draft Actelis Networks Request for Comments: 4836 Actelis Networks
Obsoletes: 3636 (if approved) July 25, 2006
Expires: January 26, 2007
Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units
(MAUs)
draft-ietf-hubmib-rfc3636bis-05.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Category: Standards Track
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Definitions of Managed Objects for
http://www.ietf.org/ietf/1id-abstracts.txt. IEEE 802.3 Medium Attachment Units (MAUs)
The list of Internet-Draft Shadow Directories can be accessed at Status of This Memo
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 26, 2007. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This document defines a portion of the Management Information Base
for use with network management protocols in the Internet community. (MIB) for use with network management protocols in the Internet
In particular, it defines objects for managing IEEE 802.3 Medium community. In particular, it defines objects for managing IEEE 802.3
Attachment Units (MAUs). This memo obsoletes RFC 3636. It amends Medium Attachment Units (MAUs). This document obsoletes RFC 3636.
that specification by moving MAU type OBJECT-IDENTITY definitions and It amends that specification by moving MAU type OBJECT-IDENTITY
relevant textual conventions into a separate Internet Assigned Number definitions and relevant textual conventions into a separate Internet
Authority (IANA) maintained MIB module. In addition, management Assigned Number Authority (IANA) maintained MIB module. In addition,
information is added to enable support for Ethernet in the First Mile management information is added to enable support for Ethernet in the
(EFM) and 10GBASE-CX4 MAUs. First Mile (EFM) and 10GBASE-CX4 MAUs.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. Relationship to RFC 3636 . . . . . . . . . . . . . . . . . 4 3.1. Relationship to RFC 3636 . . . . . . . . . . . . . . . . . 4
3.2. Relationship to other MIBs . . . . . . . . . . . . . . . . 5 3.2. Relationship to Other MIBs . . . . . . . . . . . . . . . . 5
3.2.1. Relationship to the Interfaces MIB . . . . . . . . . . 5 3.2.1. Relationship to the Interfaces MIB . . . . . . . . . . 5
3.2.2. Relationship to the 802.3 Repeater MIB module . . . . 6 3.2.2. Relationship to the 802.3 Repeater MIB Module . . . . 6
3.3. Management of Internal MAUs . . . . . . . . . . . . . . . 6 3.3. Management of Internal MAUs . . . . . . . . . . . . . . . 6
3.4. Management of IEEE 802.3 Managed Objects . . . . . . . . . 7 3.4. Mapping of IEEE 802.3 Managed Objects . . . . . . . . . . 6
3.5. Addition of new MAU Types . . . . . . . . . . . . . . . . 8 3.5. Addition of New MAU Types . . . . . . . . . . . . . . . . 9
3.5.1. dot3MauType OBJECT-IDENTITIES . . . . . . . . . . . . 8 3.5.1. dot3MauType OBJECT-IDENTITIES . . . . . . . . . . . . 9
3.5.2. IANAifMauTypeListBits Textual Convention . . . . . . . 8 3.5.2. IANAifMauTypeListBits TEXTUAL-CONVENTION . . . . . . . 9
3.5.3. IANAifMauMediaAvailable Textual Convention . . . . . . 9 3.5.3. IANAifMauMediaAvailable TEXTUAL-CONVENTION . . . . . . 9
3.5.4. IANAifMauAutoNegCapBits Textual Convention . . . . . . 9 3.5.4. IANAifMauAutoNegCapBits TEXTUAL-CONVENTION . . . . . . 10
3.5.5. JackType Textual Convention . . . . . . . . . . . . . 9 3.5.5. JackType TEXTUAL-CONVENTION . . . . . . . . . . . . . 10
4. MAU MIB Definitions . . . . . . . . . . . . . . . . . . . . . 9 4. MAU MIB Definitions . . . . . . . . . . . . . . . . . . . . . 10
5. IANA-maintained MAU TC Definitions . . . . . . . . . . . . . . 46 5. IANA-Maintained MAU TC Definitions . . . . . . . . . . . . . . 46
6. Security Considerations . . . . . . . . . . . . . . . . . . . 62 6. Security Considerations . . . . . . . . . . . . . . . . . . . 62
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63
8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 63 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 63
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64
9.1. Normative References . . . . . . . . . . . . . . . . . . . 64 9.1. Normative References . . . . . . . . . . . . . . . . . . . 64
9.2. Informative References . . . . . . . . . . . . . . . . . . 65 9.2. Informative References . . . . . . . . . . . . . . . . . . 66
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 67
Intellectual Property and Copyright Statements . . . . . . . . . . 68
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This document defines a portion of the Management Information Base
for use with network management protocols in the Internet community. (MIB) for use with network management protocols in the Internet
In particular, it defines objects for managing IEEE 802.3 Medium community. In particular, it defines objects for managing IEEE 802.3
Attachment Units (MAUs). [IEEE802.3] Medium Attachment Units (MAUs).
The previous version of this memo, RFC 3636 [RFC3636], defined a The previous version of this document, RFC 3636 [RFC3636], defined a
single MIB module. This memo splits the original MIB module into single MIB module. This document splits the original MIB module into
two, putting frequently updated object identities and textual two, putting frequently updated object identities and textual
conventions into a separate, IANA-maintained MIB module, in order to conventions into a separate, IANA-maintained MIB module, in order to
decrease the need of updating the basic MAU MIB module. decrease the need of updating the basic MAU MIB module.
The first version of the IANA-maintained MIB module also extends the The first version of the IANA-maintained MIB module also extends the
list of managed objects to support Ethernet in the First Mile (EFM) list of managed objects to support Ethernet in the First Mile (EFM)
and 10GBASE-CX4 interfaces. and 10GBASE-CX4 interfaces.
Ethernet technology, as defined by the 802.3 Working Group of the Ethernet technology, as defined by the 802.3 Working Group of the
IEEE, continues to evolve, with scalable increases in speed, new IEEE, continues to evolve, with scalable increases in speed, new
skipping to change at page 4, line 10 skipping to change at page 4, line 10
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
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-2005 [IEEE802.3]. This object classes" of IEEE Std. 802.3-2005 [IEEE802.3]. This
specification is intended to provide for management of all types of specification is intended to provide for management of all types of
Ethernet/802.3 MAUs. Ethernet/802.3 MAUs.
3.1. Relationship to RFC 3636 3.1. Relationship to RFC 3636
The management definitions provided in this memo are intended to be a The management definitions provided in this document are intended to
superset of those defined by RFC 3636 [RFC3636]. be a superset of those defined by RFC 3636 [RFC3636].
In order to decrease the need of updating the basic MAU MIB module In order to decrease the need of updating the basic MAU MIB module
due to the new MAU type, Media Available state, Auto Negotiation due to the new MAU type, Media Available state, Auto Negotiation
capability and/or Jack type introduction, all relevant object capability and/or Jack type introduction, all relevant object
identities and textual conventions have been moved to a separate, identities and textual conventions have been moved to a separate,
IANA-maintained MIB module IANA-MAU-MIB, the first version of which IANA-maintained MIB module IANA-MAU-MIB, the first version of which
is defined in this memo. Thus when a new MAU type, Media Available is defined in this document. Thus when a new MAU type, Media
state, Auto Negotiation capability and/or Jack type is defined by the Available state, Auto Negotiation capability, and/or Jack type is
IEEE 802.3 working group, only the IANA-maintained module needs to be defined by the IEEE 802.3 working group, only the IANA-maintained
revised, leaving the basic MAU-MIB module defined in this memo module needs to be revised, leaving the basic MAU-MIB module defined
unchanged. in this document unchanged.
In addition, the new definitions are added to the IANA-maintained MIB In addition, the new definitions are added to the IANA-maintained MIB
module, to support Ethernet in the First Mile (EFM) and 10GBASE-CX4 module, to support Ethernet in the First Mile (EFM) and 10GBASE-CX4
interfaces, defined in IEEE Std 802.3ah-2004 [IEEE802.3ah] and IEEE interfaces, defined in IEEE Std 802.3ah-2004 [IEEE802.3ah] and IEEE
Std 802.3ak-2004 [IEEE802.3ak] respectively, now part of IEEE Std Std 802.3ak-2004 [IEEE802.3ak] respectively, now part of IEEE Std
802.3-2005 [IEEE802.3]. 802.3-2005 [IEEE802.3].
It should be noted that the changes made in this revision will not be It should be noted that the changes made in this revision will not be
entirely backward-compatible with MIB modules that currently import entirely backward-compatible with MIB modules that currently import
MAU type object identity descriptors from the MAU-MIB; such modules MAU type object identity descriptors from the MAU-MIB; such modules
will need to be revised to import those DESCRIPTORS from the IANA- will need to be revised to import those DESCRIPTORS from the IANA-
MAU-MIB. Similarly, any management applications that process the MAU-MIB. Similarly, any management applications that process the
object identity definitions (e.g., to present the DESCRIPTION text to object identity definitions (e.g., to present the DESCRIPTION text to
a user) will need to be get those definitions from the IANA-MAU-MIB a user) will need to get those definitions from the IANA-MAU-MIB
instead of the MAU-MIB. While it is true that changes that require instead of the MAU-MIB. While it is true that changes that require
such adjustments are not strictly compliant with the SMIv2 rules such adjustments are not strictly compliant with the SMIv2 rules
governing MIB module revisions (see [RFC2578] Section 10), in this governing MIB module revisions (see [RFC2578] Section 10), in this
case continued high maintenance costs that would result from not case continued high maintenance costs that would result from not
making these changes make the deviation from the rules justified. It making these changes make the deviation from the rules justified. It
should be noted that the working group was not able to find any should be noted that the working group was not able to find any
examples of MIB modules or management applications that would examples of MIB modules or management applications that would
actually be negatively affected by the changes. actually be negatively affected by the changes.
3.2. Relationship to other MIBs 3.2. Relationship to Other MIBs
It is assumed that an agent implementing MAU-MIB will also implement It is assumed that an agent implementing MAU-MIB will also implement
(at least) the 'system' group defined in the SNMPv2 MIB [RFC3418]. (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.2.1. Relationship to the Interfaces MIB 3.2.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
skipping to change at page 5, line 50 skipping to change at page 5, line 50
objects are used to manage a PHY that allows the MAU type to be objects are used to manage a PHY that allows the MAU type to be
changed dynamically, then the agent SHALL create ifTable, changed dynamically, then the agent SHALL create ifTable,
ifStackTable, and ifInvStackTable entries that pertain to the WIS ifStackTable, and ifInvStackTable entries that pertain to the WIS
when ifMauDefaultType is changed to a 10GBASEW variant (i.e., one of when ifMauDefaultType is changed to a 10GBASEW variant (i.e., one of
dot3MauType10GigBaseW, dot3MauType10GigBaseEW, dot3MauType10GigBaseW, dot3MauType10GigBaseEW,
dot3MauType10GigBaseLW, or dot3MauType10GigBaseSW) from any other dot3MauType10GigBaseLW, or dot3MauType10GigBaseSW) from any other
type, and shall destroy the WIS-related entries when ifMauDefaultType type, and shall destroy the WIS-related entries when ifMauDefaultType
is changed to a non- 10GBASE-W type. The agent SHALL also change the is changed to a non- 10GBASE-W type. The agent SHALL also change the
values of 'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry values of 'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry
indexed by ifMauIfIndex as specified in [RFC3635] and [RFC3637] when indexed by ifMauIfIndex as specified in [RFC3635] and [RFC3637] 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.2.2. Relationship to the 802.3 Repeater MIB module 3.2.2. Relationship to the 802.3 Repeater MIB Module
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 comply with the snmpRptrModCompl compliance statement of MUST also comply with the snmpRptrModCompl compliance statement of
the 802.3 Repeater MIB module. the 802.3 Repeater MIB module.
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 that the given MAU is connected to.
3.3. Management of Internal MAUs 3.3. 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.4. Management of IEEE 802.3 Managed Objects 3.4. Mapping of IEEE 802.3 Managed Objects
This section contains the mapping between relevant managed objects
(attributes) defined in [IEEE802.3] Clause 30, and managed objects
defined in this document.
+----------------------------------+--------------------------------+ +----------------------------------+--------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Corresponding SNMP Object |
+----------------------------------+--------------------------------+ +----------------------------------+--------------------------------+
| oMAU | | | oMAU | |
+----------------------------------+--------------------------------+
| .aMAUID | rpMauIndex or ifMauIndex or | | .aMAUID | rpMauIndex or ifMauIndex or |
| | broadMauIndex | | | broadMauIndex |
+----------------------------------+--------------------------------+
| .aMAUType | rpMauType or ifMauType | | .aMAUType | rpMauType or ifMauType |
+----------------------------------+--------------------------------+
| .aMAUTypeList | ifMauTypeListBits | | .aMAUTypeList | ifMauTypeListBits |
+----------------------------------+--------------------------------+
| .aMediaAvailable | rpMauMediaAvailable or | | .aMediaAvailable | rpMauMediaAvailable or |
| | ifMauMediaAvailable | | | ifMauMediaAvailable |
+----------------------------------+--------------------------------+
| .aLoseMediaCounter | rpMauMediaAvailableStateExits | | .aLoseMediaCounter | rpMauMediaAvailableStateExits |
| | or | | | or |
| | ifMauMediaAvailableStateExits | | | ifMauMediaAvailableStateExits |
+----------------------------------+--------------------------------+
| .aJabber | rpMauJabberState and | | .aJabber | rpMauJabberState and |
| | rpMauJabberingStateEnters or | | | rpMauJabberingStateEnters or |
| | ifMauJabberState and | | | ifMauJabberState and |
| | ifMauJabberingStateEnters | | | ifMauJabberingStateEnters |
+----------------------------------+--------------------------------+
| .aMAUAdminState | rpMauStatus or ifMauStatus | | .aMAUAdminState | rpMauStatus or ifMauStatus |
+----------------------------------+--------------------------------+
| .aBbMAUXmitRcvSplitType | broadMauXmtRcvSplitType | | .aBbMAUXmitRcvSplitType | broadMauXmtRcvSplitType |
+----------------------------------+--------------------------------+
| .aBroadbandFrequencies | broadMauXmtCarrierFreq and | | .aBroadbandFrequencies | broadMauXmtCarrierFreq and |
| | broadMauTranslationFreq | | | broadMauTranslationFreq |
+----------------------------------+--------------------------------+
| .aFalseCarriers | rpMauFalseCarriers or | | .aFalseCarriers | rpMauFalseCarriers or |
| | ifMauFalseCarriers | | | ifMauFalseCarriers |
+----------------------------------+--------------------------------+
| .acResetMAU | rpMauStatus or ifMauStatus | | .acResetMAU | rpMauStatus or ifMauStatus |
+----------------------------------+--------------------------------+
| .acMAUAdminControl | rpMauStatus or ifMauStatus | | .acMAUAdminControl | rpMauStatus or ifMauStatus |
+----------------------------------+--------------------------------+
| .nJabber | rpMauJabberTrap or | | .nJabber | rpMauJabberTrap or |
| | ifMauJabberTrap | | | ifMauJabberTrap |
+----------------------------------+--------------------------------+
| oAutoNegotiation | | | oAutoNegotiation | |
+----------------------------------+--------------------------------+
| .aAutoNegID | ifMauIndex | | .aAutoNegID | ifMauIndex |
+----------------------------------+--------------------------------+
| .aAutoNegAdminState | ifMauAutoNegAdminStatus | | .aAutoNegAdminState | ifMauAutoNegAdminStatus |
+----------------------------------+--------------------------------+
| .aAutoNegRemoteSignalling | ifMauAutoNegRemoteSignalling | | .aAutoNegRemoteSignalling | ifMauAutoNegRemoteSignalling |
| .aAutoNegAutoConfig | ifMauAutoNegConfig | | .aAutoNegAutoConfig | ifMauAutoNegConfig |
+----------------------------------+--------------------------------+
| .aAutoNegLocalTechnologyAbility | ifMauAutoNegCapabilityBits | | .aAutoNegLocalTechnologyAbility | ifMauAutoNegCapabilityBits |
+----------------------------------+--------------------------------+
| .aAutoNegAdvertisedTechnologyAbi | ifMauAutoNegAdvertisedBits and | | .aAutoNegAdvertisedTechnologyAbi | ifMauAutoNegAdvertisedBits and |
| lity | ifMauAutoNegRemoteFaultAdverti | | lity | ifMauAutoNegRemoteFaultAdverti |
| | sed | | | sed |
+----------------------------------+--------------------------------+
| .aAutoNegReceivedTechnologyAbili | ifMauAutoNegReceivedBits and | | .aAutoNegReceivedTechnologyAbili | ifMauAutoNegReceivedBits and |
| ty | ifMauAutoNegRemoteFaultReceive | | ty | ifMauAutoNegRemoteFaultReceive |
| | d | | | d |
+----------------------------------+--------------------------------+
| .acAutoNegRestartAutoConfig | ifMauAutoNegRestart | | .acAutoNegRestartAutoConfig | ifMauAutoNegRestart |
+----------------------------------+--------------------------------+
| .acAutoNegAdminControl | ifMauAutoNegAdminStatus | | .acAutoNegAdminControl | ifMauAutoNegAdminStatus |
+----------------------------------+--------------------------------+ +----------------------------------+--------------------------------+
Table 1 Table 1: Mapping of IEEE 802.3 Managed Objects
The following IEEE 802.3 managed objects have not been included in The following IEEE 802.3 managed objects have not been included in
the MAU-MIB for the following reasons. the MAU-MIB for the following reasons.
+------------------------------------+------------------------------+ +------------------------------------+------------------------------+
| IEEE 802.3 Managed Object | Corresponding SNMP Object | | IEEE 802.3 Managed Object | Reason for exclusion |
+------------------------------------+------------------------------+ +------------------------------------+------------------------------+
| oMAU | | | oMAU | |
+------------------------------------+------------------------------+
| .aIdleErrorCount | Only useful for 100BaseT2, | | .aIdleErrorCount | Only useful for 100BaseT2, |
| | which is not widely | | | which is not widely |
| | implemented. | | | implemented. |
+------------------------------------+------------------------------+
| oAutoNegotiation | | | oAutoNegotiation | |
+------------------------------------+------------------------------+
| .aAutoNegLocalSelectorAbility | Only needed for support of | | .aAutoNegLocalSelectorAbility | Only needed for support of |
| | isoethernet (802.9a), which | | | isoethernet (802.9a), which |
| | is not supported by MAU-MIB. | | | is not supported by MAU-MIB. |
+------------------------------------+------------------------------+
| .aAutoNegAdvertisedSelectorAbility | | | .aAutoNegAdvertisedSelectorAbility | |
+------------------------------------+------------------------------+
| .aAutoNegReceivedSelectorAbility | | | .aAutoNegReceivedSelectorAbility | |
+------------------------------------+------------------------------+ +------------------------------------+------------------------------+
Table 2 Table 2: Unmapped IEEE 802.3 Managed Objects
3.5. Addition of new MAU Types 3.5. Addition of New MAU Types
3.5.1. dot3MauType OBJECT-IDENTITIES 3.5.1. dot3MauType OBJECT-IDENTITIES
The dot3MauType OBJECT IDENTIFIER and its OBJECT-IDENTITY definitions The dot3MauType OBJECT IDENTIFIER and its OBJECT-IDENTITY definitions
has been moved from the MAU-MIB into the IANA-maintained IANA-MAU- has been moved from the MAU-MIB into the IANA-maintained IANA-MAU-
MIB, first version of which is defined in this memo. MIB, the first version of which is defined in this document.
When a new IEEE 802.3 MAU is defined, IANA can re-issue a version of When a new IEEE 802.3 MAU is defined, IANA can re-issue a version of
IANA-MAU-MIB with the new dot3MauType OBJECT-IDENTITY and its IANA-MAU-MIB with the new dot3MauType OBJECT-IDENTITY and its
matching IANAifMauTypeListBits textual convention value and, matching IANAifMauTypeListBits textual convention value and,
possibly, with new IANAifMauMediaAvailable, IANAifMauAutoNegCapBits possibly, with new IANAifMauMediaAvailable, IANAifMauAutoNegCapBits,
and/or IANAifJackType values. and/or IANAifJackType values.
An Expert Review, as defined in RFC 2434 [RFC2434], is REQUIRED for An Expert Review, as defined in RFC 2434 [RFC2434], is REQUIRED for
the addition of the new MAU, Media Available states, Auto Negotiation the addition of the new MAU, Media Available states, Auto Negotiation
capabilities and/or Jack types. capabilities, and/or Jack types.
In some cases new MAU types may require additional managed objects or In some cases, new MAU types may require additional managed objects
may have side effects on the behavior of existing managed objects. or may have side effects on the behavior of existing managed objects.
In such cases a standards-track specification (which may be a new In such cases a standards-track specification (which may be a new
document or a revision of this document) is also REQUIRED. Any such document or a revision of this document) is also REQUIRED. Any such
document is REQUIRED to note any special properties of the MAU types document is REQUIRED to note any special properties of the MAU types
that it defines - for example, side effects on the ifStackTable as that it defines - for example, side effects on the ifStackTable as
noted in this document for 10GBASE-W MAUs. noted in this document for 10GBASE-W MAUs.
3.5.2. IANAifMauTypeListBits Textual Convention 3.5.2. IANAifMauTypeListBits TEXTUAL-CONVENTION
The syntax of ifMauTypeListBits is changed to be a textual The syntax of ifMauTypeListBits is changed to be a textual
convention, such that the enumerated integer values are now defined convention, such that the enumerated integer values are now defined
in the textual convention, IANAifMauTypeListBits, which can be re- in the textual convention IANAifMauTypeListBits, which can be re-
specified (with additional values, when defined by IEEE 802.3) in the specified (with additional values, when defined by IEEE 802.3) in the
IANA-maintained MIB module, without issuing a new version of this IANA-maintained MIB module without issuing a new version of this
document. document.
3.5.3. IANAifMauMediaAvailable Textual Convention 3.5.3. IANAifMauMediaAvailable TEXTUAL-CONVENTION
The syntax of ifMauMediaAvailable and rpMauMediaAvailable is changed The syntax of ifMauMediaAvailable and rpMauMediaAvailable is changed
a textual convention, such that the enumerated integer values are now to be a textual convention, such that the enumerated integer values
defined in the textual convention, IANAifMauMediaAvailable, which can are now defined in the textual convention IANAifMauMediaAvailable,
be re-specified (with additional values, when defined by IEEE 802.3) which can be re-specified (with additional values, when defined by
in the IANA-maintained MIB module, without issuing a new version of IEEE 802.3) in the IANA-maintained MIB module without issuing a new
this document. version of this document.
3.5.4. IANAifMauAutoNegCapBits Textual Convention 3.5.4. IANAifMauAutoNegCapBits TEXTUAL-CONVENTION
The syntax of ifMauAutoNegCapabilityBits, The syntax of ifMauAutoNegCapabilityBits,
ifMauAutoNegCapAdvertisedBits and ifMauAutoNegCapReceivedBits objects ifMauAutoNegCapAdvertisedBits, and ifMauAutoNegCapReceivedBits
is changed to be a textual convention, such that the enumerated objects is changed to be a textual convention, such that the
integer values are now defined in the textual convention, enumerated integer values are now defined in the textual convention
IANAifMauAutoNegCapBits, which can be re-specified (with additional IANAifMauAutoNegCapBits, which can be re-specified (with additional
values, when defined by IEEE 802.3) in the IANA-maintained MIB values, when defined by IEEE 802.3) in the IANA-maintained MIB module
module, without issuing a new version of this document. without issuing a new version of this document.
3.5.5. JackType Textual Convention 3.5.5. JackType TEXTUAL-CONVENTION
The JackType Textual Convention has been deprecated in favor of The JackType Textual Convention has been deprecated in favor of the
IANAifJackType defined in the IANA-maintained MIB module, so the new IANAifJackType defined in the IANA-maintained MIB module, so the new
Jack types can be added (when defined by IEEE 802.3) without issuing Jack types can be added (when defined by IEEE 802.3) without issuing
a new version of this document. a new version of this document.
4. MAU MIB Definitions 4. MAU MIB Definitions
MAU-MIB DEFINITIONS ::= BEGIN MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
Counter32, Integer32, Counter64, Counter32, Integer32, Counter64,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2
FROM SNMPv2-SMI -- RFC 2578 FROM SNMPv2-SMI -- RFC 2578
TruthValue, AutonomousType, TEXTUAL-CONVENTION TruthValue, AutonomousType, TEXTUAL-CONVENTION
FROM SNMPv2-TC -- RFC 2579 FROM SNMPv2-TC -- RFC 2579
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
InterfaceIndex InterfaceIndex
FROM IF-MIB -- RFC 2863 FROM IF-MIB -- RFC 2863
IANAifMauTypeListBits, IANAifMauMediaAvailable, IANAifMauTypeListBits, IANAifMauMediaAvailable,
IANAifMauAutoNegCapBits, IANAifJackType IANAifMauAutoNegCapBits, IANAifJackType
FROM IANA-MAU-MIB -- RFC 3636bis FROM IANA-MAU-MIB
-- EdNote: Replace RFC 3636bis above with the URL of the -- http://www.iana.org/assignments/ianamau-mib
-- actual IANA-maintained module & remove this note.
; ;
mauMod MODULE-IDENTITY mauMod MODULE-IDENTITY
LAST-UPDATED "200607250000Z" -- July 25, 2006 LAST-UPDATED "200704210000Z" -- April 21, 2007
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
Chair: Bert Wijnen
Chair: Dan Romascanu Postal: Alcatel-Lucent
Postal: Avaya Schagen 33
Atidim Technology Park, Bldg. 3 3461 GL Linschoten
Tel Aviv 61131 Netherlands
Israel Phone: +31-348-407-775
Tel: +972 3 645 8414 EMail: bwijnen@alcatel-lucent.com
E-mail: dromasca@avaya.com
Editor: Edward Beili Editor: Edward Beili
Postal: Actelis Networks Inc. Postal: Actelis Networks Inc.
25 Bazel St., P.O.B. 10173 25 Bazel St., P.O.B. 10173
Petach-Tikva 10173 Petach-Tikva 10173
Israel Israel
Tel: +972-3-924-3491 Tel: +972-3-924-3491
E-mail: edward.beili@actelis.com" EMail: edward.beili@actelis.com"
DESCRIPTION DESCRIPTION
"Management information for 802.3 MAUs. "Management information for 802.3 MAUs.
The following reference is used throughout this MIB module: The following reference is used throughout this MIB module:
[IEEE 802.3 Std] refers to: [IEEE802.3] refers to:
IEEE Std 802.3, 2005 Edition: 'IEEE Standard for Information IEEE Std 802.3, 2005 Edition: 'IEEE Standard for Information
technology - Telecommunications and information exchange technology - Telecommunications and information exchange
between systems - Local and metropolitan area networks - between systems - Local and metropolitan area networks -
Specific requirements - Part 3: Carrier sense multiple Specific requirements - Part 3: Carrier sense multiple
access with collision detection (CSMA/CD) access method and access with collision detection (CSMA/CD) access method and
physical layer specifications'. physical layer specifications'.
Of particular interest is Clause 30, 'Management'. Of particular interest is Clause 30, 'Management'.
Copyright (C) The Internet Society (2006). This Copyright (C) The IETF Trust (2007).
version of this MIB module is part of RFC XXXX; This version of this MIB module is part of RFC 4836;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
REVISION "200607250000Z" -- July 25, 2006 REVISION "200704210000Z" -- April 21, 2007
DESCRIPTION "Updated to reference IANA maintaned textual DESCRIPTION "Updated to reference IANA maintaned textual
conventions for MAU types, Media Availability state, conventions for MAU types, Media Availability state,
Auto Negotiation capabilities and jack types, Auto Negotiation capabilities, and jack types,
instead of using internally defined values. instead of using internally defined values.
This version is published as RFC XXXX." This version is published as RFC 4836."
-- EdNote: Replace XXXX with the actual RFC number
-- & remove this note.
REVISION "200309190000Z" -- September 19, 2003 REVISION "200309190000Z" -- September 19, 2003
DESCRIPTION "Updated to include support for 10 Gb/s MAUs. DESCRIPTION "Updated to include support for 10 Gb/s MAUs.
This resulted in the following revisions: This resulted in the following revisions:
- Added OBJECT-IDENTITY definitions for - Added OBJECT-IDENTITY definitions for
10 gigabit MAU types 10 gigabit MAU types
- Added fiberLC jack type to JackType TC - Added fiberLC jack type to JackType TC
- Extended ifMauTypeListBits with bits for - Extended ifMauTypeListBits with bits for
the 10 gigabit MAU types the 10 gigabit MAU types
- Added enumerations to ifMauMediaAvailable, - Added enumerations to ifMauMediaAvailable,
skipping to change at page 12, line 51 skipping to change at page 13, line 31
-- OIDs under the following branch are reserved for -- OIDs under the following branch are reserved for
-- the IANA-MAU-MIB to assign as MAU type values: -- the IANA-MAU-MIB to assign as MAU type values:
-- { snmpDot3MauMgt 4 } -- { snmpDot3MauMgt 4 }
dot3IfMauAutoNegGroup dot3IfMauAutoNegGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
-- the following OID is the MODULE-IDENTITY value -- the following OID is the MODULE-IDENTITY value
-- for this MIB module: { snmpDot3MauMgt 6 } -- for this MIB module: { snmpDot3MauMgt 6 }
-- the following OID is the MODULE-IDENTITY value
-- for the IANA-MAU-MIB: { snmpDot3MauMgt 7 }
-- --
-- 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
DESCRIPTION "Table of descriptive and status information DESCRIPTION "Table of descriptive and status information
about the MAU(s) attached to the ports of a about the MAU(s) attached to the ports of a
skipping to change at page 14, line 38 skipping to change at page 15, line 15
rpMauIndex OBJECT-TYPE rpMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only -- read-only since originally an MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index -- 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 "[IEEE802.3], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 } ::= { rpMauEntry 3 }
rpMauType OBJECT-TYPE rpMauType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies the MAU type. Values for DESCRIPTION "This object identifies the MAU type. Values for
standard IEEE 802.3 MAU types are defined in the standard IEEE 802.3 MAU types are defined in the
IANA maintained IANA-MAU-MIB module, as IANA maintained IANA-MAU-MIB module, as
OBJECT-IDENTITIES of dot3MauType. OBJECT-IDENTITIES of dot3MauType.
If the MAU type is unknown, the object identifier If the MAU type is unknown, the object identifier
zeroDotZero is returned." zeroDotZero is returned."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." REFERENCE "[IEEE802.3], 30.5.1.1.2, aMAUType."
::= { rpMauEntry 4 } ::= { rpMauEntry 4 }
rpMauStatus OBJECT-TYPE rpMauStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
operational(3), operational(3),
standby(4), standby(4),
shutdown(5), shutdown(5),
reset(6) reset(6)
skipping to change at page 15, line 33 skipping to change at page 16, line 10
The value other(1) is returned if the MAU is in The value other(1) is returned if the MAU is in
a state other than one of the states 2 through a state other than one of the states 2 through
6. 6.
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. being initialized.
A MAU in the operational(3) state is fully A MAU in the operational(3) state is fully
functional, operates, and passes signals to its functional; it operates, and passes signals to its
attached DTE or repeater port in accordance to attached DTE or repeater port in accordance to
its specification. its specification.
A MAU in standby(4) state forces DI and CI to A MAU in standby(4) state forces DI and CI to
idle and the media transmitter to idle or fault, idle, and the media transmitter to idle or fault,
if supported. Standby(4) mode only applies to if supported. Standby(4) mode only applies to
link type MAUs. The state of link type MAUs. The state of
rpMauMediaAvailable is unaffected. rpMauMediaAvailable is unaffected.
A MAU in shutdown(5) state assumes the same A MAU in shutdown(5) state assumes the same
condition on DI, CI, and the media transmitter condition on DI, CI, and the media transmitter,
as though it were powered down or not connected. as though it were powered down or not connected.
The MAU MAY return other(1) value for the The MAU MAY return other(1) value for the
rpMauJabberState and rpMauMediaAvailable objects rpMauJabberState and rpMauMediaAvailable objects
when it is in this state. For an AUI, this when it is in this state. For an AUI, this
state will remove power from the AUI. state will remove power from the AUI.
Setting this variable to the value reset(6) Setting this variable to the value reset(6)
resets the MAU in the same manner as a resets the MAU in the same manner as a
power-off, power-on cycle of at least one-half power-off, power-on cycle of at least one-half
second would. The agent is not required to second would. The agent is not required to
return the value reset (6). return the value reset (6).
Setting this variable to the value Setting this variable to the value
operational(3), standby(4), or shutdown(5) operational(3), standby(4), or shutdown(5)
causes the MAU to assume the respective state causes the MAU to assume the respective state,
except that setting a mixing-type MAU or an AUI except that setting a mixing-type MAU or an AUI
to standby(4) will cause the MAU to enter the to standby(4) will cause the MAU to enter the
shutdown state." shutdown state."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, REFERENCE "[IEEE802.3], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acResetMAU." acResetMAU."
::= { rpMauEntry 5 } ::= { rpMauEntry 5 }
rpMauMediaAvailable OBJECT-TYPE rpMauMediaAvailable OBJECT-TYPE
SYNTAX IANAifMauMediaAvailable SYNTAX IANAifMauMediaAvailable
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies Media Available state of DESCRIPTION "This object identifies Media Available state of
the MAU, complementary to the rpMauStatus. Values the MAU, complementary to the rpMauStatus. Values
for the standard IEEE 802.3 Media Available states for the standard IEEE 802.3 Media Available states
are defined in the IANA maintained IANA-MAU-MIB are defined in the IANA maintained IANA-MAU-MIB
module, as IANAifMauMediaAvailable TC." module, as IANAifMauMediaAvailable TC."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." REFERENCE "[IEEE802.3], 30.5.1.1.4, aMediaAvailable."
::= { rpMauEntry 6 } ::= { rpMauEntry 6 }
rpMauMediaAvailableStateExits OBJECT-TYPE rpMauMediaAvailableStateExits 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 times that DESCRIPTION "A count of the number of times that
rpMauMediaAvailable for this MAU instance leaves rpMauMediaAvailable 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 rptrMonitorPortLastChange." value of rptrMonitorPortLastChange."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, REFERENCE "[IEEE802.3], 30.5.1.1.5, aLoseMediaCounter.
aLoseMediaCounter.
RFC 2108, rptrMonitorPortLastChange" RFC 2108, rptrMonitorPortLastChange"
::= { rpMauEntry 7 } ::= { rpMauEntry 7 }
rpMauJabberState OBJECT-TYPE rpMauJabberState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
noJabber(3), noJabber(3),
jabbering(4) jabbering(4)
} }
skipping to change at page 17, line 23 skipping to change at page 17, line 46
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. being initialized.
If the MAU is not jabbering the agent returns If the MAU is not jabbering the agent returns
noJabber(3). This is the 'normal' state. noJabber(3). This is the 'normal' state.
If the MAU is in jabber state the agent returns If the MAU is in jabber state the agent returns
the jabbering(4) value." the jabbering(4) value."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, REFERENCE "[IEEE802.3], 30.5.1.1.6, aJabber.jabberFlag."
aJabber.jabberFlag."
::= { rpMauEntry 8 } ::= { rpMauEntry 8 }
rpMauJabberingStateEnters OBJECT-TYPE rpMauJabberingStateEnters 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 times that DESCRIPTION "A count of the number of times that
mauJabberState for this MAU instance enters the mauJabberState for this MAU instance enters the
state jabbering(4). For MAUs of type state jabbering(4). For MAUs of type
dot3MauTypeAUI, dot3MauType100BaseT4, dot3MauTypeAUI, dot3MauType100BaseT4,
dot3MauType100BaseTX, dot3MauType100BaseFX and dot3MauType100BaseTX, dot3MauType100BaseFX, and
all 1000Mbps types, this counter will always all 1000Mbps types, this counter will always
indicate zero. indicate zero.
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 rptrMonitorPortLastChange." value of rptrMonitorPortLastChange."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, REFERENCE "[IEEE802.3], 30.5.1.1.6, aJabber.jabberCounter.
aJabber.jabberCounter.
RFC 2108, rptrMonitorPortLastChange" RFC 2108, rptrMonitorPortLastChange"
::= { rpMauEntry 9 } ::= { rpMauEntry 9 }
rpMauFalseCarriers OBJECT-TYPE rpMauFalseCarriers 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 links. This counter during IDLE in 100BASE-X links. This counter
does not increment at the symbol rate. It can does not increment at the symbol rate. It can
increment after a valid carrier completion at a increment after a valid carrier completion at a
maximum rate of once per 100 ms until the next maximum rate of once per 100 ms until the next
carrier event. carrier event.
This counter increments only for MAUs of type This counter increments only for MAUs of type
dot3MauType100BaseT4, dot3MauType100BaseTX, and dot3MauType100BaseT4, dot3MauType100BaseTX,
dot3MauType100BaseFX and all 1000Mbps types. dot3MauType100BaseFX, and all 1000Mbps types.
For all other MAU types, this counter will For all other MAU types, this counter will
always indicate zero. always indicate zero.
The approximate minimum time for rollover of The approximate minimum time for rollover of
this counter is 7.4 hours. this counter is 7.4 hours.
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 rptrMonitorPortLastChange." value of rptrMonitorPortLastChange."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. REFERENCE "[IEEE802.3], 30.5.1.1.10, aFalseCarriers.
RFC 2108, rptrMonitorPortLastChange" RFC 2108, rptrMonitorPortLastChange"
::= { rpMauEntry 10 } ::= { rpMauEntry 10 }
-- The rpJackTable applies to MAUs attached to repeaters -- The rpJackTable applies to MAUs attached to repeaters
-- which have one or more external jacks (connectors). -- which have one or more external jacks (connectors).
rpJackTable OBJECT-TYPE rpJackTable OBJECT-TYPE
SYNTAX SEQUENCE OF RpJackEntry SYNTAX SEQUENCE OF RpJackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 20, line 30 skipping to change at page 21, line 4
ifMauIfIndex OBJECT-TYPE ifMauIfIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only -- read-only since originally an MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index -- 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 -- read-only since originally an MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index -- 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 "[IEEE802.3], 30.5.1.1.1, aMAUID."
::= { ifMauEntry 2 } ::= { ifMauEntry 2 }
ifMauType OBJECT-TYPE ifMauType OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies the MAU type. Values for DESCRIPTION "This object identifies the MAU type. Values for
standard IEEE 802.3 MAU types are defined in the standard IEEE 802.3 MAU types are defined in the
IANA maintained IANA-MAU-MIB module, as IANA maintained IANA-MAU-MIB module, as
OBJECT-IDENTITIES of dot3MauType. OBJECT-IDENTITIES of dot3MauType.
If the MAU type is unknown, the object identifier If the MAU type is unknown, the object identifier
zeroDotZero is returned. zeroDotZero is returned.
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
implemented for this MAU, by the value of the implemented for this MAU, by the value of the
object ifMauDefaultType. In case (2), a set to object ifMauDefaultType. In case 2), a set to
the object ifMauDefaultType will force the MAU the object ifMauDefaultType will force the MAU
into the new operating mode." into the new operating mode."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." REFERENCE "[IEEE802.3], 30.5.1.1.2, aMAUType."
::= { ifMauEntry 3 } ::= { ifMauEntry 3 }
ifMauStatus OBJECT-TYPE ifMauStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
operational(3), operational(3),
standby(4), standby(4),
shutdown(5), shutdown(5),
reset(6) reset(6)
skipping to change at page 21, line 43 skipping to change at page 22, line 16
The value other(1) is returned if the MAU is in The value other(1) is returned if the MAU is in
a state other than one of the states 2 through a state other than one of the states 2 through
6. 6.
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. being initialized.
A MAU in the operational(3) state is fully A MAU in the operational(3) state is fully
functional, operates, and passes signals to its functional; it operates, and passes signals to its
attached DTE or repeater port in accordance to attached DTE or repeater port in accordance to
its specification. its specification.
A MAU in standby(4) state forces DI and CI to A MAU in standby(4) state forces DI and CI to
idle and the media transmitter to idle or fault, idle and the media transmitter to idle or fault,
if supported. Standby(4) mode only applies to if supported. Standby(4) mode only applies to
link type MAUs. The state of link type MAUs. The state of
ifMauMediaAvailable is unaffected. ifMauMediaAvailable is unaffected.
A MAU in shutdown(5) state assumes the same A MAU in shutdown(5) state assumes the same
condition on DI, CI, and the media transmitter condition on DI, CI, and the media transmitter,
as though it were powered down or not connected. as though it were powered down or not connected.
The MAU MAY return other(1) value for the The MAU MAY return other(1) value for the
ifMauJabberState and ifMauMediaAvailable objects ifMauJabberState and ifMauMediaAvailable objects
when it is in this state. For an AUI, this when it is in this state. For an AUI, this
state will remove power from the AUI. state will remove power from the AUI.
Setting this variable to the value reset(6) Setting this variable to the value reset(6)
resets the MAU in the same manner as a resets the MAU in the same manner as a
power-off, power-on cycle of at least one-half power-off, power-on cycle of at least one-half
second would. The agent is not required to second would. The agent is not required to
return the value reset (6). return the value reset (6).
Setting this variable to the value Setting this variable to the value
operational(3), standby(4), or shutdown(5) operational(3), standby(4), or shutdown(5)
causes the MAU to assume the respective state causes the MAU to assume the respective state,
except that setting a mixing-type MAU or an AUI except that setting a mixing-type MAU or an AUI
to standby(4) will cause the MAU to enter the to standby(4) will cause the MAU to enter the
shutdown state." shutdown state."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, REFERENCE "[IEEE802.3], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acResetMAU." acResetMAU."
::= { ifMauEntry 4 } ::= { ifMauEntry 4 }
ifMauMediaAvailable OBJECT-TYPE ifMauMediaAvailable OBJECT-TYPE
SYNTAX IANAifMauMediaAvailable SYNTAX IANAifMauMediaAvailable
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies Media Available state of DESCRIPTION "This object identifies Media Available state of
the MAU, complementary to the ifMauStatus. Values the MAU, complementary to the ifMauStatus. Values
for the standard IEEE 802.3 Media Available states for the standard IEEE 802.3 Media Available states
are defined in the IANA maintained IANA-MAU-MIB are defined in the IANA maintained IANA-MAU-MIB
module, as IANAifMauMediaAvailable TC." module, as IANAifMauMediaAvailable TC."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." REFERENCE "[IEEE802.3], 30.5.1.1.4, aMediaAvailable."
::= { ifMauEntry 5 } ::= { ifMauEntry 5 }
ifMauMediaAvailableStateExits OBJECT-TYPE ifMauMediaAvailableStateExits 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 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 "[IEEE802.3], 30.5.1.1.5, aLoseMediaCounter.
aLoseMediaCounter.
RFC 2863, 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)
} }
skipping to change at page 23, line 32 skipping to change at page 24, line 5
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. being initialized.
If the MAU is not jabbering the agent returns If the MAU is not jabbering the agent returns
noJabber(3). This is the 'normal' state. noJabber(3). This is the 'normal' state.
If the MAU is in jabber state the agent returns If the MAU is in jabber state the agent returns
the jabbering(4) value." the jabbering(4) value."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, REFERENCE "[IEEE802.3], 30.5.1.1.6, aJabber.jabberFlag."
aJabber.jabberFlag."
::= { ifMauEntry 7 } ::= { ifMauEntry 7 }
ifMauJabberingStateEnters OBJECT-TYPE ifMauJabberingStateEnters 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 times that DESCRIPTION "A count of the number of times that
mauJabberState for this MAU instance enters the mauJabberState for this MAU instance enters the
state jabbering(4). This counter will always state jabbering(4). This counter will always
indicate zero for MAUs of type dot3MauTypeAUI indicate zero for MAUs of type dot3MauTypeAUI
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 "[IEEE802.3], 30.5.1.1.6, aJabber.jabberCounter.
aJabber.jabberCounter.
RFC 2863, 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.
skipping to change at page 24, line 31 skipping to change at page 24, line 49
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 This counter can roll over very quickly. A
management station is advised to poll the management station is advised to poll the
ifMauHCFalseCarriers instead of this counter in ifMauHCFalseCarriers instead of this counter in
order to avoid loss of information. 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 "[IEEE802.3], 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 This object has been deprecated in favour of
ifMauTypeListBits. 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 that 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 that 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 that
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
((2**11) + (2**16)) or 67584. ((2**11) + (2**16)), or 67584.
The powers of 2 assigned to the capabilities are The powers of 2 assigned to the capabilities are
these: these:
Power Capability Power Capability
0 other or unknown 0 other or unknown
1 AUI 1 AUI
2 10BASE-5 2 10BASE-5
3 FOIRL 3 FOIRL
4 10BASE-2 4 10BASE-2
skipping to change at page 25, line 44 skipping to change at page 26, line 15
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."
::= { ifMauEntry 10 } ::= { ifMauEntry 10 }
ifMauDefaultType OBJECT-TYPE ifMauDefaultType OBJECT-TYPE
SYNTAX AutonomousType 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.
This object represents the This object represents the
administratively-configured type of the MAU. If administratively-configured type of the MAU. If
auto-negotiation is not enabled or is not auto-negotiation is not enabled or is not
skipping to change at page 26, line 31 skipping to change at page 26, line 49
provide for underlying hardware implementations provide for underlying hardware implementations
which do not follow the exact behavior specified which do not follow the exact behavior specified
above. In particular, when above. In particular, when
ifMauAutoNegAdminStatus transitions from enabled ifMauAutoNegAdminStatus transitions from enabled
to disabled, the agent implementation MUST to disabled, the agent implementation MUST
ensure that the operational type of the MAU (as ensure that the operational type of the MAU (as
reported by ifMauType) correctly transitions to reported by ifMauType) correctly transitions to
the value specified by this object, rather than the value specified by this object, rather than
continuing to operate at the value earlier continuing to operate at the value earlier
determined by the auto-negotiation function." determined by the auto-negotiation function."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID, and REFERENCE "[IEEE802.3], 30.5.1.1.1, aMAUID, and 22.2.4.1.4."
22.2.4.1.4."
::= { ifMauEntry 11 } ::= { ifMauEntry 11 }
ifMauAutoNegSupported OBJECT-TYPE ifMauAutoNegSupported OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object indicates whether or not DESCRIPTION "This object indicates whether or not
auto-negotiation is supported on this MAU." auto-negotiation is supported on this MAU."
::= { ifMauEntry 12 } ::= { ifMauEntry 12 }
ifMauTypeListBits OBJECT-TYPE ifMauTypeListBits OBJECT-TYPE
SYNTAX IANAifMauTypeListBits SYNTAX IANAifMauTypeListBits
skipping to change at page 27, line 22 skipping to change at page 27, line 40
SYNTAX Counter64 SYNTAX Counter64
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.
This counter is a 64 bit version of This counter is a 64-bit version of
ifMauFalseCarriers. Since the 32 bit version of ifMauFalseCarriers. Since the 32-bit version of
this counter can roll over very quickly, this counter can roll over very quickly,
management stations are advised to poll the management stations are advised to poll the
64 bit version instead in order to avoid loss 64-bit version instead, in order to avoid loss
of information. 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 "[IEEE802.3], 30.5.1.1.10, aFalseCarriers.
RFC 2863, ifCounterDiscontinuityTime." RFC 2863, ifCounterDiscontinuityTime."
::= { ifMauEntry 14 } ::= { 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
skipping to change at page 29, line 34 skipping to change at page 30, line 4
ifMauAutoNegCapability Integer32, ifMauAutoNegCapability Integer32,
ifMauAutoNegCapAdvertised Integer32, ifMauAutoNegCapAdvertised Integer32,
ifMauAutoNegCapReceived Integer32, ifMauAutoNegCapReceived Integer32,
ifMauAutoNegRestart INTEGER, ifMauAutoNegRestart INTEGER,
ifMauAutoNegCapabilityBits IANAifMauAutoNegCapBits, ifMauAutoNegCapabilityBits IANAifMauAutoNegCapBits,
ifMauAutoNegCapAdvertisedBits IANAifMauAutoNegCapBits, ifMauAutoNegCapAdvertisedBits IANAifMauAutoNegCapBits,
ifMauAutoNegCapReceivedBits IANAifMauAutoNegCapBits, ifMauAutoNegCapReceivedBits IANAifMauAutoNegCapBits,
ifMauAutoNegRemoteFaultAdvertised INTEGER, ifMauAutoNegRemoteFaultAdvertised INTEGER,
ifMauAutoNegRemoteFaultReceived INTEGER ifMauAutoNegRemoteFaultReceived INTEGER
} }
ifMauAutoNegAdminStatus OBJECT-TYPE ifMauAutoNegAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enabled(1), enabled(1),
disabled(2) disabled(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION "Setting this object to enabled(1) will cause DESCRIPTION "Setting this object to enabled(1) will cause
the interface which has the auto-negotiation the interface that has the auto-negotiation
signaling ability to be enabled. signaling ability to be enabled.
If the value of this object is disabled(2) then If the value of this object is disabled(2) then
the interface will act as it would if it had no the interface will act as it would if it had no
auto-negotiation signaling. Under these auto-negotiation signaling. Under these
conditions, an IEEE 802.3 MAU will immediately conditions, an IEEE 802.3 MAU will immediately
be forced to the state indicated by the value of be forced to the state indicated by the value of
the object ifMauDefaultType. the object ifMauDefaultType.
NOTE TO IMPLEMENTORS: When NOTE TO IMPLEMENTORS: When
ifMauAutoNegAdminStatus transitions from enabled ifMauAutoNegAdminStatus transitions from enabled
to disabled, the agent implementation MUST to disabled, the agent implementation MUST
ensure that the operational type of the MAU (as ensure that the operational type of the MAU (as
reported by ifMauType) correctly transitions to reported by ifMauType) correctly transitions to
the value specified by the ifMauDefaultType the value specified by the ifMauDefaultType
object, rather than continuing to operate at the object, rather than continuing to operate at the
value earlier determined by the auto-negotiation value earlier determined by the auto-negotiation
function." function."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.2, REFERENCE "[IEEE802.3], 30.6.1.1.2, aAutoNegAdminState,
aAutoNegAdminState and 30.6.1.2.2, and 30.6.1.2.2, acAutoNegAdminControl."
acAutoNegAdminControl."
::= { ifMauAutoNegEntry 1 } ::= { ifMauAutoNegEntry 1 }
ifMauAutoNegRemoteSignaling OBJECT-TYPE ifMauAutoNegRemoteSignaling OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
detected(1), detected(1),
notdetected(2) notdetected(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A value indicating whether the remote end of DESCRIPTION "A value indicating whether the remote end of
the link is using auto-negotiation signaling. It the link is using auto-negotiation signaling. It
takes the value detected(1) if and only if, takes the value detected(1) if and only if,
during the previous link negotiation, FLP Bursts during the previous link negotiation, FLP Bursts
were received." were received."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.3, REFERENCE "[IEEE802.3], 30.6.1.1.3,
aAutoNegRemoteSignaling." aAutoNegRemoteSignaling."
::= { ifMauAutoNegEntry 2 } ::= { ifMauAutoNegEntry 2 }
ifMauAutoNegConfig OBJECT-TYPE ifMauAutoNegConfig OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
configuring(2), configuring(2),
complete(3), complete(3),
disabled(4), disabled(4),
parallelDetectFail(5) parallelDetectFail(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A value indicating the current status of the DESCRIPTION "A value indicating the current status of the
auto-negotiation process. The enumeration auto-negotiation process. The enumeration
parallelDetectFail(5) maps to a failure in parallelDetectFail(5) maps to a failure in
parallel detection as defined in 28.2.3.1 of parallel detection as defined in 28.2.3.1 of
[IEEE 802.3 Std]." [IEEE802.3]."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4, REFERENCE "[IEEE802.3], 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 This object has been deprecated in favour of
ifMauAutoNegCapabilityBits. ifMauAutoNegCapabilityBits.
A value that uniquely identifies the set of A value that uniquely identifies the set of
skipping to change at page 31, line 15 skipping to change at page 31, line 32
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 This object has been deprecated in favour of
ifMauAutoNegCapabilityBits. 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 that 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 that 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 that supports both 100Base-TX half duplex and
and 100Base-TX full duplex would have a value of 100Base-TX full duplex would have a value of
98304 ((2**15) + (2**16)). 98304 ((2**15) + (2**16)).
The powers of 2 assigned to the capabilities are The powers of 2 assigned to the capabilities are
these: these:
Power Capability Power Capability
0 other or unknown 0 other or unknown
(1-9) (reserved) (1-9) (reserved)
10 10BASE-T half duplex mode 10 10BASE-T half duplex mode
11 10BASE-T full duplex mode 11 10BASE-T full duplex mode
skipping to change at page 31, line 47 skipping to change at page 32, line 16
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."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, REFERENCE "[IEEE802.3], 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 This object has been deprecated in favour of
skipping to change at page 32, line 21 skipping to change at page 32, line 38
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."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, REFERENCE "[IEEE802.3], 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 This object has been deprecated in favour of
ifMauAutoNegCapReceivedBits. 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 that have capabilities beyond the scope of this
MIB." MIB."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, REFERENCE "[IEEE802.3], 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
STATUS current STATUS current
DESCRIPTION "If the value of this object is set to DESCRIPTION "If the value of this object is set to
restart(1) then this will force auto-negotiation restart(1) then this will force auto-negotiation
to begin link renegotiation. If auto-negotiation to begin link renegotiation. If auto-negotiation
signaling is disabled, a write to this object signaling is disabled, a write to this object
has no effect. has no effect.
Setting the value of this object to norestart(2) Setting the value of this object to norestart(2)
has no effect." has no effect."
REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1, REFERENCE "[IEEE802.3], 30.6.1.2.1,
acAutoNegRestartAutoConfig." acAutoNegRestartAutoConfig."
::= { ifMauAutoNegEntry 8 } ::= { ifMauAutoNegEntry 8 }
ifMauAutoNegCapabilityBits OBJECT-TYPE ifMauAutoNegCapabilityBits OBJECT-TYPE
SYNTAX IANAifMauAutoNegCapBits SYNTAX IANAifMauAutoNegCapBits
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
capabilities of the local auto-negotiation capabilities of the local auto-negotiation
entity. Note that interfaces that support this entity. Note that interfaces that support this
MIB may have capabilities that extend beyond the MIB may have capabilities that extend beyond the
scope of this MIB. scope of this MIB.
Note that the local auto-negotiation entity may Note that the local auto-negotiation entity may
support some capabilities beyond the scope of support some capabilities beyond the scope of
this MIB. This is indicated by returning the this 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 standard capabilities that are listed in the for standard capabilities that are listed in the
IANAifMauAutoNegCapBits TC." IANAifMauAutoNegCapBits TC."
REFERENCE "[IEEE802.3], 30.6.1.1.5,
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility." aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 9 } ::= { ifMauAutoNegEntry 9 }
ifMauAutoNegCapAdvertisedBits OBJECT-TYPE ifMauAutoNegCapAdvertisedBits OBJECT-TYPE
SYNTAX IANAifMauAutoNegCapBits SYNTAX IANAifMauAutoNegCapBits
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION "A value that uniquely identifies the set of DESCRIPTION "A value that uniquely identifies the set of
capabilities advertised by the local capabilities advertised by the local
auto-negotiation entity. auto-negotiation entity.
skipping to change at page 34, line 9 skipping to change at page 34, line 26
Capabilities in this object that are not Capabilities in this object that are not
available in ifMauAutoNegCapabilityBits cannot available in ifMauAutoNegCapabilityBits cannot
be enabled. be enabled.
Note that the local auto-negotiation entity may Note that the local auto-negotiation entity may
advertise some capabilities beyond the scope of advertise some capabilities beyond the scope of
this MIB. This is indicated by returning the this 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 standard capabilities that are listed in the for standard capabilities that are listed in the
IANAifMauAutoNegCapBits TC." IANAifMauAutoNegCapBits TC."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, REFERENCE "[IEEE802.3], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility." aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 10 } ::= { ifMauAutoNegEntry 10 }
ifMauAutoNegCapReceivedBits OBJECT-TYPE ifMauAutoNegCapReceivedBits OBJECT-TYPE
SYNTAX IANAifMauAutoNegCapBits SYNTAX IANAifMauAutoNegCapBits
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
capabilities received from the remote capabilities received from the remote
auto-negotiation entity. auto-negotiation entity.
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 that have capabilities beyond the scope of this
MIB. This is indicated by returning the bit MIB. This is indicated by returning the bit
value bOther in addition to any bit values for value bOther in addition to any bit values for
for standard capabilities that are listed in the standard capabilities that are listed in the
IANAifMauAutoNegCapBits TC." IANAifMauAutoNegCapBits TC."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, REFERENCE "[IEEE802.3], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility." aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 11 } ::= { ifMauAutoNegEntry 11 }
ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noError(1), noError(1),
offline(2), offline(2),
linkFailure(3), linkFailure(3),
autoNegError(4) autoNegError(4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION "A value that identifies any local fault DESCRIPTION "A value that identifies any local fault
indications that this MAU has detected and will indications that this MAU has detected and will
advertise at the next auto-negotiation advertise at the next auto-negotiation
interaction for 1000Mbps MAUs." interaction for 1000Mbps MAUs."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, REFERENCE "[IEEE802.3], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility." aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 12 } ::= { ifMauAutoNegEntry 12 }
ifMauAutoNegRemoteFaultReceived OBJECT-TYPE ifMauAutoNegRemoteFaultReceived OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noError(1), noError(1),
offline(2), offline(2),
linkFailure(3), linkFailure(3),
autoNegError(4) autoNegError(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A value that identifies any fault indications DESCRIPTION "A value that identifies any fault indications
received from the far end of a link by the received from the far end of a link by the
local auto-negotiation entity for 1000Mbps local auto-negotiation entity for 1000Mbps
MAUs." MAUs."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, REFERENCE "[IEEE802.3], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility." aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 13 } ::= { ifMauAutoNegEntry 13 }
-- --
-- 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
skipping to change at page 36, line 36 skipping to change at page 37, line 5
broadMauIndex OBJECT-TYPE broadMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only -- read-only since originally an MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index -- 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 "[IEEE802.3], 30.5.1.1.1, aMAUID."
::= { broadMauBasicEntry 2 } ::= { broadMauBasicEntry 2 }
broadMauXmtRcvSplitType OBJECT-TYPE broadMauXmtRcvSplitType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
single(2), single(2),
dual(3) dual(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS deprecated STATUS deprecated
skipping to change at page 37, line 12 skipping to change at page 37, line 29
multiplexing/cabling system used to separate the multiplexing/cabling system used to separate the
transmit and receive paths for the 10BROAD36 transmit and receive paths for the 10BROAD36
MAU. MAU.
The value other(1) is returned if the split type The value other(1) is returned if the split type
is not either single or dual. is not either single or dual.
The value single(2) indicates a single cable The value single(2) indicates a single cable
system. The value dual(3) indicates a dual system. The value dual(3) indicates a dual
cable system, offset normally zero." cable system, offset normally zero."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.8, REFERENCE "[IEEE802.3], 30.5.1.1.8, aBbMAUXmitRcvSplitType."
aBbMAUXmitRcvSplitType."
::= { broadMauBasicEntry 3 } ::= { broadMauBasicEntry 3 }
broadMauXmtCarrierFreq OBJECT-TYPE broadMauXmtCarrierFreq 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 variable indicates the transmit carrier This variable indicates the transmit carrier
frequency of the 10BROAD36 MAU in MHz/4; that frequency of the 10BROAD36 MAU in MHz/4; that
is, in units of 250 kHz." is, in units of 250 kHz."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, REFERENCE "[IEEE802.3], 30.5.1.1.9,
aBroadbandFrequencies.xmitCarrierFrequency." aBroadbandFrequencies.xmitCarrierFrequency."
::= { broadMauBasicEntry 4 } ::= { broadMauBasicEntry 4 }
broadMauTranslationFreq OBJECT-TYPE broadMauTranslationFreq 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 variable indicates the translation offset This variable indicates the translation offset
frequency of the 10BROAD36 MAU in MHz/4; that frequency of the 10BROAD36 MAU in MHz/4; that
is, in units of 250 kHz." is, in units of 250 kHz."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, REFERENCE "[IEEE802.3], 30.5.1.1.9,
aBroadbandFrequencies.translationFrequency." aBroadbandFrequencies.translationFrequency."
::= { broadMauBasicEntry 5 } ::= { broadMauBasicEntry 5 }
-- Notifications for use by 802.3 MAUs -- Notifications for use by 802.3 MAUs
snmpDot3MauTraps OBJECT IDENTIFIER ::= { snmpDot3MauMgt 0 } snmpDot3MauTraps OBJECT IDENTIFIER ::= { snmpDot3MauMgt 0 }
rpMauJabberTrap NOTIFICATION-TYPE rpMauJabberTrap NOTIFICATION-TYPE
OBJECTS { rpMauJabberState } OBJECTS { rpMauJabberState }
STATUS current STATUS current
DESCRIPTION "This trap is sent whenever a managed repeater DESCRIPTION "This trap is sent whenever a managed repeater
MAU enters the jabber state. MAU enters the jabber state.
The agent MUST throttle the generation of The agent MUST throttle the generation of
consecutive rpMauJabberTraps so that there is at consecutive rpMauJabberTraps so that there is at
least a five-second gap between them." least a five-second gap between them."
REFERENCE "[IEEE 802.3 Std], 30.5.1.3.1, nJabber REFERENCE "[IEEE802.3], 30.5.1.3.1, nJabber notification."
notification."
::= { snmpDot3MauTraps 1 } ::= { snmpDot3MauTraps 1 }
ifMauJabberTrap NOTIFICATION-TYPE ifMauJabberTrap NOTIFICATION-TYPE
OBJECTS { ifMauJabberState } OBJECTS { ifMauJabberState }
STATUS current STATUS current
DESCRIPTION "This trap is sent whenever a managed interface DESCRIPTION "This trap is sent whenever a managed interface
MAU enters the jabber state. MAU enters the jabber state.
The agent MUST throttle the generation of The agent MUST throttle the generation of
consecutive ifMauJabberTraps so that there is at consecutive ifMauJabberTraps so that there is at
least a five-second gap between them." least a five-second gap between them."
REFERENCE "[IEEE 802.3 Std], 30.5.1.3.1, nJabber REFERENCE "[IEEE802.3], 30.5.1.3.1, nJabber notification."
notification."
::= { snmpDot3MauTraps 2 } ::= { snmpDot3MauTraps 2 }
-- Conformance information -- Conformance information
mauModConf mauModConf
OBJECT IDENTIFIER ::= { mauMod 1 } OBJECT IDENTIFIER ::= { mauMod 1 }
mauModCompls mauModCompls
OBJECT IDENTIFIER ::= { mauModConf 1 } OBJECT IDENTIFIER ::= { mauModConf 1 }
mauModObjGrps mauModObjGrps
OBJECT IDENTIFIER ::= { mauModConf 2 } OBJECT IDENTIFIER ::= { mauModConf 2 }
skipping to change at page 41, line 37 skipping to change at page 42, line 4
::= { mauModObjGrps 10 } ::= { mauModObjGrps 10 }
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 mauIfGrpHCStats OBJECT-GROUP
OBJECTS { ifMauHCFalseCarriers } OBJECTS { ifMauHCFalseCarriers }
STATUS current STATUS current
DESCRIPTION "Conformance for high capacity statistics for DESCRIPTION "Conformance for high capacity statistics for
MAUs attached to interfaces" MAUs attached to interfaces."
::= { mauModObjGrps 12 } ::= { 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 }
STATUS current STATUS current
DESCRIPTION "Notifications for interface MAUs." DESCRIPTION "Notifications for interface MAUs."
::= { mauModNotGrps 2 } ::= { mauModNotGrps 2 }
-- Compliances -- Compliances
mauModRpCompl MODULE-COMPLIANCE mauModRpCompl MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
skipping to change at page 42, line 28 skipping to change at page 42, line 43
This compliance is deprecated and replaced by This compliance is deprecated and replaced by
mauModRpCompl2, which corrects an oversight by mauModRpCompl2, which corrects an oversight by
allowing rpMauStatus to be implemented allowing rpMauStatus to be implemented
read-only." read-only."
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 that have 100Mb/s or
greater capability." greater capability."
GROUP mauRpGrpJack GROUP mauRpGrpJack
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have one or more recommended for MAUs that have one or more
external jacks." external jacks."
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."
::= { mauModCompls 1 } ::= { mauModCompls 1 }
mauModIfCompl MODULE-COMPLIANCE mauModIfCompl MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
skipping to change at page 43, line 4 skipping to change at page 43, line 18
mauModIfCompl MODULE-COMPLIANCE mauModIfCompl 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 This compliance is deprecated and replaced by
mauModIfCompl2." mauModIfCompl2."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { mauIfGrpBasic } MANDATORY-GROUPS { mauIfGrpBasic }
GROUP mauIfGrp100Mbs GROUP mauIfGrp100Mbs
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have 100Mb/s recommended for MAUs that have 100Mb/s
capability." capability."
GROUP mauIfGrpJack GROUP mauIfGrpJack
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have one or more recommended for MAUs that have one or more
external jacks." external jacks."
GROUP mauIfGrpAutoNeg GROUP mauIfGrpAutoNeg
DESCRIPTION "Implementation of this group is mandatory DESCRIPTION "Implementation of this group is mandatory
for MAUs which support managed for MAUs that support managed
auto-negotiation." auto-negotiation."
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 }
skipping to change at page 43, line 36 skipping to change at page 44, line 4
::= { 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 This compliance is deprecated and replaced by
mauModIfCompl3." 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 that have 100Mb/s
or greater capability." or greater capability."
GROUP mauIfGrpJack GROUP mauIfGrpJack
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have one or more recommended for MAUs that have one or more
external jacks." external jacks."
GROUP mauIfGrpAutoNeg2 GROUP mauIfGrpAutoNeg2
DESCRIPTION "Implementation of this group is mandatory DESCRIPTION "Implementation of this group is mandatory
for MAUs which support managed for MAUs that support managed
auto-negotiation." auto-negotiation."
GROUP mauIfGrpAutoNeg1000Mbps GROUP mauIfGrpAutoNeg1000Mbps
DESCRIPTION "Implementation of this group is mandatory DESCRIPTION "Implementation of this group is mandatory
for MAUs which have 1000Mb/s or greater for MAUs that have 1000Mb/s or greater
capability and support managed capability and support managed
auto-negotiation." auto-negotiation."
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."
OBJECT ifMauStatus OBJECT ifMauStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
skipping to change at page 44, line 38 skipping to change at page 45, line 5
Note that compliance with this compliance Note that compliance with this compliance
statement requires compliance with the statement requires compliance with the
snmpRptrModCompl MODULE-COMPLIANCE statement of snmpRptrModCompl MODULE-COMPLIANCE statement of
the SNMP-REPEATER-MIB (RFC 2108)." the SNMP-REPEATER-MIB (RFC 2108)."
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 that have 100Mb/s or
greater capability." greater capability."
GROUP mauRpGrpJack GROUP mauRpGrpJack
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have one or more recommended for MAUs that have one or more
external jacks." external jacks."
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."
skipping to change at page 45, line 24 skipping to change at page 45, line 39
ifCompliance3 MODULE-COMPLIANCE statement of the ifCompliance3 MODULE-COMPLIANCE statement of the
IF-MIB (RFC 2863) and the dot3Compliance2 IF-MIB (RFC 2863) and the dot3Compliance2
MODULE-COMPLIANCE statement of the MODULE-COMPLIANCE statement of the
EtherLike-MIB (RFC3635)." EtherLike-MIB (RFC3635)."
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 that have 100Mb/s
or greater capability." or greater capability."
GROUP mauIfGrpHCStats GROUP mauIfGrpHCStats
DESCRIPTION "Implementation of this group is mandatory DESCRIPTION "Implementation of this group is mandatory
for MAUs which have 1000Mb/s capacity, and for MAUs that have 1000Mb/s capacity, and
is recommended for MAUs which have 100Mb/s is recommended for MAUs that have 100Mb/s
capacity." capacity."
GROUP mauIfGrpJack GROUP mauIfGrpJack
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have one or more recommended for MAUs that have one or more
external jacks." external jacks."
GROUP mauIfGrpAutoNeg2 GROUP mauIfGrpAutoNeg2
DESCRIPTION "Implementation of this group is mandatory DESCRIPTION "Implementation of this group is mandatory
for MAUs which support managed for MAUs that support managed
auto-negotiation." auto-negotiation."
GROUP mauIfGrpAutoNeg1000Mbps GROUP mauIfGrpAutoNeg1000Mbps
DESCRIPTION "Implementation of this group is mandatory DESCRIPTION "Implementation of this group is mandatory
for MAUs which have 1000Mb/s or greater for MAUs that have 1000Mb/s or greater
capability and support managed capability and support managed
auto-negotiation." auto-negotiation."
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."
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 5 } ::= { mauModCompls 5 }
END END
5. IANA-maintained MAU TC Definitions 5. IANA-Maintained MAU TC Definitions
IANA-MAU-MIB DEFINITIONS ::= BEGIN IANA-MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 MODULE-IDENTITY, OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
; ;
ianaMauMIB MODULE-IDENTITY ianaMauMIB MODULE-IDENTITY
LAST-UPDATED "200607250000Z" -- July 25, 2006 LAST-UPDATED "200704210000Z" -- April 21, 2007
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO " Internet Assigned Numbers Authority CONTACT-INFO " Internet Assigned Numbers Authority
Postal: ICANN Postal: ICANN
4676 Admiralty Way, Suite 330 4676 Admiralty Way, Suite 330
Marina del Rey, CA 90292 Marina del Rey, CA 90292
Tel: +1 310 823 9358 Tel: +1-310-823-9358
E-Mail: iana@iana.org" EMail: iana@iana.org"
DESCRIPTION DESCRIPTION
"This MIB module defines dot3MauType OBJECT-IDENTITIES and "This MIB module defines dot3MauType OBJECT-IDENTITIES and
IANAifMauListBits, IANAifMauMediaAvailable, IANAifMauListBits, IANAifMauMediaAvailable,
IANAifMauAutoNegCapBits and IANAifJackType Textual Conventions, IANAifMauAutoNegCapBits, and IANAifJackType
specifying enumerated values of the ifMauTypeListBits, TEXTUAL-CONVENTIONs, specifying enumerated values of the
ifMauMediaAvailable / rpMauMediaAvailable, ifMauTypeListBits, ifMauMediaAvailable / rpMauMediaAvailable,
ifMauAutoNegCapabilityBits / ifMauAutoNegCapAdvertisedBits / ifMauAutoNegCapabilityBits / ifMauAutoNegCapAdvertisedBits /
ifMauAutoNegCapReceivedBits and ifJackType / rpJackType objects ifMauAutoNegCapReceivedBits and ifJackType / rpJackType objects
respectively, defined in the MAU-MIB. respectively, defined in the MAU-MIB.
It is intended that each new MAU type, Media Availability It is intended that each new MAU type, Media Availability
state, Auto Negotiation capability and/or Jack type defined by state, Auto Negotiation capability and/or Jack type defined by
the IEEE 802.3 working group and approved for publication in a the IEEE 802.3 working group and approved for publication in a
revision of IEEE Std 802.3 will be added to this MIB module, revision of IEEE Std 802.3 will be added to this MIB module,
provided that it is suitable for being managed by the base provided that it is suitable for being managed by the base
objects in the MAU-MIB. An Expert Review, as defined in objects in the MAU-MIB. An Expert Review, as defined in
RFC 2434 [RFC2434], is REQUIRED for such additions. RFC 2434 [RFC2434], is REQUIRED for such additions.
The following reference is used throughout this MIB module: The following reference is used throughout this MIB module:
[IEEE 802.3 Std] refers to: [IEEE802.3] refers to:
IEEE Std 802.3, 2005 Edition: 'IEEE Standard for IEEE Std 802.3, 2005 Edition: 'IEEE Standard for
Information technology - Telecommunications and information Information technology - Telecommunications and information
exchange between systems - Local and metropolitan area exchange between systems - Local and metropolitan area
networks - Specific requirements - networks - Specific requirements -
Part 3: Carrier sense multiple access with collision Part 3: Carrier sense multiple access with collision
detection (CSMA/CD) access method and physical layer detection (CSMA/CD) access method and physical layer
specifications'. specifications'.
This reference should be updated as appropriate when new This reference should be updated as appropriate when new
MAU types, Media Availability states, Auto Negotiation MAU types, Media Availability states, Auto Negotiation
capabilities and/or Jack types are added to this MIB module. capabilities, and/or Jack types are added to this MIB module.
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
The initial version of this MIB module was published in The initial version of this MIB module was published in
RFC XXXX; for full legal notices see the RFC itself. RFC 4836; for full legal notices see the RFC itself.
Supplementary information may be available at: Supplementary information may be available at:
http://www.ietf.org/copyrights/ianamib.html" http://www.ietf.org/copyrights/ianamib.html"
REVISION "200607250000Z" -- July 25, 2006 REVISION "200704210000Z" -- April 21, 2007
DESCRIPTION "Initial version of this MIB as published in DESCRIPTION "Initial version of this MIB as published in
RFC XXX." RFC 4836."
-- EdNote: Replace XXXX with the actual RFC number & remove this note ::= { mib-2 154 }
::= { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1
-- Textual Conventions -- Textual Conventions
IANAifMauTypeListBits ::= TEXTUAL-CONVENTION IANAifMauTypeListBits ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the ifMauTypeListBits "This data type is used as the syntax of the ifMauTypeListBits
object in the (updated) definition of MAU-MIB's ifMauTable. object in the (updated) definition of MAU-MIB's ifMauTable.
The most recent version of this textual convention is The most recent version of this textual convention is available
available in the on-line version of this MIB module in the online version of this MIB module on the IANA web site.
on the IANA web site.
Requests for new values should be made to IANA via email Requests for new values should be made to IANA via email
(iana@iana.org). (iana@iana.org).
Note that changes in this textual convention SHALL be Note that changes in this textual convention SHALL be
synchronized with relevant changes in the dot3MauType synchronized with relevant changes in the dot3MauType
OBJECT-IDENTITIES." OBJECT-IDENTITIES."
REFERENCE REFERENCE
"[IEEE 802.3 Std], Section 30.5.1.1.2" "[IEEE802.3], Section 30.5.1.1.2"
SYNTAX BITS { SYNTAX BITS {
bOther(0), -- other or unknown bOther(0), -- other or unknown
bAUI(1), -- AUI bAUI(1), -- AUI
b10base5(2), -- 10BASE-5 b10base5(2), -- 10BASE-5
bFoirl(3), -- FOIRL bFoirl(3), -- FOIRL
b10base2(4), -- 10BASE-2 b10base2(4), -- 10BASE-2
b10baseT(5), -- 10BASE-T duplex mode unknown b10baseT(5), -- 10BASE-T duplex mode unknown
b10baseFP(6), -- 10BASE-FP b10baseFP(6), -- 10BASE-FP
b10baseFB(7), -- 10BASE-FB b10baseFB(7), -- 10BASE-FB
skipping to change at page 49, line 30 skipping to change at page 49, line 38
IANAifMauMediaAvailable ::= TEXTUAL-CONVENTION IANAifMauMediaAvailable ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the "This data type is used as the syntax of the
ifMauMediaAvailable and rpMauMediaAvailable objects in the ifMauMediaAvailable and rpMauMediaAvailable objects in the
(updated) definition of MAU-MIB's ifMauTable and rpMauTable (updated) definition of MAU-MIB's ifMauTable and rpMauTable
respectively. respectively.
Possible values are: Possible values are:
other(1) - undefined (not listed below) other(1) - undefined (not listed below)
unknown(2) - MAU's true state is unknown; e.g. unknown(2) - MAU's true state is unknown; e.g.,
during initialization during initialization
available(3) - link, light, or loopback is normal available(3) - link, light, or loopback is normal
notAvailable(4) - link loss, low light, or no loopback notAvailable(4) - link loss, low light, or no loopback
remoteFault(5) - a fault has been detected at the remoteFault(5) - a fault has been detected at the
remote end of the link. This value remote end of the link. This value
applies to 10BASE-FB, 100BASE-T4 Far applies to 10BASE-FB, 100BASE-T4 Far
End Fault Indication and non-specified End Fault Indication and non-specified
remote faults from a system running remote faults from a system running
auto-negotiation auto-negotiation
invalidSignal(6) - invalid signal has been received from invalidSignal(6) - invalid signal has been received from
the other end of the link, 10BASE-FB the other end of the link, 10BASE-FB
only only
remoteJabber(7) - remote fault, due to jabber remoteJabber(7) - remote fault, due to jabber
remoteLinkLoss(8) - remote fault, due to link loss remoteLinkLoss(8) - remote fault, due to link loss
remoteTest(9) - remote fault, due to test remoteTest(9) - remote fault, due to test
offline(10) - offline, Clause 37 Auto-Negotiation offline(10) - offline, Clause 37 Auto-Negotiation
only only
autoNegError(11) - Auto-Negotiation Error, Clause 37 autoNegError(11) - Auto-Negotiation Error, Clause 37
Auto-Negotiation only Auto-Negotiation only
pmdLinkFault(12) - PMA/PMD receive link fault. In case of pmdLinkFault(12) - PMA/PMD receive link fault. In case
PAF (2BASE-TL / 10PASS-TS PHYs), all of PAF (2BASE-TL / 10PASS-TS PHYs),
PMEs in the aggregation group have all PMEs in the aggregation group have
detected a link fault detected a link fault
wisFrameLoss(13) - WIS loss of frame, 10GBASE-W only wisFrameLoss(13) - WIS loss of frame, 10GBASE-W only
wisSignalLoss(14) - WIS loss of signal, 10GBASE-W only wisSignalLoss(14) - WIS loss of signal, 10GBASE-W only
pcsLinkFault(15) - PCS receive link fault pcsLinkFault(15) - PCS receive link fault
excessiveBER(16) - PCS Bit Error Ratio monitor excessiveBER(16) - PCS Bit Error Ratio monitor
reporting excessive error ratio reporting excessive error ratio
dxsLinkFault(17) - DTE XGXS receive link fault, XAUI only dxsLinkFault(17) - DTE XGXS receive link fault, XAUI only
pxsLinkFault(18) - PHY XGXS receive link fault, XAUI only pxsLinkFault(18) - PHY XGXS receive link fault, XAUI only
availableReduced(19) - link normal, reduced bandwidth, availableReduced(19) - link normal, reduced bandwidth,
2BASE-TL / 10PASS-TS only 2BASE-TL / 10PASS-TS only
ready(20) - at least one PME in the aggregation ready(20) - at least one PME in the aggregation
group is detecting handshake tones, group is detecting handshake tones,
2BASE-TL / 10PASS-TS only 2BASE-TL / 10PASS-TS only
If the MAU is a 10M b/s link or fiber type (FOIRL, 10BASE-T, If the MAU is a 10M b/s link or fiber type (FOIRL, 10BASE-T,
10BASE-F), then this is equivalent to the link test fail 10BASE-F), then this is equivalent to the link test fail
state/low light function. For an AUI, 10BASE2, 10BASE5, or state/low light function. For an AUI, 10BASE2, 10BASE5, or
10BROAD36 MAU, this indicates whether or not loopback is 10BROAD36 MAU, this indicates whether loopback is detected on
detected on the DI circuit. The value of this attribute the DI circuit. The value of this attribute persists between
persists between packets for MAU types AUI, 10BASE5, 10BASE2, packets for MAU types AUI, 10BASE5, 10BASE2, 10BROAD36, and
10BROAD36, and 10BASEFP. 10BASEFP.
At power-up or following a reset, the Media Available state At power-up or following a reset, the Media Available state
will be unknown(2) for AUI, 10BASE5, 10BASE2, 10BROAD36, and will be unknown(2) for AUI, 10BASE5, 10BASE2, 10BROAD36, and
10BASE-FP MAUs. For these MAUs loopback will be tested on each 10BASE-FP MAUs. For these MAUs loopback will be tested on each
transmission during which no collision is detected. transmission during which no collision is detected.
If DI is receiving input when DO returns to IDL after a If DI is receiving input when DO returns to IDL after a
transmission and there has been no collision during the transmission and there has been no collision during the
transmission, then loopback will be detected. The Media transmission, then loopback will be detected. The Media
Available state will only change during noncollided Available state will only change during noncollided
transmissions for AUI, 10BASE2, 10BASE5, 10BROAD36, and transmissions for AUI, 10BASE2, 10BASE5, 10BROAD36, and
10BASE-FP MAUs. 10BASE-FP MAUs.
skipping to change at page 50, line 36 skipping to change at page 50, line 45
At power-up or following a reset, the Media Available state At power-up or following a reset, the Media Available state
will be unknown(2) for AUI, 10BASE5, 10BASE2, 10BROAD36, and will be unknown(2) for AUI, 10BASE5, 10BASE2, 10BROAD36, and
10BASE-FP MAUs. For these MAUs loopback will be tested on each 10BASE-FP MAUs. For these MAUs loopback will be tested on each
transmission during which no collision is detected. transmission during which no collision is detected.
If DI is receiving input when DO returns to IDL after a If DI is receiving input when DO returns to IDL after a
transmission and there has been no collision during the transmission and there has been no collision during the
transmission, then loopback will be detected. The Media transmission, then loopback will be detected. The Media
Available state will only change during noncollided Available state will only change during noncollided
transmissions for AUI, 10BASE2, 10BASE5, 10BROAD36, and transmissions for AUI, 10BASE2, 10BASE5, 10BROAD36, and
10BASE-FP MAUs. 10BASE-FP MAUs.
For 100BASE-T2, 100BASE-T4, 100BASE-TX, 100BASE-FX, For 100BASE-T2, 100BASE-T4, 100BASE-TX, 100BASE-FX,
100BASE-LX10 and 100BASE-BX10 PHYs the enumerations match the 100BASE-LX10, and 100BASE-BX10 PHYs the enumerations match the
states within the link integrity state diagram. states within the link integrity state diagram.
Any MAU that implements management of [IEEE 802.3 Std] Clause Any MAU that implements management of [IEEE802.3] Clause
28 Auto-Negotiation, will map remote fault indication to 28 Auto-Negotiation, will map remote fault indication to
remoteFault(5). 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 RF2 bits as Auto-Negotiation, will map the received RF1 and RF2 bits as
follows: Offline maps to offline(10), Link_Failure maps to follows: Offline maps to offline(10), Link_Failure maps to
remoteFault(5) and Auto-Negotiation Error maps to remoteFault(5), and Auto-Negotiation Error maps to
autoNegError(11). autoNegError(11).
The value remoteFault(5) applies to 10BASE-FB remote The value remoteFault(5) applies to 10BASE-FB remote
fault indication, the 100BASE-X far-end fault indication and fault indication, the 100BASE-X far-end fault indication, and
nonspecified remote faults from a system running Clause 28 nonspecified remote faults from a system running Clause 28
Auto-Negotiation. Auto-Negotiation.
The value remoteJabber(7), remoteLink loss(8), or remoteTest(9) The value remoteJabber(7), remoteLink loss(8), or remoteTest(9)
SHOULD be used instead of remoteFault() where the reason for SHOULD be used instead of remoteFault(5) where the reason for
remote fault is identified in the remote signaling protocol. remote fault is identified in the remote signaling protocol.
Where a Clause 22 MII or Clause 35 GMII is present, a logic Where a Clause 22 MII or Clause 35 GMII is present, a logic
one in the remote fault bit maps to the value remoteFault(5), one in the remote fault bit maps to the value remoteFault(5),
a logic zero in the link status bit maps to the enumeration a logic zero in the link status bit maps to the enumeration
notAvailable(4). The value notAvailable(4) takes precedence notAvailable(4). The value notAvailable(4) takes precedence
over remoteFault(5). over remoteFault(5).
For 2BASE-TL and 10PASS-TS PHYs, the value unknown(2) maps to For 2BASE-TL and 10PASS-TS PHYs, the value unknown(2) maps to
the condition where the PHY (PCS with connected PMEs) is the condition where the PHY (PCS with connected PMEs) is
initializing, the value ready(20) maps to the condition where initializing, the value ready(20) maps to the condition where
the interface is down and at least one PME in the aggregation the interface is down and at least one PME in the aggregation
group is ready for handshake, the value available(3) maps to group is ready for handshake, the value available(3) maps to
the condition where all the PMEs in the aggregation group are the condition where all the PMEs in the aggregation group are
up, the value notAvailable(4) maps to the condition where all up, the value notAvailable(4) maps to the condition where all
the PMEs in the aggregation group are down and no handshake the PMEs in the aggregation group are down and no handshake
tones are detected, the value availableReduced(19) maps to the tones are detected, the value availableReduced(19) maps to the
condition where the interface is up, a link fault is detected condition where the interface is up, a link fault is detected
skipping to change at page 51, line 26 skipping to change at page 51, line 40
the condition where all the PMEs in the aggregation group are the condition where all the PMEs in the aggregation group are
up, the value notAvailable(4) maps to the condition where all up, the value notAvailable(4) maps to the condition where all
the PMEs in the aggregation group are down and no handshake the PMEs in the aggregation group are down and no handshake
tones are detected, the value availableReduced(19) maps to the tones are detected, the value availableReduced(19) maps to the
condition where the interface is up, a link fault is detected condition where the interface is up, a link fault is detected
at the receive direction by one or more PMEs in the at the receive direction by one or more PMEs in the
aggregation group, but at least one PME is up and the aggregation group, but at least one PME is up and the
enumeration pmdLinkFault(12) maps to the condition where a link enumeration pmdLinkFault(12) maps to the condition where a link
fault is detected at the receive direction by all of the PMEs fault is detected at the receive direction by all of the PMEs
in the aggregation group. in the aggregation group.
For 10 Gb/s the enumerations map to value of the link_fault For 10 Gb/s the enumerations map to value of the link_fault
variable within the Link Fault Signaling state diagram variable within the Link Fault Signaling state diagram
as follows: the value OK maps to the value available(3), as follows: the value OK maps to the value available(3),
the value Local Fault maps to the value notAvailable(4) the value Local Fault maps to the value notAvailable(4),
and the value Remote Fault maps to the value remoteFault(). and the value Remote Fault maps to the value remoteFault(5).
The value pmdLinkFault(12), wisFrameLoss(13), The value pmdLinkFault(12), wisFrameLoss(13),
wisSignalLoss(14), pcsLinkFault(15), excessiveBER(16) or wisSignalLoss(14), pcsLinkFault(15), excessiveBER(16), or
dxsLinkFault(17) SHOULD be used instead of the value dxsLinkFault(17) SHOULD be used instead of the value
notAvailable(4) where the reason for the Local Fault state can notAvailable(4), where the reason for the Local Fault state can
be identified through the use of the Clause 45 MDIO Interface. be identified through the use of the Clause 45 MDIO Interface.
Where multiple reasons for the Local Fault state can be Where multiple reasons for the Local Fault state can be
identified only the highest precedence error SHOULD be identified, only the highest precedence error SHOULD be
reported. This precedence in descending order is as follows: reported. This precedence in descending order is as follows:
pxsLinkFault pxsLinkFault
pmdLinkFault pmdLinkFault
wisFrameLoss wisFrameLoss
wisSignalLoss wisSignalLoss
pcsLinkFault pcsLinkFault
excessiveBER excessiveBER
dxsLinkFault. dxsLinkFault.
Where a Clause 45 MDIO interface is present a logic zero in Where a Clause 45 MDIO interface is present a logic zero in
the PMA/PMD Receive link status bit ([IEEE 802.3 Std] the PMA/PMD Receive link status bit ([IEEE802.3]
Section 45.2.1.2.2) maps to the Section 45.2.1.2.2) maps to the value pmdLinkFault(12),
value pmdLinkFault(12), a logic one in the LOF status bit logic one in the LOF status bit (Section 45.2.2.10.4) maps
(Section 45.2.2.10.4) maps to the value wisFrameLoss(13), to the value wisFrameLoss(13), a logic one in the LOS
a logic one in the LOS status bit (Section 45.2.2.10.5) maps status bit (Section 45.2.2.10.5) maps to the value
to the value wisSignalLoss, a logic zero in the PCS Receive wisSignalLoss, a logic zero in the PCS Receive
link status bit (Section 45.2.3.2.2) maps to the value link status bit (Section 45.2.3.2.2) maps to the value
pcsLinkFault(15), a logic one in the 10GBASE-R PCS Latched pcsLinkFault(15), a logic one in the 10GBASE-R PCS Latched
high BER status bit (Section 45.2.3.12.2) maps to the value high BER status bit (Section 45.2.3.12.2) maps to the value
excessiveBER, a logic zero in the DTE XS receive link status excessiveBER, a logic zero in the DTE XS receive link status
bit (Section 45.2.5.2.2) maps to the value dxsLinkFault(17) bit (Section 45.2.5.2.2) maps to the value dxsLinkFault(17)
and a logic zero in the PHY XS transmit link status bit and a logic zero in the PHY XS transmit link status bit
(Section 45.2.4.2.2) maps to the value pxsLinkFault(18). (Section 45.2.4.2.2) maps to the value pxsLinkFault(18).
The most recent version of this textual convention is The most recent version of this textual convention is available
available in the on-line version of this MIB module in the online version of this MIB module on the IANA web site.
on the IANA web site.
Requests for new values should be made to IANA via email Requests for new values should be made to IANA via email
(iana@iana.org)." (iana@iana.org)."
REFERENCE REFERENCE
"[IEEE 802.3 Std], Section 30.5.1.1.4" "[IEEE802.3], Section 30.5.1.1.4"
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
available(3), available(3),
notAvailable(4), notAvailable(4),
remoteFault(5), remoteFault(5),
invalidSignal(6), invalidSignal(6),
remoteJabber(7), remoteJabber(7),
remoteLinkLoss(8), remoteLinkLoss(8),
remoteTest(9), remoteTest(9),
skipping to change at page 52, line 48 skipping to change at page 53, line 15
dxsLinkFault(17), dxsLinkFault(17),
pxsLinkFault(18), pxsLinkFault(18),
availableReduced(19), availableReduced(19),
ready(20) ready(20)
} }
IANAifMauAutoNegCapBits ::= TEXTUAL-CONVENTION IANAifMauAutoNegCapBits ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This data type is used as the syntax of the "This data type is used as the syntax of the
ifMauAutoNegCapabilityBits, ifMauAutoNegCapAdvertisedBits and ifMauAutoNegCapabilityBits, ifMauAutoNegCapAdvertisedBits, and
ifMauAutoNegCapReceivedBits objects in the (updated) definition ifMauAutoNegCapReceivedBits objects in the (updated) definition
of MAU-MIB's ifMauAutoNegTable. of MAU-MIB's ifMauAutoNegTable.
The most recent version of this textual convention is The most recent version of this textual convention is available
available in the on-line version of this MIB module in the online version of this MIB module on the IANA web site.
on the IANA web site.
Requests for new values should be made to IANA via email Requests for new values should be made to IANA via email
(iana@iana.org)." (iana@iana.org)."
REFERENCE REFERENCE
"[IEEE 802.3 Std], Section 30.6.1.1.5" "[IEEE802.3], Section 30.6.1.1.5"
SYNTAX BITS { SYNTAX BITS {
bOther(0), -- other or unknown bOther(0), -- other or unknown
b10baseT(1), -- 10BASE-T half duplex mode b10baseT(1), -- 10BASE-T half duplex mode
b10baseTFD(2), -- 10BASE-T full duplex mode b10baseTFD(2), -- 10BASE-T full duplex mode
b100baseT4(3), -- 100BASE-T4 b100baseT4(3), -- 100BASE-T4
b100baseTX(4), -- 100BASE-TX half duplex mode b100baseTX(4), -- 100BASE-TX half duplex mode
b100baseTXFD(5), -- 100BASE-TX full duplex mode b100baseTXFD(5), -- 100BASE-TX full duplex mode
b100baseT2(6), -- 100BASE-T2 half duplex mode b100baseT2(6), -- 100BASE-T2 half duplex mode
b100baseT2FD(7), -- 100BASE-T2 full duplex mode b100baseT2FD(7), -- 100BASE-T2 full duplex mode
bFdxPause(8), -- PAUSE for full-duplex links bFdxPause(8), -- PAUSE for full-duplex links
skipping to change at page 54, line 13 skipping to change at page 54, line 27
mAUI(7) - AUI male mAUI(7) - AUI male
fiberSC(8) - SC fiber fiberSC(8) - SC fiber
fiberMIC(9) - MIC fiber fiberMIC(9) - MIC fiber
fiberST(10) - ST fiber fiberST(10) - ST fiber
telco(11) - Telco telco(11) - Telco
mtrj(12) - MT-RJ fiber mtrj(12) - MT-RJ fiber
hssdc(13) - fiber channel style-2 hssdc(13) - fiber channel style-2
fiberLC(14) - LC fiber fiberLC(14) - LC fiber
cx4(15) - IB4X for 10GBASE-CX4 cx4(15) - IB4X for 10GBASE-CX4
The most recent version of this textual convention is The most recent version of this textual convention is available
available in the on-line version of this MIB module in the online version of this MIB module on the IANA web site.
on the IANA web site.
Requests for new values should be made to IANA via email Requests for new values should be made to IANA via email
(iana@iana.org)." (iana@iana.org)."
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
rj45(2), rj45(2),
rj45S(3), rj45S(3),
db9(4), db9(4),
bnc(5), bnc(5),
fAUI(6), fAUI(6),
skipping to change at page 54, line 48 skipping to change at page 55, line 13
-- OBJECT IDENTITIES for MAU types -- OBJECT IDENTITIES for MAU types
-- (see rpMauType and ifMauType of MAU-MIB for usage) -- (see rpMauType and ifMauType of MAU-MIB for usage)
-- The following definitions has been moved from RFC 3636 and -- The following definitions has been moved from RFC 3636 and
-- no longer appear in its revision. -- no longer appear in its revision.
dot3MauType OBJECT IDENTIFIER ::= { mib-2 snmpDot3MauMgt(26) 4 } dot3MauType OBJECT IDENTIFIER ::= { mib-2 snmpDot3MauMgt(26) 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" REFERENCE "[IEEE802.3], Section 7"
::= { dot3MauType 1 } ::= { dot3MauType 1 }
dot3MauType10Base5 OBJECT-IDENTITY dot3MauType10Base5 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "thick coax MAU" DESCRIPTION "thick coax MAU"
REFERENCE "[IEEE 802.3 Std], Section 7" REFERENCE "[IEEE802.3], Section 7"
::= { dot3MauType 2 } ::= { dot3MauType 2 }
dot3MauTypeFoirl OBJECT-IDENTITY dot3MauTypeFoirl OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "FOIRL MAU" DESCRIPTION "FOIRL MAU"
REFERENCE "[IEEE 802.3 Std], Section 9.9" REFERENCE "[IEEE802.3], Section 9.9"
::= { dot3MauType 3 } ::= { dot3MauType 3 }
dot3MauType10Base2 OBJECT-IDENTITY dot3MauType10Base2 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "thin coax MAU" DESCRIPTION "thin coax MAU"
REFERENCE "[IEEE 802.3 Std], Section 10" REFERENCE "[IEEE802.3], Section 10"
::= { dot3MauType 4 } ::= { dot3MauType 4 }
dot3MauType10BaseT OBJECT-IDENTITY dot3MauType10BaseT OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "UTP MAU. 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" REFERENCE "[IEEE802.3], Section 14"
::= { dot3MauType 5 } ::= { dot3MauType 5 }
dot3MauType10BaseFP OBJECT-IDENTITY dot3MauType10BaseFP OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "passive fiber MAU" DESCRIPTION "passive fiber MAU"
REFERENCE "[IEEE 802.3 Std], Section 16" REFERENCE "[IEEE802.3], Section 16"
::= { dot3MauType 6 } ::= { dot3MauType 6 }
dot3MauType10BaseFB OBJECT-IDENTITY dot3MauType10BaseFB OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "sync fiber MAU" DESCRIPTION "sync fiber MAU"
REFERENCE "[IEEE 802.3 Std], Section 17" REFERENCE "[IEEE802.3], Section 17"
::= { dot3MauType 7 } ::= { dot3MauType 7 }
dot3MauType10BaseFL OBJECT-IDENTITY dot3MauType10BaseFL OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "async fiber MAU. 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" REFERENCE "[IEEE802.3], Section 18"
::= { dot3MauType 8 } ::= { dot3MauType 8 }
dot3MauType10Broad36 OBJECT-IDENTITY dot3MauType10Broad36 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "broadband DTE MAU. 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" REFERENCE "[IEEE802.3], 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, half duplex mode" DESCRIPTION "UTP MAU, half duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 14" REFERENCE "[IEEE802.3], Section 14"
::= { dot3MauType 10 } ::= { dot3MauType 10 }
dot3MauType10BaseTFD OBJECT-IDENTITY dot3MauType10BaseTFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "UTP MAU, full duplex mode" DESCRIPTION "UTP MAU, full duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 14" REFERENCE "[IEEE802.3], Section 14"
::= { dot3MauType 11 } ::= { dot3MauType 11 }
dot3MauType10BaseFLHD OBJECT-IDENTITY dot3MauType10BaseFLHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "async fiber MAU, half duplex mode" DESCRIPTION "async fiber MAU, half duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 18" REFERENCE "[IEEE802.3], Section 18"
::= { dot3MauType 12 } ::= { dot3MauType 12 }
dot3MauType10BaseFLFD OBJECT-IDENTITY dot3MauType10BaseFLFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "async fiber MAU, full duplex mode" DESCRIPTION "async fiber MAU, full duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 18" REFERENCE "[IEEE802.3], Section 18"
::= { dot3MauType 13 } ::= { dot3MauType 13 }
dot3MauType100BaseT4 OBJECT-IDENTITY dot3MauType100BaseT4 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "4 pair category 3 UTP" DESCRIPTION "4 pair category 3 UTP"
REFERENCE "[IEEE 802.3 Std], Section 23" REFERENCE "[IEEE802.3], Section 23"
::= { dot3MauType 14 } ::= { dot3MauType 14 }
dot3MauType100BaseTXHD OBJECT-IDENTITY dot3MauType100BaseTXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair category 5 UTP, half duplex mode" DESCRIPTION "2 pair category 5 UTP, half duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 25" REFERENCE "[IEEE802.3], Section 25"
::= { dot3MauType 15 } ::= { dot3MauType 15 }
dot3MauType100BaseTXFD OBJECT-IDENTITY dot3MauType100BaseTXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair category 5 UTP, full duplex mode" DESCRIPTION "2 pair category 5 UTP, full duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 25" REFERENCE "[IEEE802.3], Section 25"
::= { dot3MauType 16 } ::= { dot3MauType 16 }
dot3MauType100BaseFXHD OBJECT-IDENTITY dot3MauType100BaseFXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X fiber over PMT, half duplex mode" DESCRIPTION "X fiber over PMT, half duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 26" REFERENCE "[IEEE802.3], Section 26"
::= { dot3MauType 17 } ::= { dot3MauType 17 }
dot3MauType100BaseFXFD OBJECT-IDENTITY dot3MauType100BaseFXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X fiber over PMT, full duplex mode" DESCRIPTION "X fiber over PMT, full duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 26" REFERENCE "[IEEE802.3], Section 26"
::= { dot3MauType 18 } ::= { dot3MauType 18 }
dot3MauType100BaseT2HD OBJECT-IDENTITY dot3MauType100BaseT2HD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair category 3 UTP, half duplex mode" DESCRIPTION "2 pair category 3 UTP, half duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 32" REFERENCE "[IEEE802.3], Section 32"
::= { dot3MauType 19 } ::= { dot3MauType 19 }
dot3MauType100BaseT2FD OBJECT-IDENTITY dot3MauType100BaseT2FD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair category 3 UTP, full duplex mode" DESCRIPTION "2 pair category 3 UTP, full duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 32" REFERENCE "[IEEE802.3], 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, unknown PMD, half duplex mode" DESCRIPTION "PCS/PMA, unknown PMD, half duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 36" REFERENCE "[IEEE802.3], Section 36"
::= { dot3MauType 21 } ::= { dot3MauType 21 }
dot3MauType1000BaseXFD OBJECT-IDENTITY dot3MauType1000BaseXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "PCS/PMA, unknown PMD, full duplex mode" DESCRIPTION "PCS/PMA, unknown PMD, full duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 36" REFERENCE "[IEEE802.3], Section 36"
::= { dot3MauType 22 } ::= { dot3MauType 22 }
dot3MauType1000BaseLXHD OBJECT-IDENTITY dot3MauType1000BaseLXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over long-wavelength laser, half duplex DESCRIPTION "Fiber over long-wavelength laser, half duplex
mode" mode"
REFERENCE "[IEEE 802.3 Std], Section 38" REFERENCE "[IEEE802.3], Section 38"
::= { dot3MauType 23 } ::= { dot3MauType 23 }
dot3MauType1000BaseLXFD OBJECT-IDENTITY dot3MauType1000BaseLXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over long-wavelength laser, full duplex DESCRIPTION "Fiber over long-wavelength laser, full duplex
mode" mode"
REFERENCE "[IEEE 802.3 Std], Section 38" REFERENCE "[IEEE802.3], Section 38"
::= { dot3MauType 24 } ::= { dot3MauType 24 }
dot3MauType1000BaseSXHD OBJECT-IDENTITY dot3MauType1000BaseSXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over short-wavelength laser, half DESCRIPTION "Fiber over short-wavelength laser, half
duplex mode" duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 38" REFERENCE "[IEEE802.3], Section 38"
::= { dot3MauType 25 } ::= { dot3MauType 25 }
dot3MauType1000BaseSXFD OBJECT-IDENTITY dot3MauType1000BaseSXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over short-wavelength laser, full DESCRIPTION "Fiber over short-wavelength laser, full
duplex mode" duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 38" REFERENCE "[IEEE802.3], Section 38"
::= { dot3MauType 26 } ::= { dot3MauType 26 }
dot3MauType1000BaseCXHD OBJECT-IDENTITY dot3MauType1000BaseCXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Copper over 150-Ohm balanced cable, half DESCRIPTION "Copper over 150-Ohm balanced cable, half
duplex mode" duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 39" REFERENCE "[IEEE802.3], Section 39"
::= { dot3MauType 27 } ::= { dot3MauType 27 }
dot3MauType1000BaseCXFD OBJECT-IDENTITY dot3MauType1000BaseCXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Copper over 150-Ohm balanced cable, full DESCRIPTION "Copper over 150-Ohm balanced cable, full
duplex mode" duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 39" REFERENCE "[IEEE802.3], Section 39"
::= { dot3MauType 28 } ::= { dot3MauType 28 }
dot3MauType1000BaseTHD OBJECT-IDENTITY dot3MauType1000BaseTHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Four-pair Category 5 UTP, half duplex mode" DESCRIPTION "Four-pair Category 5 UTP, half duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 40" REFERENCE "[IEEE802.3], Section 40"
::= { dot3MauType 29 } ::= { dot3MauType 29 }
dot3MauType1000BaseTFD OBJECT-IDENTITY dot3MauType1000BaseTFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Four-pair Category 5 UTP, full duplex mode" DESCRIPTION "Four-pair Category 5 UTP, full duplex mode"
REFERENCE "[IEEE 802.3 Std], Section 40" REFERENCE "[IEEE802.3], 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, unknown PMD." DESCRIPTION "X PCS/PMA, unknown PMD."
REFERENCE "[IEEE 802.3 Std], Section 48" REFERENCE "[IEEE802.3], Section 48"
::= { dot3MauType 31 } ::= { dot3MauType 31 }
dot3MauType10GigBaseLX4 OBJECT-IDENTITY dot3MauType10GigBaseLX4 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X fiber over WWDM optics" DESCRIPTION "X fiber over WWDM optics"
REFERENCE "[IEEE 802.3 Std], Section 53" REFERENCE "[IEEE802.3], Section 53"
::= { dot3MauType 32 } ::= { dot3MauType 32 }
dot3MauType10GigBaseR OBJECT-IDENTITY dot3MauType10GigBaseR OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "R PCS/PMA, unknown PMD." DESCRIPTION "R PCS/PMA, unknown PMD."
REFERENCE "[IEEE 802.3 Std], Section 49" REFERENCE "[IEEE802.3], Section 49"
::= { dot3MauType 33 } ::= { dot3MauType 33 }
dot3MauType10GigBaseER OBJECT-IDENTITY dot3MauType10GigBaseER OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "R fiber over 1550 nm optics" DESCRIPTION "R fiber over 1550 nm optics"
REFERENCE "[IEEE 802.3 Std], Section 52" REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 34 } ::= { dot3MauType 34 }
dot3MauType10GigBaseLR OBJECT-IDENTITY dot3MauType10GigBaseLR OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "R fiber over 1310 nm optics" DESCRIPTION "R fiber over 1310 nm optics"
REFERENCE "[IEEE 802.3 Std], Section 52" REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 35 } ::= { dot3MauType 35 }
dot3MauType10GigBaseSR OBJECT-IDENTITY dot3MauType10GigBaseSR OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "R fiber over 850 nm optics" DESCRIPTION "R fiber over 850 nm optics"
REFERENCE "[IEEE 802.3 Std], Section 52" REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 36 } ::= { dot3MauType 36 }
dot3MauType10GigBaseW OBJECT-IDENTITY dot3MauType10GigBaseW OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "W PCS/PMA, unknown PMD." DESCRIPTION "W PCS/PMA, unknown PMD."
REFERENCE "[IEEE 802.3 Std], Section 49 and 50" REFERENCE "[IEEE802.3], 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" DESCRIPTION "W fiber over 1550 nm optics"
REFERENCE "[IEEE 802.3 Std], Section 52" REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 38 } ::= { dot3MauType 38 }
dot3MauType10GigBaseLW OBJECT-IDENTITY dot3MauType10GigBaseLW OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "W fiber over 1310 nm optics" DESCRIPTION "W fiber over 1310 nm optics"
REFERENCE "[IEEE 802.3 Std], Section 52" REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 39 } ::= { dot3MauType 39 }
dot3MauType10GigBaseSW OBJECT-IDENTITY dot3MauType10GigBaseSW OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "W fiber over 850 nm optics" DESCRIPTION "W fiber over 850 nm optics"
REFERENCE "[IEEE 802.3 Std], Section 52" REFERENCE "[IEEE802.3], Section 52"
::= { dot3MauType 40 } ::= { dot3MauType 40 }
------ new since RFC 3636: ------ new since RFC 3636:
dot3MauType10GigBaseCX4 OBJECT-IDENTITY dot3MauType10GigBaseCX4 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X copper over 8 pair 100-Ohm balanced cable" DESCRIPTION "X copper over 8 pair 100-Ohm balanced cable"
REFERENCE "[IEEE 802.3 Std], Section 54" REFERENCE "[IEEE802.3], Section 54"
::= { dot3MauType 41 } ::= { dot3MauType 41 }
dot3MauType2BaseTL OBJECT-IDENTITY dot3MauType2BaseTL OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Voice grade UTP copper, up to 2700m, optional PAF" DESCRIPTION "Voice grade UTP copper, up to 2700m, optional PAF"
REFERENCE "[IEEE 802.3 Std], Sections 61 and 63" REFERENCE "[IEEE802.3], Sections 61 and 63"
::= { dot3MauType 42 } ::= { dot3MauType 42 }
dot3MauType10PassTS OBJECT-IDENTITY dot3MauType10PassTS OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Voice grade UTP copper, up to 750m, optional PAF" DESCRIPTION "Voice grade UTP copper, up to 750m, optional PAF"
REFERENCE "[IEEE 802.3 Std], Sections 61 and 62" REFERENCE "[IEEE802.3], Sections 61 and 62"
::= { dot3MauType 43 } ::= { dot3MauType 43 }
dot3MauType100BaseBX10D OBJECT-IDENTITY dot3MauType100BaseBX10D OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "One single-mode fiber OLT, long wavelength, 10km" DESCRIPTION "One single-mode fiber OLT, long wavelength, 10km"
REFERENCE "[IEEE 802.3 Std], Section 58" REFERENCE "[IEEE802.3], Section 58"
::= { dot3MauType 44 } ::= { dot3MauType 44 }
dot3MauType100BaseBX10U OBJECT-IDENTITY dot3MauType100BaseBX10U OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "One single-mode fiber ONU, long wavelength, 10km" DESCRIPTION "One single-mode fiber ONU, long wavelength, 10km"
REFERENCE "[IEEE 802.3 Std], Section 58" REFERENCE "[IEEE802.3], Section 58"
::= { dot3MauType 45 } ::= { dot3MauType 45 }
dot3MauType100BaseLX10 OBJECT-IDENTITY dot3MauType100BaseLX10 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Two single-mode fibers, long wavelength, 10km" DESCRIPTION "Two single-mode fibers, long wavelength, 10km"
REFERENCE "[IEEE 802.3 Std], Section 58" REFERENCE "[IEEE802.3], Section 58"
::= { dot3MauType 46 } ::= { dot3MauType 46 }
dot3MauType1000BaseBX10D OBJECT-IDENTITY dot3MauType1000BaseBX10D OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "One single-mode fiber OLT, long wavelength, 10km" DESCRIPTION "One single-mode fiber OLT, long wavelength, 10km"
REFERENCE "[IEEE 802.3 Std], Section 59" REFERENCE "[IEEE802.3], Section 59"
::= { dot3MauType 47 } ::= { dot3MauType 47 }
dot3MauType1000BaseBX10U OBJECT-IDENTITY dot3MauType1000BaseBX10U OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "One single-mode fiber ONU, long wavelength, 10km" DESCRIPTION "One single-mode fiber ONU, long wavelength, 10km"
REFERENCE "[IEEE 802.3 Std], Section 59" REFERENCE "[IEEE802.3], Section 59"
::= { dot3MauType 48 } ::= { dot3MauType 48 }
dot3MauType1000BaseLX10 OBJECT-IDENTITY dot3MauType1000BaseLX10 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Two sigle-mode fiber, long wavelength, 10km" DESCRIPTION "Two sigle-mode fiber, long wavelength, 10km"
REFERENCE "[IEEE 802.3 Std], Section 59" REFERENCE "[IEEE802.3], Section 59"
::= { dot3MauType 49 } ::= { dot3MauType 49 }
dot3MauType1000BasePX10D OBJECT-IDENTITY dot3MauType1000BasePX10D OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "One single-mode fiber EPON OLT, 10km" DESCRIPTION "One single-mode fiber EPON OLT, 10km"
REFERENCE "[IEEE 802.3 Std], Section 60" REFERENCE "[IEEE802.3], Section 60"
::= { dot3MauType 50 } ::= { dot3MauType 50 }
dot3MauType1000BasePX10U OBJECT-IDENTITY dot3MauType1000BasePX10U OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "One single-mode fiber EPON ONU, 10km" DESCRIPTION "One single-mode fiber EPON ONU, 10km"
REFERENCE "[IEEE 802.3 Std], Section 60" REFERENCE "[IEEE802.3], Section 60"
::= { dot3MauType 51 } ::= { dot3MauType 51 }
dot3MauType1000BasePX20D OBJECT-IDENTITY dot3MauType1000BasePX20D OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "One single-mode fiber EPON OLT, 20km" DESCRIPTION "One single-mode fiber EPON OLT, 20km"
REFERENCE "[IEEE 802.3 Std], Section 60" REFERENCE "[IEEE802.3], Section 60"
::= { dot3MauType 52 } ::= { dot3MauType 52 }
dot3MauType1000BasePX20U OBJECT-IDENTITY dot3MauType1000BasePX20U OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "One single-mode fiber EPON ONU, 20km" DESCRIPTION "One single-mode fiber EPON ONU, 20km"
REFERENCE "[IEEE 802.3 Std], Section 60" REFERENCE "[IEEE802.3], Section 60"
::= { dot3MauType 53 } ::= { dot3MauType 53 }
END END
6. Security Considerations 6. Security Considerations
The IANA-MAU-MIB does not define any management objects. Instead, it The IANA-MAU-MIB does not define any management objects. Instead, it
defines a set of textual conventions which are used by the MAU-MIB defines a set of textual conventions which are used by the MAU-MIB
and may be used by other MIB modules to define management objects. and may be used by other MIB modules to define management objects.
Meaningful security considerations can only be written for MIB Meaningful security considerations can only be written for MIB
modules that define management objects. modules that define management objects.
There is a number of management objects defined in the MAU-MIB that There are a number of management objects defined in the MAU-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:
o enabling or disabling a MAU o enabling or disabling a MAU
o changing a MAU's default type o changing a MAU's default type
o enabling, disabling or restarting autonegotiation o enabling, disabling, or restarting autonegotiation
o modifying the capabilities that a MAU advertizes during o 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.
Some of the readable objects in the MAU-MIB module (i.e., objects Some of the readable objects in the MAU-MIB module (i.e., objects
with a MAX-ACCESS other than not-accessible) may be considered with a MAX-ACCESS other than not-accessible) may be considered
sensitive or vulnerable in some network environments. In some sensitive or vulnerable in some network environments. In some
environments it may be undesirable to allow unauthorized parties to environments, it may be undesirable to allow unauthorized parties to
access statistics or status information about individual links in a access statistics or status information about individual links in a
network. It is thus important to control even GET and/or NOTIFY network. It is thus important to control even GET and/or NOTIFY
access to these objects and possibly to even encrypt the values of access to these objects and possibly to even encrypt the values of
these objects when sending them over the network via SNMP. these objects when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec), Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects allowed to access and GET/SET (read/change/create/delete) the objects
in the MAU-MIB module. in the MAU-MIB module.
It is recommended that the implementors consider the security It is RECOMMENDED that the implementors consider the security
features as provided by the SNMPv3 framework (see [RFC3410], section features as provided by the SNMPv3 framework (see [RFC3410], section
8), including full support for the SNMPv3 cryptographic mechanisms 8), including full support for the SNMPv3 cryptographic mechanisms
(for authentication and privacy). (for authentication and privacy).
Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of the MAU-MIB module is properly configured to give access instance of the MAU-MIB module is properly configured to give access
to the objects only to those principals (users) that have legitimate to the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
7. IANA Considerations 7. IANA Considerations
This document defines first version of the IANA-maintained IANA-MAU- This document defines first version of the IANA-maintained IANA-MAU-
MIB module. It is intended that each new MAU type, Media Available MIB module. It is intended that each new MAU type, Media Available
state, Auto Negotiation capability and/or Jack type defined by the state, Auto Negotiation capability, and/or Jack type defined by the
IEEE 802.3 working group and approved for publication in a revision IEEE 802.3 working group and approved for publication in a revision
of IEEE Std 802.3 will be added to the IANA-maintaned MIB module, of IEEE Std 802.3 will be added to the IANA-maintaned MIB module,
provided that it is suitable for being managed by the base objects in provided that it is suitable for being managed by the base objects in
the MAU-MIB module. the MAU-MIB module.
For each new MAU type added, a short description of the MAU For each new MAU type added, a short description of the MAU
technology and, wherever possible, a reference to a publicly technology and, wherever possible, a reference to a publicly
available specification SHOULD be specified. An Expert Review, as available specification SHOULD be specified. An Expert Review, as
defined in RFC 2434 [RFC2434], is REQUIRED, for each modification. defined in RFC 2434 [RFC2434], is REQUIRED, for each modification.
skipping to change at page 64, line 24 skipping to change at page 64, line 35
Communications, Keith McCloghrie, then of Hughes LAN Systems, and Sam Communications, Keith McCloghrie, then of Hughes LAN Systems, and Sam
Roberts, then of Farallon Computing, and produced by the Hub MIB Roberts, then of Farallon Computing, and produced by the Hub MIB
Working Group. It extends that document by providing support for 100 Working Group. It extends that document by providing support for 100
Mb/sec MAUs, full duplex MAUs, auto-negotiation, and jack management Mb/sec MAUs, full duplex MAUs, auto-negotiation, and jack management
as defined in [IEEE802.3]. as defined in [IEEE802.3].
9. References 9. References
9.1. Normative References 9.1. Normative References
[IEEE802.3] [IEEE802.3] IEEE, "IEEE Standard for Information technology -
IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks -
requirements - Part 3: Carrier sense multiple access with Specific requirements - Part 3: Carrier sense multiple
collision detection (CSMA/CD) access method and physical access with collision detection (CSMA/CD) access
layer specifications", IEEE Std 802.3-2005, December 2005. method and physical layer specifications", IEEE
Std 802.3-2005, December 2005.
[IEEE802.3ae] [IEEE802.3ae] IEEE, "IEEE Standard for Information technology -
IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks -
requirements - Part 3: Carrier sense multiple access with Specific requirements - Part 3: Carrier sense multiple
collision detection (CSMA/CD) access method and physical access with collision detection (CSMA/CD) access
layer specifications - Media Access Control (MAC) method and physical layer specifications - Media
Parameters, Physical Layer and Management Parameters for Access Control (MAC) Parameters, Physical Layer and
10 Gb/s Operation", IEEE Std 802.3ae-2002, August 2002. Management Parameters for 10 Gb/s Operation", IEEE
Std 802.3ae-2002, August 2002.
[IEEE802.3ah] [IEEE802.3ah] IEEE, "Information technology - Telecommunications and
IEEE, "Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - Part metropolitan area networks - Specific requirements -
3: Carrier sense multiple access with collision detection Part 3: Carrier sense multiple access with collision
(CSMA/CD) access method and physical layer specifications detection (CSMA/CD) access method and physical layer
- Media Access Control Parameters, Physical Layers and specifications - Media Access Control Parameters,
Management Parameters for Subscriber Access Networks", Physical Layers and Management Parameters for
IEEE Std 802.3ah-2004, September 2004. Subscriber Access Networks", IEEE Std 802.3ah-2004,
September 2004.
[IEEE802.3ak] [IEEE802.3ak] IEEE, "IEEE Standard for Information technology -
IEEE, "IEEE Standard for Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks -
requirements - Part 3: Carrier sense multiple access with Specific requirements - Part 3: Carrier sense multiple
collision detection (CSMA/CD) access method and physical access with collision detection (CSMA/CD) access
layer specifications - Physical Layer and Management method and physical layer specifications - Physical
Parameters for 10Gb/s Operation, Type 10GBASE-CX4", IEEE Layer and Management Parameters for 10Gb/s Operation,
Std 802.3ak-2004, March 2004. Type 10GBASE-CX4", IEEE Std 802.3ak-2004, March 2004.
[RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K. [RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K.
McCloghrie, "Definitions of Managed Objects for IEEE 802.3 McCloghrie, "Definitions of Managed Objects for IEEE
Repeater Devices using SMIv2", RFC 2108, February 1997. 802.3 Repeater Devices using SMIv2", RFC 2108,
February 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing
IANA Considerations Section in RFCs", BCP 26, RFC 2434, an IANA Considerations Section in RFCs", BCP 26,
October 1998. RFC 2434, October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of Schoenwaelder, Ed., "Structure of Management
Management Information Version 2 (SMIv2)", STD 58, Information Version 2 (SMIv2)", STD 58, RFC 2578,
RFC 2578, April 1999. April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Schoenwaelder, Ed., "Textual Conventions for SMIv2",
Conventions for SMIv2", STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003. Ethernet-like Interface Types", RFC 3635,
September 2003.
9.2. Informative References 9.2. Informative References
[RFC1515] McMaster, D., McCloghrie, K., and S. Roberts, "Definitions [RFC1515] McMaster, D., McCloghrie, K., and S. Roberts,
of Managed Objects for IEEE 802.3 Medium Attachment Units "Definitions of Managed Objects for IEEE 802.3 Medium
(MAUs)", RFC 1515, September 1993. Attachment Units (MAUs)", RFC 1515, September 1993.
[RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K., [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie,
and S. Roberts, "Definitions of Managed Objects for IEEE K., and S. Roberts, "Definitions of Managed Objects
802.3 Medium Attachment Units (MAUs) using SMIv2", for IEEE 802.3 Medium Attachment Units (MAUs) using
RFC 2239, November 1997. SMIv2", RFC 2239, November 1997.
[RFC2668] Smith, A., Flick, J., de Graaf, K., Romascanu, D., [RFC2668] Smith, A., Flick, J., de Graaf, K., Romascanu, D.,
McMaster, D., McCloghrie, K., and S. Roberts, "Definitions McMaster, D., McCloghrie, K., and S. Roberts,
of Managed Objects for IEEE 802.3 Medium Attachment Units "Definitions of Managed Objects for IEEE 802.3 Medium
(MAUs)", RFC 2668, August 1999. Attachment Units (MAUs)", RFC 2668, August 1999.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for
Standard Management Framework", RFC 3410, December 2002. Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC3418] Presuhn, R., "Management Information Base (MIB) for the [RFC3418] Presuhn, R., "Management Information Base (MIB) for
Simple Network Management Protocol (SNMP)", STD 62, the Simple Network Management Protocol (SNMP)",
RFC 3418, December 2002. STD 62, RFC 3418, December 2002.
[RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE
Medium Attachment Units (MAUs)", RFC 3636, September 2003. 802.3 Medium Attachment Units (MAUs)", RFC 3636,
September 2003.
[RFC3637] Heard, C., "Definitions of Managed Objects for the [RFC3637] Heard, C., "Definitions of Managed Objects for the
Ethernet WAN Interface Sublayer", RFC 3637, Ethernet WAN Interface Sublayer", RFC 3637,
September 2003. September 2003.
Author's Address Author's Address
Edward Beili Edward Beili
Actelis Networks Actelis Networks
Bazel 25 Bazel 25
Petach-Tikva Petach-Tikva
Israel Israel
Phone: +972-3-924-3491 Phone: +972-3-924-3491
Email: edward.beili@actelis.com EMail: edward.beili@actelis.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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 Rights or other rights that might be claimed to Intellectual Property Rights 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; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 68, line 29 skipping to change at page 67, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Acknowledgement
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 299 change blocks. 
435 lines changed or deleted 428 lines changed or added

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