As per Relevance of the word reference, we have this rfc below:
Network Working Group A.
Request for Comments: 2668 Extreme Networks, Inc
Obsoletes: 2239 J.
Category: Standards Track Hewlett-Packard
K. de
Argon
D.
Lucent
D.
Cisco Systems, Inc
K.
Cisco Systems, Inc
S.
Farallon Computing, Inc
August 1999
Definitions of Managed Objects
IEEE 802.3 Medium Attachment Units (MAUs
Status of this
This document specifies an Internet standards track protocol for
Internet community, and requests discussion and suggestions
improvements. Please refer to the current edition of the "
Official Protocol Standards" (STD 1) for the standardization
and status of this protocol. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
This memo obsoletes RFC 2239, "Definitions of Managed Objects
IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2". This
extends that specification by including management information
for the management of 1000 Mb/s MAUs
Ethernet technology, as defined by the 802.3 Working Group of
IEEE, continues to evolve, with scalable increases in speed,
types of cabling and interfaces, and new features. This
may require changes in the managed objects in order to reflect
new functionality. This document, as with other documents issued
this working group, reflects a certain stage in the evolution
Ethernet technology. In the future, this document might be revised
Smith, et al. Standards Track [Page 1]
RFC 2668 802.3 MAU MIB August 1999
or new documents might be issued by the Ethernet Interfaces and
MIB Working Group, in order to reflect the evolution of
technology
Table of
1. Introduction ............................................... 2
2. The SNMP Management Framework .............................. 3
3. Overview ................................................... 4
3.1. Relationship to RFC 2239 ................................. 4
3.2. Relationship to RFC 1515 ................................. 4
3.3. MAU Management ........................................... 4
3.4. Relationship to Other MIBs ............................... 5
3.4.1. Relationship to the Interfaces MIB ..................... 5
3.4.2. Relationship to the 802.3 Repeater MIB ................. 5
3.5. Management of Internal MAUs .............................. 5
4. Definitions ................................................ 6
5. Intellectual Property ...................................... 49
6. Acknowledgements ........................................... 49
7. References ................................................. 50
8. Security Considerations .................................... 52
9. Authors' Addresses ......................................... 53
10. Appendix: Change Log ....................................... 55
11. Full Copyright Statement .................................. 57
1.
This memo defines a portion of the Management Information Base (MIB
for use with network management protocols in the Internet community
In particular, it defines objects for managing IEEE 802.3
Attachment Units (MAUs).
This memo also includes a MIB module. This MIB module extends
list of managed objects specified in the earlier version of this MIB
RFC 2239 [21].
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
document are to be interpreted as described in [20].
Smith, et al. Standards Track [Page 2]
RFC 2668 802.3 MAU MIB August 1999
2. The SNMP Management
The SNMP Management Framework presently consists of five
components
o An overall architecture, described in RFC 2571 [1].
o Mechanisms for describing and naming objects and events for
purpose of management. The first version of this Structure
Management Information (SMI) is called SMIv1 and described
STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].
second version, called SMIv2, is described in STD 58, RFC 2578
[5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].
o Message protocols for transferring management information.
first version of the SNMP message protocol is called SNMPv1
described in STD 15, RFC 1157 [8]. A second version of the
message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [9] and
1906 [10]. The third version of the message protocol is
SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
[12].
o Protocol operations for accessing management information.
first set of protocol operations and associated PDU formats
described in STD 15, RFC 1157 [8]. A second set of
operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2573 [14]
the view-based access control mechanism described in RFC 2575
[15].
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the mechanisms defined in the SMI
This memo specifies a MIB module that is compliant to the SMIv2.
MIB conforming to the SMIv1 can be produced through the
translations. The resulting translated MIB must be
equivalent, except where objects or events are omitted because
translation is possible (use of Counter64). Some machine
information in SMIv2 will be converted into textual descriptions
SMIv1 during the translation process. However, this loss of
readable information is not considered to change the semantics of
MIB
Smith, et al. Standards Track [Page 3]
RFC 2668 802.3 MAU MIB August 1999
3.
3.1. Relationship to RFC 2239
This MIB is intended to be a superset of that defined by RFC 2239
[21], which will go to historic status. This MIB includes all of
objects contained in that MIB, plus several new ones which
additional capabilities. Implementors are encouraged to support
applicable conformance groups in order to make the best use of
new functionality provided by this MIB. The new objects
management support for
o management of 1000 Mb/s
o management of PAUSE
o management of remote fault
3.2. Relationship to RFC 1515
RFC 2239 was a replacement for RFC 1515 [22], which is now historic
RFC 2239 defined a superset of RFC 1515 which contained all of
objects defined in RFC 1515, plus several new ones which
additional capabilities. The new objects in RFC 2239
management support for
o management of 100 Mb/s
o auto-negotiation on interface
o jack
3.3. MAU
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/
standard [16]. These MAUs may be connected to IEEE 802.3
or to 802.3 (Ethernet-like) interfaces. For convenience this
refers to these devices as "repeater MAUs" and "interface MAUs."
The definitions presented here are based on Section 30.5, "
Management for 10, 100 & 1000 Mb/s Medium Attachment Units (MAUs)",
and Annex 30A, "GDMO Specifications for 802.3 managed object classes
of IEEE Std. 802.3, 1998 edition [16]. That specification
definitions for 10Mb/s, 100Mb/s and 1000Mb/s devices.
specification is intended to serve the same purpose: to provide
management of all types of Ethernet/802.3 MAUs
Smith, et al. Standards Track [Page 4]
RFC 2668 802.3 MAU MIB August 1999
3.4. Relationship to Other
It is assumed that an agent implementing this MIB will also
(at least) the 'system' group defined in MIB-II [18]. The
sections identify other MIBs that such an agent should implement
3.4.1. Relationship to the Interfaces MIB
The sections of this document that define interface MAU-
objects specify an extension to the Interfaces MIB [19]. An
implementing these interface-MAU related objects MUST also
the relevant groups of Interface MIB. The value of the
ifMauIfIndex is the same as the value of 'ifIndex' used
instantiate the interface to which the given MAU is connected
It is expected that an agent implementing the interface-MAU
objects in this MIB will also implement the Ethernet-like
MIB, [23].
(Note that repeater ports are not represented as interfaces in
Interface MIB.)
3.4.2. Relationship to the 802.3 Repeater
The section of this document that defines repeater MAU-
objects specifies an extension to the 802.3 Repeater MIB defined
[17]. An agent implementing these repeater-MAU related objects
also implement the 802.3 Repeater MIB
The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used
instantiate a repeater MAU variable SHALL be the same as the
of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate
port to which the given MAU is connected
3.5. Management of Internal
In some situations, a MAU can be "internal" -- i.e.,
functionality is implemented entirely within a device. For example
a managed repeater may contain an internal repeater-MAU and/or
internal interface-MAU through which management
originating on one of the repeater's external ports pass in order
reach the management agent associated with the repeater.
internal MAUs may or may not be managed. If they are managed
objects describing their attributes should appear in the
MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs
dot3IfMauBasicGroup for internal interface-MAUs
Smith, et al. Standards Track [Page 5]
RFC 2668 802.3 MAU MIB August 1999
4.
MAU-MIB DEFINITIONS ::=
Counter32, Integer32,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE
OBJECT-IDENTITY, mib-2
FROM SNMPv2-
TruthValue, TEXTUAL-
FROM SNMPv2-
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-
FROM SNMPv2-CONF
mauMod MODULE-
LAST-UPDATED "9908240400Z" -- August 24, 1999
ORGANIZATION "IETF Ethernet Interfaces and Hub
Working Group
CONTACT-
"WG E-mail: hubmib@hprnd.rose.hp.
To subscribe: hubmib-request@hprnd.rose.hp.
Chair: Dan
Postal: Lucent
Atidim Technology Park, Bldg. 3
Tel Aviv 61131
Tel: +972 3 645 8414, 6458458
Fax: +972 3 648 7146
E-mail: dromasca@lucent.
Editors: Andrew
Postal: Extreme Networks, Inc
10460 Bandley
Cupertino, CA 95014
Tel: +1 408 579-2821
E-mail: andrew@extremenetworks.
John
Postal: Hewlett-Packard
8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557
Tel: +1 916 785 4018
Fax: +1 916 785 1199
E-mail: johnf@rose.hp.
Smith, et al. Standards Track [Page 6]
RFC 2668 802.3 MAU MIB August 1999
Kathryn de
Postal: Argon
25 Porter
Littleton, MA 01460
Tel: +1 978 486 0665 x163
Fax: +1 978 486 9379
E-mail: kdegraaf@argon.com
DESCRIPTION "Management information for 802.3 MAUs
The following reference is used
this MIB module
[IEEE 802.3 Std] refers
IEEE Std 802.3, 1998 Edition: '
technology - Telecommunications
information exchange between systems -
Local and metropolitan area networks -
Specific requirements - Part 3:
sense multiple access with
detection (CSMA/CD) access method
physical layer specifications',
September 1998.
Of particular interest is Clause 30, '10Mb/s
100Mb/s and 1000Mb/s Management'."
REVISION "9908240400Z" -- August 24, 1999
DESCRIPTION "This version published as RFC 2668.
to include support for 1000 Mb/
MAUs and flow control negotiation."
REVISION "9710310000Z" -- October 31, 1997
DESCRIPTION "This version published as RFC 2239."
REVISION "9309300000Z" -- September 30, 1993
DESCRIPTION "Initial version, published as RFC 1515."
::= { snmpDot3MauMgt 6 }
snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 }
-- textual
JackType ::= TEXTUAL-
STATUS
DESCRIPTION "Common enumeration values for
and interface MAU jack types."
Smith, et al. Standards Track [Page 7]
RFC 2668 802.3 MAU MIB August 1999
SYNTAX INTEGER {
other(1),
rj45(2),
rj45S(3), -- rj45
db9(4),
bnc(5),
fAUI(6), -- female
mAUI(7), -- male
fiberSC(8),
fiberMIC(9),
fiberST(10),
telco(11),
mtrj(12), -- fiber MT-
hssdc(13) -- fiber channel style-2
}
dot3
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
dot3
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
dot3
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
dot3
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
-- object identities for MAU
-- (see rpMauType and ifMauType for usage
dot3
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 }
dot3MauTypeAUI OBJECT-
STATUS
DESCRIPTION "no internal MAU, view from AUI
::= { dot3MauType 1 }
dot3MauType10Base5 OBJECT-
STATUS
DESCRIPTION "thick coax MAU (per 802.3 section 8)"
::= { dot3MauType 2 }
dot3MauTypeFoirl OBJECT-
STATUS
DESCRIPTION "FOIRL MAU (per 802.3 section 9.9)"
::= { dot3MauType 3 }
dot3MauType10Base2 OBJECT-
STATUS
Smith, et al. Standards Track [Page 8]
RFC 2668 802.3 MAU MIB August 1999
DESCRIPTION "thin coax MAU (per 802.3 section 10)"
::= { dot3MauType 4 }
dot3MauType10BaseT OBJECT-
STATUS
DESCRIPTION "UTP MAU (per 802.3 section 14).
Note that it is strongly recommended
agents return either dot3MauType10BaseTHD
dot3MauType10BaseTFD if the duplex mode
known. However, management applications
be prepared to receive this MAU type value
older agent implementations."
::= { dot3MauType 5 }
dot3MauType10BaseFP OBJECT-
STATUS
DESCRIPTION "passive fiber MAU (per 802.3 section 16)"
::= { dot3MauType 6 }
dot3MauType10BaseFB OBJECT-
STATUS
DESCRIPTION "sync fiber MAU (per 802.3 section 17)"
::= { dot3MauType 7 }
dot3MauType10BaseFL OBJECT-
STATUS
DESCRIPTION "async fiber MAU (per 802.3 section 18)
Note that it is strongly recommended
agents return either dot3MauType10BaseFLHD
dot3MauType10BaseFLFD if the duplex mode
known. However, management applications
be prepared to receive this MAU type value
older agent implementations."
::= { dot3MauType 8 }
dot3MauType10Broad36 OBJECT-
STATUS
DESCRIPTION "broadband DTE MAU (per 802.3 section 11).
Note that 10BROAD36 MAUs can be attached
interfaces but not to repeaters."
::= { dot3MauType 9 }
------ new since RFC 1515:
dot3MauType10BaseTHD OBJECT-
STATUS
DESCRIPTION "UTP MAU (per 802.3 section 14), half
mode
::= { dot3MauType 10 }
Smith, et al. Standards Track [Page 9]
RFC 2668 802.3 MAU MIB August 1999
dot3MauType10BaseTFD OBJECT-
STATUS
DESCRIPTION "UTP MAU (per 802.3 section 14), full
mode
::= { dot3MauType 11 }
dot3MauType10BaseFLHD OBJECT-
STATUS
DESCRIPTION "async fiber MAU (per 802.3 section 18),
duplex mode
::= { dot3MauType 12 }
dot3MauType10BaseFLFD OBJECT-
STATUS
DESCRIPTION "async fiber MAU (per 802.3 section 18),
duplex mode
::= { dot3MauType 13 }
dot3MauType100BaseT4 OBJECT-
STATUS
DESCRIPTION "4 pair categ. 3 UTP (per 802.3 section 23)"
::= { dot3MauType 14 }
dot3MauType100BaseTXHD OBJECT-
STATUS
DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25),
half duplex mode
::= { dot3MauType 15 }
dot3MauType100BaseTXFD OBJECT-
STATUS
DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25),
full duplex mode
::= { dot3MauType 16 }
dot3MauType100BaseFXHD OBJECT-
STATUS
DESCRIPTION "X fiber over PMT (per 802.3 section 26),
duplex mode
::= { dot3MauType 17 }
dot3MauType100BaseFXFD OBJECT-
STATUS
DESCRIPTION "X fiber over PMT (per 802.3 section 26),
duplex mode
::= { dot3MauType 18 }
dot3MauType100BaseT2HD OBJECT-
STATUS
Smith, et al. Standards Track [Page 10]
RFC 2668 802.3 MAU MIB August 1999
DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32),
half duplex mode
::= { dot3MauType 19 }
dot3MauType100BaseT2FD OBJECT-
STATUS
DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32),
full duplex mode
::= { dot3MauType 20 }
------ new since RFC 2239:
dot3MauType1000BaseXHD OBJECT-
STATUS
DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD
half duplex mode
::= { dot3MauType 21 }
dot3MauType1000BaseXFD OBJECT-
STATUS
DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD
full duplex mode
::= { dot3MauType 22 }
dot3MauType1000BaseLXHD OBJECT-
STATUS
DESCRIPTION "Fiber over long-wavelength laser (per 802.3
section 38), half duplex mode
::= { dot3MauType 23 }
dot3MauType1000BaseLXFD OBJECT-
STATUS
DESCRIPTION "Fiber over long-wavelength laser (per 802.3
section 38), full duplex mode
::= { dot3MauType 24 }
dot3MauType1000BaseSXHD OBJECT-
STATUS
DESCRIPTION "Fiber over short-wavelength laser (per 802.3
section 38), half duplex mode
::= { dot3MauType 25 }
dot3MauType1000BaseSXFD OBJECT-
STATUS
DESCRIPTION "Fiber over short-wavelength laser (per 802.3
section 38), full duplex mode
::= { dot3MauType 26 }
Smith, et al. Standards Track [Page 11]
RFC 2668 802.3 MAU MIB August 1999
dot3MauType1000BaseCXHD OBJECT-
STATUS
DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3
section 39), half duplex mode
::= { dot3MauType 27 }
dot3MauType1000BaseCXFD OBJECT-
STATUS
DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3
section 39), full duplex mode
::= { dot3MauType 28 }
dot3MauType1000BaseTHD OBJECT-
STATUS
DESCRIPTION "Four-pair Category 5 UTP (per 802.3
40), half duplex mode
::= { dot3MauType 29 }
dot3MauType1000BaseTFD OBJECT-
STATUS
DESCRIPTION "Four-pair Category 5 UTP (per 802.3
40), full duplex mode
::= { dot3MauType 30 }
--
-- The Basic Repeater MAU
--
rpMauTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
DESCRIPTION "Table of descriptive and status
about the MAU(s) attached to the ports of
repeater."
::= { dot3RpMauBasicGroup 1 }
rpMauEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
DESCRIPTION "An entry in the table, containing
about a single MAU."
INDEX { rpMauGroupIndex
rpMauPortIndex
}
::= { rpMauTable 1 }
Smith, et al. Standards Track [Page 12]
RFC 2668 802.3 MAU MIB August 1999
RpMauEntry ::=
SEQUENCE {
rpMauGroupIndex Integer32,
rpMauPortIndex Integer32,
rpMauIndex Integer32,
rpMauType OBJECT IDENTIFIER
rpMauStatus INTEGER
rpMauMediaAvailable INTEGER
rpMauMediaAvailableStateExits Counter32,
rpMauJabberState INTEGER
rpMauJabberingStateEnters Counter32,
rpMauFalseCarriers Counter32
}
rpMauGroupIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
DESCRIPTION "This variable uniquely identifies the
containing the port to which the MAU
by this entry is connected
Note: In practice, a group will generally
a field-replaceable unit (i.e., module, card
or board) that can fit in the physical
enclosure, and the group number will
to a number marked on the physical enclosure
The group denoted by a particular value of
object is the same as the group denoted by
same value of rptrGroupIndex."
REFERENCE "Reference RFC 2108, rptrGroupIndex."
::= { rpMauEntry 1 }
rpMauPortIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
DESCRIPTION "This variable uniquely identifies the
port within group rpMauGroupIndex to which
MAU described by this entry is connected."
REFERENCE "Reference RFC 2108, rptrPortIndex."
::= { rpMauEntry 2 }
rpMauIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
Smith, et al. Standards Track [Page 13]
RFC 2668 802.3 MAU MIB August 1999
DESCRIPTION "This variable uniquely identifies the
described by this entry from among
MAUs connected to the same
(rpMauPortIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 }
rpMauType OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
DESCRIPTION "This object identifies the MAU type.
initial set of MAU types are defined above.
assignment of OBJECT IDENTIFIERs to new types
MAUs is managed by the IANA. If the MAU type
unknown, the object
unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is
syntactically valid object identifier, and
conformant implementation of ASN.1 and the
must be able to generate and recognize
value."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
::= { rpMauEntry 4 }
rpMauStatus OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
operational(3),
standby(4),
shutdown(5),
reset(6)
}
MAX-ACCESS read-
STATUS
DESCRIPTION "The current state of the MAU. This object
be implemented as a read-only object by
agents and MAUs that do not implement
control of the MAU state. Some agents may
support setting the value of this object to
of the enumerated values
The value other(1) is returned if the MAU is
a state other than one of the states 2
6.
Smith, et al. Standards Track [Page 14]
RFC 2668 802.3 MAU MIB August 1999
The value unknown(2) is returned when the MAU'
true state is unknown; for example, when it
being initialized
A MAU in the operational(3) state is
functional, operates, and passes signals to
attached DTE or repeater port in accordance
its specification
A MAU in standby(4) state forces DI and CI
idle and the media transmitter to idle or fault
if supported. Standby(4) mode only applies
link type MAUs. The state
rpMauMediaAvailable is unaffected
A MAU in shutdown(5) state assumes the
condition on DI, CI, and the media
as though it were powered down or not connected
The MAU MAY return other(1) value for
rpMauJabberState and rpMauMediaAvailable
when it is in this state. For an AUI,
state will remove power from the AUI
Setting this variable to the value reset(6)
resets the MAU in the same manner as
power-off, power-on cycle of at least one-
second would. The agent is not required
return the value reset (6).
Setting this variable to the
operational(3), standby(4), or shutdown(5)
causes the MAU to assume the respective
except that setting a mixing-type MAU or an
to standby(4) will cause the MAU to enter
shutdown state."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acResetMAU."
::= { rpMauEntry 5 }
rpMauMediaAvailable OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6),
Smith, et al. Standards Track [Page 15]
RFC 2668 802.3 MAU MIB August 1999
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9),
offline(10),
autoNegError(11)
}
MAX-ACCESS read-
STATUS
DESCRIPTION "If the MAU is a link or fiber type (FOIRL
10BASE-T, 10BASE-F) then this is equivalent
the link test fail state/low light function
For an AUI or a coax (including broadband)
this indicates whether or not loopback
detected on the DI circuit. The value of
attribute persists between packets for MAU
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP
The value other(1) is returned if
mediaAvailable state is not one of 2 through 11.
The value unknown(2) is returned when the MAU'
true state is unknown; for example, when it
being initialized. At power-up or following
reset, the value of this attribute will
unknown for AUI, coax, and 10BASE-FP MAUs.
these MAUs loopback will be tested on
transmission during which no collision
detected. If DI is receiving input when
returns to IDL after a transmission and
has been no collision during the
then loopback will be detected. The value
this attribute will only change
non-collided transmissions for AUI, coax,
10BASE-FP MAUs
For 100Mbps and 1000Mbps MAUs, the
match the states within the respective
integrity state diagrams, fig 32-16, 23-12
24-15 of sections 32, 23 and 24 of [16].
MAU which implements management
auto-negotiation will map remote
indication to remote fault
The value available(3) indicates that the link
light, or loopback is normal. The
notAvailable(4) indicates link loss, low light
or no loopback
Smith, et al. Standards Track [Page 16]
RFC 2668 802.3 MAU MIB August 1999
The value remoteFault(5) indicates that a
has been detected at the remote end of the link
This value applies to 10BASE-FB, 100BASE-T4
End Fault Indication and non-specified
faults from a system running auto-negotiation
The values remoteJabber(7), remoteLinkLoss(8),
and remoteTest(9) SHOULD be used instead
remoteFault(5) where the reason for remote
is identified in the remote signaling protocol
The value invalidSignal(6) indicates that
invalid signal has been received from the
end of the link. InvalidSignal(6) applies
to MAUs of type 10BASE-FB
Where an IEEE Std 802.3u-1995 clause 22
is present, a logic one in the remote fault
(reference section 22.2.4.2.8 of that document
maps to the value remoteFault(5), and a
zero in the link status bit (reference
22.2.4.2.10 of that document) maps to the
notAvailable(4). The value notAvailable(4)
takes precedence over the value remoteFault(5).
Any MAU that implements management of clause 37
Auto-Negotiation will map the received
Fault (RF1 and RF2) bit values for Offline
offline(10), Link Failure to remoteFault(5)
Auto-Negotiation Error to autoNegError(11)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable."
::= { rpMauEntry 6 }
rpMauMediaAvailableStateExits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of the number of times
rpMauMediaAvailable for this MAU instance
the state available(3).
Discontinuities in the value of this counter
occur at re-initialization of the
system, and at other times as indicated by
value of rptrMonitorPortLastChange."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5,
aLoseMediaCounter
RFC 2108, rptrMonitorPortLastChange
Smith, et al. Standards Track [Page 17]
RFC 2668 802.3 MAU MIB August 1999
::= { rpMauEntry 7 }
rpMauJabberState OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
noJabber(3),
jabbering(4)
}
MAX-ACCESS read-
STATUS
DESCRIPTION "The value other(1) is returned if the
state is not 2, 3, or 4. The agent MUST
return other(1) for MAU type dot3MauTypeAUI
The value unknown(2) is returned when the MAU'
true state is unknown; for example, when it
being initialized
If the MAU is not jabbering the agent
noJabber(3). This is the 'normal' state
If the MAU is in jabber state the agent
the jabbering(4) value."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberFlag."
::= { rpMauEntry 8 }
rpMauJabberingStateEnters OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of the number of times
mauJabberState for this MAU instance enters
state jabbering(4). For MAUs of
dot3MauTypeAUI, dot3MauType100BaseT4,
dot3MauType100BaseTX, dot3MauType100BaseFX
all 1000Mbps types, this counter will
indicate zero
Discontinuities in the value of this
can occur at re-initialization of
management system, and at other times
indicated by the value
rptrMonitorPortLastChange."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberCounter
RFC 2108, rptrMonitorPortLastChange
Smith, et al. Standards Track [Page 18]
RFC 2668 802.3 MAU MIB August 1999
::= { rpMauEntry 9 }
rpMauFalseCarriers OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of the number of false carrier
during IDLE in 100BASE-X links. This
does not increment at the symbol rate. It
increment after a valid carrier completion at
maximum rate of once per 100 ms until the
carrier event
This counter increments only for MAUs of
dot3MauType100BaseT4, dot3MauType100BaseTX,
dot3MauType100BaseFX and all 1000Mbps types
For all other MAU types, this counter
always indicate zero
The approximate minimum time for rollover
this counter is 7.4 hours
Discontinuities in the value of this counter
occur at re-initialization of the
system, and at other times as indicated by
value of rptrMonitorPortLastChange."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers
RFC 2108, rptrMonitorPortLastChange
::= { rpMauEntry 10 }
-- The rpJackTable applies to MAUs attached to
-- which have one or more external jacks (connectors).
rpJackTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
DESCRIPTION "Information about the external jacks
to MAUs attached to the ports of a repeater."
::= { dot3RpMauBasicGroup 2 }
rpJackEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
DESCRIPTION "An entry in the table, containing
about a particular jack."
INDEX { rpMauGroupIndex
Smith, et al. Standards Track [Page 19]
RFC 2668 802.3 MAU MIB August 1999
rpMauPortIndex
rpMauIndex
}
::= { rpJackTable 1 }
RpJackEntry ::=
SEQUENCE {
rpJackIndex Integer32,
rpJackType
}
rpJackIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-
STATUS
DESCRIPTION "This variable uniquely identifies the
described by this entry from among other
attached to the same MAU (rpMauIndex)."
::= { rpJackEntry 1 }
rpJackType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
DESCRIPTION "The jack connector type, as it appears on
outside of the system."
::= { rpJackEntry 2 }
--
-- The Basic Interface MAU
--
ifMauTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
DESCRIPTION "Table of descriptive and status
about MAU(s) attached to an interface."
::= { dot3IfMauBasicGroup 1 }
ifMauEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
DESCRIPTION "An entry in the table, containing
about a single MAU."
INDEX { ifMauIfIndex
Smith, et al. Standards Track [Page 20]
RFC 2668 802.3 MAU MIB August 1999
}
::= { ifMauTable 1 }
IfMauEntry ::=
SEQUENCE {
ifMauIfIndex 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
ifMauTypeListBits
}
ifMauIfIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
DESCRIPTION "This variable uniquely identifies the
to which the MAU described by this entry
connected."
REFERENCE "RFC 1213, ifIndex
::= { ifMauEntry 1 }
ifMauIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
DESCRIPTION "This variable uniquely identifies the
described by this entry from among other
connected to the same interface (ifMauIfIndex)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID."
::= { ifMauEntry 2 }
ifMauType OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
DESCRIPTION "This object identifies the MAU type.
initial set of MAU types are defined above.
assignment of OBJECT IDENTIFIERs to new types
Smith, et al. Standards Track [Page 21]
RFC 2668 802.3 MAU MIB August 1999
MAUs is managed by the IANA. If the MAU type
unknown, the object
unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is
syntactically valid object identifier, and
conformant implementation of ASN.1 and the
must be able to generate and recognize
value
This object represents the operational type
the MAU, as determined by either (1) the
of the auto-negotiation function or (2)
auto-negotiation is not enabled or is
implemented for this MAU, by the value of
object ifMauDefaultType. In case (2), a set
the object ifMauDefaultType will force the
into the new operating mode."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType."
::= { ifMauEntry 3 }
ifMauStatus OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
operational(3),
standby(4),
shutdown(5),
reset(6)
}
MAX-ACCESS read-
STATUS
DESCRIPTION "The current state of the MAU. This object
be implemented as a read-only object by
agents and MAUs that do not implement
control of the MAU state. Some agents may
support setting the value of this object to
of the enumerated values
The value other(1) is returned if the MAU is
a state other than one of the states 2
6.
The value unknown(2) is returned when the MAU'
true state is unknown; for example, when it
being initialized
Smith, et al. Standards Track [Page 22]
RFC 2668 802.3 MAU MIB August 1999
A MAU in the operational(3) state is
functional, operates, and passes signals to
attached DTE or repeater port in accordance
its specification
A MAU in standby(4) state forces DI and CI
idle and the media transmitter to idle or fault
if supported. Standby(4) mode only applies
link type MAUs. The state
ifMauMediaAvailable is unaffected
A MAU in shutdown(5) state assumes the
condition on DI, CI, and the media
as though it were powered down or not connected
The MAU MAY return other(1) value for
ifMauJabberState and ifMauMediaAvailable
when it is in this state. For an AUI,
state will remove power from the AUI
Setting this variable to the value reset(6)
resets the MAU in the same manner as
power-off, power-on cycle of at least one-
second would. The agent is not required
return the value reset (6).
Setting this variable to the
operational(3), standby(4), or shutdown(5)
causes the MAU to assume the respective
except that setting a mixing-type MAU or an
to standby(4) will cause the MAU to enter
shutdown state."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acResetMAU."
::= { ifMauEntry 4 }
ifMauMediaAvailable OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9),
offline(10),
autoNegError(11)
Smith, et al. Standards Track [Page 23]
RFC 2668 802.3 MAU MIB August 1999
}
MAX-ACCESS read-
STATUS
DESCRIPTION "If the MAU is a link or fiber type (FOIRL
10BASE-T, 10BASE-F) then this is equivalent
the link test fail state/low light function
For an AUI or a coax (including broadband)
this indicates whether or not loopback
detected on the DI circuit. The value of
attribute persists between packets for MAU
AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP
The value other(1) is returned if
mediaAvailable state is not one of 2 through 11.
The value unknown(2) is returned when the MAU'
true state is unknown; for example, when it
being initialized. At power-up or following
reset, the value of this attribute will
unknown for AUI, coax, and 10BASE-FP MAUs.
these MAUs loopback will be tested on
transmission during which no collision
detected. If DI is receiving input when
returns to IDL after a transmission and
has been no collision during the
then loopback will be detected. The value
this attribute will only change
non-collided transmissions for AUI, coax,
10BASE-FP MAUs
For 100Mbps and 1000Mbps MAUs, the
match the states within the respective
integrity state diagrams, fig 32-16, 23-12
24-15 of sections 32, 23 and 24 of [16].
MAU which implements management
auto-negotiation will map remote
indication to remote fault
The value available(3) indicates that the link
light, or loopback is normal. The
notAvailable(4) indicates link loss, low light
or no loopback
The value remoteFault(5) indicates that a
has been detected at the remote end of the link
This value applies to 10BASE-FB, 100BASE-T4
End Fault Indication and non-specified
faults from a system running auto-negotiation
Smith, et al. Standards Track [Page 24]
RFC 2668 802.3 MAU MIB August 1999
The values remoteJabber(7), remoteLinkLoss(8),
and remoteTest(9) SHOULD be used instead
remoteFault(5) where the reason for remote
is identified in the remote signaling protocol
The value invalidSignal(6) indicates that
invalid signal has been received from the
end of the link. InvalidSignal(6) applies
to MAUs of type 10BASE-FB
Where an IEEE Std 802.3u-1995 clause 22
is present, a logic one in the remote fault
(reference section 22.2.4.2.8 of that document
maps to the value remoteFault(5), and a
zero in the link status bit (reference
22.2.4.2.10 of that document) maps to the
notAvailable(4). The value notAvailable(4)
takes precedence over the value remoteFault(5).
Any MAU that implements management of clause 37
Auto-Negotiation will map the received RF1
RF2 bit values for Offline to offline(10),
Failure to remoteFault(5) and Auto-
Error to autoNegError(11)."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable."
::= { ifMauEntry 5 }
ifMauMediaAvailableStateExits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of the number of times
ifMauMediaAvailable for this MAU instance
the state available(3).
Discontinuities in the value of this counter
occur at re-initialization of the
system, and at other times as indicated by
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5,
aLoseMediaCounter
RFC 2233, ifCounterDiscontinuityTime."
::= { ifMauEntry 6 }
ifMauJabberState OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
noJabber(3),
Smith, et al. Standards Track [Page 25]
RFC 2668 802.3 MAU MIB August 1999
jabbering(4)
}
MAX-ACCESS read-
STATUS
DESCRIPTION "The value other(1) is returned if the
state is not 2, 3, or 4. The agent MUST
return other(1) for MAU type dot3MauTypeAUI
The value unknown(2) is returned when the MAU'
true state is unknown; for example, when it
being initialized
If the MAU is not jabbering the agent
noJabber(3). This is the 'normal' state
If the MAU is in jabber state the agent
the jabbering(4) value."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberFlag."
::= { ifMauEntry 7 }
ifMauJabberingStateEnters OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of the number of times
mauJabberState for this MAU instance enters
state jabbering(4). This counter will
indicate zero for MAUs of type dot1
and those of speeds above 10Mbps
Discontinuities in the value of this counter
occur at re-initialization of the
system, and at other times as indicated by
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6,
aJabber.jabberCounter
RFC 2233, ifCounterDiscontinuityTime."
::= { ifMauEntry 8 }
ifMauFalseCarriers OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
DESCRIPTION "A count of the number of false carrier
during IDLE in 100BASE-X and 1000BASE-X links
For all other MAU types, this counter
Smith, et al. Standards Track [Page 26]
RFC 2668 802.3 MAU MIB August 1999
always indicate zero. This counter does
increment at the symbol rate
It can increment after a valid
completion at a maximum rate of once per 100
for 100BASE-X and once per 10us for 1000BASE-
until the next CarrierEvent
Discontinuities in the value of this counter
occur at re-initialization of the
system, and at other times as indicated by
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers
RFC 2233, ifCounterDiscontinuityTime."
::= { ifMauEntry 9 }
ifMauTypeList OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
A value that uniquely identifies the set
possible IEEE 802.3 types that the MAU could be
The value is a sum which initially takes
value zero. Then, for each type capability
this MAU, 2 raised to the power noted below
added to the sum. For example, a MAU which
the capability to be only 10BASE-T would have
value of 512 (2**9). In contrast, a MAU
supports both 10Base-T (full duplex)
100BASE-TX (full duplex) would have a value
((2**11) + (2**16)) or 67584.
The powers of 2 assigned to the capabilities
these
Power
0 other or
1
2 10BASE-5
3
4 10BASE-2
5 10BASE-T duplex mode
6 10BASE-
7 10BASE-
8 10BASE-FL duplex mode
9 10BROAD36
Smith, et al. Standards Track [Page 27]
RFC 2668 802.3 MAU MIB August 1999
10 10BASE-T half duplex
11 10BASE-T full duplex
12 10BASE-FL half duplex
13 10BASE-FL full duplex
14 100BASE-T
15 100BASE-TX half duplex
16 100BASE-TX full duplex
17 100BASE-FX half duplex
18 100BASE-FX full duplex
19 100BASE-T2 half duplex
20 100BASE-T2 full duplex
If auto-negotiation is present on this MAU,
object will map to ifMauAutoNegCapability
This object has been deprecated in favour
ifMauTypeListBits."
::= { ifMauEntry 10 }
ifMauDefaultType OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
DESCRIPTION "This object identifies the
administrative baseband MAU type, to be used
conjunction with the operational MAU
denoted by ifMauType
The set of possible values for this object
the same as the set defined for the
object
This object represents
administratively-configured type of the MAU.
auto-negotiation is not enabled or is
implemented for this MAU, the value of
object determines the operational type of
MAU. In this case, a set to this object
force the MAU into the specified operating mode
If auto-negotiation is implemented and
for this MAU, the operational type of the
is determined by auto-negotiation, and the
of this object denotes the type to which the
will automatically revert if/
auto-negotiation is later disabled
NOTE TO IMPLEMENTORS: It may be necessary
Smith, et al. Standards Track [Page 28]
RFC 2668 802.3 MAU MIB August 1999
provide for underlying hardware
which do not follow the exact behavior
above. In particular,
ifMauAutoNegAdminStatus transitions from
to disabled, the agent implementation
ensure that the operational type of the MAU (
reported by ifMauType) correctly transitions
the value specified by this object, rather
continuing to operate at the value
determined by the auto-negotiation function."
REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID,
22.2.4.1.4."
::= { ifMauEntry 11 }
ifMauAutoNegSupported OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
DESCRIPTION "This object indicates whether or
auto-negotiation is supported on this MAU."
::= { ifMauEntry 12 }
ifMauTypeListBits OBJECT-
SYNTAX BITS {
bOther(0), -- other or
bAUI(1), --
b10base5(2), -- 10BASE-5
bFoirl(3), --
b10base2(4), -- 10BASE-2
b10baseT(5), -- 10BASE-T duplex mode
b10baseFP(6), -- 10BASE-
b10baseFB(7), -- 10BASE-
b10baseFL(8), -- 10BASE-FL duplex mode
b10broad36(9), -- 10BROAD36
b10baseTHD(10), -- 10BASE-T half duplex
b10baseTFD(11), -- 10BASE-T full duplex
b10baseFLHD(12), -- 10BASE-FL half duplex
b10baseFLFD(13), -- 10BASE-FL full duplex
b100baseT4(14), -- 100BASE-T
b100baseTXHD(15), -- 100BASE-TX half duplex
b100baseTXFD(16), -- 100BASE-TX full duplex
b100baseFXHD(17), -- 100BASE-FX half duplex
b100baseFXFD(18), -- 100BASE-FX full duplex
b100baseT2HD(19), -- 100BASE-T2 half duplex
b100baseT2FD(20), -- 100BASE-T2 full duplex
Smith, et al. Standards Track [Page 29]
RFC 2668 802.3 MAU MIB August 1999
b1000baseXHD(21), -- 1000BASE-X half duplex
b1000baseXFD(22), -- 1000BASE-X full duplex
b1000baseLXHD(23), -- 1000BASE-LX half duplex
b1000baseLXFD(24), -- 1000BASE-LX full duplex
b1000baseSXHD(25), -- 1000BASE-SX half duplex
b1000baseSXFD(26), -- 1000BASE-SX full duplex
b1000baseCXHD(27), -- 1000BASE-CX half duplex
b1000baseCXFD(28), -- 1000BASE-CX full duplex
b1000baseTHD(29), -- 1000BASE-T half duplex
b1000baseTFD(30) -- 1000BASE-T full duplex
}
MAX-ACCESS read-
STATUS
DESCRIPTION "A value that uniquely identifies the set
possible IEEE 802.3 types that the MAU could be
If auto-negotiation is present on this MAU,
object will map to ifMauAutoNegCapability
Note that this MAU may be capable of
as a MAU type that is beyond the scope of
MIB. This is indicated by returning
bit value bOther in addition to any bit
for capabilities that are listed above."
::= { ifMauEntry 13 }
-- The ifJackTable applies to MAUs attached to
-- which have one or more external jacks (connectors).
ifJackTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
DESCRIPTION "Information about the external jacks
to MAUs attached to an interface."
::= { dot3IfMauBasicGroup 2 }
ifJackEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
DESCRIPTION "An entry in the table, containing
about a particular jack."
INDEX { ifMauIfIndex
ifMauIndex
}
::= { ifJackTable 1 }
Smith, et al. Standards Track [Page 30]
RFC 2668 802.3 MAU MIB August 1999
IfJackEntry ::=
SEQUENCE {
ifJackIndex Integer32,
ifJackType
}
ifJackIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-
STATUS
DESCRIPTION "This variable uniquely identifies the
described by this entry from among other
attached to the same MAU."
::= { ifJackEntry 1 }
ifJackType OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
DESCRIPTION "The jack connector type, as it appears on
outside of the system."
::= { ifJackEntry 2 }
-- The ifMauAutoNegTable applies to systems in
-- auto-negotiation is supported on one or more
-- attached to interfaces. Note that if auto-
-- is present and enabled, the ifMauType object
-- the result of the auto-negotiation function
ifMauAutoNegTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
DESCRIPTION "Configuration and status objects for
auto-negotiation function of MAUs attached
interfaces."
::= { dot3IfMauAutoNegGroup 1 }
ifMauAutoNegEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
DESCRIPTION "An entry in the table, containing
and status information for the auto-
function of a particular MAU."
INDEX { ifMauIfIndex
}
Smith, et al. Standards Track [Page 31]
RFC 2668 802.3 MAU MIB August 1999
::= { ifMauAutoNegTable 1 }
IfMauAutoNegEntry ::=
SEQUENCE {
ifMauAutoNegAdminStatus INTEGER
ifMauAutoNegRemoteSignaling INTEGER
ifMauAutoNegConfig INTEGER
ifMauAutoNegCapability Integer32,
ifMauAutoNegCapAdvertised Integer32,
ifMauAutoNegCapReceived Integer32,
ifMauAutoNegRestart INTEGER
ifMauAutoNegCapabilityBits BITS
ifMauAutoNegCapAdvertisedBits BITS
ifMauAutoNegCapReceivedBits BITS
ifMauAutoNegRemoteFaultAdvertised INTEGER
ifMauAutoNegRemoteFaultReceived
}
ifMauAutoNegAdminStatus OBJECT-
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-
STATUS
DESCRIPTION "Setting this object to enabled(1) will
the interface which has the auto-
signaling ability to be enabled
If the value of this object is disabled(2)
the interface will act as it would if it had
auto-negotiation signaling. Under
conditions, an IEEE 802.3 MAU will
be forced to the state indicated by the value
the object ifMauDefaultType
NOTE TO IMPLEMENTORS:
ifMauAutoNegAdminStatus transitions from
to disabled, the agent implementation
ensure that the operational type of the MAU (
reported by ifMauType) correctly transitions
the value specified by the
object, rather than continuing to operate at
value earlier determined by the auto-
function."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.2,
aAutoNegAdminState and 30.6.1.2.2,
acAutoNegAdminControl."
Smith, et al. Standards Track [Page 32]
RFC 2668 802.3 MAU MIB August 1999
::= { ifMauAutoNegEntry 1 }
ifMauAutoNegRemoteSignaling OBJECT-
SYNTAX INTEGER {
detected(1),
notdetected(2)
}
MAX-ACCESS read-
STATUS
DESCRIPTION "A value indicating whether the remote end
the link is using auto-negotiation signaling.
takes the value detected(1) if and only if
during the previous link negotiation, FLP
were received."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.3,
aAutoNegRemoteSignaling."
::= { ifMauAutoNegEntry 2 }
ifMauAutoNegConfig OBJECT-
SYNTAX INTEGER {
other(1),
configuring(2),
complete(3),
disabled(4),
parallelDetectFail(5)
}
MAX-ACCESS read-
STATUS
DESCRIPTION "A value indicating the current status of
auto-negotiation process. The
parallelDetectFail(5) maps to a failure
parallel detection as defined in 28.2.3.1
[IEEE 802.3 Std]."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4,
aAutoNegAutoConfig."
::= { ifMauAutoNegEntry 4 }
ifMauAutoNegCapability OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
A value that uniquely identifies the set
capabilities of the local auto-
entity. The value is a sum which
takes the value zero. Then, for each
of this interface, 2 raised to the power
Smith, et al. Standards Track [Page 33]
RFC 2668 802.3 MAU MIB August 1999
below is added to the sum. For example,
interface which has the capability to
only 100Base-TX half duplex would have a
of 32768 (2**15). In contrast, an
which supports both 100Base-TX half duplex
and 100Base-TX full duplex would have a value
98304 ((2**15) + (2**16)).
The powers of 2 assigned to the capabilities
these
Power
0 other or
(1-9) (reserved
10 10BASE-T half duplex
11 10BASE-T full duplex
12 (reserved
13 (reserved
14 100BASE-T
15 100BASE-TX half duplex
16 100BASE-TX full duplex
17 (reserved
18 (reserved
19 100BASE-T2 half duplex
20 100BASE-T2 full duplex
Note that interfaces that support this MIB
have capabilities that extend beyond the
of this MIB
This object has been deprecated in favour
ifMauAutoNegCapabilityBits
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 5 }
ifMauAutoNegCapAdvertised OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
A value that uniquely identifies the set
capabilities advertised by the
auto-negotiation entity. Refer
ifMauAutoNegCapability for a description of
possible values of this object
Capabilities in this object that are
Smith, et al. Standards Track [Page 34]
RFC 2668 802.3 MAU MIB August 1999
available in ifMauAutoNegCapability cannot
enabled
This object has been deprecated in favour
ifMauAutoNegCapAdvertisedBits
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 6 }
ifMauAutoNegCapReceived OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
DESCRIPTION "********* THIS OBJECT IS DEPRECATED **********
A value that uniquely identifies the set
capabilities received from the
auto-negotiation entity. Refer
ifMauAutoNegCapability for a description of
possible values of this object
Note that interfaces that support this MIB
be attached to remote auto-negotiation
which have capabilities beyond the scope of
MIB
This object has been deprecated in favour
ifMauAutoNegCapReceivedBits
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 7 }
ifMauAutoNegRestart OBJECT-
SYNTAX INTEGER {
restart(1),
norestart(2)
}
MAX-ACCESS read-
STATUS
DESCRIPTION "If the value of this object is set
restart(1) then this will force auto-
to begin link renegotiation. If auto-
signaling is disabled, a write to this
has no effect
Setting the value of this object to norestart(2)
has no effect."
REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1,
Smith, et al. Standards Track [Page 35]
RFC 2668 802.3 MAU MIB August 1999
acAutoNegRestartAutoConfig."
::= { ifMauAutoNegEntry 8 }
ifMauAutoNegCapabilityBits OBJECT-
SYNTAX BITS {
bOther(0), -- other or
b10baseT(1), -- 10BASE-T half duplex
b10baseTFD(2), -- 10BASE-T full duplex
b100baseT4(3), -- 100BASE-T
b100baseTX(4), -- 100BASE-TX half duplex
b100baseTXFD(5), -- 100BASE-TX full duplex
b100baseT2(6), -- 100BASE-T2 half duplex
b100baseT2FD(7), -- 100BASE-T2 full duplex
bfdxPause(8), -- PAUSE for full-duplex
bfdxAPause(9), -- Asymmetric PAUSE for full-
--
bfdxSPause(10), -- Symmetric PAUSE for full-
--
bfdxBPause(11), -- Asymmetric and Symmetric PAUSE
-- full-duplex
b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX
-- duplex
b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX
-- duplex
b1000baseT(14), -- 1000BASE-T half duplex
b1000baseTFD(15) -- 1000BASE-T full duplex
}
MAX-ACCESS read-
STATUS
DESCRIPTION "A value that uniquely identifies the set
capabilities of the local auto-
entity. Note that interfaces that support
MIB may have capabilities that extend beyond
scope of this MIB
Note that the local auto-negotiation entity
support some capabilities beyond the scope
this MIB. This is indicated by returning
bit value bOther in addition to any bit
for capabilities that are listed above."
REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 9 }
ifMauAutoNegCapAdvertisedBits OBJECT-
SYNTAX BITS {
bOther(0), -- other or
b10baseT(1), -- 10BASE-T half duplex
Smith, et al. Standards Track [Page 36]
RFC 2668 802.3 MAU MIB August 1999
b10baseTFD(2), -- 10BASE-T full duplex
b100baseT4(3), -- 100BASE-T
b100baseTX(4), -- 100BASE-TX half duplex
b100baseTXFD(5), -- 100BASE-TX full duplex
b10