draft-ietf-hubmib-mau-mib-04.txt   rfc2239.txt 
Definitions of Managed Objects Network Working Group K. de Graaf
for IEEE 802.3 Medium Attachment Units (MAUs) Request for Comments: 2239 3Com Corporation
using SMIv2 Category: Standards Track D. Romascanu
Madge Networks Ltd.
28 February 1997 D. McMaster
Cisco Systems Inc.
<draft-ietf-hubmib-mau-mib-04.txt> K. McCloghrie
Cisco Systems Inc.
Kathryn de Graaf S. Roberts
3Com Corporation Farallon Computing, Inc.
November 1997
Dan Romascanu
Madge Networks (Israel) Ltd.
Donna McMaster
Cisco Systems Inc.
Keith McCloghrie
Cisco Systems Inc.
Sam Roberts
Farallon Computing, Inc.
,
Status of this Memo
This document is an Internet-Draft. Internet-Drafts are
working documents of the Internet Engineering Task Force
(IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is not appropriate to use Internet-
Drafts as reference material or to cite them other than as a
"work in progress".
To learn the current status of any Internet-Draft, please
check the "1id-abstracts.txt" listing contained in the
Internet-Drafts Shadow Directories on ds.internic.net (US East
Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast),
or munnari.oz.au (Pacific Rim).
Abstract
This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management
protocols in the Internet community. In particular, it
defines objects for managing 10 and 100 Mb/second Medium
Attachment Units (MAUs) based on IEEE Std 802.3 Section 30,
"10 & 100 Mb/s Management," October 26, 1995.
This memo does not specify a standard for the Internet
community.
1. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework presently consists of
three major components. They are:
o the SMI, described in RFC 1902 [6] - the mechanisms used
for describing and naming objects for the purpose of
management.
,
o the MIB-II, STD 17, RFC 1213 [5] - the core set of
managed objects for the Internet suite of protocols.
o the protocol, RFC 1157 [10] and/or RFC 1905 [9] - the
protocol used for accessing managed information.
Textual conventions are defined in RFC 1903 [7], and
conformance statements are defined in RFC 1904 [8].
The Framework permits new objects to be defined for the
purpose of experimentation and evaluation.
1.1. Object Definitions
Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the
MIB are defined using the subset of Abstract Syntax Notation
One (ASN.1) defined in the SMI. In particular, each object
type is named by an OBJECT IDENTIFIER, an administratively
assigned name. The object type together with an object
instance serves to uniquely identify a specific instantiation
of the object. For human convenience, we often use a textual
string, termed the descriptor, to refer to the object type.
,
2. Overview
2.1. Relationship to RFC 1515
This MIB is intended to be a superset of that defined by RFC
1515 [11], which will go to historic status. This MIB
includes all of the objects contained in that MIB, plus
several new ones which provide additional capabilities.
Implementors are encouraged to support all applicable
conformance groups in order to make the best use of the new
functionality provided by this MIB. The new objects provide
management support for:
o management of 100 Mb/s devices
o auto-negotiation on interface MAUs
o jack management
2.2. MAU Management
Instances of these object types represent attributes of an
IEEE 802.3 MAU. Several types of MAUs are defined in the IEEE
802.3 CSMA/CD standard [1] and [2]. These MAUs may be
connected to IEEE 802.3 repeaters or to 802.3 (Ethernet-like)
interfaces. For convenience this document refers to these
devices as "repeater MAUs" and "interface MAUs."
The definitions presented here are based on Section 30.5,
"Layer Management for 10 & 100 Mb/s Medium Attachment Units
(MAUs)", and Annex 30A, "GDMO Specifications for 802.3 managed
objects" of IEEE Std 802.3u-1995. That specification includes
definitions for both 10Mb/s and 100Mb/s devices, and is
essentially a superset of the 10Mb/s definitions given by IEEE
802.3 Section 20. This specification is intended to serve the
same purpose: to provide for management of both 10Mb/s and
100Mb/s MAUs.
2.3. Relationship to Other MIBs Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs) using SMIv2
It is assumed that an agent implementing this MIB will also Status of this Memo
implement (at least) the 'system' group defined in MIB-II [5].
The following sections identify other MIBs that such an agent
, This document specifies an Internet standards track protocol for the
should implement. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
2.3.1. Relationship to the MIB-II 'interfaces' group Copyright Notice
The sections of this document that define interface MAU- Copyright (C) The Internet Society (1997). All Rights Reserved.
related objects specify an extension to the 'interfaces' group
of MIB-II. An agent implementing these interface-MAU related
objects must also implement the 'interfaces' group of MIB-II.
The value of the object ifMauIfIndex is the same as the value
of 'ifIndex' used to instantiate the interface to which the
given MAU is connected.
It is expected that an agent implementing the interface-MAU Table of Contents
related objects in this MIB will also implement the Ethernet-
like Interfaces MIB, RFC 1650.
(Note that repeater ports are not represented as interfaces in 1 The SNMPv2 Network Management Framework ............... 2
the sense of MIB-II's 'interfaces' group.) 1.1 Object Definitions .................................. 2
2 Overview .............................................. 3
2.1 Relationship to RFC 1515 ............................ 3
2.2 MAU Management ...................................... 3
2.3 Relationship to Other MIBs .......................... 3
2.3.1 Relationship to the MIB-II 'interfaces' group ..... 3
2.3.2 Relationship to the 802.3 Repeater MIB ............ 4
2.4 Management of Internal MAUs ......................... 4
3 Definitions ........................................... 4
4 Acknowledgements ...................................... 39
5 References ............................................ 40
6 Security Considerations ............................... 41
7 Authors' Addresses .................................... 41
8 Full Copyright Statement .............................. 43
2.3.2. Relationship to the 802.3 Repeater MIB Abstract
The section of this document that defines repeater MAU-related This memo defines an portion of the Management Information Base (MIB)
objects specifies an extension to the 802.3 Repeater MIB for use with network management protocols in the Internet community.
defined in [4]. An agent implementing these repeater-MAU In particular, it defines objects for managing 10 and 100 Mb/second
related objects must also implement the 802.3 Repeater MIB. Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30,
"10 & 100 Mb/s Management," October 26, 1995.
The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to 1. The SNMPv2 Network Management Framework
instantiate a repeater MAU variable shall be the same as the
values of 'rptrPortGroupIndex' and 'rptrPortIndex' used to
instantiate the port to which the given MAU is connected.
2.4. Management of Internal MAUs The SNMPv2 Network Management Framework presently consists of three
major components. They are:
In some situations, a MAU can be "internal" -- i.e., its o the SMI, described in RFC 1902 [6] - the mechanisms used
functionality is implemented entirely within a device. For for describing and naming objects for the purpose of management.
example, a managed repeater may contain an internal repeater-
MAU and/or an internal interface-MAU through which management
communications originating on one of the repeater's external
ports pass in order to reach the management agent associated
with the repeater. Such internal MAUs may or may not be
managed. If they are managed, objects describing their
attributes should appear in the appropriate MIB subtree:
, o the MIB-II, STD 17, RFC 1213 [5] - the core set of
dot3RpMauBasicGroup for internal repeater-MAUs and managed objects for the Internet suite of protocols.
dot3IfMauBasicGroup for internal interface-MAUs.
, o the protocol, STD 15, RFC 1157 [10] and/or RFC 1905 [9] -
3. Definitions the protocol used for accessing managed information.
MAU-MIB DEFINITIONS ::= BEGIN Textual conventions are defined in RFC 1903 [7], and conformance
statements are defined in RFC 1904 [8].
IMPORTS The Framework permits new objects to be defined for the purpose of
Counter32, Integer32, experimentation and evaluation.
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE,
OBJECT-IDENTITY, mib-2
FROM SNMPv2-SMI
TruthValue, TEXTUAL-CONVENTION
FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF;
mauMod MODULE-IDENTITY 1.1. Object Definitions
LAST-UPDATED "9702280000Z"
ORGANIZATION "IETF HUB MIB Working Group"
CONTACT-INFO
"WG E-mail: hubmib@hprnd.rose.hp.com
Chair: Dan Romascanu Managed objects are accessed via a virtual information store, termed
Postal: Madge Networks (Israel) Ltd. the Management Information Base or MIB. Objects in the MIB are
Atidim Technology Park, Bldg. 3 defined using the subset of Abstract Syntax Notation One (ASN.1)
Tel Aviv 61131, Israel defined in the SMI. In particular, each object type is named by an
Tel: 972-3-6458414, 6458458 OBJECT IDENTIFIER, an administratively assigned name. The object
Fax: 972-3-6487146 type together with an object instance serves to uniquely identify a
E-mail: dromasca@madge.com specific instantiation of the object. For human convenience, we
often use a textual string, termed the descriptor, to refer to the
object type.
Editor: Kathryn de Graaf 2. Overview
Postal: 3Com Corporation
118 Turnpike Rd.
Southborough, MA 01772
USA
Tel: (508)229-1627
Fax: (508)490-5882
E-mail: kdegraaf@isd.3com.com"
DESCRIPTION
"Management information for 802.3 MAUs.
The following references are used throughout this 2.1. Relationship to RFC 1515
MIB module:
[IEEE 802.3 Std] This MIB is intended to be a superset of that defined by RFC 1515
refers to IEEE 802.3/ISO 8802-3 Information [11], which will go to historic status. This MIB includes all of the
objects contained in that MIB, plus several new ones which provide
additional capabilities. Implementors are encouraged to support all
applicable conformance groups in order to make the best use of the
new functionality provided by this MIB. The new objects provide
management support for:
, o management of 100 Mb/s devices
processing systems - Local area networks -
Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method
and physical layer specifications (1993),
and to IEEE Std 802.3u-1995, Supplement to
IEEE Std 802.3, clauses 22 through 29.
[IEEE 802.3 Mgt] o auto-negotiation on interface MAUs
refers to IEEE 802.3u-1995, - 10 Mb/s &
100 Mb/s Management, Section 30 -
Supplement to IEEE Std 802.3."
::= { snmpDot3MauMgt 6 }
snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } o jack management
-- textual conventions 2.2. MAU Management
JackType ::= TEXTUAL-CONVENTION Instances of these object types represent attributes of an IEEE 802.3
STATUS current MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD
DESCRIPTION standard [1] and [2]. These MAUs may be connected to IEEE 802.3
"Common enumeration values for repeater and repeaters or to 802.3 (Ethernet-like) interfaces. For convenience
interface MAU jack types." this document refers to these devices as "repeater MAUs" and
SYNTAX INTEGER { "interface MAUs."
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)
}
dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } The definitions presented here are based on Section 30.5, "Layer
dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } Management for 10 & 100 Mb/s Medium Attachment Units (MAUs)", and
dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } Annex 30A, "GDMO Specifications for 802.3 managed objects" of IEEE
Std 802.3u-1995. That specification includes definitions for both
10Mb/s and 100Mb/s devices, and is essentially a superset of the
10Mb/s definitions given by IEEE 802.3 Section 20. This
specification is intended to serve the same purpose: to provide for
management of both 10Mb/s and 100Mb/s MAUs.
dot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } 2.3. Relationship to Other MIBs
, It is assumed that an agent implementing this MIB will also implement
-- object identities for MAU types (at least) the 'system' group defined in MIB-II [5]. The following
-- (see rpMauType and ifMauType for usage) sections identify other MIBs that such an agent should implement.
dot3MauType 2.3.1. Relationship to the MIB-II 'interfaces' group
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 }
dot3MauTypeAUI OBJECT-IDENTITY The sections of this document that define interface MAU-related
STATUS current objects specify an extension to the 'interfaces' group of MIB-II. An
DESCRIPTION agent implementing these interface-MAU related objects must also
"no internal MAU, view from AUI" implement the 'interfaces' group of MIB-II. The value of the object
::= { dot3MauType 1 } ifMauIfIndex is the same as the value of 'ifIndex' used to
instantiate the interface to which the given MAU is connected.
dot3MauType10Base5 OBJECT-IDENTITY It is expected that an agent implementing the interface-MAU related
STATUS current objects in this MIB will also implement the Ethernet- like Interfaces
DESCRIPTION MIB, RFC 1650.
"thick coax MAU (per 802.3 section 8)"
::= { dot3MauType 2 }
dot3MauTypeFoirl OBJECT-IDENTITY (Note that repeater ports are not represented as interfaces in the
STATUS current sense of MIB-II's 'interfaces' group.)
DESCRIPTION
"FOIRL MAU (per 802.3 section 9.9)"
::= { dot3MauType 3 }
dot3MauType10Base2 OBJECT-IDENTITY 2.3.2. Relationship to the 802.3 Repeater MIB
STATUS current
DESCRIPTION
"thin coax MAU (per 802.3 section 10)"
::= { dot3MauType 4 }
dot3MauType10BaseT OBJECT-IDENTITY The section of this document that defines repeater MAU-related
STATUS current objects specifies an extension to the 802.3 Repeater MIB defined in
DESCRIPTION [4]. An agent implementing these repeater-MAU related objects must
"UTP MAU (per 802.3 section 14)" also implement the 802.3 Repeater MIB.
::= { dot3MauType 5 }
dot3MauType10BaseFP OBJECT-IDENTITY The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to
STATUS current instantiate a repeater MAU variable shall be the same as the values
DESCRIPTION of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the
"passive fiber MAU (per 802.3 section 16)" port to which the given MAU is connected.
::= { dot3MauType 6 }
dot3MauType10BaseFB OBJECT-IDENTITY 2.4. Management of Internal MAUs
STATUS current
DESCRIPTION
, In some situations, a MAU can be "internal" -- i.e., its
"sync fiber MAU (per 802.3 section 17)" functionality is implemented entirely within a device. For example,
::= { dot3MauType 7 } a managed repeater may contain an internal repeater- MAU and/or an
internal interface-MAU through which management communications
originating on one of the repeater's external ports pass in order to
reach the management agent associated with the repeater. Such
internal MAUs may or may not be managed. If they are managed,
objects describing their attributes should appear in the appropriate
MIB subtree:
dot3MauType10BaseFL OBJECT-IDENTITY dot3RpMauBasicGroup for internal repeater-MAUs and
STATUS current dot3IfMauBasicGroup for internal interface-MAUs.
DESCRIPTION
"async fiber MAU (per 802.3 section 18)"
::= { dot3MauType 8 }
dot3MauType10Broad36 OBJECT-IDENTITY 3. Definitions
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: MAU-MIB DEFINITIONS ::= BEGIN
dot3MauType10BaseTHD OBJECT-IDENTITY IMPORTS
STATUS current Counter32, Integer32,
DESCRIPTION OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE,
"UTP MAU (per 802.3 section 14), half duplex mode" OBJECT-IDENTITY, mib-2
::= { dot3MauType 10 } FROM SNMPv2-SMI
TruthValue, TEXTUAL-CONVENTION
FROM SNMPv2-TC
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP
FROM SNMPv2-CONF;
dot3MauType10BaseTFD OBJECT-IDENTITY mauMod MODULE-IDENTITY
STATUS current LAST-UPDATED "9710310000Z"
DESCRIPTION ORGANIZATION "IETF HUB MIB Working Group"
"UTP MAU (per 802.3 section 14), full duplex mode" CONTACT-INFO
::= { dot3MauType 11 } "WG E-mail: hubmib@hprnd.rose.hp.com
dot3MauType10BaseFLHD OBJECT-IDENTITY Chair: Dan Romascanu
STATUS current Postal: Madge Networks (Israel) Ltd.
DESCRIPTION Atidim Technology Park, Bldg. 3
"async fiber MAU (per 802.3 section 18), half Tel Aviv 61131, Israel
duplex mode" Tel: 972-3-6458414, 6458458
::= { dot3MauType 12 } Fax: 972-3-6487146
E-mail: dromasca@madge.com
dot3MauType10BaseFLFD OBJECT-IDENTITY Editor: Kathryn de Graaf
STATUS current Postal: 3Com Corporation
DESCRIPTION 118 Turnpike Rd.
"async fiber MAU (per 802.3 section 18), full Southborough, MA 01772
duplex mode" USA
::= { dot3MauType 13 } Tel: (508)229-1627
Fax: (508)490-5882
E-mail: kdegraaf@isd.3com.com"
DESCRIPTION
"Management information for 802.3 MAUs.
, The following references are used throughout this
MIB module:
dot3MauType100BaseT4 OBJECT-IDENTITY [IEEE 802.3 Std]
STATUS current refers to IEEE 802.3/ISO 8802-3 Information
DESCRIPTION processing systems - Local area networks -
"4 pair categ. 3 UTP (per 802.3 section 23)" Part 3: Carrier sense multiple access with
::= { dot3MauType 14 } collision detection (CSMA/CD) access method
and physical layer specifications (1993),
and to IEEE Std 802.3u-1995, Supplement to
IEEE Std 802.3, clauses 22 through 29.
dot3MauType100BaseTXHD OBJECT-IDENTITY [IEEE 802.3 Mgt]
STATUS current refers to IEEE 802.3u-1995, - 10 Mb/s &
DESCRIPTION 100 Mb/s Management, Section 30 -
"2 pair categ. 5 UTP (per 802.3 section 25), half Supplement to IEEE Std 802.3."
duplex mode" ::= { snmpDot3MauMgt 6 }
::= { dot3MauType 15 }
dot3MauType100BaseTXFD OBJECT-IDENTITY snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 }
STATUS current
DESCRIPTION
"2 pair categ. 5 UTP (per 802.3 section 25), full
duplex mode"
::= { dot3MauType 16 }
dot3MauType100BaseFXHD OBJECT-IDENTITY -- textual conventions
STATUS current
DESCRIPTION
"X fiber over PMT (per 802.3 section 26), half
duplex mode"
::= { dot3MauType 17 }
dot3MauType100BaseFXFD OBJECT-IDENTITY JackType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"X fiber over PMT (per 802.3 section 26), full "Common enumeration values for repeater and
duplex mode" interface MAU jack types."
::= { dot3MauType 18 } 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)
}
dot3MauType100BaseT2HD OBJECT-IDENTITY dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
STATUS current dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
DESCRIPTION dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
"2 pair categ. 3 UTP (per 802.3 section 32), half
duplex mode"
::= { dot3MauType 19 }
dot3MauType100BaseT2FD OBJECT-IDENTITY dot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
STATUS current
DESCRIPTION
"2 pair categ. 3 UTP (per 802.3 section 32), full
, -- object identities for MAU types
duplex mode" -- (see rpMauType and ifMauType for usage)
::= { dot3MauType 20 }
-- dot3MauType
-- The Basic Repeater MAU Table OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 }
--
rpMauTable OBJECT-TYPE dot3MauTypeAUI OBJECT-IDENTITY
SYNTAX SEQUENCE OF RpMauEntry STATUS current
MAX-ACCESS not-accessible DESCRIPTION
STATUS current "no internal MAU, view from AUI"
DESCRIPTION ::= { dot3MauType 1 }
"Table of descriptive and status information about
the MAU(s) attached to the ports of a repeater."
::= { dot3RpMauBasicGroup 1 }
rpMauEntry OBJECT-TYPE dot3MauType10Base5 OBJECT-IDENTITY
SYNTAX RpMauEntry STATUS current
MAX-ACCESS not-accessible DESCRIPTION
STATUS current "thick coax MAU (per 802.3 section 8)"
DESCRIPTION ::= { dot3MauType 2 }
"An entry in the table, containing information
about a single MAU."
INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex }
::= { rpMauTable 1 }
RpMauEntry ::= dot3MauTypeFoirl OBJECT-IDENTITY
SEQUENCE { STATUS current
rpMauGroupIndex DESCRIPTION
Integer32, "FOIRL MAU (per 802.3 section 9.9)"
rpMauPortIndex ::= { dot3MauType 3 }
Integer32,
rpMauIndex
Integer32,
rpMauType
OBJECT IDENTIFIER,
rpMauStatus
INTEGER,
rpMauMediaAvailable
INTEGER,
rpMauMediaAvailableStateExits
Counter32,
rpMauJabberState
INTEGER,
, dot3MauType10Base2 OBJECT-IDENTITY
STATUS current
DESCRIPTION
"thin coax MAU (per 802.3 section 10)"
::= { dot3MauType 4 }
rpMauJabberingStateEnters dot3MauType10BaseT OBJECT-IDENTITY
Counter32, STATUS current
rpMauFalseCarriers DESCRIPTION
Counter32 "UTP MAU (per 802.3 section 14)"
} ::= { dot3MauType 5 }
rpMauGroupIndex OBJECT-TYPE dot3MauType10BaseFP OBJECT-IDENTITY
SYNTAX Integer32 (1..2147483647) STATUS current
MAX-ACCESS read-only DESCRIPTION
STATUS current "passive fiber MAU (per 802.3 section 16)"
DESCRIPTION ::= { dot3MauType 6 }
"This variable uniquely identifies the group
containing the port to which the MAU described by
this entry is connected.
Note: In practice, a group will generally be a dot3MauType10BaseFB OBJECT-IDENTITY
field-replaceable unit (i.e., module, card, or STATUS current
board) that can fit in the physical system DESCRIPTION
enclosure, and the group number will correspond to "sync fiber MAU (per 802.3 section 17)"
a number marked on the physical enclosure. ::= { dot3MauType 7 }
The group denoted by a particular value of this dot3MauType10BaseFL OBJECT-IDENTITY
object is the same as the group denoted by the STATUS current
same value of rptrGroupIndex." DESCRIPTION
::= { rpMauEntry 1 } "async fiber MAU (per 802.3 section 18)"
::= { dot3MauType 8 }
rpMauPortIndex OBJECT-TYPE dot3MauType10Broad36 OBJECT-IDENTITY
SYNTAX Integer32 (1..2147483647) STATUS current
MAX-ACCESS read-only DESCRIPTION
STATUS current "broadband DTE MAU (per 802.3 section 11). Note
DESCRIPTION that 10BROAD36 MAUs can be attached to interfaces
"This variable uniquely identifies the repeater but not to repeaters."
port within group rpMauGroupIndex to which the MAU ::= { dot3MauType 9 }
described by this entry is connected."
REFERENCE
"Reference RFC 1516, rptrPortIndex."
::= { rpMauEntry 2 }
rpMauIndex OBJECT-TYPE ------ new since RFC 1515:
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
, dot3MauType10BaseTHD OBJECT-IDENTITY
connected to the same port (rpMauPortIndex)." STATUS current
REFERENCE DESCRIPTION
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." "UTP MAU (per 802.3 section 14), half duplex mode"
::= { rpMauEntry 3 } ::= { dot3MauType 10 }
rpMauType OBJECT-TYPE dot3MauType10BaseTFD OBJECT-IDENTITY
SYNTAX OBJECT IDENTIFIER STATUS current
MAX-ACCESS read-only DESCRIPTION
STATUS current "UTP MAU (per 802.3 section 14), full duplex mode"
DESCRIPTION ::= { dot3MauType 11 }
"This object identifies the 10 or 100 Mb/s
baseband 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
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } dot3MauType10BaseFLHD OBJECT-IDENTITY
STATUS current
DESCRIPTION
"async fiber MAU (per 802.3 section 18), half
duplex mode"
::= { dot3MauType 12 }
is returned. Note that unknownMauType is a dot3MauType10BaseFLFD OBJECT-IDENTITY
syntactically valid object identifier, and any STATUS current
conformant implementation of ASN.1 and the BER DESCRIPTION
must be able to generate and recognize this "async fiber MAU (per 802.3 section 18), full
value." duplex mode"
REFERENCE ::= { dot3MauType 13 }
"[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
::= { rpMauEntry 4 }
rpMauStatus OBJECT-TYPE dot3MauType100BaseT4 OBJECT-IDENTITY
SYNTAX INTEGER { STATUS current
other(1), DESCRIPTION
unknown(2), "4 pair categ. 3 UTP (per 802.3 section 23)"
operational(3), ::= { dot3MauType 14 }
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
, dot3MauType100BaseTXHD OBJECT-IDENTITY
enumerated values. STATUS current
DESCRIPTION
"2 pair categ. 5 UTP (per 802.3 section 25), half
duplex mode"
::= { dot3MauType 15 }
The value other(1) is returned if the MAU is in a dot3MauType100BaseTXFD OBJECT-IDENTITY
state other than one of the states 2 through 6. STATUS current
DESCRIPTION
"2 pair categ. 5 UTP (per 802.3 section 25), full
duplex mode"
::= { dot3MauType 16 }
The value unknown(2) is returned when the MAU's dot3MauType100BaseFXHD OBJECT-IDENTITY
true state is unknown; for example, when it is STATUS current
being initialized. DESCRIPTION
"X fiber over PMT (per 802.3 section 26), half
duplex mode"
::= { dot3MauType 17 }
A MAU in the operational(3) state is fully dot3MauType100BaseFXFD OBJECT-IDENTITY
functional, operates, and passes signals to its STATUS current
attached DTE or repeater port in accordance to its DESCRIPTION
specification. "X fiber over PMT (per 802.3 section 26), full
duplex mode"
::= { dot3MauType 18 }
A MAU in standby(4) state forces DI and CI to idle dot3MauType100BaseT2HD OBJECT-IDENTITY
and the media transmitter to idle or fault, if STATUS current
supported. Standby(4) mode only applies to link DESCRIPTION
type MAUs. The state of rpMauMediaAvailable is "2 pair categ. 3 UTP (per 802.3 section 32), half
unaffected. duplex mode"
::= { dot3MauType 19 }
A MAU in shutdown(5) state assumes the same dot3MauType100BaseT2FD OBJECT-IDENTITY
condition on DI, CI, and the media transmitter as STATUS current
though it were powered down or not connected. The DESCRIPTION
MAU may return other(1) value for the "2 pair categ. 3 UTP (per 802.3 section 32), full
rpMauJabberState and rpMauMediaAvailable objects duplex mode"
when it is in this state. For an AUI, this state ::= { dot3MauType 20 }
will remove power from the AUI.
Setting this variable to the value reset(6) resets --
the MAU in the same manner as a power-off, power- -- The Basic Repeater MAU Table
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 operational(3), rpMauTable OBJECT-TYPE
standby(4), or shutdown(5) causes the MAU to SYNTAX SEQUENCE OF RpMauEntry
assume the respective state except that setting a MAX-ACCESS not-accessible
mixing-type MAU or an AUI to standby(4) will cause STATUS current
the MAU to enter the shutdown state." DESCRIPTION
REFERENCE "Table of descriptive and status information about
"[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, the MAU(s) attached to the ports of a repeater."
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, ::= { dot3RpMauBasicGroup 1 }
acRESETMAU."
::= { rpMauEntry 5 }
, rpMauEntry OBJECT-TYPE
SYNTAX RpMauEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single MAU."
INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex }
::= { rpMauTable 1 }
rpMauMediaAvailable OBJECT-TYPE RpMauEntry ::=
SYNTAX INTEGER { SEQUENCE {
other(1), rpMauGroupIndex
unknown(2), Integer32,
available(3), rpMauPortIndex
notAvailable(4), Integer32,
remoteFault(5), rpMauIndex
invalidSignal(6), Integer32,
remoteJabber(7), rpMauType
remoteLinkLoss(8), OBJECT IDENTIFIER,
remoteTest(9) rpMauStatus
} INTEGER,
MAX-ACCESS read-only rpMauMediaAvailable
STATUS current INTEGER,
DESCRIPTION rpMauMediaAvailableStateExits
"If the MAU is a link or fiber type (FOIRL, Counter32,
10BASE-T, 10BASE-F) then this is equivalent to the rpMauJabberState
link test fail state/low light function. For an INTEGER,
AUI or a coax (including broadband) MAU this rpMauJabberingStateEnters
indicates whether or not loopback is detected on Counter32,
the DI circuit. The value of this attribute rpMauFalseCarriers
persists between packets for MAU types AUI, Counter32
10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. }
The value other(1) is returned if the rpMauGroupIndex OBJECT-TYPE
mediaAvailable state is not one of 2 through 6. SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the group
containing the port to which the MAU described by
this entry is connected.
The value unknown(2) is returned when the MAU's Note: In practice, a group will generally be a
true state is unknown; for example, when it is field-replaceable unit (i.e., module, card, or
being initialized. At power-up or following a board) that can fit in the physical system
reset, the value of this attribute will be unknown enclosure, and the group number will correspond to
for AUI, coax, and 10BASE-FP MAUs. For these MAUs a number marked on the physical enclosure.
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.
For 100BASE-T4, 100BASE-TX and 100BASE-FX the The group denoted by a particular value of this
enumerations match the states within the object is the same as the group denoted by the
respective link integrity state diagrams, fig 23- same value of rptrGroupIndex."
12 and 24-15 of sections 23 and 24 of [2]. Any ::= { rpMauEntry 1 }
, rpMauPortIndex OBJECT-TYPE
MAU which implements management of auto- SYNTAX Integer32 (1..2147483647)
negotiation will map remote fault indication to MAX-ACCESS read-only
remote fault. 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 1516, rptrPortIndex."
::= { rpMauEntry 2 }
The value available(3) indicates that the link, rpMauIndex OBJECT-TYPE
light, or loopback is normal. The value SYNTAX Integer32 (1..2147483647)
notAvailable(4) indicates link loss, low light, or MAX-ACCESS read-only
no loopback. STATUS current
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 Mgt], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 }
The value remoteFault(5) indicates that a fault rpMauType OBJECT-TYPE
has been detected at the remote end of the link. SYNTAX OBJECT IDENTIFIER
This value applies to 10BASE-FB, 100BASE-T4 Far MAX-ACCESS read-only
End Fault Indication and non-specified remote STATUS current
faults from a system running auto-negotiation. DESCRIPTION
The values remoteJabber(7), remoteLinkLoss(8), and "This object identifies the 10 or 100 Mb/s
remoteTest(9) should be used instead of baseband MAU type. An initial set of MAU types
remoteFault(5) where the reason for remote fault are defined above. The assignment of OBJECT
is identified in the remote signaling protocol. IDENTIFIERs to new types of MAUs is managed by the
IANA. If the MAU type is unknown, the object
identifier
The value invalidSignal(6) indicates that an unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
invalid signal has been received from the other
end of the link. InvalidSignal(6) applies only to
MAUs of type 10BASE-FB.
Where an IEEE Std 802.3u-1995 clause 22 MII is is returned. Note that unknownMauType is a
present, a logic one in the remote fault bit syntactically valid object identifier, and any
(reference section 22.2.4.2.8 of that document) conformant implementation of ASN.1 and the BER
maps to the value remoteFault(5), and a logic zero must be able to generate and recognize this
in the link status bit (reference section value."
22.2.4.2.10 of that document) maps to the value REFERENCE
notAvailable(4). The value notAvailable(4) takes "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
precedence over the value remoteFault(5)." ::= { rpMauEntry 4 }
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
::= { rpMauEntry 6 }
rpMauMediaAvailableStateExits OBJECT-TYPE rpMauStatus OBJECT-TYPE
SYNTAX Counter32 SYNTAX INTEGER {
MAX-ACCESS read-only other(1),
STATUS current unknown(2),
DESCRIPTION operational(3),
"A count of the number of times that standby(4),
rpMauMediaAvailable for this MAU instance leaves shutdown(5),
the state available(3)." reset(6)
REFERENCE }
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
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." state other than one of the states 2 through 6.
::= { rpMauEntry 7 }
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 A MAU in the operational(3) state is fully
true state is unknown; for example, when it is functional, operates, and passes signals to its
being initialized. attached DTE or repeater port in accordance to its
specification.
If the MAU is not jabbering the agent returns A MAU in standby(4) state forces DI and CI to idle
noJabber(3). This is the 'normal' state. and the media transmitter to idle or fault, if
supported. Standby(4) mode only applies to link
type MAUs. The state of rpMauMediaAvailable is
unaffected.
If the MAU is in jabber state the agent returns A MAU in shutdown(5) state assumes the same
the jabbering(4) value." condition on DI, CI, and the media transmitter as
REFERENCE though it were powered down or not connected. The
"[IEEE 802.3 Mgt], 30.5.1.1.6, MAU may return other(1) value for the
aJabber.jabberFlag." rpMauJabberState and rpMauMediaAvailable objects
::= { rpMauEntry 8 } when it is in this state. For an AUI, this state
will remove power from the AUI.
rpMauJabberingStateEnters OBJECT-TYPE Setting this variable to the value reset(6) resets
SYNTAX Counter32 the MAU in the same manner as a power-off, power-
MAX-ACCESS read-only on cycle of at least one-half second would. The
STATUS current agent is not required to return the value reset
DESCRIPTION (6).
"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, and dot3MauType100BaseFX,
this counter will always indicate zero."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberCounter."
, Setting this variable to the value 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 Mgt], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acRESETMAU."
::= { rpMauEntry 5 }
::= { rpMauEntry 9 } rpMauMediaAvailable OBJECT-TYPE
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9)
}
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.
rpMauFalseCarriers OBJECT-TYPE The value other(1) is returned if the
SYNTAX Counter32 mediaAvailable state is not one of 2 through 6.
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 The value unknown(2) is returned when the MAU's
dot3MauType100BaseT4, dot3MauType100BaseTX, and true state is unknown; for example, when it is
dot3MauType100BaseFX. For all other MAU types, being initialized. At power-up or following a
this counter will always indicate zero. 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 approximate minimum time for rollover of this For 100BASE-T4, 100BASE-TX and 100BASE-FX the
counter is 7.4 hours." enumerations match the states within the
REFERENCE respective link integrity state diagrams, fig 23-
"[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." 12 and 24-15 of sections 23 and 24 of [2]. Any
::= { rpMauEntry 10 } MAU which implements management of auto-
negotiation will map remote fault indication to
remote fault.
-- The rpJackTable applies to MAUs attached to repeaters The value available(3) indicates that the link,
-- which have one or more external jacks (connectors). light, or loopback is normal. The value
notAvailable(4) indicates link loss, low light, or
no loopback.
rpJackTable OBJECT-TYPE The value remoteFault(5) indicates that a fault
SYNTAX SEQUENCE OF RpJackEntry has been detected at the remote end of the link.
MAX-ACCESS not-accessible This value applies to 10BASE-FB, 100BASE-T4 Far
STATUS current End Fault Indication and non-specified remote
DESCRIPTION faults from a system running auto-negotiation.
"Information about the external jacks attached to The values remoteJabber(7), remoteLinkLoss(8), and
MAUs attached to the ports of a repeater." remoteTest(9) should be used instead of
::= { dot3RpMauBasicGroup 2 } remoteFault(5) where the reason for remote fault
is identified in the remote signaling protocol.
rpJackEntry OBJECT-TYPE The value invalidSignal(6) indicates that an
SYNTAX RpJackEntry invalid signal has been received from the other
MAX-ACCESS not-accessible end of the link. InvalidSignal(6) applies only to
STATUS current MAUs of type 10BASE-FB.
DESCRIPTION
"An entry in the table, containing information
about a particular jack."
, Where an IEEE Std 802.3u-1995 clause 22 MII is
present, a logic one in the remote fault bit
(reference section 22.2.4.2.8 of that document)
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)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
::= { rpMauEntry 6 }
INDEX { rpMauGroupIndex, rpMauMediaAvailableStateExits OBJECT-TYPE
rpMauPortIndex, SYNTAX Counter32
rpMauIndex, MAX-ACCESS read-only
rpJackIndex } STATUS current
::= { rpJackTable 1 } DESCRIPTION
"A count of the number of times that
rpMauMediaAvailable for this MAU instance leaves
the state available(3)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter."
::= { rpMauEntry 7 }
RpJackEntry ::= rpMauJabberState OBJECT-TYPE
SEQUENCE { SYNTAX INTEGER {
rpJackIndex other(1),
Integer32, unknown(2),
rpJackType noJabber(3),
JackType 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.
rpJackIndex OBJECT-TYPE The value unknown(2) is returned when the MAU's
SYNTAX Integer32 (1..2147483647) true state is unknown; for example, when it is
MAX-ACCESS not-accessible being initialized.
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 }
rpJackType OBJECT-TYPE If the MAU is not jabbering the agent returns
SYNTAX JackType noJabber(3). This is the 'normal' state.
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The jack connector type, as it appears on the
outside of the system."
::= { rpJackEntry 2 }
-- If the MAU is in jabber state the agent returns
-- The Basic Interface MAU Table the jabbering(4) value."
-- REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberFlag."
::= { rpMauEntry 8 }
ifMauTable OBJECT-TYPE rpMauJabberingStateEnters OBJECT-TYPE
SYNTAX SEQUENCE OF IfMauEntry SYNTAX Counter32
MAX-ACCESS not-accessible MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table of descriptive and status information about "A count of the number of times that
MAU(s) attached to an interface." mauJabberState for this MAU instance enters the
state jabbering(4). For MAUs of type
dot3MauTypeAUI, dot3MauType100BaseT4,
dot3MauType100BaseTX, and dot3MauType100BaseFX,
this counter will always indicate zero."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberCounter."
, ::= { rpMauEntry 9 }
::= { dot3IfMauBasicGroup 1 } rpMauFalseCarriers OBJECT-TYPE
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.
ifMauEntry OBJECT-TYPE This counter increments only for MAUs of type
SYNTAX IfMauEntry dot3MauType100BaseT4, dot3MauType100BaseTX, and
MAX-ACCESS not-accessible dot3MauType100BaseFX. For all other MAU types,
STATUS current this counter will always indicate zero.
DESCRIPTION
"An entry in the table, containing information
about a single MAU."
INDEX { ifMauIfIndex, ifMauIndex }
::= { ifMauTable 1 }
IfMauEntry ::= The approximate minimum time for rollover of this
SEQUENCE { counter is 7.4 hours."
ifMauIfIndex REFERENCE
Integer32, "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers."
ifMauIndex ::= { rpMauEntry 10 }
Integer32,
ifMauType
OBJECT IDENTIFIER,
ifMauStatus
INTEGER,
ifMauMediaAvailable
INTEGER,
ifMauMediaAvailableStateExits
Counter32,
ifMauJabberState
INTEGER,
ifMauJabberingStateEnters
Counter32,
ifMauFalseCarriers
Counter32,
ifMauTypeList
Integer32,
ifMauDefaultType
OBJECT IDENTIFIER,
ifMauAutoNegSupported
TruthValue
}
ifMauIfIndex OBJECT-TYPE -- The rpJackTable applies to MAUs attached to repeaters
SYNTAX Integer32 (1..2147483647) -- which have one or more external jacks (connectors).
MAX-ACCESS read-only
STATUS current
DESCRIPTION
, rpJackTable OBJECT-TYPE
"This variable uniquely identifies the interface SYNTAX SEQUENCE OF RpJackEntry
to which the MAU described by this entry is MAX-ACCESS not-accessible
connected." STATUS current
REFERENCE DESCRIPTION
"RFC 1213, ifIndex" "Information about the external jacks attached to
::= { ifMauEntry 1 } MAUs attached to the ports of a repeater."
::= { dot3RpMauBasicGroup 2 }
ifMauIndex OBJECT-TYPE rpJackEntry OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX RpJackEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable uniquely identifies the MAU "An entry in the table, containing information
described by this entry from among other MAUs about a particular jack."
connected to the same interface (ifMauIfIndex)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID."
::= { ifMauEntry 2 }
ifMauType OBJECT-TYPE INDEX { rpMauGroupIndex,
SYNTAX OBJECT IDENTIFIER rpMauPortIndex,
MAX-ACCESS read-only rpMauIndex,
STATUS current rpJackIndex }
DESCRIPTION ::= { rpJackTable 1 }
"This object identifies the 10 or 100 Mb/s
baseband or broadband 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
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } RpJackEntry ::=
SEQUENCE {
rpJackIndex
Integer32,
rpJackType
JackType
}
is returned. Note that unknownMauType is a rpJackIndex OBJECT-TYPE
syntactically valid object identifier, and any SYNTAX Integer32 (1..2147483647)
conformant implementation of ASN.1 and the BER MAX-ACCESS not-accessible
must be able to generate and recognize this value. 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 }
This object represents the operational type of the rpJackType OBJECT-TYPE
MAU, as determined by either (1) the result of the SYNTAX JackType
auto-negotiation function or (2) if auto- MAX-ACCESS read-only
negotiation is not enabled or is not implemented STATUS current
for this MAU, by the value of the object DESCRIPTION
ifMauDefaultType. In case (2), a set to the "The jack connector type, as it appears on the
object ifMauDefaultType will force the MAU into outside of the system."
::= { rpJackEntry 2 }
, --
the new operating mode." -- The Basic Interface MAU Table
REFERENCE --
"[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
::= { ifMauEntry 3 }
ifMauStatus OBJECT-TYPE ifMauTable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX SEQUENCE OF IfMauEntry
other(1), MAX-ACCESS not-accessible
unknown(2), STATUS current
operational(3), DESCRIPTION
standby(4), "Table of descriptive and status information about
shutdown(5), MAU(s) attached to an interface."
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 ::= { dot3IfMauBasicGroup 1 }
state other than one of the states 2 through 6.
The value unknown(2) is returned when the MAU's ifMauEntry OBJECT-TYPE
true state is unknown; for example, when it is SYNTAX IfMauEntry
being initialized. MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single MAU."
INDEX { ifMauIfIndex, ifMauIndex }
::= { ifMauTable 1 }
A MAU in the operational(3) state is fully IfMauEntry ::=
functional, operates, and passes signals to its SEQUENCE {
attached DTE or repeater port in accordance to its ifMauIfIndex
specification. Integer32,
ifMauIndex
Integer32,
ifMauType
OBJECT IDENTIFIER,
ifMauStatus
INTEGER,
ifMauMediaAvailable
INTEGER,
ifMauMediaAvailableStateExits
Counter32,
ifMauJabberState
INTEGER,
ifMauJabberingStateEnters
Counter32,
ifMauFalseCarriers
Counter32,
ifMauTypeList
Integer32,
ifMauDefaultType
OBJECT IDENTIFIER,
ifMauAutoNegSupported
TruthValue
}
A MAU in standby(4) state forces DI and CI to idle ifMauIfIndex OBJECT-TYPE
and the media transmitter to idle or fault, if SYNTAX Integer32 (1..2147483647)
supported. Standby(4) mode only applies to link MAX-ACCESS read-only
type MAUs. The state of ifMauMediaAvailable is STATUS current
unaffected. DESCRIPTION
"This variable uniquely identifies the interface
to which the MAU described by this entry is
connected."
REFERENCE
"RFC 1213, ifIndex"
::= { ifMauEntry 1 }
A MAU in shutdown(5) state assumes the same ifMauIndex OBJECT-TYPE
condition on DI, CI, and the media transmitter as SYNTAX Integer32 (1..2147483647)
though it were powered down or not connected. The 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 Mgt], 30.5.1.1.1, aMAUID."
::= { ifMauEntry 2 }
, ifMauType OBJECT-TYPE
MAU may return other(1) value for the SYNTAX OBJECT IDENTIFIER
ifMauJabberState and ifMauMediaAvailable objects MAX-ACCESS read-only
when it is in this state. For an AUI, this state STATUS current
will remove power from the AUI. DESCRIPTION
"This object identifies the 10 or 100 Mb/s
baseband or broadband 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
Setting this variable to the value reset(6) resets unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
the MAU in the same manner as a 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 operational(3), is returned. Note that unknownMauType is a
standby(4), or shutdown(5) causes the MAU to syntactically valid object identifier, and any
assume the respective state except that setting a conformant implementation of ASN.1 and the BER
mixing-type MAU or an AUI to standby(4) will cause must be able to generate and recognize this value.
the MAU to enter the shutdown state."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acRESETMAU."
::= { ifMauEntry 4 }
ifMauMediaAvailable OBJECT-TYPE This object represents the operational type of the
SYNTAX INTEGER { MAU, as determined by either (1) the result of the
other(1), auto-negotiation function or (2) if auto-
unknown(2), negotiation is not enabled or is not implemented
available(3), for this MAU, by the value of the object
notAvailable(4), ifMauDefaultType. In case (2), a set to the
remoteFault(5), object ifMauDefaultType will force the MAU into
invalidSignal(6), the new operating mode."
remoteJabber(7), REFERENCE
remoteLinkLoss(8), "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
remoteTest(9) ::= { ifMauEntry 3 }
}
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.
, ifMauStatus OBJECT-TYPE
The value other(1) is returned if the SYNTAX INTEGER {
mediaAvailable state is not one of 2 through 6. 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.
The value unknown(2) is returned when the MAU's The value other(1) is returned if the MAU is in a
true state is unknown; for example, when it is state other than one of the states 2 through 6.
being initialized. At power-up or following a
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.
For 100BASE-T4, 100BASE-TX and 100BASE-FX the The value unknown(2) is returned when the MAU's
enumerations match the states within the true state is unknown; for example, when it is
respective link integrity state diagrams, fig 23- being initialized.
12 and 24-15 of sections 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, A MAU in the operational(3) state is fully
light, or loopback is normal. The value functional, operates, and passes signals to its
notAvailable(4) indicates link loss, low light, or attached DTE or repeater port in accordance to its
no loopback. specification.
The value remoteFault(5) indicates that a fault A MAU in standby(4) state forces DI and CI to idle
has been detected at the remote end of the link. and the media transmitter to idle or fault, if
This value applies to 10BASE-FB, 100BASE-T4 Far supported. Standby(4) mode only applies to link
End Fault Indication and non-specified remote type MAUs. The state of ifMauMediaAvailable is
faults from a system running auto-negotiation. unaffected.
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 A MAU in shutdown(5) state assumes the same
invalid signal has been received from the other condition on DI, CI, and the media transmitter as
end of the link. InvalidSignal(6) applies only to though it were powered down or not connected. The
MAUs of type 10BASE-FB. MAU may return other(1) value for the
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) resets
Where an IEEE Std 802.3u-1995 clause 22 MII is the MAU in the same manner as a power-off, power-
present, a logic one in the remote fault bit on cycle of at least one-half second would. The
(reference section 22.2.4.2.8 of that document) agent is not required to return the value reset
maps to the value remoteFault(5), and a logic zero (6).
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)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
::= { ifMauEntry 5 }
ifMauMediaAvailableStateExits OBJECT-TYPE Setting this variable to the value operational(3),
SYNTAX Counter32 standby(4), or shutdown(5) causes the MAU to
MAX-ACCESS read-only assume the respective state except that setting a
STATUS current mixing-type MAU or an AUI to standby(4) will cause
DESCRIPTION the MAU to enter the shutdown state."
"A count of the number of times that REFERENCE
ifMauMediaAvailable for this MAU instance leaves "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState,
the state available(3)." 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
REFERENCE acRESETMAU."
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." ::= { ifMauEntry 4 }
::= { ifMauEntry 6 }
ifMauJabberState OBJECT-TYPE ifMauMediaAvailable OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
noJabber(3), available(3),
jabbering(4) notAvailable(4),
} remoteFault(5),
MAX-ACCESS read-only invalidSignal(6),
STATUS current remoteJabber(7),
DESCRIPTION remoteLinkLoss(8),
"The value other(1) is returned if the jabber remoteTest(9)
state is not 2, 3, or 4. The agent must always }
return other(1) for MAU type dot3MauTypeAUI. 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 unknown(2) is returned when the MAU's The value other(1) is returned if the
true state is unknown; for example, when it is mediaAvailable state is not one of 2 through 6.
being initialized.
If the MAU is not jabbering the agent returns The value unknown(2) is returned when the MAU's
noJabber(3). This is the 'normal' state. true state is unknown; for example, when it is
being initialized. At power-up or following a
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.
, For 100BASE-T4, 100BASE-TX and 100BASE-FX the
If the MAU is in jabber state the agent returns enumerations match the states within the
the jabbering(4) value." respective link integrity state diagrams, fig 23-
REFERENCE 12 and 24-15 of sections 23 and 24 of [2]. Any
"[IEEE 802.3 Mgt], 30.5.1.1.6, MAU which implements management of auto-
aJabber.jabberFlag." negotiation will map remote fault indication to
::= { ifMauEntry 7 } remote fault.
ifMauJabberingStateEnters OBJECT-TYPE The value available(3) indicates that the link,
SYNTAX Counter32 light, or loopback is normal. The value
MAX-ACCESS read-only notAvailable(4) indicates link loss, low light, or
STATUS current no loopback.
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, and dot3MauType100BaseFX,
this counter will always indicate zero."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberCounter."
::= { ifMauEntry 8 }
ifMauFalseCarriers OBJECT-TYPE The value remoteFault(5) indicates that a fault
SYNTAX Counter32 has been detected at the remote end of the link.
MAX-ACCESS read-only This value applies to 10BASE-FB, 100BASE-T4 Far
STATUS current End Fault Indication and non-specified remote
DESCRIPTION faults from a system running auto-negotiation.
"A count of the number of false carrier events The values remoteJabber(7), remoteLinkLoss(8), and
during IDLE in 100BASE-X links. This counter does remoteTest(9) should be used instead of
not increment at the symbol rate. It can remoteFault(5) where the reason for remote fault
increment after a valid carrier completion at a is identified in the remote signaling protocol.
maximum rate of once per 100 ms until the next
carrier event.
This counter increments only for MAUs of type The value invalidSignal(6) indicates that an
dot3MauType100BaseT4, dot3MauType100BaseTX, and invalid signal has been received from the other
dot3MauType100BaseFX. For all other MAU types, end of the link. InvalidSignal(6) applies only to
this counter will always indicate zero. MAUs of type 10BASE-FB.
The approximate minimum time for rollover of this Where an IEEE Std 802.3u-1995 clause 22 MII is
counter is 7.4 hours." present, a logic one in the remote fault bit
REFERENCE (reference section 22.2.4.2.8 of that document)
"[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." maps to the value remoteFault(5), and a logic zero
::= { ifMauEntry 9 } 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)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
::= { ifMauEntry 5 }
, ifMauMediaAvailableStateExits OBJECT-TYPE
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)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter."
::= { ifMauEntry 6 }
ifMauTypeList OBJECT-TYPE ifMauJabberState OBJECT-TYPE
SYNTAX Integer32 SYNTAX INTEGER {
MAX-ACCESS read-only other(1),
STATUS current unknown(2),
DESCRIPTION noJabber(3),
"A value that uniquely identifies the set of jabbering(4)
possible IEEE 802.3 types that the MAU could be. }
The value is a sum which initially takes the value MAX-ACCESS read-only
zero. Then, for each type capability of this MAU, STATUS current
2 raised to the power noted below is added to the DESCRIPTION
sum. For example, a MAU which has the capability "The value other(1) is returned if the jabber
to be only 10BASE-T would have a value of 512 state is not 2, 3, or 4. The agent must always
(2**9). In contrast, a MAU which supports both return other(1) for MAU type dot3MauTypeAUI.
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 The value unknown(2) is returned when the MAU's
these: true state is unknown; for example, when it is
being initialized.
Power Capability If the MAU is not jabbering the agent returns
0 other or unknown noJabber(3). This is the 'normal' state.
1 AUI
2 10BASE-5
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 If the MAU is in jabber state the agent returns
object will map to ifMauAutoNegCapability." the jabbering(4) value."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberFlag."
::= { ifMauEntry 7 }
, ifMauJabberingStateEnters OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
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, and dot3MauType100BaseFX,
this counter will always indicate zero."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberCounter."
::= { ifMauEntry 10 } ::= { ifMauEntry 8 }
ifMauDefaultType OBJECT-TYPE ifMauFalseCarriers OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX Counter32
MAX-ACCESS read-write MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object identifies the default administrative "A count of the number of false carrier events
10 or 100 Mb/s baseband MAU type, to be used in during IDLE in 100BASE-X links. This counter does
conjunction with the operational MAU type denoted not increment at the symbol rate. It can
by ifMauType. increment after a valid carrier completion at a
maximum rate of once per 100 ms until the next
carrier event.
The set of possible values for this object is the This counter increments only for MAUs of type
same as the set defined for the ifMauType object. dot3MauType100BaseT4, dot3MauType100BaseTX, and
dot3MauType100BaseFX. For all other MAU types,
this counter will always indicate zero.
This object represents the administratively- The approximate minimum time for rollover of this
configured type of the MAU. If auto-negotiation counter is 7.4 hours."
is not enabled or is not implemented for this MAU, REFERENCE
the value of this object determines the "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers."
operational type of the MAU. In this case, a set ::= { ifMauEntry 9 }
to this object will force the MAU into the
specified operating mode.
If auto-negotiation is implemented and enabled for ifMauTypeList OBJECT-TYPE
this MAU, the operational type of the MAU is SYNTAX Integer32
determined by auto-negotiation, and the value of MAX-ACCESS read-only
this object denotes the type to which the MAU will STATUS current
automatically revert if/when auto-negotiation is DESCRIPTION
later disabled. "A value that uniquely identifies the set of
possible IEEE 802.3 types that the MAU could be.
The value is a sum which initially takes the value
zero. Then, for each type capability of this MAU,
2 raised to the power noted below is added to the
sum. For example, a MAU which has 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.
NOTE TO IMPLEMENTORS: It may be necessary to The powers of 2 assigned to the capabilities are
provide for underlying hardware implementations these:
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 Mgt], 30.5.1.1.1, aMAUID, and [IEEE
802.3 Std], 22.2.4.1.4."
::= { ifMauEntry 11 }
, Power Capability
0 other or unknown
1 AUI
2 10BASE-5
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
ifMauAutoNegSupported OBJECT-TYPE If auto-negotiation is present on this MAU, this
SYNTAX TruthValue object will map to ifMauAutoNegCapability."
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates whether or not auto-
negotiation is supported on this MAU."
::= { ifMauEntry 12 }
-- The ifJackTable applies to MAUs attached to interfaces ::= { ifMauEntry 10 }
-- which have one or more external jacks (connectors).
ifJackTable OBJECT-TYPE ifMauDefaultType OBJECT-TYPE
SYNTAX SEQUENCE OF IfJackEntry SYNTAX OBJECT IDENTIFIER
MAX-ACCESS not-accessible MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about the external jacks attached to "This object identifies the default administrative
MAUs attached to an interface." 10 or 100 Mb/s baseband MAU type, to be used in
::= { dot3IfMauBasicGroup 2 } conjunction with the operational MAU type denoted
by ifMauType.
ifJackEntry OBJECT-TYPE The set of possible values for this object is the
SYNTAX IfJackEntry same as the set defined for the ifMauType object.
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a particular jack."
INDEX { ifMauIfIndex,
ifMauIndex,
ifJackIndex }
::= { ifJackTable 1 }
IfJackEntry ::= This object represents the administratively-
SEQUENCE { configured type of the MAU. If auto-negotiation
ifJackIndex is not enabled or is not implemented for this MAU,
Integer32, the value of this object determines the
ifJackType operational type of the MAU. In this case, a set
JackType to this object will force the MAU into the
} specified operating mode.
ifJackIndex OBJECT-TYPE If auto-negotiation is implemented and enabled for
this MAU, the operational type of the MAU is
determined by auto-negotiation, and the value of
this object denotes the type to which the MAU will
automatically revert if/when auto-negotiation is
later disabled.
, NOTE TO IMPLEMENTORS: It may be necessary to
SYNTAX Integer32 (1..2147483647) provide for underlying hardware implementations
MAX-ACCESS not-accessible which do not follow the exact behavior specified
STATUS current above. In particular, when
DESCRIPTION ifMauAutoNegAdminStatus transitions from enabled
"This variable uniquely identifies the jack to disabled, the agent implementation must ensure
described by this entry from among other jacks that the operational type of the MAU (as reported
attached to the same MAU." by ifMauType) correctly transitions to the value
::= { ifJackEntry 1 } specified by this object, rather than continuing
to operate at the value earlier determined by the
auto-negotiation function."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID, and [IEEE
802.3 Std], 22.2.4.1.4."
::= { ifMauEntry 11 }
ifJackType OBJECT-TYPE ifMauAutoNegSupported OBJECT-TYPE
SYNTAX JackType SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The jack connector type, as it appears on the "This object indicates whether or not auto-
outside of the system." negotiation is supported on this MAU."
::= { ifJackEntry 2 } ::= { ifMauEntry 12 }
-- 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 DESCRIPTION
"Configuration and status objects for the auto- "Information about the external jacks attached to
negotiation function of MAUs attached 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 DESCRIPTION
"An entry in the table, containing configuration "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,
::= { ifMauAutoNegTable 1 } ifJackIndex }
::= { ifJackTable 1 }
, IfJackEntry ::=
SEQUENCE {
ifJackIndex
Integer32,
ifJackType
JackType
}
IfMauAutoNegEntry ::= ifJackIndex OBJECT-TYPE
SEQUENCE { SYNTAX Integer32 (1..2147483647)
ifMauAutoNegAdminStatus MAX-ACCESS not-accessible
INTEGER, STATUS current
ifMauAutoNegRemoteSignaling DESCRIPTION
INTEGER, "This variable uniquely identifies the jack
ifMauAutoNegConfig described by this entry from among other jacks
INTEGER, attached to the same MAU."
ifMauAutoNegCapability ::= { ifJackEntry 1 }
Integer32,
ifMauAutoNegCapAdvertised
Integer32,
ifMauAutoNegCapReceived
Integer32,
ifMauAutoNegRestart
INTEGER
} ifJackType OBJECT-TYPE
SYNTAX JackType
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The jack connector type, as it appears on the
outside of the system."
::= { ifJackEntry 2 }
ifMauAutoNegAdminStatus OBJECT-TYPE -- The ifMauAutoNegTable applies to systems in which
SYNTAX INTEGER { -- auto-negotiation is supported on one or more MAUs
enabled(1), -- attached to interfaces. Note that if auto-negotiation
disabled(2) -- is present and enabled, the ifMauType object reflects
} -- the result of the auto-negotiation function.
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.
If the value of this object is disabled(2) then ifMauAutoNegTable OBJECT-TYPE
the interface will act as it would if it had no SYNTAX SEQUENCE OF IfMauAutoNegEntry
auto-negotiation signaling. Under these MAX-ACCESS not-accessible
conditions, an IEEE 802.3 MAU will immediately be STATUS current
forced to the state indicated by the value of the DESCRIPTION
object ifMauDefaultType. "Configuration and status objects for the auto-
negotiation function of MAUs attached to
interfaces."
::= { dot3IfMauAutoNegGroup 1 }
NOTE TO IMPLEMENTORS: When ifMauAutoNegEntry OBJECT-TYPE
ifMauAutoNegAdminStatus transitions from enabled SYNTAX IfMauAutoNegEntry
to disabled, the agent implementation must ensure MAX-ACCESS not-accessible
that the operational type of the MAU (as reported STATUS current
by ifMauType) correctly transitions to the value DESCRIPTION
specified by the ifMauDefaultType object, rather "An entry in the table, containing configuration
and status information for the auto-negotiation
function of a particular MAU."
INDEX { ifMauIfIndex, ifMauIndex }
::= { ifMauAutoNegTable 1 }
, IfMauAutoNegEntry ::=
than continuing to operate at the value earlier SEQUENCE {
determined by the auto-negotiation function." ifMauAutoNegAdminStatus
REFERENCE INTEGER,
"[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState ifMauAutoNegRemoteSignaling
and 30.6.1.2.2, acAutoNegAdminControl." INTEGER,
::= { ifMauAutoNegEntry 1 } ifMauAutoNegConfig
INTEGER,
ifMauAutoNegCapability
Integer32,
ifMauAutoNegCapAdvertised
Integer32,
ifMauAutoNegCapReceived
Integer32,
ifMauAutoNegRestart
INTEGER
ifMauAutoNegRemoteSignaling OBJECT-TYPE }
SYNTAX INTEGER {
detected(1),
notdetected(2)
}
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 Mgt], 30.6.1.1.3,
aAutoNegRemoteSignaling."
::= { ifMauAutoNegEntry 2 }
ifMauAutoNegConfig OBJECT-TYPE ifMauAutoNegAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), enabled(1),
configuring(2), disabled(2)
complete(3), }
disabled(4), MAX-ACCESS read-write
parallelDetectFail(5) STATUS current
} DESCRIPTION
MAX-ACCESS read-only "Setting this object to enabled(1) will cause the
STATUS current interface which has the auto-negotiation signaling
DESCRIPTION ability to be enabled.
"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 Mgt], 30.6.1.1.4,
aAutoNegAutoConfig."
::= { ifMauAutoNegEntry 4 }
, If the value of this object is disabled(2) then
the interface will act as it would if it had no
auto-negotiation signaling. Under these
conditions, an IEEE 802.3 MAU will immediately be
forced to the state indicated by the value of the
object ifMauDefaultType.
ifMauAutoNegCapability OBJECT-TYPE NOTE TO IMPLEMENTORS: When
SYNTAX Integer32 ifMauAutoNegAdminStatus transitions from enabled
MAX-ACCESS read-only to disabled, the agent implementation must ensure
STATUS current that the operational type of the MAU (as reported
DESCRIPTION by ifMauType) correctly transitions to the value
"A value that uniquely identifies the set of specified by the ifMauDefaultType object, rather
capabilities of the local auto-negotiation entity. than continuing to operate at the value earlier
The value is a sum which initially takes the value determined by the auto-negotiation function."
zero. Then, for each capability of this REFERENCE
interface, 2 raised to the power noted below is "[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState
added to the sum. For example, an interface which and 30.6.1.2.2, acAutoNegAdminControl."
has the capability to support only 100Base-TX half ::= { ifMauAutoNegEntry 1 }
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)).
The powers of 2 assigned to the capabilities are ifMauAutoNegRemoteSignaling OBJECT-TYPE
these: SYNTAX INTEGER {
detected(1),
notdetected(2)
}
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 Mgt], 30.6.1.1.3,
aAutoNegRemoteSignaling."
::= { ifMauAutoNegEntry 2 }
Power Capability ifMauAutoNegConfig OBJECT-TYPE
0 other or unknown SYNTAX INTEGER {
(1-9) (reserved) other(1),
10 10BASE-T half duplex mode configuring(2),
11 10BASE-T full duplex mode complete(3),
12 (reserved) disabled(4),
13 (reserved) parallelDetectFail(5)
14 100BASE-T4 }
15 100BASE-TX half duplex mode MAX-ACCESS read-only
16 100BASE-TX full duplex mode STATUS current
17 (reserved) DESCRIPTION
18 (reserved) "A value indicating the current status of the
19 100BASE-T2 half duplex mode auto-negotiation process. The enumeration
20 100BASE-T2 full duplex mode 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 Mgt], 30.6.1.1.4,
aAutoNegAutoConfig."
::= { ifMauAutoNegEntry 4 }
Note that interfaces that support this MIB may ifMauAutoNegCapability OBJECT-TYPE
have capabilities that extend beyond the scope of SYNTAX Integer32
this MIB." MAX-ACCESS read-only
REFERENCE STATUS current
"[IEEE 802.3 Mgt], 30.6.1.1.5, DESCRIPTION
aAutoNegLocalTechnologyAbility." "A value that uniquely identifies the set of
::= { ifMauAutoNegEntry 5 } capabilities of the local auto-negotiation entity.
The value is a sum which initially takes the value
zero. Then, for each capability 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)).
ifMauAutoNegCapAdvertised OBJECT-TYPE The powers of 2 assigned to the capabilities are
these:
, Power Capability
SYNTAX Integer32 0 other or unknown
MAX-ACCESS read-write (1-9) (reserved)
STATUS current 10 10BASE-T half duplex mode
DESCRIPTION 11 10BASE-T full duplex mode
"A value that uniquely identifies the set of 12 (reserved)
capabilities advertised by the local auto- 13 (reserved)
negotiation entity. Refer to 14 100BASE-T4
ifMauAutoNegCapability for a description of the 15 100BASE-TX half duplex mode
possible values of this object. 16 100BASE-TX full duplex mode
17 (reserved)
18 (reserved)
19 100BASE-T2 half duplex mode
20 100BASE-T2 full duplex mode
Capabilities in this object that are not available Note that interfaces that support this MIB may
in ifMauAutoNegCapability cannot be enabled." have capabilities that extend beyond the scope of
REFERENCE this MIB."
"[IEEE 802.3 Mgt], 30.6.1.1.6, REFERENCE
aAutoNegAdvertisedTechnologyAbility." "[IEEE 802.3 Mgt], 30.6.1.1.5,
::= { ifMauAutoNegEntry 6 } aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 5 }
ifMauAutoNegCapReceived OBJECT-TYPE ifMauAutoNegCapAdvertised OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that uniquely identifies the set of "A value that uniquely identifies the set of
capabilities received from the remote auto- capabilities advertised by the local auto-
negotiation entity. Refer to negotiation entity. Refer to
ifMauAutoNegCapability for a description of the ifMauAutoNegCapability for a description of the
possible values of this object. possible values of this object.
Note that interfaces that support this MIB may be Capabilities in this object that are not available
attached to remote auto-negotiation entities which in ifMauAutoNegCapability cannot be enabled."
have capabilities beyond the scope of this MIB." REFERENCE
REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.6,
"[IEEE 802.3 Mgt], 30.6.1.1.7, aAutoNegAdvertisedTechnologyAbility."
aAutoNegReceivedTechnologyAbility." ::= { ifMauAutoNegEntry 6 }
::= { ifMauAutoNegEntry 7 }
ifMauAutoNegRestart OBJECT-TYPE ifMauAutoNegCapReceived OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32
restart(1), MAX-ACCESS read-only
norestart(2) STATUS current
} DESCRIPTION
MAX-ACCESS read-write "A value that uniquely identifies the set of
STATUS current capabilities received from the remote auto-
DESCRIPTION negotiation entity. Refer to
"If the value of this object is set to restart(1) ifMauAutoNegCapability for a description of the
possible values of this object.
, Note that interfaces that support this MIB may be
then this will force auto-negotiation to begin attached to remote auto-negotiation entities which
link renegotiation. If auto-negotiation signaling have capabilities beyond the scope of this MIB."
is disabled, a write to this object has no effect. REFERENCE
"[IEEE 802.3 Mgt], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 7 }
Setting the value of this object to norestart(2) ifMauAutoNegRestart OBJECT-TYPE
has no effect." SYNTAX INTEGER {
REFERENCE restart(1),
"[IEEE 802.3 Mgt], 30.6.1.2.1, norestart(2)
acAutoNegRestartAutoConfig."
::= { ifMauAutoNegEntry 8 }
-- }
-- The Basic Broadband MAU Table 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.
broadMauBasicTable OBJECT-TYPE Setting the value of this object to norestart(2)
SYNTAX SEQUENCE OF BroadMauBasicEntry has no effect."
MAX-ACCESS not-accessible REFERENCE
STATUS current "[IEEE 802.3 Mgt], 30.6.1.2.1,
DESCRIPTION acAutoNegRestartAutoConfig."
"Table of descriptive and status information about ::= { ifMauAutoNegEntry 8 }
the broadband MAUs connected to interfaces."
::= { dot3BroadMauBasicGroup 1 }
broadMauBasicEntry OBJECT-TYPE --
SYNTAX BroadMauBasicEntry -- The Basic Broadband MAU Table
MAX-ACCESS not-accessible --
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single broadband MAU."
INDEX { broadMauIfIndex, broadMauIndex }
::= { broadMauBasicTable 1 }
BroadMauBasicEntry ::= broadMauBasicTable OBJECT-TYPE
SEQUENCE { SYNTAX SEQUENCE OF BroadMauBasicEntry
broadMauIfIndex MAX-ACCESS not-accessible
Integer32, STATUS current
broadMauIndex DESCRIPTION
Integer32, "Table of descriptive and status information about
broadMauXmtRcvSplitType the broadband MAUs connected to interfaces."
INTEGER, ::= { dot3BroadMauBasicGroup 1 }
broadMauXmtCarrierFreq
Integer32,
, broadMauBasicEntry OBJECT-TYPE
SYNTAX BroadMauBasicEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single broadband MAU."
INDEX { broadMauIfIndex, broadMauIndex }
::= { broadMauBasicTable 1 }
broadMauTranslationFreq BroadMauBasicEntry ::=
Integer32 SEQUENCE {
} broadMauIfIndex
Integer32,
broadMauIndex
Integer32,
broadMauXmtRcvSplitType
INTEGER,
broadMauIfIndex OBJECT-TYPE broadMauXmtCarrierFreq
SYNTAX Integer32 (1..2147483647) Integer32,
MAX-ACCESS read-only broadMauTranslationFreq
STATUS current Integer32
DESCRIPTION }
"This variable uniquely identifies the interface
to which the MAU described by this entry is
connected."
REFERENCE
"Reference RFC 1213, ifIndex."
::= { broadMauBasicEntry 1 }
broadMauIndex OBJECT-TYPE broadMauIfIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647) SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable uniquely identifies the MAU "This variable uniquely identifies the interface
connected to interface broadMauIfIndex that is to which the MAU described by this entry is
described by this entry." connected."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID." "Reference RFC 1213, ifIndex."
::= { broadMauBasicEntry 2 } ::= { broadMauBasicEntry 1 }
broadMauXmtRcvSplitType OBJECT-TYPE broadMauIndex OBJECT-TYPE
SYNTAX INTEGER { SYNTAX Integer32 (1..2147483647)
other(1), MAX-ACCESS read-only
single(2), STATUS current
dual(3) DESCRIPTION
} "This variable uniquely identifies the MAU
MAX-ACCESS read-only connected to interface broadMauIfIndex that is
STATUS current described by this entry."
DESCRIPTION REFERENCE
"This object indicates the type of frequency "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID."
multiplexing/cabling system used to separate the ::= { broadMauBasicEntry 2 }
transmit and receive paths for the 10BROAD36 MAU.
The value other(1) is returned if the split type broadMauXmtRcvSplitType OBJECT-TYPE
is not either single or dual. SYNTAX INTEGER {
other(1),
single(2),
dual(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the type of frequency
multiplexing/cabling system used to separate the
transmit and receive paths for the 10BROAD36 MAU.
The value single(2) indicates a single cable The value other(1) is returned if the split type
is not either single or dual.
, The value single(2) indicates a single cable
system. The value dual(3) indicates a dual cable system. The value dual(3) indicates a dual cable
system, offset normally zero." system, offset normally zero."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBbMAUXmitRcvSplitType." aBbMAUXmitRcvSplitType."
::= { broadMauBasicEntry 3 } ::= { broadMauBasicEntry 3 }
broadMauXmtCarrierFreq OBJECT-TYPE broadMauXmtCarrierFreq OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the transmit carrier "This variable indicates the transmit carrier
frequency of the 10BROAD36 MAU in MHz/4; that is, frequency of the 10BROAD36 MAU in MHz/4; that is,
in units of 250 kHz." in units of 250 kHz."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBroadbandFrequencies.xmitCarrierFrequency." aBroadbandFrequencies.xmitCarrierFrequency."
::= { broadMauBasicEntry 4 } ::= { broadMauBasicEntry 4 }
broadMauTranslationFreq OBJECT-TYPE broadMauTranslationFreq OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable indicates the translation offset "This variable indicates the translation offset
frequency of the 10BROAD36 MAU in MHz/4; that is, frequency of the 10BROAD36 MAU in MHz/4; that is,
in units of 250 kHz." in units of 250 kHz."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBroadbandFrequencies.translationFrequency." aBroadbandFrequencies.translationFrequency."
::= { broadMauBasicEntry 5 } ::= { broadMauBasicEntry 5 }
-- Notifications for use by 802.3 MAUs -- Notifications for use by 802.3 MAUs
rpMauJabberTrap NOTIFICATION-TYPE rpMauJabberTrap NOTIFICATION-TYPE
OBJECTS { rpMauJabberState } OBJECTS { rpMauJabberState }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This trap is sent whenever a managed repeater MAU "This trap is sent whenever a managed repeater MAU
enters the jabber state. enters the jabber state.
The agent must throttle the generation of The agent must throttle the generation of
consecutive rpMauJabberTraps so that there is at
least a five-second gap between them."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
notification."
::= { snmpDot3MauMgt 0 1 }
, ifMauJabberTrap NOTIFICATION-TYPE
consecutive rpMauJabberTraps so that there is at OBJECTS { ifMauJabberState }
least a five-second gap between them." STATUS current
REFERENCE DESCRIPTION
"[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber "This trap is sent whenever a managed interface
notification." MAU enters the jabber state.
::= { snmpDot3MauMgt 0 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 REFERENCE
"This trap is sent whenever a managed interface "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
MAU enters the jabber state. notification."
::= { snmpDot3MauMgt 0 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."
::= { snmpDot3MauMgt 0 2 }
-- Conformance information mauModConf
OBJECT IDENTIFIER ::= { mauMod 1 }
mauModCompls
OBJECT IDENTIFIER ::= { mauModConf 1 }
mauModObjGrps
OBJECT IDENTIFIER ::= { mauModConf 2 }
mauModNotGrps
OBJECT IDENTIFIER ::= { mauModConf 3 }
mauModConf -- Object groups
OBJECT IDENTIFIER ::= { mauMod 1 }
mauModCompls
OBJECT IDENTIFIER ::= { mauModConf 1 }
mauModObjGrps
OBJECT IDENTIFIER ::= { mauModConf 2 }
mauModNotGrps
OBJECT IDENTIFIER ::= { mauModConf 3 }
-- Object groups mauRpGrpBasic OBJECT-GROUP
OBJECTS { rpMauGroupIndex,
rpMauPortIndex,
rpMauIndex,
rpMauType,
rpMauStatus,
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 }
mauRpGrpBasic OBJECT-GROUP mauRpGrp100Mbs OBJECT-GROUP
OBJECTS { rpMauGroupIndex, OBJECTS { rpMauFalseCarriers }
rpMauPortIndex, STATUS current
rpMauIndex, DESCRIPTION
rpMauType, "Conformance group for MAUs attached to
rpMauStatus, repeater ports with 100 Mb/s capability."
rpMauMediaAvailable, ::= { mauModObjGrps 2 }
rpMauMediaAvailableStateExits,
, mauRpGrpJack OBJECT-GROUP
rpMauJabberState, OBJECTS { rpJackType }
rpMauJabberingStateEnters } STATUS current
STATUS current DESCRIPTION
DESCRIPTION "Conformance group for MAUs attached to
"Basic conformance group for MAUs attached to repeater ports with managed jacks."
repeater ports. This group is also the ::= { mauModObjGrps 3 }
conformance specification for RFC 1515
implementations."
::= { mauModObjGrps 1 }
mauRpGrp100Mbs OBJECT-GROUP mauIfGrpBasic OBJECT-GROUP
OBJECTS { rpMauFalseCarriers } OBJECTS { ifMauIfIndex,
STATUS current ifMauIndex,
DESCRIPTION ifMauType,
"Conformance group for MAUs attached to ifMauStatus,
repeater ports with 100 Mb/s 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 ifMauDefaultType,
"Conformance group for MAUs attached to ifMauAutoNegSupported }
repeater ports with managed jacks." STATUS current
::= { mauModObjGrps 3 } DESCRIPTION
"Conformance group for MAUs attached
to interfaces with 100 Mb/s capability."
::= { mauModObjGrps 5 }
mauIfGrpBasic OBJECT-GROUP mauIfGrpJack OBJECT-GROUP
OBJECTS { ifMauIfIndex, OBJECTS { ifJackType }
ifMauIndex, STATUS current
ifMauType, DESCRIPTION
ifMauStatus, "Conformance group for MAUs attached
ifMauMediaAvailable, to interfaces with managed jacks."
ifMauMediaAvailableStateExits, ::= { mauModObjGrps 6 }
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 mauIfGrpAutoNeg OBJECT-GROUP
OBJECTS { ifMauFalseCarriers, OBJECTS { ifMauAutoNegAdminStatus,
ifMauAutoNegRemoteSignaling,
ifMauAutoNegConfig,
ifMauAutoNegCapability,
ifMauAutoNegCapAdvertised,
ifMauAutoNegCapReceived,
ifMauAutoNegRestart }
STATUS current
DESCRIPTION
"Conformance group for MAUs attached to
interfaces with managed auto-negotiation."
::= { mauModObjGrps 7 }
, mauBroadBasic OBJECT-GROUP
ifMauTypeList, OBJECTS { broadMauIfIndex,
ifMauDefaultType, broadMauIndex,
ifMauAutoNegSupported } broadMauXmtRcvSplitType,
STATUS current broadMauXmtCarrierFreq,
DESCRIPTION broadMauTranslationFreq }
"Conformance group for MAUs attached STATUS current
to interfaces with 100 Mb/s capability." DESCRIPTION
::= { mauModObjGrps 5 } "Conformance group for broadband MAUs
attached to interfaces. This group
provides a conformance specification
for RFC 1515 implementations."
::= { mauModObjGrps 8 }
mauIfGrpJack OBJECT-GROUP -- Notification groups
OBJECTS { ifJackType }
STATUS current
DESCRIPTION
"Conformance group for MAUs attached
to interfaces with managed jacks."
::= { mauModObjGrps 6 }
mauIfGrpAutoNeg OBJECT-GROUP rpMauNotifications NOTIFICATION-GROUP
OBJECTS { ifMauAutoNegAdminStatus, NOTIFICATIONS { rpMauJabberTrap }
ifMauAutoNegRemoteSignaling, STATUS current
ifMauAutoNegConfig, DESCRIPTION
ifMauAutoNegCapability, "Notifications for repeater MAUs."
ifMauAutoNegCapAdvertised, ::= { mauModNotGrps 1 }
ifMauAutoNegCapReceived,
ifMauAutoNegRestart }
STATUS current
DESCRIPTION
"Conformance group for MAUs attached to
interfaces with managed auto-negotiation."
::= { mauModObjGrps 7 }
mauBroadBasic OBJECT-GROUP ifMauNotifications NOTIFICATION-GROUP
OBJECTS { broadMauIfIndex, NOTIFICATIONS { ifMauJabberTrap }
broadMauIndex, STATUS current
broadMauXmtRcvSplitType, DESCRIPTION
broadMauXmtCarrierFreq, "Notifications for interface MAUs."
broadMauTranslationFreq } ::= { mauModNotGrps 2 }
STATUS current
DESCRIPTION
"Conformance group for broadband MAUs
attached to interfaces. This group
provides a conformance specification
for RFC 1515 implementations."
::= { mauModObjGrps 8 }
, -- Compliances
-- Notification groups mauModRpCompl MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance for MAUs attached to repeater ports."
rpMauNotifications NOTIFICATION-GROUP MODULE -- this module
NOTIFICATIONS { rpMauJabberTrap } MANDATORY-GROUPS { mauRpGrpBasic }
STATUS current
DESCRIPTION
"Notifications for repeater MAUs."
::= { mauModNotGrps 1 }
ifMauNotifications NOTIFICATION-GROUP GROUP mauRpGrp100Mbs
NOTIFICATIONS { ifMauJabberTrap } DESCRIPTION
STATUS current "Implementation of this optional group is
DESCRIPTION recommended for MAUs which have 100Mb/s
"Notifications for interface MAUs." capability."
::= { mauModNotGrps 2 }
-- Compliances GROUP mauRpGrpJack
DESCRIPTION
"Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."
mauModRpCompl MODULE-COMPLIANCE GROUP rpMauNotifications
STATUS current DESCRIPTION
DESCRIPTION "Implementation of this group is
"Compliance for MAUs attached to repeater ports." recommended for MAUs attached to repeater
ports."
MODULE -- this module ::= { mauModCompls 1 }
MANDATORY-GROUPS { mauRpGrpBasic }
GROUP mauRpGrp100Mbs mauModIfCompl MODULE-COMPLIANCE
DESCRIPTION STATUS current
"Implementation of this optional group is DESCRIPTION
recommended for MAUs which have 100Mb/s "Compliance for MAUs attached to interfaces."
capability."
GROUP mauRpGrpJack MODULE -- this module
DESCRIPTION MANDATORY-GROUPS { mauIfGrpBasic }
"Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."
GROUP rpMauNotifications GROUP mauIfGrp100Mbs
DESCRIPTION DESCRIPTION
"Implementation of this group is "Implementation of this optional group is
recommended for MAUs attached to repeater recommended for MAUs which have 100Mb/s
ports." capability."
, GROUP mauIfGrpJack
DESCRIPTION
"Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."
::= { mauModCompls 1 } GROUP mauIfGrpAutoNeg
DESCRIPTION
"Implementation of this group is
mandatory for MAUs which support
managed auto-negotiation."
mauModIfCompl MODULE-COMPLIANCE GROUP mauBroadBasic
STATUS current DESCRIPTION
DESCRIPTION "Implementation of this group is
"Compliance for MAUs attached to interfaces." mandatory for broadband MAUs."
MODULE -- this module GROUP ifMauNotifications
MANDATORY-GROUPS { mauIfGrpBasic } DESCRIPTION
"Implementation of this group is
recommended for MAUs attached to
interfaces."
GROUP mauIfGrp100Mbs ::= { mauModCompls 2 }
DESCRIPTION
"Implementation of this optional group is
recommended for MAUs which have 100Mb/s
capability."
GROUP mauIfGrpJack END
DESCRIPTION
"Implementation of this optional group is
recommended for MAUs which have one or more
external jacks."
GROUP mauIfGrpAutoNeg 4. Acknowledgements
DESCRIPTION
"Implementation of this group is
mandatory for MAUs which support
managed auto-negotiation."
GROUP mauBroadBasic This document was produced by the IETF Hub MIB Working Group, whose
DESCRIPTION efforts were greatly advanced by the contributions of the following
"Implementation of this group is people:
mandatory for broadband MAUs."
GROUP ifMauNotifications Chuck Black
DESCRIPTION John Flick
"Implementation of this group is Jeff Johnson
recommended for MAUs attached to Leon Leong
interfaces." Mike Lui
Dave Perkins
Geoff Thompson
Maurice Turcotte
Paul Woodruff
::= { mauModCompls 2 } Special thanks as well to Dave Perkins for his excellent work on the
SMICng compiler, which made it easy to take advantage of the latest
SNMPv2 constructs in this MIB.
END 5. References
, [1] IEEE 802.3/ISO 8802-3 Information processing systems -
4. Acknowledgements Local area networks - Part 3: Carrier sense multiple
access with collision detection (CSMA/CD) access method
and physical layer specifications, 1993.
This document was produced by the IETF Hub MIB Working Group, [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium
whose efforts were greatly advanced by the contributions of Attachment Units and Repeater for 100 Mb/s Operation,
the following people: Type 100BASE-T," Sections 21 through 29, Supplement to
IEEE Std 802.3, October 26, 1995.
Chuck Black [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30,
John Flick Supplement to IEEE Std 802.3, October 26, 1995.
Jeff Johnson
Leon Leong
Mike Lui
Dave Perkins
Geoff Thompson
Maurice Turcotte
Paul Woodruff
Special thanks as well to Dave Perkins for his excellent work [4] de Graaf, K., D. Romascanu, D. McMaster and K.
on the SMICng compiler, which made it easy to take advantage McCloghrie, "Definitions of Managed Objects for IEEE
of the latest SNMPv2 constructs in this MIB. 802.3 Repeater Devices using SMIv2", RFC 2108, February
1997.
, [5] McCloghrie, K. and M. Rose, Editors, "Management
5. References Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, March 1991.
[1] IEEE 802.3/ISO 8802-3 Information processing systems - [6] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Local area networks - Part 3: Carrier sense multiple "Structure of Management Information for version 2 of the
access with collision detection (CSMA/CD) access method Simple Network Management Protocol (SNMPv2)", RFC 1902,
and physical layer specifications, 1993. January 1996.
[2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium [7] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Attachment Units and Repeater for 100 Mb/s Operation, Conventions for version 2 of the Simple Network Management
Type 100BASE-T," Sections 21 through 29, Supplement to Protocol (SNMPv2)", RFC 1903, January 1996.
IEEE Std 802.3, October 26, 1995.
[3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, [8] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Supplement to IEEE Std 802.3, October 26, 1995. "Conformance Statements for version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1904, January 1996.
[4] de Graaf, K., D. Romascanu, D. McMaster, and K. [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
McCloghrie, "Definitions of Managed Objects for IEEE Operations for version 2 of the Simple Network Management
802.3 Repeater Devices using SMIv2", RFC 2108, February Protocol (SNMPv2)", RFC 1905, January 1996.
1997.
[5] McCloghrie, K., and M. Rose, Editors, "Management [10] Case, J., M. Fedor, M. Schoffstall and J. Davin, "Simple
Information Base for Network Management of TCP/IP-based Network Management Protocol", STD 15, RFC 1157, May 1990.
internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems,
Performance Systems International, March 1991.
[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., [11] McMaster, D., K. McCloghrie and S. Roberts, "Definitions of
and S. Waldbusser, "Structure of Management Information Managed Objects for IEEE 802.3 Medium Attachment Units
for version 2 of the Simple Network Management Protocol (MAUs)", RFC 1515, September 1993.
(SNMPv2)", RFC 1902, January 1996.
[7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 6. Security Considerations
and S. Waldbusser, "Textual Conventions for version 2 of
the Simple Network Management Protocol (SNMPv2)", RFC
1903, January 1996.
[8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., Certain management information defined in this MIB may be considered
and S. Waldbusser, "Conformance Statements for version 2 sensitive in some network environments. Therefore, authentication of
of the Simple Network Management Protocol (SNMPv2)", RFC received SNMP requests and controlled access to management
1904, January 1996. information should be employed in such environments. The method for
this authentication is a function of the SNMP Administrative
Framework, and has not been expanded by this MIB.
[9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., Several objects in this MIB allow write access. Setting these
and S. Waldbusser, "Protocol Operations for version 2 of objects can have a serious effect on the operation of the network,
the Simple Network Management Protocol (SNMPv2)", RFC including enabling or disabling a MAU, changing a MAU's default type,
1905, January 1996. enabling, disabling or restarting autonegotiation, or modifying the
capabilities that a MAU advertizes during autonegotiation. It is
recommended that implementers seriously consider whether set
operations should be allowed without providing, at a minimum,
authentication of request origin.
, 7. Authors' Addresses
[10] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Kathryn de Graaf
Network Management Protocol", RFC 1157, SNMP Research, 3Com Corporation
Performance Systems International, MIT Laboratory for 118 Turnpike Rd.
Computer Science, May 1990. Southborough, MA 01772 USA
[11] McMaster, D., K. McCloghrie, S. Roberts, "Definitions of Phone: (508)229-1627
Managed Objects for IEEE 802.3 Medium Attachment Units Fax: (508)490-5882
(MAUs)", RFC 1515, September 1993. EMail: kdegraaf@isd.3com.com
, Dan Romascanu
Madge Networks (Israel) Ltd.
Atidim Technology Park, Bldg. 3
Tel Aviv 61131, Israel
6. Security Considerations Phone: 972-3-6458414, 6458458
Fax: 972-3-6487146
EMail: dromasca@madge.com
Security issues are not discussed in this memo. Donna McMaster
Cisco Systems Inc.
170 West Tasman Drive
San Jose, CA 95134
7. Authors' Addresses Phone:: (408) 526-5260
EMail: mcmaster@cisco.com
Keith McCloghrie
Cisco Systems Inc.
170 West Tasman Drive
San Jose, CA 95134
Kathryn de Graaf Phone: (408) 526-5260
3Com Corporation EMail: kzm@cisco.com
118 Turnpike Rd.
Southborough, MA 01772 USA
Tel: (508)229-1627
Fax: (508)490-5882
E-mail: kdegraaf@isd.3com.com
Dan Romascanu Sam Roberts
Madge Networks (Israel) Ltd. Farallon Computing, Inc.
Atidim Technology Park, Bldg. 3 2470 Mariner Square Loop
Tel Aviv 61131, Israel Alameda, CA 94501-1010
Tel: 972-3-6458414, 6458458
Fax: 972-3-6487146
E-mail: dromasca@madge.com
Donna McMaster Phone:: (510) 814-5215
Cisco Systems Inc. EMail: sroberts@farallon.com
170 West Tasman Drive
San Jose, CA 95134
Tel: (408) 526-5260
E-Mail: mcmaster@cisco.com
Keith McCloghrie 8. Full Copyright Statement
Cisco Systems Inc.
170 West Tasman Drive
San Jose, CA 95134
Tel: (408) 526-5260
E-Mail: kzm@cisco.com
Sam Roberts Copyright (C) The Internet Society (1997). All Rights Reserved.
Farallon Computing, Inc.
2470 Mariner Square Loop
Alameda, CA 94501-1010
Tel: (510) 814-5215
E-Mail: sroberts@farallon.com
, This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
Table of Contents The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
1 The SNMPv2 Network Management Framework ............... 2 This document and the information contained herein is provided on an
1.1 Object Definitions .................................. 3 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
2 Overview .............................................. 4 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
2.1 Relationship to RFC 1515 ............................ 4 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
2.2 MAU Management ...................................... 4 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
2.3 Relationship to Other MIBs .......................... 4 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
2.3.1 Relationship to the MIB-II 'interfaces' group ..... 5
2.3.2 Relationship to the 802.3 Repeater MIB ............ 5
2.4 Management of Internal MAUs ......................... 5
3 Definitions ........................................... 7
4 Acknowledgements ...................................... 44
5 References ............................................ 45
6 Security Considerations ............................... 47
7 Authors' Addresses .................................... 47
 End of changes. 278 change blocks. 
1759 lines changed or deleted 1700 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/