--- 1/draft-ietf-hubmib-mau-mib-v3-00.txt 2006-02-04 23:26:20.000000000 +0100 +++ 2/draft-ietf-hubmib-mau-mib-v3-01.txt 2006-02-04 23:26:20.000000000 +0100 @@ -11,26 +11,26 @@ K. de Graaf Argon Networks D. Romascanu Avaya Inc. D. McMaster Cisco Systems, Inc. K. McCloghrie Cisco Systems, Inc. S. Roberts Farallon Computing, Inc. - June 2001 + February 2002 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs) - + Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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. @@ -41,30 +41,32 @@ material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt To view the list Internet-Draft Shadow Directories, see http://www.ietf.org/shadow.html. Copyright Notice - Copyright (C) The Internet Society (2001). All Rights Reserved. + Copyright (C) The Internet Society (2002). All Rights Reserved. Abstract This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo obsoletes RFC 2668, ''Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)''. This memo extends that specification by including management information useful for the - management of 10 gigabit per second (Gb/s) MAUs. + management of 10 gigabit per second (Gb/s) MAUs. This memo also + obsoletes RFC 1515, ''Definitions of Managed Objects for IEEE 802.3 + Medium Attachment Units (MAUs)''. Ethernet technology, as defined by the 802.3 Working Group of the IEEE, continues to evolve, with scalable increases in speed, new types of cabling and interfaces, and new features. This evolution may require changes in the managed objects in order to reflect this new functionality. This document, as with other documents issued by this working group, reflects a certain stage in the evolution of Ethernet technology. In the future, this document might be revised, or new documents might be issued by the Ethernet Interfaces and Hub MIB Working Group, in order to reflect the evolution of Ethernet @@ -72,224 +74,309 @@ Distribution of this memo is unlimited. Please forward comments to hubmib@ietf.org. Table of Contents 1. Introduction ............................................... 3 2. The SNMP Management Framework .............................. 3 3. Overview ................................................... 4 3.1. Relationship to RFC 2668 ................................. 4 - 3.2. Relationship to RFC 2239 ................................. 4 + 3.2. Relationship to RFC 2239 ................................. 5 3.3. Relationship to RFC 1515 ................................. 5 - 3.4. MAU Management ........................................... 5 3.5. Relationship to Other MIBs ............................... 5 3.5.1. Relationship to the Interfaces MIB ..................... 5 3.5.2. Relationship to the 802.3 Repeater MIB ................. 6 3.6. Management of Internal MAUs .............................. 6 - 4. Definitions ................................................ 6 - 5. Intellectual Property ...................................... 51 - 6. Acknowledgements ........................................... 52 - 7. References ................................................. 52 - 8. Security Considerations .................................... 54 - 9. Authors' Addresses ......................................... 55 - A. Change Log ................................................. 55 - A.1. Changes since RFC 2668 ................................... 55 - A.2. Changes between RFC 2239 and RFC 2668 .................... 56 - B. Full Copyright Statement ................................... 57 + 3.7. Mapping of IEEE 802.3 Managed Objects .................... 7 + 4. Definitions ................................................ 8 + 5. Intellectual Property ...................................... 55 + 6. Acknowledgements ........................................... 56 + 7. References ................................................. 56 + 8. Security Considerations .................................... 59 + 9. Authors' Addresses ......................................... 59 + A. Change Log ................................................. 59 + A.1. Changes since RFC 2668 ................................... 59 + A.2. Changes between RFC 2239 and RFC 2668 .................... 60 + B. Full Copyright Statement ................................... 61 1. Introduction This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it defines objects for managing IEEE 802.3 Medium Attachment Units (MAUs). This memo also includes a MIB module. This MIB module extends the list of managed objects specified in the earlier version of this MIB: - RFC 2668 [23]. + RFC 2668 [RFC2668]. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this - document are to be interpreted as described in [22]. + document are to be interpreted as described in [RFC2119]. 2. The SNMP Management Framework The SNMP Management Framework presently consists of five major components: - o An overall architecture, described in RFC 2571 [1]. + o An overall architecture, described in RFC 2571 [RFC2571]. o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in - STD 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. - The second version, called SMIv2, is described in STD 58, RFC - 2578 [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7]. + STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC + 1215 [RFC1215]. The second version, called SMIv2, is described + in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and + STD 58, RFC 2580 [RFC2580]. o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and - described in STD 15, RFC 1157 [8]. A second version of the SNMP - message protocol, which is not an Internet standards track - protocol, is called SNMPv2c and described in RFC 1901 [9] and - RFC 1906 [10]. The third version of the message protocol is - called SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and - RFC 2574 [12]. + described in STD 15, RFC 1157 [RFC1157]. A second version of + the SNMP message protocol, which is not an Internet standards + track protocol, is called SNMPv2c and described in RFC 1901 + [RFC1901] and RFC 1906 [RFC1906]. The third version of the + message protocol is called SNMPv3 and described in RFC 1906 + [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. o Protocol operations for accessing management information. The first set of protocol operations and associated PDU formats is - described in STD 15, RFC 1157 [8]. A second set of protocol - operations and associated PDU formats is described in RFC 1905 - [13]. + described in STD 15, RFC 1157 [RFC1157]. A second set of + protocol operations and associated PDU formats is described in + RFC 1905 [RFC1905]. - o A set of fundamental applications described in RFC 2573 [14] and - the view-based access control mechanism described in RFC 2575 - [15]. + o A set of fundamental applications described in RFC 2573 + [RFC2573] and the view-based access control mechanism described + in RFC 2575 [RFC2575]. A more detailed introduction to the current SNMP Management Framework - can be found in RFC 2570 [16]. + can be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no translation is possible (use of Counter64). Some machine readable information in SMIv2 will be converted into textual descriptions in SMIv1 during the translation process. However, this loss of machine readable information is not considered to change the semantics of the MIB. 3. Overview -3.1. Relationship to RFC 2668 + 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 [IEEE802.3]. 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 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Medium + Attachment Units (MAUs)", Section 30.6, "Management for link Auto- + Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed + object classes" of IEEE Std. 802.3, 2000 edition [IEEE802.3], as + ammended by IEEE Draft P802.3ae/D4.01 [P802.3ae]. That specification + includes definitions for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s + devices. This specification is intended to serve the same purpose: to + provide for management of all types of Ethernet/802.3 MAUs. +3.1. Relationship to RFC 2668 This MIB is intended to be a superset of that defined by RFC 2668 - [23], which will go to historic status. This MIB includes all of the - objects contained in that MIB, with new and updated definitions which - provide support for 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 and updated definitions provide management support for 10 Gb/s - devices. + [RFC2668], which will go to historic status. This MIB includes all + of the objects contained in that MIB, with new and updated + definitions which provide support for 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 and updated definitions provide + management support for 10 Gb/s devices. 3.2. Relationship to RFC 2239 - RFC 2668 was a replacement for RFC 2239 [24], which is now historic. - RFC 2668 defined a superset of that defined by RFC 2239 [24], which - contained all of the objects defined in RFC 2239, plus several new - ones which provide additional capabilities. The new objects provided - management support for: + RFC 2668 was a replacement for RFC 2239 [RFC2239], which is now + historic. RFC 2668 defined a superset of that defined by RFC 2239 + [RFC2239], which contained all of the objects defined in RFC 2239, + plus several new ones which provide additional capabilities. The new + objects provided management support for: o management of 1000 Mb/s devices o management of PAUSE negotiation + o management of remote fault status 3.3. Relationship to RFC 1515 - RFC 2239 was a replacement for RFC 1515 [25], which is now historic. - RFC 2239 defined a superset of RFC 1515 which contained all of the - objects defined in RFC 1515, plus several new ones which provided - additional capabilities. The new objects in RFC 2239 provided - management support for: + RFC 2239 was a replacement for RFC 1515 [RFC1515], which is now + historic. RFC 2239 defined a superset of RFC 1515 which contained + all of the objects defined in RFC 1515, plus several new ones which + provided additional capabilities. The new objects in RFC 2239 + provided management support for: o management of 100 Mb/s devices o auto-negotiation on interface MAUs o jack management -3.4. 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 [17]. 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 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Medium - Attachment Units (MAUs)", and Annex 30A, "GDMO Specifications for - 802.3 managed object classes" of IEEE Std. 802.3, 2000 edition [17], - as ammended by IEEE Draft P802.3ae/D3.0 [18]. That specification - includes definitions for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s - devices. This specification is intended to serve the same purpose: to - provide for management of all types of Ethernet/802.3 MAUs. - 3.5. 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 [20]. The following - sections identify other MIBs that such an agent should implement. + (at least) the 'system' group defined in the SNMPv2 MIB [RFC1907]. + The following sections identify other MIBs that such an agent should + implement. 3.5.1. Relationship to the Interfaces MIB. The sections of this document that define interface MAU-related - objects specify an extension to the Interfaces MIB [21]. An agent - implementing these interface-MAU related objects MUST also implement - the relevant groups of Interface MIB. The value of the object - ifMauIfIndex is the same as the value of 'ifIndex' used to + objects specify an extension to the Interfaces MIB [RFC2863]. An + agent implementing these interface-MAU related objects MUST also + implement the relevant groups of Interface MIB. 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 REQUIRED that an agent implementing the interface-MAU related objects in this MIB will also implement the Ethernet-like Interfaces - MIB, [26]. + MIB, [ETHERIF]. Furthermore, when the interface-MAU related objects + are used to manage a 10GBASE-W PHY -- e.e., when ifMauType is equal + to dot2MauType10GigBaseW or any other 10GBASE-W variant -- then the + agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB + [ETHERWIS] and must follow the interface layering model specified + therein. In that case the value of the object ifMauIfIndex is the + same as the value of 'ifIndex' for the layer at the top of the stack, + i.e., for the ifTable entry that has 'ifType' equal to + ethernetCsmacd(6). If the interface-MAU related objects are used to + manage a PHY that allows the MAU type to be changed dynamically, then + the agent SHALL create ifTable, ifStackTable, and ifInvStackTable + entries that pertain to the WIS when ifMauDefaultType is changed to a + 10GBASEW variant (i.e., one of dot3MauType10GigBaseW, + dot3MauType10GigBaseEW, dot3MauType10GigBaseLW, or + dot3MauType10GigBaseSW) from any other type, and shall destroy the + WIS-related entries when ifMauDefaultType is changed to a non- + 10GBASE-W type. The agent SHALL also change the values of + 'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry indexed + by ifMauIfIndex as specified in [ETHERIF] and [ETHERWIS] when + ifMauDefaultType is manipulated in this way but SHALL NOT otherwise + alter that entry. (Note that repeater ports are not represented as interfaces in the Interface MIB.) 3.5.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 - [19]. An agent implementing these repeater-MAU related objects MUST - also implement the 802.3 Repeater MIB. + [RFC2108]. 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. 3.6. 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 subtree: dot3RpMauBasicGroup for internal repeater-MAUs and dot3IfMauBasicGroup for internal interface-MAUs. +3.7. Mapping of IEEE 802.3 Managed Objects + + IEEE 802.3 Managed Object Corresponding SNMP Object + + oMAU + .aMAUID rpMauIndex or + ifMauIndex or + broadMauIndex + .aMAUType rpMauType or + ifMauType + .aMAUTypeList ifMauTypeListBits + .aMediaAvailable rpMauMediaAvailable or + ifMauMediaAvailable + .aLoseMediaCounter rpMauMediaAvailableStateExits + or + ifMauMediaAvailableStateExits + .aJabber rpMauJabberState and + rpMauJabberingStateEnters or + ifMauJabberState and + ifMauJabberingStateEnters + .aMAUAdminState rpMauStatus or + ifMauStatus + .aBbMAUXmitRcvSplitType broadMauXmtRcvSplitType + .aBroadbandFrequencies broadMauXmtCarrierFreq and + broadMauTranslationFreq + .aFalseCarriers rpMauFalseCarriers or + ifMauFalseCarriers + .acResetMAU rpMauStatus or + ifMauStatus + .acMAUAdminControl rpMauStatus or + ifMauStatus + .nJabber rpMauJabberTrap or + ifMauJabberTrap + + oAutoNegotiation + .aAutoNegID ifMauIndex + .aAutoNegAdminState ifMauAutoNegAdminStatus + .aAutoNegRemoteSignalling ifMauAutoNegRemoteSignalling + .aAutoNegAutoConfig ifMauAutoNegConfig + .aAutoNegLocalTechnologyAbility ifMauAutoNegCapabilityBits + .aAutoNegAdvertisedTechnologyAbility ifMauAutoNegAdvertisedBits and + ifMauAutoNegRemoteFaultAdvertised + .aAutoNegReceivedTechnologyAbility ifMauAutoNegReceivedBits and + ifMauAutoNegRemoteFaultReceived + .acAutoNegRestartAutoConfig ifMauAutoNegRestart + .acAutoNegAdminControl ifMauAutoNegAdminStatus + + The following IEEE 802.3 managed objects have not been included in + this MIB for the following reasons. + + IEEE 802.3 Managed Object Corresponding SNMP Object + + oMAU + .aIdleErrorCount Only useful for 100BaseT2, + which is not widely + implemented. + + oAutoNegotiation + .aAutoNegLocalSelectorAbility Only needed for support of + .aAutoNegAdvertisedSelectorAbility isoethernet (802.9a), which is + .aAutoNegReceivedSelectorAbility not supported by this MIB. + 4. Definitions MAU-MIB DEFINITIONS ::= BEGIN IMPORTS - Counter32, Integer32, + Counter32, Integer32, Counter64, OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, OBJECT-IDENTITY, mib-2 FROM SNMPv2-SMI TruthValue, TEXTUAL-CONVENTION FROM SNMPv2-TC OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP FROM SNMPv2-CONF InterfaceIndex FROM IF-MIB; + mauMod MODULE-IDENTITY - LAST-UPDATED "200106260024Z" -- June 26, 2001 + LAST-UPDATED "200202280000Z" -- February 28, 2002 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" CONTACT-INFO "WG E-mail: hubmib@ietf.org To subscribe: hubmib-request@ietf.org Chair: Dan Romascanu Postal: Avaya Inc. Atidim Technology Park, Bldg. 3 Tel Aviv 61131 @@ -312,31 +399,32 @@ [IEEE 802.3 Std] refers to IEEE Std 802.3, 2000 Edition: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications', as - ammended by IEEE Draft P802.3ae/D3.0: + ammended by IEEE Draft P802.3ae/D4.01: 'Supplement to Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method & Physica Layer Specifications - Media Access Control (MAC) Parameters, Physical Layer, and Management Parameters - for 10 Gb/s Operation', March 2001. + for 10 Gb/s Operation', February 2002. Of particular interest is Clause 30, '10Mb/s, 100Mb/s, 1000Mb/s and 10 Gb/s Management'." - REVISION "200106260024Z" -- June 26, 2001 + + REVISION "200202280000Z" -- February 28, 2002 DESCRIPTION "This version published as RFC XXXX. Updated to include support for 10 Gb/s MAUs." REVISION "9908240400Z" -- August 24, 1999 DESCRIPTION "This version published as RFC 2668. Updated to include support for 1000 Mb/sec MAUs and flow control negotiation." REVISION "9710310000Z" -- October 31, 1997 DESCRIPTION "Version published as RFC 2239." @@ -360,21 +448,22 @@ rj45S(3), -- rj45 shielded db9(4), bnc(5), fAUI(6), -- female aui mAUI(7), -- male aui fiberSC(8), fiberMIC(9), fiberST(10), telco(11), mtrj(12), -- fiber MT-RJ - hssdc(13) -- fiber channel style-2 + hssdc(13), -- fiber channel style-2 + fiberLC(14) } dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } dot3IfMauAutoNegGroup @@ -1048,31 +1141,32 @@ ifMauType OBJECT IDENTIFIER, ifMauStatus INTEGER, ifMauMediaAvailable INTEGER, ifMauMediaAvailableStateExits Counter32, ifMauJabberState INTEGER, ifMauJabberingStateEnters Counter32, ifMauFalseCarriers Counter32, ifMauTypeList Integer32, ifMauDefaultType OBJECT IDENTIFIER, ifMauAutoNegSupported TruthValue, - ifMauTypeListBits BITS + ifMauTypeListBits BITS, + ifMauHCFalseCarriers Counter64 } ifMauIfIndex OBJECT-TYPE SYNTAX InterfaceIndex 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" + REFERENCE "RFC 2863, ifIndex" ::= { ifMauEntry 1 } ifMauIndex 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 interface (ifMauIfIndex)." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." @@ -1194,21 +1288,21 @@ 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 - mediaAvailable state is not one of 2 through 11. + mediaAvailable state is not one of 2 through 18. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. At power-up or following a reset, the value of this attribute will be unknown for AUI, coax, and 10BASE-FP MAUs. For these MAUs loopback will be tested on each transmission during which no collision is detected. If DI is receiving input when DO returns to IDL after a transmission and there @@ -1300,21 +1394,21 @@ DESCRIPTION "A count of the number of times that ifMauMediaAvailable for this MAU instance leaves the state available(3). Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, aLoseMediaCounter. - RFC 2233, ifCounterDiscontinuityTime." + RFC 2863, ifCounterDiscontinuityTime." ::= { ifMauEntry 6 } ifMauJabberState OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), noJabber(3), jabbering(4) } MAX-ACCESS read-only @@ -1345,46 +1439,52 @@ state jabbering(4). This counter will always indicate zero for MAUs of type dot1MauTypeAUI and those of speeds above 10Mbps. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, aJabber.jabberCounter. - RFC 2233, ifCounterDiscontinuityTime." + RFC 2863, ifCounterDiscontinuityTime." ::= { ifMauEntry 8 } ifMauFalseCarriers OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "A count of the number of false carrier events during IDLE in 100BASE-X and 1000BASE-X links. For all other MAU types, this counter will always indicate zero. 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 for 100BASE-X and once per 10us for 1000BASE-X until the next CarrierEvent. + This counter can roll over very quickly. A + management station is advised to poll the + ifMauHCFalseCarriers instead of this counter in + order to avoid loss of information. + Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. - RFC 2233, ifCounterDiscontinuityTime." + RFC 2863, ifCounterDiscontinuityTime." ::= { ifMauEntry 9 } + ifMauTypeList OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS deprecated DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 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 @@ -1535,20 +1634,46 @@ If auto-negotiation is present on this MAU, this object will map to ifMauAutoNegCapability. Note that this MAU may be capable of operating as a MAU type that is beyond the scope of this MIB. This is indicated by returning the bit value bOther in addition to any bit values for capabilities that are listed above." ::= { ifMauEntry 13 } + ifMauHCFalseCarriers OBJECT-TYPE + SYNTAX Counter64 + MAX-ACCESS read-only + STATUS current + DESCRIPTION "A count of the number of false carrier events + during IDLE in 100BASE-X and 1000BASE-X links. + + For all other MAU types, this counter will + always indicate zero. This counter does not + increment at the symbol rate. + + This counter is a 64 bit version of + ifMauFalseCarriers. Since the 32 bit version of + this counter can roll over very quickly, + management stations are advised to poll the + 64 bit version instead in order to avoid loss + of information. + + Discontinuities in the value of this counter can + occur at re-initialization of the management + system, and at other times as indicated by the + value of ifCounterDiscontinuityTime." + REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. + RFC 2863, ifCounterDiscontinuityTime." + ::= { ifMauEntry 14 } + -- The ifJackTable applies to MAUs attached to interfaces -- which have one or more external jacks (connectors). ifJackTable OBJECT-TYPE SYNTAX SEQUENCE OF IfJackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about the external jacks attached to MAUs attached to an interface." ::= { dot3IfMauBasicGroup 2 } @@ -2004,23 +2130,22 @@ broadMauIfIndex OBJECT-TYPE SYNTAX InterfaceIndex MAX-ACCESS read-only STATUS deprecated DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** This variable uniquely identifies the interface to which the MAU described by this entry is connected." - REFERENCE "Reference RFC 1213, ifIndex." + REFERENCE "Reference RFC 2863, ifIndex." ::= { broadMauBasicEntry 1 } - broadMauIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS deprecated DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** This variable uniquely identifies the MAU connected to interface broadMauIfIndex that is described by this entry." REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." @@ -2258,20 +2382,27 @@ mauIfGrpAutoNeg1000Mbps OBJECT-GROUP OBJECTS { ifMauAutoNegRemoteFaultAdvertised, ifMauAutoNegRemoteFaultReceived } STATUS current DESCRIPTION "Conformance group for 1000Mbps MAUs attached to interfaces with managed auto-negotiation." ::= { mauModObjGrps 11 } + mauIfGrpHCStats OBJECT-GROUP + OBJECTS { ifMauHCFalseCarriers } + STATUS current + DESCRIPTION "Conformance for high capacity statistics for + MAUs attached to interfaces" + ::= { mauModObjGrps 12 } + -- Notification groups rpMauNotifications NOTIFICATION-GROUP NOTIFICATIONS { rpMauJabberTrap } STATUS current DESCRIPTION "Notifications for repeater MAUs." ::= { mauModNotGrps 1 } ifMauNotifications NOTIFICATION-GROUP NOTIFICATIONS { ifMauJabberTrap } @@ -2340,22 +2472,24 @@ GROUP mauBroadBasic DESCRIPTION "Implementation of this group is mandatory for broadband MAUs." GROUP ifMauNotifications DESCRIPTION "Implementation of this group is recommended for MAUs attached to interfaces." ::= { mauModCompls 2 } mauModIfCompl2 MODULE-COMPLIANCE - STATUS current - DESCRIPTION "Compliance for MAUs attached to interfaces." + STATUS deprecated + DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** + + Compliance for MAUs attached to interfaces." MODULE -- this module MANDATORY-GROUPS { mauIfGrpBasic } GROUP mauIfGrpHighCapacity DESCRIPTION "Implementation of this optional group is recommended for MAUs which have 100Mb/s or greater capability." GROUP mauIfGrpJack @@ -2402,20 +2537,63 @@ GROUP rpMauNotifications DESCRIPTION "Implementation of this group is recommended for MAUs attached to repeater ports." OBJECT rpMauStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required." ::= { mauModCompls 4 } + mauModIfCompl3 MODULE-COMPLIANCE + STATUS current + DESCRIPTION "Compliance for MAUs attached to interfaces." + + MODULE -- this module + MANDATORY-GROUPS { mauIfGrpBasic } + + GROUP mauIfGrpHighCapacity + DESCRIPTION "Implementation of this optional group is + recommended for MAUs which have 100Mb/s + or greater capability." + + GROUP mauIfGrpHCStats + DESCRIPTION "Implemention of this group is mandatory + for MAUs which have 1000Mb/s capacity, and + is recommended for MAUs which have 100Mb/s + capacity." + + GROUP mauIfGrpJack + DESCRIPTION "Implementation of this optional group is + recommended for MAUs which have one or more + external jacks." + + GROUP mauIfGrpAutoNeg2 + DESCRIPTION "Implementation of this group is mandatory + for MAUs which support managed + auto-negotiation." + + GROUP mauIfGrpAutoNeg1000Mbps + DESCRIPTION "Implementation of this group is mandatory + for MAUs which have 1000Mb/s or greater + capability and support managed + auto-negotiation." + + GROUP ifMauNotifications + DESCRIPTION "Implementation of this group is recommended + for MAUs attached to interfaces." + + OBJECT ifMauStatus + MIN-ACCESS read-only + DESCRIPTION "Write access is not required." + ::= { mauModCompls 5 } + END 5. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the @@ -2432,141 +2610,160 @@ rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 6. Acknowledgements This document was produced by the IETF Ethernet Interfaces and Hub MIB Working Group, whose efforts were greatly advanced by the contributions of the following people: + Mike Ayers + Mike Heard Chuck Black John Flick Jeff Johnson + Kam Lam Leon Leong Mike Lui + Kerry McDonald + K.C. Norseth Dave Perkins + Dan Romascanu + Andrew Smith + Kaj Tesink Geoff Thompson Maurice Turcotte Paul Woodruff - Special thanks as well to Dave Perkins for his excellent work on the - SMICng compiler, which made it easy to take advantage of the latest - SNMPv2 constructs in this MIB. - 7. References - [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for - Describing SNMP Management Frameworks", RFC 2571, May 1999. + Normative References - [2] Rose, M. and K. McCloghrie, "Structure and Identification of - Management Information for TCP/IP-based Internets", STD 16, - RFC 1155, May 1990. + [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, + J., Rose, M. and S. Waldbusser, "Structure of Management + Information Version 2 (SMIv2)", STD 58, RFC 2578, April + 1999. - [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16, - RFC 1212, March 1991. + [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, + J., Rose, M. and S. Waldbusser, "Textual Conventions for + SMIv2", STD 58, RFC 2579, April 1999. - [4] Rose, M., "A Convention for Defining Traps for use with the - SNMP", RFC 1215, March 1991. + [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, + J., Rose, M. and S. Waldbusser, "Conformance Statements + for SMIv2", STD 58, RFC 2580, April 1999. - [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, - M. and S. Waldbusser, "Structure of Management Information - Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. + [IEEE802.3] IEEE, IEEE Std 802.3, 2000 Edition: "Information + technology - Telecommunications and information exchange + between systems - Local and metropolitan area networks - + Specific requirements - Part 3: Carrier sense multiple + access with collision detection (CSMA/CD) access method + and physical layer specifications", (Adopted by ISO/IEC + and redesignated as ISO/IEC 8802-3:2000(E), 2000. - [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, - M. and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, - RFC 2579, April 1999. + [P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, + IEEE Draft P802.3ae/D4.01, February 2002, work in + progress. - [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, - M. and S. Waldbusser, "Conformance Statements for SMIv2", STD - 58, RFC 2580, April 1999. + [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group + MIB using SMIv2", RFC 2863, June 2000. - [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple - Network Management Protocol", STD 15, RFC 1157, May 1990. + [RFC2108] de Graaf, K., D. Romascanu, D. McMaster, and K. + McCloghrie, "Definitions of Managed Objects for IEEE + 802.3 Repeater Devices using SMIv2", RFC 2108, February + 1997. - [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, - "Introduction to Community-based SNMPv2", RFC 1901, January - 1996. + [ETHERIF] Flick, J., "Definitions of Managed Objects for the + Ethernet-like Interface Types", work in progress, + draft-ietf-hubmib-etherif-mib-v3-01.txt, February, 2002. - [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport - Mappings for Version 2 of the Simple Network Management Protocol - (SNMPv2)", RFC 1906, January 1996. + Non-Normative References - [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message - Processing and Dispatching for the Simple Network Management - Protocol (SNMP)", RFC 2572, May 1999. + [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An + Architecture for Describing SNMP Management Frameworks", + RFC 2571, April 1999. - [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) - for version 3 of the Simple Network Management Protocol - (SNMPv3)", RFC 2574, May 1999. + [RFC1155] Rose, M. and K. McCloghrie, "Structure and + Identification of Management Information for + TCP/IP-based Internets", STD 16, RFC 1155, May 1990. - [13] 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. + [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", + STD 16, RFC 1212, March 1991. - [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC - 2573, May 1999. + [RFC1215] Rose, M., "A Convention for Defining Traps for use with + the SNMP", RFC 1215, March 1991. - [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access - Control Model (VACM) for the Simple Network Management Protocol - (SNMP)", RFC 2575, May 1999. + [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, + "Simple Network Management Protocol", STD 15, RFC 1157, + May 1990. - [16] Case, J., Mundy, R., Partain, D. and B. Stewart, - "Introduction to Version 3 of the Internet-Standard Network - Management Framework", RFC 2570, April 1999. + [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, + "Introduction to Community-based SNMPv2", RFC 1901, + January 1996. - [17] IEEE, IEEE Std 802.3, 2000 Edition: "Information technology - - Telecommunications and information exchange between systems - - Local and metropolitan area networks - Specific requirements - - Part 3: Carrier sense multiple access with collision detection - (CSMA/CD) access method and physical layer specifications", - (Adopted by ISO/IEC and redesignated as ISO/IEC 8802-3:2000(E), - 2000. + [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, + "Transport Mappings for Version 2 of the Simple Network + Management Protocol (SNMPv2)", RFC 1906, January 1996. - [18] IEEE, IEEE Draft P802.3ae/D3.0: "Supplement to Carrier Sense - Multiple Access with Collision Detection (CSMA/CD) Access - Method & Physical Layer Specifications - Media Access Control - (MAC) Parameters, Physical Layer, and Management Parameters - for 10 Gb/s Operation", March 2001. + [RFC2572] Case, J., Harrington, D., Presuhn R. and B. Wijnen, + "Message Processing and Dispatching for the Simple + Network Management Protocol (SNMP)", RFC 2572, May 1999. - [19] de Graaf, K., D. Romascanu, D. McMaster, and K. McCloghrie, - "Definitions of Managed Objects for IEEE 802.3 Repeater Devices - using SMIv2", RFC 2108, February 1997. + [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model + (USM) for version 3 of the Simple Network Management + Protocol (SNMPv3)", RFC 2574, May 1999. - [20] McCloghrie, K. and M. Rose, Editors, "Management Information - Base for Network Management of TCP/IP-based internets: MIB-II", - STD 17, RFC 1213, March 1991. + [RFC1905] 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. - [21] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB - using SMIv2", RFC 2863, June 2000. + [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 + Applications", RFC 2573, May 1999. - [22] Bradner, S., "Key words for use in RFCs to Indicate + [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based + Access Control Model (VACM) for the Simple Network + Management Protocol (SNMP)", RFC 2575, May 1999. + + [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, + "Introduction to Version 3 of the Internet-Standard + Network Management Framework", RFC 2570, April 1999. + + [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997. - [23] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster, D., - McCloghrie, K. and S. Roberts, "Definitions of Managed Objects - for IEEE 802.3 Medium Attachment Units (MAUs)", RFC 2668, August - 1999. + [RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, + "Management Information Base for Version 2 of the + Simple Network Management Protocol (SNMPv2)", RFC 1907, + January 1996. - [24] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K. and S. - Roberts, "Definitions of Managed Objects for IEEE 802.3 Medium - Attachment Units (MAUs) using SMIv2", RFC 2239, November 1997. + [RFC2668] Smith, A., Flick, J., deGraaf, K., Romascanu, D., + McMaster, D., McCloghrie, K. and S. Roberts, + "Definitions of Managed Objects for IEEE 802.3 Medium + Attachment Units (MAUs)", RFC 2668, August 1999. - [25] McMaster, D., McCloghrie, K. and S. Roberts, "Definitions of - Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)", - RFC 1515, September 1993. + [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, + K. and S. Roberts, "Definitions of Managed Objects for + IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", + RFC 2239, November 1997. - [26] Flick, J., and J. Johnson, "Definitions of Managed Objects for - the Ethernet-like Interface Types", work in progress, - draft-ietf-hubmib-etherif-mib-v3-00.txt, June, 2001. + [RFC1515] McMaster, D., McCloghrie, K. and S. Roberts, + "Definitions of Managed Objects for IEEE 802.3 Medium + Attachment Units (MAUs)", RFC 1515, September 1993. + + [ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald, + K., Norseth, K. C., and K. Tesink, "Definitions of + Managed Objects for the Ethernet WAN Interface + Sublayer", work in progress, + draft-ietf-hubmib-wis-mib-02.txt, February 2002. 8. Security Considerations + There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write. Setting these objects can have a serious effect on the operation of the network, including: enabling or disabling a MAU changing a MAU's default type enabling, disabling or restarting autonegotiation modifying the capabilities that a MAU advertizes during autonegotiation. @@ -2576,22 +2773,22 @@ network operations. SNMPv1 by itself is such an insecure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use - of the User-based Security Model RFC 2574 [12] and the View-based - Access Control Model RFC 2575 [15] is recommended. + of the User-based Security Model RFC 2574 [RFC2574] and the View- + based Access Control Model RFC 2575 [RFC2575] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, is properly configured to give access to those objects only to those principals (users) that have legitimate rights to access them. 9. Authors' Addresses John Flick Hewlett-Packard Company @@ -2628,20 +2824,26 @@ (7) ifMauTypeListBits has been extended with bits for the 10 Gb/s MAU types. (8) The MODULE-IDENTITY clause has been updated to reflect the changes in the MIB module. (9) MIB boilerplate in section 2 has been updated to the latest approved text. + (10) Added 64-bit version of ifMauFalseCarriers, and updated + compliances accordingly. + + (11) Added section on mapping of IEEE managed objects to the + objects in this MIB module. + A.2. Changes between RFC 2239 and RFC 2668 This section enumerates the changes made to RFC 2239 to produce RFC 2668. (1) The MODULE-IDENTITY has been updated to reflect the changes in the MIB. (2) OBJECT-IDENTITY definitions have been added for gigabit MAU types. @@ -2680,21 +2882,21 @@ (12) Refer to the Interfaces MIB, rather than the interfaces group of MIB-II. (13) Updated references to refer to latest edition of IEEE 802.3. (14) An intellectual property notice was added, as required by RFC 2026. B. Full Copyright Statement - Copyright (C) The Internet Society (2001). All Rights Reserved. + Copyright (C) The Internet Society (2002). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of