< draft-ietf-hubmib-mau-00.txt   draft-ietf-hubmib-mau-01.txt >
Internet Draft 802.3 MAU MIB 3 March 1993 Internet Draft 802.3 MAU MIB 22 March 1993
Definitions of Managed Objects Definitions of Managed Objects
for IEEE 802.3 Medium Attachment Units (MAUs) for IEEE 802.3 Medium Attachment Units (MAUs)
3 March 1993 22 March 1993
Donna McMaster Donna McMaster
SynOptics Communications, Inc. SynOptics Communications, Inc.
mcmaster@synoptics.com mcmaster@synoptics.com
Keith McCloghrie Keith McCloghrie
Hughes LAN Systems, Inc. Hughes LAN Systems, Inc.
kzm@hls.com kzm@hls.com
Sam Roberts Sam Roberts
skipping to change at line 29 skipping to change at line 29
sroberts@farallon.com sroberts@farallon.com
1. Abstract 1. Abstract
This document defines an experimental portion of the This document defines an experimental portion of the
Management Information Base (MIB) for use with network Management Information Base (MIB) for use with network
management protocols in TCP/IP-based internets. In management protocols in TCP/IP-based internets. In
particular, it defines objects for managing IEEE 802.3 Medium particular, it defines objects for managing IEEE 802.3 Medium
Attachment Units (MAUs). Attachment Units (MAUs).
2. Status of this Memo 2. Status of this Document
This document is an Internet Draft. Internet Drafts are This document is an Internet Draft. Internet Drafts are
working documents of the Internet Engineering Task Force working documents of the Internet Engineering Task Force
(IETF), its Areas, and its Working Groups. Note that other (IETF), its Areas, and its Working Groups. Note that other
groups may also distribute working documents as Internet groups may also distribute working documents as Internet
Drafts. Drafts.
[Page 1] Expires 3 September 1993 [Page 1] Expires 22 September 1993
Internet Drafts are draft documents valid for a maximum of six Internet Drafts are draft documents valid for a maximum of six
months. Internet Drafts may be updated, replaced, or months. Internet Drafts may be updated, replaced, or
obsoleted by other documents at any time. It is not obsoleted by other documents at any time. It is not
appropriate to use Internet Drafts as reference material or to appropriate to use Internet Drafts as reference material or to
cite them other than as a "working draft" or "work in cite them other than as a "working draft" or "work in
progress." progress."
Please check the I-D abstract listing contained in each Please check the I-D abstract listing contained in each
Internet Draft directory to learn the current status of this Internet Draft directory to learn the current status of this
or any other Internet Draft. or any other Internet Draft.
This document, when finalized, will be submitted to the RFC This document, when finalized, will be submitted to the RFC
editor as an extension to the SNMP MIB. Distribution of this editor as an extension to the SNMP MIB. Distribution of this
document is unlimited. Please send comments to Donna McMaster document is unlimited. Please send comments to Donna McMaster
(mcmaster@synoptics.com), Keith McCloghrie (kzm@hls.com), and (mcmaster@synoptics.com), Keith McCloghrie (kzm@hls.com), and
Sam Roberts (sroberts@farallon.com). Sam Roberts (sroberts@farallon.com).
[Page 2] Expires 3 September 1993 [Page 2] Expires 22 September 1993
3. Management Framework 3. Management Framework
The Internet-standard Network Management Framework consists of The Internet-standard Network Management Framework consists of
three components. They are: three components. They are:
STD 16/RFC 1155 [1] which defines the SMI, the mechanisms STD 16/RFC 1155 [1] which defines the SMI, the mechanisms
used for describing and naming objects for the purpose of used for describing and naming objects for the purpose of
management. STD 16/RFC 1212 [7] defines a more concise management. STD 16/RFC 1212 [7] defines a more concise
description mechanism, which is wholly consistent with description mechanism, which is wholly consistent with
the SMI. the SMI.
skipping to change at line 79 skipping to change at line 79
1213 [4] defines MIB-II, an evolution of MIB-I based on 1213 [4] defines MIB-II, an evolution of MIB-I based on
implementation experience and new operational implementation experience and new operational
requirements. requirements.
STD 15/RFC 1157 [3] which defines the SNMP, the protocol STD 15/RFC 1157 [3] which defines the SNMP, the protocol
used for network access to managed objects. used for network access to managed objects.
The Framework permits new objects to be defined for the The Framework permits new objects to be defined for the
purpose of experimentation and evaluation. purpose of experimentation and evaluation.
[Page 3] Expires 3 September 1993 [Page 3] Expires 22 September 1993
4. Objects 4. Objects
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. Objects in the termed the Management Information Base or MIB. Objects in the
MIB are defined using the subset of Abstract Syntax Notation MIB are defined using the subset of Abstract Syntax Notation
One (ASN.1) [5] defined in the SMI. In particular, each One (ASN.1) [5] defined in the SMI. In particular, each
object has a name, a syntax, and an encoding. The name is an object has a name, a syntax, and an encoding. The name is an
object identifier, an administratively assigned name, which object identifier, an administratively assigned name, which
specifies an object type. The object type together with an specifies an object type. The object type together with an
object instance serves to uniquely identify a specific object instance serves to uniquely identify a specific
skipping to change at line 117 skipping to change at line 117
[6], subject to the additional requirements imposed by the [6], subject to the additional requirements imposed by the
SNMP. SNMP.
4.1. Format of Definitions 4.1. Format of Definitions
Section 6 contains the specification of all object types Section 6 contains the specification of all object types
contained in this MIB module. The object types are defined contained in this MIB module. The object types are defined
using the conventions defined in the SMI, as amended by the using the conventions defined in the SMI, as amended by the
extensions specified in [9,10]. extensions specified in [9,10].
[Page 4] Expires 3 September 1993 [Page 4] Expires 22 September 1993
5. Overview 5. Overview
Instances of the object types defined in this document Instances of the object types defined in this document
represent attributes of an IEEE 802.3 MAU. Several types of represent attributes of an IEEE 802.3 MAU. Several types of
MAUs are defined in the IEEE 802.3/ISO 8802-3 CSMA/CD standard MAUs are defined in the IEEE 802.3/ISO 8802-3 CSMA/CD standard
[9]. [9].
These MAUs may be connected to IEEE 802.3 repeaters or to These MAUs may be connected to IEEE 802.3 repeaters or to
802.3 (Ethernet-like) interfaces. For convenience this 802.3 (Ethernet-like) interfaces. For convenience this
document refers to these devices as "repeater MAUs" and document refers to these devices as "repeater MAUs" and
skipping to change at line 150 skipping to change at line 150
5.2. Structure of MIB 5.2. Structure of MIB
Objects in this MIB are arranged into MIB groups. Each MIB Objects in this MIB are arranged into MIB groups. Each MIB
group is organized as a set of related objects. group is organized as a set of related objects.
5.2.1. The Repeater MAU Basic Group Definitions 5.2.1. The Repeater MAU Basic Group Definitions
This group contains all repeater MAU-related configuration, This group contains all repeater MAU-related configuration,
status, and control objects. Implementation of the status, and control objects. Implementation of the
rpMauBasicGroup is mandatory for MAUs attached to repeaters. dot3RpMauBasicGroup is mandatory for MAUs attached to
repeaters.
5.2.2. The Interface MAU Basic Group Definitions 5.2.2. The Interface MAU Basic Group Definitions
This group contains all interface MAU-related configuration, This group contains all interface MAU-related configuration,
status, and control objects. Implementation of the status, and control objects. Implementation of the
dot3IfMauBasicGroup is mandatory for MAUs attached to
[Page 5] Expires 3 September 1993 [Page 5] Expires 22 September 1993
ifMauBasicGroup is mandatory for MAUs attached to interfaces. interfaces.
5.2.3. The Broadband MAU Basic Group Definitions 5.2.3. The Broadband MAU Basic Group Definitions
This group contains all broadband-specific MAU-related This group contains all broadband-specific MAU-related
configuration objects. Implementation of the configuration objects. Implementation of the
broadMauBasicGroup is mandatory for 10BROAD36 MAUs, and is not dot3BroadMauBasicGroup is mandatory for 10BROAD36 MAUs, and is
appropriate for other types of MAUs. not appropriate for other types of MAUs.
5.3. Relationship to Other MIBs 5.3. Relationship to Other MIBs
It is assumed that an agent implementing this MIB will also It is assumed that an agent implementing this MIB will also
implement (at least) the 'system' group defined in MIB-II [4]. implement (at least) the 'system' group defined in MIB-II [4].
The following sections identify other MIBs that such an agent The following sections identify other MIBs that such an agent
should implement. should implement.
5.3.1. Relationship to the 'system' group 5.3.1. Relationship to the 'system' group
skipping to change at line 201 skipping to change at line 203
MAU is connected. MAU is connected.
It is expected that an agent implementing the interface-MAU It is expected that an agent implementing the interface-MAU
related objects in this MIB will also implement the Extensions related objects in this MIB will also implement the Extensions
to the Generic Interface MIB [11] and the Ethernet-like to the Generic Interface MIB [11] and the Ethernet-like
Interfaces MIB [12]. Interfaces MIB [12].
(Note that repeater ports are not represented as interfaces in (Note that repeater ports are not represented as interfaces in
the sense of MIB-II's 'interfaces' group. See section 3.4.2 the sense of MIB-II's 'interfaces' group. See section 3.4.2
[Page 6] Expires 3 September 1993 [Page 6] Expires 22 September 1993
of the repeater MIB [13] for more details.) of the repeater MIB [13] for more details.)
5.3.3. Relationship to the 802.3 Repeater MIB 5.3.3. Relationship to the 802.3 Repeater MIB
The section of this document that defines repeater MAU-related The section of this document that defines repeater MAU-related
objects specifies an extension to the 802.3 Repeater MIB objects specifies an extension to the 802.3 Repeater MIB
defined in [13]. An agent implementing these repeater-MAU defined in [13]. An agent implementing these repeater-MAU
related objects must also implement the 802.3 Repeater MIB. related objects must also implement the 802.3 Repeater MIB.
The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to
instantiate a repeater MAU variable shall be the same as the instantiate a repeater MAU variable shall be the same as the
values of 'rptrPortGroupIndex' and 'rptrPortIndex' used to values of 'rptrPortGroupIndex' and 'rptrPortIndex' used to
instantiate the port to which the given MAU is connected. instantiate the port to which the given MAU is connected.
[Page 7] Expires 3 September 1993 [Page 7] Expires 22 September 1993
6. Definitions 6. Definitions
SNMP-MAU-MIB DEFINITIONS ::= BEGIN SNMP-MAU-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
experimental, Counter FROM RFC1155-SMI experimental, Counter FROM RFC1155-SMI
OBJECT-TYPE FROM RFC-1212 OBJECT-TYPE FROM RFC-1212
TRAP-TYPE FROM RFC-1215; TRAP-TYPE FROM RFC-1215;
snmpDot3MauMgt OBJECT IDENTIFIER ::= { experimental 35 } snmpDot3MauMgt OBJECT IDENTIFIER ::= { experimental 35 }
skipping to change at line 252 skipping to change at line 254
-- Definitions of Managed Objects for IEEE 802.3 Repeater -- Definitions of Managed Objects for IEEE 802.3 Repeater
-- Devices, Internet Working Group Request for Comments -- Devices, Internet Working Group Request for Comments
-- 1368. Network Information Center, SRI International, -- 1368. Network Information Center, SRI International,
-- Menlo Park, California, (October, 1992). -- Menlo Park, California, (October, 1992).
-- --
-- [IEEE 802.3 MAU Mgt] -- [IEEE 802.3 MAU Mgt]
-- refers to IEEE P802.3p, 'Layer Management for 10 Mb/s -- refers to IEEE P802.3p, 'Layer Management for 10 Mb/s
-- Medium Access Unit (MAUs), Section 20,' Draft Supplement -- Medium Access Unit (MAUs), Section 20,' Draft Supplement
-- to ANSI/IEEE 802.3, (Draft 5, July 11, 1992). -- to ANSI/IEEE 802.3, (Draft 5, July 11, 1992).
[Page 8] Expires 3 September 1993 [Page 8] Expires 22 September 1993
-- MIB Groups -- MIB Groups
-- --
-- The rpMauBasicGroup is mandatory for MAUs attached to -- The dot3RpMauBasicGroup is mandatory for MAUs attached to
-- repeaters. -- repeaters.
-- The ifMauBasicGroup is mandatory for MAUs attached to -- The dot3IfMauBasicGroup is mandatory for MAUs attached to
-- DTEs (interfaces). -- DTEs (interfaces).
-- The broadMauBasicGroup is mandatory for broadband MAUs -- The dot3BroadMauBasicGroup is mandatory for broadband MAUs
-- attached to DTEs. -- attached to DTEs.
dot3RpMauBasicGroup dot3RpMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 }
dot3IfMauBasicGroup dot3IfMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 }
dot3BroadMauBasicGroup dot3BroadMauBasicGroup
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }
-- object identifiers for MAU types -- object identifiers for MAU types
skipping to change at line 294 skipping to change at line 296
OBJECT IDENTIFIER ::= { dot3MauType 6 } OBJECT IDENTIFIER ::= { dot3MauType 6 }
dot3MauType10BaseFB -- sync fiber MAU (per 802.3 section 17) dot3MauType10BaseFB -- sync fiber MAU (per 802.3 section 17)
OBJECT IDENTIFIER ::= { dot3MauType 7 } OBJECT IDENTIFIER ::= { dot3MauType 7 }
dot3MauType10BaseFL -- async fiber MAU (per 802.3 section 18) dot3MauType10BaseFL -- async fiber MAU (per 802.3 section 18)
OBJECT IDENTIFIER ::= { dot3MauType 8 } OBJECT IDENTIFIER ::= { dot3MauType 8 }
dot3MauType10Broad36 -- broadband DTE MAU (per 802.3 section 11) dot3MauType10Broad36 -- broadband DTE MAU (per 802.3 section 11)
-- note that 10BROAD36 MAUs can be attached to interfaces but -- note that 10BROAD36 MAUs can be attached to interfaces but
-- not to repeaters -- not to repeaters
OBJECT IDENTIFIER ::= { dot3MauType 9 } OBJECT IDENTIFIER ::= { dot3MauType 9 }
[Page 9] Expires 3 September 1993 [Page 9] Expires 22 September 1993
-- --
-- The Repeater MAU Basic Group -- The Repeater MAU Basic Group
-- --
-- Implementation of the Repeater MAU Basic Group is mandatory -- Implementation of the Repeater MAU Basic Group is mandatory
-- for MAUs attached to repeaters. -- for MAUs attached to repeaters.
-- --
-- The Basic Repeater MAU Table -- The Basic Repeater MAU Table
-- --
skipping to change at line 341 skipping to change at line 343
INTEGER, INTEGER,
rpMauType rpMauType
OBJECT IDENTIFIER, OBJECT IDENTIFIER,
rpMauStatus rpMauStatus
INTEGER, INTEGER,
rpMauMediaAvailable rpMauMediaAvailable
INTEGER, INTEGER,
rpMauMediaAvailableChanges rpMauMediaAvailableChanges
Counter, Counter,
[Page 10] Expires 3 September 1993 [Page 10] Expires 22 September 1993
rpMauJabberState rpMauJabberState
INTEGER, INTEGER,
rpMauJabberStateChanges rpMauJabberStateChanges
Counter Counter
} }
rpMauGroupIndex OBJECT-TYPE rpMauGroupIndex OBJECT-TYPE
SYNTAX INTEGER (1..1024) SYNTAX INTEGER (1..1024)
ACCESS read-only ACCESS read-only
STATUS mandatory STATUS mandatory
skipping to change at line 388 skipping to change at line 390
connected to port rpMauPortIndex within group connected to port rpMauPortIndex within group
rpMauGroupIndex that is described by this entry." rpMauGroupIndex that is described by this entry."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID." "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID."
::= { rpMauEntry 3 } ::= { rpMauEntry 3 }
rpMauType OBJECT-TYPE rpMauType OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
ACCESS read-only ACCESS read-only
[Page 11] Expires 3 September 1993 [Page 11] Expires 22 September 1993
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"This object identifies the 10 Mb/s baseband MAU "This object identifies the 10 Mb/s baseband MAU
type. An initial set of MAU types are defined type. An initial set of MAU types are defined
above. The assignment of OBJECT IDENTIFIERs to above. The assignment of OBJECT IDENTIFIERs to
new types of MAUs is managed by the IANA. If the new types of MAUs is managed by the IANA. If the
MAU type is unknown, the object identifier MAU type is unknown, the object identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
skipping to change at line 435 skipping to change at line 437
setting the value of this object to some of the setting the value of this object to some of the
enumerated values. enumerated values.
The value other(1) is returned if the MAU is in a The value other(1) is returned if the MAU is in a
state other than one of the states 2 through 6. state other than one of the states 2 through 6.
The value unknown(2) is returned when the MAU's The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is true state is unknown; for example, when it is
being initialized. being initialized.
[Page 12] Expires 3 September 1993 [Page 12] Expires 22 September 1993
A MAU in the operational(3) state is fully A MAU in the operational(3) state is fully
functional, operates, and passes signals to its functional, operates, and passes signals to its
attached DTE or repeater port in accordance to its attached DTE or repeater port in accordance to its
specification. specification.
A MAU in standby(4) state forces DI and CI and the A MAU in standby(4) state forces DI and CI and the
media transmitter to idle. Standby(4) mode only media transmitter to idle. Standby(4) mode only
applies to link type MAUs. The state of applies to link type MAUs. The state of
rpMauMediaAvailable is unaffected. rpMauMediaAvailable is unaffected.
skipping to change at line 482 skipping to change at line 484
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
available(3), available(3),
notAvailable(4), notAvailable(4),
remoteFault(5), remoteFault(5),
invalidSignal(6) invalidSignal(6)
} }
ACCESS read-only ACCESS read-only
[Page 13] Expires 3 September 1993 [Page 13] Expires 22 September 1993
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"If the MAU is a link or fiber type (FOIRL, "If the MAU is a link or fiber type (FOIRL,
10BASE-T, 10BASE-F) then this is equivalent to the 10BASE-T, 10BASE-F) then this is equivalent to the
link test fail state/low light function. For an link test fail state/low light function. For an
AUI or a coax (including broadband) MAU this AUI or a coax (including broadband) MAU this
indicates whether or not loopback is detected on indicates whether or not loopback is detected on
the DI circuit. The value of this attribute the DI circuit. The value of this attribute
persists between packets for MAU types AUI, persists between packets for MAU types AUI,
10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
skipping to change at line 528 skipping to change at line 530
The value invalidSignal(6) indicates that an The value invalidSignal(6) indicates that an
invalid signal has been received from the other invalid signal has been received from the other
end of the link. Both remoteFault(5) and end of the link. Both remoteFault(5) and
invalidSignal(6) apply only to MAUs of type invalidSignal(6) apply only to MAUs of type
10BASE-FB." 10BASE-FB."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aMediaAvailable." aMediaAvailable."
::= { rpMauEntry 6 } ::= { rpMauEntry 6 }
[Page 14] Expires 3 September 1993 [Page 14] Expires 22 September 1993
rpMauMediaAvailableChanges OBJECT-TYPE rpMauMediaAvailableChanges OBJECT-TYPE
SYNTAX Counter SYNTAX Counter
ACCESS read-only ACCESS read-only
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"A count of the number of times that "A count of the number of times that
rpMauMediaAvailable for this MAU instance leaves rpMauMediaAvailable for this MAU instance leaves
the state available(3)." the state available(3)."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
skipping to change at line 575 skipping to change at line 577
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aJabber.jabberFlag." aJabber.jabberFlag."
::= { rpMauEntry 8 } ::= { rpMauEntry 8 }
rpMauJabberStateChanges OBJECT-TYPE rpMauJabberStateChanges OBJECT-TYPE
SYNTAX Counter SYNTAX Counter
ACCESS read-only ACCESS read-only
STATUS mandatory STATUS mandatory
[Page 15] Expires 3 September 1993 [Page 15] Expires 22 September 1993
DESCRIPTION DESCRIPTION
"A count of the number of times that "A count of the number of times that
rpMauJabberState for this MAU instance enters the rpMauJabberState for this MAU instance enters the
state jabbering(4). For a MAU of type state jabbering(4). For a MAU of type
dot3MauTypeAUI, this counter will always indicate dot3MauTypeAUI, this counter will always indicate
zero." zero."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aJabber.jabberCounter." aJabber.jabberCounter."
::= { rpMauEntry 9 } ::= { rpMauEntry 9 }
[Page 16] Expires 3 September 1993 [Page 16] Expires 22 September 1993
-- --
-- The Interface MAU Basic Group -- The Interface MAU Basic Group
-- --
-- Implementation of the Interface MAU Basic Group is mandatory -- Implementation of the Interface MAU Basic Group is mandatory
-- for MAUs attached to DTEs (interfaces). -- for MAUs attached to DTEs (interfaces).
-- --
-- The Basic Interface MAU Table -- The Basic Interface MAU Table
-- --
skipping to change at line 634 skipping to change at line 636
OBJECT IDENTIFIER, OBJECT IDENTIFIER,
ifMauStatus ifMauStatus
INTEGER, INTEGER,
ifMauMediaAvailable ifMauMediaAvailable
INTEGER, INTEGER,
ifMauMediaAvailableChanges ifMauMediaAvailableChanges
Counter, Counter,
ifMauJabberState ifMauJabberState
INTEGER, INTEGER,
[Page 17] Expires 3 September 1993 [Page 17] Expires 22 September 1993
ifMauJabberStateChanges ifMauJabberStateChanges
Counter Counter
} }
ifMauIfIndex OBJECT-TYPE ifMauIfIndex OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
ACCESS read-only ACCESS read-only
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"This variable uniquely identifies the interface "This variable uniquely identifies the interface
skipping to change at line 681 skipping to change at line 683
IDENTIFIERs to new types of MAUs is managed by the IDENTIFIERs to new types of MAUs is managed by the
IANA. If the MAU type is unknown, the object IANA. If the MAU type is unknown, the object
identifier identifier
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } unknownMauType OBJECT IDENTIFIER ::= { 0 0 }
is returned. Note that unknownMauType is a is returned. Note that unknownMauType is a
syntactically valid object identifier, and any syntactically valid object identifier, and any
conformant implementation of ASN.1 and the BER conformant implementation of ASN.1 and the BER
[Page 18] Expires 3 September 1993 [Page 18] Expires 22 September 1993
must be able to generate and recognize this must be able to generate and recognize this
value." value."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aMAUType." aMAUType."
::= { ifMauEntry 3 } ::= { ifMauEntry 3 }
ifMauStatus OBJECT-TYPE ifMauStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
skipping to change at line 728 skipping to change at line 730
specification. specification.
A MAU in standby(4) state forces DI and CI and the A MAU in standby(4) state forces DI and CI and the
media transmitter to idle. Standby(4) mode only media transmitter to idle. Standby(4) mode only
applies to link type MAUs. The state of applies to link type MAUs. The state of
ifMauMediaAvailable is unaffected. ifMauMediaAvailable is unaffected.
A MAU in shutdown(5) state assumes the same A MAU in shutdown(5) state assumes the same
condition on DI, CI, and the media transmitter as condition on DI, CI, and the media transmitter as
[Page 19] Expires 3 September 1993 [Page 19] Expires 22 September 1993
though it were powered down. The MAU may return though it were powered down. The MAU may return
other(1) value for the mauJabber and other(1) value for the mauJabber and
ifMauMediaAvailable objects when it is in this ifMauMediaAvailable objects when it is in this
state. For an AUI, this state will remove power state. For an AUI, this state will remove power
from the AUI. from the AUI.
Setting this variable to the value reset(6) resets Setting this variable to the value reset(6) resets
the MAU in the same manner as a power-off, power- the MAU in the same manner as a power-off, power-
on cycle of at least one-half second would. The on cycle of at least one-half second would. The
agent is not required to return the value reset agent is not required to return the value reset
skipping to change at line 775 skipping to change at line 777
10BASE-T, 10BASE-F) then this is equivalent to the 10BASE-T, 10BASE-F) then this is equivalent to the
link test fail state/low light function. For an link test fail state/low light function. For an
AUI or a coax (including broadband) MAU this AUI or a coax (including broadband) MAU this
indicates whether or not loopback is detected on indicates whether or not loopback is detected on
the DI circuit. The value of this attribute the DI circuit. The value of this attribute
persists between packets for MAU types AUI, persists between packets for MAU types AUI,
10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP.
The value other(1) is returned if the The value other(1) is returned if the
[Page 20] Expires 3 September 1993 [Page 20] Expires 22 September 1993
mediaAvailable state is not one of 2 through 6. mediaAvailable state is not one of 2 through 6.
The value unknown(2) is returned when the MAU's The value unknown(2) is returned when the MAU's
true state is unknown; for example, when it is true state is unknown; for example, when it is
being initialized. At power-up or following a being initialized. At power-up or following a
reset, the value of this attribute will be unknown reset, the value of this attribute will be unknown
for AUI, coax, and 10BASE-FP MAUs. For these MAUs for AUI, coax, and 10BASE-FP MAUs. For these MAUs
loopback will be tested on each transmission loopback will be tested on each transmission
during which no collision is detected. If DI is during which no collision is detected. If DI is
receiving input when DO returns to IDL after a receiving input when DO returns to IDL after a
skipping to change at line 822 skipping to change at line 824
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"A count of the number of times that "A count of the number of times that
ifMauMediaAvailable for this MAU instance leaves ifMauMediaAvailable for this MAU instance leaves
the state available(3)." the state available(3)."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
lostMediaCount." lostMediaCount."
::= { ifMauEntry 6 } ::= { ifMauEntry 6 }
[Page 21] Expires 3 September 1993 [Page 21] Expires 22 September 1993
ifMauJabberState OBJECT-TYPE ifMauJabberState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
other(1), other(1),
unknown(2), unknown(2),
noJabber(3), noJabber(3),
jabbering(4) jabbering(4)
} }
ACCESS read-only ACCESS read-only
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
skipping to change at line 866 skipping to change at line 868
"A count of the number of times that "A count of the number of times that
ifMauJabberState for this MAU instance enters the ifMauJabberState for this MAU instance enters the
state jabbering(4). For a MAU of type state jabbering(4). For a MAU of type
dot3MauTypeAUI, this counter will always indicate dot3MauTypeAUI, this counter will always indicate
zero." zero."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aJabber.jabberCounter." aJabber.jabberCounter."
::= { ifMauEntry 8 } ::= { ifMauEntry 8 }
[Page 22] Expires 3 September 1993 [Page 22] Expires 22 September 1993
-- --
-- The Broadband MAU Basic Group -- The Broadband MAU Basic Group
-- --
-- Implementation of the Broadband MAU Basic Group is mandatory -- Implementation of the Broadband MAU Basic Group is mandatory
-- for broadband MAUs attached to DTEs. -- for broadband MAUs attached to DTEs.
-- --
-- The Basic Broadband MAU Table -- The Basic Broadband MAU Table
-- --
skipping to change at line 913 skipping to change at line 915
INTEGER, INTEGER,
broadMauXmtCarrierFreq broadMauXmtCarrierFreq
INTEGER, INTEGER,
broadMauTranslationFreq broadMauTranslationFreq
INTEGER INTEGER
} }
broadMauIfIndex OBJECT-TYPE broadMauIfIndex OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
[Page 23] Expires 3 September 1993 [Page 23] Expires 22 September 1993
ACCESS read-only ACCESS read-only
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"This variable uniquely identifies the interface "This variable uniquely identifies the interface
to which the MAU described by this entry is to which the MAU described by this entry is
connected." connected."
REFERENCE REFERENCE
"Reference RFC 1213, ifIndex." "Reference RFC 1213, ifIndex."
::= { broadMauBasicEntry 1 } ::= { broadMauBasicEntry 1 }
skipping to change at line 960 skipping to change at line 962
is not either single or dual. is not either single or dual.
The value single(2) indicates a single cable The value single(2) indicates a single cable
system. The value dual(3) indicates a dual cable system. The value dual(3) indicates a dual cable
system, offset normally zero." system, offset normally zero."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBbMAUXmitRcvSplitType." aBbMAUXmitRcvSplitType."
::= { broadMauBasicEntry 3 } ::= { broadMauBasicEntry 3 }
[Page 24] Expires 3 September 1993 [Page 24] Expires 22 September 1993
broadMauXmtCarrierFreq OBJECT-TYPE broadMauXmtCarrierFreq OBJECT-TYPE
SYNTAX INTEGER SYNTAX INTEGER
ACCESS read-only ACCESS read-only
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"This variable indicates the transmit carrier "This variable indicates the transmit carrier
frequency of the 10BROAD36 MAU in MHz/4; that is, frequency of the 10BROAD36 MAU in MHz/4; that is,
in units of 250 kHz." in units of 250 kHz."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
skipping to change at line 987 skipping to change at line 989
STATUS mandatory STATUS mandatory
DESCRIPTION DESCRIPTION
"This variable indicates the translation offset "This variable indicates the translation offset
frequency of the 10BROAD36 MAU in MHz/4; that is, frequency of the 10BROAD36 MAU in MHz/4; that is,
in units of 250 kHz." in units of 250 kHz."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, "Reference IEEE 802.3 MAU Mgt, 20.2.3.2,
aBroadbandFrequencies.translationFrequency." aBroadbandFrequencies.translationFrequency."
::= { broadMauBasicEntry 5 } ::= { broadMauBasicEntry 5 }
[Page 25] Expires 3 September 1993 [Page 25] Expires 22 September 1993
-- Traps for use by 802.3 MAUs -- Traps for use by 802.3 MAUs
-- Traps are defined using the conventions in RFC 1215 [8]. -- Traps are defined using the conventions in RFC 1215 [8].
rpMauJabberTrap TRAP-TYPE rpMauJabberTrap TRAP-TYPE
ENTERPRISE snmpDot3MauMgt ENTERPRISE snmpDot3MauMgt
VARIABLES { rpMauJabberState } VARIABLES { rpMauJabberState }
DESCRIPTION DESCRIPTION
"This trap is sent whenever a managed repeater MAU "This trap is sent whenever a managed repeater MAU
enters the jabber state. enters the jabber state.
skipping to change at line 1024 skipping to change at line 1026
The agent must throttle the generation of The agent must throttle the generation of
consecutive ifMauJabberTraps so that there is at consecutive ifMauJabberTraps so that there is at
least a five-second gap between them." least a five-second gap between them."
REFERENCE REFERENCE
"Reference IEEE 802.3 MAU Mgt, 20.2.3.4, "Reference IEEE 802.3 MAU Mgt, 20.2.3.4,
nJabberNotification." nJabberNotification."
::= 2 ::= 2
END END
[Page 26] Expires 3 September 1993 [Page 26] Expires 22 September 1993
7. Acknowledgments 7. Acknowledgments
This document is the work of the IETF Hub MIB Working Group. This document is the work of the IETF Hub MIB Working Group.
It is based on a proposal written by Geoff Thompson and It is based on a proposal written by Geoff Thompson and
modified by the IEEE 802.3 Repeater Management Task Force. modified by the IEEE 802.3 Repeater Management Task Force.
Paul Woodruff provided valuable corrections and suggestions Paul Woodruff provided valuable corrections and suggestions
for improvement. for improvement.
Members of the IETF Hub MIB Working Group included: Members of the IETF Hub MIB Working Group included:
skipping to change at line 1071 skipping to change at line 1073
Ron Jacoby rj@sgi.com Ron Jacoby rj@sgi.com
Mike Janson mjanson@mot.com Mike Janson mjanson@mot.com
Ken Jones konkord!ksj@uunet.uu.net Ken Jones konkord!ksj@uunet.uu.net
Satish Joshi sjoshi@synoptics.com Satish Joshi sjoshi@synoptics.com
Frank Kastenholz kasten@europa.clearpoint.com Frank Kastenholz kasten@europa.clearpoint.com
Manu Kaycee kaycee@trlian.enet.dec.com Manu Kaycee kaycee@trlian.enet.dec.com
Mark Kepke mak@cnd.hp.com Mark Kepke mak@cnd.hp.com
Mark Kerestes att!alux2!hawk@uunet.uu.net Mark Kerestes att!alux2!hawk@uunet.uu.net
Kenneth Key key@cs.utk.edu Kenneth Key key@cs.utk.edu
[Page 27] Expires 3 September 1993 [Page 27] Expires 22 September 1993
Yoav Kluger ykluger@fibhaifa.com Yoav Kluger ykluger@fibhaifa.com
Cheryl Krupczak cheryl@cc.gatech.edu Cheryl Krupczak cheryl@cc.gatech.edu
Ron Lau rlau@synoptics.com Ron Lau rlau@synoptics.com
Chao-Yu Liang cliang@synoptics.com Chao-Yu Liang cliang@synoptics.com
Dave Lindemulder da@mtung.att.com Dave Lindemulder da@mtung.att.com
Richie McBride rm@bix.co.uk Richie McBride rm@bix.co.uk
Keith McCloghrie kzm@hls.com Keith McCloghrie kzm@hls.com
Evan McGinnis bem@3com.com Evan McGinnis bem@3com.com
Donna McMaster mcmaster@synoptics.com Donna McMaster mcmaster@synoptics.com
David Minnich dwm@fibercom.com David Minnich dwm@fibercom.com
skipping to change at line 1118 skipping to change at line 1120
Timothy Walden tmwalden@saturn.sys.acc.com Timothy Walden tmwalden@saturn.sys.acc.com
Philip Wang watadn!phil@uunet.uu.net Philip Wang watadn!phil@uunet.uu.net
Drew Wansley dwansley@secola.columbia.ncr.com Drew Wansley dwansley@secola.columbia.ncr.com
David Ward dward@chipcom.com David Ward dward@chipcom.com
Steve Wong wong@took.enet.dec.com Steve Wong wong@took.enet.dec.com
Paul Woodruff paul-woodruff@3com.com Paul Woodruff paul-woodruff@3com.com
Brian Wyld brianw@spider.co.uk Brian Wyld brianw@spider.co.uk
June-Kang Yang natadm!yang@uunet.uu.net June-Kang Yang natadm!yang@uunet.uu.net
Henry Yip natadm!henry@uunet.uu.net Henry Yip natadm!henry@uunet.uu.net
[Page 28] Expires 3 September 1993 [Page 28] Expires 22 September 1993
John Ziegler ziegler@artel.com John Ziegler ziegler@artel.com
Joseph Zur fibronics!zur@uunet.uu.net Joseph Zur zur@fibhaifa.com
[Page 29] Expires 3 September 1993 [Page 29] Expires 22 September 1993
8. References 8. References
[1] Rose, M., and K. McCloghrie, "Structure and [1] Rose, M., and K. McCloghrie, "Structure and
Identification of Management Information for TCP/IP-based Identification of Management Information for TCP/IP-based
internets", STD 16, RFC 1155, Performance Systems internets", STD 16, RFC 1155, Performance Systems
International, Hughes LAN Systems, May 1990. International, Hughes LAN Systems, May 1990.
[2] McCloghrie, K., and M. Rose, "Management Information Base [2] McCloghrie, K., and M. Rose, "Management Information Base
for Network Management of TCP/IP-based internets", RFC for Network Management of TCP/IP-based internets", RFC
1156, Hughes LAN Systems, Performance Systems 1156, Hughes LAN Systems, Performance Systems
skipping to change at line 1169 skipping to change at line 1171
Definitions", STD 16, RFC 1212, Performance Systems Definitions", STD 16, RFC 1212, Performance Systems
International, Hughes LAN Systems, March 1991. International, Hughes LAN Systems, March 1991.
[8] Rose, M., Editor, "A Convention for Defining Traps for [8] Rose, M., Editor, "A Convention for Defining Traps for
use with the SNMP", RFC 1215, Performance Systems use with the SNMP", RFC 1215, Performance Systems
International, March 1991. International, March 1991.
[9] IEEE 802.3/ISO 8802-3 Information processing systems - [9] IEEE 802.3/ISO 8802-3 Information processing systems -
Local area networks - Part 3: Carrier sense multiple Local area networks - Part 3: Carrier sense multiple
[Page 30] Expires 3 September 1993 [Page 30] Expires 22 September 1993
access with collision detection (CSMA/CD) access method access with collision detection (CSMA/CD) access method
and physical layer specifications, 2nd edition, September and physical layer specifications, 2nd edition, September
21, 1990. 21, 1990.
[10] IEEE P802.3p, "Layer Management for 10 Mb/s Medium Access [10] IEEE P802.3p, "Layer Management for 10 Mb/s Medium Access
Unit (MAUs), Section 20", Draft Supplement to ANSI/IEEE Unit (MAUs), Section 20", Draft Supplement to ANSI/IEEE
802.3, Draft 5, July 11, 1992. 802.3, Draft 5, July 11, 1992.
[11] McCloghrie, K., Editor, "Extensions to the Generic- [11] McCloghrie, K., Editor, "Extensions to the Generic-
Interface MIB", RFC 1229, Hughes LAN Systems, May 1991, Interface MIB", RFC 1229, Hughes LAN Systems, May 1991,
skipping to change at line 1193 skipping to change at line 1195
[12] Kastenholz, F., "Definitions of Managed Objects for the [12] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 1398, FTP Software, Ethernet-like Interface Types", RFC 1398, FTP Software,
Inc., January 1993. Inc., January 1993.
[13] McMaster, D., and K. McCloghrie, Editors, "Definitions of [13] McMaster, D., and K. McCloghrie, Editors, "Definitions of
Managed Objects for IEEE 802.3 Repeater Devices", RFC Managed Objects for IEEE 802.3 Repeater Devices", RFC
1368, SynOptics Communications, Hughes LAN Systems, 1368, SynOptics Communications, Hughes LAN Systems,
October 1992. October 1992.
[Page 31] Expires 3 September 1993 [Page 31] Expires 22 September 1993
Table of Contents Table of Contents
1 Abstract .............................................. 1 1 Abstract .............................................. 1
2 Status of this Memo ................................... 1 2 Status of this Document ............................... 1
3 Management Framework .................................. 3 3 Management Framework .................................. 3
4 Objects ............................................... 4 4 Objects ............................................... 4
4.1 Format of Definitions ............................... 4 4.1 Format of Definitions ............................... 4
5 Overview .............................................. 5 5 Overview .............................................. 5
5.1 Terminology ......................................... 5 5.1 Terminology ......................................... 5
5.2 Structure of MIB .................................... 5 5.2 Structure of MIB .................................... 5
5.2.1 The Repeater MAU Basic Group Definitions .......... 5 5.2.1 The Repeater MAU Basic Group Definitions .......... 5
5.2.2 The Interface MAU Basic Group Definitions ......... 5 5.2.2 The Interface MAU Basic Group Definitions ......... 5
5.2.3 The Broadband MAU Basic Group Definitions ......... 6 5.2.3 The Broadband MAU Basic Group Definitions ......... 6
5.3 Relationship to Other MIBs .......................... 6 5.3 Relationship to Other MIBs .......................... 6
skipping to change at line 1220 skipping to change at line 1222
5.3.3 Relationship to the 802.3 Repeater MIB ............ 7 5.3.3 Relationship to the 802.3 Repeater MIB ............ 7
6 Definitions ........................................... 8 6 Definitions ........................................... 8
6.1 Groups in the Repeater MAU MIB ...................... 9 6.1 Groups in the Repeater MAU MIB ...................... 9
6.1.1 The Repeater MAU Basic Group Definitions .......... 10 6.1.1 The Repeater MAU Basic Group Definitions .......... 10
6.1.2 The Interface MAU Basic Group Definitions ......... 17 6.1.2 The Interface MAU Basic Group Definitions ......... 17
6.1.3 The Broadband MAU Basic Group Definitions ......... 23 6.1.3 The Broadband MAU Basic Group Definitions ......... 23
6.2 Traps for use by 802.3 MAUs ......................... 26 6.2 Traps for use by 802.3 MAUs ......................... 26
7 Acknowledgments ....................................... 27 7 Acknowledgments ....................................... 27
8 References ............................................ 30 8 References ............................................ 30
[Page 32] Expires 3 September 1993 [Page 32] Expires 22 September 1993
 End of changes. 43 change blocks. 
43 lines changed or deleted 45 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/