As per Relevance of the word reference, we have this rfc below:
Network Working Group K. de
Request for Comments: 2239 3Com
Category: Standards Track D.
Madge Networks Ltd
D.
Cisco Systems Inc
K.
Cisco Systems Inc
S.
Farallon Computing, Inc
November 1997
Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs) using SMIv
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 (1997). All Rights Reserved
Table of
1 The SNMPv2 Network Management Framework ............... 2
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
de Graaf, et. al. Standards Track [Page 1]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
This memo defines an 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/
Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30,
"10 & 100 Mb/s Management," October 26, 1995.
1. The SNMPv2 Network Management
The SNMPv2 Network Management Framework presently consists of
major components. They are
o the SMI, described in RFC 1902 [6] - the mechanisms
for describing and naming objects for the purpose of management
o the MIB-II, STD 17, RFC 1213 [5] - the core set
managed objects for the Internet suite of protocols
o the protocol, STD 15, RFC 1157 [10] and/or RFC 1905 [9] -
the protocol used for accessing managed information
Textual conventions are defined in RFC 1903 [7], and
statements are defined in RFC 1904 [8].
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
1.1. Object
Managed objects are accessed via a virtual information store,
the Management Information Base or MIB. Objects in the MIB
defined using the subset of Abstract Syntax Notation One (ASN.1)
defined in the SMI. In particular, each object type is named by
OBJECT IDENTIFIER, an administratively assigned name. The
type together with an object instance serves to uniquely identify
specific instantiation of the object. For human convenience,
often use a textual string, termed the descriptor, to refer to
object type
de Graaf, et. al. Standards Track [Page 2]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
2.
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
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 100 Mb/s
o auto-negotiation on interface
o jack
2.2. 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 [1] and [2]. These MAUs may be connected to IEEE 802.3
repeaters or to 802.3 (Ethernet-like) interfaces. For
this document refers to these devices as "repeater MAUs"
"interface MAUs."
The definitions presented here are based on Section 30.5, "
Management for 10 & 100 Mb/s Medium Attachment Units (MAUs)",
Annex 30A, "GDMO Specifications for 802.3 managed objects" of
Std 802.3u-1995. That specification includes definitions for
10Mb/s and 100Mb/s devices, and is essentially a superset of
10Mb/s definitions given by IEEE 802.3 Section 20.
specification is intended to serve the same purpose: to provide
management of both 10Mb/s and 100Mb/s MAUs
2.3. Relationship to Other
It is assumed that an agent implementing this MIB will also
(at least) the 'system' group defined in MIB-II [5]. The
sections identify other MIBs that such an agent should implement
2.3.1. Relationship to the MIB-II 'interfaces'
The sections of this document that define interface MAU-
objects specify an extension to the 'interfaces' group of MIB-II.
agent implementing these interface-MAU related objects must
de Graaf, et. al. Standards Track [Page 3]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
implement the 'interfaces' group of MIB-II. 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, RFC 1650.
(Note that repeater ports are not represented as interfaces in
sense of MIB-II's 'interfaces' group.)
2.3.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
[4]. 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
2.4. 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
3.
MAU-MIB DEFINITIONS ::=
Counter32, Integer32,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE
OBJECT-IDENTITY, mib-2
FROM SNMPv2-
TruthValue, TEXTUAL-
de Graaf, et. al. Standards Track [Page 4]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
FROM SNMPv2-
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-
FROM SNMPv2-CONF
mauMod MODULE-
LAST-UPDATED "9710310000Z
ORGANIZATION "IETF HUB MIB Working Group
CONTACT-
"WG E-mail: hubmib@hprnd.rose.hp.
Chair: Dan
Postal: Madge Networks (Israel) Ltd
Atidim Technology Park, Bldg. 3
Tel Aviv 61131,
Tel: 972-3-6458414, 6458458
Fax: 972-3-6487146
E-mail: dromasca@madge.
Editor: Kathryn de
Postal: 3Com
118 Turnpike Rd
Southborough, MA 01772
Tel: (508)229-1627
Fax: (508)490-5882
E-mail: kdegraaf@isd.3com.com
"Management information for 802.3 MAUs
The following references are used throughout
MIB module
[IEEE 802.3 Std
refers to IEEE 802.3/ISO 8802-3
processing systems - Local area networks -
Part 3: Carrier sense multiple access
collision detection (CSMA/CD) access
and physical layer specifications (1993),
and to IEEE Std 802.3u-1995, Supplement
IEEE Std 802.3, clauses 22 through 29.
[IEEE 802.3 Mgt
refers to IEEE 802.3u-1995, - 10 Mb/s &
100 Mb/s Management, Section 30 -
Supplement to IEEE Std 802.3."
::= { snmpDot3MauMgt 6 }
de Graaf, et. al. Standards Track [Page 5]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 }
-- textual
JackType ::= TEXTUAL-
STATUS
"Common enumeration values for repeater
interface MAU jack types."
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)
}
dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
dot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
-- object identities for MAU
-- (see rpMauType and ifMauType for usage
dot3
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 }
dot3MauTypeAUI OBJECT-
STATUS
"no internal MAU, view from AUI
::= { dot3MauType 1 }
dot3MauType10Base5 OBJECT-
STATUS
"thick coax MAU (per 802.3 section 8)"
::= { dot3MauType 2 }
de Graaf, et. al. Standards Track [Page 6]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
dot3MauTypeFoirl OBJECT-
STATUS
"FOIRL MAU (per 802.3 section 9.9)"
::= { dot3MauType 3 }
dot3MauType10Base2 OBJECT-
STATUS
"thin coax MAU (per 802.3 section 10)"
::= { dot3MauType 4 }
dot3MauType10BaseT OBJECT-
STATUS
"UTP MAU (per 802.3 section 14)"
::= { dot3MauType 5 }
dot3MauType10BaseFP OBJECT-
STATUS
"passive fiber MAU (per 802.3 section 16)"
::= { dot3MauType 6 }
dot3MauType10BaseFB OBJECT-
STATUS
"sync fiber MAU (per 802.3 section 17)"
::= { dot3MauType 7 }
dot3MauType10BaseFL OBJECT-
STATUS
"async fiber MAU (per 802.3 section 18)"
::= { dot3MauType 8 }
dot3MauType10Broad36 OBJECT-
STATUS
"broadband DTE MAU (per 802.3 section 11).
that 10BROAD36 MAUs can be attached to
but not to repeaters."
::= { dot3MauType 9 }
------ new since RFC 1515:
dot3MauType10BaseTHD OBJECT-
STATUS
de Graaf, et. al. Standards Track [Page 7]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
"UTP MAU (per 802.3 section 14), half duplex mode
::= { dot3MauType 10 }
dot3MauType10BaseTFD OBJECT-
STATUS
"UTP MAU (per 802.3 section 14), full duplex mode
::= { dot3MauType 11 }
dot3MauType10BaseFLHD OBJECT-
STATUS
"async fiber MAU (per 802.3 section 18),
duplex mode
::= { dot3MauType 12 }
dot3MauType10BaseFLFD OBJECT-
STATUS
"async fiber MAU (per 802.3 section 18),
duplex mode
::= { dot3MauType 13 }
dot3MauType100BaseT4 OBJECT-
STATUS
"4 pair categ. 3 UTP (per 802.3 section 23)"
::= { dot3MauType 14 }
dot3MauType100BaseTXHD OBJECT-
STATUS
"2 pair categ. 5 UTP (per 802.3 section 25),
duplex mode
::= { dot3MauType 15 }
dot3MauType100BaseTXFD OBJECT-
STATUS
"2 pair categ. 5 UTP (per 802.3 section 25),
duplex mode
::= { dot3MauType 16 }
dot3MauType100BaseFXHD OBJECT-
STATUS
"X fiber over PMT (per 802.3 section 26),
de Graaf, et. al. Standards Track [Page 8]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
duplex mode
::= { dot3MauType 17 }
dot3MauType100BaseFXFD OBJECT-
STATUS
"X fiber over PMT (per 802.3 section 26),
duplex mode
::= { dot3MauType 18 }
dot3MauType100BaseT2HD OBJECT-
STATUS
"2 pair categ. 3 UTP (per 802.3 section 32),
duplex mode
::= { dot3MauType 19 }
dot3MauType100BaseT2FD OBJECT-
STATUS
"2 pair categ. 3 UTP (per 802.3 section 32),
duplex mode
::= { dot3MauType 20 }
--
-- The Basic Repeater MAU
--
rpMauTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Table of descriptive and status information
the MAU(s) attached to the ports of a repeater."
::= { dot3RpMauBasicGroup 1 }
rpMauEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the table, containing
about a single MAU."
INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex }
::= { rpMauTable 1 }
de Graaf, et. al. Standards Track [Page 9]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
RpMauEntry ::=
SEQUENCE {
Integer32,
Integer32,
Integer32,
OBJECT IDENTIFIER
INTEGER
INTEGER
Counter32,
INTEGER
Counter32,
Counter32
}
rpMauGroupIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This variable uniquely identifies the
containing the port to which the MAU described
this entry is connected
Note: In practice, a group will generally be
field-replaceable unit (i.e., module, card,
board) that can fit in the physical
enclosure, and the group number will correspond
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."
::= { rpMauEntry 1 }
rpMauPortIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
de Graaf, et. al. Standards Track [Page 10]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
"This variable uniquely identifies the
port within group rpMauGroupIndex to which the
described by this entry is connected."
"Reference RFC 1516, rptrPortIndex."
::= { rpMauEntry 2 }
rpMauIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This variable uniquely identifies the
described by this entry from among other
connected to the same port (rpMauPortIndex)."
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 }
rpMauType OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"This object identifies the 10 or 100 Mb/
baseband MAU type. An initial set of MAU
are defined above. The assignment of
IDENTIFIERs to new types of MAUs is managed by
IANA. If the MAU type is unknown, the
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."
"[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
::= { rpMauEntry 4 }
rpMauStatus OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
operational(3),
de Graaf, et. al. Standards Track [Page 11]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
standby(4),
shutdown(5),
reset(6)
}
MAX-ACCESS read-
STATUS
"The current state of the MAU. This object may
implemented as a read-only object by those
and MAUs that do not implement software control
the MAU state. Some agents may not
setting the value of this object to some of
enumerated values
The value other(1) is returned if the MAU is in
state other than one of the states 2 through 6.
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 to
specification
A MAU in standby(4) state forces DI and CI to
and the media transmitter to idle or fault,
supported. Standby(4) mode only applies to
type MAUs. The state of rpMauMediaAvailable
unaffected
A MAU in shutdown(5) state assumes the
condition on DI, CI, and the media transmitter
though it were powered down or not connected.
MAU may return other(1) value for
rpMauJabberState and rpMauMediaAvailable
when it is in this state. For an AUI, this
will remove power from the AUI
Setting this variable to the value reset(6)
the MAU in the same manner as a power-off, power
on cycle of at least one-half second would.
agent is not required to return the value
(6).
Setting this variable to the value operational(3),
standby(4), or shutdown(5) causes the MAU
de Graaf, et. al. Standards Track [Page 12]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
assume the respective state except that setting
mixing-type MAU or an AUI to standby(4) will
the MAU to enter the shutdown state."
"[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 }
rpMauMediaAvailable OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9)
}
MAX-ACCESS read-
STATUS
"If the MAU is a link or fiber type (FOIRL
10BASE-T, 10BASE-F) then this is equivalent to
link test fail state/low light function. For
AUI or a coax (including broadband) MAU
indicates whether or not loopback is detected
the DI circuit. The value of this
persists between packets for MAU types AUI
10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP
The value other(1) is returned if
mediaAvailable state is not one of 2 through 6.
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 be
for AUI, coax, and 10BASE-FP MAUs. For these
loopback will be tested on each
during which no collision is detected. If DI
receiving input when DO returns to IDL after
transmission and there has been no
during the transmission then loopback will
detected. The value of this attribute will
change during non-collided transmissions for AUI
de Graaf, et. al. Standards Track [Page 13]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
coax, and 10BASE-FP MAUs
For 100BASE-T4, 100BASE-TX and 100BASE-FX
enumerations match the states within
respective link integrity state diagrams, fig 23-
12 and 24-15 of sections 23 and 24 of [2].
MAU which implements management of auto
negotiation will map remote fault indication
remote fault
The value available(3) indicates that the link
light, or loopback is normal. The
notAvailable(4) indicates link loss, low light,
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
The values remoteJabber(7), remoteLinkLoss(8),
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 only
MAUs of type 10BASE-FB
Where an IEEE Std 802.3u-1995 clause 22 MII
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 logic
in the link status bit (reference
22.2.4.2.10 of that document) maps to the
notAvailable(4). The value notAvailable(4)
precedence over the value remoteFault(5)."
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
::= { rpMauEntry 6 }
rpMauMediaAvailableStateExits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"A count of the number of times
de Graaf, et. al. Standards Track [Page 14]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
rpMauMediaAvailable for this MAU instance
the state available(3)."
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter."
::= { rpMauEntry 7 }
rpMauJabberState OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
noJabber(3),
jabbering(4)
}
MAX-ACCESS read-
STATUS
"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."
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberFlag."
::= { rpMauEntry 8 }
rpMauJabberingStateEnters OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"A count of the number of times
mauJabberState for this MAU instance enters
state jabbering(4). For MAUs of
dot3MauTypeAUI, dot3MauType100BaseT4,
dot3MauType100BaseTX, and dot3MauType100BaseFX
this counter will always indicate zero."
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberCounter."
de Graaf, et. al. Standards Track [Page 15]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
::= { rpMauEntry 9 }
rpMauFalseCarriers OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"A count of the number of false carrier
during IDLE in 100BASE-X links. This counter
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. For all other MAU types
this counter will always indicate zero
The approximate minimum time for rollover of
counter is 7.4 hours."
"[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers."
::= { 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
"Information about the external jacks attached
MAUs attached to the ports of a repeater."
::= { dot3RpMauBasicGroup 2 }
rpJackEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the table, containing
about a particular jack."
INDEX { rpMauGroupIndex
rpMauPortIndex
de Graaf, et. al. Standards Track [Page 16]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
rpMauIndex
rpJackIndex }
::= { rpJackTable 1 }
RpJackEntry ::=
SEQUENCE {
Integer32,
}
rpJackIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-
STATUS
"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
"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
"Table of descriptive and status information
MAU(s) attached to an interface."
::= { dot3IfMauBasicGroup 1 }
ifMauEntry OBJECT-
SYNTAX
de Graaf, et. al. Standards Track [Page 17]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
MAX-ACCESS not-
STATUS
"An entry in the table, containing
about a single MAU."
INDEX { ifMauIfIndex, ifMauIndex }
::= { ifMauTable 1 }
IfMauEntry ::=
SEQUENCE {
Integer32,
Integer32,
OBJECT IDENTIFIER
INTEGER
INTEGER
Counter32,
INTEGER
Counter32,
Counter32,
Integer32,
OBJECT IDENTIFIER
}
ifMauIfIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This variable uniquely identifies the
to which the MAU described by this entry
connected."
"RFC 1213, ifIndex
::= { ifMauEntry 1 }
de Graaf, et. al. Standards Track [Page 18]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
ifMauIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This variable uniquely identifies the
described by this entry from among other
connected to the same interface (ifMauIfIndex)."
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID."
::= { ifMauEntry 2 }
ifMauType OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"This object identifies the 10 or 100 Mb/
baseband or broadband MAU type. An initial set
MAU types are defined above. The assignment
OBJECT IDENTIFIERs to new types of MAUs is
by the IANA. If the MAU type is unknown,
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 this value
This object represents the operational type of
MAU, as determined by either (1) the result of
auto-negotiation function or (2) if auto
negotiation is not enabled or is not
for this MAU, by the value of the
ifMauDefaultType. In case (2), a set to
object ifMauDefaultType will force the MAU
the new operating mode."
"[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
::= { ifMauEntry 3 }
ifMauStatus OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
operational(3),
de Graaf, et. al. Standards Track [Page 19]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
standby(4),
shutdown(5),
reset(6)
}
MAX-ACCESS read-
STATUS
"The current state of the MAU. This object may
implemented as a read-only object by those
and MAUs that do not implement software control
the MAU state. Some agents may not
setting the value of this object to some of
enumerated values
The value other(1) is returned if the MAU is in
state other than one of the states 2 through 6.
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 to
specification
A MAU in standby(4) state forces DI and CI to
and the media transmitter to idle or fault,
supported. Standby(4) mode only applies to
type MAUs. The state of ifMauMediaAvailable
unaffected
A MAU in shutdown(5) state assumes the
condition on DI, CI, and the media transmitter
though it were powered down or not connected.
MAU may return other(1) value for
ifMauJabberState and ifMauMediaAvailable
when it is in this state. For an AUI, this
will remove power from the AUI
Setting this variable to the value reset(6)
the MAU in the same manner as a power-off, power
on cycle of at least one-half second would.
agent is not required to return the value
(6).
Setting this variable to the value operational(3),
standby(4), or shutdown(5) causes the MAU
de Graaf, et. al. Standards Track [Page 20]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
assume the respective state except that setting
mixing-type MAU or an AUI to standby(4) will
the MAU to enter the shutdown state."
"[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-
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9)
}
MAX-ACCESS read-
STATUS
"If the MAU is a link or fiber type (FOIRL
10BASE-T, 10BASE-F) then this is equivalent to
link test fail state/low light function. For
AUI or a coax (including broadband) MAU
indicates whether or not loopback is detected
the DI circuit. The value of this
persists between packets for MAU types AUI
10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP
The value other(1) is returned if
mediaAvailable state is not one of 2 through 6.
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 be
for AUI, coax, and 10BASE-FP MAUs. For these
loopback will be tested on each
during which no collision is detected. If DI
receiving input when DO returns to IDL after
transmission and there has been no
during the transmission then loopback will
detected. The value of this attribute will
change during non-collided transmissions for AUI
de Graaf, et. al. Standards Track [Page 21]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
coax, and 10BASE-FP MAUs
For 100BASE-T4, 100BASE-TX and 100BASE-FX
enumerations match the states within
respective link integrity state diagrams, fig 23-
12 and 24-15 of sections 23 and 24 of [2].
MAU which implements management of auto
negotiation will map remote fault indication
remote fault
The value available(3) indicates that the link
light, or loopback is normal. The
notAvailable(4) indicates link loss, low light,
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
The values remoteJabber(7), remoteLinkLoss(8),
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 only
MAUs of type 10BASE-FB
Where an IEEE Std 802.3u-1995 clause 22 MII
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 logic
in the link status bit (reference
22.2.4.2.10 of that document) maps to the
notAvailable(4). The value notAvailable(4)
precedence over the value remoteFault(5)."
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
::= { ifMauEntry 5 }
ifMauMediaAvailableStateExits OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"A count of the number of times
de Graaf, et. al. Standards Track [Page 22]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
ifMauMediaAvailable for this MAU instance
the state available(3)."
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter."
::= { ifMauEntry 6 }
ifMauJabberState OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
noJabber(3),
jabbering(4)
}
MAX-ACCESS read-
STATUS
"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."
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberFlag."
::= { ifMauEntry 7 }
ifMauJabberingStateEnters OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"A count of the number of times
mauJabberState for this MAU instance enters
state jabbering(4). For MAUs of
dot3MauTypeAUI, dot3MauType100BaseT4,
dot3MauType100BaseTX, and dot3MauType100BaseFX
this counter will always indicate zero."
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberCounter."
de Graaf, et. al. Standards Track [Page 23]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
::= { ifMauEntry 8 }
ifMauFalseCarriers OBJECT-
SYNTAX Counter32
MAX-ACCESS read-
STATUS
"A count of the number of false carrier
during IDLE in 100BASE-X links. This counter
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. For all other MAU types
this counter will always indicate zero
The approximate minimum time for rollover of
counter is 7.4 hours."
"[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers."
::= { ifMauEntry 9 }
ifMauTypeList OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"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 the
zero. Then, for each type capability of this MAU
2 raised to the power noted below is added to
sum. For example, a MAU which has the
to be only 10BASE-T would have a value of 512
(2**9). In contrast, a MAU which supports
10Base-T (full duplex) and 100BASE-TX (
duplex) would have a value of ((2**11) + (2**16))
or 67584.
The powers of 2 assigned to the capabilities
these
Power
0 other or
1
de Graaf, et. al. Standards Track [Page 24]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
2 10BASE-5
3
4 10BASE-2
5 10BASE-T duplex mode
6 10BASE-
7 10BASE-
8 10BASE-FL duplex mode
9 10BROAD36
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."
::= { ifMauEntry 10 }
ifMauDefaultType OBJECT-
SYNTAX OBJECT
MAX-ACCESS read-
STATUS
"This object identifies the default
10 or 100 Mb/s baseband MAU type, to be used
conjunction with the operational MAU type
by ifMauType
The set of possible values for this object is
same as the set defined for the ifMauType object
This object represents the administratively
configured type of the MAU. If auto-
is not enabled or is not implemented for this MAU
the value of this object determines
operational type of the MAU. In this case, a
to this object will force the MAU into
specified operating mode
If auto-negotiation is implemented and enabled
this MAU, the operational type of the MAU
de Graaf, et. al. Standards Track [Page 25]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
determined by auto-negotiation, and the value
this object denotes the type to which the MAU
automatically revert if/when auto-negotiation
later disabled
NOTE TO IMPLEMENTORS: It may be necessary
provide for underlying hardware
which do not follow the exact behavior
above. In particular,
ifMauAutoNegAdminStatus transitions from
to disabled, the agent implementation must
that the operational type of the MAU (as
by ifMauType) correctly transitions to the
specified by this object, rather than
to operate at the value earlier determined by
auto-negotiation function."
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID, and [
802.3 Std], 22.2.4.1.4."
::= { ifMauEntry 11 }
ifMauAutoNegSupported OBJECT-
SYNTAX
MAX-ACCESS read-
STATUS
"This object indicates whether or not auto
negotiation is supported on this MAU."
::= { ifMauEntry 12 }
-- The ifJackTable applies to MAUs attached to
-- which have one or more external jacks (connectors).
ifJackTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Information about the external jacks attached
MAUs attached to an interface."
::= { dot3IfMauBasicGroup 2 }
ifJackEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
de Graaf, et. al. Standards Track [Page 26]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
"An entry in the table, containing
about a particular jack."
INDEX { ifMauIfIndex
ifMauIndex
ifJackIndex }
::= { ifJackTable 1 }
IfJackEntry ::=
SEQUENCE {
Integer32,
}
ifJackIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-
STATUS
"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
"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
de Graaf, et. al. Standards Track [Page 27]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
"Configuration and status objects for the auto
negotiation function of MAUs attached
interfaces."
::= { dot3IfMauAutoNegGroup 1 }
ifMauAutoNegEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the table, containing
and status information for the auto-
function of a particular MAU."
INDEX { ifMauIfIndex, ifMauIndex }
::= { ifMauAutoNegTable 1 }
IfMauAutoNegEntry ::=
SEQUENCE {
INTEGER
INTEGER
INTEGER
Integer32,
Integer32,
Integer32,
}
ifMauAutoNegAdminStatus OBJECT-
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-
STATUS
"Setting this object to enabled(1) will cause
interface which has the auto-negotiation
ability to be enabled
de Graaf, et. al. Standards Track [Page 28]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
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 immediately
forced to the state indicated by the value of
object ifMauDefaultType
NOTE TO IMPLEMENTORS:
ifMauAutoNegAdminStatus transitions from
to disabled, the agent implementation must
that the operational type of the MAU (as
by ifMauType) correctly transitions to the
specified by the ifMauDefaultType object,
than continuing to operate at the value
determined by the auto-negotiation function."
"[IEEE 802.3 Mgt], 30.6.1.1.2,
and 30.6.1.2.2, acAutoNegAdminControl."
::= { ifMauAutoNegEntry 1 }
ifMauAutoNegRemoteSignaling OBJECT-
SYNTAX INTEGER {
detected(1),
notdetected(2)
}
MAX-ACCESS read-
STATUS
"A value indicating whether the remote end of
link is using auto-negotiation signaling. It
the value detected(1) if and only if, during
previous link negotiation, FLP Bursts
received."
"[IEEE 802.3 Mgt], 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
de Graaf, et. al. Standards Track [Page 29]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
"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 of [
802.3 Std]."
"[IEEE 802.3 Mgt], 30.6.1.1.4,
aAutoNegAutoConfig."
::= { ifMauAutoNegEntry 4 }
ifMauAutoNegCapability OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"A value that uniquely identifies the set
capabilities of the local auto-negotiation entity
The value is a sum which initially takes the
zero. Then, for each capability of
interface, 2 raised to the power noted below
added to the sum. For example, an interface
has the capability to support only 100Base-TX
duplex would have a value of 32768 (2**15).
contrast, an interface which supports
100Base-TX half duplex and and 100Base-TX
duplex would have a value of 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
de Graaf, et. al. Standards Track [Page 30]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
have capabilities that extend beyond the scope
this MIB."
"[IEEE 802.3 Mgt], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 5 }
ifMauAutoNegCapAdvertised OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"A value that uniquely identifies the set
capabilities advertised by the local auto
negotiation entity. Refer
ifMauAutoNegCapability for a description of
possible values of this object
Capabilities in this object that are not
in ifMauAutoNegCapability cannot be enabled."
"[IEEE 802.3 Mgt], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 6 }
ifMauAutoNegCapReceived OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"A value that uniquely identifies the set
capabilities received from the remote auto
negotiation entity. Refer
ifMauAutoNegCapability for a description of
possible values of this object
Note that interfaces that support this MIB may
attached to remote auto-negotiation entities
have capabilities beyond the scope of this MIB."
"[IEEE 802.3 Mgt], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 7 }
ifMauAutoNegRestart OBJECT-
SYNTAX INTEGER {
restart(1),
norestart(2)
de Graaf, et. al. Standards Track [Page 31]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
}
MAX-ACCESS read-
STATUS
"If the value of this object is set to restart(1)
then this will force auto-negotiation to
link renegotiation. If auto-negotiation
is disabled, a write to this object has no effect
Setting the value of this object to norestart(2)
has no effect."
"[IEEE 802.3 Mgt], 30.6.1.2.1,
acAutoNegRestartAutoConfig."
::= { ifMauAutoNegEntry 8 }
--
-- The Basic Broadband MAU
--
broadMauBasicTable OBJECT-
SYNTAX SEQUENCE OF
MAX-ACCESS not-
STATUS
"Table of descriptive and status information
the broadband MAUs connected to interfaces."
::= { dot3BroadMauBasicGroup 1 }
broadMauBasicEntry OBJECT-
SYNTAX
MAX-ACCESS not-
STATUS
"An entry in the table, containing
about a single broadband MAU."
INDEX { broadMauIfIndex, broadMauIndex }
::= { broadMauBasicTable 1 }
BroadMauBasicEntry ::=
SEQUENCE {
Integer32,
Integer32,
INTEGER
de Graaf, et. al. Standards Track [Page 32]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
Integer32,
Integer32
}
broadMauIfIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This variable uniquely identifies the
to which the MAU described by this entry
connected."
"Reference RFC 1213, ifIndex."
::= { broadMauBasicEntry 1 }
broadMauIndex OBJECT-
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-
STATUS
"This variable uniquely identifies the
connected to interface broadMauIfIndex that
described by this entry."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID."
::= { broadMauBasicEntry 2 }
broadMauXmtRcvSplitType OBJECT-
SYNTAX INTEGER {
other(1),
single(2),
dual(3)
}
MAX-ACCESS read-
STATUS
"This object indicates the type of
multiplexing/cabling system used to separate
transmit and receive paths for the 10BROAD36 MAU
The value other(1) is returned if the split
is not either single or dual
The value single(2) indicates a single
system. The value dual(3) indicates a dual
de Graaf, et. al. Standards Track [Page 33]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
system, offset normally zero."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBbMAUXmitRcvSplitType."
::= { broadMauBasicEntry 3 }
broadMauXmtCarrierFreq OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"This variable indicates the transmit
frequency of the 10BROAD36 MAU in MHz/4; that is
in units of 250 kHz."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBroadbandFrequencies.xmitCarrierFrequency."
::= { broadMauBasicEntry 4 }
broadMauTranslationFreq OBJECT-
SYNTAX Integer32
MAX-ACCESS read-
STATUS
"This variable indicates the translation
frequency of the 10BROAD36 MAU in MHz/4; that is
in units of 250 kHz."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBroadbandFrequencies.translationFrequency."
::= { broadMauBasicEntry 5 }
-- Notifications for use by 802.3
rpMauJabberTrap NOTIFICATION-
OBJECTS { rpMauJabberState }
STATUS
"This trap is sent whenever a managed repeater
enters the jabber state
The agent must throttle the generation
consecutive rpMauJabberTraps so that there is
least a five-second gap between them."
"[IEEE 802.3 Mgt], 30.5.1.3.1,
de Graaf, et. al. Standards Track [Page 34]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
notification."
::= { snmpDot3MauMgt 0 1 }
ifMauJabberTrap NOTIFICATION-
OBJECTS { ifMauJabberState }
STATUS
"This trap is sent whenever a managed
MAU enters the jabber state
The agent must throttle the generation
consecutive ifMauJabberTraps so that there is
least a five-second gap between them."
"[IEEE 802.3 Mgt], 30.5.1.3.1,
notification."
::= { snmpDot3MauMgt 0 2 }
-- Conformance
OBJECT IDENTIFIER ::= { mauMod 1 }
OBJECT IDENTIFIER ::= { mauModConf 1 }
OBJECT IDENTIFIER ::= { mauModConf 2 }
OBJECT IDENTIFIER ::= { mauModConf 3 }
-- Object
mauRpGrpBasic OBJECT-
OBJECTS { rpMauGroupIndex
rpMauPortIndex
rpMauIndex
rpMauType
rpMauStatus
rpMauMediaAvailable
rpMauMediaAvailableStateExits
rpMauJabberState
rpMauJabberingStateEnters }
STATUS
"Basic conformance group for MAUs attached
repeater ports. This group is also
conformance specification for RFC 1515
de Graaf, et. al. Standards Track [Page 35]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
implementations."
::= { mauModObjGrps 1 }
mauRpGrp100Mbs OBJECT-
OBJECTS { rpMauFalseCarriers }
STATUS
"Conformance group for MAUs attached
repeater ports with 100 Mb/s capability."
::= { mauModObjGrps 2 }
mauRpGrpJack OBJECT-
OBJECTS { rpJackType }
STATUS
"Conformance group for MAUs attached
repeater ports with managed jacks."
::= { mauModObjGrps 3 }
mauIfGrpBasic OBJECT-
OBJECTS { ifMauIfIndex
ifMauIndex
ifMauType
ifMauStatus
ifMauMediaAvailable
ifMauMediaAvailableStateExits
ifMauJabberState
ifMauJabberingStateEnters }
STATUS
"Basic conformance group for MAUs attached
interfaces. This group also provides
conformance specification for RFC 1515
implementations."
::= { mauModObjGrps 4 }
mauIfGrp100Mbs OBJECT-
OBJECTS { ifMauFalseCarriers
ifMauTypeList
ifMauDefaultType
ifMauAutoNegSupported }
STATUS
"Conformance group for MAUs
to interfaces with 100 Mb/s capability."
::= { mauModObjGrps 5 }
mauIfGrpJack OBJECT-
de Graaf, et. al. Standards Track [Page 36]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
OBJECTS { ifJackType }
STATUS
"Conformance group for MAUs
to interfaces with managed jacks."
::= { mauModObjGrps 6 }
mauIfGrpAutoNeg OBJECT-
OBJECTS { ifMauAutoNegAdminStatus
ifMauAutoNegRemoteSignaling
ifMauAutoNegConfig
ifMauAutoNegCapability
ifMauAutoNegCapAdvertised
ifMauAutoNegCapReceived
ifMauAutoNegRestart }
STATUS
"Conformance group for MAUs attached
interfaces with managed auto-negotiation."
::= { mauModObjGrps 7 }
mauBroadBasic OBJECT-
OBJECTS { broadMauIfIndex
broadMauIndex
broadMauXmtRcvSplitType
broadMauXmtCarrierFreq
broadMauTranslationFreq }
STATUS
"Conformance group for broadband
attached to interfaces. This
provides a conformance
for RFC 1515 implementations."
::= { mauModObjGrps 8 }
-- Notification
rpMauNotifications NOTIFICATION-
NOTIFICATIONS { rpMauJabberTrap }
STATUS
"Notifications for repeater MAUs."
::= { mauModNotGrps 1 }
ifMauNotifications NOTIFICATION-
NOTIFICATIONS { ifMauJabberTrap }
STATUS
de Graaf, et. al. Standards Track [Page 37]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
"Notifications for interface MAUs."
::= { mauModNotGrps 2 }
--
mauModRpCompl MODULE-
STATUS
"Compliance for MAUs attached to repeater ports."
MODULE -- this
MANDATORY-GROUPS { mauRpGrpBasic }
GROUP mauRpGrp100
"Implementation of this optional group
recommended for MAUs which have 100Mb/
capability."
GROUP
"Implementation of this optional group
recommended for MAUs which have one or
external jacks."
GROUP
"Implementation of this group
recommended for MAUs attached to
ports."
::= { mauModCompls 1 }
mauModIfCompl MODULE-
STATUS
"Compliance for MAUs attached to interfaces."
MODULE -- this
MANDATORY-GROUPS { mauIfGrpBasic }
GROUP mauIfGrp100
"Implementation of this optional group
recommended for MAUs which have 100Mb/
capability."
de Graaf, et. al. Standards Track [Page 38]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
GROUP
"Implementation of this optional group
recommended for MAUs which have one or
external jacks."
GROUP
"Implementation of this group
mandatory for MAUs which
managed auto-negotiation."
GROUP
"Implementation of this group
mandatory for broadband MAUs."
GROUP
"Implementation of this group
recommended for MAUs attached
interfaces."
::= { mauModCompls 2 }
4.
This document was produced by the IETF Hub MIB Working Group,
efforts were greatly advanced by the contributions of the
people
Chuck
John
Jeff
Leon
Mike
Dave
Geoff
Maurice
Paul
Special thanks as well to Dave Perkins for his excellent work on
SMICng compiler, which made it easy to take advantage of the
SNMPv2 constructs in this MIB
de Graaf, et. al. Standards Track [Page 39]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
5.
[1] IEEE 802.3/ISO 8802-3 Information processing systems -
Local area networks - Part 3: Carrier sense
access with collision detection (CSMA/CD) access
and physical layer specifications, 1993.
[2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer,
Attachment Units and Repeater for 100 Mb/s Operation
Type 100BASE-T," Sections 21 through 29, Supplement
IEEE Std 802.3, October 26, 1995.
[3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30,
Supplement to IEEE Std 802.3, October 26, 1995.
[4] de Graaf, K., D. Romascanu, D. McMaster and K
McCloghrie, "Definitions of Managed Objects for
802.3 Repeater Devices using SMIv2", RFC 2108,
1997.
[5] McCloghrie, K. and M. Rose, Editors, "
Information Base for Network Management of TCP/IP-
internets: MIB-II", STD 17, RFC 1213, March 1991.
[6] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser
"Structure of Management Information for version 2 of
Simple Network Management Protocol (SNMPv2)", RFC 1902,
January 1996.
[7] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Conventions for version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1903, January 1996.
[8] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser
"Conformance Statements for version 2 of the Simple
Management Protocol (SNMPv2)", RFC 1904, January 1996.
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "
Operations for version 2 of the Simple Network
Protocol (SNMPv2)", RFC 1905, January 1996.
[10] Case, J., M. Fedor, M. Schoffstall and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, May 1990.
[11] McMaster, D., K. McCloghrie and S. Roberts, "Definitions
Managed Objects for IEEE 802.3 Medium Attachment
(MAUs)", RFC 1515, September 1993.
de Graaf, et. al. Standards Track [Page 40]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
6. Security
Certain management information defined in this MIB may be
sensitive in some network environments. Therefore, authentication
received SNMP requests and controlled access to
information should be employed in such environments. The method
this authentication is a function of the SNMP
Framework, and has not been expanded by this MIB
Several objects in this MIB allow write access. Setting
objects can have a serious effect on the operation of the network
including enabling or disabling a MAU, changing a MAU's default type
enabling, disabling or restarting autonegotiation, or modifying
capabilities that a MAU advertizes during autonegotiation. It
recommended that implementers seriously consider whether
operations should be allowed without providing, at a minimum
authentication of request origin
7. Authors'
Kathryn de
3Com
118 Turnpike Rd
Southborough, MA 01772
Phone: (508)229-1627
Fax: (508)490-5882
EMail: kdegraaf@isd.3com.
Dan
Madge Networks (Israel) Ltd
Atidim Technology Park, Bldg. 3
Tel Aviv 61131,
Phone: 972-3-6458414, 6458458
Fax: 972-3-6487146
EMail: dromasca@madge.
Donna
Cisco Systems Inc
170 West Tasman
San Jose, CA 95134
Phone:: (408) 526-5260
EMail: mcmaster@cisco.
de Graaf, et. al. Standards Track [Page 41]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
Keith
Cisco Systems Inc
170 West Tasman
San Jose, CA 95134
Phone: (408) 526-5260
EMail: kzm@cisco.
Sam
Farallon Computing, Inc
2470 Mariner Square
Alameda, CA 94501-1010
Phone:: (510) 814-5215
EMail: sroberts@farallon.
de Graaf, et. al. Standards Track [Page 42]
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
8. Full Copyright
Copyright (C) The Internet Society (1997). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
de Graaf, et. al. Standards Track [Page 43]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
