draft-ietf-hubmib-mau-mib-v2-03.txt   rfc2668.txt 
Hub MIB Working Group A. Smith Network Working Group A. Smith
INTERNET DRAFT Extreme Networks, Inc. Request for Comments: 2668 Extreme Networks, Inc.
J. Flick Obsoletes: 2239 J. Flick
Hewlett-Packard Company Category: Standards Track Hewlett-Packard Company
K. de Graaf K. de Graaf
Argon Networks Argon Networks
D. Romascanu D. Romascanu
Lucent Technologies Lucent Technologies
D. McMaster D. McMaster
Cisco Systems, Inc. Cisco Systems, Inc.
K. McCloghrie K. McCloghrie
Cisco Systems, Inc. Cisco Systems, Inc.
S. Roberts S. Roberts
Farallon Computing, Inc. Farallon Computing, Inc.
March 1999 August 1999
Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs) using SMIv2
<draft-ietf-hubmib-mau-mib-v2-03.txt> Definitions of Managed Objects for
IEEE 802.3 Medium Attachment Units (MAUs)
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet-Drafts are working Internet community, and requests discussion and suggestions for
documents of the Internet Engineering Task Force (IETF), its areas, improvements. Please refer to the current edition of the "Internet
and its working groups. Note that other groups may also distribute Official Protocol Standards" (STD 1) for the standardization state
working documents as Internet-Drafts. and status of this protocol. Distribution of this memo is unlimited.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress."
To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
This memo obsoletes RFC 2239, ''Definitions of Managed Objects for This memo obsoletes RFC 2239, "Definitions of Managed Objects for
IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2''. This memo IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2". This memo
extends that specification by including management information useful extends that specification by including management information useful
for the management of 1000 Mb/s MAUs. for the management of 1000 Mb/s MAUs.
Ethernet technology, as defined by the 802.3 Working Group of the Ethernet technology, as defined by the 802.3 Working Group of the
IEEE, continues to evolve, with scalable increases in speed, new IEEE, continues to evolve, with scalable increases in speed, new
types of cabling and interfaces, and new features. This evolution types of cabling and interfaces, and new features. This evolution
may require changes in the managed objects in order to reflect this may require changes in the managed objects in order to reflect this
new functionality. This document, as with other documents issued by new functionality. This document, as with other documents issued by
this working group, reflects a certain stage in the evolution of this working group, reflects a certain stage in the evolution of
Ethernet technology. In the future, this document might be revised, Ethernet technology. In the future, this document might be revised,
or new documents might be issued by the Ethernet Interfaces and Hub or new documents might be issued by the Ethernet Interfaces and Hub
MIB Working Group, in order to reflect the evolution of Ethernet MIB Working Group, in order to reflect the evolution of Ethernet
technology. technology.
Distribution of this memo is unlimited. Please forward comments to
hubmib@hprnd.rose.hp.com.
Table of Contents Table of Contents
1. Introduction ............................................... 2 1. Introduction ............................................... 2
2. The SNMP Management Framework .............................. 3 2. The SNMP Management Framework .............................. 3
3. Overview ................................................... 4 3. Overview ................................................... 4
3.1. Relationship to RFC 2239 ................................. 4 3.1. Relationship to RFC 2239 ................................. 4
3.2. Relationship to RFC 1515 ................................. 4 3.2. Relationship to RFC 1515 ................................. 4
3.3. MAU Management ........................................... 4 3.3. MAU Management ........................................... 4
3.4. Relationship to Other MIBs ............................... 5 3.4. Relationship to Other MIBs ............................... 5
3.4.1. Relationship to the Interfaces MIB ..................... 5 3.4.1. Relationship to the Interfaces MIB ..................... 5
3.4.2. Relationship to the 802.3 Repeater MIB ................. 5 3.4.2. Relationship to the 802.3 Repeater MIB ................. 5
3.5. Management of Internal MAUs .............................. 5 3.5. Management of Internal MAUs .............................. 5
4. Definitions ................................................ 6 4. Definitions ................................................ 6
5. Intellectual Property ...................................... 47 5. Intellectual Property ...................................... 49
6. Acknowledgements ........................................... 48 6. Acknowledgements ........................................... 49
7. References ................................................. 48 7. References ................................................. 50
8. Security Considerations .................................... 51 8. Security Considerations .................................... 52
9. Authors' Addresses ......................................... 51 9. Authors' Addresses ......................................... 53
A. Change Log ................................................. 53 10. Appendix: Change Log ....................................... 55
B. Full Copyright Statement ................................... 54 11. Full Copyright Statement .................................. 57
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines objects for managing IEEE 802.3 Medium In particular, it defines objects for managing IEEE 802.3 Medium
Attachment Units (MAUs). Attachment Units (MAUs).
This memo also includes a MIB module. This MIB module extends the This memo also includes a MIB module. This MIB module extends the
list of managed objects specified in the earlier version of this MIB: list of managed objects specified in the earlier version of this MIB:
skipping to change at page 3, line 16 skipping to change at page 3, line 10
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [20]. document are to be interpreted as described in [20].
2. The SNMP Management Framework 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC second version, called SMIv2, is described in STD 58, RFC 2578
1904 [7]. [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [8]. A second version of the SNMP
protocol, which is not an Internet standards track protocol, is message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
The third version of the message protocol is called SNMPv3 and 1906 [10]. The third version of the message protocol is called
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations described in STD 15, RFC 1157 [8]. A second set of protocol
and associated PDU formats is described in RFC 1905 [13]. operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2273 [14] and o A set of fundamental applications described in RFC 2573 [14] and
the view-based access control mechanism described in RFC 2275 the view-based access control mechanism described in RFC 2575
[15]. [15].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
skipping to change at page 6, line 24 skipping to change at page 6, line 20
Counter32, Integer32, Counter32, Integer32,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE,
OBJECT-IDENTITY, mib-2 OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue, TEXTUAL-CONVENTION TruthValue, TEXTUAL-CONVENTION
FROM SNMPv2-TC FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
mauMod MODULE-IDENTITY mauMod MODULE-IDENTITY
LAST-UPDATED "9901280031Z" -- January 28, 1999 LAST-UPDATED "9908240400Z" -- August 24, 1999
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-mail: hubmib@hprnd.rose.hp.com "WG E-mail: hubmib@hprnd.rose.hp.com
To subscribe: hubmib-request@hprnd.rose.hp.com To subscribe: hubmib-request@hprnd.rose.hp.com
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Lucent Technologies Postal: Lucent Technologies
Atidim Technology Park, Bldg. 3 Atidim Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
Israel Israel
Tel: +972 3 645 8414, 6458458 Tel: +972 3 645 8414, 6458458
Fax: +972 3 648 7146 Fax: +972 3 648 7146
E-mail: dromasca@lucent.com E-mail: dromasca@lucent.com
Editors: Andrew Smith Editors: Andrew Smith
Postal: Extreme Networks, Inc. Postal: Extreme Networks, Inc.
10460 Bandley Drive 10460 Bandley Drive
Cupertino, CA 95014 Cupertino, CA 95014
USA USA
Tel: +1 408 342 0999 Tel: +1 408 579-2821
E-mail: andrew@extremenetworks.com E-mail: andrew@extremenetworks.com
John Flick John Flick
Postal: Hewlett-Packard Company Postal: Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557 Roseville, CA 95747-5557
USA USA
Tel: +1 916 785 4018 Tel: +1 916 785 4018
Fax: +1 916 785 1199 Fax: +1 916 785 1199
E-mail: johnf@rose.hp.com E-mail: johnf@rose.hp.com
Kathryn de Graaf
Kathryn de Graaf Postal: Argon Networks
Postal: Argon Networks 25 Porter Road
25 Porter Road Littleton, MA 01460
Littleton, MA 01460 USA
USA Tel: +1 978 486 0665 x163
Tel: +1 978 486 0665 x163 Fax: +1 978 486 9379
Fax: +1 978 486 9379 E-mail: kdegraaf@argon.com"
E-mail: kdegraaf@argon.com" DESCRIPTION "Management information for 802.3 MAUs.
DESCRIPTION "Management information for 802.3 MAUs.
The following reference is used throughout The following reference is used throughout
this MIB module: this MIB module:
[IEEE 802.3 Std] refers to [IEEE 802.3 Std] refers to
IEEE Std 802.3, 1998 Edition: 'Information IEEE Std 802.3, 1998 Edition: 'Information
technology - Telecommunications and technology - Telecommunications and
information exchange between systems - information exchange between systems -
Local and metropolitan area networks - Local and metropolitan area networks -
Specific requirements - Part 3: Carrier Specific requirements - Part 3: Carrier
sense multiple access with collision sense multiple access with collision
detection (CSMA/CD) access method and detection (CSMA/CD) access method and
physical layer specifications', physical layer specifications',
September 1998. September 1998.
Of particular interest is Clause 30, '10Mb/s, Of particular interest is Clause 30, '10Mb/s,
100Mb/s and 1000Mb/s Management'." 100Mb/s and 1000Mb/s Management'."
REVISION "9901280031Z" -- January 28, 1999 REVISION "9908240400Z" -- August 24, 1999
DESCRIPTION "Updated to include support for 1000 Mb/sec DESCRIPTION "This version published as RFC 2668. Updated
to include support for 1000 Mb/sec
MAUs and flow control negotiation." MAUs and flow control negotiation."
REVISION "9710310000Z" -- October 31, 1997 REVISION "9710310000Z" -- October 31, 1997
DESCRIPTION "Version published as RFC 2239." DESCRIPTION "This version published as RFC 2239."
::= { snmpDot3MauMgt 6 } REVISION "9309300000Z" -- September 30, 1993
DESCRIPTION "Initial version, published as RFC 1515."
snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } ::= { snmpDot3MauMgt 6 }
-- textual conventions snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 }
JackType ::= TEXTUAL-CONVENTION -- textual conventions
STATUS current
DESCRIPTION "Common enumeration values for repeater
and interface MAU jack types."
SYNTAX INTEGER {
other(1),
rj45(2),
rj45S(3), -- rj45 shielded
db9(4),
bnc(5),
fAUI(6), -- female aui
mAUI(7), -- male aui
fiberSC(8),
fiberMIC(9),
fiberST(10),
telco(11),
mtrj(12), -- fiber MT-RJ
hssdc(13) -- fiber channel style-2
}
dot3RpMauBasicGroup JackType ::= TEXTUAL-CONVENTION
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } STATUS current
dot3IfMauBasicGroup DESCRIPTION "Common enumeration values for repeater
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } and interface MAU jack types."
dot3BroadMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
dot3IfMauAutoNegGroup SYNTAX INTEGER {
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } other(1),
rj45(2),
rj45S(3), -- rj45 shielded
db9(4),
bnc(5),
fAUI(6), -- female aui
mAUI(7), -- male aui
fiberSC(8),
fiberMIC(9),
fiberST(10),
telco(11),
mtrj(12), -- fiber MT-RJ
hssdc(13) -- fiber channel style-2
}
-- object identities for MAU types dot3RpMauBasicGroup
-- (see rpMauType and ifMauType for usage) OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
dot3IfMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
dot3BroadMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
dot3MauType dot3IfMauAutoNegGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
dot3MauTypeAUI OBJECT-IDENTITY -- object identities for MAU types
STATUS current -- (see rpMauType and ifMauType for usage)
DESCRIPTION "no internal MAU, view from AUI"
::= { dot3MauType 1 }
dot3MauType10Base5 OBJECT-IDENTITY dot3MauType
STATUS current OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 }
DESCRIPTION "thick coax MAU (per 802.3 section 8)"
::= { dot3MauType 2 }
dot3MauTypeFoirl OBJECT-IDENTITY dot3MauTypeAUI OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "FOIRL MAU (per 802.3 section 9.9)" DESCRIPTION "no internal MAU, view from AUI"
::= { dot3MauType 3 } ::= { dot3MauType 1 }
dot3MauType10Base2 OBJECT-IDENTITY dot3MauType10Base5 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "thin coax MAU (per 802.3 section 10)" DESCRIPTION "thick coax MAU (per 802.3 section 8)"
::= { dot3MauType 4 } ::= { dot3MauType 2 }
dot3MauTypeFoirl OBJECT-IDENTITY
STATUS current
DESCRIPTION "FOIRL MAU (per 802.3 section 9.9)"
::= { dot3MauType 3 }
dot3MauType10BaseT OBJECT-IDENTITY dot3MauType10Base2 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "UTP MAU (per 802.3 section 14)" DESCRIPTION "thin coax MAU (per 802.3 section 10)"
::= { dot3MauType 5 } ::= { dot3MauType 4 }
dot3MauType10BaseFP OBJECT-IDENTITY dot3MauType10BaseT OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "passive fiber MAU (per 802.3 section 16)" DESCRIPTION "UTP MAU (per 802.3 section 14).
::= { dot3MauType 6 } Note that it is strongly recommended that
agents return either dot3MauType10BaseTHD or
dot3MauType10BaseTFD if the duplex mode is
known. However, management applications should
be prepared to receive this MAU type value from
older agent implementations."
::= { dot3MauType 5 }
dot3MauType10BaseFB OBJECT-IDENTITY dot3MauType10BaseFP OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "sync fiber MAU (per 802.3 section 17)" DESCRIPTION "passive fiber MAU (per 802.3 section 16)"
::= { dot3MauType 7 } ::= { dot3MauType 6 }
dot3MauType10BaseFL OBJECT-IDENTITY dot3MauType10BaseFB OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "async fiber MAU (per 802.3 section 18)" DESCRIPTION "sync fiber MAU (per 802.3 section 17)"
::= { dot3MauType 8 } ::= { dot3MauType 7 }
dot3MauType10Broad36 OBJECT-IDENTITY dot3MauType10BaseFL OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "broadband DTE MAU (per 802.3 section 11). DESCRIPTION "async fiber MAU (per 802.3 section 18)
Note that 10BROAD36 MAUs can be attached to Note that it is strongly recommended that
interfaces but not to repeaters." agents return either dot3MauType10BaseFLHD or
::= { dot3MauType 9 } dot3MauType10BaseFLFD if the duplex mode is
known. However, management applications should
be prepared to receive this MAU type value from
older agent implementations."
::= { dot3MauType 8 }
------ new since RFC 1515: dot3MauType10Broad36 OBJECT-IDENTITY
STATUS current
DESCRIPTION "broadband DTE MAU (per 802.3 section 11).
Note that 10BROAD36 MAUs can be attached to
interfaces but not to repeaters."
::= { dot3MauType 9 }
------ new since RFC 1515:
dot3MauType10BaseTHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "UTP MAU (per 802.3 section 14), half duplex
mode"
::= { dot3MauType 10 }
dot3MauType10BaseTHD OBJECT-IDENTITY dot3MauType10BaseTFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "UTP MAU (per 802.3 section 14), half duplex DESCRIPTION "UTP MAU (per 802.3 section 14), full duplex
mode" mode"
::= { dot3MauType 10 } ::= { dot3MauType 11 }
dot3MauType10BaseTFD OBJECT-IDENTITY dot3MauType10BaseFLHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "UTP MAU (per 802.3 section 14), full duplex DESCRIPTION "async fiber MAU (per 802.3 section 18), half
mode" duplex mode"
::= { dot3MauType 11 } ::= { dot3MauType 12 }
dot3MauType10BaseFLHD OBJECT-IDENTITY dot3MauType10BaseFLFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "async fiber MAU (per 802.3 section 18), half DESCRIPTION "async fiber MAU (per 802.3 section 18), full
duplex mode" duplex mode"
::= { dot3MauType 12 } ::= { dot3MauType 13 }
dot3MauType10BaseFLFD OBJECT-IDENTITY dot3MauType100BaseT4 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "async fiber MAU (per 802.3 section 18), full DESCRIPTION "4 pair categ. 3 UTP (per 802.3 section 23)"
duplex mode" ::= { dot3MauType 14 }
::= { dot3MauType 13 }
dot3MauType100BaseT4 OBJECT-IDENTITY dot3MauType100BaseTXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "4 pair categ. 3 UTP (per 802.3 section 23)" DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25),
::= { dot3MauType 14 } half duplex mode"
::= { dot3MauType 15 }
dot3MauType100BaseTXHD OBJECT-IDENTITY dot3MauType100BaseTXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25),
half duplex mode" full duplex mode"
::= { dot3MauType 15 } ::= { dot3MauType 16 }
dot3MauType100BaseTXFD OBJECT-IDENTITY dot3MauType100BaseFXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), DESCRIPTION "X fiber over PMT (per 802.3 section 26), half
full duplex mode" duplex mode"
::= { dot3MauType 16 } ::= { dot3MauType 17 }
dot3MauType100BaseFXFD OBJECT-IDENTITY
STATUS current
DESCRIPTION "X fiber over PMT (per 802.3 section 26), full
duplex mode"
::= { dot3MauType 18 }
dot3MauType100BaseFXHD OBJECT-IDENTITY dot3MauType100BaseT2HD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X fiber over PMT (per 802.3 section 26), half DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32),
duplex mode" half duplex mode"
::= { dot3MauType 17 } ::= { dot3MauType 19 }
dot3MauType100BaseFXFD OBJECT-IDENTITY dot3MauType100BaseT2FD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "X fiber over PMT (per 802.3 section 26), full DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32),
duplex mode" full duplex mode"
::= { dot3MauType 18 } ::= { dot3MauType 20 }
dot3MauType100BaseT2HD OBJECT-IDENTITY ------ new since RFC 2239:
STATUS current
DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32),
half duplex mode"
::= { dot3MauType 19 } dot3MauType1000BaseXHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD,
half duplex mode"
::= { dot3MauType 21 }
dot3MauType100BaseT2FD OBJECT-IDENTITY dot3MauType1000BaseXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32), DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD,
full duplex mode" full duplex mode"
::= { dot3MauType 20 } ::= { dot3MauType 22 }
------ new since RFC 2239: dot3MauType1000BaseLXHD OBJECT-IDENTITY
STATUS current
DESCRIPTION "Fiber over long-wavelength laser (per 802.3
section 38), half duplex mode"
::= { dot3MauType 23 }
dot3MauType1000BaseXHD OBJECT-IDENTITY dot3MauType1000BaseLXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, DESCRIPTION "Fiber over long-wavelength laser (per 802.3
half duplex mode" section 38), full duplex mode"
::= { dot3MauType 21 } ::= { dot3MauType 24 }
dot3MauType1000BaseXFD OBJECT-IDENTITY dot3MauType1000BaseSXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, DESCRIPTION "Fiber over short-wavelength laser (per 802.3
full duplex mode" section 38), half duplex mode"
::= { dot3MauType 22 } ::= { dot3MauType 25 }
dot3MauType1000BaseLXHD OBJECT-IDENTITY dot3MauType1000BaseSXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over long-wavelength laser (per 802.3 DESCRIPTION "Fiber over short-wavelength laser (per 802.3
section 38), half duplex mode" section 38), full duplex mode"
::= { dot3MauType 23 } ::= { dot3MauType 26 }
dot3MauType1000BaseLXFD OBJECT-IDENTITY dot3MauType1000BaseCXHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over long-wavelength laser (per 802.3 DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3
section 38), full duplex mode" section 39), half duplex mode"
::= { dot3MauType 24 } ::= { dot3MauType 27 }
dot3MauType1000BaseSXHD OBJECT-IDENTITY dot3MauType1000BaseCXFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over short-wavelength laser (per 802.3 DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3
section 38), half duplex mode" section 39), full duplex mode"
::= { dot3MauType 25 } ::= { dot3MauType 28 }
dot3MauType1000BaseSXFD OBJECT-IDENTITY dot3MauType1000BaseTHD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Fiber over short-wavelength laser (per 802.3 DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section
section 38), full duplex mode" 40), half duplex mode"
::= { dot3MauType 26 } ::= { dot3MauType 29 }
dot3MauType1000BaseCXHD OBJECT-IDENTITY dot3MauType1000BaseTFD OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section
section 39), half duplex mode" 40), full duplex mode"
::= { dot3MauType 27 } ::= { dot3MauType 30 }
dot3MauType1000BaseCXFD OBJECT-IDENTITY --
STATUS current -- The Basic Repeater MAU Table
DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 --
section 39), full duplex mode"
::= { dot3MauType 28 }
dot3MauType1000BaseTHD OBJECT-IDENTITY rpMauTable OBJECT-TYPE
STATUS current SYNTAX SEQUENCE OF RpMauEntry
DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section MAX-ACCESS not-accessible
40), half duplex mode" STATUS current
::= { dot3MauType 29 } DESCRIPTION "Table of descriptive and status information
about the MAU(s) attached to the ports of a
repeater."
::= { dot3RpMauBasicGroup 1 }
dot3MauType1000BaseTFD OBJECT-IDENTITY rpMauEntry OBJECT-TYPE
STATUS current SYNTAX RpMauEntry
DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section MAX-ACCESS not-accessible
40), full duplex mode" STATUS current
::= { dot3MauType 30 } DESCRIPTION "An entry in the table, containing information
about a single MAU."
INDEX { rpMauGroupIndex,
rpMauPortIndex,
rpMauIndex
}
::= { rpMauTable 1 }
-- RpMauEntry ::=
-- The Basic Repeater MAU Table SEQUENCE {
-- rpMauGroupIndex Integer32,
rpMauPortIndex Integer32,
rpMauIndex Integer32,
rpMauType OBJECT IDENTIFIER,
rpMauStatus INTEGER,
rpMauMediaAvailable INTEGER,
rpMauMediaAvailableStateExits Counter32,
rpMauJabberState INTEGER,
rpMauJabberingStateEnters Counter32,
rpMauFalseCarriers Counter32
}
rpMauTable OBJECT-TYPE rpMauGroupIndex OBJECT-TYPE
SYNTAX SEQUENCE OF RpMauEntry SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "Table of descriptive and status information DESCRIPTION "This variable uniquely identifies the group
about the MAU(s) attached to the ports of a containing the port to which the MAU described
repeater." by this entry is connected.
::= { dot3RpMauBasicGroup 1 }
rpMauEntry OBJECT-TYPE Note: In practice, a group will generally be
SYNTAX RpMauEntry a field-replaceable unit (i.e., module, card,
MAX-ACCESS not-accessible or board) that can fit in the physical system
STATUS current enclosure, and the group number will correspond
DESCRIPTION "An entry in the table, containing information to a number marked on the physical enclosure.
about a single MAU."
INDEX { rpMauGroupIndex,
rpMauPortIndex,
rpMauIndex
}
::= { rpMauTable 1 }
RpMauEntry ::= The group denoted by a particular value of this
SEQUENCE { object is the same as the group denoted by the
rpMauGroupIndex Integer32, same value of rptrGroupIndex."
rpMauPortIndex Integer32, REFERENCE "Reference RFC 2108, rptrGroupIndex."
rpMauIndex Integer32, ::= { rpMauEntry 1 }
rpMauType OBJECT IDENTIFIER,
rpMauStatus INTEGER,
rpMauMediaAvailable INTEGER,
rpMauMediaAvailableStateExits Counter32,
rpMauJabberState INTEGER,
rpMauJabberingStateEnters Counter32,
rpMauFalseCarriers Counter32
}
rpMauGroupIndex OBJECT-TYPE rpMauPortIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This variable uniquely identifies the group DESCRIPTION "This variable uniquely identifies the repeater
containing the port to which the MAU described port within group rpMauGroupIndex to which the
by this entry is connected. MAU described by this entry is connected."
REFERENCE "Reference RFC 2108, rptrPortIndex."
::= { rpMauEntry 2 }
Note: In practice, a group will generally be rpMauIndex OBJECT-TYPE
a field-replaceable unit (i.e., module, card, SYNTAX Integer32 (1..2147483647)
or board) that can fit in the physical system MAX-ACCESS read-only
enclosure, and the group number will correspond STATUS current
to a number marked on the physical enclosure. DESCRIPTION "This variable uniquely identifies the MAU
described by this entry from among other
MAUs connected to the same port
(rpMauPortIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 }
The group denoted by a particular value of this rpMauType OBJECT-TYPE
object is the same as the group denoted by the SYNTAX OBJECT IDENTIFIER
same value of rptrGroupIndex." MAX-ACCESS read-only
REFERENCE "Reference RFC 2108, rptrGroupIndex." STATUS current
::= { rpMauEntry 1 } DESCRIPTION "This object identifies the MAU type. An
initial set of MAU types are defined above. The
assignment of OBJECT IDENTIFIERs to new types of
MAUs is managed by the IANA. If the MAU type is
unknown, the object identifier
rpMauPortIndex OBJECT-TYPE unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This variable uniquely identifies the repeater
port within group rpMauGroupIndex to which the
MAU described by this entry is connected."
REFERENCE "Reference RFC 2108, rptrPortIndex."
::= { rpMauEntry 2 }
rpMauIndex OBJECT-TYPE is returned. Note that unknownMauType is a
SYNTAX Integer32 (1..2147483647) syntactically valid object identifier, and any
MAX-ACCESS read-only conformant implementation of ASN.1 and the BER
STATUS current must be able to generate and recognize this
DESCRIPTION "This variable uniquely identifies the MAU value."
described by this entry from among other REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
MAUs connected to the same port ::= { rpMauEntry 4 }
(rpMauPortIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 }
rpMauType OBJECT-TYPE rpMauStatus OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX INTEGER {
MAX-ACCESS read-only other(1),
STATUS current unknown(2),
DESCRIPTION "This object identifies the MAU type. An operational(3),
initial set of MAU types are defined above. The standby(4),
assignment of OBJECT IDENTIFIERs to new types of shutdown(5),
MAUs is managed by the IANA. If the MAU type is reset(6)
unknown, the object identifier }
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The current state of the MAU. This object MAY
be implemented as a read-only object by those
agents and MAUs that do not implement software
control of the MAU state. Some agents may not
support setting the value of this object to some
of the enumerated values.
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } The value other(1) is returned if the MAU is in
a state other than one of the states 2 through
6.
is returned. Note that unknownMauType is a The value unknown(2) is returned when the MAU's
syntactically valid object identifier, and any true state is unknown; for example, when it is
conformant implementation of ASN.1 and the BER being initialized.
must be able to generate and recognize this
value."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
::= { rpMauEntry 4 }
rpMauStatus OBJECT-TYPE A MAU in the operational(3) state is fully
SYNTAX INTEGER { functional, operates, and passes signals to its
other(1), attached DTE or repeater port in accordance to
unknown(2), its specification.
operational(3),
standby(4),
shutdown(5),
reset(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The current state of the MAU. This object MAY
be implemented as a read-only object by those
agents and MAUs that do not implement software
control of the MAU state. Some agents may not
support setting the value of this object to some
of the enumerated values.
The value other(1) is returned if the MAU is in A MAU in standby(4) state forces DI and CI to
a state other than one of the states 2 through idle and the media transmitter to idle or fault,
6. if supported. Standby(4) mode only applies to
link type MAUs. The state of
rpMauMediaAvailable is unaffected.
The value unknown(2) is returned when the MAU's A MAU in shutdown(5) state assumes the same
true state is unknown; for example, when it is condition on DI, CI, and the media transmitter
being initialized. as though it were powered down or not connected.
The MAU MAY return other(1) value for the
rpMauJabberState and rpMauMediaAvailable objects
when it is in this state. For an AUI, this
state will remove power from the AUI.
A MAU in the operational(3) state is fully Setting this variable to the value reset(6)
functional, operates, and passes signals to its resets the MAU in the same manner as a
attached DTE or repeater port in accordance to power-off, power-on cycle of at least one-half
its specification. second would. The agent is not required to
return the value reset (6).
A MAU in standby(4) state forces DI and CI to Setting this variable to the value
idle and the media transmitter to idle or fault, operational(3), standby(4), or shutdown(5)
if supported. Standby(4) mode only applies to causes the MAU to assume the respective state
link type MAUs. The state of except that setting a mixing-type MAU or an AUI
rpMauMediaAvailable is unaffected. to standby(4) will cause the MAU to enter the
shutdown state."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acResetMAU."
::= { rpMauEntry 5 }
A MAU in shutdown(5) state assumes the same rpMauMediaAvailable OBJECT-TYPE
condition on DI, CI, and the media transmitter SYNTAX INTEGER {
as though it were powered down or not connected. other(1),
The MAU MAY return other(1) value for the unknown(2),
rpMauJabberState and rpMauMediaAvailable objects available(3),
when it is in this state. For an AUI, this notAvailable(4),
state will remove power from the AUI. remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9),
offline(10),
autoNegError(11)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "If the MAU is a link or fiber type (FOIRL,
10BASE-T, 10BASE-F) then this is equivalent to
the link test fail state/low light function.
For an AUI or a coax (including broadband) MAU
this indicates whether or not loopback is
detected on the DI circuit. The value of this
attribute persists between packets for MAU types
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
Setting this variable to the value reset(6) The value other(1) is returned if the
resets the MAU in the same manner as a mediaAvailable state is not one of 2 through 11.
power-off, power-on cycle of at least one-half
second would. The agent is not required to
return the value reset (6).
Setting this variable to the value The value unknown(2) is returned when the MAU's
operational(3), standby(4), or shutdown(5) true state is unknown; for example, when it is
causes the MAU to assume the respective state being initialized. At power-up or following a
except that setting a mixing-type MAU or an AUI reset, the value of this attribute will be
to standby(4) will cause the MAU to enter the unknown for AUI, coax, and 10BASE-FP MAUs. For
shutdown state." these MAUs loopback will be tested on each
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, transmission during which no collision is
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, detected. If DI is receiving input when DO
acResetMAU." returns to IDL after a transmission and there
::= { rpMauEntry 5 } has been no collision during the transmission
then loopback will be detected. The value of
this attribute will only change during
non-collided transmissions for AUI, coax, and
10BASE-FP MAUs.
rpMauMediaAvailable OBJECT-TYPE For 100Mbps and 1000Mbps MAUs, the enumerations
SYNTAX INTEGER { match the states within the respective link
other(1), integrity state diagrams, fig 32-16, 23-12 and
unknown(2), 24-15 of sections 32, 23 and 24 of [16]. Any
available(3), MAU which implements management of
notAvailable(4), auto-negotiation will map remote fault
remoteFault(5), indication to remote fault.
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9),
offline(10),
autoNegError(11)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "If the MAU is a link or fiber type (FOIRL,
10BASE-T, 10BASE-F) then this is equivalent to
the link test fail state/low light function.
For an AUI or a coax (including broadband) MAU
this indicates whether or not loopback is
detected on the DI circuit. The value of this
attribute persists between packets for MAU types
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
The value other(1) is returned if the The value available(3) indicates that the link,
mediaAvailable state is not one of 2 through 6. light, or loopback is normal. The value
notAvailable(4) indicates link loss, low light,
or no loopback.
The value unknown(2) is returned when the MAU's The value remoteFault(5) indicates that a fault
true state is unknown; for example, when it is has been detected at the remote end of the link.
being initialized. At power-up or following a This value applies to 10BASE-FB, 100BASE-T4 Far
reset, the value of this attribute will be End Fault Indication and non-specified remote
unknown for AUI, coax, and 10BASE-FP MAUs. For faults from a system running auto-negotiation.
these MAUs loopback will be tested on each The values remoteJabber(7), remoteLinkLoss(8),
transmission during which no collision is and remoteTest(9) SHOULD be used instead of
detected. If DI is receiving input when DO remoteFault(5) where the reason for remote fault
returns to IDL after a transmission and there is identified in the remote signaling protocol.
has been no collision during the transmission
then loopback will be detected. The value of
this attribute will only change during
non-collided transmissions for AUI, coax, and
10BASE-FP MAUs.
For 100Mbps and 1000Mbps MAUs, the enumerations The value invalidSignal(6) indicates that an
match the states within the respective link invalid signal has been received from the other
integrity state diagrams, fig 32-16, 23-12 and end of the link. InvalidSignal(6) applies only
24-15 of sections 32, 23 and 24 of [2]. Any MAU to MAUs of type 10BASE-FB.
which implements management of auto-negotiation
will map remote fault indication to remote
fault.
The value available(3) indicates that the link, Where an IEEE Std 802.3u-1995 clause 22 MII
light, or loopback is normal. The value is present, a logic one in the remote fault bit
notAvailable(4) indicates link loss, low light, (reference section 22.2.4.2.8 of that document)
or no loopback. maps to the value remoteFault(5), and a logic
zero in the link status bit (reference section
22.2.4.2.10 of that document) maps to the value
notAvailable(4). The value notAvailable(4)
takes precedence over the value remoteFault(5).
The value remoteFault(5) indicates that a fault Any MAU that implements management of clause 37
has been detected at the remote end of the link. Auto-Negotiation will map the received Remote
This value applies to 10BASE-FB, 100BASE-T4 Far Fault (RF1 and RF2) bit values for Offline to
End Fault Indication and non-specified remote offline(10), Link Failure to remoteFault(5) and
faults from a system running auto-negotiation. Auto-Negotiation Error to autoNegError(11)."
The values remoteJabber(7), remoteLinkLoss(8),
and remoteTest(9) SHOULD be used instead of
remoteFault(5) where the reason for remote fault
is identified in the remote signaling protocol.
The value invalidSignal(6) indicates that an REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable."
invalid signal has been received from the other ::= { rpMauEntry 6 }
end of the link. InvalidSignal(6) applies only
to MAUs of type 10BASE-FB.
Where an IEEE Std 802.3u-1995 clause 22 MII rpMauMediaAvailableStateExits OBJECT-TYPE
is present, a logic one in the remote fault bit SYNTAX Counter32
(reference section 22.2.4.2.8 of that document) MAX-ACCESS read-only
maps to the value remoteFault(5), and a logic STATUS current
zero in the link status bit (reference section DESCRIPTION "A count of the number of times that
22.2.4.2.10 of that document) maps to the value rpMauMediaAvailable for this MAU instance leaves
notAvailable(4). The value notAvailable(4) the state available(3).
takes precedence over the value remoteFault(5).
Any MAU that implements management of clause 37 Discontinuities in the value of this counter can
Auto-Negotiation will map the received Remote occur at re-initialization of the management
Fault (RF1 and RF2) bit values for Offline to system, and at other times as indicated by the
offline(10), Link Failure to remoteFault(5) and value of rptrMonitorPortLastChange."
Auto-Negotiation Error to autoNegError(11)." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5,
aLoseMediaCounter.
RFC 2108, rptrMonitorPortLastChange"
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." ::= { rpMauEntry 7 }
::= { rpMauEntry 6 }
rpMauMediaAvailableStateExits OBJECT-TYPE rpMauJabberState OBJECT-TYPE
SYNTAX Counter32 SYNTAX INTEGER {
MAX-ACCESS read-only other(1),
STATUS current unknown(2),
DESCRIPTION "A count of the number of times that noJabber(3),
rpMauMediaAvailable for this MAU instance leaves jabbering(4)
the state available(3)." }
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, MAX-ACCESS read-only
aLoseMediaCounter." STATUS current
::= { rpMauEntry 7 } DESCRIPTION "The value other(1) is returned if the jabber
state is not 2, 3, or 4. The agent MUST always
return other(1) for MAU type dot3MauTypeAUI.
rpMauJabberState OBJECT-TYPE The value unknown(2) is returned when the MAU's
SYNTAX INTEGER { true state is unknown; for example, when it is
other(1), being initialized.
unknown(2),
noJabber(3),
jabbering(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The value other(1) is returned if the jabber
state is not 2, 3, or 4. The agent MUST always
return other(1) for MAU type dot3MauTypeAUI.
The value unknown(2) is returned when the MAU's If the MAU is not jabbering the agent returns
true state is unknown; for example, when it is noJabber(3). This is the 'normal' state.
being initialized.
If the MAU is not jabbering the agent returns If the MAU is in jabber state the agent returns
noJabber(3). This is the 'normal' state. the jabbering(4) value."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberFlag."
::= { rpMauEntry 8 }
If the MAU is in jabber state the agent returns rpMauJabberingStateEnters OBJECT-TYPE
the jabbering(4) value." SYNTAX Counter32
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, MAX-ACCESS read-only
aJabber.jabberFlag." STATUS current
::= { rpMauEntry 8 } DESCRIPTION "A count of the number of times that
mauJabberState for this MAU instance enters the
state jabbering(4). For MAUs of type
dot3MauTypeAUI, dot3MauType100BaseT4,
dot3MauType100BaseTX, dot3MauType100BaseFX and
all 1000Mbps types, this counter will always
indicate zero.
rpMauJabberingStateEnters OBJECT-TYPE Discontinuities in the value of this counter
SYNTAX Counter32 can occur at re-initialization of the
MAX-ACCESS read-only management system, and at other times as
STATUS current indicated by the value of
DESCRIPTION "A count of the number of times that rptrMonitorPortLastChange."
mauJabberState for this MAU instance enters the REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
state jabbering(4). For MAUs of type aJabber.jabberCounter.
dot3MauTypeAUI, dot3MauType100BaseT4, RFC 2108, rptrMonitorPortLastChange"
dot3MauType100BaseTX, dot3MauType100BaseFX and
all 1000Mbps types, this counter will always
indicate zero."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberCounter."
::= { rpMauEntry 9 }
rpMauFalseCarriers OBJECT-TYPE ::= { rpMauEntry 9 }
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of false carrier events
during IDLE in 100BASE-X links. This counter
does not increment at the symbol rate. It can
increment after a valid carrier completion at a
maximum rate of once per 100 ms until the next
carrier event.
This counter increments only for MAUs of type rpMauFalseCarriers OBJECT-TYPE
dot3MauType100BaseT4, dot3MauType100BaseTX, and SYNTAX Counter32
dot3MauType100BaseFX and all 1000Mbps types. MAX-ACCESS read-only
For all other MAU types, this counter will STATUS current
always indicate zero. DESCRIPTION "A count of the number of false carrier events
during IDLE in 100BASE-X links. This counter
does not increment at the symbol rate. It can
increment after a valid carrier completion at a
maximum rate of once per 100 ms until the next
carrier event.
The approximate minimum time for rollover of This counter increments only for MAUs of type
this counter is 7.4 hours." dot3MauType100BaseT4, dot3MauType100BaseTX, and
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers." dot3MauType100BaseFX and all 1000Mbps types.
::= { rpMauEntry 10 } For all other MAU types, this counter will
always indicate zero.
-- The rpJackTable applies to MAUs attached to repeaters The approximate minimum time for rollover of
-- which have one or more external jacks (connectors). this counter is 7.4 hours.
rpJackTable OBJECT-TYPE Discontinuities in the value of this counter can
SYNTAX SEQUENCE OF RpJackEntry occur at re-initialization of the management
MAX-ACCESS not-accessible system, and at other times as indicated by the
STATUS current value of rptrMonitorPortLastChange."
DESCRIPTION "Information about the external jacks attached REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers.
to MAUs attached to the ports of a repeater." RFC 2108, rptrMonitorPortLastChange"
::= { dot3RpMauBasicGroup 2 } ::= { rpMauEntry 10 }
rpJackEntry OBJECT-TYPE -- The rpJackTable applies to MAUs attached to repeaters
SYNTAX RpJackEntry -- which have one or more external jacks (connectors).
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "An entry in the table, containing information
about a particular jack."
INDEX { rpMauGroupIndex,
rpMauPortIndex,
rpMauIndex,
rpJackIndex
}
::= { rpJackTable 1 }
RpJackEntry ::= rpJackTable OBJECT-TYPE
SEQUENCE { SYNTAX SEQUENCE OF RpJackEntry
rpJackIndex Integer32, MAX-ACCESS not-accessible
rpJackType JackType STATUS current
} DESCRIPTION "Information about the external jacks attached
to MAUs attached to the ports of a repeater."
::= { dot3RpMauBasicGroup 2 }
rpJackIndex OBJECT-TYPE rpJackEntry OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX RpJackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "This variable uniquely identifies the jack DESCRIPTION "An entry in the table, containing information
described by this entry from among other jacks about a particular jack."
attached to the same MAU (rpMauIndex)." INDEX { rpMauGroupIndex,
::= { rpJackEntry 1 } rpMauPortIndex,
rpMauIndex,
rpJackIndex
}
::= { rpJackTable 1 }
rpJackType OBJECT-TYPE RpJackEntry ::=
SYNTAX JackType SEQUENCE {
MAX-ACCESS read-only rpJackIndex Integer32,
STATUS current rpJackType JackType
DESCRIPTION "The jack connector type, as it appears on the }
outside of the system."
::= { rpJackEntry 2 }
-- rpJackIndex OBJECT-TYPE
-- The Basic Interface MAU Table SYNTAX Integer32 (1..2147483647)
-- MAX-ACCESS not-accessible
STATUS current
DESCRIPTION "This variable uniquely identifies the jack
described by this entry from among other jacks
attached to the same MAU (rpMauIndex)."
::= { rpJackEntry 1 }
ifMauTable OBJECT-TYPE rpJackType OBJECT-TYPE
SYNTAX SEQUENCE OF IfMauEntry SYNTAX JackType
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "Table of descriptive and status information DESCRIPTION "The jack connector type, as it appears on the
about MAU(s) attached to an interface." outside of the system."
::= { dot3IfMauBasicGroup 1 } ::= { rpJackEntry 2 }
ifMauEntry OBJECT-TYPE --
SYNTAX IfMauEntry -- The Basic Interface MAU Table
MAX-ACCESS not-accessible --
STATUS current
DESCRIPTION "An entry in the table, containing information
about a single MAU."
INDEX { ifMauIfIndex,
ifMauIndex
}
::= { ifMauTable 1 }
IfMauEntry ::= ifMauTable OBJECT-TYPE
SEQUENCE { SYNTAX SEQUENCE OF IfMauEntry
ifMauIfIndex Integer32, MAX-ACCESS not-accessible
ifMauIndex Integer32, STATUS current
ifMauType OBJECT IDENTIFIER, DESCRIPTION "Table of descriptive and status information
ifMauStatus INTEGER, about MAU(s) attached to an interface."
ifMauMediaAvailable INTEGER, ::= { dot3IfMauBasicGroup 1 }
ifMauMediaAvailableStateExits Counter32,
ifMauJabberState INTEGER,
ifMauJabberingStateEnters Counter32,
ifMauFalseCarriers Counter32,
ifMauTypeList Integer32,
ifMauDefaultType OBJECT IDENTIFIER,
ifMauAutoNegSupported TruthValue,
ifMauTypeListBits BITS
}
ifMauIfIndex OBJECT-TYPE ifMauEntry OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX IfMauEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "This variable uniquely identifies the interface DESCRIPTION "An entry in the table, containing information
to which the MAU described by this entry is about a single MAU."
connected." INDEX { ifMauIfIndex,
REFERENCE "RFC 1213, ifIndex" ifMauIndex
::= { ifMauEntry 1 } }
::= { ifMauTable 1 }
ifMauIndex OBJECT-TYPE IfMauEntry ::=
SYNTAX Integer32 (1..2147483647) SEQUENCE {
MAX-ACCESS read-only ifMauIfIndex Integer32,
STATUS current ifMauIndex Integer32,
DESCRIPTION "This variable uniquely identifies the MAU ifMauType OBJECT IDENTIFIER,
described by this entry from among other MAUs ifMauStatus INTEGER,
connected to the same interface (ifMauIfIndex)." ifMauMediaAvailable INTEGER,
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." ifMauMediaAvailableStateExits Counter32,
::= { ifMauEntry 2 } ifMauJabberState INTEGER,
ifMauJabberingStateEnters Counter32,
ifMauFalseCarriers Counter32,
ifMauTypeList Integer32,
ifMauDefaultType OBJECT IDENTIFIER,
ifMauAutoNegSupported TruthValue,
ifMauTypeListBits BITS
}
ifMauType OBJECT-TYPE ifMauIfIndex OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "This object identifies the 10 or 100 Mb/s DESCRIPTION "This variable uniquely identifies the interface
baseband or broadband MAU type. An initial set to which the MAU described by this entry is
of MAU types are defined above. The assignment connected."
of OBJECT IDENTIFIERs to new types of MAUs is REFERENCE "RFC 1213, ifIndex"
managed by the IANA. If the MAU type is ::= { ifMauEntry 1 }
unknown, the object identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } ifMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION "This variable uniquely identifies the MAU
described by this entry from among other MAUs
connected to the same interface (ifMauIfIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { ifMauEntry 2 }
is returned. Note that unknownMauType is a ifMauType OBJECT-TYPE
syntactically valid object identifier, and any SYNTAX OBJECT IDENTIFIER
conformant implementation of ASN.1 and the BER MAX-ACCESS read-only
must be able to generate and recognize this STATUS current
value. DESCRIPTION "This object identifies the MAU type. An
initial set of MAU types are defined above. The
assignment of OBJECT IDENTIFIERs to new types of
MAUs is managed by the IANA. If the MAU type is
unknown, the object identifier
This object represents the operational type of unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
the MAU, as determined by either (1) the result
of the auto-negotiation function or (2) if
auto-negotiation is not enabled or is not
implemented for this MAU, by the value of the
object ifMauDefaultType. In case (2), a set to
the object ifMauDefaultType will force the MAU
into the new operating mode."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
::= { ifMauEntry 3 }
ifMauStatus OBJECT-TYPE is returned. Note that unknownMauType is a
SYNTAX INTEGER { syntactically valid object identifier, and any
other(1), conformant implementation of ASN.1 and the BER
unknown(2), must be able to generate and recognize this
operational(3), value.
standby(4),
shutdown(5),
reset(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The current state of the MAU. This object MAY
be implemented as a read-only object by those
agents and MAUs that do not implement software
control of the MAU state. Some agents may not
support setting the value of this object to some
of the enumerated values.
The value other(1) is returned if the MAU is in This object represents the operational type of
a state other than one of the states 2 through the MAU, as determined by either (1) the result
6. of the auto-negotiation function or (2) if
auto-negotiation is not enabled or is not
implemented for this MAU, by the value of the
object ifMauDefaultType. In case (2), a set to
the object ifMauDefaultType will force the MAU
into the new operating mode."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
::= { ifMauEntry 3 }
The value unknown(2) is returned when the MAU's ifMauStatus OBJECT-TYPE
true state is unknown; for example, when it is SYNTAX INTEGER {
being initialized. other(1),
unknown(2),
operational(3),
standby(4),
shutdown(5),
reset(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "The current state of the MAU. This object MAY
be implemented as a read-only object by those
agents and MAUs that do not implement software
control of the MAU state. Some agents may not
support setting the value of this object to some
of the enumerated values.
A MAU in the operational(3) state is fully The value other(1) is returned if the MAU is in
functional, operates, and passes signals to its a state other than one of the states 2 through
attached DTE or repeater port in accordance to 6.
its specification.
A MAU in standby(4) state forces DI and CI to The value unknown(2) is returned when the MAU's
idle and the media transmitter to idle or fault, true state is unknown; for example, when it is
if supported. Standby(4) mode only applies to being initialized.
link type MAUs. The state of
ifMauMediaAvailable is unaffected.
A MAU in shutdown(5) state assumes the same A MAU in the operational(3) state is fully
condition on DI, CI, and the media transmitter functional, operates, and passes signals to its
as though it were powered down or not connected. attached DTE or repeater port in accordance to
The MAU MAY return other(1) value for the its specification.
ifMauJabberState and ifMauMediaAvailable objects
when it is in this state. For an AUI, this
state will remove power from the AUI.
Setting this variable to the value reset(6) A MAU in standby(4) state forces DI and CI to
resets the MAU in the same manner as a idle and the media transmitter to idle or fault,
power-off, power-on cycle of at least one-half if supported. Standby(4) mode only applies to
second would. The agent is not required to link type MAUs. The state of
return the value reset (6). ifMauMediaAvailable is unaffected.
Setting this variable to the value A MAU in shutdown(5) state assumes the same
operational(3), standby(4), or shutdown(5) condition on DI, CI, and the media transmitter
causes the MAU to assume the respective state as though it were powered down or not connected.
except that setting a mixing-type MAU or an AUI The MAU MAY return other(1) value for the
to standby(4) will cause the MAU to enter the ifMauJabberState and ifMauMediaAvailable objects
shutdown state." when it is in this state. For an AUI, this
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, state will remove power from the AUI.
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acResetMAU."
::= { ifMauEntry 4 }
ifMauMediaAvailable OBJECT-TYPE Setting this variable to the value reset(6)
SYNTAX INTEGER { resets the MAU in the same manner as a
other(1), power-off, power-on cycle of at least one-half
unknown(2), second would. The agent is not required to
available(3), return the value reset (6).
notAvailable(4),
remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9),
offline(10),
autoNegError(11)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "If the MAU is a link or fiber type (FOIRL,
10BASE-T, 10BASE-F) then this is equivalent to
the link test fail state/low light function.
For an AUI or a coax (including broadband) MAU
this indicates whether or not loopback is
detected on the DI circuit. The value of this
attribute persists between packets for MAU types
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
The value other(1) is returned if the Setting this variable to the value
mediaAvailable state is not one of 2 through 6. operational(3), standby(4), or shutdown(5)
causes the MAU to assume the respective state
except that setting a mixing-type MAU or an AUI
to standby(4) will cause the MAU to enter the
shutdown state."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acResetMAU."
::= { ifMauEntry 4 }
ifMauMediaAvailable OBJECT-TYPE
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9),
offline(10),
autoNegError(11)
The value unknown(2) is returned when the MAU's }
true state is unknown; for example, when it is MAX-ACCESS read-only
being initialized. At power-up or following a STATUS current
reset, the value of this attribute will be DESCRIPTION "If the MAU is a link or fiber type (FOIRL,
unknown for AUI, coax, and 10BASE-FP MAUs. For 10BASE-T, 10BASE-F) then this is equivalent to
these MAUs loopback will be tested on each the link test fail state/low light function.
transmission during which no collision is For an AUI or a coax (including broadband) MAU
detected. If DI is receiving input when DO this indicates whether or not loopback is
returns to IDL after a transmission and there detected on the DI circuit. The value of this
has been no collision during the transmission attribute persists between packets for MAU types
then loopback will be detected. The value of AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
this attribute will only change during
non-collided transmissions for AUI, coax, and
10BASE-FP MAUs.
For 100Mbps and 1000Mbps MAUs, the enumerations The value other(1) is returned if the
match the states within the respective link mediaAvailable state is not one of 2 through 11.
integrity state diagrams, fig 32-16, 23-12 and
24-15 of sections 32, 23 and 24 of [2]. Any MAU
which implements management of auto-negotiation
will map remote fault indication to remote
fault.
The value available(3) indicates that the link, The value unknown(2) is returned when the MAU's
light, or loopback is normal. The value true state is unknown; for example, when it is
notAvailable(4) indicates link loss, low light, being initialized. At power-up or following a
or no loopback. reset, the value of this attribute will be
unknown for AUI, coax, and 10BASE-FP MAUs. For
these MAUs loopback will be tested on each
transmission during which no collision is
detected. If DI is receiving input when DO
returns to IDL after a transmission and there
has been no collision during the transmission
then loopback will be detected. The value of
this attribute will only change during
non-collided transmissions for AUI, coax, and
10BASE-FP MAUs.
The value remoteFault(5) indicates that a fault For 100Mbps and 1000Mbps MAUs, the enumerations
has been detected at the remote end of the link. match the states within the respective link
This value applies to 10BASE-FB, 100BASE-T4 Far integrity state diagrams, fig 32-16, 23-12 and
End Fault Indication and non-specified remote 24-15 of sections 32, 23 and 24 of [16]. Any
faults from a system running auto-negotiation. MAU which implements management of
The values remoteJabber(7), remoteLinkLoss(8), auto-negotiation will map remote fault
and remoteTest(9) SHOULD be used instead of indication to remote fault.
remoteFault(5) where the reason for remote fault
is identified in the remote signaling protocol.
The value invalidSignal(6) indicates that an The value available(3) indicates that the link,
invalid signal has been received from the other light, or loopback is normal. The value
end of the link. InvalidSignal(6) applies only notAvailable(4) indicates link loss, low light,
to MAUs of type 10BASE-FB. or no loopback.
Where an IEEE Std 802.3u-1995 clause 22 MII The value remoteFault(5) indicates that a fault
is present, a logic one in the remote fault bit has been detected at the remote end of the link.
(reference section 22.2.4.2.8 of that document) This value applies to 10BASE-FB, 100BASE-T4 Far
maps to the value remoteFault(5), and a logic End Fault Indication and non-specified remote
zero in the link status bit (reference section faults from a system running auto-negotiation.
22.2.4.2.10 of that document) maps to the value
notAvailable(4). The value notAvailable(4)
takes precedence over the value remoteFault(5).
Any MAU that implements management of clause 37 The values remoteJabber(7), remoteLinkLoss(8),
Auto-Negotiation will map the received RF1 and and remoteTest(9) SHOULD be used instead of
RF2 bit values for Offline to offline(10), Link remoteFault(5) where the reason for remote fault
Failure to remoteFault(5) and Auto-Negotiation is identified in the remote signaling protocol.
Error to autoNegError(11)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable."
::= { ifMauEntry 5 }
ifMauMediaAvailableStateExits OBJECT-TYPE The value invalidSignal(6) indicates that an
SYNTAX Counter32 invalid signal has been received from the other
MAX-ACCESS read-only end of the link. InvalidSignal(6) applies only
STATUS current to MAUs of type 10BASE-FB.
DESCRIPTION "A count of the number of times that
ifMauMediaAvailable for this MAU instance leaves
the state available(3)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5,
aLoseMediaCounter."
::= { ifMauEntry 6 }
ifMauJabberState OBJECT-TYPE Where an IEEE Std 802.3u-1995 clause 22 MII
SYNTAX INTEGER { is present, a logic one in the remote fault bit
other(1), (reference section 22.2.4.2.8 of that document)
unknown(2), maps to the value remoteFault(5), and a logic
noJabber(3), zero in the link status bit (reference section
jabbering(4) 22.2.4.2.10 of that document) maps to the value
} notAvailable(4). The value notAvailable(4)
MAX-ACCESS read-only takes precedence over the value remoteFault(5).
STATUS current
DESCRIPTION "The value other(1) is returned if the jabber
state is not 2, 3, or 4. The agent MUST always
return other(1) for MAU type dot3MauTypeAUI.
The value unknown(2) is returned when the MAU's Any MAU that implements management of clause 37
true state is unknown; for example, when it is Auto-Negotiation will map the received RF1 and
being initialized. RF2 bit values for Offline to offline(10), Link
Failure to remoteFault(5) and Auto-Negotiation
Error to autoNegError(11)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable."
::= { ifMauEntry 5 }
If the MAU is not jabbering the agent returns ifMauMediaAvailableStateExits OBJECT-TYPE
noJabber(3). This is the 'normal' state. SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of times that
ifMauMediaAvailable for this MAU instance leaves
the state available(3).
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5,
aLoseMediaCounter.
RFC 2233, ifCounterDiscontinuityTime."
::= { ifMauEntry 6 }
If the MAU is in jabber state the agent returns ifMauJabberState OBJECT-TYPE
the jabbering(4) value." SYNTAX INTEGER {
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, other(1),
aJabber.jabberFlag." unknown(2),
::= { ifMauEntry 7 } noJabber(3),
jabbering(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "The value other(1) is returned if the jabber
state is not 2, 3, or 4. The agent MUST always
return other(1) for MAU type dot3MauTypeAUI.
ifMauJabberingStateEnters OBJECT-TYPE The value unknown(2) is returned when the MAU's
SYNTAX Counter32 true state is unknown; for example, when it is
MAX-ACCESS read-only being initialized.
STATUS current
DESCRIPTION "A count of the number of times that
mauJabberState for this MAU instance enters the
state jabbering(4). This counter will always
indicate zero for MAUs of type dot1MauTypeAUI
and those of speeds above 10Mbps."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberCounter."
::= { ifMauEntry 8 }
ifMauFalseCarriers OBJECT-TYPE If the MAU is not jabbering the agent returns
SYNTAX Counter32 noJabber(3). This is the 'normal' state.
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A count of the number of false carrier events
during IDLE in 100BASE-X and 1000BASE-X links.
For all other MAU types, this counter will If the MAU is in jabber state the agent returns
always indicate zero. This counter does not the jabbering(4) value."
increment at the symbol rate. REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberFlag."
::= { ifMauEntry 7 }
It can increment after a valid carrier ifMauJabberingStateEnters OBJECT-TYPE
completion at a maximum rate of once per 100 ms SYNTAX Counter32
for 100BASE-X and once per 10us for 1000BASE-X MAX-ACCESS read-only
until the next CarrierEvent." STATUS current
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers." DESCRIPTION "A count of the number of times that
::= { ifMauEntry 9 } mauJabberState for this MAU instance enters the
state jabbering(4). This counter will always
indicate zero for MAUs of type dot1MauTypeAUI
and those of speeds above 10Mbps.
ifMauTypeList OBJECT-TYPE Discontinuities in the value of this counter can
SYNTAX Integer32 occur at re-initialization of the management
MAX-ACCESS read-only system, and at other times as indicated by the
STATUS deprecated value of ifCounterDiscontinuityTime."
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberCounter.
RFC 2233, ifCounterDiscontinuityTime."
::= { ifMauEntry 8 }
A value that uniquely identifies the set of ifMauFalseCarriers OBJECT-TYPE
possible IEEE 802.3 types that the MAU could be. SYNTAX Counter32
The value is a sum which initially takes the MAX-ACCESS read-only
value zero. Then, for each type capability of STATUS current
this MAU, 2 raised to the power noted below is DESCRIPTION "A count of the number of false carrier events
added to the sum. For example, a MAU which has during IDLE in 100BASE-X and 1000BASE-X links.
the capability to be only 10BASE-T would have a
value of 512 (2**9). In contrast, a MAU which
supports both 10Base-T (full duplex) and
100BASE-TX (full duplex) would have a value of
((2**11) + (2**16)) or 67584.
The powers of 2 assigned to the capabilities are For all other MAU types, this counter will
these: always indicate zero. This counter does not
increment at the symbol rate.
Power Capability It can increment after a valid carrier
0 other or unknown completion at a maximum rate of once per 100 ms
1 AUI for 100BASE-X and once per 10us for 1000BASE-X
2 10BASE-5 until the next CarrierEvent.
3 FOIRL
4 10BASE-2
5 10BASE-T duplex mode unknown
6 10BASE-FP
7 10BASE-FB
8 10BASE-FL duplex mode unknown
9 10BROAD36
10 10BASE-T half duplex mode
11 10BASE-T full duplex mode
12 10BASE-FL half duplex mode
13 10BASE-FL full duplex mode
14 100BASE-T4
15 100BASE-TX half duplex mode
16 100BASE-TX full duplex mode
17 100BASE-FX half duplex mode
18 100BASE-FX full duplex mode
19 100BASE-T2 half duplex mode
20 100BASE-T2 full duplex mode
If auto-negotiation is present on this MAU, this Discontinuities in the value of this counter can
object will map to ifMauAutoNegCapability. occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers.
RFC 2233, ifCounterDiscontinuityTime."
::= { ifMauEntry 9 }
This object has been deprecated in favour of ifMauTypeList OBJECT-TYPE
ifMauTypeListBits." SYNTAX Integer32
::= { ifMauEntry 10 } MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
ifMauDefaultType OBJECT-TYPE A value that uniquely identifies the set of
SYNTAX OBJECT IDENTIFIER possible IEEE 802.3 types that the MAU could be.
MAX-ACCESS read-write The value is a sum which initially takes the
STATUS current value zero. Then, for each type capability of
DESCRIPTION "This object identifies the default this MAU, 2 raised to the power noted below is
administrative baseband MAU type, to be used in added to the sum. For example, a MAU which has
conjunction with the operational MAU type the capability to be only 10BASE-T would have a
denoted by ifMauType. value of 512 (2**9). In contrast, a MAU which
supports both 10Base-T (full duplex) and
100BASE-TX (full duplex) would have a value of
((2**11) + (2**16)) or 67584.
The set of possible values for this object is The powers of 2 assigned to the capabilities are
the same as the set defined for the ifMauType these:
object.
This object represents the Power Capability
administratively-configured type of the MAU. If 0 other or unknown
auto-negotiation is not enabled or is not 1 AUI
implemented for this MAU, the value of this 2 10BASE-5
object determines the operational type of the 3 FOIRL
MAU. In this case, a set to this object will 4 10BASE-2
force the MAU into the specified operating mode. 5 10BASE-T duplex mode unknown
6 10BASE-FP
7 10BASE-FB
8 10BASE-FL duplex mode unknown
9 10BROAD36
If auto-negotiation is implemented and enabled 10 10BASE-T half duplex mode
for this MAU, the operational type of the MAU 11 10BASE-T full duplex mode
is determined by auto-negotiation, and the value 12 10BASE-FL half duplex mode
of this object denotes the type to which the MAU 13 10BASE-FL full duplex mode
will automatically revert if/when 14 100BASE-T4
auto-negotiation is later disabled. 15 100BASE-TX half duplex mode
16 100BASE-TX full duplex mode
17 100BASE-FX half duplex mode
18 100BASE-FX full duplex mode
19 100BASE-T2 half duplex mode
20 100BASE-T2 full duplex mode
NOTE TO IMPLEMENTORS: It may be necessary to If auto-negotiation is present on this MAU, this
provide for underlying hardware implementations object will map to ifMauAutoNegCapability.
which do not follow the exact behavior specified
above. In particular, when
ifMauAutoNegAdminStatus transitions from enabled
to disabled, the agent implementation MUST
ensure that the operational type of the MAU (as
reported by ifMauType) correctly transitions to
the value specified by this object, rather than
continuing to operate at the value earlier
determined by the auto-negotiation function."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID, and
22.2.4.1.4."
::= { ifMauEntry 11 }
ifMauAutoNegSupported OBJECT-TYPE This object has been deprecated in favour of
SYNTAX TruthValue ifMauTypeListBits."
MAX-ACCESS read-only ::= { ifMauEntry 10 }
STATUS current
DESCRIPTION "This object indicates whether or not
auto-negotiation is supported on this MAU."
::= { ifMauEntry 12 }
ifMauTypeListBits OBJECT-TYPE ifMauDefaultType OBJECT-TYPE
SYNTAX BITS { SYNTAX OBJECT IDENTIFIER
bOther(0), -- other or unknown MAX-ACCESS read-write
bAUI(1), -- AUI STATUS current
b10base5(2), -- 10BASE-5 DESCRIPTION "This object identifies the default
bFoirl(3), -- FOIRL administrative baseband MAU type, to be used in
conjunction with the operational MAU type
denoted by ifMauType.
b10base2(4), -- 10BASE-2 The set of possible values for this object is
b10baseT(5), -- 10BASE-T duplex mode unknown the same as the set defined for the ifMauType
b10baseFP(6), -- 10BASE-FP object.
b10baseFB(7), -- 10BASE-FB
b10baseFL(8), -- 10BASE-FL duplex mode unknown
b10broad36(9), -- 10BROAD36
b10baseTHD(10), -- 10BASE-T half duplex mode
b10baseTFD(11), -- 10BASE-T full duplex mode
b10baseFLHD(12), -- 10BASE-FL half duplex mode
b10baseFLFD(13), -- 10BASE-FL full duplex mode
b100baseT4(14), -- 100BASE-T4 This object represents the
b100baseTXHD(15), -- 100BASE-TX half duplex mode administratively-configured type of the MAU. If
b100baseTXFD(16), -- 100BASE-TX full duplex mode auto-negotiation is not enabled or is not
b100baseFXHD(17), -- 100BASE-FX half duplex mode implemented for this MAU, the value of this
b100baseFXFD(18), -- 100BASE-FX full duplex mode object determines the operational type of the
b100baseT2HD(19), -- 100BASE-T2 half duplex mode MAU. In this case, a set to this object will
b100baseT2FD(20), -- 100BASE-T2 full duplex mode force the MAU into the specified operating mode.
b1000baseXHD(21), -- 1000BASE-X half duplex mode If auto-negotiation is implemented and enabled
b1000baseXFD(22), -- 1000BASE-X full duplex mode for this MAU, the operational type of the MAU
b1000baseLXHD(23), -- 1000BASE-LX half duplex mode is determined by auto-negotiation, and the value
b1000baseLXFD(24), -- 1000BASE-LX full duplex mode of this object denotes the type to which the MAU
b1000baseSXHD(25), -- 1000BASE-SX half duplex mode will automatically revert if/when
b1000baseSXFD(26), -- 1000BASE-SX full duplex mode auto-negotiation is later disabled.
b1000baseCXHD(27), -- 1000BASE-CX half duplex mode
b1000baseCXFD(28), -- 1000BASE-CX full duplex mode
b1000baseTHD(29), -- 1000BASE-T half duplex mode
b1000baseTFD(30) -- 1000BASE-T full duplex mode
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A value that uniquely identifies the set of
possible IEEE 802.3 types that the MAU could be.
If auto-negotiation is present on this MAU, this
object will map to ifMauAutoNegCapability."
::= { ifMauEntry 13 }
-- The ifJackTable applies to MAUs attached to interfaces NOTE TO IMPLEMENTORS: It may be necessary to
-- which have one or more external jacks (connectors). provide for underlying hardware implementations
which do not follow the exact behavior specified
above. In particular, when
ifMauAutoNegAdminStatus transitions from enabled
to disabled, the agent implementation MUST
ensure that the operational type of the MAU (as
reported by ifMauType) correctly transitions to
the value specified by this object, rather than
continuing to operate at the value earlier
determined by the auto-negotiation function."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID, and
22.2.4.1.4."
::= { ifMauEntry 11 }
ifJackTable OBJECT-TYPE ifMauAutoNegSupported OBJECT-TYPE
SYNTAX SEQUENCE OF IfJackEntry SYNTAX TruthValue
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "Information about the external jacks attached DESCRIPTION "This object indicates whether or not
to MAUs attached to an interface." auto-negotiation is supported on this MAU."
::= { dot3IfMauBasicGroup 2 } ::= { ifMauEntry 12 }
ifJackEntry OBJECT-TYPE ifMauTypeListBits OBJECT-TYPE
SYNTAX IfJackEntry SYNTAX BITS {
MAX-ACCESS not-accessible bOther(0), -- other or unknown
STATUS current bAUI(1), -- AUI
DESCRIPTION "An entry in the table, containing information b10base5(2), -- 10BASE-5
about a particular jack." bFoirl(3), -- FOIRL
INDEX { ifMauIfIndex,
ifMauIndex,
ifJackIndex
}
::= { ifJackTable 1 }
IfJackEntry ::= b10base2(4), -- 10BASE-2
SEQUENCE { b10baseT(5), -- 10BASE-T duplex mode unknown
ifJackIndex Integer32, b10baseFP(6), -- 10BASE-FP
ifJackType JackType b10baseFB(7), -- 10BASE-FB
} b10baseFL(8), -- 10BASE-FL duplex mode unknown
b10broad36(9), -- 10BROAD36
b10baseTHD(10), -- 10BASE-T half duplex mode
b10baseTFD(11), -- 10BASE-T full duplex mode
b10baseFLHD(12), -- 10BASE-FL half duplex mode
b10baseFLFD(13), -- 10BASE-FL full duplex mode
ifJackIndex OBJECT-TYPE b100baseT4(14), -- 100BASE-T4
SYNTAX Integer32 (1..2147483647) b100baseTXHD(15), -- 100BASE-TX half duplex mode
MAX-ACCESS not-accessible b100baseTXFD(16), -- 100BASE-TX full duplex mode
STATUS current b100baseFXHD(17), -- 100BASE-FX half duplex mode
DESCRIPTION "This variable uniquely identifies the jack b100baseFXFD(18), -- 100BASE-FX full duplex mode
described by this entry from among other jacks b100baseT2HD(19), -- 100BASE-T2 half duplex mode
attached to the same MAU." b100baseT2FD(20), -- 100BASE-T2 full duplex mode
::= { ifJackEntry 1 } b1000baseXHD(21), -- 1000BASE-X half duplex mode
b1000baseXFD(22), -- 1000BASE-X full duplex mode
b1000baseLXHD(23), -- 1000BASE-LX half duplex mode
b1000baseLXFD(24), -- 1000BASE-LX full duplex mode
b1000baseSXHD(25), -- 1000BASE-SX half duplex mode
b1000baseSXFD(26), -- 1000BASE-SX full duplex mode
b1000baseCXHD(27), -- 1000BASE-CX half duplex mode
b1000baseCXFD(28), -- 1000BASE-CX full duplex mode
b1000baseTHD(29), -- 1000BASE-T half duplex mode
b1000baseTFD(30) -- 1000BASE-T full duplex mode
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A value that uniquely identifies the set of
possible IEEE 802.3 types that the MAU could be.
If auto-negotiation is present on this MAU, this
object will map to ifMauAutoNegCapability.
ifJackType OBJECT-TYPE Note that this MAU may be capable of operating
SYNTAX JackType as a MAU type that is beyond the scope of this
MAX-ACCESS read-only MIB. This is indicated by returning the
STATUS current bit value bOther in addition to any bit values
DESCRIPTION "The jack connector type, as it appears on the for capabilities that are listed above."
outside of the system." ::= { ifMauEntry 13 }
::= { ifJackEntry 2 }
-- The ifMauAutoNegTable applies to systems in which -- The ifJackTable applies to MAUs attached to interfaces
-- auto-negotiation is supported on one or more MAUs -- which have one or more external jacks (connectors).
-- attached to interfaces. Note that if auto-negotiation
-- is present and enabled, the ifMauType object reflects
-- the result of the auto-negotiation function.
ifMauAutoNegTable OBJECT-TYPE ifJackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfMauAutoNegEntry SYNTAX SEQUENCE OF IfJackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "Configuration and status objects for the DESCRIPTION "Information about the external jacks attached
auto-negotiation function of MAUs attached to to MAUs attached to an interface."
interfaces." ::= { dot3IfMauBasicGroup 2 }
::= { dot3IfMauAutoNegGroup 1 }
ifMauAutoNegEntry OBJECT-TYPE ifJackEntry OBJECT-TYPE
SYNTAX IfMauAutoNegEntry SYNTAX IfJackEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An entry in the table, containing configuration DESCRIPTION "An entry in the table, containing information
and status information for the auto-negotiation about a particular jack."
function of a particular MAU." INDEX { ifMauIfIndex,
INDEX { ifMauIfIndex, ifMauIndex,
ifMauIndex ifJackIndex
} }
::= { ifMauAutoNegTable 1 } ::= { ifJackTable 1 }
IfMauAutoNegEntry ::= IfJackEntry ::=
SEQUENCE { SEQUENCE {
ifMauAutoNegAdminStatus INTEGER, ifJackIndex Integer32,
ifMauAutoNegRemoteSignaling INTEGER, ifJackType JackType
ifMauAutoNegConfig INTEGER, }
ifMauAutoNegCapability Integer32,
ifMauAutoNegCapAdvertised Integer32,
ifMauAutoNegCapReceived Integer32,
ifMauAutoNegRestart INTEGER,
ifMauAutoNegCapabilityBits BITS,
ifMauAutoNegCapAdvertisedBits BITS,
ifMauAutoNegCapReceivedBits BITS,
ifMauAutoNegRemoteFaultAdvertised INTEGER,
ifMauAutoNegRemoteFaultReceived INTEGER
}
ifMauAutoNegAdminStatus OBJECT-TYPE ifJackIndex OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32 (1..2147483647)
enabled(1), MAX-ACCESS not-accessible
disabled(2) STATUS current
} DESCRIPTION "This variable uniquely identifies the jack
MAX-ACCESS read-write described by this entry from among other jacks
STATUS current attached to the same MAU."
DESCRIPTION "Setting this object to enabled(1) will cause ::= { ifJackEntry 1 }
the interface which has the auto-negotiation
signaling ability to be enabled.
If the value of this object is disabled(2) then ifJackType OBJECT-TYPE
the interface will act as it would if it had no SYNTAX JackType
auto-negotiation signaling. Under these MAX-ACCESS read-only
conditions, an IEEE 802.3 MAU will immediately STATUS current
be forced to the state indicated by the value of DESCRIPTION "The jack connector type, as it appears on the
the object ifMauDefaultType. outside of the system."
::= { ifJackEntry 2 }
NOTE TO IMPLEMENTORS: When -- The ifMauAutoNegTable applies to systems in which
ifMauAutoNegAdminStatus transitions from enabled -- auto-negotiation is supported on one or more MAUs
to disabled, the agent implementation MUST -- attached to interfaces. Note that if auto-negotiation
ensure that the operational type of the MAU (as -- is present and enabled, the ifMauType object reflects
reported by ifMauType) correctly transitions to -- the result of the auto-negotiation function.
the value specified by the ifMauDefaultType
object, rather than continuing to operate at the
value earlier determined by the auto-negotiation
function."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.2,
aAutoNegAdminState and 30.6.1.2.2,
acAutoNegAdminControl."
::= { ifMauAutoNegEntry 1 }
ifMauAutoNegRemoteSignaling OBJECT-TYPE ifMauAutoNegTable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX SEQUENCE OF IfMauAutoNegEntry
detected(1), MAX-ACCESS not-accessible
notdetected(2) STATUS current
} DESCRIPTION "Configuration and status objects for the
MAX-ACCESS read-only auto-negotiation function of MAUs attached to
STATUS current interfaces."
DESCRIPTION "A value indicating whether the remote end of ::= { dot3IfMauAutoNegGroup 1 }
the link is using auto-negotiation signaling. It
takes the value detected(1) if and only if,
during the previous link negotiation, FLP Bursts
were received."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.3,
aAutoNegRemoteSignaling."
::= { ifMauAutoNegEntry 2 }
ifMauAutoNegConfig OBJECT-TYPE ifMauAutoNegEntry OBJECT-TYPE
SYNTAX INTEGER { SYNTAX IfMauAutoNegEntry
other(1), MAX-ACCESS not-accessible
configuring(2), STATUS current
complete(3), DESCRIPTION "An entry in the table, containing configuration
disabled(4), and status information for the auto-negotiation
parallelDetectFail(5) function of a particular MAU."
} INDEX { ifMauIfIndex,
MAX-ACCESS read-only ifMauIndex
STATUS current }
DESCRIPTION "A value indicating the current status of the
auto-negotiation process. The enumeration
parallelDetectFail(5) maps to a failure in
parallel detection as defined in 28.2.3.1 of
[IEEE 802.3 Std]."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4,
aAutoNegAutoConfig."
::= { ifMauAutoNegEntry 4 }
ifMauAutoNegCapability OBJECT-TYPE ::= { ifMauAutoNegTable 1 }
SYNTAX Integer32
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
A value that uniquely identifies the set of IfMauAutoNegEntry ::=
capabilities of the local auto-negotiation SEQUENCE {
entity. The value is a sum which initially ifMauAutoNegAdminStatus INTEGER,
takes the value zero. Then, for each capability ifMauAutoNegRemoteSignaling INTEGER,
of this interface, 2 raised to the power noted ifMauAutoNegConfig INTEGER,
below is added to the sum. For example, an ifMauAutoNegCapability Integer32,
interface which has the capability to support ifMauAutoNegCapAdvertised Integer32,
only 100Base-TX half duplex would have a value ifMauAutoNegCapReceived Integer32,
of 32768 (2**15). In contrast, an interface ifMauAutoNegRestart INTEGER,
which supports both 100Base-TX half duplex and ifMauAutoNegCapabilityBits BITS,
and 100Base-TX full duplex would have a value of ifMauAutoNegCapAdvertisedBits BITS,
98304 ((2**15) + (2**16)). ifMauAutoNegCapReceivedBits BITS,
ifMauAutoNegRemoteFaultAdvertised INTEGER,
ifMauAutoNegRemoteFaultReceived INTEGER
}
The powers of 2 assigned to the capabilities are ifMauAutoNegAdminStatus OBJECT-TYPE
these: SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "Setting this object to enabled(1) will cause
the interface which has the auto-negotiation
signaling ability to be enabled.
Power Capability If the value of this object is disabled(2) then
0 other or unknown the interface will act as it would if it had no
(1-9) (reserved) auto-negotiation signaling. Under these
10 10BASE-T half duplex mode conditions, an IEEE 802.3 MAU will immediately
11 10BASE-T full duplex mode be forced to the state indicated by the value of
12 (reserved) the object ifMauDefaultType.
13 (reserved)
14 100BASE-T4
15 100BASE-TX half duplex mode
16 100BASE-TX full duplex mode
17 (reserved)
18 (reserved)
19 100BASE-T2 half duplex mode
20 100BASE-T2 full duplex mode
Note that interfaces that support this MIB may NOTE TO IMPLEMENTORS: When
have capabilities that extend beyond the scope ifMauAutoNegAdminStatus transitions from enabled
of this MIB. to disabled, the agent implementation MUST
ensure that the operational type of the MAU (as
reported by ifMauType) correctly transitions to
the value specified by the ifMauDefaultType
object, rather than continuing to operate at the
value earlier determined by the auto-negotiation
function."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.2,
aAutoNegAdminState and 30.6.1.2.2,
acAutoNegAdminControl."
This object has been deprecated in favour of ::= { ifMauAutoNegEntry 1 }
ifMauAutoNegCapabilityBits"
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 5 }
ifMauAutoNegCapAdvertised OBJECT-TYPE ifMauAutoNegRemoteSignaling OBJECT-TYPE
SYNTAX Integer32 SYNTAX INTEGER {
MAX-ACCESS read-write detected(1),
STATUS deprecated notdetected(2)
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** }
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A value indicating whether the remote end of
the link is using auto-negotiation signaling. It
takes the value detected(1) if and only if,
during the previous link negotiation, FLP Bursts
were received."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.3,
aAutoNegRemoteSignaling."
::= { ifMauAutoNegEntry 2 }
A value that uniquely identifies the set of ifMauAutoNegConfig OBJECT-TYPE
capabilities advertised by the local SYNTAX INTEGER {
auto-negotiation entity. Refer to other(1),
ifMauAutoNegCapability for a description of the configuring(2),
possible values of this object. complete(3),
disabled(4),
parallelDetectFail(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A value indicating the current status of the
auto-negotiation process. The enumeration
parallelDetectFail(5) maps to a failure in
parallel detection as defined in 28.2.3.1 of
[IEEE 802.3 Std]."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4,
aAutoNegAutoConfig."
::= { ifMauAutoNegEntry 4 }
Capabilities in this object that are not ifMauAutoNegCapability OBJECT-TYPE
available in ifMauAutoNegCapability cannot be SYNTAX Integer32
enabled. MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
This object has been deprecated in favour of A value that uniquely identifies the set of
ifMauAutoNegCapAdvertisedBits" capabilities of the local auto-negotiation
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, entity. The value is a sum which initially
aAutoNegAdvertisedTechnologyAbility." takes the value zero. Then, for each capability
::= { ifMauAutoNegEntry 6 } of this interface, 2 raised to the power noted
below is added to the sum. For example, an
interface which has the capability to support
only 100Base-TX half duplex would have a value
of 32768 (2**15). In contrast, an interface
which supports both 100Base-TX half duplex and
and 100Base-TX full duplex would have a value of
98304 ((2**15) + (2**16)).
ifMauAutoNegCapReceived OBJECT-TYPE The powers of 2 assigned to the capabilities are
SYNTAX Integer32 these:
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
A value that uniquely identifies the set of Power Capability
capabilities received from the remote 0 other or unknown
auto-negotiation entity. Refer to (1-9) (reserved)
ifMauAutoNegCapability for a description of the 10 10BASE-T half duplex mode
possible values of this object. 11 10BASE-T full duplex mode
12 (reserved)
13 (reserved)
14 100BASE-T4
15 100BASE-TX half duplex mode
16 100BASE-TX full duplex mode
17 (reserved)
18 (reserved)
19 100BASE-T2 half duplex mode
20 100BASE-T2 full duplex mode
Note that interfaces that support this MIB may Note that interfaces that support this MIB may
be attached to remote auto-negotiation entities have capabilities that extend beyond the scope
which have capabilities beyond the scope of this of this MIB.
MIB. This object has been deprecated in favour of
ifMauAutoNegCapabilityBits"
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 5 }
This object has been deprecated in favour of ifMauAutoNegCapAdvertised OBJECT-TYPE
ifMauAutoNegCapReceivedBits" SYNTAX Integer32
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, MAX-ACCESS read-write
aAutoNegReceivedTechnologyAbility." STATUS deprecated
::= { ifMauAutoNegEntry 7 } DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
ifMauAutoNegRestart OBJECT-TYPE A value that uniquely identifies the set of
SYNTAX INTEGER { capabilities advertised by the local
restart(1), auto-negotiation entity. Refer to
norestart(2) ifMauAutoNegCapability for a description of the
possible values of this object.
} Capabilities in this object that are not
MAX-ACCESS read-write available in ifMauAutoNegCapability cannot be
STATUS current enabled.
DESCRIPTION "If the value of this object is set to
restart(1) then this will force auto-negotiation
to begin link renegotiation. If auto-negotiation
signaling is disabled, a write to this object
has no effect.
Setting the value of this object to norestart(2) This object has been deprecated in favour of
has no effect." ifMauAutoNegCapAdvertisedBits"
REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1, REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6,
acAutoNegRestartAutoConfig." aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 8 } ::= { ifMauAutoNegEntry 6 }
ifMauAutoNegCapabilityBits OBJECT-TYPE ifMauAutoNegCapReceived OBJECT-TYPE
SYNTAX BITS { SYNTAX Integer32
bOther(0), -- other or unknown MAX-ACCESS read-only
b10baseT(1), -- 10BASE-T half duplex mode STATUS deprecated
b10baseTFD(2), -- 10BASE-T full duplex mode DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
b100baseT4(3), -- 100BASE-T4
b100baseTX(4), -- 100BASE-TX half duplex mode
b100baseTXFD(5), -- 100BASE-TX full duplex mode
b100baseT2(6), -- 100BASE-T2 half duplex mode
b100baseT2FD(7), -- 100BASE-T2 full duplex mode
bfdxPause(8), -- PAUSE for full-duplex links
bfdxAPause(9), -- Asymmetric PAUSE for full-duplex
-- links
bfdxSPause(10), -- Symmetric PAUSE for full-duplex
-- links
bfdxBPause(11), -- Asymmetric and Symmetric PAUSE for
-- full-duplex links
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half
-- duplex mode
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full
-- duplex mode
b1000baseT(14), -- 1000BASE-T half duplex mode
b1000baseTFD(15) -- 1000BASE-T full duplex mode
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A value that uniquely identifies the set of
capabilities of the local auto-negotiation
entity. Note that interfaces that support this
MIB may have capabilities that extend beyond the
scope of this MIB."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 9 } A value that uniquely identifies the set of
capabilities received from the remote
auto-negotiation entity. Refer to
ifMauAutoNegCapability for a description of the
possible values of this object.
ifMauAutoNegCapAdvertisedBits OBJECT-TYPE Note that interfaces that support this MIB may
SYNTAX BITS { be attached to remote auto-negotiation entities
which have capabilities beyond the scope of this
MIB.
This object has been deprecated in favour of
ifMauAutoNegCapReceivedBits"
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 7 }
ifMauAutoNegRestart OBJECT-TYPE
SYNTAX INTEGER {
restart(1),
norestart(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "If the value of this object is set to
restart(1) then this will force auto-negotiation
to begin link renegotiation. If auto-negotiation
signaling is disabled, a write to this object
has no effect.
Setting the value of this object to norestart(2)
has no effect."
REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1,
acAutoNegRestartAutoConfig."
::= { ifMauAutoNegEntry 8 }
ifMauAutoNegCapabilityBits OBJECT-TYPE
SYNTAX BITS {
bOther(0), -- other or unknown
b10baseT(1), -- 10BASE-T half duplex mode
b10baseTFD(2), -- 10BASE-T full duplex mode
b100baseT4(3), -- 100BASE-T4
b100baseTX(4), -- 100BASE-TX half duplex mode
b100baseTXFD(5), -- 100BASE-TX full duplex mode
b100baseT2(6), -- 100BASE-T2 half duplex mode
b100baseT2FD(7), -- 100BASE-T2 full duplex mode
bfdxPause(8), -- PAUSE for full-duplex links
bfdxAPause(9), -- Asymmetric PAUSE for full-duplex
-- links
bfdxSPause(10), -- Symmetric PAUSE for full-duplex
-- links
bfdxBPause(11), -- Asymmetric and Symmetric PAUSE for
-- full-duplex links
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half
-- duplex mode
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full
-- duplex mode
b1000baseT(14), -- 1000BASE-T half duplex mode
b1000baseTFD(15) -- 1000BASE-T full duplex mode
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A value that uniquely identifies the set of
capabilities of the local auto-negotiation
entity. Note that interfaces that support this
MIB may have capabilities that extend beyond the
scope of this MIB.
Note that the local auto-negotiation entity may
support some capabilities beyond the scope of
this MIB. This is indicated by returning the
bit value bOther in addition to any bit values
for capabilities that are listed above."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 9 }
ifMauAutoNegCapAdvertisedBits OBJECT-TYPE
SYNTAX BITS {
bOther(0), -- other or unknown
b10baseT(1), -- 10BASE-T half duplex mode
b10baseTFD(2), -- 10BASE-T full duplex mode
b100baseT4(3), -- 100BASE-T4
b100baseTX(4), -- 100BASE-TX half duplex mode
b100baseTXFD(5), -- 100BASE-TX full duplex mode
b100baseT2(6), -- 100BASE-T2 half duplex mode
b100baseT2FD(7), -- 100BASE-T2 full duplex mode
bFdxPause(8), -- PAUSE for full-duplex links
bFdxAPause(9), -- Asymmetric PAUSE for full-duplex
-- links
bFdxSPause(10), -- Symmetric PAUSE for full-duplex
-- links
bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for
-- full-duplex links
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half
-- duplex mode
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full
-- duplex mode
b1000baseT(14), -- 1000BASE-T half duplex mode
b1000baseTFD(15) -- 1000BASE-T full duplex mode
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "A value that uniquely identifies the set of
capabilities advertised by the local
auto-negotiation entity.
Capabilities in this object that are not
available in ifMauAutoNegCapabilityBits cannot
be enabled.
Note that the local auto-negotiation entity may
advertise some capabilities beyond the scope of
this MIB. This is indicated by returning the
bit value bOther in addition to any bit values
for capabilities that are listed above."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 10 }
ifMauAutoNegCapReceivedBits OBJECT-TYPE
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
bFdxAPause(9), -- Asymmetric PAUSE for full-duplex bFdxAPause(9), -- Asymmetric PAUSE for full-duplex
skipping to change at page 36, line 30 skipping to change at page 38, line 17
bFdxSPause(10), -- Symmetric PAUSE for full-duplex bFdxSPause(10), -- Symmetric PAUSE for full-duplex
-- links -- links
bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for
-- full-duplex links -- full-duplex links
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half
-- duplex mode -- duplex mode
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full
-- duplex mode -- duplex mode
b1000baseT(14), -- 1000BASE-T half duplex mode b1000baseT(14), -- 1000BASE-T half duplex mode
b1000baseTFD(15) -- 1000BASE-T full duplex mode b1000baseTFD(15) -- 1000BASE-T full duplex mode
} }
MAX-ACCESS read-write 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 advertised by the local capabilities received from the remote
auto-negotiation entity. auto-negotiation entity.
Capabilities in this object that are not
available in ifMauAutoNegCapability cannot be
enabled."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 10 }
ifMauAutoNegCapReceivedBits OBJECT-TYPE
SYNTAX BITS {
bOther(0), -- other or unknown
b10baseT(1), -- 10BASE-T half duplex mode
b10baseTFD(2), -- 10BASE-T full duplex mode
b100baseT4(3), -- 100BASE-T4
b100baseTX(4), -- 100BASE-TX half duplex mode
b100baseTXFD(5), -- 100BASE-TX full duplex mode
b100baseT2(6), -- 100BASE-T2 half duplex mode
b100baseT2FD(7), -- 100BASE-T2 full duplex mode
bFdxPause(8), -- PAUSE for full-duplex links
bFdxAPause(9), -- Asymmetric PAUSE for full-duplex
-- links
bFdxSPause(10), -- Symmetric PAUSE for full-duplex
-- links
bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for
-- full-duplex links
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half
-- duplex mode
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full
-- duplex mode
b1000baseT(14), -- 1000BASE-T half duplex mode
b1000baseTFD(15) -- 1000BASE-T full duplex mode
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A value that uniquely identifies the set of
capabilities received from the remote
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 which have capabilities beyond the scope of this
MIB." MIB. This is indicated by returning the bit
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, value bOther in addition to any bit values for
aAutoNegReceivedTechnologyAbility." capabilities that are listed above."
::= { ifMauAutoNegEntry 11 } REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 11 }
ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE
SYNTAX INTEGER {
noError(1),
offline(2),
linkFailure(3),
autoNegError(4)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION "A value that identifies any local fault
indications that this MAU has detected and will
advertise at the next auto-negotiation
interaction for 1000Mbps MAUs."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 12 }
ifMauAutoNegRemoteFaultAdvertised 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-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A value that identifies any local fault DESCRIPTION "A value that identifies any fault indications
indications that this MAU has detected and will received from the far end of a link by the
advertise at the next auto-negotiation local auto-negotiation entity for 1000Mbps
interaction for 1000Mbps MAUs." MAUs."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7,
aAutoNegAdvertisedTechnologyAbility." aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 12 } ::= { ifMauAutoNegEntry 13 }
ifMauAutoNegRemoteFaultReceived OBJECT-TYPE --
SYNTAX INTEGER { -- The Basic Broadband MAU Table
noError(1), --
offline(2),
linkFailure(3),
autoNegError(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION "A value that identifies any fault indications
received from the far end of a link by the
local auto-negotiation entity for 1000Mbps
MAUs."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 13 }
-- broadMauBasicTable OBJECT-TYPE
-- The Basic Broadband MAU Table SYNTAX SEQUENCE OF BroadMauBasicEntry
-- MAX-ACCESS not-accessible
STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
broadMauBasicTable OBJECT-TYPE Table of descriptive and status information
SYNTAX SEQUENCE OF BroadMauBasicEntry about the broadband MAUs connected to
MAX-ACCESS not-accessible interfaces."
STATUS deprecated ::= { dot3BroadMauBasicGroup 1 }
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
Table of descriptive and status information broadMauBasicEntry OBJECT-TYPE
about the broadband MAUs connected to SYNTAX BroadMauBasicEntry
interfaces." MAX-ACCESS not-accessible
::= { dot3BroadMauBasicGroup 1 } STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
broadMauBasicEntry OBJECT-TYPE An entry in the table, containing information
SYNTAX BroadMauBasicEntry about a single broadband MAU."
MAX-ACCESS not-accessible INDEX { broadMauIfIndex,
STATUS deprecated broadMauIndex
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** }
::= { broadMauBasicTable 1 }
An entry in the table, containing information BroadMauBasicEntry ::=
about a single broadband MAU." SEQUENCE {
INDEX { broadMauIfIndex, broadMauIfIndex Integer32,
broadMauIndex broadMauIndex Integer32,
} broadMauXmtRcvSplitType INTEGER,
::= { broadMauBasicTable 1 } broadMauXmtCarrierFreq Integer32,
broadMauTranslationFreq Integer32
}
BroadMauBasicEntry ::= broadMauIfIndex OBJECT-TYPE
SEQUENCE { SYNTAX Integer32 (1..2147483647)
broadMauIfIndex Integer32, MAX-ACCESS read-only
broadMauIndex Integer32, STATUS deprecated
broadMauXmtRcvSplitType INTEGER, DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
broadMauXmtCarrierFreq Integer32,
broadMauTranslationFreq Integer32
}
broadMauIfIndex OBJECT-TYPE This variable uniquely identifies the interface
SYNTAX Integer32 (1..2147483647) to which the MAU described by this entry is
MAX-ACCESS read-only connected."
STATUS deprecated REFERENCE "Reference RFC 1213, ifIndex."
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** ::= { broadMauBasicEntry 1 }
This variable uniquely identifies the interface broadMauIndex OBJECT-TYPE
to which the MAU described by this entry is SYNTAX Integer32 (1..2147483647)
connected." MAX-ACCESS read-only
REFERENCE "Reference RFC 1213, ifIndex." STATUS deprecated
::= { broadMauBasicEntry 1 } DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
broadMauIndex OBJECT-TYPE This variable uniquely identifies the MAU
SYNTAX Integer32 (1..2147483647) connected to interface broadMauIfIndex that is
MAX-ACCESS read-only described by this entry."
STATUS deprecated REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** ::= { broadMauBasicEntry 2 }
This variable uniquely identifies the MAU broadMauXmtRcvSplitType OBJECT-TYPE
connected to interface broadMauIfIndex that is SYNTAX INTEGER {
described by this entry." other(1),
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." single(2),
::= { broadMauBasicEntry 2 } dual(3)
}
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
broadMauXmtRcvSplitType OBJECT-TYPE This object indicates the type of frequency
SYNTAX INTEGER { multiplexing/cabling system used to separate the
other(1), transmit and receive paths for the 10BROAD36
single(2), MAU.
dual(3)
}
MAX-ACCESS read-only
STATUS deprecated
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
This object indicates the type of frequency The value other(1) is returned if the split type
multiplexing/cabling system used to separate the is not either single or dual.
transmit and receive paths for the 10BROAD36
MAU.
The value other(1) is returned if the split type The value single(2) indicates a single cable
is not either single or dual. system. The value dual(3) indicates a dual
cable system, offset normally zero."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.8,
aBbMAUXmitRcvSplitType."
::= { broadMauBasicEntry 3 }
The value single(2) indicates a single cable broadMauXmtCarrierFreq OBJECT-TYPE
system. The value dual(3) indicates a dual SYNTAX Integer32
cable system, offset normally zero." MAX-ACCESS read-only
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.8, STATUS deprecated
aBbMAUXmitRcvSplitType." DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
::= { broadMauBasicEntry 3 }
broadMauXmtCarrierFreq OBJECT-TYPE This variable indicates the transmit carrier
SYNTAX Integer32 frequency of the 10BROAD36 MAU in MHz/4; that
MAX-ACCESS read-only is, in units of 250 kHz."
STATUS deprecated REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9,
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** aBroadbandFrequencies.xmitCarrierFrequency."
::= { broadMauBasicEntry 4 }
This variable indicates the transmit carrier broadMauTranslationFreq OBJECT-TYPE
frequency of the 10BROAD36 MAU in MHz/4; that SYNTAX Integer32
is, in units of 250 kHz." MAX-ACCESS read-only
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, STATUS deprecated
aBroadbandFrequencies.xmitCarrierFrequency." DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
::= { broadMauBasicEntry 4 }
broadMauTranslationFreq OBJECT-TYPE This variable indicates the translation offset
SYNTAX Integer32 frequency of the 10BROAD36 MAU in MHz/4; that
MAX-ACCESS read-only is, in units of 250 kHz."
STATUS deprecated REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9,
DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** aBroadbandFrequencies.translationFrequency."
::= { broadMauBasicEntry 5 }
This variable indicates the translation offset -- Notifications for use by 802.3 MAUs
frequency of the 10BROAD36 MAU in MHz/4; that
is, in units of 250 kHz."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9,
aBroadbandFrequencies.translationFrequency."
::= { broadMauBasicEntry 5 }
-- Notifications for use by 802.3 MAUs snmpDot3MauTraps OBJECT IDENTIFIER ::= { snmpDot3MauMgt 0 }
snmpDot3MauTraps OBJECT IDENTIFIER ::= { snmpDot3MauMgt 0 } rpMauJabberTrap NOTIFICATION-TYPE
OBJECTS { rpMauJabberState }
STATUS current
DESCRIPTION "This trap is sent whenever a managed repeater
MAU enters the jabber state.
rpMauJabberTrap NOTIFICATION-TYPE The agent MUST throttle the generation of
OBJECTS { rpMauJabberState } consecutive rpMauJabberTraps so that there is at
STATUS current least a five-second gap between them."
DESCRIPTION "This trap is sent whenever a managed repeater REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
MAU enters the jabber state. notification."
::= { snmpDot3MauTraps 1 }
The agent MUST throttle the generation of ifMauJabberTrap NOTIFICATION-TYPE
consecutive rpMauJabberTraps so that there is at OBJECTS { ifMauJabberState }
least a five-second gap between them." STATUS current
REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber DESCRIPTION "This trap is sent whenever a managed interface
notification." MAU enters the jabber state.
::= { snmpDot3MauTraps 1 }
ifMauJabberTrap NOTIFICATION-TYPE The agent MUST throttle the generation of
OBJECTS { ifMauJabberState } consecutive ifMauJabberTraps so that there is at
STATUS current least a five-second gap between them."
DESCRIPTION "This trap is sent whenever a managed interface REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
MAU enters the jabber state. notification."
::= { snmpDot3MauTraps 2 }
The agent MUST throttle the generation of -- Conformance information
consecutive ifMauJabberTraps so that there is at
least a five-second gap between them."
REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
notification."
::= { snmpDot3MauTraps 2 }
-- Conformance information mauModConf
OBJECT IDENTIFIER ::= { mauMod 1 }
mauModCompls
OBJECT IDENTIFIER ::= { mauModConf 1 }
mauModObjGrps
OBJECT IDENTIFIER ::= { mauModConf 2 }
mauModNotGrps
OBJECT IDENTIFIER ::= { mauModConf 3 }
-- Object groups
mauModConf mauRpGrpBasic OBJECT-GROUP
OBJECT IDENTIFIER ::= { mauMod 1 } OBJECTS { rpMauGroupIndex,
mauModCompls rpMauPortIndex,
OBJECT IDENTIFIER ::= { mauModConf 1 } rpMauIndex,
mauModObjGrps rpMauType,
OBJECT IDENTIFIER ::= { mauModConf 2 } rpMauStatus,
mauModNotGrps rpMauMediaAvailable,
OBJECT IDENTIFIER ::= { mauModConf 3 } rpMauMediaAvailableStateExits,
rpMauJabberState,
rpMauJabberingStateEnters
}
STATUS current
DESCRIPTION "Basic conformance group for MAUs attached to
repeater ports. This group is also the
conformance specification for RFC 1515
implementations."
::= { mauModObjGrps 1 }
-- Object groups mauRpGrp100Mbs OBJECT-GROUP
OBJECTS { rpMauFalseCarriers }
STATUS current
DESCRIPTION "Conformance group for MAUs attached to
repeater ports with 100 Mb/s or greater
capability."
::= { mauModObjGrps 2 }
mauRpGrpBasic OBJECT-GROUP mauRpGrpJack OBJECT-GROUP
OBJECTS { rpMauGroupIndex, OBJECTS { rpJackType }
rpMauPortIndex, STATUS current
rpMauIndex, DESCRIPTION "Conformance group for MAUs attached to
rpMauType, repeater ports with managed jacks."
rpMauStatus, ::= { mauModObjGrps 3 }
rpMauMediaAvailable,
rpMauMediaAvailableStateExits,
rpMauJabberState,
rpMauJabberingStateEnters
}
STATUS current
DESCRIPTION "Basic conformance group for MAUs attached to
repeater ports. This group is also the
conformance specification for RFC 1515
implementations."
::= { mauModObjGrps 1 }
mauRpGrp100Mbs OBJECT-GROUP mauIfGrpBasic OBJECT-GROUP
OBJECTS { rpMauFalseCarriers } OBJECTS { ifMauIfIndex,
STATUS current ifMauIndex,
DESCRIPTION "Conformance group for MAUs attached to ifMauType,
repeater ports with 100 Mb/s or greater ifMauStatus,
capability." ifMauMediaAvailable,
::= { mauModObjGrps 2 } ifMauMediaAvailableStateExits,
ifMauJabberState,
ifMauJabberingStateEnters
}
STATUS current
DESCRIPTION "Basic conformance group for MAUs attached to
interfaces. This group also provides a
conformance specification for RFC 1515
implementations."
::= { mauModObjGrps 4 }
mauRpGrpJack OBJECT-GROUP mauIfGrp100Mbs OBJECT-GROUP
OBJECTS { rpJackType } OBJECTS { ifMauFalseCarriers,
STATUS current ifMauTypeList,
DESCRIPTION "Conformance group for MAUs attached to ifMauDefaultType,
repeater ports with managed jacks." ifMauAutoNegSupported
::= { mauModObjGrps 3 } }
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
mauIfGrpBasic OBJECT-GROUP Conformance group for MAUs attached to
OBJECTS { ifMauIfIndex, interfaces with 100 Mb/s capability.
ifMauIndex,
ifMauType,
ifMauStatus,
ifMauMediaAvailable,
ifMauMediaAvailableStateExits,
ifMauJabberState,
ifMauJabberingStateEnters
}
STATUS current
DESCRIPTION "Basic conformance group for MAUs attached to
interfaces. This group also provides a
conformance specification for RFC 1515
implementations."
::= { mauModObjGrps 4 }
mauIfGrp100Mbs OBJECT-GROUP This object group has been deprecated in favor
OBJECTS { ifMauFalseCarriers, of mauIfGrpHighCapacity."
ifMauTypeList, ::= { mauModObjGrps 5 }
ifMauDefaultType,
ifMauAutoNegSupported
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
Conformance group for MAUs attached to mauIfGrpJack OBJECT-GROUP
interfaces with 100 Mb/s capability. OBJECTS { ifJackType }
STATUS current
DESCRIPTION "Conformance group for MAUs attached to
interfaces with managed jacks."
This object group has been deprecated in favor ::= { mauModObjGrps 6 }
of mauIfGrpHighCapacity."
::= { mauModObjGrps 5 }
mauIfGrpJack OBJECT-GROUP mauIfGrpAutoNeg OBJECT-GROUP
OBJECTS { ifJackType } OBJECTS { ifMauAutoNegAdminStatus,
STATUS current ifMauAutoNegRemoteSignaling,
DESCRIPTION "Conformance group for MAUs attached to ifMauAutoNegConfig,
interfaces with managed jacks." ifMauAutoNegCapability,
::= { mauModObjGrps 6 } ifMauAutoNegCapAdvertised,
ifMauAutoNegCapReceived,
ifMauAutoNegRestart
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
mauIfGrpAutoNeg OBJECT-GROUP Conformance group for MAUs attached to
OBJECTS { ifMauAutoNegAdminStatus, interfaces with managed auto-negotiation.
ifMauAutoNegRemoteSignaling,
ifMauAutoNegConfig,
ifMauAutoNegCapability,
ifMauAutoNegCapAdvertised,
ifMauAutoNegCapReceived,
ifMauAutoNegRestart
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
Conformance group for MAUs attached to This object group has been deprecated in favor
interfaces with managed auto-negotiation. of mauIfGrpAutoNeg2."
::= { mauModObjGrps 7 }
This object group has been deprecated in favor mauBroadBasic OBJECT-GROUP
of mauIfGrpAutoNeg2." OBJECTS { broadMauIfIndex,
::= { mauModObjGrps 7 } broadMauIndex,
broadMauXmtRcvSplitType,
broadMauXmtCarrierFreq,
broadMauTranslationFreq
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
mauBroadBasic OBJECT-GROUP Conformance group for broadband MAUs attached
OBJECTS { broadMauIfIndex, to interfaces.
broadMauIndex,
broadMauXmtRcvSplitType,
broadMauXmtCarrierFreq,
broadMauTranslationFreq
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
Conformance group for broadband MAUs attached This object group is deprecated. There have
to interfaces. been no reported implementations of this group,
and it was felt to be unlikely that there will
be any future implementations."
::= { mauModObjGrps 8 }
This object group is deprecated. There have mauIfGrpHighCapacity OBJECT-GROUP
been no reported implementations of this group, OBJECTS { ifMauFalseCarriers,
and it was felt to be unlikely that there will ifMauTypeListBits,
be any future implementations." ifMauDefaultType,
::= { mauModObjGrps 8 } ifMauAutoNegSupported
}
STATUS current
DESCRIPTION "Conformance group for MAUs attached to
interfaces with 100 Mb/s or greater capability."
::= { mauModObjGrps 9 }
mauIfGrpHighCapacity OBJECT-GROUP mauIfGrpAutoNeg2 OBJECT-GROUP
OBJECTS { ifMauFalseCarriers, OBJECTS { ifMauAutoNegAdminStatus,
ifMauTypeListBits, ifMauAutoNegRemoteSignaling,
ifMauDefaultType, ifMauAutoNegConfig,
ifMauAutoNegSupported ifMauAutoNegCapabilityBits,
} ifMauAutoNegCapAdvertisedBits,
STATUS current ifMauAutoNegCapReceivedBits,
DESCRIPTION "Conformance group for MAUs attached to ifMauAutoNegRestart
interfaces with 100 Mb/s or greater capability." }
::= { mauModObjGrps 9 } STATUS current
DESCRIPTION "Conformance group for MAUs attached to
interfaces with managed auto-negotiation."
::= { mauModObjGrps 10 }
mauIfGrpAutoNeg2 OBJECT-GROUP mauIfGrpAutoNeg1000Mbps OBJECT-GROUP
OBJECTS { ifMauAutoNegAdminStatus, OBJECTS { ifMauAutoNegRemoteFaultAdvertised,
ifMauAutoNegRemoteSignaling, ifMauAutoNegRemoteFaultReceived
ifMauAutoNegConfig, }
ifMauAutoNegCapabilityBits, STATUS current
ifMauAutoNegCapAdvertisedBits, DESCRIPTION "Conformance group for 1000Mbps MAUs attached to
ifMauAutoNegCapReceivedBits, interfaces with managed auto-negotiation."
ifMauAutoNegRestart ::= { mauModObjGrps 11 }
}
STATUS current
DESCRIPTION "Conformance group for MAUs attached to
interfaces with managed auto-negotiation."
::= { mauModObjGrps 10 }
mauIfGrpAutoNeg1000Mbps OBJECT-GROUP -- Notification groups
OBJECTS { ifMauAutoNegRemoteFaultAdvertised,
ifMauAutoNegRemoteFaultReceived
}
STATUS current
DESCRIPTION "Conformance group for 1000Mbps MAUs attached to
interfaces with managed auto-negotiation."
::= { mauModObjGrps 11 }
-- Notification groups rpMauNotifications NOTIFICATION-GROUP
NOTIFICATIONS { rpMauJabberTrap }
STATUS current
DESCRIPTION "Notifications for repeater MAUs."
::= { mauModNotGrps 1 }
rpMauNotifications NOTIFICATION-GROUP ifMauNotifications NOTIFICATION-GROUP
NOTIFICATIONS { rpMauJabberTrap } NOTIFICATIONS { ifMauJabberTrap }
STATUS current STATUS current
DESCRIPTION "Notifications for repeater MAUs." DESCRIPTION "Notifications for interface MAUs."
::= { mauModNotGrps 1 } ::= { mauModNotGrps 2 }
ifMauNotifications NOTIFICATION-GROUP -- Compliances
NOTIFICATIONS { ifMauJabberTrap }
STATUS current
DESCRIPTION "Notifications for interface MAUs."
::= { mauModNotGrps 2 }
-- Compliances mauModRpCompl MODULE-COMPLIANCE
mauModRpCompl MODULE-COMPLIANCE STATUS deprecated
STATUS deprecated DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
Compliance for MAUs attached to repeater Compliance for MAUs attached to repeater
ports. ports.
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 which 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 which 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 ********
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 which 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 which 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 which 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 }
mauModIfCompl2 MODULE-COMPLIANCE mauModIfCompl2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "Compliance for MAUs attached to interfaces." DESCRIPTION "Compliance for MAUs attached to interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { mauIfGrpBasic } MANDATORY-GROUPS { mauIfGrpBasic }
GROUP mauIfGrpHighCapacity GROUP mauIfGrpHighCapacity
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have 100Mb/s recommended for MAUs which have 100Mb/s
or greater capability." or greater capability."
GROUP mauIfGrpJack GROUP mauIfGrpJack
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 which 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 which 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 which 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 3 } ::= { mauModCompls 3 }
mauModRpCompl2 MODULE-COMPLIANCE mauModRpCompl2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "Compliance for MAUs attached to repeater DESCRIPTION "Compliance for MAUs attached to repeater
ports." ports."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { mauRpGrpBasic } MANDATORY-GROUPS { mauRpGrpBasic }
GROUP mauRpGrp100Mbs GROUP mauRpGrp100Mbs
DESCRIPTION "Implementation of this optional group is DESCRIPTION "Implementation of this optional group is
recommended for MAUs which have 100Mb/s or recommended for MAUs which have 100Mb/s or
greater capability." greater capability."
GROUP mauRpGrpJack GROUP mauRpGrpJack
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 which 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."
::= { mauModCompls 4 } ::= { mauModCompls 4 }
END END
5. Intellectual Property 5. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; neither does it represent that it
skipping to change at page 48, line 38 skipping to change at page 49, line 33
Geoff Thompson Geoff Thompson
Maurice Turcotte Maurice Turcotte
Paul Woodruff Paul Woodruff
Special thanks as well to Dave Perkins for his excellent work on the Special thanks as well to Dave Perkins for his excellent work on the
SMICng compiler, which made it easy to take advantage of the latest SMICng compiler, which made it easy to take advantage of the latest
SNMPv2 constructs in this MIB. SNMPv2 constructs in this MIB.
7. References 7. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron Describing SNMP Management Frameworks", RFC 2571, May 1999.
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", STD 16, Management Information for TCP/IP-based Internets", STD 16, RFC
RFC 1155, Performance Systems International, Hughes LAN Systems, 1155, May 1990.
May 1990
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
RFC 1212, Performance Systems International, Hughes LAN Systems, RFC 1212, March 1991.
March 1991
[4] M. Rose, "A Convention for Defining Traps for use with the [4] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC 1215, Performance Systems International, March 1991 SNMP", RFC 1215, March 1991.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
"Structure of Management Information for Version 2 of the Simple M. and S. Waldbusser, "Structure of Management Information
Network Management Protocol (SNMPv2)", RFC 1902, SNMP Research, Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
Conventions for Version 2 of the Simple Network Management M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58,
Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco RFC 2579, April 1999.
Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose,
"Conformance Statements for Version 2 of the Simple Network M. and S. Waldbusser, "Conformance Statements for SMIv2", STD
Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., 58, RFC 2580, April 1999.
Cisco Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, SNMP Research, Network Management Protocol", STD 15, RFC 1157, May 1990.
Performance Systems International, Performance Systems
International, MIT Laboratory for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP "Introduction to Community-based SNMPv2", RFC 1901, January
Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1996.
Inc., International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
"Transport Mappings for Version 2 of the Simple Network Mappings for Version 2 of the Simple Network Management Protocol
Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., (SNMPv2)", RFC 1906, January 1996.
Cisco Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [11] Case, J., Harrington, D., Presuhn, R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Protocol (SNMP)", RFC 2572, May 1999.
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
for version 3 of the Simple Network Management Protocol for version 3 of the Simple Network Management Protocol
(SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. (SNMPv3)", RFC 2574, May 1999.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Operations for Version 2 of the Simple Network Management
Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Protocol (SNMPv2)", RFC 1905, January 1996.
Systems, Inc., Dover Beach Consulting, Inc., International
Network Services, January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 2573, May 1999.
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, (SNMP)", RFC 2575, May 1999.
Inc., Cisco Systems, Inc., January 1998
[16] IEEE, IEEE Std 802.3, 1998 Edition: "Information technology - [16] IEEE, IEEE Std 802.3, 1998 Edition: "Information technology -
Telecommunications and information exchange between systems - Telecommunications and information exchange between systems -
Local and metropolitan area networks - Specific requirements - Local and metropolitan area networks - Specific requirements -
Part 3: Carrier sense multiple access with collision detection Part 3: Carrier sense multiple access with collision detection
(CSMA/CD) access method and physical layer specifications" (CSMA/CD) access method and physical layer specifications"
(incorporating ANSI/IEEE Std. 802.3, 1996 Edition, IEEE Std. (incorporating ANSI/IEEE Std. 802.3, 1996 Edition, IEEE Std.
802.3r-1996, 802.3u-1995, 802.3x&y-1997, 802.3z-1998, and 802.3r-1996, 802.3u-1995, 802.3x&y-1997, 802.3z-1998, and
802.3aa-1998), September 1998. 802.3aa-1998), September 1998.
[17] de Graaf, K., D. Romascanu, D. McMaster, and K. McCloghrie, [17] de Graaf, K., Romascanu, D., McMaster, D. and K. McCloghrie,
"Definitions of Managed Objects for IEEE 802.3 Repeater Devices "Definitions of Managed Objects for IEEE 802.3 Repeater Devices
using SMIv2", RFC 2108, 3Com Corporation, Madge Networks using SMIv2", RFC 2108, February 1997.
(Israel) Ltd., Coloma Communications, Cisco Systems, Inc.,
February 1997.
[18] McCloghrie, K., and M. Rose, Editors, "Management Information [18] McCloghrie, K. and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets: MIB-II", Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, Hughes LAN Systems, Performance Systems STD 17, RFC 1213, March 1991.
International, March 1991.
[19] McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB [19] McCloghrie, K. and F. Kastenholtz, "The Interfaces Group MIB
using SMIv2", RFC 2233, Cisco Systems, FTP Software, November using SMIv2", RFC 2233, November 1997.
1997.
[20] Bradner, S., "Key words for use in RFCs to Indicate [20] Bradner, S., "Key words for use in RFCs to Indicate Requirements
Requirements Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[21] de Graaf, K., Romascanu, D., McMaster, D., K. McCloghrie, [21] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K. and S.
S. Roberts, "Definitions of Managed Objects Roberts, "Definitions of Managed Objects for IEEE 802.3 Medium
for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", Attachment Units (MAUs) using SMIv2", RFC 2239, November 1997.
RFC 2239, 3Com Corporation, Madge Networks Ltd., Cisco Systems
Inc., Cisco Systems Inc., Farallon Computing, Inc.,
November 1997.
[22] McMaster, D., K. McCloghrie and S. Roberts, "Definitions of [22] McMaster, D., McCloghrie, K. and S. Roberts, "Definitions of
Managed Objects for IEEE 802.3 Medium Attachment Units Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)",
(MAUs)", RFC 1515, SynOptics Communications, Inc., Hughes LAN RFC 1515, September 1993.
Systems, Inc., Farallon Computing, Inc., September 1993.
[23] Flick, J., and J. Johnson, "Definitions of Managed Objects for [23] Flick, J. and J. Johnson, "Definitions of Managed Objects for
the Ethernet-like Interface Types", work in progress, the Ethernet-like Interface Types", RFC 2665, August 1999.
draft-ietf-hubmib-etherif-mib-v2-02.txt, Hewlett-Packard
Company, RedBack Networks, January, 1999.
8. Security Considerations 8. Security Considerations
There are a number of management objects defined in this MIB that There are a number of management objects defined in this MIB that
have a MAX-ACCESS clause of read-write. Setting these objects can have a MAX-ACCESS clause of read-write. Setting these objects can
have a serious effect on the operation of the network, including: have a serious effect on the operation of the network, including:
enabling or disabling a MAU enabling or disabling a MAU
changing a MAU's default type changing a MAU's default type
enabling, disabling or restarting autonegotiation enabling, disabling or restarting autonegotiation
skipping to change at page 51, line 40 skipping to change at page 51, line 51
network operations. network operations.
SNMPv1 by itself is such an insecure environment. Even if the SNMPv1 by itself is such an insecure environment. Even if the
network itself is secure (for example by using IPSec), even then, network itself is secure (for example by using IPSec), even then,
there is no control as to who on the secure network is allowed to there is no control as to who on the secure network is allowed to
access and GET/SET (read/change/create/delete) the objects in this access and GET/SET (read/change/create/delete) the objects in this
MIB. MIB.
It is recommended that the implementers consider the security It is recommended that the implementers consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework. Specifically, the use
of the User-based Security Model RFC 2274 [12] and the View-based of the User-based Security Model RFC 2574 [12] and the View-based
Access Control Model RFC 2275 [15] is recommended. Access Control Model RFC 2575 [15] is recommended.
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to those objects only to those principals configured to give access to those objects only to those principals
(users) that have legitimate rights to access them. (users) that have legitimate rights to access them.
9. Authors' Addresses 9. Authors' Addresses
Andrew Smith Andrew Smith
Extreme Networks, Inc. Extreme Networks, Inc.
10460 Bandley Drive 3585 Monroe St.
Cupertino, CA 95014, USA Santa Clara, CA 95051 USA
Tel: +1 408 342 0999
E-Mail: andrew@extremenetworks.com Phone: +1 408 579-2821
EMail: andrew@extremenetworks.com
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557 Roseville, CA 95747-5557
Phone: +1 916 785 4018 Phone: +1 916 785 4018
E-mail: johnf@rose.hp.com EMail: johnf@rose.hp.com
Kathryn de Graaf Kathryn de Graaf
Argon Networks Argon Networks
25 Porter Road 25 Porter Road
Littleton, MA 01460 USA Littleton, MA 01460 USA
Tel: +1 978 486 0665 x163
Phone: +1 978 486 0665 x163
Fax: +1 978 486 9379 Fax: +1 978 486 9379
E-mail: kdegraaf@argon.com EMail: kdegraaf@argon.com
Dan Romascanu Dan Romascanu
Lucent Technologies Lucent Technologies
Atidim Technology Park, Bldg. 3 Atidim Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
Israel Israel
Tel: 972 3 645 8414, 6458458
Fax: 972 3 648 7146
E-mail: dromasca@lucent.com
Phone: 972 3 645 8414, 6458458
Fax: 972 3 648 7146
EMail: dromasca@lucent.com
Donna McMaster Donna McMaster
Cisco Systems Inc. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
Tel: +1 408 526 5260
E-Mail: mcmaster@cisco.com Phone: +1 408 526 5260
EMail: mcmaster@cisco.com
Keith McCloghrie Keith McCloghrie
Cisco Systems Inc. Cisco Systems Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134 San Jose, CA 95134
Tel: +1 408 526 5260
E-Mail: kzm@cisco.com Phone: +1 408 526 5260
EMail: kzm@cisco.com
Sam Roberts Sam Roberts
Farallon Computing, Inc. Farallon Computing, Inc.
2470 Mariner Square Loop 2470 Mariner Square Loop
Alameda, CA 94501-1010 Alameda, CA 94501-1010
Tel: +1 510 814 5215
E-Mail: sroberts@farallon.com
A. Change Log Phone: +1 510 814 5215
EMail: sroberts@farallon.com
Appendix
Change Log
This section enumerates the changes made to RFC 2239 to produce this This section enumerates the changes made to RFC 2239 to produce this
document. document.
(1) The MODULE-IDENTITY has been updated to reflect the changes (1) The MODULE-IDENTITY has been updated to reflect the changes
in the MIB. in the MIB.
(2) OBJECT-IDENTITY definitions have been added for gigabit MAU (2) OBJECT-IDENTITY definitions have been added for gigabit MAU
types. types.
skipping to change at page 54, line 10 skipping to change at page 56, line 5
(11) Updated the SNMP Network Management Framework boilerplate. (11) Updated the SNMP Network Management Framework boilerplate.
(12) Refer to the Interfaces MIB, rather than the interfaces (12) Refer to the Interfaces MIB, rather than the interfaces
group of MIB-II. group of MIB-II.
(13) Updated references to refer to latest edition of IEEE 802.3. (13) Updated references to refer to latest edition of IEEE 802.3.
(14) An intellectual property notice was added, as required by (14) An intellectual property notice was added, as required by
RFC 2026. RFC 2026.
B. Full Copyright Statement 11. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
skipping to change at line 2556 skipping to change at page 56, line 32
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.
 End of changes. 316 change blocks. 
1815 lines changed or deleted 1850 lines changed or added

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