idnits 2.17.1 draft-ietf-hubmib-etherif-mib-v2-01.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 511 has weird spacing: '...issions dot...' == Line 517 has weird spacing: '...cvError dot3S...' == Line 541 has weird spacing: '...pported dot3...' == Line 547 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 (November 1998) is 9293 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-01 -- Possible downref: Non-RFC (?) normative reference: ref. '28' Summary: 28 errors (**), 0 flaws (~~), 8 warnings (==), 6 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 November 1998 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 entire list of current Internet-Drafts, please check the 26 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 27 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 28 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 29 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 31 Copyright Notice 33 Copyright (C) The Internet Society (1998). All Rights Reserved. 35 Abstract 37 This memo defines a portion of the Management Information Base (MIB) 38 for use with network management protocols in the Internet community. 39 This memo obsoletes RFC 2358 ''Definitions of Managed Objects for the 40 Ethernet-like Interface Types''. This memo extends that 41 specification by including management information useful for the 42 management of 1000 Mb/s and full-duplex Ethernet interfaces. 44 Ethernet technology, as defined by the 802.3 Working Group of the 45 IEEE, continues to evolve, with scalable increases in speed, new 46 types of cabling and interfaces, and new features. This evolution 47 may require changes in the managed objects in order to reflect this 48 new functionality. This document, as with other documents issued by 49 this working group, reflects a certain stage in the evolution of 50 Ethernet technology. In the future, this document might be revised, 51 or new documents might be issued by the Ethernet Interfaces and Hub 52 MIB Working Group, in order to reflect the evolution of Ethernet 53 technology. 55 Distribution of this memo is unlimited. Please forward comments to 56 hubmib@hprnd.rose.hp.com. 58 Table of Contents 60 1. Introduction ................................................ 2 61 2. The SNMP Management Framework .............................. 3 62 3. Overview ................................................... 4 63 3.1. Relation to MIB-2 ........................................ 4 64 3.2. Relation to the Interfaces MIB ........................... 5 65 3.2.1. Layering Model ......................................... 5 66 3.2.2. Virtual Circuits ....................................... 5 67 3.2.3. ifTestTable ............................................ 5 68 3.2.4. ifRcvAddressTable ...................................... 6 69 3.2.5. ifPhysAddress .......................................... 6 70 3.2.6. ifType ................................................. 7 71 3.2.7. Specific Interface MIB Objects ......................... 7 72 3.3. Relation to the 802.3 MAU MIB ............................ 11 73 3.4. dot3StatsEtherChipSet .................................... 11 74 3.5. Mapping of IEEE 802.3 Managed Objects .................... 11 75 4. Definitions ................................................ 14 76 5. Intellectual Property ...................................... 35 77 6. Acknowledgements ........................................... 36 78 7. References ................................................. 37 79 8. Security Considerations .................................... 40 80 9. Author's Addresses ......................................... 40 81 A. Change Log ................................................. 41 82 A.1. Changes since RFC 2358 ................................... 41 83 A.2. Changes between RFC 1650 and RFC 2358 .................... 42 84 B. Full Copyright Statement ................................... 43 86 1. Introduction 88 This memo defines a portion of the Management Information Base (MIB) 89 for use with network management protocols in the Internet community. 90 In particular, it defines objects for managing Ethernet-like 91 interfaces. 93 This memo also includes a MIB module. This MIB module extends the 94 list of managed objects specified in the earlier version of this MIB: 96 RFC 2358 [23]. 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in [26]. 102 2. The SNMP Management Framework 104 The SNMP Management Framework presently consists of five major 105 components: 107 o An overall architecture, described in RFC 2271 [1]. 109 o Mechanisms for describing and naming objects and events for the 110 purpose of management. The first version of this Structure of 111 Management Information (SMI) is called SMIv1 and described in 112 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 113 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 114 1904 [7]. 116 o Message protocols for transferring management information. The 117 first version of the SNMP message protocol is called SNMPv1 and 118 described in RFC 1157 [8]. A second version of the SNMP message 119 protocol, which is not an Internet standards track protocol, is 120 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 121 The third version of the message protocol is called SNMPv3 and 122 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 124 o Protocol operations for accessing management information. The 125 first set of protocol operations and associated PDU formats is 126 described in RFC 1157 [8]. A second set of protocol operations 127 and associated PDU formats is described in RFC 1905 [13]. 129 o A set of fundamental applications described in RFC 2273 [14] and 130 the view-based access control mechanism described in RFC 2275 131 [15]. 133 Managed objects are accessed via a virtual information store, termed 134 the Management Information Base or MIB. Objects in the MIB are 135 defined using the mechanisms defined in the SMI. 137 This memo specifies a MIB module that is compliant to the SMIv2. A 138 MIB conforming to the SMIv1 can be produced through the appropriate 139 translations. The resulting translated MIB must be semantically 140 equivalent, except where objects or events are omitted because no 141 translation is possible (use of Counter64). Some machine readable 142 information in SMIv2 will be converted into textual descriptions in 143 SMIv1 during the translation process. However, this loss of machine 144 readable information is not considered to change the semantics of the 145 MIB. 147 3. Overview 149 Instances of these object types represent attributes of an interface 150 to an ethernet-like communications medium. At present, ethernet-like 151 media are identified by the following values of the ifType object in 152 the Interfaces MIB [25]: 154 ethernetCsmacd(6) 155 iso88023Csmacd(7) 156 starLan(11) 158 The definitions presented here are based on Section 30, "10 Mb/s, 100 159 Mb/s and 1000 Mb/s Management", and Annex 30A, "GDMO Specification 160 for 802.3 managed object classes" of IEEE Std. 802.3, 1998 Edition 161 [16], as originally interpreted by Frank Kastenholz then of Interlan 162 in [17]. Implementors of these MIB objects should note that IEEE 163 Std. 802.3 [16] explicitly describes (in the form of Pascal 164 pseudocode) when, where, and how various MAC attributes are measured. 165 The IEEE document also describes the effects of MAC actions that may 166 be invoked by manipulating instances of the MIB objects defined here. 168 To the extent that some of the attributes defined in [16] are 169 represented by previously defined objects in MIB-2 [24] or in the 170 Interfaces MIB [25], such attributes are not redundantly represented 171 by objects defined in this memo. Among the attributes represented by 172 objects defined in other memos are the number of octets transmitted 173 or received on a particular interface, the number of frames 174 transmitted or received on a particular interface, the promiscuous 175 status of an interface, the MAC address of an interface, and 176 multicast information associated with an interface. 178 3.1. Relation to MIB-2 180 This section applies only when this MIB is used in conjunction with 181 the "old" (RFC 1213) [24] interface group. 183 The relationship between an ethernet-like interface and an interface 184 in the context of MIB-2 is one-to-one. As such, the value of an 185 ifIndex object instance can be directly used to identify 186 corresponding instances of the objects defined herein. 188 For agents which implement the (now deprecated) ifSpecific object, an 189 instance of that object that is associated with an ethernet-like 190 interface has the OBJECT IDENTIFIER value: 192 dot3 OBJECT IDENTIFER ::= { transmission 7 } 194 3.2. Relation to the Interfaces MIB 196 The Interface MIB [25] requires that any MIB which is an adjunct of 197 the Interface MIB clarify specific areas within the Interface MIB. 198 These areas were intentionally left vague in the Interface MIB to 199 avoid over constraining the MIB, thereby precluding management of 200 certain media-types. 202 Section 3.3 of [25] enumerates several areas which a media-specific 203 MIB must clarify. Each of these areas is addressed in a following 204 subsection. The implementor is referred to [25] in order to 205 understand the general intent of these areas. 207 3.2.1. Layering Model 209 This MIB does not provide for layering. There are no sublayers. 211 EDITOR'S NOTE: 213 One could foresee the development of an 802.2 and enet-transceiver 214 MIB. They could be higher and lower sublayers, respectively. All 215 that THIS document should do is allude to the possibilities and urge 216 the implementor to be aware of the possibility and that they may have 217 requirements which supersede the requirements in this document. 219 3.2.2. Virtual Circuits 221 This medium does not support virtual circuits and this area is not 222 applicable to this MIB. 224 3.2.3. ifTestTable 226 This MIB defines two tests for media which are instrumented with this 227 MIB; TDR and Loopback. Implementation of these tests is not 228 required. Many common interface chips do not support one or both of 229 these tests. 231 These two tests are provided as a convenience, allowing a common 232 method to invoke the test. 234 Standard MIBs do not include objects in which to return the results 235 of the TDR test. Any needed objects MUST be provided in the vendor 236 specific MIB. 238 Note that the ifTestTable is now deprecated. Work is underway to 239 define a replacement MIB for system and interface testing. It is 240 expected that the tests defined in this document will be usable in 241 this replacement MIB. 243 3.2.4. ifRcvAddressTable 245 This table contains all IEEE 802.3 addresses, unicast, multicast, and 246 broadcast, for which this interface will receive packets and forward 247 them up to a higher layer entity for local consumption. The format 248 of the address, contained in ifRcvAddressAddress, is the same as for 249 ifPhysAddress. 251 In the event that the interface is part of a MAC bridge, this table 252 does not include unicast addresses which are accepted for possible 253 forwarding out some other port. This table is explicitly not 254 intended to provide a bridge address filtering mechanism. 256 3.2.5. ifPhysAddress 258 This object contains the IEEE 802.3 address which is placed in the 259 source-address field of any Ethernet, Starlan, or IEEE 802.3 frames 260 that originate at this interface. Usually this will be kept in ROM 261 on the interface hardware. Some systems may set this address via 262 software. 264 In a system where there are several such addresses the designer has a 265 tougher choice. The address chosen should be the one most likely to 266 be of use to network management (e.g. the address placed in ARP 267 responses for systems which are primarily IP systems). 269 If the designer truly can not chose, use of the factory- provided ROM 270 address is suggested. 272 If the address can not be determined, an octet string of zero length 273 should be returned. 275 The address is stored in binary in this object. The address is 276 stored in "canonical" bit order, that is, the Group Bit is positioned 277 as the low-order bit of the first octet. Thus, the first byte of a 278 multicast address would have the bit 0x01 set. 280 3.2.6. ifType 282 This MIB applies to interfaces which have any of the following ifType 283 values: 285 ethernetCsmacd(6) 286 iso88023Csmacd(7) 287 starLan(11) 289 It is RECOMMENDED that all Ethernet-like interfaces use an ifType of 290 ethernetCsmacd(6) regardless of the speed that the interface is 291 running or the link-layer encapsulation in use. iso88023Csmacd(7) 292 and starLan(11) are supported for backwards compatability. 294 There are three other interface types defined in the IANAifType-MIB 295 for Ethernet. They are fastEther(62), fastEtherFX(69), and 296 gigabitEthernet(117). This document takes the position that an 297 Ethernet is an Ethernet, and Ethernet interfaces SHOULD always have 298 the same value of ifType. Information on the particular flavor of 299 Ethernet that an interface is running is available from ifSpeed in 300 the Interfaces MIB, and ifMauType in the 802.3 MAU MIB. An 301 Ethernet-like interface SHOULD NOT use the fastEther(62), 302 fastEtherFX(69), or gigabitEthernet(117) ifTypes. 304 Interfaces with any of the supported ifType values map to the 305 EtherLike-MIB in the same manner. There are no implementation 306 differences. 308 3.2.7. Specific Interface MIB Objects 310 The following table provides specific implementation guidelines for 311 applying the interface group objects to ethernet-like media. 313 Object 315 ifIndex Each ethernet-like interface is 316 represented by an ifEntry. The 317 dot3StatsTable in this MIB module is 318 indexed by dot3StatsIndex. The interface 319 identified by a particular value of 320 dot3StatsIndex is the same interface as 321 identified by the same value of ifIndex. 323 ifDescr Refer to [25]. 325 ifType Refer to section 3.2.6. 327 ifMtu 1500 octets. NOTE: This is the MTU as 328 seen by the MAC client. When a higher 329 layer protocol, like IP, is running over 330 Ethernet, this is the MTU that will be 331 seen by that higher layer protocol. 332 However, when using the IEEE 802.2 LLC 333 protocol, higher layer protocols will 334 see a different MTU. In particular, an 335 LLC type 1 client protocol will see 336 an MTU of 1497 octets, and a protocol 337 running over SNAP will see an MTU of 338 1492 octets. 340 ifSpeed The current operational speed of the 341 interface in bits per second. For 342 current ethernet-like interfaces, this 343 will be equal to 1,000,000 (1 million), 344 10,000,000 (10 million), 100,000,000 345 (100 million), or 1,000,000,000 (1 346 billion). If the interface implements 347 auto-negotiation, auto-negotiation is 348 enabled for this interface, and the 349 interface has not yet negotiated to an 350 operational speed, this object SHOULD 351 reflect the maximum speed supported by 352 the interface. Note that this object 353 MUST NOT indicate a doubled value when 354 operating in full-duplex mode. It MUST 355 indicate the correct line speed 356 regardless of the current duplex mode. 357 The duplex mode of the interface may 358 be determined by examining either the 359 dot3StatsDuplexStatus object in this 360 MIBmodule, or the ifMauType object in 361 the 802.3 MAU MIB. 363 ifPhysAddress Refer to section 3.2.5. 365 ifAdminStatus Write access is not required. Support 366 for 'testing' is not required. 368 ifOperStatus The operational state of the interface. 369 Support for 'testing' is not required. 370 The value 'dormant' has no meaning for 371 an ethernet-like interface. 373 ifLastChange Refer to [25]. 375 ifInOctets The number of octets in valid MAC frames 376 received on this interface, including 377 the MAC header and FCS. 379 ifInUcastPkts Refer to [25]. 381 ifInDiscards Refer to [25]. 383 ifInErrors The sum for this interface of 384 dot3StatsAlignmentErrors, 385 dot3StatsFCSErrors, 386 dot3StatsFrameTooLongs, 387 dot3StatsInternalMacReceiveErrors and 388 dot3StatsSymbolErrors. 390 ifInUnknownProtos Refer to [25]. 392 ifOutOctets The number of octets transmitted in 393 valid MAC frames on this interface, 394 including the MAC header and FCS. 396 ifOutUcastPkts Refer to [25]. 398 ifOutDiscards Refer to [25]. 400 ifOutErrors The sum for this interface of: 401 dot3StatsSQETestErrors, 402 dot3StatsLateCollisions, 403 dot3StatsExcessiveCollisions, 404 dot3StatsInternalMacTransmitErrors and 405 dot3StatsCarrierSenseErrors. 407 ifName Locally-significant textual name for the 408 interface (e.g. lan0). 410 ifInMulticastPkts Refer to [25]. 412 ifInBroadcastPkts Refer to [25]. 414 ifOutMulticastPkts Refer to [25]. 416 ifOutBroadcastPkts Refer to [25]. 418 ifHCInOctets 64-bit versions of counters. Required 419 ifHCOutOctets for ethernet-like interfaces that are 420 capable of operating at 20Mbit/sec or 421 faster, even if the interface is 422 currently operating at less than 423 20Mbit/sec. 425 ifHCInUcastPkts 64-bit versions of packet counters. 426 ifHCInMulticastPkts Required for ethernet-like interfaces 427 ifHCInBroadcastPkts that are capable of operating at 428 ifHCOutUcastPkts 640Mbit/sec or faster, even if the 429 ifHCOutMulticastPkts interface is currently operating at 430 ifHCOutBroadcastPkts less than 640Mbit/sec. 432 ifLinkUpDownTrapEnable Refer to [25]. Default is 'enabled' 434 ifHighSpeed The current operational speed of the 435 interface in millions of bits per 436 second. For current ethernet-like 437 interfaces, this will be equal to 1, 10, 438 100, or 1,000. If the interface 439 implements auto-negotiation, 440 auto-negotiation is enabled for this 441 interface, and the interface has not yet 442 negotiated to an operational speed, this 443 object SHOULD reflect the maximum speed 444 supported by the interface. Note that 445 this object MUST NOT indicate a doubled 446 value when operating in full-duplex 447 mode. It MUST indicate the correct line 448 speed regardless of the current duplex 449 mode. The duplex mode of the interface 450 may be determined by examining either 451 the dot3StatsDuplexStatus object in this 452 MIB module, or the ifMauType object in 453 the 802.3 MAU MIB. 455 ifPromiscuousMode Refer to [25]. 457 ifConnectorPresent This will normally be 'true'. 459 ifAlias Refer to [25]. 461 ifCounterDiscontinuityTime Refer to [25]. 463 ifStackHigherLayer Refer to section 3.2.1. 464 ifStackLowerLayer 465 ifStackStatus 467 ifRcvAddressAddress Refer to section 3.2.4. 468 ifRcvAddressStatus 469 ifRcvAddressType 471 3.3. Relation to the 802.3 MAU MIB 473 Support for the mauModIfCompl2 compliance statement of the MAU-MIB 474 [27] is REQUIRED for Ethernet-like interfaces. This MIB is needed in 475 order to allow applications to determine the current MAU type in use 476 by the interface, and to control autonegotiation and duplex mode for 477 the interface. Implementing this MIB module without implementing the 478 MAU-MIB would leave applications with no standard way to determine 479 the media type in use, and no standard way to control the duplex mode 480 of the interface. 482 3.4. dot3StatsEtherChipSet 484 This document defines an object called dot3StatsEtherChipSet, which 485 is used to identify the MAC hardware used to communicate on an 486 interface. Previous versions of this document contained a number of 487 OID assignments for some existing Ethernet chipsets. Maintaining 488 that list as part of this document has proven to be problematic, so 489 the OID assignments contained in prevous versions of this document 490 have now been moved to a separate document [28]. That document also 491 contains information on future management of chipset OID assignments. 493 3.5. Mapping of IEEE 802.3 Managed Objects 495 IEEE 802.3 Managed Object Corresponding SNMP Object 497 oMacEntity 498 .aMACID dot3StatsIndex or 499 IF-MIB - ifIndex 500 .aFramesTransmittedOK IF-MIB - ifOutUCastPkts + 501 ifOutMulticastPkts + 502 ifOutBroadcastPkts 503 .aSingleCollisionFrames dot3StatsSingleCollisionFrames 504 .aMultipleCollisionFrames dot3StatsMultipleCollisionFrames 505 .aFramesReceivedOK IF-MIB - ifInUcastPkts + 506 ifInMulticastPkts + 507 ifInBroadcastPkts 508 .aFrameCheckSequenceErrors dot3StatsFCSErrors 509 .aAlignmentErrors dot3StatsAlignmentErrors 510 .aOctetsTransmittedOK IF-MIB - ifOutOctets* 511 .aFramesWithDeferredXmissions dot3StatsDeferredTransmissions 512 .aLateCollisions dot3StatsLateCollisions 513 .aFramesAbortedDueToXSColls dot3StatsExcessiveCollisions 514 .aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors 515 .aCarrierSenseErrors dot3StatsCarrierSenseErrors 516 .aOctetsReceivedOK IF-MIB - ifInOctets* 517 .aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors 518 .aPromiscuousStatus IF-MIB - ifPromiscuousMode 519 .aReadMulticastAddressList IF-MIB - ifRcvAddressTable 520 .aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts 521 .aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts 522 .aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts 523 .aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts 524 .aFrameTooLongErrors dot3StatsFrameTooLongs 525 .aReadWriteMACAddress IF-MIB - ifPhysAddress 526 .aCollisionFrames dot3CollFrequencies 527 .aDuplexStatus dot3StatsDuplexStatus 528 .acAddGroupAddress IF-MIB - ifRcvAddressTable 529 .acDeleteGroupAddress IF-MIB - ifRcvAddressTable 530 .acExecuteSelfTest dot3TestLoopBack 532 oPHYEntity 533 .aPHYID dot3StatsIndex or 534 IF-MIB - ifIndex 535 .aSQETestErrors dot3StatsSQETestErrors 536 .aSymbolErrorDuringCarrier dot3StatsSymbolErrors 538 oMACControlEntity 539 .aMACControlID dot3StatsIndex or 540 IF-MIB - ifIndex 541 .aMACControlFunctionsSupported dot3ControlFunctionsSupported and 542 dot3ControlFunctionsEnabled 543 .aUnsupportedOpcodesReceived dot3ControlInUnknownOpcodes 545 oPAUSEEntity 546 .aPAUSELinkDelayAllowance dot3PauseLinkDelayAllowance 547 .aPAUSEMACCtrlFramesTransmitted dot3OutPauseFrames 548 .aPAUSEMACCtrlFramesReceived dot3InPauseFrames 550 * Note that the octet counters in IF-MIB do not exactly match the 551 definition of the octet counters in IEEE 802.3. aOctetsTransmittedOK 552 and aOctetsReceivedOK count only the octets in the clientData and Pad 553 fields, whereas ifInOctets and ifOutOctets include the entire MAC 554 frame, including MAC header and FCS. However, the IF-MIB counters 555 can be derived from the IEEE 802.3 counters as follows: 557 ifInOctets = aOctetsReceivedOK + (18 * aFramesReceivedOK) 558 ifOutOctets = aOctetsTransmittedOK + (18 * aFramesTransmittedOK) 560 The following IEEE 802.3 managed objects have been removed from this 561 MIB module as a result of implementation feedback: 563 oMacEntity 564 .aFramesWithExcessiveDeferral 565 .aInRangeLengthErrors 566 .aOutOfRangeLengthField 567 .aMACEnableStatus 568 .aTransmitEnableStatus 569 .aMulticastReceiveStatus 570 .acInitializeMAC 572 Please see [19] for the detailed reasoning on why these objects were 573 removed. 575 In addition, the following IEEE 802.3 managed objects have not been 576 included in this MIB for the following reasons. 578 IEEE 802.3 Managed Object Disposition 580 oMACEntity 581 .aMACCapabilities Can be derived from 582 MAU-MIB - ifMauTypeListBits 584 oPHYEntity 585 .aPhyType Can be derived from 586 MAU-MIB - ifMauType 588 .aPhyTypeList Can be derived from 589 MAU-MIB - ifMauTypeListBits 591 .aMIIDetect Not considered useful. 593 .aPhyAdminState Can already obtain interface 594 state from IF-MIB - ifOperStatus 595 and MAU state from MAU-MIB - 596 ifMauStatus. Providing an 597 additional state for the PHY 598 was not considered useful. 600 .acPhyAdminControl Can already control interface 601 state from IF-MIB - ifAdminStatus 602 and MAU state from MAU-MIB - 603 ifMauStatus. Providing separate 604 admin control of the PHY was not 605 considered useful. 607 oMACControlEntity 608 .aMACControlFramesTransmitted Can be determined by summing the 609 OutFrames counters for the 610 individual control functions 612 .aMACControlFramesReceived Can be determined by summing the 613 InFrames counters for the 614 individual control functions 616 4. Definitions 618 EtherLike-MIB DEFINITIONS ::= BEGIN 620 IMPORTS 621 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, 622 Counter32, Unsigned32, mib-2, transmission 623 FROM SNMPv2-SMI 624 MODULE-COMPLIANCE, OBJECT-GROUP 625 FROM SNMPv2-CONF 626 ifIndex, InterfaceIndex 627 FROM IF-MIB; 629 etherMIB MODULE-IDENTITY 630 LAST-UPDATED "9811172346Z" -- November 17, 1998 631 ORGANIZATION "IETF 802.3 Hub MIB Working Group" 632 CONTACT-INFO 633 "WG E-mail: hubmib@hprnd.rose.hp.com 634 To subscribe: hubmib-request@hprnd.rose.hp.com 636 Chair: Dan Romascanu 637 Postal: LANNET Ltd. 638 Atidum Technology Park, Bldg. 3 639 Tel Aviv 61131 640 Israel 641 Tel: +972 3 645 8414 642 E-mail: dromasca@lannet.com 644 Editor: John Flick 645 Postal: Hewlett-Packard Company 646 8000 Foothills Blvd. M/S 5556 647 Roseville, CA 95747-5556 648 USA 649 Tel: +1 916 785 4018 650 Fax: +1 916 785 3583 651 E-mail: johnf@rose.hp.com 653 Editor: Jeffrey Johnson 654 Postal: RedBack Networks 655 2570 North First Street, Suite 410 656 San Jose, CA, 95131 657 USA 658 Tel: +1 408 571 2699 659 Fax: +1 408 571 2698 660 E-Mail: jeff@redbacknetworks.com" 662 DESCRIPTION "The MIB module to describe generic objects for 663 Ethernet-like network interfaces. 665 The following reference is used throughout this 666 MIB module: 668 [IEEE 802.3 Std] refers to: 669 IEEE Std 802.3, 1998 Edition: 'Information 670 technology - Telecommunications and 671 information exchange between systems - 672 Local and metropolitan area networks - 673 Specific requirements - Part 3: Carrier 674 sense multiple access with collision 675 detection (CSMA/CD) access method and 676 physical layer specifications', 677 September 1998. 679 Of particular interest is Clause 30, '10Mb/s, 680 100Mb/s and 1000Mb/s Management'." 682 REVISION "9811172346Z" -- November 17, 1998 683 DESCRIPTION "Updated to include support for 1000 Mb/sec 684 interfaces and full-duplex interfaces." 686 REVISION "9806032150Z" -- June 3, 1998 687 DESCRIPTION "Updated to include support for 100 Mb/sec 688 interfaces. Published as RFC 2358." 690 REVISION "9402030400Z" -- February 3, 1994 691 DESCRIPTION "Version published as RFC 1650." 692 ::= { mib-2 35 } 694 etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 } 696 dot3 OBJECT IDENTIFIER ::= { transmission 7 } 698 -- the Ethernet-like Statistics group 700 dot3StatsTable OBJECT-TYPE 701 SYNTAX SEQUENCE OF Dot3StatsEntry 702 MAX-ACCESS not-accessible 703 STATUS current 704 DESCRIPTION "Statistics for a collection of ethernet-like 705 interfaces attached to a particular system." 706 ::= { dot3 2 } 708 dot3StatsEntry OBJECT-TYPE 709 SYNTAX Dot3StatsEntry 710 MAX-ACCESS not-accessible 711 STATUS current 712 DESCRIPTION "Statistics for a particular interface to an 713 ethernet-like medium." 714 INDEX { dot3StatsIndex } 715 ::= { dot3StatsTable 1 } 717 Dot3StatsEntry ::= 718 SEQUENCE { 719 dot3StatsIndex InterfaceIndex, 720 dot3StatsAlignmentErrors Counter32, 721 dot3StatsFCSErrors Counter32, 722 dot3StatsSingleCollisionFrames Counter32, 723 dot3StatsMultipleCollisionFrames Counter32, 724 dot3StatsSQETestErrors Counter32, 725 dot3StatsDeferredTransmissions Counter32, 726 dot3StatsLateCollisions Counter32, 727 dot3StatsExcessiveCollisions Counter32, 728 dot3StatsInternalMacTransmitErrors Counter32, 729 dot3StatsCarrierSenseErrors Counter32, 730 dot3StatsFrameTooLongs Counter32, 731 dot3StatsInternalMacReceiveErrors Counter32, 732 dot3StatsEtherChipSet OBJECT IDENTIFIER, 733 dot3StatsSymbolErrors Counter32, 734 dot3StatsDuplexStatus INTEGER 735 } 737 dot3StatsIndex OBJECT-TYPE 738 SYNTAX InterfaceIndex 739 MAX-ACCESS read-only 740 STATUS current 741 DESCRIPTION "An index value that uniquely identifies an 742 interface to an ethernet-like medium. The 743 interface identified by a particular value of 744 this index is the same interface as identified 745 by the same value of ifIndex." 746 REFERENCE "RFC 2233, ifIndex" 747 ::= { dot3StatsEntry 1 } 749 dot3StatsAlignmentErrors OBJECT-TYPE 750 SYNTAX Counter32 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION "A count of frames received on a particular 754 interface that are not an integral number of 755 octets in length and do not pass the FCS check. 757 The count represented by an instance of this 758 object is incremented when the alignmentError 759 status is returned by the MAC service to the 760 LLC (or other MAC user). Received frames for 761 which multiple error conditions obtain are, 762 according to the conventions of IEEE 802.3 763 Layer Management, counted exclusively according 764 to the error status presented to the LLC. 766 This counter does not increment for 8-bit wide 767 group encoding schemes." 768 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7, 769 aAlignmentErrors" 770 ::= { dot3StatsEntry 2 } 772 dot3StatsFCSErrors OBJECT-TYPE 773 SYNTAX Counter32 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION "A count of frames received on a particular 777 interface that are an integral number of octets 778 in length but do not pass the FCS check. This 779 count does not include frames received with 780 frame-too-long or frame-too-short error. 782 The count represented by an instance of this 783 object is incremented when the frameCheckError 784 status is returned by the MAC service to the 785 LLC (or other MAC user). Received frames for 786 which multiple error conditions obtain are, 787 according to the conventions of IEEE 802.3 788 Layer Management, counted exclusively according 789 to the error status presented to the LLC. 791 Note: Coding errors detected by the physical 792 layer for speeds above 10 Mb/s will cause the 793 frame to fail the FCS check." 794 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6, 795 aFrameCheckSequenceErrors." 796 ::= { dot3StatsEntry 3 } 798 dot3StatsSingleCollisionFrames OBJECT-TYPE 799 SYNTAX Counter32 800 MAX-ACCESS read-only 801 STATUS current 802 DESCRIPTION "A count of successfully transmitted frames on 803 a particular interface for which transmission 804 is inhibited by exactly one collision. 806 A frame that is counted by an instance of this 807 object is also counted by the corresponding 808 instance of either the ifOutUcastPkts, 809 ifOutMulticastPkts, or ifOutBroadcastPkts, 810 and is not counted by the corresponding 811 instance of the dot3StatsMultipleCollisionFrames 812 object. 814 This counter does not increment when the 815 interface is operating in full-duplex mode." 816 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.3, 817 aSingleCollisionFrames." 818 ::= { dot3StatsEntry 4 } 820 dot3StatsMultipleCollisionFrames OBJECT-TYPE 821 SYNTAX Counter32 822 MAX-ACCESS read-only 823 STATUS current 824 DESCRIPTION "A count of successfully transmitted frames on 825 a particular interface for which transmission 826 is inhibited by more than one collision. 828 A frame that is counted by an instance of this 829 object is also counted by the corresponding 830 instance of either the ifOutUcastPkts, 831 ifOutMulticastPkts, or ifOutBroadcastPkts, 832 and is not counted by the corresponding 833 instance of the dot3StatsSingleCollisionFrames 834 object. 836 This counter does not increment when the 837 interface is operating in full-duplex mode." 838 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.4, 839 aMultipleCollisionFrames." 840 ::= { dot3StatsEntry 5 } 842 dot3StatsSQETestErrors OBJECT-TYPE 843 SYNTAX Counter32 844 MAX-ACCESS read-only 845 STATUS current 846 DESCRIPTION "A count of times that the SQE TEST ERROR 847 message is generated by the PLS sublayer for a 848 particular interface. The SQE TEST ERROR 849 is set in accordance with the rules for 850 verification of the SQE detection mechanism in 851 the PLS Carrier Sense Function as described in 852 IEEE Std. 802.3, 1998 Edition, section 7.2.4.6. 854 This counter does not increment on interfaces 855 operating at speeds greater than 10 Mb/s, or on 856 interfaces operating in full-duplex mode." 857 REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4, 858 aSQETestErrors." 859 ::= { dot3StatsEntry 6 } 861 dot3StatsDeferredTransmissions OBJECT-TYPE 862 SYNTAX Counter32 863 MAX-ACCESS read-only 864 STATUS current 865 DESCRIPTION "A count of frames for which the first 866 transmission attempt on a particular interface 867 is delayed because the medium is busy. 869 The count represented by an instance of this 870 object does not include frames involved in 871 collisions. 873 This counter does not increment when the 874 interface is operating in full-duplex mode." 875 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.9, 876 aFramesWithDeferredXmissions." 877 ::= { dot3StatsEntry 7 } 879 dot3StatsLateCollisions OBJECT-TYPE 880 SYNTAX Counter32 881 MAX-ACCESS read-only 882 STATUS current 883 DESCRIPTION "The number of times that a collision is 884 detected on a particular interface later than 885 one slotTime into the transmission of a packet. 887 A (late) collision included in a count 888 represented by an instance of this object is 889 also considered as a (generic) collision for 890 purposes of other collision-related 891 statistics. 893 This counter does not increment when the 894 interface is operating in full-duplex mode." 896 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.10, 897 aLateCollisions." 898 ::= { dot3StatsEntry 8 } 900 dot3StatsExcessiveCollisions OBJECT-TYPE 901 SYNTAX Counter32 902 MAX-ACCESS read-only 903 STATUS current 904 DESCRIPTION "A count of frames for which transmission on a 905 particular interface fails due to excessive 906 collisions. 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.11, 911 aFramesAbortedDueToXSColls." 912 ::= { dot3StatsEntry 9 } 914 dot3StatsInternalMacTransmitErrors 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 an internal 920 MAC sublayer transmit error. A frame is only 921 counted by an instance of this object if it is 922 not counted by the corresponding instance of 923 either the dot3StatsLateCollisions object, the 924 dot3StatsExcessiveCollisions object, or the 925 dot3StatsCarrierSenseErrors object. 927 The precise meaning of the count represented by 928 an instance of this object is implementation- 929 specific. In particular, an instance of this 930 object may represent a count of transmission 931 errors on a particular interface that are not 932 otherwise counted." 933 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12, 934 aFramesLostDueToIntMACXmitError." 935 ::= { dot3StatsEntry 10 } 937 dot3StatsCarrierSenseErrors OBJECT-TYPE 938 SYNTAX Counter32 939 MAX-ACCESS read-only 940 STATUS current 941 DESCRIPTION "The number of times that the carrier sense 942 condition was lost or never asserted when 943 attempting to transmit a frame on a particular 944 interface. 946 The count represented by an instance of this 947 object is incremented at most once per 948 transmission attempt, even if the carrier sense 949 condition fluctuates during a transmission 950 attempt. 952 This counter does not increment when the 953 interface is operating in full-duplex mode." 954 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.13, 955 aCarrierSenseErrors." 956 ::= { dot3StatsEntry 11 } 958 -- { dot3StatsEntry 12 } is not assigned 960 dot3StatsFrameTooLongs OBJECT-TYPE 961 SYNTAX Counter32 962 MAX-ACCESS read-only 963 STATUS current 964 DESCRIPTION "A count of frames received on a particular 965 interface that exceed the maximum permitted 966 frame size. 968 The count represented by an instance of this 969 object is incremented when the frameTooLong 970 status is returned by the MAC service to the 971 LLC (or other MAC user). Received frames for 972 which multiple error conditions obtain are, 973 according to the conventions of IEEE 802.3 974 Layer Management, counted exclusively according 975 to the error status presented to the LLC." 976 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25, 977 aFrameTooLongErrors." 978 ::= { dot3StatsEntry 13 } 980 -- { dot3StatsEntry 14 } is not assigned 982 -- { dot3StatsEntry 15 } is not assigned 984 dot3StatsInternalMacReceiveErrors OBJECT-TYPE 985 SYNTAX Counter32 986 MAX-ACCESS read-only 987 STATUS current 988 DESCRIPTION "A count of frames for which reception on a 989 particular interface fails due to an internal 990 MAC sublayer receive error. A frame is only 991 counted by an instance of this object if it is 992 not counted by the corresponding instance of 993 either the dot3StatsFrameTooLongs object, the 994 dot3StatsAlignmentErrors object, or the 995 dot3StatsFCSErrors object. 997 The precise meaning of the count represented by 998 an instance of this object is implementation- 999 specific. In particular, an instance of this 1000 object may represent a count of receive errors 1001 on a particular interface that are not 1002 otherwise counted." 1003 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15, 1004 aFramesLostDueToIntMACRcvError." 1005 ::= { dot3StatsEntry 16 } 1007 dot3StatsEtherChipSet OBJECT-TYPE 1008 SYNTAX OBJECT IDENTIFIER 1009 MAX-ACCESS read-only 1010 STATUS current 1011 DESCRIPTION "This object contains an OBJECT IDENTIFIER 1012 which identifies the chipset used to 1013 realize the interface. Ethernet-like 1014 interfaces are typically built out of 1015 several different chips. The MIB implementor 1016 is presented with a decision of which chip 1017 to identify via this object. The implementor 1018 should identify the chip which is usually 1019 called the Medium Access Control chip. 1020 If no such chip is easily identifiable, 1021 the implementor should identify the chip 1022 which actually gathers the transmit 1023 and receive statistics and error 1024 indications. This would allow a 1025 manager station to correlate the 1026 statistics and the chip generating 1027 them, giving it the ability to take 1028 into account any known anomalies 1029 in the chip." 1030 ::= { dot3StatsEntry 17 } 1032 dot3StatsSymbolErrors OBJECT-TYPE 1033 SYNTAX Counter32 1034 MAX-ACCESS read-only 1035 STATUS current 1036 DESCRIPTION "For an interface operating at 100 Mb/s, the 1037 number of times there was an invalid data symbol 1038 when a valid carrier was present. 1040 For an interface operating in half-duplex mode 1041 at 1000 Mb/s, the number of times the receiving 1042 media is non-idle (a carrier event) for a period 1043 of time equal to or greater than slotTime, and 1044 during which there was at least one occurrence 1045 of an event that causes the PHY to indicate 1046 'Data reception error' or 'carrier extend error' 1047 on the GMII. 1049 For an interface operating in full-duplex mode 1050 at 1000 Mb/s, the number of times the receiving 1051 media is non-idle a carrier event) for a period 1052 of time equal to or greater than minFrameSize, 1053 and during which there was at least one 1054 occurrence of an event that causes the PHY to 1055 indicate 'Data reception error' on the GMII. 1057 The count represented by an instance of this 1058 object is incremented at most once per carrier 1059 event, even if multiple symbol errors occur 1060 during the carrier event. This count does 1061 not increment if a collision is present." 1062 REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, 1063 aSymbolErrorDuringCarrier." 1064 ::= { dot3StatsEntry 18 } 1066 dot3StatsDuplexStatus OBJECT-TYPE 1067 SYNTAX INTEGER { 1068 unknown(1), 1069 halfDuplex(2), 1070 fullDuplex(3) 1071 } 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION "The current mode of operation of the MAC 1075 entity. 'unknown' indicates that the current 1076 duplex mode could not be determined. 1078 Management control of the duplex mode is 1079 accomplished through the MAU MIB. When 1080 an interface does not support autonegotiation, 1081 or when autonegotiation is not enabled, the 1082 duplex mode is controlled using 1083 ifMauDefaultType. When autonegotiation is 1084 supported and enabled, duplex mode is controlled 1085 using ifMauAutoNegAdvertisedBits. In either 1086 case, the currently operating duplex mode is 1087 reflected both in this object and in ifMauType." 1089 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32, 1090 aDuplexStatus." 1091 ::= { dot3StatsEntry 19 } 1093 -- the Ethernet-like Collision Statistics group 1095 -- Implementation of this group is optional; it is appropriate 1096 -- for all systems which have the necessary metering 1098 dot3CollTable OBJECT-TYPE 1099 SYNTAX SEQUENCE OF Dot3CollEntry 1100 MAX-ACCESS not-accessible 1101 STATUS current 1102 DESCRIPTION "A collection of collision histograms for a 1103 particular set of interfaces." 1104 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.30, 1105 aCollisionFrames." 1106 ::= { dot3 5 } 1108 dot3CollEntry OBJECT-TYPE 1109 SYNTAX Dot3CollEntry 1110 MAX-ACCESS not-accessible 1111 STATUS current 1112 DESCRIPTION "A cell in the histogram of per-frame 1113 collisions for a particular interface. An 1114 instance of this object represents the 1115 frequency of individual MAC frames for which 1116 the transmission (successful or otherwise) on a 1117 particular interface is accompanied by a 1118 particular number of media collisions." 1119 INDEX { ifIndex, dot3CollCount } 1120 ::= { dot3CollTable 1 } 1122 Dot3CollEntry ::= 1123 SEQUENCE { 1124 dot3CollCount INTEGER, 1125 dot3CollFrequencies Counter32 1126 } 1128 -- { dot3CollEntry 1 } is no longer in use 1130 dot3CollCount OBJECT-TYPE 1131 SYNTAX INTEGER (1..16) 1132 MAX-ACCESS not-accessible 1133 STATUS current 1134 DESCRIPTION "The number of per-frame media collisions for 1135 which a particular collision histogram cell 1136 represents the frequency on a particular 1137 interface." 1138 ::= { dot3CollEntry 2 } 1140 dot3CollFrequencies OBJECT-TYPE 1141 SYNTAX Counter32 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION "A count of individual MAC frames for which the 1145 transmission (successful or otherwise) on a 1146 particular interface occurs after the 1147 frame has experienced exactly the number 1148 of collisions in the associated 1149 dot3CollCount object. 1151 For example, a frame which is transmitted 1152 on interface 77 after experiencing 1153 exactly 4 collisions would be indicated 1154 by incrementing only dot3CollFrequencies.77.4. 1155 No other instance of dot3CollFrequencies would 1156 be incremented in this example. 1158 This counter does not increment when the 1159 interface is operating in full-duplex mode." 1160 ::= { dot3CollEntry 3 } 1162 dot3ControlTable OBJECT-TYPE 1163 SYNTAX SEQUENCE OF Dot3ControlEntry 1164 MAX-ACCESS not-accessible 1165 STATUS current 1166 DESCRIPTION "A table of descriptive and status information 1167 about the MAC Control sublayer on the 1168 ethernet-like interfaces attached to a 1169 particular system." 1170 ::= { dot3 9 } 1172 dot3ControlEntry OBJECT-TYPE 1173 SYNTAX Dot3ControlEntry 1174 MAX-ACCESS not-accessible 1175 STATUS current 1176 DESCRIPTION "An entry in the table, containing information 1177 about the MAC Control sublayer on a single 1178 ethernet-like interface." 1179 INDEX { dot3StatsIndex } 1180 ::= { dot3ControlTable 1 } 1182 Dot3ControlEntry ::= 1183 SEQUENCE { 1184 dot3ControlFunctionsSupported BITS, 1185 dot3ControlInUnknownOpcodes Counter32 1186 } 1188 dot3ControlFunctionsSupported OBJECT-TYPE 1189 SYNTAX BITS { 1190 pause(0) 1191 } 1192 MAX-ACCESS read-only 1193 STATUS current 1194 DESCRIPTION "A list of the possible MAC Control functions 1195 implemented for this interface." 1196 REFERENCE "[IEEE 802.3 Std.], 30.3.3.2, 1197 aMACControlFunctionsSupported." 1198 ::= { dot3ControlEntry 1 } 1200 dot3ControlInUnknownOpcodes OBJECT-TYPE 1201 SYNTAX Counter32 1202 MAX-ACCESS read-only 1203 STATUS current 1204 DESCRIPTION "A count of MAC Control frames received on this 1205 interface that contain an opcode that is not 1206 supported by this device." 1207 REFERENCE "[IEEE 802.3 Std.], 30.3.3.5, 1208 aUnsupportedOpcodesReceived" 1209 ::= { dot3ControlEntry 2 } 1211 dot3PauseTable OBJECT-TYPE 1212 SYNTAX SEQUENCE OF Dot3PauseEntry 1213 MAX-ACCESS not-accessible 1214 STATUS current 1215 DESCRIPTION "A table of descriptive and status information 1216 about the MAC Control PAUSE function on the 1217 ethernet-like interfaces attached to a 1218 particular system." 1219 ::= { dot3 10 } 1221 dot3PauseEntry OBJECT-TYPE 1222 SYNTAX Dot3PauseEntry 1223 MAX-ACCESS not-accessible 1224 STATUS current 1225 DESCRIPTION "An entry in the table, containing information 1226 about the MAC Control PAUSE function on a single 1227 ethernet-like interface." 1228 INDEX { dot3StatsIndex } 1229 ::= { dot3PauseTable 1 } 1231 Dot3PauseEntry ::= 1232 SEQUENCE { 1233 dot3PauseAdminMode INTEGER, 1234 dot3PauseOperMode INTEGER, 1235 dot3PauseLinkDelayAllowance Unsigned32, 1236 dot3InPauseFrames Counter32, 1237 dot3OutPauseFrames Counter32 1238 } 1240 dot3PauseAdminMode OBJECT-TYPE 1241 SYNTAX INTEGER { 1242 disabled(1), 1243 enabledXmit(2), 1244 enabledRcv(3), 1245 enabledXmitAndRcv(4) 1246 } 1247 MAX-ACCESS read-write 1248 STATUS current 1249 DESCRIPTION "This object is used to configure the default 1250 administrative PAUSE mode for this interface. 1252 This object represents the 1253 administratively-configured PAUSE mode for this 1254 interface. If auto-negotiation is not enabled 1255 or is not implemented for the active MAU 1256 attached to this interface, the value of this 1257 object determines the operational PAUSE mode 1258 of the interface whenever it is operating in 1259 full-duplex mode. In this case, a set to this 1260 object will force the interface into the 1261 specified mode. 1263 If auto-negotiation is implemented and enabled 1264 for the MAU attached to this interface, the 1265 PAUSE mode for this interface is determined by 1266 auto-negotiation, and the value of this object 1267 denotes the mode to which the interface will 1268 automatically revert if/when auto-negotiation is 1269 later disabled. Note that when auto-negotiation 1270 is running, administrative control of the PAUSE 1271 mode may be accomplished using the 1272 ifMauAutoNegCapAdvertisedBits object in the 1273 MAU-MIB. 1275 Note that the value of this object is ignored 1276 when the interface is not operating in 1277 full-duplex mode. 1279 An attempt to set this object to 1280 'enabledXmit(2)' or 'enabledRcv(3)' will fail 1281 on interfaces that do not support operation 1282 at greater than 100 Mb/s." 1283 ::= { dot3PauseEntry 1 } 1285 dot3PauseOperMode OBJECT-TYPE 1286 SYNTAX INTEGER { 1287 disabled(1), 1288 enabledXmit(2), 1289 enabledRcv(3), 1290 enabledXmitAndRcv(4) 1291 } 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION "This object reflects the PAUSE mode currently 1295 in use on this interface, as determined by 1296 either (1) the result of the auto-negotiation 1297 function or (2) if auto-negotiation is not 1298 enabled or is not implemented for the active MAU 1299 attached to this interface, by the value of 1300 dot3PauseAdminMode. Interfaces operating at 1301 100 Mb/s or less will never return 1302 'enabledXmit(2)' or 'enabledRcv(3)'. Interfaces 1303 operating in half-duplex mode will always return 1304 'disabled(1)'. Interfaces on which 1305 auto-negotiation is enabled but not yet 1306 completed should return the value 1307 'disabled(1)'." 1308 ::= { dot3PauseEntry 2 } 1310 dot3PauseLinkDelayAllowance OBJECT-TYPE 1311 SYNTAX Unsigned32 (0..4294967295) 1312 MAX-ACCESS read-write 1313 STATUS current 1314 DESCRIPTION "The allowance, in bit times, made by the PAUSE 1315 MAC Control entity for round-trip propagation 1316 delay of the full-duplex link." 1317 REFERENCE "[IEEE 802.3 Std.], 30.3.4.1, 1318 aPAUSELinkDelayAllowance." 1319 ::= { dot3PauseEntry 3 } 1321 dot3InPauseFrames OBJECT-TYPE 1322 SYNTAX Counter32 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION "A count of MAC Control frames received on this 1326 interface with an opcode indicating the PAUSE 1327 operation. 1329 This counter does not increment when the 1330 interface is operating in half-duplex mode." 1331 REFERENCE "[IEEE 802.3 Std.], 30.3.4.3, 1332 aPAUSEMACCtrlFramesReceived." 1333 ::= { dot3PauseEntry 4 } 1335 dot3OutPauseFrames OBJECT-TYPE 1336 SYNTAX Counter32 1337 MAX-ACCESS read-only 1338 STATUS current 1339 DESCRIPTION "A count of MAC Control frames transmitted on 1340 this interface with an opcode indicating the 1341 PAUSE operation. 1343 This counter does not increment when the 1344 interface is operating in half-duplex mode." 1345 REFERENCE "[IEEE 802.3 Std.], 30.3.4.2, 1346 aPAUSEMACCtrlFramesTransmitted." 1347 ::= { dot3PauseEntry 5 } 1349 -- 802.3 Tests 1351 dot3Tests OBJECT IDENTIFIER ::= { dot3 6 } 1353 dot3Errors OBJECT IDENTIFIER ::= { dot3 7 } 1355 -- TDR Test 1357 dot3TestTdr OBJECT-IDENTITY 1358 STATUS current 1359 DESCRIPTION "The Time-Domain Reflectometry (TDR) test is 1360 specific to ethernet-like interfaces of type 1361 10Base5 and 10Base2. The TDR value may be 1362 useful in determining the approximate distance 1363 to a cable fault. It is advisable to repeat 1364 this test to check for a consistent resulting 1365 TDR value, to verify that there is a fault. 1367 A TDR test returns as its result the time 1368 interval, measured in 10 MHz ticks or 100 nsec 1369 units, between the start of TDR test 1370 transmission and the subsequent detection of a 1371 collision or deassertion of carrier. On 1372 successful completion of a TDR test, the result 1373 is stored as the value of an appropriate 1374 instance of an appropriate vendor specific MIB 1375 object, and the OBJECT IDENTIFIER of that 1376 instance is stored in the appropriate instance 1377 of the appropriate test result code object 1378 (thereby indicating where the result has been 1379 stored)." 1380 ::= { dot3Tests 1 } 1382 -- Loopback Test 1384 dot3TestLoopBack OBJECT-IDENTITY 1385 STATUS current 1386 DESCRIPTION "This test configures the MAC chip and executes 1387 an internal loopback test of memory, data paths, 1388 and the MAC chip logic. This loopback test can 1389 only be executed if the interface is offline. 1390 Once the test has completed, the MAC chip should 1391 be reinitialized for network operation, but it 1392 should remain offline. 1394 If an error occurs during a test, the 1395 appropriate test result object will be set 1396 to indicate a failure. The two OBJECT 1397 IDENTIFIER values dot3ErrorInitError and 1398 dot3ErrorLoopbackError may be used to provided 1399 more information as values for an appropriate 1400 test result code object." 1401 ::= { dot3Tests 2 } 1403 dot3ErrorInitError OBJECT-IDENTITY 1404 STATUS current 1405 DESCRIPTION "Couldn't initialize MAC chip for test." 1406 ::= { dot3Errors 1 } 1408 dot3ErrorLoopbackError OBJECT-IDENTITY 1409 STATUS current 1410 DESCRIPTION "Expected data not received (or not received 1411 correctly) in loopback test." 1412 ::= { dot3Errors 2 } 1414 -- conformance information 1416 etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 } 1417 etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 } 1418 etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 } 1420 -- compliance statements 1422 etherCompliance MODULE-COMPLIANCE 1423 STATUS deprecated 1424 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 1426 The compliance statement for managed network 1427 entities which have ethernet-like network 1428 interfaces. 1430 This compliance is deprecated and replaced by 1431 dot3Compliance." 1433 MODULE -- this module 1434 MANDATORY-GROUPS { etherStatsGroup } 1436 GROUP etherCollisionTableGroup 1437 DESCRIPTION "This group is optional. It is appropriate 1438 for all systems which have the necessary 1439 metering. Implementation in such systems is 1440 highly recommended." 1441 ::= { etherCompliances 1 } 1443 ether100MbsCompliance MODULE-COMPLIANCE 1444 STATUS deprecated 1445 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 1447 The compliance statement for managed network 1448 entities which have 100 Mb/sec ethernet-like 1449 network interfaces. 1451 This compliance is deprecated and replaced by 1452 dot3Compliance." 1454 MODULE -- this module 1455 MANDATORY-GROUPS { etherStats100MbsGroup } 1457 GROUP etherCollisionTableGroup 1458 DESCRIPTION "This group is optional. It is appropriate 1459 for all systems which have the necessary 1460 metering. Implementation in such systems is 1461 highly recommended." 1462 ::= { etherCompliances 2 } 1464 dot3Compliance MODULE-COMPLIANCE 1465 STATUS current 1466 DESCRIPTION "The compliance statement for managed network 1467 entities which have ethernet-like network 1468 interfaces." 1470 MODULE -- this module 1471 MANDATORY-GROUPS { etherStatsBaseGroup } 1473 GROUP etherDuplexGroup 1474 DESCRIPTION "This group is mandatory for all 1475 ethernet-like network interfaces which are 1476 capable of operating in full-duplex mode. 1477 It is highly recommended for all 1478 ethernet-like network interfaces." 1480 GROUP etherStatsLowSpeedGroup 1481 DESCRIPTION "This group is mandatory for all 1482 ethernet-like network interfaces which are 1483 capable of operating at 10 Mb/s or slower in 1484 half-duplex mode." 1486 GROUP etherStatsHighSpeedGroup 1487 DESCRIPTION "This group is mandatory for all 1488 ethernet-like network interfaces which are 1489 capable of operating at 100 Mb/s or faster." 1491 GROUP etherControlGroup 1492 DESCRIPTION "This group is mandatory for all 1493 ethernet-like network interfaces that 1494 support the MAC Control sublayer." 1496 GROUP etherControlPauseGroup 1497 DESCRIPTION "This group is mandatory for all 1498 ethernet-like network interfaces that 1499 support the MAC Control PAUSE function." 1501 OBJECT dot3PauseLinkDelayAllowance 1502 MIN-ACCESS read-only 1503 DESCRIPTION "Write access is not required." 1505 GROUP etherCollisionTableGroup 1506 DESCRIPTION "This group is optional. It is appropriate 1507 for all ethernet-like network interfaces 1508 which are capable of operating in 1509 half-duplex mode and have the necessary 1510 metering. Implementation in systems with 1511 such interfaces is highly recommended." 1513 ::= { etherCompliances 3 } 1515 -- units of conformance 1517 etherStatsGroup OBJECT-GROUP 1518 OBJECTS { dot3StatsIndex, 1519 dot3StatsAlignmentErrors, 1520 dot3StatsFCSErrors, 1521 dot3StatsSingleCollisionFrames, 1522 dot3StatsMultipleCollisionFrames, 1523 dot3StatsSQETestErrors, 1524 dot3StatsDeferredTransmissions, 1525 dot3StatsLateCollisions, 1526 dot3StatsExcessiveCollisions, 1527 dot3StatsInternalMacTransmitErrors, 1528 dot3StatsCarrierSenseErrors, 1529 dot3StatsFrameTooLongs, 1530 dot3StatsInternalMacReceiveErrors, 1531 dot3StatsEtherChipSet 1532 } 1533 STATUS deprecated 1534 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 1536 A collection of objects providing information 1537 applicable to all ethernet-like network 1538 interfaces. 1540 This object group has been deprecated and 1541 replaced by etherStatsBaseGroup and 1542 etherStatsLowSpeedGroup." 1543 ::= { etherGroups 1 } 1545 etherCollisionTableGroup OBJECT-GROUP 1546 OBJECTS { dot3CollFrequencies 1547 } 1548 STATUS current 1549 DESCRIPTION "A collection of objects providing a histogram 1550 of packets successfully transmitted after 1551 experiencing exactly N collisions." 1552 ::= { etherGroups 2 } 1554 etherStats100MbsGroup OBJECT-GROUP 1555 OBJECTS { dot3StatsIndex, 1556 dot3StatsAlignmentErrors, 1557 dot3StatsFCSErrors, 1558 dot3StatsSingleCollisionFrames, 1559 dot3StatsMultipleCollisionFrames, 1560 dot3StatsDeferredTransmissions, 1561 dot3StatsLateCollisions, 1562 dot3StatsExcessiveCollisions, 1563 dot3StatsInternalMacTransmitErrors, 1564 dot3StatsCarrierSenseErrors, 1565 dot3StatsFrameTooLongs, 1566 dot3StatsInternalMacReceiveErrors, 1567 dot3StatsEtherChipSet, 1568 dot3StatsSymbolErrors 1569 } 1570 STATUS deprecated 1571 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 1573 A collection of objects providing information 1574 applicable to 100 Mb/sec ethernet-like network 1575 interfaces. 1577 This object group has been deprecated and 1578 replaced by etherStatsBaseGroup and 1579 etherStatsHighSpeedGroup." 1580 ::= { etherGroups 3 } 1582 etherStatsBaseGroup OBJECT-GROUP 1583 OBJECTS { dot3StatsIndex, 1584 dot3StatsAlignmentErrors, 1585 dot3StatsFCSErrors, 1586 dot3StatsSingleCollisionFrames, 1587 dot3StatsMultipleCollisionFrames, 1588 dot3StatsDeferredTransmissions, 1589 dot3StatsLateCollisions, 1590 dot3StatsExcessiveCollisions, 1591 dot3StatsInternalMacTransmitErrors, 1592 dot3StatsCarrierSenseErrors, 1593 dot3StatsFrameTooLongs, 1594 dot3StatsInternalMacReceiveErrors, 1595 dot3StatsEtherChipSet 1596 } 1597 STATUS current 1598 DESCRIPTION "A collection of objects providing information 1599 applicable to all ethernet-like network 1600 interfaces." 1601 ::= { etherGroups 4 } 1603 etherStatsLowSpeedGroup OBJECT-GROUP 1604 OBJECTS { dot3StatsSQETestErrors } 1605 STATUS current 1606 DESCRIPTION "A collection of objects providing information 1607 applicable to ethernet-like network interfaces 1608 capable of operating at 10 Mb/s or slower in 1609 half-duplex mode." 1610 ::= { etherGroups 5 } 1612 etherStatsHighSpeedGroup OBJECT-GROUP 1613 OBJECTS { dot3StatsSymbolErrors } 1614 STATUS current 1615 DESCRIPTION "A collection of objects providing information 1616 applicable to ethernet-like network interfaces 1617 capable of operating at 100 Mb/s or faster." 1618 ::= { etherGroups 6 } 1620 etherDuplexGroup OBJECT-GROUP 1621 OBJECTS { dot3StatsDuplexStatus } 1622 STATUS current 1623 DESCRIPTION "A collection of objects providing information 1624 about the duplex mode of an ethernet-like 1625 network interface." 1626 ::= { etherGroups 7 } 1628 etherControlGroup OBJECT-GROUP 1629 OBJECTS { dot3ControlFunctionsSupported, 1630 dot3ControlInUnknownOpcodes 1631 } 1632 STATUS current 1633 DESCRIPTION "A collection of objects providing information 1634 about the MAC Control sublayer on ethernet-like 1635 network interfaces." 1636 ::= { etherGroups 8 } 1638 etherControlPauseGroup OBJECT-GROUP 1639 OBJECTS { dot3PauseAdminMode, 1640 dot3PauseOperMode, 1641 dot3PauseLinkDelayAllowance, 1642 dot3InPauseFrames, 1643 dot3OutPauseFrames 1644 } 1645 STATUS current 1646 DESCRIPTION "A collection of objects providing information 1647 about and control of the MAC Control PAUSE 1648 function on ethernet-like network interfaces." 1649 ::= { etherGroups 9 } 1651 END 1653 5. Intellectual Property 1655 The IETF takes no position regarding the validity or scope of any 1656 intellectual property or other rights that might be claimed to 1657 pertain to the implementation or use of the technology described in 1658 this document or the extent to which any license under such rights 1659 might or might not be available; neither does it represent that it 1660 has made any effort to identify any such rights. Information on the 1661 IETF's procedures with respect to rights in standards-track and 1662 standards-related documentation can be found in BCP-11. Copies of 1663 claims of rights made available for publication and any assurances of 1664 licenses to be made available, or the result of an attempt made to 1665 obtain a general license or permission for the use of such 1666 proprietary rights by implementors or users of this specification can 1667 be obtained from the IETF Secretariat. 1669 The IETF invites any interested party to bring to its attention any 1670 copyrights, patents or patent applications, or other proprietary 1671 rights which may cover technology that may be required to practice 1672 this standard. Please address the information to the IETF Executive 1673 Director. 1675 6. Acknowledgements 1677 This document was produced by the Ethernet Interfaces and Hub MIB 1678 Working Group. 1680 This document is based on the Proposed Standard Ethernet MIB, RFC 1681 2358 [23], edited by John Flick of Hewlett-Packard and Jeffrey 1682 Johnson of RedBack Networks and produced by the 802.3 Hub MIB Working 1683 Group. It extends that document by providing support for full-duplex 1684 Ethernet interfaces and 1000 Mb/sec Ethernet interfaces as outlined 1685 in [16]. 1687 RFC 2358, in turn, is almost completely based on both the Standard 1688 Ethernet MIB, RFC 1643 [21], and the Proposed Standard Ethernet MIB 1689 using the SNMPv2 SMI, RFC 1650 [22], both of which were edited by 1690 Frank Kastenholz of FTP Software and produced by the Interfaces MIB 1691 Working Group. RFC 2358 extends those documents by providing support 1692 for 100 Mb/sec ethernet interfaces. 1694 RFC 1643 and RFC 1650, in turn, are based on the Draft Standard 1695 Ethernet MIB, RFC 1398 [20], also edited by Frank Kastenholz and 1696 produced by the Ethernet MIB Working Group. 1698 RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, 1699 RFC 1284 [18], which was edited by John Cook of Chipcom and produced 1700 by the Transmission MIB Working Group. The Ethernet MIB Working 1701 Group gathered implementation experience of the variables specified 1702 in RFC 1284, documented that experience in RFC 1369 [19], and used 1703 that information to develop this revised MIB. 1705 RFC 1284, in turn, is based on a document written by Frank 1706 Kastenholz, then of Interlan, entitled IEEE 802.3 Layer Management 1707 Draft M compatible MIB for TCP/IP Networks [17]. This document was 1708 modestly reworked, initially by the SNMP Working Group, and then by 1709 the Transmission Working Group, to reflect the current conventions 1710 for defining objects for MIB interfaces. James Davin, of the MIT 1711 Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN 1712 Systems, contributed to later drafts of this memo. Marshall Rose of 1713 Performance Systems International, Inc. converted the document into 1714 RFC 1212 [3] concise format. Anil Rijsinghani of DEC contributed 1715 text that more adequately describes the TDR test. Thanks to Frank 1716 Kastenholz of Interlan and Louis Steinberg of IBM for their 1717 experimentation. 1719 7. References 1721 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1722 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1723 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1724 January 1998 1726 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1727 Management Information for TCP/IP-based Internets", STD 16, 1728 RFC 1155, Performance Systems International, Hughes LAN Systems, 1729 May 1990 1731 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, 1732 RFC 1212, Performance Systems International, Hughes LAN Systems, 1733 March 1991 1735 [4] M. Rose, "A Convention for Defining Traps for use with the 1736 SNMP", RFC 1215, Performance Systems International, March 1991 1738 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1739 "Structure of Management Information for Version 2 of the Simple 1740 Network Management Protocol (SNMPv2)", RFC 1902, SNMP Research, 1741 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1742 International Network Services, January 1996. 1744 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1745 Conventions for Version 2 of the Simple Network Management 1746 Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco 1747 Systems, Inc., Dover Beach Consulting, Inc., International 1748 Network Services, January 1996. 1750 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1751 "Conformance Statements for Version 2 of the Simple Network 1752 Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., 1753 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1754 Network Services, January 1996. 1756 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1757 Network Management Protocol", STD 15, RFC 1157, SNMP Research, 1758 Performance Systems International, Performance Systems 1759 International, MIT Laboratory for Computer Science, May 1990. 1761 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1762 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 1763 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1764 Inc., International Network Services, January 1996. 1766 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1767 "Transport Mappings for Version 2 of the Simple Network 1768 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 1769 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1770 Network Services, January 1996. 1772 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1773 Processing and Dispatching for the Simple Network Management 1774 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron 1775 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1776 January 1998. 1778 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1779 for version 3 of the Simple Network Management Protocol 1780 (SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. 1782 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1783 Operations for Version 2 of the Simple Network Management 1784 Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco 1785 Systems, Inc., Dover Beach Consulting, Inc., International 1786 Network Services, January 1996. 1788 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1789 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 1790 Systems, January 1998 1792 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1793 Control Model (VACM) for the Simple Network Management Protocol 1794 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, 1795 Inc., Cisco Systems, Inc., January 1998 1797 [16] IEEE, IEEE Std 802.3, 1998 Edition: "Information technology - 1798 Telecommunications and information exchange between systems - 1799 Local and metropolitan area networks - Specific requirements - 1800 Part 3: Carrier sense multiple access with collision detection 1801 (CSMA/CD) access method and physical layer specifications" 1802 (incorporating ANSI/IEEE Std. 802.3, 1996 Edition, IEEE Std. 1803 802.3r-1996, 802.3u-1995, 802.3x&y-1997, 802.3z-1998, and 1804 802.3aa-1998), September 1998. 1806 [17] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible 1807 MIB for TCP/IP Networks", electronic mail message to mib- 1808 wg@nnsc.nsf.net, 9 June 1989. 1810 [18] Cook, J., "Definitions of Managed Objects for Ethernet-Like 1811 Interface Types", RFC 1284, Chipcom Corporation, December 1991. 1813 [19] Kastenholz, F., "Implementation Notes and Experience for The 1814 Internet Ethernet MIB", RFC 1369, FTP Software, October 1992. 1816 [20] Kastenholz, F., "Definitions of Managed Objects for the 1817 Ethernet-like Interface Types", RFC 1398, FTP Software, Inc., 1818 January 1993. 1820 [21] Kastenholz, F., "Definitions of Managed Objects for the 1821 Ethernet-like Interface Types", STD 50, RFC 1643, FTP Software, 1822 Inc., July 1994. 1824 [22] Kastenholz, F., "Definitions of Managed Objects for the 1825 Ethernet-like Interface Types using SMIv2", RFC 1650, 1826 FTP Software, Inc., August 1994. 1828 [23] Flick, J., and J. Johnson, "Definitions of Managed Objects 1829 for the Ethernet-like Interface Types", RFC 2358, 1830 Hewlett-Packard Company, RedBack Networks, June 1998. 1832 [24] McCloghrie, K., and M. Rose, Editors, "Management Information 1833 Base for Network Management of TCP/IP-based internets: MIB-II", 1834 STD 17, RFC 1213, Hughes LAN Systems, Performance Systems 1835 International, March 1991. 1837 [25] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB 1838 using SMIv2", RFC 2233, Cisco Systems, FTP Software, 1839 November 1997. 1841 [26] Bradner, S., "Key words for use in RFCs to Indicate 1842 Requirements Levels", BCP 14, RFC 2119, March 1997. 1844 [27] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster, 1845 D., McCloghrie, K., and S. Roberts, "Definitions of Managed 1846 Objects for IEEE 802.3 Medium Attachment Units (MAUs) using 1847 SMIv2", work in progress, draft-ietf-hubmib-mau-mib-v2-01.txt, 1848 Extreme Networks, Inc., Hewlett-Packard Company, Argon Networks, 1849 LANNET Ltd., Cisco Systems, Inc., Cisco Systems Inc., Farallon 1850 Computing Inc., November 1998. 1852 [28] "Ethernet Interface Chipset Registrations", work in progress. 1854 8. Security Considerations 1856 There are two management objects defined in this MIB that have a 1857 MAX-ACCESS clause of read-write. Such objects may be considered 1858 sensitive or vulnerable in some network environments. The support 1859 for SET operations in a non-secure environment without proper 1860 protection can have a negative effect on network operations. 1862 There are a number of managed objects in this MIB that may be 1863 considered to contain sensitive information. In particular, the 1864 dot3StatsEtherChipSet object may be considered sensitive in many 1865 environments, since it would allow an intruder to obtain information 1866 about which vendor's equipment is in use on the network. 1868 Therefore, it may be important in some environments to control read 1869 access to these objects and possibly to even encrypt the values of 1870 these object when sending them over the network via SNMP. Not all 1871 versions of SNMP provide features for such a secure environment. 1873 SNMPv1 by itself is such an insecure environment. Even if the 1874 network itself is secure (for example by using IPSec), even then, 1875 there is no control as to who on the secure network is allowed to 1876 access and GET (read) the objects in this MIB. 1878 It is recommended that the implementors consider the security 1879 features as provided by the SNMPv3 framework. Specifically, the use 1880 of the User-based Security Model RFC 2274 [12] and the View-based 1881 Access Control Model RFC 2275 [15] is recommended. 1883 It is then a customer/user responsibility to ensure that the SNMP 1884 entity giving access to an instance of this MIB, is properly 1885 configured to give access to those objects only to those principals 1886 (users) that have legitimate rights to access them. 1888 9. Author's Addresses 1890 John Flick 1891 Hewlett-Packard Company 1892 8000 Foothills Blvd. M/S 5556 1893 Roseville, CA 95747-5556 1895 Phone: +1 916 785 4018 1896 Email: johnf@rose.hp.com 1898 Jeffrey Johnson 1899 RedBack Networks 1900 2570 North First Street, Suite 410 1901 San Jose, CA, 95131, USA 1903 Phone: +1 408 571 2699 1904 EMail: jeff@redbacknetworks.com 1906 A. Change Log 1908 A.1. Changes since RFC 2358 1910 This section enumerates changes made to RFC 2358 to produce this 1911 document. 1913 (1) Section 2 has been replaced with the current SNMP 1914 Management Framework boilerplate. 1916 (2) The ifMtu mapping has been clarified. 1918 (3) The relationship between the IEEE 802.3 octet counters 1919 and the IF-MIB octet counters has been clarified. 1921 (4) REFERENCE clauses have been updated to reflect the 1922 actual IEEE 802.3 managed object that each MIB object 1923 is based on. 1925 (5) The following object DESCRIPTION clauses have been 1926 updated to reflect that they do not increment in 1927 full-duplex mode: dot3StatsSingleCollisionFrames, 1928 dot3StatsMultipleCollisionFrames, dot3StatsSQETestErrors, 1929 dot3StatsDeferredTransmissions, dot3StatsLateCollisions, 1930 dot3StatsExcessiveCollisions, dot3StatsCarrierSenseErrors, 1931 dot3CollFrequencies. 1933 (6) The following object DESCRIPTION clauses have been 1934 updated to reflect behaviour on full-duplex and 1935 1000 Mb/s interfaces: dot3StatsAlignmentErrors, 1936 dot3StatsFCSErrors, dot3StatsSQETestErrors, 1937 dot3StatsLateCollisions, dot3StatsSymbolErrors. 1939 (7) Two new tables, dot3ControlTable and dot3PauseTable, 1940 have been added. 1942 (8) A new object, dot3StatsDuplexStatus, has been added. 1944 (9) The object groups and compliances have been restructured. 1946 (10) The dot3ChipSets have been moved to a separate document. 1948 A.2. Changes between RFC 1650 and RFC 2358 1950 This section enumerates changes made to RFC 1650 to produce RFC 2358. 1952 (1) The MODULE-IDENTITY has been updated to reflect the changes 1953 in the MIB. 1955 (2) A new object, dot3StatsSymbolErrors, has been added. 1957 (3) The definition of the object dot3StatsIndex has been 1958 converted to use the SMIv2 OBJECT-TYPE macro. 1960 (4) A new conformance group, etherStats100MbsGroup, has been 1961 added. 1963 (5) A new compliance statement, ether100MbsCompliance, has 1964 been added. 1966 (6) The Acknowledgements were extended to provide a more 1967 complete history of the origin of this document. 1969 (7) The discussion of ifType has been expanded. 1971 (8) A section on mapping of Interfaces MIB objects has 1972 been added. 1974 (9) A section defining the relationship of this MIB to 1975 the MAU MIB has been added. 1977 (10) A section on the mapping of IEEE 802.3 managed objects 1978 to this MIB and the Interfaces MIB has been added. 1980 (11) Converted the dot3Tests, dot3Errors, and dot3ChipSets 1981 OIDs to use the OBJECT-IDENTITY macro. 1983 (12) Added to the list of registered dot3ChipSets. 1985 (13) An intellectual property notice and copyright notice 1986 were added, as required by RFC 2026. 1988 B. Full Copyright Statement 1990 This document and translations of it may be copied and furnished to 1991 others, and derivative works that comment on or otherwise explain it 1992 or assist in its implementation may be prepared, copied, published 1993 and distributed, in whole or in part, without restriction of any 1994 kind, provided that the above copyright notice and this paragraph are 1995 included on all such copies and derivative works. However, this 1996 document itself may not be modified in any way, such as by removing 1997 the copyright notice or references to the Internet Society or other 1998 Internet organizations, except as needed for the purpose of 1999 developing Internet standards in which case the procedures for 2000 copyrights defined in the Internet Standards process must be 2001 followed, or as required to translate it into languages other than 2002 English. 2004 The limited permissions granted above are perpetual and will not be 2005 revoked by the Internet Society or its successors or assigns. 2007 This document and the information contained herein is provided on an 2008 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2009 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2010 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2011 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2012 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.