As per Relevance of the word reference, we have this rfc below:
Network Working Group D.
Request for Comments: 1515 SynOptics Communications, Inc
K.
Hughes LAN Systems, Inc
S.
Farallon Computing, Inc
September 1993
Definitions of Managed
for IEEE 802.3 Medium Attachment Units (MAUs
Status of this
This RFC 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" for the standardization state and
of this protocol. Distribution of this memo is unlimited
This document defines a portion of the Management Information
(MIB) for use with network management protocols in TCP/IP-
internets. In particular, it defines objects for managing IEEE 802.3
Medium Attachment Units (MAUs).
Table of
1. The Network Management Framework ...................... 2
2. Objects ............................................... 2
3. Overview .............................................. 2
3.1 Terminology .......................................... 3
3.2 Structure of MIB ..................................... 3
3.2.1 The Repeater MAU Basic Group Definitions ........... 3
3.2.2 The Interface MAU Basic Group Definitions .......... 3
3.2.3 The Broadband MAU Basic Group Definitions .......... 3
3.3 Relationship to Other MIBs ........................... 3
3.3.1 Relationship to the 'system' group ................. 3
3.3.2 Relationship to the 'interfaces' group ............. 4
3.3.3 Relationship to the 802.3 Repeater MIB ............. 4
3.4 Management of Internal MAUs .......................... 4
4. Definitions ........................................... 5
4.1 Groups in the Repeater MAU MIB ....................... 5
4.1.1 The Repeater MAU Basic Group Definitions ........... 6
4.1.2 The Interface MAU Basic Group Definitions .......... 12
4.1.3 The Broadband MAU Basic Group Definitions .......... 18
4.2 Traps for use by 802.3 MAUs .......................... 20
McMaster, McCloghrie & Roberts [Page 1]
RFC 1515 802.3 MAU MIB September 1993
5. Acknowledgments ....................................... 21
6. References ............................................ 23
7. Security Considerations ............................... 24
8. Authors' Addresses .................................... 25
1. The Network Management
The Internet-standard Network Management Framework consists of
components. They are
STD 16, RFC 1155 [1] which defines the SMI, the mechanisms
for describing and naming objects for the purpose of management
STD 16, RFC 1212 [7] defines a more concise description mechanism
which is wholly consistent with the SMI
STD 17, RFC 1213 [4] which defines MIB-II, the core set of
objects for the Internet suite of protocols
STD 15, RFC 1157 [3] which defines the SNMP, the protocol used
network access to managed objects
The Framework permits new objects to be defined for the purpose
experimentation and evaluation
2. 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 object type is
by an OBJECT IDENTIFIER, an administratively assigned name.
object type together with an object instance serves to
identify a specific instantiation of the object. For
convenience, we often use a textual string, termed the descriptor,
refer to the object type
3.
Instances of the object types defined in this document
attributes of an IEEE 802.3 MAU. Several types of MAUs are
in the IEEE 802.3/ISO 8802-3 CSMA/CD standard [9].
These MAUs may be connected to IEEE 802.3 repeaters or to 802.3
(Ethernet-like) interfaces. For convenience this document refers
these devices as "repeater MAUs" and "interface MAUs."
The definitions presented here are based on Draft 5 of Section 20
IEEE P802.3p, "Layer Management for 10 Mb/s Medium Attachment
McMaster, McCloghrie & Roberts [Page 2]
RFC 1515 802.3 MAU MIB September 1993
(MAUs), Section 20" [10] dated 11 July 1992.
3.1.
Refer to Section 3.1.2 of [13] for simple definitions of the
"repeater," "port," and "MAU" as used in the context of
document. For a more complete and precise definition of these terms
refer to Section 9 of [9].
3.2. Structure of
Objects in this MIB are arranged into MIB groups. Each MIB group
organized as a set of related objects
3.2.1. The Repeater MAU Basic Group
This group contains all repeater MAU-related configuration, status
and control objects. Implementation of the dot3RpMauBasicGroup
mandatory for MAUs attached to repeaters
3.2.2. The Interface MAU Basic Group
This group contains all interface MAU-related configuration, status
and control objects. Implementation of the dot3IfMauBasicGroup
mandatory for MAUs attached to interfaces
3.2.3. The Broadband MAU Basic Group
This group contains all broadband-specific MAU-related
objects. Implementation of the dot3BroadMauBasicGroup is
for 10BROAD36 MAUs, and is not appropriate for other types of MAUs
3.3. Relationship to Other
It is assumed that an agent implementing this MIB will also
(at least) the 'system' group defined in MIB-II [4]. The
sections identify other MIBs that such an agent should implement
3.3.1. Relationship to the 'system'
In MIB-II, the 'system' group is defined as being mandatory for
systems such that each managed entity contains one instance of
object in the 'system' group. Thus, those objects apply to
entity even if the entity's sole functionality is management of
MAU
McMaster, McCloghrie & Roberts [Page 3]
RFC 1515 802.3 MAU MIB September 1993
3.3.2. Relationship to the 'interfaces'
The sections of this document that define interface MAU-
objects specify an extension to the 'interfaces' group of MIB-II [4].
An agent implementing these interface-MAU related objects must
implement the 'interfaces' group of MIB-II. The value of the same
the value of 'ifIndex' used to instantiate the interface to which
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 [11].
(Note that repeater ports are not represented as interfaces in
sense of MIB-II's 'interfaces' group. See section 3.4.2 of
repeater MIB [12] for more details.)
3.3.3. 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
[13]. An agent implementing these repeater-MAU related objects
also implement the 802.3 Repeater MIB
The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used
instantiate a repeater MAU variable shall be the same as the
of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate
port to which the given MAU is connected
3.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 group -- dot3RpMauBasicGroup for internal repeater-MAUs
dot3IfMauBasicGroup for internal interface-MAUs
McMaster, McCloghrie & Roberts [Page 4]
RFC 1515 802.3 MAU MIB September 1993
4.
MAU-MIB DEFINITIONS ::=
Counter FROM RFC1155-
OBJECT-TYPE FROM RFC-1212
TRAP-TYPE FROM RFC-1215;
snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 }
--
--
-- The following references are used throughout this MIB
--
-- [RFC 1213]
-- refers to McCloghrie, K., and M. Rose, Editors
-- Management Information Base for Network
-- of TCP/IP-based internets: MIB-II, STD 17, RFC 1213,
-- Hughes LAN Systems, Performance Systems International
-- March 1991.
--
-- [RFC 1368]
-- refers to McMaster, D., and K. McCloghrie, Editors
-- Definitions of Managed Objects for IEEE 802.3
-- Devices, RFC 1368, SynOptics Communications,
-- LAN Systems, October 1992.
--
-- [IEEE 802.3 MAU Mgt
-- refers to IEEE P802.3p, 'Layer Management for 10 Mb/
-- Medium Access Unit (MAUs), Section 20,' Draft
-- to ANSI/IEEE 802.3, Draft 5, 11 July 1992.
-- MIB
--
-- The dot3RpMauBasicGroup is mandatory for MAUs attached
-- repeaters
-- The dot3IfMauBasicGroup is mandatory for MAUs attached
-- DTEs (interfaces).
-- The dot3BroadMauBasicGroup is mandatory for broadband
-- attached to DTEs
dot3
McMaster, McCloghrie & Roberts [Page 5]
RFC 1515 802.3 MAU MIB September 1993
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
dot3
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
dot3
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
-- object identifiers for MAU
-- (see rpMauType and ifMauType for usage
dot3
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 }
dot3MauTypeAUI -- no internal MAU, view from
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)
OBJECT IDENTIFIER ::= { dot3MauType 8 }
dot3MauType10Broad36 -- broadband DTE MAU (per 802.3 section 11)
-- note that 10BROAD36 MAUs can be attached to interfaces
-- not to
OBJECT IDENTIFIER ::= { dot3MauType 9 }
--
-- The Repeater MAU Basic
--
-- Implementation of the Repeater MAU Basic Group is
-- for MAUs attached to repeaters
--
-- The Basic Repeater MAU
--
rpMauTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
McMaster, McCloghrie & Roberts [Page 6]
RFC 1515 802.3 MAU MIB September 1993
"Table of descriptive and status information
the MAU(s) attached to the ports of a repeater."
::= { dot3RpMauBasicGroup 1 }
rpMauEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"An entry in the table, containing
about a single MAU."
INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex }
::= { rpMauTable 1 }
RpMauEntry ::=
SEQUENCE {
INTEGER
INTEGER
INTEGER
OBJECT IDENTIFIER
INTEGER
INTEGER
Counter
INTEGER
}
rpMauGroupIndex OBJECT-
SYNTAX INTEGER (1..1024)
ACCESS read-
STATUS
"This variable uniquely identifies the
group containing the port to which the
described by this entry is connected."
"Reference RFC1368, rptrGroupIndex."
::= { rpMauEntry 1 }
McMaster, McCloghrie & Roberts [Page 7]
RFC 1515 802.3 MAU MIB September 1993
rpMauPortIndex OBJECT-
SYNTAX INTEGER (1..1024)
ACCESS read-
STATUS
"This variable uniquely identifies the
port within group rpMauGroupIndex to which the
described by this entry is connected."
"Reference RFC 1368, rptrPortIndex."
::= { rpMauEntry 2 }
rpMauIndex OBJECT-
SYNTAX INTEGER (1..9)
ACCESS read-
STATUS
"This variable uniquely identifies the
connected to port rpMauPortIndex within
rpMauGroupIndex that is described by this entry."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID."
::= { rpMauEntry 3 }
rpMauType OBJECT-
SYNTAX OBJECT
ACCESS read-
STATUS
"This object identifies the 10 Mb/s baseband
type. An initial set of MAU types are
above. The assignment of OBJECT IDENTIFIERs
new types of MAUs is managed by the IANA. If
MAU type is unknown, the object
unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is
syntactically valid object identifier, and
conformant implementation of ASN.1 and the
must be able to generate and recognize
value."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aMAUType."
::= { rpMauEntry 4 }
rpMauStatus OBJECT-
McMaster, McCloghrie & Roberts [Page 8]
RFC 1515 802.3 MAU MIB September 1993
SYNTAX INTEGER {
other(1),
unknown(2),
operational(3),
standby(4),
shutdown(5),
reset(6)
}
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 and
media transmitter to idle. Standby(4) mode
applies to link type MAUs. The state
rpMauMediaAvailable is unaffected
A MAU in shutdown(5) state assumes the
condition on DI, CI, and the media transmitter
though it were powered down. The MAU may
other(1) value for the mauJabber
rpMauMediaAvailable objects when it is in
state. For an AUI, this state will remove
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).
McMaster, McCloghrie & Roberts [Page 9]
RFC 1515 802.3 MAU MIB September 1993
Setting this variable to the value operational(3),
standby(4), or shutdown(5) causes the MAU
assume the respective state except that setting
mixing-type MAU or an AUI to standby(4) will
the MAU to enter the shutdown state."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aMAUAdminState, and 20.2.3.3,
and acResetMAUAction."
::= { rpMauEntry 5 }
rpMauMediaAvailable OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6)
}
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
coax, and 10BASE-FP MAUs
McMaster, McCloghrie & Roberts [Page 10]
RFC 1515 802.3 MAU MIB September 1993
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
The value invalidSignal(6) indicates that
invalid signal has been received from the
end of the link. Both remoteFault(5)
invalidSignal(6) apply only to MAUs of
10BASE-FB."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aMediaAvailable."
::= { rpMauEntry 6 }
rpMauMediaAvailableStateExits OBJECT-
SYNTAX
ACCESS read-
STATUS
"A count of the number of times
rpMauMediaAvailable for this MAU instance
the state available(3)."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
lostMediaCount."
::= { rpMauEntry 7 }
rpMauJabberState OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
noJabber(3),
jabbering(4)
}
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
McMaster, McCloghrie & Roberts [Page 11]
RFC 1515 802.3 MAU MIB September 1993
If the MAU is not jabbering the agent
noJabber(3). This is the 'normal' state
If the MAU is in jabber state the agent
the jabbering(4) value."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aJabber.jabberFlag."
::= { rpMauEntry 8 }
rpMauJabberingStateEnters OBJECT-
SYNTAX
ACCESS read-
STATUS
"A count of the number of times
rpMauJabberState for this MAU instance enters
state jabbering(4). For a MAU of
dot3MauTypeAUI, this counter will always
zero."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aJabber.jabberCounter."
::= { rpMauEntry 9 }
--
-- The Interface MAU Basic
--
-- Implementation of the Interface MAU Basic Group is
-- for MAUs attached to DTEs (interfaces).
--
-- The Basic Interface MAU
--
ifMauTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"Table of descriptive and status information
the MAU(s) attached to an interface."
::= { dot3IfMauBasicGroup 1 }
ifMauEntry OBJECT-
SYNTAX
ACCESS not-
McMaster, McCloghrie & Roberts [Page 12]
RFC 1515 802.3 MAU MIB September 1993
STATUS
"An entry in the table, containing
about a single MAU."
INDEX { ifMauIfIndex, ifMauIndex }
::= { ifMauTable 1 }
IfMauEntry ::=
SEQUENCE {
INTEGER
INTEGER
OBJECT IDENTIFIER
INTEGER
INTEGER
Counter
INTEGER
}
ifMauIfIndex OBJECT-
SYNTAX
ACCESS read-
STATUS
"This variable uniquely identifies the
to which the MAU described by this entry
connected."
"Reference RFC 1213, ifIndex."
::= { ifMauEntry 1 }
ifMauIndex OBJECT-
SYNTAX INTEGER (1..9)
ACCESS read-
STATUS
"This variable uniquely identifies the
connected to interface ifMauIfIndex that
described by this entry."
McMaster, McCloghrie & Roberts [Page 13]
RFC 1515 802.3 MAU MIB September 1993
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID."
::= { ifMauEntry 2 }
ifMauType OBJECT-
SYNTAX OBJECT
ACCESS read-
STATUS
"This object identifies the 10 Mb/s baseband
broadband 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."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aMAUType."
::= { ifMauEntry 3 }
ifMauStatus OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
operational(3),
standby(4),
shutdown(5),
reset(6)
}
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.
McMaster, McCloghrie & Roberts [Page 14]
RFC 1515 802.3 MAU MIB September 1993
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 and
media transmitter to idle. Standby(4) mode
applies to link type MAUs. The state
ifMauMediaAvailable is unaffected
A MAU in shutdown(5) state assumes the
condition on DI, CI, and the media transmitter
though it were powered down. The MAU may
other(1) value for the mauJabber
ifMauMediaAvailable objects when it is in
state. For an AUI, this state will remove
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
assume the respective state except that setting
mixing-type MAU or an AUI to standby(4) will
the MAU to enter the shutdown state."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aMAUAdminState, and 20.2.3.3,
and acResetMAUAction."
::= { ifMauEntry 4 }
ifMauMediaAvailable OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
available(3),
notAvailable(4),
remoteFault(5),
invalidSignal(6)
}
McMaster, McCloghrie & Roberts [Page 15]
RFC 1515 802.3 MAU MIB September 1993
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
coax, and 10BASE-FP MAUs
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
The value invalidSignal(6) indicates that
invalid signal has been received from the
end of the link. Both remoteFault(5)
invalidSignal(6) apply only to MAUs of
10BASE-FB."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aMediaAvailable."
::= { ifMauEntry 5 }
ifMauMediaAvailableStateExits OBJECT-
SYNTAX
McMaster, McCloghrie & Roberts [Page 16]
RFC 1515 802.3 MAU MIB September 1993
ACCESS read-
STATUS
"A count of the number of times
ifMauMediaAvailable for this MAU instance
the state available(3)."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
lostMediaCount."
::= { ifMauEntry 6 }
ifMauJabberState OBJECT-
SYNTAX INTEGER {
other(1),
unknown(2),
noJabber(3),
jabbering(4)
}
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."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aJabber.jabberFlag."
::= { ifMauEntry 7 }
ifMauJabberingStateEnters OBJECT-
SYNTAX
ACCESS read-
STATUS
"A count of the number of times
ifMauJabberState for this MAU instance enters
state jabbering(4). For a MAU of
dot3MauTypeAUI, this counter will always
McMaster, McCloghrie & Roberts [Page 17]
RFC 1515 802.3 MAU MIB September 1993
zero."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aJabber.jabberCounter."
::= { ifMauEntry 8 }
--
-- The Broadband MAU Basic
--
-- Implementation of the Broadband MAU Basic Group is
-- for broadband MAUs attached to DTEs
--
-- The Basic Broadband MAU
--
broadMauBasicTable OBJECT-
SYNTAX SEQUENCE OF
ACCESS not-
STATUS
"Table of descriptive and status information
the broadband MAUs connected to interfaces."
::= { dot3BroadMauBasicGroup 1 }
broadMauBasicEntry OBJECT-
SYNTAX
ACCESS not-
STATUS
"An entry in the table, containing
about a single broadband MAU."
INDEX { broadMauIfIndex, broadMauIndex }
::= { broadMauBasicTable 1 }
BroadMauBasicEntry ::=
SEQUENCE {
INTEGER
INTEGER
INTEGER
INTEGER
McMaster, McCloghrie & Roberts [Page 18]
RFC 1515 802.3 MAU MIB September 1993
}
broadMauIfIndex OBJECT-
SYNTAX
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 INTEGER (1..9)
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)
}
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
system, offset normally zero."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBbMAUXmitRcvSplitType."
McMaster, McCloghrie & Roberts [Page 19]
RFC 1515 802.3 MAU MIB September 1993
::= { broadMauBasicEntry 3 }
broadMauXmtCarrierFreq OBJECT-
SYNTAX
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
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 }
-- Traps for use by 802.3
-- Traps are defined using the conventions in RFC 1215 [8].
rpMauJabberTrap TRAP-
ENTERPRISE snmpDot3
VARIABLES { rpMauJabberState }
"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."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.4,
nJabberNotification."
::= 1
McMaster, McCloghrie & Roberts [Page 20]
RFC 1515 802.3 MAU MIB September 1993
ifMauJabberTrap TRAP-
ENTERPRISE snmpDot3
VARIABLES { ifMauJabberState }
"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."
"Reference IEEE 802.3 MAU Mgt, 20.2.3.4,
nJabberNotification."
::= 2
5.
This document is the work of the IETF Hub MIB Working Group. It
based on a proposal written by Geoff Thompson and modified by
IEEE 802.3 Repeater Management Task Force. Paul Woodruff
valuable corrections and suggestions for improvement
Members of the IETF Hub MIB Working Group included
Karl Auerbach karl@eng.sun.
Jim Barnes barnes@xylogics.
Steve Bostock steveb@novell.
David Bridgham dab@asylum.sf.ca.
Jack Brown jbrown@huahuca-emh8.army.
Howard Brown brown@ctron.
Lida Canin lida@apple.
Jeffrey Case case@cs.utk.
Carson Cheung carson@bnr.com.
James Codespote jpcodes@tycho.ncsc.
John Cook cook@chipcom.
Dave Cullerot cullerot@ctron.
James Davin jrd@ptt.lcs.mit.
Gary Ellis garye@hpspd.spd.hp.
David Engel david@cds.
Mike Erlinger mike@mti.
Jeff
Bill Fardy fardy@ctron.
Jeff Fried jmf@relay.proteon.
Bob Friesenhahn pdrusa!bob@uunet.uu.
Shawn Gallagher gallagher@quiver.enet.dec.
McMaster, McCloghrie & Roberts [Page 21]
RFC 1515 802.3 MAU MIB September 1993
Mike Grieves mgrieves@chipcom.
Walter Guilarte 70026.1715@compuserve.
Phillip Hasse phasse@honchuca-emh8.army.
Mark Hoerth mark_hoerth@hp0400.desk.hp.
Greg Hollingsworth gregh@mailer.jhuapl.
Ron Jacoby rj@sgi.
Mike Janson mjanson@mot.
Ken Jones konkord!ksj@uunet.uu.
Satish Joshi sjoshi@synoptics.
Frank Kastenholz kasten@europa.clearpoint.
Manu Kaycee kaycee@trlian.enet.dec.
Mark Kepke mak@cnd.hp.
Mark Kerestes att!alux2!hawk@uunet.uu.
Kenneth Key key@cs.utk.
Yoav Kluger ykluger@fibhaifa.
Cheryl Krupczak cheryl@cc.gatech.
Ron Lau rlau@synoptics.
Chao-Yu Liang cliang@synoptics.
Dave Lindemulder da@mtung.att.
Richie McBride rm@bix.co.
Keith McCloghrie kzm@hls.
Evan McGinnis bem@3com.
Donna McMaster mcmaster@synoptics.
David Minnich dwm@fibercom.
Lynn Monsanto monsanto@sun.
Miriam Nihart miriam@decwet.zso.dec.
Niels Ole Brunsgaard nob@dowtyns.
Edison Paw esp@3com.
David Perkins dperkins@synoptics.
Jason Perreault perreaul@interlan.interlan.
John Pickens jrp@3com.
Jim Reinstedler jimr@sceng.ub.
Anil Rijsinghani anil@levers.enet.dec.
Sam Roberts sroberts@farallon.
Dan Romascanu dan@lannet.
Marshall Rose mrose@dbc.mtview.ca.
Rick Royston rick@lsumus.sncc.lsu.
Michael Sabo sabo@dockmaster.ncsc.
Jonathan Saperia saperia@tcpjon.enet.dec.
Mark Schaefer schaefer@davidsys.
Anil Singhal nsinghal@hawk.ulowell.
Timon Sloane peernet!timon@uunet.uu.
Bob Stewart rlstewart@eng.xyplex.
Emil Sturniolo emil@dss.
Bruce Taber taber@interlan.
Iris Tal 437-3580@mcimail.
Mark Therieau markt@python.eng.microcom.
Geoff Thompson thompson@synoptics.
McMaster, McCloghrie & Roberts [Page 22]
RFC 1515 802.3 MAU MIB September 1993
Dean Throop throop@dg-rtp.dg.
Steven Waldbusser waldbusser@andrew.cmu.
Timothy Walden tmwalden@saturn.sys.acc.
Philip Wang watadn!phil@uunet.uu.
Drew Wansley dwansley@secola.columbia.ncr.
David Ward dward@chipcom.
Steve Wong wong@took.enet.dec.
Paul Woodruff paul-woodruff@3com.
Brian Wyld brianw@spider.co.
June-Kang Yang natadm!yang@uunet.uu.
Henry Yip natadm!henry@uunet.uu.
John Ziegler ziegler@artel.
Joseph Zur zur@fibhaifa.
6.
[1] Rose, M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based internets", STD 16,
1155, Performance Systems International, Hughes LAN Systems,
1990.
[2] McCloghrie, K., and M. Rose, "Management Information Base
Network Management of TCP/IP-based internets", RFC 1156,
LAN Systems, Performance Systems International, May 1990.
[3] Case, J., Fedor M., Schoffstall, M., and J. Davin, "
Network Management Protocol", STD 15, RFC 1157, SNMP Research
Performance Systems International, Performance
International, MIT Laboratory for Computer Science, May 1990.
[4] McCloghrie, K., and M. Rose, Editors, "Management
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, Hughes LAN Systems, Performance
International, March 1991.
[5] Information processing systems - Open Systems Interconnection -
Specification of Abstract Syntax Notation One (ASN.1),
International Organization for Standardization,
Standard 8824, December 1987.
[6] Information processing systems - Open Systems Interconnection -
Specification of Basic Encoding Rules for Abstract Notation
(ASN.1), International Organization for Standardization
International Standard 8825, December 1987.
[7] Rose, M., and K. McCloghrie, Editors, "Concise MIB Definitions",
STD 16, RFC 1212, Performance Systems International, Hughes
Systems, March 1991.
McMaster, McCloghrie & Roberts [Page 23]
RFC 1515 802.3 MAU MIB September 1993
[8] Rose, M., Editor, "A Convention for Defining Traps for use
the SNMP", RFC 1215, Performance Systems International,
1991.
[9] IEEE 802.3/ISO 8802-3 Information processing systems -
area networks - Part 3: Carrier sense multiple access
collision detection (CSMA/CD) access method and physical
specifications, 2nd edition, September 21, 1990.
[10] IEEE P802.3p, "Layer Management for 10 Mb/s Medium Access
(MAUs), Section 20", Draft Supplement to ANSI/IEEE 802.3,
5, July 11, 1992.
[11] Kastenholz, F., "Definitions of Managed Objects for
Ethernet-like Interface Types", RFC 1398, FTP Software, Inc.,
January 1993.
[12] McMaster, D., and K. McCloghrie, Editors, "Definitions
Managed Objects for IEEE 802.3 Repeater Devices", RFC 1368,
SynOptics Communications, Hughes LAN Systems, October 1992.
7. Security
Security issues are not discussed in this memo
McMaster, McCloghrie & Roberts [Page 24]
RFC 1515 802.3 MAU MIB September 1993
8. Authors'
Donna
SynOptics Communications, Inc
4401 Great America
P.O. Box 58185
Santa Clara, CA 95052-8185
Phone: (408) 764-1206
EMail: mcmaster@synoptics.
Keith
Hughes LAN Systems, Inc
1225 Charleston
Mountain View, CA 94043
Phone: (415) 966-7934
EMail: kzm@hls.
Sam
Farallon Computing, Inc
2470 Mariner Square
Alameda, CA 94501-1010
Phone: (510) 814-5215
EMail: sroberts@farallon.
McMaster, McCloghrie & Roberts [Page 25]
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
