--- 1/draft-ietf-hubmib-mau-mib-01.txt 2006-02-04 23:26:13.000000000 +0100 +++ 2/draft-ietf-hubmib-mau-mib-02.txt 2006-02-04 23:26:13.000000000 +0100 @@ -1,20 +1,20 @@ Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) - 14 February 1996 + 31 May 1996 - + Dan Romascanu Madge Networks (Israel) Ltd. - dan@lannet.com + dromasca@madge.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 @@ -24,190 +24,222 @@ 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), + +, 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: + The SNMPv2 Network Management Framework presently consists of + three major components. They are: - o RFC 1902 which defines the SMI, the mechanisms used for - describing and naming objects for the purpose of + o the SMI, described in RFC 1902 [6] - 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 the MIB-II, STD 17, RFC 1213 [5] - 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. + o the protocol, RFC 1157 [10] and/or RFC 1905 [9] - the + protocol used for accessing managed information. + + Textual conventions are defined in RFC 1903 [7], and + conformance statements are defined in RFC 1904 [8]. 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 of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. +, 2. Overview + 2.1. Relationship to RFC 1515 + + This MIB is intended to be a superset of that defined by RFC + 1515 [11], which will go to historic status. This MIB + includes all of the objects contained in that MIB, plus + several new ones which provide additional capabilities. + Implementors are encouraged to support all applicable + conformance groups in order to make the best use of the new + functionality provided by this MIB. The new objects provide + management support for: + + o management of 100 Mb/s devices + + o auto-negotiation + + o jack management + + 2.2. MAU Management + 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 + 2.3. 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. + implement (at least) the 'system' group defined in MIB-II [5]. The following sections identify other MIBs that such an agent + +, should implement. - 2.1.1. Relationship to the 'interfaces' group + 2.3.1. Relationship to the MIB-II '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 + The value of the object ifMauIfIndex 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.) - 2.1.2. Relationship to the 802.3 Repeater MIB + + 2.3.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 + 2.4. 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 -- + attributes should appear in the appropriate MIB subtree: + +, dot3RpMauBasicGroup for internal repeater-MAUs and dot3IfMauBasicGroup for internal interface-MAUs. +, 3. Definitions MAU-MIB DEFINITIONS ::= BEGIN IMPORTS - experimental, Counter32, Integer32, - OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE + OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 FROM SNMPv2-SMI OBJECT-GROUP, MODULE-COMPLIANCE - FROM SNMPv2-CONF - mib-2 - FROM RFC1213-MIB; + FROM SNMPv2-CONF; mauMod MODULE-IDENTITY - LAST-UPDATED "9602140000Z" + LAST-UPDATED "9605310000Z" 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 + E-mail: dromasca@madge.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 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 } + snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } 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) @@ -224,33 +256,68 @@ 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 but + +, -- not to repeaters OBJECT IDENTIFIER ::= { dot3MauType 9 } - -- new for 100 MB/s: + ------ new since RFC 1515: - dot3MauType100BaseT4 -- 4 pair categ. 3 UTP (per 802.3 section 23) + dot3MauType10BaseTHD -- UTP MAU (per 802.3 section 14) + -- half duplex mode OBJECT IDENTIFIER ::= { dot3MauType 10 } - dot3MauType100BaseTX -- 2 pair categ. 5 UTP (per 802.3 section 25) + + dot3MauType10BaseTFD -- UTP MAU (per 802.3 section 14) + -- full duplex mode OBJECT IDENTIFIER ::= { dot3MauType 11 } - dot3MauType100BaseFX -- X fiber over PMT (per 802.3 section 26) + + dot3MauType10BaseFLHD -- async fiber MAU (per 802.3 section 18) + -- half duplex mode OBJECT IDENTIFIER ::= { dot3MauType 12 } + dot3MauType10BaseFLFD -- async fiber MAU (per 802.3 section 18) + -- full duplex mode + OBJECT IDENTIFIER ::= { dot3MauType 13 } + + dot3MauType100BaseT4 -- 4 pair categ. 3 UTP (per 802.3 section 23) + OBJECT IDENTIFIER ::= { dot3MauType 14 } + + dot3MauType100BaseTXHD -- 2 pair categ. 5 UTP (per 802.3 section 25), + -- half duplex mode + OBJECT IDENTIFIER ::= { dot3MauType 15 } + + dot3MauType100BaseTXFD -- 2 pair categ. 5 UTP (per 802.3 section 25), + -- full duplex mode + OBJECT IDENTIFIER ::= { dot3MauType 16 } + + dot3MauType100BaseFXHD -- X fiber over PMT (per 802.3 section 26) + -- half duplex mode + OBJECT IDENTIFIER ::= { dot3MauType 17 } + + dot3MauType100BaseFXFD -- X fiber over PMT (per 802.3 section 26) + -- full duplex mode + OBJECT IDENTIFIER ::= { dot3MauType 18 } + + dot3MauType100BaseT2 + OBJECT IDENTIFIER ::= { dot3MauType 19 } + -- + +, -- 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." @@ -283,20 +350,21 @@ 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 @@ -321,27 +389,29 @@ 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." + described by this entry from among other MAUs + connected to the same port (rpMauPortIndex)." 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 @@ -373,20 +443,22 @@ 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 @@ -418,20 +490,22 @@ 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, @@ -457,34 +531,36 @@ 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 + 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. + 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. @@ -508,20 +584,22 @@ "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. @@ -553,20 +631,22 @@ 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 @@ -591,114 +671,73 @@ 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, + INDEX { rpMauGroupIndex, + rpMauPortIndex, + rpMauIndex, 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 - 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 + MAX-ACCESS not-accessible 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 } + described by this entry from among other jacks + attached to the same MAU (rpMauIndex)." + ::= { rpJackEntry 1 } rpJackType OBJECT-TYPE SYNTAX INTEGER { other(1), - rj45(2) + rj45(2), + rj45S(3), -- rj45 shielded + db9(4), + bnc(5), + fAUI(6), -- female aui + mAUI(7), -- male aui + fiberSC(8), + fiberMIC(9), + fiberST(10), + telco(11) } MAX-ACCESS read-only STATUS current DESCRIPTION "The jack connector type, as it appears on the outside of the system." - ::= { rpJackEntry 5 } + ::= { rpJackEntry 2 } -- -- 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 @@ -730,60 +769,71 @@ 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." + described by this entry from among other MAUs + connected to the same interface (ifMauIfIndex)." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." ::= { ifMauEntry 2 } ifMauType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER - MAX-ACCESS read-only + MAX-ACCESS read-write 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." + must be able to generate and recognize this value. + + If auto-negotiation is not enabled or is not + implemented for this MAU, a set to this object + will force the MAU into the new operating mode. + If auto-negotiation is present and enabled on this + MAU, a set to this object has no effect, and the + +, + value of this object reflects the result of the + auto-negotiation function." 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), @@ -813,20 +863,22 @@ 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 @@ -858,20 +910,22 @@ 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 @@ -881,42 +935,44 @@ 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 + 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. + 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)." @@ -948,20 +1004,22 @@ 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 @@ -993,58 +1051,70 @@ 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)). + 10Base-T (full duplex) and 100BASE-TX (full + duplex) would have a value of ((2**11) + (2**16)) + or 67584. The powers of 2 assigned to the capabilities are these: Power Capability + 0 other or unknown 1 AUI 2 10BASE-5 3 FOIRL 4 10BASE-2 - 5 10BASE-T + 5 10BASE-T duplex mode unknown 6 10BASE-FP 7 10BASE-FB - 8 10BASE-FL + 8 10BASE-FL duplex mode unknown 9 10BROAD36 - 10 100BASE-T4 - 11 100BASE-TX - 12 100BASE-FX - If auto-negotiation is present on the jack to - which this MAU is attached, this attribute will - map to the ifMauAutoNegCapability." + 10 10BASE-T half duplex mode + 11 10BASE-T full duplex mode + 12 10BASE-FL half duplex mode + 13 10BASE-FL full duplex mode + 14 100BASE-T4 + 15 100BASE-TX half duplex mode + 16 100BASE-TX full duplex mode + 17 100BASE-FX half duplex mode + 18 100BASE-FX full duplex mode + 19 100BASE-T2 + +, + If auto-negotiation is present on this MAU, this + object will map to 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 @@ -1052,129 +1122,114 @@ 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, + INDEX { ifMauIfIndex, + ifMauIndex, ifJackIndex } ::= { ifJackTable 1 } IfJackEntry ::= SEQUENCE { - ifJackIfIndex - Integer32, - ifJackMauIndex - Integer32, ifJackIndex Integer32, ifJackType INTEGER } - ifJackIfIndex OBJECT-TYPE - SYNTAX Integer32 - 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 + MAX-ACCESS not-accessible 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 } + described by this entry from among other jacks + +, + attached to the same MAU." + ::= { ifJackEntry 1 } ifJackType OBJECT-TYPE SYNTAX INTEGER { other(1), - rj45(2) + rj45(2), + rj45S(3), -- rj45 shielded + db9(4), + bnc(5), + fAUI(6), -- female aui + mAUI(7), -- male aui + fiberSC(8), + fiberMIC(9), + fiberST(10), + telco(11) } MAX-ACCESS read-only STATUS current DESCRIPTION "The jack connector type, as it appears on the outside of the system." - ::= { ifJackEntry 4 } + ::= { ifJackEntry 2 } + -- The ifMauAutoNegTable applies to systems in which -- auto-negotiation is supported on one or more MAUs - -- attached to interfaces. + -- attached to interfaces. Note that if auto-negotiation + -- is present and enabled, the ifMauType object reflects + -- the result of the auto-negotiation function. 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 } + INDEX { ifMauIfIndex, ifMauIndex } ::= { ifMauAutoNegTable 1 } IfMauAutoNegEntry ::= SEQUENCE { ifMauAutoNegAdminStatus INTEGER, ifMauAutoNegRemoteSignaling INTEGER, ifMauAutoNegConfig INTEGER, ifMauAutoNegCapability Integer32, ifMauAutoNegCapAdvertised Integer32, ifMauAutoNegCapReceived Integer32, - ifMauAutoNegTechnologyInUse - INTEGER, ifMauAutoNegRestart INTEGER } + 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 @@ -1171,29 +1226,30 @@ 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. + ability to be enabled. - 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.]" + If the value of this object is disabled(2) 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 state indicated by a write to the + object ifMauType." + +, 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) } @@ -1225,73 +1281,69 @@ 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)). + has the capability to support only 100Base-TX half + duplex would have a value of 32768 (2**15). In + contrast, an interface which supports both + 100Base-TX half duplex and and 100Base-TX full + duplex would have a value of 98304 ((2**15) + + (2**16)). 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 - 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. + 0 other or unknown + (1-9) (reserved) + 10 10BASE-T half duplex mode + 11 10BASE-T full duplex mode + 12 (reserved) + 13 (reserved) + 14 100BASE-T4 + 15 100BASE-TX half duplex mode + 16 100BASE-TX full duplex mode 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." @@ -1309,68 +1361,41 @@ 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 { 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 } + ::= { ifMauAutoNegEntry 8 } 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 } @@ -1396,20 +1421,22 @@ 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 @@ -1441,20 +1468,22 @@ 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 } @@ -1484,20 +1513,22 @@ 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 @@ -1528,152 +1559,247 @@ 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 } +, + mauRpGrp100Mbs OBJECT-GROUP + OBJECTS { rpMauFalseCarriers } STATUS current DESCRIPTION "Conformance group for MAUs attached to - repeater ports with extended management - (including 100 Mb/s and jack management)." + repeater ports with 100 Mb/s capability." ::= { mauModObjGrps 2 } + mauRpGrpJack OBJECT-GROUP + OBJECTS { rpJackType } + STATUS current + DESCRIPTION + "Conformance group for MAUs attached to + repeater ports with managed jacks." + ::= { mauModObjGrps 3 } + 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 } - mauIfGrpExtended OBJECT-GROUP + ::= { mauModObjGrps 4 } + + mauIfGrp100Mbs OBJECT-GROUP OBJECTS { ifMauFalseCarriers, - ifMauTypeList, + ifMauTypeList } + STATUS current + DESCRIPTION + "Conformance group for MAUs attached + to interfaces with 100 Mb/s capability." + ::= { mauModObjGrps 5 } - ifJackIfIndex, - ifJackMauIndex, - ifJackIndex, - ifJackType } + mauIfGrpJack OBJECT-GROUP + OBJECTS { ifJackType } STATUS current + +, DESCRIPTION "Conformance group for MAUs attached - to interfaces with extended management - (including 100 Mb/s and jack management)." - ::= { mauModObjGrps 4 } + to interfaces with managed jacks." + ::= { mauModObjGrps 6 } 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 } + ::= { mauModObjGrps 7 } 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 } - -- Notification groups - - -- ?? later + ::= { mauModObjGrps 8 } -- Compliances mauModRpCompl MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance for MAUs attached to repeater ports." MODULE -- this module MANDATORY-GROUPS { mauRpGrpBasic } - GROUP mauRpGrpExtended + GROUP mauRpGrp100Mbs + +, DESCRIPTION "Implementation of this optional group is recommended for MAUs which have 100Mb/s - capability and/or more than one attached - external jack." + capability." + + GROUP mauRpGrpJack + DESCRIPTION + "Implementation of this optional group is + recommended for MAUs which have one or more + external jacks." ::= { mauModCompls 1 } mauModIfCompl MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance for MAUs attached to interfaces." MODULE -- this module MANDATORY-GROUPS { mauIfGrpBasic } - GROUP mauIfGrpExtended + GROUP mauIfGrp100Mbs DESCRIPTION "Implementation of this optional group is recommended for MAUs which have 100Mb/s - capability and/or more than one attached - external jack." + capability." + + GROUP mauIfGrpJack + DESCRIPTION + "Implementation of this optional group is + recommended for MAUs which have one or more + external jacks." GROUP mauIfGrpAutoNeg DESCRIPTION - "Implementation of this optional group - is recommended for MAUs which support + "Implementation of this group is + mandatory for MAUs which support managed auto-negotiation." + GROUP mauBroadBasic DESCRIPTION "Implementation of this group is mandatory for broadband MAUs." +, ::= { mauModCompls 2 } END + +, 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. + Objects for IEEE 802.3 Repeater Devices", May 1996. + + [5] McCloghrie, K., and M. Rose, Editors, "Management + Information Base for Network Management of TCP/IP-based + internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, + Performance Systems International, March 1991. + + [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., + and S. Waldbusser, "Structure of Management Information + for version 2 of the Simple Network Management Protocol + (SNMPv2)", RFC 1902, January 1996. + + [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., + and S. Waldbusser, "Textual Conventions for version 2 of + the Simple Network Management Protocol (SNMPv2)", RFC + 1903, January 1996. + + [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., + and S. Waldbusser, "Conformance Statements for version 2 + of the Simple Network Management Protocol (SNMPv2)", RFC + 1904, January 1996. + + [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., + and S. Waldbusser, "Protocol Operations for version 2 of + the Simple Network Management Protocol (SNMPv2)", RFC + 1905, January 1996. + + [10] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple + Network Management Protocol", RFC 1157, SNMP Research, + +, + Performance Systems International, MIT Laboratory for + Computer Science, May 1990. + + [11] McMaster, D., K. McCloghrie, S. Roberts, "Definitions of + Managed Objects for IEEE 802.3 Medium Attachment Units + (MAUs)", RFC 1515, September 1993. + +, + 5. Security Considerations + + Security issues are not discussed in this memo. + + 6. Authors' Addresses + + Dan Romascanu + Madge Networks (Israel) Ltd. + Atidim Technology Park, Bldg. 3 + Tel Aviv 61131, Israel + Tel: 972-3-6458414, 6458458 + Fax: 972-3-6487146 + E-mail: dromasca@madge.com + + Kathryn de Graaf + 3Com Corporation + 118 Turnpike Rd. + Southborough, MA 01772 USA + Tel: (508)229-1627 + Fax: (508)490-5882 + E-mail: kdegraaf@isd.3com.com + +, + Table of Contents + + 1 The SNMPv2 Network Management Framework ............... 2 + 1.1 Object Definitions .................................. 2 + 2 Overview .............................................. 4 + 2.1 Relationship to RFC 1515 ............................ 4 + 2.2 MAU Management ...................................... 4 + 2.3 Relationship to Other MIBs .......................... 4 + 2.3.1 Relationship to the MIB-II 'interfaces' group ..... 5 + 2.3.2 Relationship to the 802.3 Repeater MIB ............ 5 + 2.4 Management of Internal MAUs ......................... 5 + 3 Definitions ........................................... 7 + 4 References ............................................ 41 + 5 Security Considerations ............................... 43 + 6 Authors' Addresses .................................... 43