idnits 2.17.1 draft-ietf-hubmib-etherif-mib-v2-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. -- The abstract seems to indicate that this document obsoletes RFC2358, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 523 has weird spacing: '...issions dot...' == Line 529 has weird spacing: '...cvError dot3S...' == Line 553 has weird spacing: '...pported dot3...' == Line 559 has weird spacing: '...smitted dot3O...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (January 1999) is 9231 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '15') (Obsoleted by RFC 2575) -- Possible downref: Non-RFC (?) normative reference: ref. '16' -- Possible downref: Non-RFC (?) normative reference: ref. '17' ** Obsolete normative reference: RFC 1284 (ref. '18') (Obsoleted by RFC 1398) ** Downref: Normative reference to an Informational RFC: RFC 1369 (ref. '19') ** Obsolete normative reference: RFC 1398 (ref. '20') (Obsoleted by RFC 1623) ** Obsolete normative reference: RFC 1643 (ref. '21') (Obsoleted by RFC 3638) ** Obsolete normative reference: RFC 1650 (ref. '22') (Obsoleted by RFC 2358) ** Obsolete normative reference: RFC 2358 (ref. '23') (Obsoleted by RFC 2665) ** Obsolete normative reference: RFC 2233 (ref. '25') (Obsoleted by RFC 2863) == Outdated reference: A later version (-04) exists of draft-ietf-hubmib-mau-mib-v2-02 == Outdated reference: A later version (-02) exists of draft-ietf-hubmib-ether-chipsets-00 ** Downref: Normative reference to an Informational draft: draft-ietf-hubmib-ether-chipsets (ref. '28') Summary: 29 errors (**), 0 flaws (~~), 9 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Hub MIB Working Group J. Flick 3 INTERNET DRAFT Hewlett-Packard Company 4 J. Johnson 5 RedBack Networks 6 January 1999 8 Definitions of Managed Objects for 9 the Ethernet-like Interface Types 11 13 Status of this Memo 15 This document is an Internet-Draft. Internet-Drafts are working 16 documents of the Internet Engineering Task Force (IETF), its areas, 17 and its working groups. Note that other groups may also distribute 18 working documents as Internet-Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet- Drafts as reference 23 material or to cite them other than as "work in progress." 25 To view the list Internet-Draft Shadow Directories, see 26 http://www.ietf.org/shadow.html. 28 Copyright Notice 30 Copyright (C) The Internet Society (1999). All Rights Reserved. 32 Abstract 34 This memo defines a portion of the Management Information Base (MIB) 35 for use with network management protocols in the Internet community. 36 This memo obsoletes RFC 2358 ''Definitions of Managed Objects for the 37 Ethernet-like Interface Types''. This memo extends that 38 specification by including management information useful for the 39 management of 1000 Mb/s and full-duplex Ethernet interfaces. 41 Ethernet technology, as defined by the 802.3 Working Group of the 42 IEEE, continues to evolve, with scalable increases in speed, new 43 types of cabling and interfaces, and new features. This evolution 44 may require changes in the managed objects in order to reflect this 45 new functionality. This document, as with other documents issued by 46 this working group, reflects a certain stage in the evolution of 47 Ethernet technology. In the future, this document might be revised, 48 or new documents might be issued by the Ethernet Interfaces and Hub 49 MIB Working Group, in order to reflect the evolution of Ethernet 50 technology. 52 Distribution of this memo is unlimited. Please forward comments to 53 hubmib@hprnd.rose.hp.com. 55 Table of Contents 57 1. Introduction ................................................ 2 58 2. The SNMP Management Framework .............................. 3 59 3. Overview ................................................... 4 60 3.1. Relation to MIB-2 ........................................ 4 61 3.2. Relation to the Interfaces MIB ........................... 5 62 3.2.1. Layering Model ......................................... 5 63 3.2.2. Virtual Circuits ....................................... 5 64 3.2.3. ifTestTable ............................................ 5 65 3.2.4. ifRcvAddressTable ...................................... 6 66 3.2.5. ifPhysAddress .......................................... 6 67 3.2.6. ifType ................................................. 6 68 3.2.7. Specific Interface MIB Objects ......................... 7 69 3.3. Relation to the 802.3 MAU MIB ............................ 10 70 3.4. dot3StatsEtherChipSet .................................... 11 71 3.5. Mapping of IEEE 802.3 Managed Objects .................... 11 72 4. Definitions ................................................ 14 73 5. Intellectual Property ...................................... 36 74 6. Acknowledgements ........................................... 36 75 7. References ................................................. 37 76 8. Security Considerations .................................... 40 77 9. Author's Addresses ......................................... 41 78 A. Change Log ................................................. 41 79 A.1. Changes since RFC 2358 ................................... 41 80 A.2. Changes between RFC 1650 and RFC 2358 .................... 42 81 B. Full Copyright Statement ................................... 43 83 1. Introduction 85 This memo defines a portion of the Management Information Base (MIB) 86 for use with network management protocols in the Internet community. 87 In particular, it defines objects for managing Ethernet-like 88 interfaces. 90 This memo also includes a MIB module. This MIB module extends the 91 list of managed objects specified in the earlier version of this MIB: 92 RFC 2358 [23]. 94 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 95 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 96 document are to be interpreted as described in [26]. 98 2. The SNMP Management Framework 100 The SNMP Management Framework presently consists of five major 101 components: 103 o An overall architecture, described in RFC 2271 [1]. 105 o Mechanisms for describing and naming objects and events for the 106 purpose of management. The first version of this Structure of 107 Management Information (SMI) is called SMIv1 and described in 108 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 109 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 110 1904 [7]. 112 o Message protocols for transferring management information. The 113 first version of the SNMP message protocol is called SNMPv1 and 114 described in RFC 1157 [8]. A second version of the SNMP message 115 protocol, which is not an Internet standards track protocol, is 116 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 117 The third version of the message protocol is called SNMPv3 and 118 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 120 o Protocol operations for accessing management information. The 121 first set of protocol operations and associated PDU formats is 122 described in RFC 1157 [8]. A second set of protocol operations 123 and associated PDU formats is described in RFC 1905 [13]. 125 o A set of fundamental applications described in RFC 2273 [14] and 126 the view-based access control mechanism described in RFC 2275 127 [15]. 129 Managed objects are accessed via a virtual information store, termed 130 the Management Information Base or MIB. Objects in the MIB are 131 defined using the mechanisms defined in the SMI. 133 This memo specifies a MIB module that is compliant to the SMIv2. A 134 MIB conforming to the SMIv1 can be produced through the appropriate 135 translations. The resulting translated MIB must be semantically 136 equivalent, except where objects or events are omitted because no 137 translation is possible (use of Counter64). Some machine readable 138 information in SMIv2 will be converted into textual descriptions in 139 SMIv1 during the translation process. However, this loss of machine 140 readable information is not considered to change the semantics of the 141 MIB. 143 3. Overview 145 Instances of these object types represent attributes of an interface 146 to an ethernet-like communications medium. At present, ethernet-like 147 media are identified by the following values of the ifType object in 148 the Interfaces MIB [25]: 150 ethernetCsmacd(6) 151 iso88023Csmacd(7) 152 starLan(11) 154 The definitions presented here are based on Section 30, "10 Mb/s, 100 155 Mb/s and 1000 Mb/s Management", and Annex 30A, "GDMO Specification 156 for 802.3 managed object classes" of IEEE Std. 802.3, 1998 Edition 157 [16], as originally interpreted by Frank Kastenholz then of Interlan 158 in [17]. Implementors of these MIB objects should note that IEEE 159 Std. 802.3 [16] explicitly describes (in the form of Pascal 160 pseudocode) when, where, and how various MAC attributes are measured. 161 The IEEE document also describes the effects of MAC actions that may 162 be invoked by manipulating instances of the MIB objects defined here. 164 To the extent that some of the attributes defined in [16] are 165 represented by previously defined objects in MIB-2 [24] or in the 166 Interfaces MIB [25], such attributes are not redundantly represented 167 by objects defined in this memo. Among the attributes represented by 168 objects defined in other memos are the number of octets transmitted 169 or received on a particular interface, the number of frames 170 transmitted or received on a particular interface, the promiscuous 171 status of an interface, the MAC address of an interface, and 172 multicast information associated with an interface. 174 3.1. Relation to MIB-2 176 This section applies only when this MIB is used in conjunction with 177 the "old" (RFC 1213) [24] interface group. 179 The relationship between an ethernet-like interface and an interface 180 in the context of MIB-2 is one-to-one. As such, the value of an 181 ifIndex object instance can be directly used to identify 182 corresponding instances of the objects defined herein. 184 For agents which implement the (now deprecated) ifSpecific object, an 185 instance of that object that is associated with an ethernet-like 186 interface has the OBJECT IDENTIFIER value: 188 dot3 OBJECT IDENTIFER ::= { transmission 7 } 190 3.2. Relation to the Interfaces MIB 192 The Interface MIB [25] requires that any MIB which is an adjunct of 193 the Interface MIB clarify specific areas within the Interface MIB. 194 These areas were intentionally left vague in the Interface MIB to 195 avoid over constraining the MIB, thereby precluding management of 196 certain media-types. 198 Section 3.3 of [25] enumerates several areas which a media-specific 199 MIB must clarify. Each of these areas is addressed in a following 200 subsection. The implementor is referred to [25] in order to 201 understand the general intent of these areas. 203 3.2.1. Layering Model 205 This MIB does not provide for layering. There are no sublayers. 207 EDITOR'S NOTE: 209 One could foresee the development of an 802.2 and enet-transceiver 210 MIB. They could be higher and lower sublayers, respectively. All 211 that THIS document should do is allude to the possibilities and urge 212 the implementor to be aware of the possibility and that they may have 213 requirements which supersede the requirements in this document. 215 3.2.2. Virtual Circuits 217 This medium does not support virtual circuits and this area is not 218 applicable to this MIB. 220 3.2.3. ifTestTable 222 This MIB defines two tests for media which are instrumented with this 223 MIB; TDR and Loopback. Implementation of these tests is not 224 required. Many common interface chips do not support one or both of 225 these tests. 227 These two tests are provided as a convenience, allowing a common 228 method to invoke the test. 230 Standard MIBs do not include objects in which to return the results 231 of the TDR test. Any needed objects MUST be provided in the vendor 232 specific MIB. 234 Note that the ifTestTable is now deprecated. Work is underway to 235 define a replacement MIB for system and interface testing. It is 236 expected that the tests defined in this document will be usable in 237 this replacement MIB. 239 3.2.4. ifRcvAddressTable 241 This table contains all IEEE 802.3 addresses, unicast, multicast, and 242 broadcast, for which this interface will receive packets and forward 243 them up to a higher layer entity for local consumption. The format 244 of the address, contained in ifRcvAddressAddress, is the same as for 245 ifPhysAddress. 247 In the event that the interface is part of a MAC bridge, this table 248 does not include unicast addresses which are accepted for possible 249 forwarding out some other port. This table is explicitly not 250 intended to provide a bridge address filtering mechanism. 252 3.2.5. ifPhysAddress 254 This object contains the IEEE 802.3 address which is placed in the 255 source-address field of any Ethernet, Starlan, or IEEE 802.3 frames 256 that originate at this interface. Usually this will be kept in ROM 257 on the interface hardware. Some systems may set this address via 258 software. 260 In a system where there are several such addresses the designer has a 261 tougher choice. The address chosen should be the one most likely to 262 be of use to network management (e.g. the address placed in ARP 263 responses for systems which are primarily IP systems). 265 If the designer truly can not chose, use of the factory- provided ROM 266 address is suggested. 268 If the address can not be determined, an octet string of zero length 269 should be returned. 271 The address is stored in binary in this object. The address is 272 stored in "canonical" bit order, that is, the Group Bit is positioned 273 as the low-order bit of the first octet. Thus, the first byte of a 274 multicast address would have the bit 0x01 set. 276 3.2.6. ifType 278 This MIB applies to interfaces which have any of the following ifType 279 values: 281 ethernetCsmacd(6) 282 iso88023Csmacd(7) 283 starLan(11) 285 It is RECOMMENDED that all Ethernet-like interfaces use an ifType of 286 ethernetCsmacd(6) regardless of the speed that the interface is 287 running or the link-layer encapsulation in use. iso88023Csmacd(7) 288 and starLan(11) are supported for backwards compatability. 290 There are three other interface types defined in the IANAifType-MIB 291 for Ethernet. They are fastEther(62), fastEtherFX(69), and 292 gigabitEthernet(117). This document takes the position that an 293 Ethernet is an Ethernet, and Ethernet interfaces SHOULD always have 294 the same value of ifType. Information on the particular flavor of 295 Ethernet that an interface is running is available from ifSpeed in 296 the Interfaces MIB, and ifMauType in the 802.3 MAU MIB. An 297 Ethernet-like interface SHOULD NOT use the fastEther(62), 298 fastEtherFX(69), or gigabitEthernet(117) ifTypes. 300 Interfaces with any of the supported ifType values map to the 301 EtherLike-MIB in the same manner. There are no implementation 302 differences. 304 3.2.7. Specific Interface MIB Objects 306 The following table provides specific implementation guidelines for 307 applying the interface group objects to ethernet-like media. 309 Object 311 ifIndex Each ethernet-like interface is 312 represented by an ifEntry. The 313 dot3StatsTable in this MIB module is 314 indexed by dot3StatsIndex. The interface 315 identified by a particular value of 316 dot3StatsIndex is the same interface as 317 identified by the same value of ifIndex. 319 ifDescr Refer to [25]. 321 ifType Refer to section 3.2.6. 323 ifMtu 1500 octets. NOTE: This is the MTU as 324 seen by the MAC client. When a higher 325 layer protocol, like IP, is running over 326 Ethernet, this is the MTU that will be 327 seen by that higher layer protocol. 329 However, when using the IEEE 802.2 LLC 330 protocol, higher layer protocols will 331 see a different MTU. In particular, an 332 LLC type 1 client protocol will see 333 an MTU of 1497 octets, and a protocol 334 running over SNAP will see an MTU of 335 1492 octets. 337 ifSpeed The current operational speed of the 338 interface in bits per second. For 339 current ethernet-like interfaces, this 340 will be equal to 1,000,000 (1 million), 341 10,000,000 (10 million), 100,000,000 342 (100 million), or 1,000,000,000 (1 343 billion). If the interface implements 344 auto-negotiation, auto-negotiation is 345 enabled for this interface, and the 346 interface has not yet negotiated to an 347 operational speed, this object SHOULD 348 reflect the maximum speed supported by 349 the interface. Note that this object 350 MUST NOT indicate a doubled value when 351 operating in full-duplex mode. It MUST 352 indicate the correct line speed 353 regardless of the current duplex mode. 354 The duplex mode of the interface may 355 be determined by examining either the 356 dot3StatsDuplexStatus object in this 357 MIBmodule, or the ifMauType object in 358 the 802.3 MAU MIB. 360 ifPhysAddress Refer to section 3.2.5. 362 ifAdminStatus Write access is not required. Support 363 for 'testing' is not required. 365 ifOperStatus The operational state of the interface. 366 Support for 'testing' is not required. 367 The value 'dormant' has no meaning for 368 an ethernet-like interface. 370 ifLastChange Refer to [25]. 372 ifInOctets The number of octets in valid MAC frames 373 received on this interface, including 374 the MAC header and FCS. 376 ifInUcastPkts Refer to [25]. 378 ifInDiscards Refer to [25]. 380 ifInErrors The sum for this interface of 381 dot3StatsAlignmentErrors, 382 dot3StatsFCSErrors, 383 dot3StatsFrameTooLongs, 384 dot3StatsInternalMacReceiveErrors and 385 dot3StatsSymbolErrors. 387 ifInUnknownProtos Refer to [25]. 389 ifOutOctets The number of octets transmitted in 390 valid MAC frames on this interface, 391 including the MAC header and FCS. 393 ifOutUcastPkts Refer to [25]. 395 ifOutDiscards Refer to [25]. 397 ifOutErrors The sum for this interface of: 398 dot3StatsSQETestErrors, 399 dot3StatsLateCollisions, 400 dot3StatsExcessiveCollisions, 401 dot3StatsInternalMacTransmitErrors and 402 dot3StatsCarrierSenseErrors. 404 ifName Locally-significant textual name for the 405 interface (e.g. lan0). 407 ifInMulticastPkts Refer to [25]. 409 ifInBroadcastPkts Refer to [25]. 411 ifOutMulticastPkts Refer to [25]. 413 ifOutBroadcastPkts Refer to [25]. 415 ifHCInOctets 64-bit versions of counters. Required 416 ifHCOutOctets for ethernet-like interfaces that are 417 capable of operating at 20Mbit/sec or 418 faster, even if the interface is 419 currently operating at less than 420 20Mbit/sec. 422 ifHCInUcastPkts 64-bit versions of packet counters. 423 ifHCInMulticastPkts Required for ethernet-like interfaces 424 ifHCInBroadcastPkts that are capable of operating at 425 ifHCOutUcastPkts 640Mbit/sec or faster, even if the 426 ifHCOutMulticastPkts interface is currently operating at 427 ifHCOutBroadcastPkts less than 640Mbit/sec. 429 ifLinkUpDownTrapEnable Refer to [25]. Default is 'enabled' 431 ifHighSpeed The current operational speed of the 432 interface in millions of bits per 433 second. For current ethernet-like 434 interfaces, this will be equal to 1, 10, 435 100, or 1,000. If the interface 436 implements auto-negotiation, 437 auto-negotiation is enabled for this 438 interface, and the interface has not yet 439 negotiated to an operational speed, this 440 object SHOULD reflect the maximum speed 441 supported by the interface. Note that 442 this object MUST NOT indicate a doubled 443 value when operating in full-duplex 444 mode. It MUST indicate the correct line 445 speed regardless of the current duplex 446 mode. The duplex mode of the interface 447 may be determined by examining either 448 the dot3StatsDuplexStatus object in this 449 MIB module, or the ifMauType object in 450 the 802.3 MAU MIB. 452 ifPromiscuousMode Refer to [25]. 454 ifConnectorPresent This will normally be 'true'. 456 ifAlias Refer to [25]. 458 ifCounterDiscontinuityTime Refer to [25]. 460 ifStackHigherLayer Refer to section 3.2.1. 461 ifStackLowerLayer 462 ifStackStatus 464 ifRcvAddressAddress Refer to section 3.2.4. 465 ifRcvAddressStatus 466 ifRcvAddressType 468 3.3. Relation to the 802.3 MAU MIB 470 Support for the mauModIfCompl2 compliance statement of the MAU-MIB 471 [27] is REQUIRED for Ethernet-like interfaces. This MIB is needed in 472 order to allow applications to determine the current MAU type in use 473 by the interface, and to control autonegotiation and duplex mode for 474 the interface. Implementing this MIB module without implementing the 475 MAU-MIB would leave applications with no standard way to determine 476 the media type in use, and no standard way to control the duplex mode 477 of the interface. 479 3.4. dot3StatsEtherChipSet 481 This document defines an object called dot3StatsEtherChipSet, which 482 is used to identify the MAC hardware used to communicate on an 483 interface. Previous versions of this document contained a number of 484 OID assignments for some existing Ethernet chipsets. Maintaining 485 that list as part of this document has proven to be problematic, so 486 the OID assignments contained in prevous versions of this document 487 have now been moved to a separate document [28]. 489 The dot3StatsEtherChipSet object has now been deprecated. 490 Implementation feedback indicates that this object is much more 491 useful in theory than in practice. The object's utility in debugging 492 network problems in the field appears to be limited. In those cases 493 where it may be useful, it is not sufficient, since it identifies 494 only the MAC chip, and not the PHY, PMD, or driver. The 495 administrative overhead involved in maintaining a central registry of 496 chipset OIDs cannot be justified for an object whose usefulness is 497 questionable at best. 499 Implementations which continue to support this object for the purpose 500 of backwards compatability may continue to use the values defined in 501 [28]. For chipsets not listed in [28], implementors should assign 502 OBJECT IDENTIFIERS within that part of the registration tree 503 delegated to individual enterprises. 505 3.5. Mapping of IEEE 802.3 Managed Objects 507 IEEE 802.3 Managed Object Corresponding SNMP Object 509 oMacEntity 510 .aMACID dot3StatsIndex or 511 IF-MIB - ifIndex 512 .aFramesTransmittedOK IF-MIB - ifOutUCastPkts + 513 ifOutMulticastPkts + 514 ifOutBroadcastPkts 515 .aSingleCollisionFrames dot3StatsSingleCollisionFrames 516 .aMultipleCollisionFrames dot3StatsMultipleCollisionFrames 517 .aFramesReceivedOK IF-MIB - ifInUcastPkts + 518 ifInMulticastPkts + 519 ifInBroadcastPkts 520 .aFrameCheckSequenceErrors dot3StatsFCSErrors 521 .aAlignmentErrors dot3StatsAlignmentErrors 522 .aOctetsTransmittedOK IF-MIB - ifOutOctets* 523 .aFramesWithDeferredXmissions dot3StatsDeferredTransmissions 524 .aLateCollisions dot3StatsLateCollisions 525 .aFramesAbortedDueToXSColls dot3StatsExcessiveCollisions 526 .aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors 527 .aCarrierSenseErrors dot3StatsCarrierSenseErrors 528 .aOctetsReceivedOK IF-MIB - ifInOctets* 529 .aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors 530 .aPromiscuousStatus IF-MIB - ifPromiscuousMode 531 .aReadMulticastAddressList IF-MIB - ifRcvAddressTable 532 .aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts 533 .aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts 534 .aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts 535 .aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts 536 .aFrameTooLongErrors dot3StatsFrameTooLongs 537 .aReadWriteMACAddress IF-MIB - ifPhysAddress 538 .aCollisionFrames dot3CollFrequencies 539 .aDuplexStatus dot3StatsDuplexStatus 540 .acAddGroupAddress IF-MIB - ifRcvAddressTable 541 .acDeleteGroupAddress IF-MIB - ifRcvAddressTable 542 .acExecuteSelfTest dot3TestLoopBack 544 oPHYEntity 545 .aPHYID dot3StatsIndex or 546 IF-MIB - ifIndex 547 .aSQETestErrors dot3StatsSQETestErrors 548 .aSymbolErrorDuringCarrier dot3StatsSymbolErrors 550 oMACControlEntity 551 .aMACControlID dot3StatsIndex or 552 IF-MIB - ifIndex 553 .aMACControlFunctionsSupported dot3ControlFunctionsSupported and 554 dot3ControlFunctionsEnabled 555 .aUnsupportedOpcodesReceived dot3ControlInUnknownOpcodes 557 oPAUSEEntity 558 .aPAUSELinkDelayAllowance dot3PauseLinkDelayAllowance 559 .aPAUSEMACCtrlFramesTransmitted dot3OutPauseFrames 560 .aPAUSEMACCtrlFramesReceived dot3InPauseFrames 562 * Note that the octet counters in IF-MIB do not exactly match the 563 definition of the octet counters in IEEE 802.3. aOctetsTransmittedOK 564 and aOctetsReceivedOK count only the octets in the clientData and Pad 565 fields, whereas ifInOctets and ifOutOctets include the entire MAC 566 frame, including MAC header and FCS. However, the IF-MIB counters 567 can be derived from the IEEE 802.3 counters as follows: 569 ifInOctets = aOctetsReceivedOK + (18 * aFramesReceivedOK) 570 ifOutOctets = aOctetsTransmittedOK + (18 * aFramesTransmittedOK) 572 The following IEEE 802.3 managed objects have been removed from this 573 MIB module as a result of implementation feedback: 575 oMacEntity 576 .aFramesWithExcessiveDeferral 577 .aInRangeLengthErrors 578 .aOutOfRangeLengthField 579 .aMACEnableStatus 580 .aTransmitEnableStatus 581 .aMulticastReceiveStatus 582 .acInitializeMAC 584 Please see [19] for the detailed reasoning on why these objects were 585 removed. 587 In addition, the following IEEE 802.3 managed objects have not been 588 included in this MIB for the following reasons. 590 IEEE 802.3 Managed Object Disposition 592 oMACEntity 593 .aMACCapabilities Can be derived from 594 MAU-MIB - ifMauTypeListBits 596 oPHYEntity 597 .aPhyType Can be derived from 598 MAU-MIB - ifMauType 600 .aPhyTypeList Can be derived from 601 MAU-MIB - ifMauTypeListBits 603 .aMIIDetect Not considered useful. 605 .aPhyAdminState Can already obtain interface 606 state from IF-MIB - ifOperStatus 607 and MAU state from MAU-MIB - 608 ifMauStatus. Providing an 609 additional state for the PHY 610 was not considered useful. 612 .acPhyAdminControl Can already control interface 613 state from IF-MIB - ifAdminStatus 614 and MAU state from MAU-MIB - 615 ifMauStatus. Providing separate 616 admin control of the PHY was not 617 considered useful. 619 oMACControlEntity 620 .aMACControlFramesTransmitted Can be determined by summing the 621 OutFrames counters for the 622 individual control functions 624 .aMACControlFramesReceived Can be determined by summing the 625 InFrames counters for the 626 individual control functions 628 4. Definitions 630 EtherLike-MIB DEFINITIONS ::= BEGIN 632 IMPORTS 633 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, 634 Counter32, Unsigned32, mib-2, transmission 635 FROM SNMPv2-SMI 636 MODULE-COMPLIANCE, OBJECT-GROUP 637 FROM SNMPv2-CONF 638 ifIndex, InterfaceIndex 639 FROM IF-MIB; 641 etherMIB MODULE-IDENTITY 642 LAST-UPDATED "9901280031Z" -- January 28, 1999 643 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 644 Working Group" 645 CONTACT-INFO 646 "WG E-mail: hubmib@hprnd.rose.hp.com 647 To subscribe: hubmib-request@hprnd.rose.hp.com 649 Chair: Dan Romascanu 650 Postal: Lucent Technologies 651 Atidum Technology Park, Bldg. 3 652 Tel Aviv 61131 653 Israel 654 Tel: +972 3 645 8414 655 E-mail: dromasca@lucent.com 657 Editor: John Flick 658 Postal: Hewlett-Packard Company 659 8000 Foothills Blvd. M/S 5557 660 Roseville, CA 95747-5557 661 USA 663 Tel: +1 916 785 4018 664 Fax: +1 916 785 1199 665 E-mail: johnf@rose.hp.com 667 Editor: Jeffrey Johnson 668 Postal: RedBack Networks 669 2570 North First Street, Suite 410 670 San Jose, CA, 95131 671 USA 672 Tel: +1 408 571 2699 673 Fax: +1 408 571 2698 674 E-Mail: jeff@redbacknetworks.com" 676 DESCRIPTION "The MIB module to describe generic objects for 677 Ethernet-like network interfaces. 679 The following reference is used throughout this 680 MIB module: 682 [IEEE 802.3 Std] refers to: 683 IEEE Std 802.3, 1998 Edition: 'Information 684 technology - Telecommunications and 685 information exchange between systems - 686 Local and metropolitan area networks - 687 Specific requirements - Part 3: Carrier 688 sense multiple access with collision 689 detection (CSMA/CD) access method and 690 physical layer specifications', 691 September 1998. 693 Of particular interest is Clause 30, '10Mb/s, 694 100Mb/s and 1000Mb/s Management'." 696 REVISION "9901280031Z" -- January 28, 1999 697 DESCRIPTION "Updated to include support for 1000 Mb/sec 698 interfaces and full-duplex interfaces." 700 REVISION "9806032150Z" -- June 3, 1998 701 DESCRIPTION "Updated to include support for 100 Mb/sec 702 interfaces. Published as RFC 2358." 704 REVISION "9402030400Z" -- February 3, 1994 705 DESCRIPTION "Version published as RFC 1650." 706 ::= { mib-2 35 } 708 etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 } 710 dot3 OBJECT IDENTIFIER ::= { transmission 7 } 711 -- the Ethernet-like Statistics group 713 dot3StatsTable OBJECT-TYPE 714 SYNTAX SEQUENCE OF Dot3StatsEntry 715 MAX-ACCESS not-accessible 716 STATUS current 717 DESCRIPTION "Statistics for a collection of ethernet-like 718 interfaces attached to a particular system." 719 ::= { dot3 2 } 721 dot3StatsEntry OBJECT-TYPE 722 SYNTAX Dot3StatsEntry 723 MAX-ACCESS not-accessible 724 STATUS current 725 DESCRIPTION "Statistics for a particular interface to an 726 ethernet-like medium." 727 INDEX { dot3StatsIndex } 728 ::= { dot3StatsTable 1 } 730 Dot3StatsEntry ::= 731 SEQUENCE { 732 dot3StatsIndex InterfaceIndex, 733 dot3StatsAlignmentErrors Counter32, 734 dot3StatsFCSErrors Counter32, 735 dot3StatsSingleCollisionFrames Counter32, 736 dot3StatsMultipleCollisionFrames Counter32, 737 dot3StatsSQETestErrors Counter32, 738 dot3StatsDeferredTransmissions Counter32, 739 dot3StatsLateCollisions Counter32, 740 dot3StatsExcessiveCollisions Counter32, 741 dot3StatsInternalMacTransmitErrors Counter32, 742 dot3StatsCarrierSenseErrors Counter32, 743 dot3StatsFrameTooLongs Counter32, 744 dot3StatsInternalMacReceiveErrors Counter32, 745 dot3StatsEtherChipSet OBJECT IDENTIFIER, 746 dot3StatsSymbolErrors Counter32, 747 dot3StatsDuplexStatus INTEGER 748 } 750 dot3StatsIndex OBJECT-TYPE 751 SYNTAX InterfaceIndex 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION "An index value that uniquely identifies an 755 interface to an ethernet-like medium. The 756 interface identified by a particular value of 757 this index is the same interface as identified 758 by the same value of ifIndex." 760 REFERENCE "RFC 2233, ifIndex" 761 ::= { dot3StatsEntry 1 } 763 dot3StatsAlignmentErrors OBJECT-TYPE 764 SYNTAX Counter32 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION "A count of frames received on a particular 768 interface that are not an integral number of 769 octets in length and do not pass the FCS check. 771 The count represented by an instance of this 772 object is incremented when the alignmentError 773 status is returned by the MAC service to the 774 LLC (or other MAC user). Received frames for 775 which multiple error conditions obtain are, 776 according to the conventions of IEEE 802.3 777 Layer Management, counted exclusively according 778 to the error status presented to the LLC. 780 This counter does not increment for 8-bit wide 781 group encoding schemes." 782 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7, 783 aAlignmentErrors" 784 ::= { dot3StatsEntry 2 } 786 dot3StatsFCSErrors OBJECT-TYPE 787 SYNTAX Counter32 788 MAX-ACCESS read-only 789 STATUS current 790 DESCRIPTION "A count of frames received on a particular 791 interface that are an integral number of octets 792 in length but do not pass the FCS check. This 793 count does not include frames received with 794 frame-too-long or frame-too-short error. 796 The count represented by an instance of this 797 object is incremented when the frameCheckError 798 status is returned by the MAC service to the 799 LLC (or other MAC user). Received frames for 800 which multiple error conditions obtain are, 801 according to the conventions of IEEE 802.3 802 Layer Management, counted exclusively according 803 to the error status presented to the LLC. 805 Note: Coding errors detected by the physical 806 layer for speeds above 10 Mb/s will cause the 807 frame to fail the FCS check." 809 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6, 810 aFrameCheckSequenceErrors." 811 ::= { dot3StatsEntry 3 } 813 dot3StatsSingleCollisionFrames OBJECT-TYPE 814 SYNTAX Counter32 815 MAX-ACCESS read-only 816 STATUS current 817 DESCRIPTION "A count of successfully transmitted frames on 818 a particular interface for which transmission 819 is inhibited by exactly one collision. 821 A frame that is counted by an instance of this 822 object is also counted by the corresponding 823 instance of either the ifOutUcastPkts, 824 ifOutMulticastPkts, or ifOutBroadcastPkts, 825 and is not counted by the corresponding 826 instance of the dot3StatsMultipleCollisionFrames 827 object. 829 This counter does not increment when the 830 interface is operating in full-duplex mode." 831 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.3, 832 aSingleCollisionFrames." 833 ::= { dot3StatsEntry 4 } 835 dot3StatsMultipleCollisionFrames OBJECT-TYPE 836 SYNTAX Counter32 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION "A count of successfully transmitted frames on 840 a particular interface for which transmission 841 is inhibited by more than one collision. 843 A frame that is counted by an instance of this 844 object is also counted by the corresponding 845 instance of either the ifOutUcastPkts, 846 ifOutMulticastPkts, or ifOutBroadcastPkts, 847 and is not counted by the corresponding 848 instance of the dot3StatsSingleCollisionFrames 849 object. 851 This counter does not increment when the 852 interface is operating in full-duplex mode." 853 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.4, 854 aMultipleCollisionFrames." 855 ::= { dot3StatsEntry 5 } 857 dot3StatsSQETestErrors OBJECT-TYPE 858 SYNTAX Counter32 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION "A count of times that the SQE TEST ERROR 862 message is generated by the PLS sublayer for a 863 particular interface. The SQE TEST ERROR 864 is set in accordance with the rules for 865 verification of the SQE detection mechanism in 866 the PLS Carrier Sense Function as described in 867 IEEE Std. 802.3, 1998 Edition, section 7.2.4.6. 869 This counter does not increment on interfaces 870 operating at speeds greater than 10 Mb/s, or on 871 interfaces operating in full-duplex mode." 872 REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4, 873 aSQETestErrors." 874 ::= { dot3StatsEntry 6 } 876 dot3StatsDeferredTransmissions OBJECT-TYPE 877 SYNTAX Counter32 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION "A count of frames for which the first 881 transmission attempt on a particular interface 882 is delayed because the medium is busy. 884 The count represented by an instance of this 885 object does not include frames involved in 886 collisions. 888 This counter does not increment when the 889 interface is operating in full-duplex mode." 890 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.9, 891 aFramesWithDeferredXmissions." 892 ::= { dot3StatsEntry 7 } 894 dot3StatsLateCollisions OBJECT-TYPE 895 SYNTAX Counter32 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION "The number of times that a collision is 899 detected on a particular interface later than 900 one slotTime into the transmission of a packet. 902 A (late) collision included in a count 903 represented by an instance of this object is 904 also considered as a (generic) collision for 905 purposes of other collision-related 906 statistics. 908 This counter does not increment when the 909 interface is operating in full-duplex mode." 910 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.10, 911 aLateCollisions." 912 ::= { dot3StatsEntry 8 } 914 dot3StatsExcessiveCollisions OBJECT-TYPE 915 SYNTAX Counter32 916 MAX-ACCESS read-only 917 STATUS current 918 DESCRIPTION "A count of frames for which transmission on a 919 particular interface fails due to excessive 920 collisions. 922 This counter does not increment when the 923 interface is operating in full-duplex mode." 924 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.11, 925 aFramesAbortedDueToXSColls." 926 ::= { dot3StatsEntry 9 } 928 dot3StatsInternalMacTransmitErrors OBJECT-TYPE 929 SYNTAX Counter32 930 MAX-ACCESS read-only 931 STATUS current 932 DESCRIPTION "A count of frames for which transmission on a 933 particular interface fails due to an internal 934 MAC sublayer transmit error. A frame is only 935 counted by an instance of this object if it is 936 not counted by the corresponding instance of 937 either the dot3StatsLateCollisions object, the 938 dot3StatsExcessiveCollisions object, or the 939 dot3StatsCarrierSenseErrors object. 941 The precise meaning of the count represented by 942 an instance of this object is implementation- 943 specific. In particular, an instance of this 944 object may represent a count of transmission 945 errors on a particular interface that are not 946 otherwise counted." 947 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12, 948 aFramesLostDueToIntMACXmitError." 949 ::= { dot3StatsEntry 10 } 951 dot3StatsCarrierSenseErrors OBJECT-TYPE 952 SYNTAX Counter32 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION "The number of times that the carrier sense 956 condition was lost or never asserted when 957 attempting to transmit a frame on a particular 958 interface. 960 The count represented by an instance of this 961 object is incremented at most once per 962 transmission attempt, even if the carrier sense 963 condition fluctuates during a transmission 964 attempt. 966 This counter does not increment when the 967 interface is operating in full-duplex mode." 968 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.13, 969 aCarrierSenseErrors." 970 ::= { dot3StatsEntry 11 } 972 -- { dot3StatsEntry 12 } is not assigned 974 dot3StatsFrameTooLongs OBJECT-TYPE 975 SYNTAX Counter32 976 MAX-ACCESS read-only 977 STATUS current 978 DESCRIPTION "A count of frames received on a particular 979 interface that exceed the maximum permitted 980 frame size. 982 The count represented by an instance of this 983 object is incremented when the frameTooLong 984 status is returned by the MAC service to the 985 LLC (or other MAC user). Received frames for 986 which multiple error conditions obtain are, 987 according to the conventions of IEEE 802.3 988 Layer Management, counted exclusively according 989 to the error status presented to the LLC." 990 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25, 991 aFrameTooLongErrors." 992 ::= { dot3StatsEntry 13 } 994 -- { dot3StatsEntry 14 } is not assigned 996 -- { dot3StatsEntry 15 } is not assigned 998 dot3StatsInternalMacReceiveErrors OBJECT-TYPE 999 SYNTAX Counter32 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION "A count of frames for which reception on a 1003 particular interface fails due to an internal 1004 MAC sublayer receive error. A frame is only 1005 counted by an instance of this object if it is 1006 not counted by the corresponding instance of 1007 either the dot3StatsFrameTooLongs object, the 1008 dot3StatsAlignmentErrors object, or the 1009 dot3StatsFCSErrors object. 1011 The precise meaning of the count represented by 1012 an instance of this object is implementation- 1013 specific. In particular, an instance of this 1014 object may represent a count of receive errors 1015 on a particular interface that are not 1016 otherwise counted." 1017 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15, 1018 aFramesLostDueToIntMACRcvError." 1019 ::= { dot3StatsEntry 16 } 1021 dot3StatsEtherChipSet OBJECT-TYPE 1022 SYNTAX OBJECT IDENTIFIER 1023 MAX-ACCESS read-only 1024 STATUS deprecated 1025 DESCRIPTION "******** THIS OBJECT IS DEPRECATED ******** 1027 This object contains an OBJECT IDENTIFIER 1028 which identifies the chipset used to 1029 realize the interface. Ethernet-like 1030 interfaces are typically built out of 1031 several different chips. The MIB implementor 1032 is presented with a decision of which chip 1033 to identify via this object. The implementor 1034 should identify the chip which is usually 1035 called the Medium Access Control chip. 1036 If no such chip is easily identifiable, 1037 the implementor should identify the chip 1038 which actually gathers the transmit 1039 and receive statistics and error 1040 indications. This would allow a 1041 manager station to correlate the 1042 statistics and the chip generating 1043 them, giving it the ability to take 1044 into account any known anomalies 1045 in the chip." 1046 ::= { dot3StatsEntry 17 } 1048 dot3StatsSymbolErrors OBJECT-TYPE 1049 SYNTAX Counter32 1050 MAX-ACCESS read-only 1051 STATUS current 1052 DESCRIPTION "For an interface operating at 100 Mb/s, the 1053 number of times there was an invalid data symbol 1054 when a valid carrier was present. 1056 For an interface operating in half-duplex mode 1057 at 1000 Mb/s, the number of times the receiving 1058 media is non-idle (a carrier event) for a period 1059 of time equal to or greater than slotTime, and 1060 during which there was at least one occurrence 1061 of an event that causes the PHY to indicate 1062 'Data reception error' or 'carrier extend error' 1063 on the GMII. 1065 For an interface operating in full-duplex mode 1066 at 1000 Mb/s, the number of times the receiving 1067 media is non-idle a carrier event) for a period 1068 of time equal to or greater than minFrameSize, 1069 and during which there was at least one 1070 occurrence of an event that causes the PHY to 1071 indicate 'Data reception error' on the GMII. 1073 The count represented by an instance of this 1074 object is incremented at most once per carrier 1075 event, even if multiple symbol errors occur 1076 during the carrier event. This count does 1077 not increment if a collision is present." 1078 REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, 1079 aSymbolErrorDuringCarrier." 1080 ::= { dot3StatsEntry 18 } 1082 dot3StatsDuplexStatus OBJECT-TYPE 1083 SYNTAX INTEGER { 1084 unknown(1), 1085 halfDuplex(2), 1086 fullDuplex(3) 1087 } 1088 MAX-ACCESS read-only 1089 STATUS current 1090 DESCRIPTION "The current mode of operation of the MAC 1091 entity. 'unknown' indicates that the current 1092 duplex mode could not be determined. 1094 Management control of the duplex mode is 1095 accomplished through the MAU MIB. When 1096 an interface does not support autonegotiation, 1097 or when autonegotiation is not enabled, the 1098 duplex mode is controlled using 1099 ifMauDefaultType. When autonegotiation is 1100 supported and enabled, duplex mode is controlled 1101 using ifMauAutoNegAdvertisedBits. In either 1102 case, the currently operating duplex mode is 1103 reflected both in this object and in ifMauType." 1104 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32, 1105 aDuplexStatus." 1106 ::= { dot3StatsEntry 19 } 1108 -- the Ethernet-like Collision Statistics group 1110 -- Implementation of this group is optional; it is appropriate 1111 -- for all systems which have the necessary metering 1113 dot3CollTable OBJECT-TYPE 1114 SYNTAX SEQUENCE OF Dot3CollEntry 1115 MAX-ACCESS not-accessible 1116 STATUS current 1117 DESCRIPTION "A collection of collision histograms for a 1118 particular set of interfaces." 1119 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.30, 1120 aCollisionFrames." 1121 ::= { dot3 5 } 1123 dot3CollEntry OBJECT-TYPE 1124 SYNTAX Dot3CollEntry 1125 MAX-ACCESS not-accessible 1126 STATUS current 1127 DESCRIPTION "A cell in the histogram of per-frame 1128 collisions for a particular interface. An 1129 instance of this object represents the 1130 frequency of individual MAC frames for which 1131 the transmission (successful or otherwise) on a 1132 particular interface is accompanied by a 1133 particular number of media collisions." 1134 INDEX { ifIndex, dot3CollCount } 1135 ::= { dot3CollTable 1 } 1137 Dot3CollEntry ::= 1138 SEQUENCE { 1139 dot3CollCount INTEGER, 1140 dot3CollFrequencies Counter32 1141 } 1143 -- { dot3CollEntry 1 } is no longer in use 1145 dot3CollCount OBJECT-TYPE 1146 SYNTAX INTEGER (1..16) 1147 MAX-ACCESS not-accessible 1148 STATUS current 1149 DESCRIPTION "The number of per-frame media collisions for 1150 which a particular collision histogram cell 1151 represents the frequency on a particular 1152 interface." 1153 ::= { dot3CollEntry 2 } 1155 dot3CollFrequencies OBJECT-TYPE 1156 SYNTAX Counter32 1157 MAX-ACCESS read-only 1158 STATUS current 1159 DESCRIPTION "A count of individual MAC frames for which the 1160 transmission (successful or otherwise) on a 1161 particular interface occurs after the 1162 frame has experienced exactly the number 1163 of collisions in the associated 1164 dot3CollCount object. 1166 For example, a frame which is transmitted 1167 on interface 77 after experiencing 1168 exactly 4 collisions would be indicated 1169 by incrementing only dot3CollFrequencies.77.4. 1170 No other instance of dot3CollFrequencies would 1171 be incremented in this example. 1173 This counter does not increment when the 1174 interface is operating in full-duplex mode." 1175 ::= { dot3CollEntry 3 } 1177 dot3ControlTable OBJECT-TYPE 1178 SYNTAX SEQUENCE OF Dot3ControlEntry 1179 MAX-ACCESS not-accessible 1180 STATUS current 1181 DESCRIPTION "A table of descriptive and status information 1182 about the MAC Control sublayer on the 1183 ethernet-like interfaces attached to a 1184 particular system." 1185 ::= { dot3 9 } 1187 dot3ControlEntry OBJECT-TYPE 1188 SYNTAX Dot3ControlEntry 1189 MAX-ACCESS not-accessible 1190 STATUS current 1191 DESCRIPTION "An entry in the table, containing information 1192 about the MAC Control sublayer on a single 1193 ethernet-like interface." 1194 INDEX { dot3StatsIndex } 1195 ::= { dot3ControlTable 1 } 1197 Dot3ControlEntry ::= 1198 SEQUENCE { 1199 dot3ControlFunctionsSupported BITS, 1200 dot3ControlInUnknownOpcodes Counter32 1201 } 1203 dot3ControlFunctionsSupported OBJECT-TYPE 1204 SYNTAX BITS { 1205 pause(0) 1206 } 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION "A list of the possible MAC Control functions 1210 implemented for this interface." 1211 REFERENCE "[IEEE 802.3 Std.], 30.3.3.2, 1212 aMACControlFunctionsSupported." 1213 ::= { dot3ControlEntry 1 } 1215 dot3ControlInUnknownOpcodes OBJECT-TYPE 1216 SYNTAX Counter32 1217 MAX-ACCESS read-only 1218 STATUS current 1219 DESCRIPTION "A count of MAC Control frames received on this 1220 interface that contain an opcode that is not 1221 supported by this device." 1222 REFERENCE "[IEEE 802.3 Std.], 30.3.3.5, 1223 aUnsupportedOpcodesReceived" 1224 ::= { dot3ControlEntry 2 } 1226 dot3PauseTable OBJECT-TYPE 1227 SYNTAX SEQUENCE OF Dot3PauseEntry 1228 MAX-ACCESS not-accessible 1229 STATUS current 1230 DESCRIPTION "A table of descriptive and status information 1231 about the MAC Control PAUSE function on the 1232 ethernet-like interfaces attached to a 1233 particular system." 1234 ::= { dot3 10 } 1236 dot3PauseEntry OBJECT-TYPE 1237 SYNTAX Dot3PauseEntry 1238 MAX-ACCESS not-accessible 1239 STATUS current 1240 DESCRIPTION "An entry in the table, containing information 1241 about the MAC Control PAUSE function on a single 1242 ethernet-like interface." 1243 INDEX { dot3StatsIndex } 1244 ::= { dot3PauseTable 1 } 1246 Dot3PauseEntry ::= 1247 SEQUENCE { 1248 dot3PauseAdminMode INTEGER, 1249 dot3PauseOperMode INTEGER, 1250 dot3PauseLinkDelayAllowance Unsigned32, 1251 dot3InPauseFrames Counter32, 1252 dot3OutPauseFrames Counter32 1253 } 1255 dot3PauseAdminMode OBJECT-TYPE 1256 SYNTAX INTEGER { 1257 disabled(1), 1258 enabledXmit(2), 1259 enabledRcv(3), 1260 enabledXmitAndRcv(4) 1261 } 1262 MAX-ACCESS read-write 1263 STATUS current 1264 DESCRIPTION "This object is used to configure the default 1265 administrative PAUSE mode for this interface. 1267 This object represents the 1268 administratively-configured PAUSE mode for this 1269 interface. If auto-negotiation is not enabled 1270 or is not implemented for the active MAU 1271 attached to this interface, the value of this 1272 object determines the operational PAUSE mode 1273 of the interface whenever it is operating in 1274 full-duplex mode. In this case, a set to this 1275 object will force the interface into the 1276 specified mode. 1278 If auto-negotiation is implemented and enabled 1279 for the MAU attached to this interface, the 1280 PAUSE mode for this interface is determined by 1281 auto-negotiation, and the value of this object 1282 denotes the mode to which the interface will 1283 automatically revert if/when auto-negotiation is 1284 later disabled. Note that when auto-negotiation 1285 is running, administrative control of the PAUSE 1286 mode may be accomplished using the 1287 ifMauAutoNegCapAdvertisedBits object in the 1288 MAU-MIB. 1290 Note that the value of this object is ignored 1291 when the interface is not operating in 1292 full-duplex mode. 1294 An attempt to set this object to 1295 'enabledXmit(2)' or 'enabledRcv(3)' will fail 1296 on interfaces that do not support operation 1297 at greater than 100 Mb/s." 1298 ::= { dot3PauseEntry 1 } 1300 dot3PauseOperMode OBJECT-TYPE 1301 SYNTAX INTEGER { 1302 disabled(1), 1303 enabledXmit(2), 1304 enabledRcv(3), 1305 enabledXmitAndRcv(4) 1306 } 1307 MAX-ACCESS read-only 1308 STATUS current 1309 DESCRIPTION "This object reflects the PAUSE mode currently 1310 in use on this interface, as determined by 1311 either (1) the result of the auto-negotiation 1312 function or (2) if auto-negotiation is not 1313 enabled or is not implemented for the active MAU 1314 attached to this interface, by the value of 1315 dot3PauseAdminMode. Interfaces operating at 1316 100 Mb/s or less will never return 1317 'enabledXmit(2)' or 'enabledRcv(3)'. Interfaces 1318 operating in half-duplex mode will always return 1319 'disabled(1)'. Interfaces on which 1320 auto-negotiation is enabled but not yet 1321 completed should return the value 1322 'disabled(1)'." 1323 ::= { dot3PauseEntry 2 } 1325 dot3PauseLinkDelayAllowance OBJECT-TYPE 1326 SYNTAX Unsigned32 (0..4294967295) 1327 MAX-ACCESS read-write 1328 STATUS current 1329 DESCRIPTION "The allowance, in bit times, made by the PAUSE 1330 MAC Control entity for round-trip propagation 1331 delay of the full-duplex link." 1333 REFERENCE "[IEEE 802.3 Std.], 30.3.4.1, 1334 aPAUSELinkDelayAllowance." 1335 ::= { dot3PauseEntry 3 } 1337 dot3InPauseFrames OBJECT-TYPE 1338 SYNTAX Counter32 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION "A count of MAC Control frames received on this 1342 interface with an opcode indicating the PAUSE 1343 operation. 1345 This counter does not increment when the 1346 interface is operating in half-duplex mode." 1347 REFERENCE "[IEEE 802.3 Std.], 30.3.4.3, 1348 aPAUSEMACCtrlFramesReceived." 1349 ::= { dot3PauseEntry 4 } 1351 dot3OutPauseFrames OBJECT-TYPE 1352 SYNTAX Counter32 1353 MAX-ACCESS read-only 1354 STATUS current 1355 DESCRIPTION "A count of MAC Control frames transmitted on 1356 this interface with an opcode indicating the 1357 PAUSE operation. 1359 This counter does not increment when the 1360 interface is operating in half-duplex mode." 1361 REFERENCE "[IEEE 802.3 Std.], 30.3.4.2, 1362 aPAUSEMACCtrlFramesTransmitted." 1363 ::= { dot3PauseEntry 5 } 1365 -- 802.3 Tests 1367 dot3Tests OBJECT IDENTIFIER ::= { dot3 6 } 1369 dot3Errors OBJECT IDENTIFIER ::= { dot3 7 } 1371 -- TDR Test 1373 dot3TestTdr OBJECT-IDENTITY 1374 STATUS current 1375 DESCRIPTION "The Time-Domain Reflectometry (TDR) test is 1376 specific to ethernet-like interfaces of type 1377 10Base5 and 10Base2. The TDR value may be 1378 useful in determining the approximate distance 1379 to a cable fault. It is advisable to repeat 1380 this test to check for a consistent resulting 1381 TDR value, to verify that there is a fault. 1383 A TDR test returns as its result the time 1384 interval, measured in 10 MHz ticks or 100 nsec 1385 units, between the start of TDR test 1386 transmission and the subsequent detection of a 1387 collision or deassertion of carrier. On 1388 successful completion of a TDR test, the result 1389 is stored as the value of an appropriate 1390 instance of an appropriate vendor specific MIB 1391 object, and the OBJECT IDENTIFIER of that 1392 instance is stored in the appropriate instance 1393 of the appropriate test result code object 1394 (thereby indicating where the result has been 1395 stored)." 1396 ::= { dot3Tests 1 } 1398 -- Loopback Test 1400 dot3TestLoopBack OBJECT-IDENTITY 1401 STATUS current 1402 DESCRIPTION "This test configures the MAC chip and executes 1403 an internal loopback test of memory, data paths, 1404 and the MAC chip logic. This loopback test can 1405 only be executed if the interface is offline. 1406 Once the test has completed, the MAC chip should 1407 be reinitialized for network operation, but it 1408 should remain offline. 1410 If an error occurs during a test, the 1411 appropriate test result object will be set 1412 to indicate a failure. The two OBJECT 1413 IDENTIFIER values dot3ErrorInitError and 1414 dot3ErrorLoopbackError may be used to provided 1415 more information as values for an appropriate 1416 test result code object." 1417 ::= { dot3Tests 2 } 1419 dot3ErrorInitError OBJECT-IDENTITY 1420 STATUS current 1421 DESCRIPTION "Couldn't initialize MAC chip for test." 1422 ::= { dot3Errors 1 } 1424 dot3ErrorLoopbackError OBJECT-IDENTITY 1425 STATUS current 1426 DESCRIPTION "Expected data not received (or not received 1427 correctly) in loopback test." 1428 ::= { dot3Errors 2 } 1430 -- conformance information 1432 etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 } 1434 etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 } 1435 etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 } 1437 -- compliance statements 1439 etherCompliance MODULE-COMPLIANCE 1440 STATUS deprecated 1441 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 1443 The compliance statement for managed network 1444 entities which have ethernet-like network 1445 interfaces. 1447 This compliance is deprecated and replaced by 1448 dot3Compliance." 1450 MODULE -- this module 1451 MANDATORY-GROUPS { etherStatsGroup } 1453 GROUP etherCollisionTableGroup 1454 DESCRIPTION "This group is optional. It is appropriate 1455 for all systems which have the necessary 1456 metering. Implementation in such systems is 1457 highly recommended." 1458 ::= { etherCompliances 1 } 1460 ether100MbsCompliance MODULE-COMPLIANCE 1461 STATUS deprecated 1462 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 1464 The compliance statement for managed network 1465 entities which have 100 Mb/sec ethernet-like 1466 network interfaces. 1468 This compliance is deprecated and replaced by 1469 dot3Compliance." 1471 MODULE -- this module 1472 MANDATORY-GROUPS { etherStats100MbsGroup } 1473 GROUP etherCollisionTableGroup 1474 DESCRIPTION "This group is optional. It is appropriate 1475 for all systems which have the necessary 1476 metering. Implementation in such systems is 1477 highly recommended." 1478 ::= { etherCompliances 2 } 1480 dot3Compliance MODULE-COMPLIANCE 1481 STATUS current 1482 DESCRIPTION "The compliance statement for managed network 1483 entities which have ethernet-like network 1484 interfaces." 1486 MODULE -- this module 1487 MANDATORY-GROUPS { etherStatsBaseGroup } 1489 GROUP etherDuplexGroup 1490 DESCRIPTION "This group is mandatory for all 1491 ethernet-like network interfaces which are 1492 capable of operating in full-duplex mode. 1493 It is highly recommended for all 1494 ethernet-like network interfaces." 1496 GROUP etherStatsLowSpeedGroup 1497 DESCRIPTION "This group is mandatory for all 1498 ethernet-like network interfaces which are 1499 capable of operating at 10 Mb/s or slower in 1500 half-duplex mode." 1502 GROUP etherStatsHighSpeedGroup 1503 DESCRIPTION "This group is mandatory for all 1504 ethernet-like network interfaces which are 1505 capable of operating at 100 Mb/s or faster." 1507 GROUP etherControlGroup 1508 DESCRIPTION "This group is mandatory for all 1509 ethernet-like network interfaces that 1510 support the MAC Control sublayer." 1512 GROUP etherControlPauseGroup 1513 DESCRIPTION "This group is mandatory for all 1514 ethernet-like network interfaces that 1515 support the MAC Control PAUSE function." 1517 OBJECT dot3PauseLinkDelayAllowance 1518 MIN-ACCESS read-only 1519 DESCRIPTION "Write access is not required." 1520 GROUP etherCollisionTableGroup 1521 DESCRIPTION "This group is optional. It is appropriate 1522 for all ethernet-like network interfaces 1523 which are capable of operating in 1524 half-duplex mode and have the necessary 1525 metering. Implementation in systems with 1526 such interfaces is highly recommended." 1527 ::= { etherCompliances 3 } 1529 -- units of conformance 1531 etherStatsGroup OBJECT-GROUP 1532 OBJECTS { dot3StatsIndex, 1533 dot3StatsAlignmentErrors, 1534 dot3StatsFCSErrors, 1535 dot3StatsSingleCollisionFrames, 1536 dot3StatsMultipleCollisionFrames, 1537 dot3StatsSQETestErrors, 1538 dot3StatsDeferredTransmissions, 1539 dot3StatsLateCollisions, 1540 dot3StatsExcessiveCollisions, 1541 dot3StatsInternalMacTransmitErrors, 1542 dot3StatsCarrierSenseErrors, 1543 dot3StatsFrameTooLongs, 1544 dot3StatsInternalMacReceiveErrors, 1545 dot3StatsEtherChipSet 1546 } 1547 STATUS deprecated 1548 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 1550 A collection of objects providing information 1551 applicable to all ethernet-like network 1552 interfaces. 1554 This object group has been deprecated and 1555 replaced by etherStatsBaseGroup and 1556 etherStatsLowSpeedGroup." 1557 ::= { etherGroups 1 } 1559 etherCollisionTableGroup OBJECT-GROUP 1560 OBJECTS { dot3CollFrequencies 1561 } 1562 STATUS current 1563 DESCRIPTION "A collection of objects providing a histogram 1564 of packets successfully transmitted after 1565 experiencing exactly N collisions." 1566 ::= { etherGroups 2 } 1568 etherStats100MbsGroup OBJECT-GROUP 1569 OBJECTS { dot3StatsIndex, 1570 dot3StatsAlignmentErrors, 1571 dot3StatsFCSErrors, 1572 dot3StatsSingleCollisionFrames, 1573 dot3StatsMultipleCollisionFrames, 1574 dot3StatsDeferredTransmissions, 1575 dot3StatsLateCollisions, 1576 dot3StatsExcessiveCollisions, 1577 dot3StatsInternalMacTransmitErrors, 1578 dot3StatsCarrierSenseErrors, 1579 dot3StatsFrameTooLongs, 1580 dot3StatsInternalMacReceiveErrors, 1581 dot3StatsEtherChipSet, 1582 dot3StatsSymbolErrors 1583 } 1584 STATUS deprecated 1585 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 1587 A collection of objects providing information 1588 applicable to 100 Mb/sec ethernet-like network 1589 interfaces. 1591 This object group has been deprecated and 1592 replaced by etherStatsBaseGroup and 1593 etherStatsHighSpeedGroup." 1594 ::= { etherGroups 3 } 1596 etherStatsBaseGroup OBJECT-GROUP 1597 OBJECTS { dot3StatsIndex, 1598 dot3StatsAlignmentErrors, 1599 dot3StatsFCSErrors, 1600 dot3StatsSingleCollisionFrames, 1601 dot3StatsMultipleCollisionFrames, 1602 dot3StatsDeferredTransmissions, 1603 dot3StatsLateCollisions, 1604 dot3StatsExcessiveCollisions, 1605 dot3StatsInternalMacTransmitErrors, 1606 dot3StatsCarrierSenseErrors, 1607 dot3StatsFrameTooLongs, 1608 dot3StatsInternalMacReceiveErrors 1609 } 1610 STATUS current 1611 DESCRIPTION "A collection of objects providing information 1612 applicable to all ethernet-like network 1613 interfaces." 1614 ::= { etherGroups 4 } 1616 etherStatsLowSpeedGroup OBJECT-GROUP 1617 OBJECTS { dot3StatsSQETestErrors } 1618 STATUS current 1619 DESCRIPTION "A collection of objects providing information 1620 applicable to ethernet-like network interfaces 1621 capable of operating at 10 Mb/s or slower in 1622 half-duplex mode." 1623 ::= { etherGroups 5 } 1625 etherStatsHighSpeedGroup OBJECT-GROUP 1626 OBJECTS { dot3StatsSymbolErrors } 1627 STATUS current 1628 DESCRIPTION "A collection of objects providing information 1629 applicable to ethernet-like network interfaces 1630 capable of operating at 100 Mb/s or faster." 1631 ::= { etherGroups 6 } 1633 etherDuplexGroup OBJECT-GROUP 1634 OBJECTS { dot3StatsDuplexStatus } 1635 STATUS current 1636 DESCRIPTION "A collection of objects providing information 1637 about the duplex mode of an ethernet-like 1638 network interface." 1639 ::= { etherGroups 7 } 1641 etherControlGroup OBJECT-GROUP 1642 OBJECTS { dot3ControlFunctionsSupported, 1643 dot3ControlInUnknownOpcodes 1644 } 1645 STATUS current 1646 DESCRIPTION "A collection of objects providing information 1647 about the MAC Control sublayer on ethernet-like 1648 network interfaces." 1649 ::= { etherGroups 8 } 1651 etherControlPauseGroup OBJECT-GROUP 1652 OBJECTS { dot3PauseAdminMode, 1653 dot3PauseOperMode, 1654 dot3PauseLinkDelayAllowance, 1655 dot3InPauseFrames, 1656 dot3OutPauseFrames 1657 } 1658 STATUS current 1659 DESCRIPTION "A collection of objects providing information 1660 about and control of the MAC Control PAUSE 1661 function on ethernet-like network interfaces." 1662 ::= { etherGroups 9 } 1664 END 1666 5. Intellectual Property 1668 The IETF takes no position regarding the validity or scope of any 1669 intellectual property or other rights that might be claimed to 1670 pertain to the implementation or use of the technology described in 1671 this document or the extent to which any license under such rights 1672 might or might not be available; neither does it represent that it 1673 has made any effort to identify any such rights. Information on the 1674 IETF's procedures with respect to rights in standards-track and 1675 standards-related documentation can be found in BCP-11. Copies of 1676 claims of rights made available for publication and any assurances of 1677 licenses to be made available, or the result of an attempt made to 1678 obtain a general license or permission for the use of such 1679 proprietary rights by implementors or users of this specification can 1680 be obtained from the IETF Secretariat. 1682 The IETF invites any interested party to bring to its attention any 1683 copyrights, patents or patent applications, or other proprietary 1684 rights which may cover technology that may be required to practice 1685 this standard. Please address the information to the IETF Executive 1686 Director. 1688 6. Acknowledgements 1690 This document was produced by the Ethernet Interfaces and Hub MIB 1691 Working Group. 1693 This document is based on the Proposed Standard Ethernet MIB, RFC 1694 2358 [23], edited by John Flick of Hewlett-Packard and Jeffrey 1695 Johnson of RedBack Networks and produced by the 802.3 Hub MIB Working 1696 Group. It extends that document by providing support for full-duplex 1697 Ethernet interfaces and 1000 Mb/sec Ethernet interfaces as outlined 1698 in [16]. 1700 RFC 2358, in turn, is almost completely based on both the Standard 1701 Ethernet MIB, RFC 1643 [21], and the Proposed Standard Ethernet MIB 1702 using the SNMPv2 SMI, RFC 1650 [22], both of which were edited by 1703 Frank Kastenholz of FTP Software and produced by the Interfaces MIB 1704 Working Group. RFC 2358 extends those documents by providing support 1705 for 100 Mb/sec ethernet interfaces. 1707 RFC 1643 and RFC 1650, in turn, are based on the Draft Standard 1708 Ethernet MIB, RFC 1398 [20], also edited by Frank Kastenholz and 1709 produced by the Ethernet MIB Working Group. 1711 RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, 1712 RFC 1284 [18], which was edited by John Cook of Chipcom and produced 1713 by the Transmission MIB Working Group. The Ethernet MIB Working 1714 Group gathered implementation experience of the variables specified 1715 in RFC 1284, documented that experience in RFC 1369 [19], and used 1716 that information to develop this revised MIB. 1718 RFC 1284, in turn, is based on a document written by Frank 1719 Kastenholz, then of Interlan, entitled IEEE 802.3 Layer Management 1720 Draft M compatible MIB for TCP/IP Networks [17]. This document was 1721 modestly reworked, initially by the SNMP Working Group, and then by 1722 the Transmission Working Group, to reflect the current conventions 1723 for defining objects for MIB interfaces. James Davin, of the MIT 1724 Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN 1725 Systems, contributed to later drafts of this memo. Marshall Rose of 1726 Performance Systems International, Inc. converted the document into 1727 RFC 1212 [3] concise format. Anil Rijsinghani of DEC contributed 1728 text that more adequately describes the TDR test. Thanks to Frank 1729 Kastenholz of Interlan and Louis Steinberg of IBM for their 1730 experimentation. 1732 7. References 1734 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1735 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1736 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1737 January 1998 1739 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1740 Management Information for TCP/IP-based Internets", STD 16, 1741 RFC 1155, Performance Systems International, Hughes LAN Systems, 1742 May 1990 1744 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, 1745 RFC 1212, Performance Systems International, Hughes LAN Systems, 1746 March 1991 1748 [4] M. Rose, "A Convention for Defining Traps for use with the 1749 SNMP", RFC 1215, Performance Systems International, March 1991 1751 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1752 "Structure of Management Information for Version 2 of the Simple 1753 Network Management Protocol (SNMPv2)", RFC 1902, SNMP Research, 1754 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1755 International Network Services, January 1996. 1757 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1758 Conventions for Version 2 of the Simple Network Management 1759 Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco 1760 Systems, Inc., Dover Beach Consulting, Inc., International 1761 Network Services, January 1996. 1763 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1764 "Conformance Statements for Version 2 of the Simple Network 1765 Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., 1766 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1767 Network Services, January 1996. 1769 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1770 Network Management Protocol", STD 15, RFC 1157, SNMP Research, 1771 Performance Systems International, Performance Systems 1772 International, MIT Laboratory for Computer Science, May 1990. 1774 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1775 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 1776 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1777 Inc., International Network Services, January 1996. 1779 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1780 "Transport Mappings for Version 2 of the Simple Network 1781 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 1782 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1783 Network Services, January 1996. 1785 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1786 Processing and Dispatching for the Simple Network Management 1787 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron 1788 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1789 January 1998. 1791 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1792 for version 3 of the Simple Network Management Protocol 1793 (SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. 1795 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1796 Operations for Version 2 of the Simple Network Management 1797 Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco 1798 Systems, Inc., Dover Beach Consulting, Inc., International 1799 Network Services, January 1996. 1801 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1802 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1803 Systems, January 1998 1805 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1806 Control Model (VACM) for the Simple Network Management Protocol 1807 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, 1808 Inc., Cisco Systems, Inc., January 1998 1810 [16] IEEE, IEEE Std 802.3, 1998 Edition: "Information technology - 1811 Telecommunications and information exchange between systems - 1812 Local and metropolitan area networks - Specific requirements - 1813 Part 3: Carrier sense multiple access with collision detection 1814 (CSMA/CD) access method and physical layer specifications" 1815 (incorporating ANSI/IEEE Std. 802.3, 1996 Edition, IEEE Std. 1816 802.3r-1996, 802.3u-1995, 802.3x&y-1997, 802.3z-1998, and 1817 802.3aa-1998), September 1998. 1819 [17] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible 1820 MIB for TCP/IP Networks", electronic mail message to mib- 1821 wg@nnsc.nsf.net, 9 June 1989. 1823 [18] Cook, J., "Definitions of Managed Objects for Ethernet-Like 1824 Interface Types", RFC 1284, Chipcom Corporation, December 1991. 1826 [19] Kastenholz, F., "Implementation Notes and Experience for The 1827 Internet Ethernet MIB", RFC 1369, FTP Software, October 1992. 1829 [20] Kastenholz, F., "Definitions of Managed Objects for the 1830 Ethernet-like Interface Types", RFC 1398, FTP Software, Inc., 1831 January 1993. 1833 [21] Kastenholz, F., "Definitions of Managed Objects for the 1834 Ethernet-like Interface Types", STD 50, RFC 1643, FTP Software, 1835 Inc., July 1994. 1837 [22] Kastenholz, F., "Definitions of Managed Objects for the 1838 Ethernet-like Interface Types using SMIv2", RFC 1650, 1839 FTP Software, Inc., August 1994. 1841 [23] Flick, J., and J. Johnson, "Definitions of Managed Objects 1842 for the Ethernet-like Interface Types", RFC 2358, 1843 Hewlett-Packard Company, RedBack Networks, June 1998. 1845 [24] McCloghrie, K., and M. Rose, Editors, "Management Information 1846 Base for Network Management of TCP/IP-based internets: MIB-II", 1847 STD 17, RFC 1213, Hughes LAN Systems, Performance Systems 1848 International, March 1991. 1850 [25] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB 1851 using SMIv2", RFC 2233, Cisco Systems, FTP Software, 1852 November 1997. 1854 [26] Bradner, S., "Key words for use in RFCs to Indicate 1855 Requirements Levels", BCP 14, RFC 2119, March 1997. 1857 [27] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster, 1858 D., McCloghrie, K., and S. Roberts, "Definitions of Managed 1859 Objects for IEEE 802.3 Medium Attachment Units (MAUs) using 1860 SMIv2", work in progress, draft-ietf-hubmib-mau-mib-v2-02.txt, 1861 Extreme Networks, Inc., Hewlett-Packard Company, Argon Networks, 1862 LANNET Ltd., Cisco Systems, Inc., Cisco Systems Inc., Farallon 1863 Computing Inc., January 1999. 1865 [28] Flick, J., "Definitions of Object Identifiers for Identifying 1866 Ethernet Chip Sets", work in progress, 1867 draft-ietf-hubmib-ether-chipsets-00.txt, Hewlett-Packard 1868 Company, January 1999. 1870 8. Security Considerations 1872 There are two management objects defined in this MIB that have a 1873 MAX-ACCESS clause of read-write. Such objects may be considered 1874 sensitive or vulnerable in some network environments. The support 1875 for SET operations in a non-secure environment without proper 1876 protection can have a negative effect on network operations. 1878 There are a number of managed objects in this MIB that may be 1879 considered to contain sensitive information. In particular, the 1880 dot3StatsEtherChipSet object may be considered sensitive in many 1881 environments, since it would allow an intruder to obtain information 1882 about which vendor's equipment is in use on the network. Note that 1883 this object has been deprecated. However, some implementors may 1884 still choose to implement it for backwards compatability. 1886 Therefore, it may be important in some environments to control read 1887 access to these objects and possibly to even encrypt the values of 1888 these objects when sending them over the network via SNMP. Not all 1889 versions of SNMP provide features for such a secure environment. 1891 SNMPv1 by itself is such an insecure environment. Even if the 1892 network itself is secure (for example by using IPSec), even then, 1893 there is no control as to who on the secure network is allowed to 1894 access and GET (read) the objects in this MIB. 1896 It is recommended that the implementors consider the security 1897 features as provided by the SNMPv3 framework. Specifically, the use 1898 of the User-based Security Model RFC 2274 [12] and the View-based 1899 Access Control Model RFC 2275 [15] is recommended. 1901 It is then a customer/user responsibility to ensure that the SNMP 1902 entity giving access to an instance of this MIB, is properly 1903 configured to give access to those objects only to those principals 1904 (users) that have legitimate rights to access them. 1906 9. Author's Addresses 1908 John Flick 1909 Hewlett-Packard Company 1910 8000 Foothills Blvd. M/S 5557 1911 Roseville, CA 95747-5557 1913 Phone: +1 916 785 4018 1914 Email: johnf@rose.hp.com 1916 Jeffrey Johnson 1917 RedBack Networks 1918 2570 North First Street, Suite 410 1919 San Jose, CA, 95131, USA 1921 Phone: +1 408 571 2699 1922 EMail: jeff@redbacknetworks.com 1924 A. Change Log 1926 A.1. Changes since RFC 2358 1928 This section enumerates changes made to RFC 2358 to produce this 1929 document. 1931 (1) Section 2 has been replaced with the current SNMP 1932 Management Framework boilerplate. 1934 (2) The ifMtu mapping has been clarified. 1936 (3) The relationship between the IEEE 802.3 octet counters 1937 and the IF-MIB octet counters has been clarified. 1939 (4) REFERENCE clauses have been updated to reflect the 1940 actual IEEE 802.3 managed object that each MIB object 1941 is based on. 1943 (5) The following object DESCRIPTION clauses have been 1944 updated to reflect that they do not increment in 1945 full-duplex mode: dot3StatsSingleCollisionFrames, 1946 dot3StatsMultipleCollisionFrames, dot3StatsSQETestErrors, 1947 dot3StatsDeferredTransmissions, dot3StatsLateCollisions, 1948 dot3StatsExcessiveCollisions, dot3StatsCarrierSenseErrors, 1949 dot3CollFrequencies. 1951 (6) The following object DESCRIPTION clauses have been 1952 updated to reflect behaviour on full-duplex and 1953 1000 Mb/s interfaces: dot3StatsAlignmentErrors, 1954 dot3StatsFCSErrors, dot3StatsSQETestErrors, 1955 dot3StatsLateCollisions, dot3StatsSymbolErrors. 1957 (7) Two new tables, dot3ControlTable and dot3PauseTable, 1958 have been added. 1960 (8) A new object, dot3StatsDuplexStatus, has been added. 1962 (9) The object groups and compliances have been restructured. 1964 (10) The dot3StatsEtherChipSet object has been deprecated. 1966 (11) The dot3ChipSets have been moved to a separate document. 1968 A.2. Changes between RFC 1650 and RFC 2358 1970 This section enumerates changes made to RFC 1650 to produce RFC 2358. 1972 (1) The MODULE-IDENTITY has been updated to reflect the changes 1973 in the MIB. 1975 (2) A new object, dot3StatsSymbolErrors, has been added. 1977 (3) The definition of the object dot3StatsIndex has been 1978 converted to use the SMIv2 OBJECT-TYPE macro. 1980 (4) A new conformance group, etherStats100MbsGroup, has been 1981 added. 1983 (5) A new compliance statement, ether100MbsCompliance, has 1984 been added. 1986 (6) The Acknowledgements were extended to provide a more 1987 complete history of the origin of this document. 1989 (7) The discussion of ifType has been expanded. 1991 (8) A section on mapping of Interfaces MIB objects has 1992 been added. 1994 (9) A section defining the relationship of this MIB to 1995 the MAU MIB has been added. 1997 (10) A section on the mapping of IEEE 802.3 managed objects 1998 to this MIB and the Interfaces MIB has been added. 2000 (11) Converted the dot3Tests, dot3Errors, and dot3ChipSets 2001 OIDs to use the OBJECT-IDENTITY macro. 2003 (12) Added to the list of registered dot3ChipSets. 2005 (13) An intellectual property notice and copyright notice 2006 were added, as required by RFC 2026. 2008 B. Full Copyright Statement 2010 This document and translations of it may be copied and furnished to 2011 others, and derivative works that comment on or otherwise explain it 2012 or assist in its implementation may be prepared, copied, published 2013 and distributed, in whole or in part, without restriction of any 2014 kind, provided that the above copyright notice and this paragraph are 2015 included on all such copies and derivative works. However, this 2016 document itself may not be modified in any way, such as by removing 2017 the copyright notice or references to the Internet Society or other 2018 Internet organizations, except as needed for the purpose of 2019 developing Internet standards in which case the procedures for 2020 copyrights defined in the Internet Standards process must be 2021 followed, or as required to translate it into languages other than 2022 English. 2024 The limited permissions granted above are perpetual and will not be 2025 revoked by the Internet Society or its successors or assigns. 2027 This document and the information contained herein is provided on an 2028 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2029 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2030 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2031 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2032 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.