Internet Draft 802.3 MAU MIB 14 February 1996
Definitions of Managed Objects
for IEEE 802.3 Medium Attachment Units (MAUs)
14 February 1996
<draft-ietf-hubmib-mau-mib-01.txt>
Dan Romascanu
Madge Networks (Israel) Ltd.
dan@lannet.com
Kathryn de Graaf
3Com Corporation
kdegraaf@isd.3com.com
Status of this Memo
This document is an Internet-Draft. Internet-Drafts are
working documents of the Internet Engineering Task Force
(IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six
months and may be updated, replaced, or obsoleted by other
documents at any time. It is not appropriate to use Internet-
Drafts as reference material or to cite them other than as a
"work in progress".
To learn the current status of any Internet-Draft, please
check the "1id-abstracts.txt" listing contained in the
Internet-Drafts Shadow Directories on ds.internic.net (US East
Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast),
Expires August 1996 [Page 1]
Internet Draft 802.3 MAU MIB 14 February 1996
or munnari.oz.au (Pacific Rim).
Abstract
This memo defines an experimental portion of the Management
Information Base (MIB) for use with network management
protocols in the Internet community. In particular, it
defines objects for managing 10 and 100 Mb/second Medium
Attachment Units (MAUs) based on IEEE Std 802.3 Section 30,
"10 & 100 Mb/s Management," October 26, 1995.
This memo does not specify a standard for the Internet
community.
1. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of several
major components. They include:
o RFC 1902 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of
management.
o STD 17, RFC 1213 defines MIB-II, the core set of managed
objects for the Internet suite of protocols.
o RFC 1905 which defines the protocol used for network
access to managed objects.
The Framework permits new objects to be defined for the
purpose of experimentation and evaluation.
1.1. Object Definitions
Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the
MIB are defined using the subset of Abstract Syntax Notation
One (ASN.1) defined in the SMI. In particular, each object
type is named by an OBJECT IDENTIFIER, an administratively
assigned name. The object type together with an object
instance serves to uniquely identify a specific instantiation
Expires August 1996 [Page 2]
Internet Draft 802.3 MAU MIB 14 February 1996
of the object. For human convenience, we often use a textual
string, termed the descriptor, to refer to the object type.
Expires August 1996 [Page 3]
Internet Draft 802.3 MAU MIB 14 February 1996
2. Overview
Instances of these object types represent attributes of an
IEEE 802.3 MAU. Several types of MAUs are defined in the IEEE
802.3 CSMA/CD standard [1] and [2]. These MAUs may be
connected to IEEE 802.3 repeaters or to 802.3 (Ethernet-like)
interfaces. For convenience this document refers to these
devices as "repeater MAUs" and "interface MAUs."
The definitions presented here are based on Section 30.5,
"Layer Management for 10 & 100 Mb/s Medium Attachment Units
(MAUs)", and Annex 30A, "GDMO Specifications for 802.3 managed
objects" of IEEE Std 802.3u-1995. That specification includes
definitions for both 10Mb/s and 100Mb/s devices, and is
essentially a superset of the 10Mb/s definitions given by IEEE
802.3 Section 20. This specification is intended to serve the
same purpose: to provide for management of both 10Mb/s and
100Mb/s MAUs.
2.1. Relationship to Other MIBs
It is assumed that an agent implementing this MIB will also
implement (at least) the 'system' group defined in MIB-II.
The following sections identify other MIBs that such an agent
should implement.
2.1.1. Relationship to the 'interfaces' group
The sections of this document that define interface MAU-
related objects specify an extension to the 'interfaces' group
of MIB-II. An agent implementing these interface-MAU related
objects must also implement the 'interfaces' group of MIB-II.
The value of the ifMauIfIndex object is the same as the value
of 'ifIndex' used to instantiate the interface to which the
given MAU is connected.
It is expected that an agent implementing the interface-MAU
related objects in this MIB will also implement the Ethernet-
like Interfaces MIB, RFC 1650.
(Note that repeater ports are not represented as interfaces in
the sense of MIB-II's 'interfaces' group.)
Expires August 1996 [Page 4]
Internet Draft 802.3 MAU MIB 14 February 1996
2.1.2. Relationship to the 802.3 Repeater MIB
The section of this document that defines repeater MAU-related
objects specifies an extension to the 802.3 Repeater MIB
defined in [4]. An agent implementing these repeater-MAU
related objects must also implement the 802.3 Repeater MIB.
The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to
instantiate a repeater MAU variable shall be the same as the
values of 'rptrPortGroupIndex' and 'rptrPortIndex' used to
instantiate the port to which the given MAU is connected.
2.2. Management of Internal MAUs
In some situations, a MAU can be "internal" -- i.e., its
functionality is implemented entirely within a device. For
example, a managed repeater may contain an internal repeater-
MAU and/or an internal interface-MAU through which management
communications originating on one of the repeater's external
ports pass in order to reach the management agent associated
with the repeater. Such internal MAUs may or may not be
managed. If they are managed, objects describing their
attributes should appear in the appropriate MIB group --
dot3RpMauBasicGroup for internal repeater-MAUs and
dot3IfMauBasicGroup for internal interface-MAUs.
Expires August 1996 [Page 5]
Internet Draft 802.3 MAU MIB 14 February 1996
3. Definitions
MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS
experimental,
Counter32, Integer32,
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE
FROM SNMPv2-SMI
OBJECT-GROUP, MODULE-COMPLIANCE
FROM SNMPv2-CONF
mib-2
FROM RFC1213-MIB;
mauMod MODULE-IDENTITY
LAST-UPDATED "9602140000Z"
ORGANIZATION "IETF HUB MIB Working Group"
CONTACT-INFO
"WG E-mail: hubmib@hprnd.rose.hp.com
Chair: Dan Romascanu
Postal: Madge Networks (Israel) Ltd.
Atidim Technology Park, Bldg. 3
Tel Aviv 61131, Israel
Tel: 972-3-6458414, 6458458
Fax: 972-3-6487146
E-mail: dan@lannet.com
Editor: Kathryn de Graaf
Postal: 3Com Corporation
118 Turnpike Rd.
Southborough, MA 01772
USA
Tel: (508)229-1627
Fax: (508)490-5882
E-mail: kdegraaf@isd.3com.com"
DESCRIPTION
"Management information for 802.3 MAUs.
The following references are used throughout this
MIB module:
[IEEE 802.3 Std]
refers to IEEE 802.3/ISO 8802-3 Information
Expires August 1996 [Page 6]
Internet Draft 802.3 MAU MIB 14 February 1996
processing systems - Local area networks -
Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method
and physical layer specifications (1993),
and to IEEE Std 802.3u-1995, Supplement to
IEEE Std 802.3, clauses 22 through 29.
[IEEE 802.3 Mgt]
refers to IEEE 802.3u-1995, - 10 Mb/s &
100 Mb/s Management, Section 30 -
Supplement to IEEE Std 802.3."
::= { snmpDot3MauMgt 6 }
snmpDot3MauMgt OBJECT IDENTIFIER ::= { experimental x }
dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
dot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 }
-- object identifiers for MAU types
-- (see rpMauType and ifMauType for usage)
dot3MauType
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 }
dot3MauTypeAUI -- no internal MAU, view from AUI
OBJECT IDENTIFIER ::= { dot3MauType 1 }
dot3MauType10Base5 -- thick coax MAU (per 802.3 section 8)
OBJECT IDENTIFIER ::= { dot3MauType 2 }
dot3MauTypeFoirl -- FOIRL MAU (per 802.3 section 9.9)
OBJECT IDENTIFIER ::= { dot3MauType 3 }
dot3MauType10Base2 -- thin coax MAU (per 802.3 section 10)
OBJECT IDENTIFIER ::= { dot3MauType 4 }
dot3MauType10BaseT -- UTP MAU (per 802.3 section 14)
OBJECT IDENTIFIER ::= { dot3MauType 5 }
dot3MauType10BaseFP -- passive fiber MAU (per 802.3 section 16)
OBJECT IDENTIFIER ::= { dot3MauType 6 }
dot3MauType10BaseFB -- sync fiber MAU (per 802.3 section 17)
OBJECT IDENTIFIER ::= { dot3MauType 7 }
dot3MauType10BaseFL -- async fiber MAU (per 802.3 section 18)
Expires August 1996 [Page 7]
Internet Draft 802.3 MAU MIB 14 February 1996
OBJECT IDENTIFIER ::= { dot3MauType 8 }
dot3MauType10Broad36 -- broadband DTE MAU (per 802.3 section 11)
-- note that 10BROAD36 MAUs can be attached to interfaces but
-- not to repeaters
OBJECT IDENTIFIER ::= { dot3MauType 9 }
-- new for 100 MB/s:
dot3MauType100BaseT4 -- 4 pair categ. 3 UTP (per 802.3 section 23)
OBJECT IDENTIFIER ::= { dot3MauType 10 }
dot3MauType100BaseTX -- 2 pair categ. 5 UTP (per 802.3 section 25)
OBJECT IDENTIFIER ::= { dot3MauType 11 }
dot3MauType100BaseFX -- X fiber over PMT (per 802.3 section 26)
OBJECT IDENTIFIER ::= { dot3MauType 12 }
--
-- The Basic Repeater MAU Table
--
rpMauTable OBJECT-TYPE
SYNTAX SEQUENCE OF RpMauEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of descriptive and status information about
the MAU(s) attached to the ports of a repeater."
::= { dot3RpMauBasicGroup 1 }
rpMauEntry OBJECT-TYPE
SYNTAX RpMauEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single MAU."
INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex }
::= { rpMauTable 1 }
RpMauEntry ::=
SEQUENCE {
rpMauGroupIndex
Integer32,
rpMauPortIndex
Integer32,
Expires August 1996 [Page 8]
Internet Draft 802.3 MAU MIB 14 February 1996
rpMauIndex
Integer32,
rpMauType
OBJECT IDENTIFIER,
rpMauStatus
INTEGER,
rpMauMediaAvail
INTEGER,
rpMauMediaAvailStateExits
Counter32,
rpMauJabberState
INTEGER,
rpMauJabberingStateEnters
Counter32,
rpMauFalseCarriers
Counter32
}
rpMauGroupIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the group
containing the port to which the MAU described by
this entry is connected.
Note: In practice, a group will generally be a
field-replaceable unit (i.e., module, card, or
board) that can fit in the physical system
enclosure, and the group number will correspond to
a number marked on the physical enclosure.
The group denoted by a particular value of this
object is the same as the group denoted by the
same value of rptrGroupIndex."
::= { rpMauEntry 1 }
rpMauPortIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the repeater
port within group rpMauGroupIndex to which the MAU
Expires August 1996 [Page 9]
Internet Draft 802.3 MAU MIB 14 February 1996
described by this entry is connected."
REFERENCE
""
::= { rpMauEntry 2 }
rpMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the MAU
connected to port rpMauPortIndex within group
rpMauGroupIndex that is described by this entry."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID."
::= { rpMauEntry 3 }
rpMauType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the 10 or 100 Mb/s
baseband MAU type. An initial set of MAU types
are defined above. The assignment of OBJECT
IDENTIFIERs to new types of MAUs is managed by the
IANA. If the MAU type is unknown, the object
identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is a
syntactically valid object identifier, and any
conformant implementation of ASN.1 and the BER
must be able to generate and recognize this
value."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
::= { rpMauEntry 4 }
rpMauStatus OBJECT-TYPE
SYNTAX INTEGER {
other(1),
unknown(2),
operational(3),
Expires August 1996 [Page 10]
Internet Draft 802.3 MAU MIB 14 February 1996
standby(4),
shutdown(5),
reset(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The current state of the MAU. This object may be
implemented as a read-only object by those agents
and MAUs that do not implement software control of
the MAU state. Some agents may not support
setting the value of this object to some of the
enumerated values.
The value other(1) is returned if the MAU is in a
state other than one of the states 2 through 6.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized.
A MAU in the operational(3) state is fully
functional, operates, and passes signals to its
attached DTE or repeater port in accordance to its
specification.
A MAU in standby(4) state forces DI and CI to idle
and the media transmitter to idle or fault, if
supported. Standby(4) mode only applies to link
type MAUs. The state of rpMauMediaAvail is
unaffected.
A MAU in shutdown(5) state assumes the same
condition on DI, CI, and the media transmitter as
though it were powered down or not connected. The
MAU may return other(1) value for the
rpMauJabberState and rpMauMediaAvail objects when
it is in this state. For an AUI, this state will
remove power from the AUI.
Setting this variable to the value reset(6) resets
the MAU in the same manner as a power-off, power-
on cycle of at least one-half second would. The
agent is not required to return the value reset
(6).
Expires August 1996 [Page 11]
Internet Draft 802.3 MAU MIB 14 February 1996
Setting this variable to the value operational(3),
standby(4), or shutdown(5) causes the MAU to
assume the respective state except that setting a
mixing-type MAU or an AUI to standby(4) will cause
the MAU to enter the shutdown state."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acRESETMAU."
::= { rpMauEntry 5 }
rpMauMediaAvail OBJECT-TYPE
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the MAU is a link or fiber type (FOIRL,
10BASE-T, 10BASE-F) then this is equivalent to the
link test fail state/low light function. For an
AUI or a coax (including broadband) MAU this
indicates whether or not loopback is detected on
the DI circuit. The value of this attribute
persists between packets for MAU types AUI,
10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
The value other(1) is returned if the mediaAvail
state is not one of 2 through 6.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized. At power-up or following a
reset, the value of this attribute will be unknown
for AUI, coax, and 10BASE-FP MAUs. For these MAUs
loopback will be tested on each transmission
during which no collision is detected. If DI is
Expires August 1996 [Page 12]
Internet Draft 802.3 MAU MIB 14 February 1996
receiving input when DO returns to IDL after a
transmission and there has been no collision
during the transmission then loopback will be
detected. The value of this attribute will only
change during non-collided transmissions for AUI,
coax, and 10BASE-FP MAUs.
For 100BASE-T4, 100BASE-TX and 100BASE-FX the
enumerations match the states within the
respective link integrity state diagrams, fig 23-
12 and 24-15 of sections 23 and 24 of [2]. Any
MAU which implements management of Auto-
Negotiation will map remote fault indication to
remote fault.
The value available(3) indicates that the link,
light, or loopback is normal. The value
notAvailable(4) indicates link loss, low light, or
no loopback.
The value remoteFault(5) indicates that a fault
has been detected at the remote end of the link.
This value applies to 10BASE-FB, 100BASE-T4 Far
End Fault Indication and non-specified remote
faults from a system running Auto-Negotiation.
The values remoteJabber(7), remoteLinkLoss(8), and
remoteTest(9) should be used instead of
remoteFault(5) where the reason for remote fault
is identified in the remote signaling protocol.
The value invalidSignal(6) indicates that an
invalid signal has been received from the other
end of the link. InvalidSignal(6) applies only to
MAUs of type 10BASE-FB.
Where an IEEE Std 802.3u-1995 clause 22 MII is
present, a logic one in the remote fault bit
(reference section 22.2.4.2.8 of that document)
maps to the value remoteFault(5), and a logic zero
in the link status bit (reference section
22.2.4.2.10 of that document) maps to the value
notAvailable(4). The value notAvailable(4) takes
precedence over the value remoteFault(5)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
Expires August 1996 [Page 13]
Internet Draft 802.3 MAU MIB 14 February 1996
::= { rpMauEntry 6 }
rpMauMediaAvailStateExits OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times that
rpMauMediaAvail for this MAU instance leaves the
state available(3)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter."
::= { rpMauEntry 7 }
rpMauJabberState OBJECT-TYPE
SYNTAX INTEGER {
other(1),
unknown(2),
noJabber(3),
jabbering(4)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value other(1) is returned if the jabber
state is not 2, 3, or 4. The agent must always
return other(1) for MAU type dot3MauTypeAUI.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized.
If the MAU is not jabbering the agent returns
noJabber(3). This is the 'normal' state.
If the MAU is in jabber state the agent returns
the jabbering(4) value."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberFlag."
::= { rpMauEntry 8 }
rpMauJabberingStateEnters OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
Expires August 1996 [Page 14]
Internet Draft 802.3 MAU MIB 14 February 1996
STATUS current
DESCRIPTION
"A count of the number of times that
mauJabberState for this MAU instance enters the
state jabbering(4). For MAUs of type
dot3MauTypeAUI, dot3MauType100BaseT4,
dot3MauType100BaseTX, and dot3MauType100BaseFX,
this counter will always indicate zero."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberCounter."
::= { rpMauEntry 9 }
rpMauFalseCarriers OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of false carrier events
during IDLE in 100BASE-X links. This counter does
not increment at the symbol rate. It can
increment after a valid carrier completion at a
maximum rate of once per 100 ms until the next
carrier event.
This counter increments only for MAUs of type
dot3MauType100BaseT4, dot3MauType100BaseTX, and
dot3MauType100BaseFX. For all other MAU types,
this counter will always indicate zero.
The approximate minimum time for rollover of this
counter is 7.4 hours."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers."
::= { rpMauEntry 10 }
-- The rpJackTable applies to MAUs attached to repeaters
-- which have one or more external jacks (connectors).
rpJackTable OBJECT-TYPE
SYNTAX SEQUENCE OF RpJackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
Expires August 1996 [Page 15]
Internet Draft 802.3 MAU MIB 14 February 1996
"Information about the external jacks attached to
MAUs attached to the ports of a repeater."
::= { dot3RpMauBasicGroup 2 }
rpJackEntry OBJECT-TYPE
SYNTAX RpJackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a particular jack."
INDEX { rpJackGroupIndex,
rpJackPortIndex,
rpJackMauIndex,
rpJackIndex }
::= { rpJackTable 1 }
RpJackEntry ::=
SEQUENCE {
rpJackGroupIndex
Integer32,
rpJackPortIndex
Integer32,
rpJackMauIndex
Integer32,
rpJackIndex
Integer32,
rpJackType
INTEGER
}
rpJackGroupIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the group
within containing the port attached to the MAU to
which the jack described by this entry is
connected.
Note: In practice, a group will generally be a
field-replaceable unit (i.e., module, card, or
board) that can fit in the physical system
Expires August 1996 [Page 16]
Internet Draft 802.3 MAU MIB 14 February 1996
enclosure, and the group number will correspond to
a number marked on the physical enclosure.
The group denoted by a particular value of this
object is the same as the group denoted by the
same value of rpMauGroupIndex."
::= { rpJackEntry 1 }
rpJackPortIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the repeater
port within group rpJackGroupIndex attached to the
MAU to which the jack described by this entry is
connected."
REFERENCE
""
::= { rpJackEntry 2 }
rpJackMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the MAU
connected to port rpJackPortIndex within group
rpJackGroupIndex to which the jack that is
described by this entry is connected."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID."
::= { rpJackEntry 3 }
rpJackIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the jack
described by this entry among within other jacks
attached to the MAU denoted by rpJackMauIndex."
::= { rpJackEntry 4 }
rpJackType OBJECT-TYPE
Expires August 1996 [Page 17]
Internet Draft 802.3 MAU MIB 14 February 1996
SYNTAX INTEGER {
other(1),
rj45(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The jack connector type, as it appears on the
outside of the system."
::= { rpJackEntry 5 }
--
-- The Basic Interface MAU Table
--
ifMauTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfMauEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of descriptive and status information about
MAU(s) attached to an interface."
::= { dot3IfMauBasicGroup 1 }
ifMauEntry OBJECT-TYPE
SYNTAX IfMauEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single MAU."
INDEX { ifMauIfIndex, ifMauIndex }
::= { ifMauTable 1 }
IfMauEntry ::=
SEQUENCE {
ifMauIfIndex
Integer32,
ifMauIndex
Integer32,
ifMauType
OBJECT IDENTIFIER,
ifMauStatus
INTEGER,
Expires August 1996 [Page 18]
Internet Draft 802.3 MAU MIB 14 February 1996
ifMauMediaAvail
INTEGER,
ifMauMediaAvailStateExits
Counter32,
ifMauJabberState
INTEGER,
ifMauJabberingStateEnters
Counter32,
ifMauFalseCarriers
Counter32,
ifMauTypeList
Integer32
}
ifMauIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the interface
to which the MAU described by this entry is
connected."
REFERENCE
"RFC 1213, ifIndex"
::= { ifMauEntry 1 }
ifMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the MAU
connected to interface ifMauIfIndex that is
described by this entry."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID."
::= { ifMauEntry 2 }
ifMauType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object identifies the 10 or 100 Mb/s
baseband MAU type. An initial set of MAU types
Expires August 1996 [Page 19]
Internet Draft 802.3 MAU MIB 14 February 1996
are defined above. The assignment of OBJECT
IDENTIFIERs to new types of MAUs is managed by the
IANA. If the MAU type is unknown, the object
identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is a
syntactically valid object identifier, and any
conformant implementation of ASN.1 and the BER
must be able to generate and recognize this
value."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType."
::= { ifMauEntry 3 }
ifMauStatus OBJECT-TYPE
SYNTAX INTEGER {
other(1),
unknown(2),
operational(3),
standby(4),
shutdown(5),
reset(6)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The current state of the MAU. This object may be
implemented as a read-only object by those agents
and MAUs that do not implement software control of
the MAU state. Some agents may not support
setting the value of this object to some of the
enumerated values.
The value other(1) is returned if the MAU is in a
state other than one of the states 2 through 6.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized.
A MAU in the operational(3) state is fully
functional, operates, and passes signals to its
attached DTE or repeater port in accordance to its
Expires August 1996 [Page 20]
Internet Draft 802.3 MAU MIB 14 February 1996
specification.
A MAU in standby(4) state forces DI and CI to idle
and the media transmitter to idle or fault, if
supported. Standby(4) mode only applies to link
type MAUs. The state of ifMauMediaAvail is
unaffected.
A MAU in shutdown(5) state assumes the same
condition on DI, CI, and the media transmitter as
though it were powered down or not connected. The
MAU may return other(1) value for the
ifMauJabberState and ifMauMediaAvail objects when
it is in this state. For an AUI, this state will
remove power from the AUI.
Setting this variable to the value reset(6) resets
the MAU in the same manner as a power-off, power-
on cycle of at least one-half second would. The
agent is not required to return the value reset
(6).
Setting this variable to the value operational(3),
standby(4), or shutdown(5) causes the MAU to
assume the respective state except that setting a
mixing-type MAU or an AUI to standby(4) will cause
the MAU to enter the shutdown state."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState,
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1,
acRESETMAU."
::= { ifMauEntry 4 }
ifMauMediaAvail OBJECT-TYPE
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6),
remoteJabber(7),
remoteLinkLoss(8),
remoteTest(9)
}
Expires August 1996 [Page 21]
Internet Draft 802.3 MAU MIB 14 February 1996
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If the MAU is a link or fiber type (FOIRL,
10BASE-T, 10BASE-F) then this is equivalent to the
link test fail state/low light function. For an
AUI or a coax (including broadband) MAU this
indicates whether or not loopback is detected on
the DI circuit. The value of this attribute
persists between packets for MAU types AUI,
10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
The value other(1) is returned if the mediaAvail
state is not one of 2 through 6.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized. At power-up or following a
reset, the value of this attribute will be unknown
for AUI, coax, and 10BASE-FP MAUs. For these MAUs
loopback will be tested on each transmission
during which no collision is detected. If DI is
receiving input when DO returns to IDL after a
transmission and there has been no collision
during the transmission then loopback will be
detected. The value of this attribute will only
change during non-collided transmissions for AUI,
coax, and 10BASE-FP MAUs.
For 100BASE-T4, 100BASE-TX and 100BASE-FX the
enumerations match the states within the
respective link integrity state diagrams, fig 23-
12 and 24-15 of sections 23 and 24 of [2]. Any
MAU which implements management of Auto-
Negotiation will map remote fault indication to
remote fault.
The value available(3) indicates that the link,
light, or loopback is normal. The value
notAvailable(4) indicates link loss, low light, or
no loopback.
The value remoteFault(5) indicates that a fault
has been detected at the remote end of the link.
This value applies to 10BASE-FB, 100BASE-T4 Far
Expires August 1996 [Page 22]
Internet Draft 802.3 MAU MIB 14 February 1996
End Fault Indication and non-specified remote
faults from a system running Auto-Negotiation.
The values remoteJabber(7), remoteLinkLoss(8), and
remoteTest(9) should be used instead of
remoteFault(5) where the reason for remote fault
is identified in the remote signaling protocol.
The value invalidSignal(6) indicates that an
invalid signal has been received from the other
end of the link. InvalidSignal(6) applies only to
MAUs of type 10BASE-FB.
Where an IEEE Std 802.3u-1995 clause 22 MII is
present, a logic one in the remote fault bit
(reference section 22.2.4.2.8 of that document)
maps to the value remoteFault(5), and a logic zero
in the link status bit (reference section
22.2.4.2.10 of that document) maps to the value
notAvailable(4). The value notAvailable(4) takes
precedence over the value remoteFault(5)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable."
::= { ifMauEntry 5 }
ifMauMediaAvailStateExits OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times that
ifMauMediaAvail for this MAU instance leaves the
state available(3)."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter."
::= { ifMauEntry 6 }
ifMauJabberState OBJECT-TYPE
SYNTAX INTEGER {
other(1),
unknown(2),
noJabber(3),
jabbering(4)
}
MAX-ACCESS read-only
STATUS current
Expires August 1996 [Page 23]
Internet Draft 802.3 MAU MIB 14 February 1996
DESCRIPTION
"The value other(1) is returned if the jabber
state is not 2, 3, or 4. The agent must always
return other(1) for MAU type dot3MauTypeAUI.
The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is
being initialized.
If the MAU is not jabbering the agent returns
noJabber(3). This is the 'normal' state.
If the MAU is in jabber state the agent returns
the jabbering(4) value."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberFlag."
::= { ifMauEntry 7 }
ifMauJabberingStateEnters OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of times that
mauJabberState for this MAU instance enters the
state jabbering(4). For MAUs of type
dot3MauTypeAUI, dot3MauType100BaseT4,
dot3MauType100BaseTX, and dot3MauType100BaseFX,
this counter will always indicate zero."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.6,
aJabber.jabberCounter."
::= { ifMauEntry 8 }
ifMauFalseCarriers OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A count of the number of false carrier events
during IDLE in 100BASE-X links. This counter does
not increment at the symbol rate. It can
increment after a valid carrier completion at a
maximum rate of once per 100 ms until the next
Expires August 1996 [Page 24]
Internet Draft 802.3 MAU MIB 14 February 1996
carrier event.
This counter increments only for MAUs of type
dot3MauType100BaseT4, dot3MauType100BaseTX, and
dot3MauType100BaseFX. For all other MAU types,
this counter will always indicate zero.
The approximate minimum time for rollover of this
counter is 7.4 hours."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers."
::= { ifMauEntry 9 }
ifMauTypeList OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that uniquely identifies the set of
possible IEEE 802.3 types that the MAU could be.
The value is a sum which initially takes the value
zero. Then, for each type capability of this MAU,
2 raised to the power noted below is added to the
sum. For example, a MAU which has the capability
to be only 10BASE-T would have a value of 512
(2**9). In contrast, a MAU which supports both
10Base-T and 100BASE-TX would have a value of 1536
((2**9) + (2**10)).
The powers of 2 assigned to the capabilities are
these:
Power Capability
1 AUI
2 10BASE-5
3 FOIRL
4 10BASE-2
5 10BASE-T
6 10BASE-FP
7 10BASE-FB
8 10BASE-FL
9 10BROAD36
10 100BASE-T4
11 100BASE-TX
12 100BASE-FX
Expires August 1996 [Page 25]
Internet Draft 802.3 MAU MIB 14 February 1996
If auto-negotiation is present on the jack to
which this MAU is attached, this attribute will
map to the ifMauAutoNegCapability."
::= { ifMauEntry 10 }
-- The ifJackTable applies to MAUs attached to interfaces
-- which have one or more external jacks (connectors).
ifJackTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfJackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Information about the external jacks attached to
MAUs attached to an interface."
::= { dot3IfMauBasicGroup 2 }
ifJackEntry OBJECT-TYPE
SYNTAX IfJackEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a particular jack."
INDEX { ifJackIfIndex,
ifJackMauIndex,
ifJackIndex }
::= { ifJackTable 1 }
IfJackEntry ::=
SEQUENCE {
ifJackIfIndex
Integer32,
ifJackMauIndex
Integer32,
ifJackIndex
Integer32,
ifJackType
INTEGER
}
ifJackIfIndex OBJECT-TYPE
SYNTAX Integer32
Expires August 1996 [Page 26]
Internet Draft 802.3 MAU MIB 14 February 1996
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the interface
attached to the MAU to which the jack described by
this entry is connected.
The interface denoted by a particular value of
this object is the same as the group denoted by
the same value of ifMauIfIndex."
::= { ifJackEntry 1 }
ifJackMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the MAU
connected to port ifJackIfIndex to which the jack
that is described by this entry is connected."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID."
::= { ifJackEntry 2 }
ifJackIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the jack
described by this entry among within other jacks
attached to the MAU denoted by ifJackMauIndex."
::= { ifJackEntry 3 }
ifJackType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
rj45(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The jack connector type, as it appears on the
outside of the system."
::= { ifJackEntry 4 }
Expires August 1996 [Page 27]
Internet Draft 802.3 MAU MIB 14 February 1996
-- The ifMauAutoNegTable applies to systems in which
-- auto-negotiation is supported on one or more MAUs
-- attached to interfaces.
ifMauAutoNegTable OBJECT-TYPE
SYNTAX SEQUENCE OF IfMauAutoNegEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Configuration and status objects for the auto-
negotiation function of MAUs attached to
interfaces."
::= { dot3IfMauAutoNegGroup 1 }
ifMauAutoNegEntry OBJECT-TYPE
SYNTAX IfMauAutoNegEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing configuration
and status information for the auto-negotiation
function of a particular MAU."
AUGMENTS { ifMauEntry }
::= { ifMauAutoNegTable 1 }
IfMauAutoNegEntry ::=
SEQUENCE {
ifMauAutoNegAdminStatus
INTEGER,
ifMauAutoNegRemoteSignaling
INTEGER,
ifMauAutoNegConfig
INTEGER,
ifMauAutoNegCapability
Integer32,
ifMauAutoNegCapAdvertised
Integer32,
ifMauAutoNegCapReceived
Integer32,
ifMauAutoNegTechnologyInUse
INTEGER,
ifMauAutoNegRestart
INTEGER
}
Expires August 1996 [Page 28]
Internet Draft 802.3 MAU MIB 14 February 1996
ifMauAutoNegAdminStatus OBJECT-TYPE
SYNTAX INTEGER {
enabled(1),
disabled(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to enabled(1) will cause the
interface which has the auto-negotiation signaling
ability to be enabled. If disabled then the
interface will act as it would if it had no auto-
negotiation signaling.
Under these conditions, an IEEE 802.3 MAU will
immediately be forced to the states indicated by a
write to the object rpMauType or ifMauType.
[Ed.--This doesn't allow for half vs. full
duplex.]"
REFERENCE
"[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState
and 30.6.1.2.2, acAutoNegAdminControl."
::= { ifMauAutoNegEntry 1 }
ifMauAutoNegRemoteSignaling OBJECT-TYPE
SYNTAX INTEGER {
detected(1),
notdetected(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value indicating whether the remote end of the
link is using auto-negotiation signaling. It takes
the value detected(1) if and only if, during the
previous link negotiation, FLP Bursts were
received."
REFERENCE
"[IEEE 802.3 Mgt], 30.6.1.1.3,
aAutoNegRemoteSignaling."
::= { ifMauAutoNegEntry 2 }
ifMauAutoNegConfig OBJECT-TYPE
SYNTAX INTEGER {
other(1),
Expires August 1996 [Page 29]
Internet Draft 802.3 MAU MIB 14 February 1996
configuring(2),
complete(3),
disabled(4),
parallelDetectFail(5)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value indicating the current status of the
auto-negotiation process. The enumeration
parallelDetectFail(5) maps to a failure in
parallel detection as defined in 28.2.3.1 of [IEEE
802.3 Std]."
REFERENCE
"[IEEE 802.3 Mgt], 30.6.1.1.4,
aAutoNegAutoConfig."
::= { ifMauAutoNegEntry 4 }
ifMauAutoNegCapability OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that uniquely identifies the set of
capabilities of the local auto-negotiation entity.
The value is a sum which initially takes the value
zero. Then, for each capability of this
interface, 2 raised to the power noted below is
added to the sum. For example, an interface which
has the capability to support only 100Base-TX
would have a value of 512 (2**9). In contrast, an
interface which supports both 100Base-TX and
100Base-TX Full Duplex would have a value of 1536
((2**9) + (2**10)).
The powers of 2 assigned to the capabilities are
these:
Power Capability
1 other
2 reserved
3 10BASE-T
4 10BASE-T Full Duplex
5 10BASE-FL
6 10BASE-FL Full Duplex
Expires August 1996 [Page 30]
Internet Draft 802.3 MAU MIB 14 February 1996
7 10BASE-FB
8 10BASE-FB Full Duplex
9 100BASE-TX
10 100BASE-TX Full Duplex
11 100BASE-FX
12 100BASE-FX Full Duplex
13 100BASE-T4
For IEEE 802.3 MAUs, the half- and full-duplex
value pairs each map to a single MAU type. For
example, 10BASE-T and 10BASE-T Full Duplex each
use a MAU type of dot3MauType10BaseT.
Note that interfaces that support this MIB may
have capabilities that extend beyond the scope of
this MIB."
REFERENCE
"[IEEE 802.3 Mgt], 30.6.1.1.5,
aAutoNegLocalTechnologyAbility."
::= { ifMauAutoNegEntry 5 }
ifMauAutoNegCapAdvertised OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A value that uniquely identifies the set of
capabilities advertised by the local auto-
negotiation entity. Refer to
ifMauAutoNegCapability for a description of the
possible values of this object.
Capabilities in this object that are not available
in ifMauAutoNegCapability cannot be enabled."
REFERENCE
"[IEEE 802.3 Mgt], 30.6.1.1.6,
aAutoNegAdvertisedTechnologyAbility."
::= { ifMauAutoNegEntry 6 }
ifMauAutoNegCapReceived OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"A value that uniquely identifies the set of
Expires August 1996 [Page 31]
Internet Draft 802.3 MAU MIB 14 February 1996
capabilities received from the remote auto-
negotiation entity. Refer to
ifMauAutoNegCapability for a description of the
possible values of this object.
Note that interfaces that support this MIB may be
attached to remote auto-negotiation entities which
have capabilities beyond the scope of this MIB."
REFERENCE
"[IEEE 802.3 Mgt], 30.6.1.1.7,
aAutoNegReceivedTechnologyAbility."
::= { ifMauAutoNegEntry 7 }
ifMauAutoNegTechnologyInUse OBJECT-TYPE
SYNTAX INTEGER {
other(1),
reserved(2),
t10BASET(3),
t10BASETFD(4),
t10BASEFL(5),
t10BASEFLFD(6),
t10BASEFB(7),
t10BASEFBFD(8),
t100BASETX(9),
t100BASETXFD(10),
t100BASEFX(11),
t100BASEFXFD(12),
t100BASET4(13)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of this object identifies the
technology currently in use on the link to which
this MAU is attached. This value may be a result
of auto- negotiation on the link. If auto-
negotiation is disabled and the MAU is an IEEE
802.3 MAU, this object will change to reflect the
result of a write to the object rpMauType or
ifMauType."
::= { ifMauAutoNegEntry 8 }
ifMauAutoNegRestart OBJECT-TYPE
SYNTAX INTEGER {
Expires August 1996 [Page 32]
Internet Draft 802.3 MAU MIB 14 February 1996
restart(1),
norestart(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"If the value of this object is set to restart(1)
then this will force auto-negotiation to begin
link renegotiation. If auto-negotiation signaling
is disabled, a write to this object has no effect.
Setting the value of this object to norestart(2)
has no effect."
REFERENCE
"[IEEE 802.3 Mgt], 30.6.1.2.1,
acAutoNegRestartAutoConfig."
::= { ifMauAutoNegEntry 9 }
broadMauBasicTable OBJECT-TYPE
SYNTAX SEQUENCE OF BroadMauBasicEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of descriptive and status information about
the broadband MAUs connected to interfaces."
::= { dot3BroadMauBasicGroup 1 }
broadMauBasicEntry OBJECT-TYPE
SYNTAX BroadMauBasicEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"An entry in the table, containing information
about a single broadband MAU."
INDEX { broadMauIfIndex, broadMauIndex }
::= { broadMauBasicTable 1 }
BroadMauBasicEntry ::=
SEQUENCE {
broadMauIfIndex
Integer32,
broadMauIndex
Integer32,
broadMauXmtRcvSplitType
Expires August 1996 [Page 33]
Internet Draft 802.3 MAU MIB 14 February 1996
INTEGER,
broadMauXmtCarrierFreq
Integer32,
broadMauTranslationFreq
Integer32
}
broadMauIfIndex OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the interface
to which the MAU described by this entry is
connected."
REFERENCE
"Reference RFC 1213, ifIndex."
::= { broadMauBasicEntry 1 }
broadMauIndex OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable uniquely identifies the MAU
connected to interface broadMauIfIndex that is
described by this entry."
REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID."
::= { broadMauBasicEntry 2 }
broadMauXmtRcvSplitType OBJECT-TYPE
SYNTAX INTEGER {
other(1),
single(2),
dual(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates the type of frequency
multiplexing/cabling system used to separate the
transmit and receive paths for the 10BROAD36 MAU.
The value other(1) is returned if the split type
Expires August 1996 [Page 34]
Internet Draft 802.3 MAU MIB 14 February 1996
is not either single or dual.
The value single(2) indicates a single cable
system. The value dual(3) indicates a dual cable
system, offset normally zero."
REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBbMAUXmitRcvSplitType."
::= { broadMauBasicEntry 3 }
broadMauXmtCarrierFreq OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable indicates the transmit carrier
frequency of the 10BROAD36 MAU in MHz/4; that is,
in units of 250 kHz."
REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBroadbandFrequencies.xmitCarrierFrequency."
::= { broadMauBasicEntry 4 }
broadMauTranslationFreq OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This variable indicates the translation offset
frequency of the 10BROAD36 MAU in MHz/4; that is,
in units of 250 kHz."
REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBroadbandFrequencies.translationFrequency."
::= { broadMauBasicEntry 5 }
-- Notifications for use by 802.3 MAUs
rpMauJabberTrap NOTIFICATION-TYPE
OBJECTS { rpMauJabberState }
STATUS current
DESCRIPTION
"This trap is sent whenever a managed repeater MAU
Expires August 1996 [Page 35]
Internet Draft 802.3 MAU MIB 14 February 1996
enters the jabber state.
The agent must throttle the generation of
consecutive rpMauJabberTraps so that there is at
least a five-second gap between them."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
notification."
::= { snmpDot3MauMgt 0 1 }
ifMauJabberTrap NOTIFICATION-TYPE
OBJECTS { ifMauJabberState }
STATUS current
DESCRIPTION
"This trap is sent whenever a managed interface
MAU enters the jabber state.
The agent must throttle the generation of
consecutive ifMauJabberTraps so that there is at
least a five-second gap between them."
REFERENCE
"[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber
notification."
::= { snmpDot3MauMgt 0 2 }
-- Conformance information
mauModConf
OBJECT IDENTIFIER ::= { mauMod 1 }
mauModCompls
OBJECT IDENTIFIER ::= { mauModConf 1 }
mauModObjGrps
OBJECT IDENTIFIER ::= { mauModConf 2 }
mauModNotGrps
OBJECT IDENTIFIER ::= { mauModConf 3 }
-- Object groups
mauRpGrpBasic OBJECT-GROUP
OBJECTS { rpMauGroupIndex,
rpMauPortIndex,
rpMauIndex,
rpMauType,
Expires August 1996 [Page 36]
Internet Draft 802.3 MAU MIB 14 February 1996
rpMauStatus,
rpMauMediaAvail,
rpMauMediaAvailStateExits,
rpMauJabberState,
rpMauJabberingStateEnters }
STATUS current
DESCRIPTION
"Basic conformance group for MAUs attached to
repeater ports. This group is also the
conformance specification for RFC 1515
implementations."
::= { mauModObjGrps 1 }
mauRpGrpExtended OBJECT-GROUP
OBJECTS { rpMauFalseCarriers,
rpJackGroupIndex,
rpJackPortIndex,
rpJackMauIndex,
rpJackIndex,
rpJackType }
STATUS current
DESCRIPTION
"Conformance group for MAUs attached to
repeater ports with extended management
(including 100 Mb/s and jack management)."
::= { mauModObjGrps 2 }
mauIfGrpBasic OBJECT-GROUP
OBJECTS { ifMauIfIndex,
ifMauIndex,
ifMauType,
ifMauStatus,
ifMauMediaAvail,
ifMauMediaAvailStateExits,
ifMauJabberState,
ifMauJabberingStateEnters }
STATUS current
DESCRIPTION
"Basic conformance group for MAUs attached to
interfaces. This group also provides a
conformance specification for RFC 1515
implementations."
::= { mauModObjGrps 3 }
Expires August 1996 [Page 37]
Internet Draft 802.3 MAU MIB 14 February 1996
mauIfGrpExtended OBJECT-GROUP
OBJECTS { ifMauFalseCarriers,
ifMauTypeList,
ifJackIfIndex,
ifJackMauIndex,
ifJackIndex,
ifJackType }
STATUS current
DESCRIPTION
"Conformance group for MAUs attached
to interfaces with extended management
(including 100 Mb/s and jack management)."
::= { mauModObjGrps 4 }
mauIfGrpAutoNeg OBJECT-GROUP
OBJECTS { ifMauAutoNegAdminStatus,
ifMauAutoNegRemoteSignaling,
ifMauAutoNegConfig,
ifMauAutoNegCapability,
ifMauAutoNegCapAdvertised,
ifMauAutoNegCapReceived,
ifMauAutoNegTechnologyInUse,
ifMauAutoNegRestart }
STATUS current
DESCRIPTION
"Conformance group for MAUs attached to
interfaces with managed auto-negotiation."
::= { mauModObjGrps 5 }
mauBroadBasic OBJECT-GROUP
OBJECTS { broadMauIfIndex,
broadMauIndex,
broadMauXmtRcvSplitType,
broadMauXmtCarrierFreq,
broadMauTranslationFreq }
STATUS current
DESCRIPTION
"Conformance group for broadband MAUs
attached to interfaces. This group
provides a conformance specification
for RFC 1515 implementations."
::= { mauModObjGrps 6 }
Expires August 1996 [Page 38]
Internet Draft 802.3 MAU MIB 14 February 1996
-- Notification groups
-- ?? later
-- Compliances
mauModRpCompl MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance for MAUs attached to repeater ports."
MODULE -- this module
MANDATORY-GROUPS { mauRpGrpBasic }
GROUP mauRpGrpExtended
DESCRIPTION
"Implementation of this optional group is
recommended for MAUs which have 100Mb/s
capability and/or more than one attached
external jack."
::= { mauModCompls 1 }
mauModIfCompl MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"Compliance for MAUs attached to interfaces."
MODULE -- this module
MANDATORY-GROUPS { mauIfGrpBasic }
GROUP mauIfGrpExtended
DESCRIPTION
"Implementation of this optional group is
recommended for MAUs which have 100Mb/s
capability and/or more than one attached
external jack."
GROUP mauIfGrpAutoNeg
DESCRIPTION
"Implementation of this optional group
is recommended for MAUs which support
managed auto-negotiation."
Expires August 1996 [Page 39]
Internet Draft 802.3 MAU MIB 14 February 1996
GROUP mauBroadBasic
DESCRIPTION
"Implementation of this group is
mandatory for broadband MAUs."
::= { mauModCompls 2 }
END
Expires August 1996 [Page 40]
Internet Draft 802.3 MAU MIB 14 February 1996
4. References
[1] IEEE 802.3/ISO 8802-3 Information processing systems -
Local area networks - Part 3: Carrier sense multiple
access with collision detection (CSMA/CD) access method
and physical layer specifications, 1993.
[2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium
Attachment Units and Repeater for 100 Mb/s Operation,
Type 100BASE-T," Sections 21 through 29, Supplement to
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] Romascanu, D., and K. de Graaf, "Definitions of Managed
Objects for IEEE 802.3 Repeater Devices", February 1996.
Expires August 1996 [Page 41]
