--- 1/draft-ietf-hubmib-mau-mib-02.txt 2006-02-04 23:26:14.000000000 +0100 +++ 2/draft-ietf-hubmib-mau-mib-03.txt 2006-02-04 23:26:14.000000000 +0100 @@ -1,45 +1,52 @@ + Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) - 31 May 1996 + 23 August 1996 - + + + Donna McMaster + Livingston Enterprises + + Keith McCloghrie + Cisco Systems Inc. + + Sam Roberts + Farallon Computing, Inc. Dan Romascanu Madge Networks (Israel) Ltd. - 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 groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet- Drafts as reference material or to cite them other than as a "work in progress". To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), - -, 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. @@ -49,40 +56,39 @@ 1. The SNMPv2 Network Management Framework The SNMPv2 Network Management Framework presently consists of three major components. They are: o the SMI, described in RFC 1902 [6] - the mechanisms used for describing and naming objects for the purpose of management. +, o the MIB-II, STD 17, RFC 1213 [5] - the core set of managed objects for the Internet suite of protocols. 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 @@ -177,25 +183,27 @@ , 3. Definitions MAU-MIB DEFINITIONS ::= BEGIN IMPORTS Counter32, Integer32, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 FROM SNMPv2-SMI + TruthValue + FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE FROM SNMPv2-CONF; mauMod MODULE-IDENTITY - LAST-UPDATED "9605310000Z" + LAST-UPDATED "9608230000Z" 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 @@ -211,24 +219,24 @@ 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 , + 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 } @@ -254,24 +262,24 @@ 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 but , + 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 since RFC 1515: dot3MauType10BaseTHD -- UTP MAU (per 802.3 section 14) -- half duplex mode OBJECT IDENTIFIER ::= { dot3MauType 10 } dot3MauType10BaseTFD -- UTP MAU (per 802.3 section 14) @@ -301,23 +309,22 @@ -- 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." @@ -348,23 +355,24 @@ rpMauMediaAvail INTEGER, rpMauMediaAvailStateExits Counter32, rpMauJabberState INTEGER, rpMauJabberingStateEnters Counter32, rpMauFalseCarriers Counter32 - } , + } + rpMauGroupIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the group containing the port to which the MAU described by this entry is connected. Note: In practice, a group will generally be a @@ -380,38 +388,37 @@ rpMauPortIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the repeater port within group rpMauGroupIndex to which the MAU described by this entry is connected." REFERENCE - "" + "Reference RFC 1516, rptrPortIndex." ::= { rpMauEntry 2 } rpMauIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the MAU 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 - , + 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 @@ -442,23 +449,22 @@ "The current state of the MAU. This object may be implemented as a read-only object by those agents and MAUs that do not implement software control of the MAU state. Some agents may not support setting the value of this object to some of the enumerated values. The value other(1) is returned if the MAU is in a state other than one of the states 2 through 6. - The value unknown(2) is returned when the MAU's - , + 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 @@ -489,23 +495,23 @@ "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, acRESETMAU." ::= { rpMauEntry 5 } rpMauMediaAvail OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), available(3), - notAvailable(4), , + 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, @@ -536,23 +542,23 @@ For 100BASE-T4, 100BASE-TX and 100BASE-FX the enumerations match the states within the respective link integrity state diagrams, fig 23- 12 and 24-15 of sections 23 and 24 of [2]. Any MAU which implements management of auto- negotiation will map remote fault indication to remote fault. The value available(3) indicates that the link, - light, or loopback is normal. The value , + light, or loopback is normal. The value notAvailable(4) indicates link loss, low light, or no loopback. The value remoteFault(5) indicates that a fault has been detected at the remote end of the link. This value applies to 10BASE-FB, 100BASE-T4 Far End Fault Indication and non-specified remote faults from a system running auto-negotiation. The values remoteJabber(7), remoteLinkLoss(8), and remoteTest(9) should be used instead of @@ -583,23 +589,23 @@ DESCRIPTION "A count of the number of times that rpMauMediaAvail for this MAU instance leaves the state available(3)." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." ::= { rpMauEntry 7 } rpMauJabberState OBJECT-TYPE SYNTAX INTEGER { - other(1), , + 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. @@ -630,23 +636,23 @@ dot3MauType100BaseTX, and dot3MauType100BaseFX, this counter will always indicate zero." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, aJabber.jabberCounter." ::= { rpMauEntry 9 } rpMauFalseCarriers OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only - STATUS current , + 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 @@ -763,28 +769,31 @@ INTEGER, ifMauMediaAvailStateExits Counter32, ifMauJabberState INTEGER, ifMauJabberingStateEnters Counter32, ifMauFalseCarriers Counter32, ifMauTypeList - Integer32 + Integer32, + ifMauDefaultType + OBJECT IDENTIFIER, + ifMauAutoNegSupported + TruthValue } +, 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 @@ -794,46 +803,47 @@ DESCRIPTION "This variable uniquely identifies the MAU 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-write + MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the 10 or 100 Mb/s baseband MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value. - 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 + This object represents the operational type of the + MAU, as determined by either (1) the result of the , - value of this object reflects the result of the - auto-negotiation function." + auto-negotiation function or (2) if auto- + negotiation is not enabled or is not implemented + for this MAU, by the value of the object + ifMauDefaultType. In case (2), a set to the + object ifMauDefaultType will force the MAU into + the new operating mode." 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), @@ -859,26 +869,26 @@ A MAU in the operational(3) state is fully functional, operates, and passes signals to its attached DTE or repeater port in accordance to its specification. A MAU in standby(4) state forces DI and CI to idle and the media transmitter to idle or fault, if supported. Standby(4) mode only applies to link type MAUs. The state of 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 @@ -906,26 +916,26 @@ remoteJabber(7), remoteLinkLoss(8), remoteTest(9) } MAX-ACCESS read-only STATUS current DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 10BASE-T, 10BASE-F) then this is equivalent to the link test fail state/low light function. For an + +, AUI or a coax (including broadband) MAU this indicates whether or not loopback is detected on the DI circuit. The value of this attribute persists between packets for MAU types AUI, - -, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. The value other(1) is returned if the mediaAvail state is not one of 2 through 6. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. At power-up or following a reset, the value of this attribute will be unknown for AUI, coax, and 10BASE-FP MAUs. For these MAUs @@ -954,25 +964,24 @@ The value remoteFault(5) indicates that a fault has been detected at the remote end of the link. This value applies to 10BASE-FB, 100BASE-T4 Far End Fault Indication and non-specified remote faults from a system running auto-negotiation. The values remoteJabber(7), remoteLinkLoss(8), and remoteTest(9) should be used instead of remoteFault(5) where the reason for remote fault is identified in the remote signaling protocol. +, The value invalidSignal(6) indicates that an invalid signal has been received from the other end of the link. InvalidSignal(6) applies only to - -, MAUs of type 10BASE-FB. Where an IEEE Std 802.3u-1995 clause 22 MII is present, a logic one in the remote fault bit (reference section 22.2.4.2.8 of that document) maps to the value remoteFault(5), and a logic zero in the link status bit (reference section 22.2.4.2.10 of that document) maps to the value notAvailable(4). The value notAvailable(4) takes precedence over the value remoteFault(5)." @@ -1001,25 +1010,25 @@ } MAX-ACCESS read-only STATUS current DESCRIPTION "The value other(1) is returned if the jabber state is not 2, 3, or 4. The agent must always return other(1) for MAU type dot3MauTypeAUI. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is + +, being initialized. If the MAU is not jabbering the agent returns - -, noJabber(3). This is the 'normal' state. If the MAU is in jabber state the agent returns the jabbering(4) value." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, aJabber.jabberFlag." ::= { ifMauEntry 7 } ifMauJabberingStateEnters OBJECT-TYPE @@ -1048,25 +1057,24 @@ not increment at the symbol rate. It can increment after a valid carrier completion at a maximum rate of once per 100 ms until the next carrier event. This counter increments only for MAUs of type dot3MauType100BaseT4, dot3MauType100BaseTX, and dot3MauType100BaseFX. For all other MAU types, this counter will always indicate zero. +, The approximate minimum time for rollover of this counter is 7.4 hours." REFERENCE - -, "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." ::= { 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. @@ -1095,28 +1103,84 @@ 8 10BASE-FL duplex mode unknown 9 10BROAD36 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 } + ifMauDefaultType OBJECT-TYPE + SYNTAX OBJECT IDENTIFIER + MAX-ACCESS read-write + STATUS current + DESCRIPTION + "This object identifies the default administrative + 10 or 100 Mb/s baseband MAU type, to be used in + conjunction with the operational MAU type denoted + by ifMauType. + + The set of possible values for this object is the + same as the set defined for the ifMauType object. + + This object represents the administratively- + configured type of the MAU. If auto-negotiation + is not enabled or is not implemented for this MAU, + the value of this object determines the + operational type of the MAU. In this case, a set + to this object will force the MAU into the + specified operating mode. + + If auto-negotiation is implemented and enabled for + this MAU, the operational type of the MAU is + determined by auto-negotiation, and the value of + this object denotes the type to which the MAU will + automatically revert if/when auto-negotiation is + later disabled. + + NOTE TO IMPLEMENTORS: It may be necessary to + provide for underlying hardware implementations + which do not follow the exact behavior specified + above. In particular, when + ifMauAutoNegAdminStatus transitions from enabled + to disabled, the agent implementation must ensure + that the operational type of the MAU (as reported + by ifMauType) correctly transitions to the value + specified by this object, rather than continuing + to operate at the value earlier determined by the + +, + auto-negotiation function." + REFERENCE + "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID, and [IEEE + 802.3 Std], 22.2.4.1.4." + ::= { ifMauEntry 11 } + + ifMauAutoNegSupported OBJECT-TYPE + SYNTAX TruthValue + MAX-ACCESS read-only + STATUS current + DESCRIPTION + "This object indicates whether or not auto- + negotiation is supported on this MAU." + ::= { ifMauEntry 12 } + -- The ifJackTable applies to MAUs attached to interfaces -- which have one or more external jacks (connectors). ifJackTable OBJECT-TYPE SYNTAX SEQUENCE OF IfJackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about the external jacks attached to MAUs attached to an interface." @@ -1131,33 +1195,33 @@ about a particular jack." INDEX { ifMauIfIndex, ifMauIndex, ifJackIndex } ::= { ifJackTable 1 } IfJackEntry ::= SEQUENCE { ifJackIndex Integer32, + +, ifJackType INTEGER } ifJackIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS not-accessible STATUS current DESCRIPTION "This variable uniquely identifies the jack described by this entry from among other jacks - -, attached to the same MAU." ::= { ifJackEntry 1 } ifJackType OBJECT-TYPE SYNTAX INTEGER { other(1), rj45(2), rj45S(3), -- rj45 shielded db9(4), bnc(5), @@ -1176,34 +1240,34 @@ ::= { ifJackEntry 2 } -- The ifMauAutoNegTable applies to systems in which -- auto-negotiation is supported on one or more MAUs -- 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." INDEX { ifMauIfIndex, ifMauIndex } ::= { ifMauAutoNegTable 1 } IfMauAutoNegEntry ::= SEQUENCE { ifMauAutoNegAdminStatus @@ -1222,34 +1286,43 @@ 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 ability to be enabled. 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." + forced to the state indicated by the value of the + object ifMauDefaultType. -, + NOTE TO IMPLEMENTORS: When + ifMauAutoNegAdminStatus transitions from enabled + to disabled, the agent implementation must ensure + that the operational type of the MAU (as reported + by ifMauType) correctly transitions to the value + specified by the ifMauDefaultType object, rather + than continuing to operate at the value earlier + determined by the auto-negotiation function." 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) } @@ -1260,20 +1333,22 @@ link is using auto-negotiation signaling. It takes the value detected(1) if and only if, during the previous link negotiation, FLP Bursts were received." REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.3, aAutoNegRemoteSignaling." ::= { ifMauAutoNegEntry 2 } ifMauAutoNegConfig OBJECT-TYPE + +, SYNTAX INTEGER { other(1), configuring(2), complete(3), disabled(4), parallelDetectFail(5) } MAX-ACCESS read-only STATUS current DESCRIPTION @@ -1281,22 +1356,20 @@ 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 @@ -1307,20 +1380,22 @@ duplex would have a value of 98304 ((2**15) + (2**16)). The powers of 2 assigned to the capabilities are these: Power Capability 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." @@ -1328,22 +1403,20 @@ "[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." @@ -1354,20 +1427,22 @@ MAX-ACCESS read-only STATUS current DESCRIPTION "A value that uniquely identifies the set of capabilities received from the remote auto- negotiation entity. Refer to ifMauAutoNegCapability for a description of the possible values of this object. Note that interfaces that support this MIB may be + +, attached to remote auto-negotiation entities which have capabilities beyond the scope of this MIB." REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.7, aAutoNegReceivedTechnologyAbility." ::= { ifMauAutoNegEntry 7 } ifMauAutoNegRestart OBJECT-TYPE SYNTAX INTEGER { restart(1), @@ -1375,22 +1450,20 @@ } 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 8 } broadMauBasicTable OBJECT-TYPE SYNTAX SEQUENCE OF BroadMauBasicEntry MAX-ACCESS not-accessible STATUS current @@ -1400,20 +1473,22 @@ ::= { dot3BroadMauBasicGroup 1 } broadMauBasicEntry OBJECT-TYPE SYNTAX BroadMauBasicEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the table, containing information about a single broadband MAU." INDEX { broadMauIfIndex, broadMauIndex } + +, ::= { broadMauBasicTable 1 } BroadMauBasicEntry ::= SEQUENCE { broadMauIfIndex Integer32, broadMauIndex Integer32, broadMauXmtRcvSplitType INTEGER, @@ -1421,22 +1496,20 @@ 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 @@ -1447,20 +1520,22 @@ described by this entry." REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID." ::= { broadMauBasicEntry 2 } broadMauXmtRcvSplitType OBJECT-TYPE SYNTAX INTEGER { other(1), single(2), dual(3) + +, } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the type of frequency multiplexing/cabling system used to separate the transmit and receive paths for the 10BROAD36 MAU. The value other(1) is returned if the split type is not either single or dual. @@ -1468,22 +1543,20 @@ 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 } @@ -1494,41 +1567,40 @@ STATUS current DESCRIPTION "This variable indicates the translation offset frequency of the 10BROAD36 MAU in MHz/4; that is, in units of 250 kHz." REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aBroadbandFrequencies.translationFrequency." ::= { broadMauBasicEntry 5 } +, -- Notifications for use by 802.3 MAUs rpMauJabberTrap NOTIFICATION-TYPE OBJECTS { rpMauJabberState } STATUS current DESCRIPTION "This trap is sent whenever a managed repeater MAU enters the jabber state. The agent must throttle the generation of consecutive rpMauJabberTraps so that there is at least a five-second gap between them." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber notification." ::= { snmpDot3MauMgt 0 1 } ifMauJabberTrap NOTIFICATION-TYPE OBJECTS { ifMauJabberState } - -, STATUS current DESCRIPTION "This trap is sent whenever a managed interface MAU enters the jabber state. The agent must throttle the generation of consecutive ifMauJabberTraps so that there is at least a five-second gap between them." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber @@ -1539,41 +1611,41 @@ mauModConf OBJECT IDENTIFIER ::= { mauMod 1 } mauModCompls OBJECT IDENTIFIER ::= { mauModConf 1 } mauModObjGrps OBJECT IDENTIFIER ::= { mauModConf 2 } mauModNotGrps OBJECT IDENTIFIER ::= { mauModConf 3 } +, -- Object groups mauRpGrpBasic OBJECT-GROUP OBJECTS { rpMauGroupIndex, rpMauPortIndex, rpMauIndex, rpMauType, rpMauStatus, rpMauMediaAvail, rpMauMediaAvailStateExits, rpMauJabberState, rpMauJabberingStateEnters } STATUS current DESCRIPTION "Basic conformance group for MAUs attached to repeater ports. This group is also the conformance specification for RFC 1515 implementations." ::= { mauModObjGrps 1 } -, mauRpGrp100Mbs OBJECT-GROUP OBJECTS { rpMauFalseCarriers } STATUS current DESCRIPTION "Conformance group for MAUs attached to repeater ports with 100 Mb/s capability." ::= { mauModObjGrps 2 } mauRpGrpJack OBJECT-GROUP OBJECTS { rpJackType } @@ -1585,42 +1657,44 @@ 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 4 } mauIfGrp100Mbs OBJECT-GROUP OBJECTS { ifMauFalseCarriers, - ifMauTypeList } + ifMauTypeList, + ifMauDefaultType, + ifMauAutoNegSupported } STATUS current DESCRIPTION "Conformance group for MAUs attached to interfaces with 100 Mb/s capability." ::= { mauModObjGrps 5 } mauIfGrpJack OBJECT-GROUP OBJECTS { ifJackType } STATUS current - -, DESCRIPTION "Conformance group for MAUs attached to interfaces with managed jacks." ::= { mauModObjGrps 6 } mauIfGrpAutoNeg OBJECT-GROUP OBJECTS { ifMauAutoNegAdminStatus, ifMauAutoNegRemoteSignaling, ifMauAutoNegConfig, ifMauAutoNegCapability, @@ -1630,20 +1704,22 @@ STATUS current DESCRIPTION "Conformance group for MAUs attached to interfaces with managed auto-negotiation." ::= { 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 8 } @@ -1651,22 +1727,20 @@ mauModRpCompl MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance for MAUs attached to repeater ports." MODULE -- this module MANDATORY-GROUPS { mauRpGrpBasic } GROUP mauRpGrp100Mbs - -, DESCRIPTION "Implementation of this optional group is recommended for MAUs which have 100Mb/s capability." GROUP mauRpGrpJack DESCRIPTION "Implementation of this optional group is recommended for MAUs which have one or more external jacks." @@ -1675,20 +1749,22 @@ mauModIfCompl MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance for MAUs attached to interfaces." MODULE -- this module MANDATORY-GROUPS { mauIfGrpBasic } GROUP mauIfGrp100Mbs + +, DESCRIPTION "Implementation of this optional group is recommended for MAUs which have 100Mb/s capability." GROUP mauIfGrpJack DESCRIPTION "Implementation of this optional group is recommended for MAUs which have one or more external jacks." @@ -1697,27 +1773,43 @@ DESCRIPTION "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 + 4. Acknowledgements + + This document was produced by the IETF Hub MIB Working Group, + whose efforts were greatly advanced by the contributions of + the following people: + + Chuck Black + John Flick + Jeff Johnson + Leon Leong + Mike Lui + Dave Perkins + Geoff Thompson + Maurice Turcotte + Paul Woodruff + +, + 5. 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. @@ -1758,25 +1850,44 @@ , 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 + 6. Security Considerations Security issues are not discussed in this memo. - 6. Authors' Addresses + 7. Authors' Addresses + + Donna McMaster + Livingston Enterprises + Tel: (916) 676-1147 + E-Mail: donna@livingston.com + + Keith McCloghrie + Cisco Systems Inc. + 170 West Tasman Drive + San Jose, CA 95134 + Tel: (408) 526-5260 + E-Mail: kzm@cisco.com + + Sam Roberts + Farallon Computing, Inc. + 2470 Mariner Square Loop + Alameda, CA 94501-1010 + Tel: (510) 814-5215 + E-Mail: sroberts@farallon.com 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 @@ -1784,22 +1895,23 @@ 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 + 1.1 Object Definitions .................................. 3 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 + 4 Acknowledgements ...................................... 42 + 5 References ............................................ 43 + 6 Security Considerations ............................... 45 + 7 Authors' Addresses .................................... 45