idnits 2.17.1 draft-ietf-hubmib-etherif-mib-v2-00.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 510 has weird spacing: '...issions dot...' == Line 516 has weird spacing: '...cvError dot3S...' -- 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 (August 1998) is 9378 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' -- Possible downref: Non-RFC (?) normative reference: ref. '18' -- Possible downref: Non-RFC (?) normative reference: ref. '19' -- Possible downref: Non-RFC (?) normative reference: ref. '20' ** Obsolete normative reference: RFC 1284 (ref. '21') (Obsoleted by RFC 1398) ** Downref: Normative reference to an Informational RFC: RFC 1369 (ref. '22') ** Obsolete normative reference: RFC 1398 (ref. '23') (Obsoleted by RFC 1623) ** Obsolete normative reference: RFC 1643 (ref. '24') (Obsoleted by RFC 3638) ** Obsolete normative reference: RFC 1650 (ref. '25') (Obsoleted by RFC 2358) ** Obsolete normative reference: RFC 2358 (ref. '26') (Obsoleted by RFC 2665) ** Obsolete normative reference: RFC 2233 (ref. '28') (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 2239 (ref. '30') (Obsoleted by RFC 2668) Summary: 29 errors (**), 0 flaws (~~), 5 warnings (==), 8 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 August 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, reflect 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. Mapping of IEEE 802.3 Managed Objects .................... 11 74 4. Definitions ................................................ 12 75 5. Intellectual Property ...................................... 40 76 6. Acknowledgements ........................................... 41 77 7. References ................................................. 42 78 8. Security Considerations .................................... 45 79 9. Author's Addresses ......................................... 45 80 A. Change Log ................................................. 46 81 A.1. Changes since RFC 2358 ................................... 46 82 A.2. Changes between RFC 1650 and RFC 2358 .................... 47 83 B. Full Copyright Statement ................................... 47 85 1. Introduction 87 This memo defines a portion of the Management Information Base (MIB) 88 for use with network management protocols in the Internet community. 89 In particular, it defines objects for managing Ethernet-like 90 interfaces. 92 This memo also includes a MIB module. This MIB module extends the 93 list of managed objects specified in the earlier version of this MIB: 94 RFC2358 [26]. 96 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 97 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 98 document are to be interpreted as described in [29]. 100 2. The SNMP Management Framework 102 The SNMP Management Framework presently consists of five major 103 components: 105 o An overall architecture, described in RFC 2271 [1]. 107 o Mechanisms for describing and naming objects and events for the 108 purpose of management. The first version of this Structure of 109 Management Information (SMI) is called SMIv1 and described in 110 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 111 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 112 1904 [7]. 114 o Message protocols for transferring management information. The 115 first version of the SNMP message protocol is called SNMPv1 and 116 described in RFC 1157 [8]. A second version of the SNMP message 117 protocol, which is not an Internet standards track protocol, is 118 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 119 The third version of the message protocol is called SNMPv3 and 120 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 122 o Protocol operations for accessing management information. The 123 first set of protocol operations and associated PDU formats is 124 described in RFC 1157 [8]. A second set of protocol operations 125 and associated PDU formats is described in RFC 1905 [13]. 127 o A set of fundamental applications described in RFC 2273 [14] and 128 the view-based access control mechanism described in RFC 2275 129 [15]. 131 Managed objects are accessed via a virtual information store, termed 132 the Management Information Base or MIB. Objects in the MIB are 133 defined using the mechanisms defined in the SMI. 135 This memo specifies a MIB module that is compliant to the SMIv2. A 136 MIB conforming to the SMIv1 can be produced through the appropriate 137 translations. The resulting translated MIB must be semantically 138 equivalent, except where objects or events are omitted because no 139 translation is possible (use of Counter64). Some machine readable 140 information in SMIv2 will be converted into textual descriptions in 141 SMIv1 during the translation process. However, this loss of machine 142 readable information is not considered to change the semantics of the 143 MIB. 145 3. Overview 147 Instances of these object types represent attributes of an interface 148 to an ethernet-like communications medium. At present, ethernet-like 149 media are identified by the following values of the ifType object in 150 the Interfaces MIB [28]: 152 ethernetCsmacd(6) 153 iso88023Csmacd(7) 154 starLan(11) 156 The definitions presented here are based on IEEE Draft 802.3z/D4.2, 157 Section 30 [19], as originally interpreted by Frank Kastenholz then 158 of Interlan in [20]. Implementors of these MIB objects should note 159 that IEEE Std. 802.3 ([16], [17], and [18]) and IEEE Draft 802.3z 160 [19] explicitly describe (in the form of Pascal pseudocode) when, 161 where, and how various MAC attributes are measured. The IEEE 162 documents also describe the effects of MAC actions that may be 163 invoked by manipulating instances of the MIB objects defined here. 165 To the extent that some of the attributes defined in [19] are 166 represented by previously defined objects in MIB-2 [27] or in the 167 Interfaces MIB [28], such attributes are not redundantly represented 168 by objects defined in this memo. Among the attributes represented by 169 objects defined in other memos are the number of octets transmitted 170 or received on a particular interface, the number of frames 171 transmitted or received on a particular interface, the promiscuous 172 status of an interface, the MAC address of an interface, and 173 multicast information associated with an interface. 175 3.1. Relation to MIB-2 177 This section applies only when this MIB is used in conjunction with 178 the "old" (RFC 1213) [27] interface group. 180 The relationship between an ethernet-like interface and an interface 181 in the context of the Internet-standard MIB is one-to-one. As such, 182 the value of an ifIndex object instance can be directly used to 183 identify corresponding instances of the objects defined herein. 185 For agents which implement the (now deprecated) ifSpecific object, an 186 instance of that object that is associated with an ethernet-like 187 interface has the OBJECT IDENTIFIER value: 189 dot3 OBJECT IDENTIFER ::= { transmission 7 } 191 3.2. Relation to the Interfaces MIB 193 The Interface MIB [28] requires that any MIB which is an adjunct of 194 the Interface MIB clarify specific areas within the Interface MIB. 195 These areas were intentionally left vague in the Interface MIB to 196 avoid over constraining the MIB, thereby precluding management of 197 certain media-types. 199 Section 3.3 of [28] enumerates several areas which a media-specific 200 MIB must clarify. Each of these areas is addressed in a following 201 subsection. The implementor is referred to [28] in order to 202 understand the general intent of these areas. 204 3.2.1. Layering Model 206 This MIB does not provide for layering. There are no sublayers. 208 EDITOR'S NOTE: 210 One could foresee the development of an 802.2 and enet-transceiver 211 MIB. They could be higher and lower sublayers, respectively. All 212 that THIS document should do is allude to the possibilities and urge 213 the implementor to be aware of the possibility and that they may have 214 requirements which supersede the requirements in this document. 216 3.2.2. Virtual Circuits 218 This medium does not support virtual circuits and this area is not 219 applicable to this MIB. 221 3.2.3. ifTestTable 223 This MIB defines two tests for media which are instrumented with this 224 MIB; TDR and Loopback. Implementation of these tests is not 225 required. Many common interface chips do not support one or both of 226 these tests. 228 These two tests are provided as a convenience, allowing a common 229 method to invoke the test. 231 Standard MIBs do not include objects in which to return the results 232 of the TDR test. Any needed objects MUST be provided in the vendor 233 specific MIB. 235 Note that the ifTestTable is now deprecated. Work is underway to 236 define a replacement MIB for system and interface testing. It is 237 expected that the tests defined in this document will be usable in 238 this replacement MIB. 240 3.2.4. ifRcvAddressTable 242 This table contains all IEEE 802.3 addresses, unicast, multicast, and 243 broadcast, for which this interface will receive packets and forward 244 them up to a higher layer entity for local consumption. The format 245 of the address, contained in ifRcvAddressAddress, is the same as for 246 ifPhysAddress. 248 In the event that the interface is part of a MAC bridge, this table 249 does not include unicast addresses which are accepted for possible 250 forwarding out some other port. This table is explicitly not 251 intended to provide a bridge address filtering mechanism. 253 3.2.5. ifPhysAddress 255 This object contains the IEEE 802.3 address which is placed in the 256 source-address field of any Ethernet, Starlan, or IEEE 802.3 frames 257 that originate at this interface. Usually this will be kept in ROM 258 on the interface hardware. Some systems may set this address via 259 software. 261 In a system where there are several such addresses the designer has a 262 tougher choice. The address chosen should be the one most likely to 263 be of use to network management (e.g. the address placed in ARP 264 responses for systems which are primarily IP systems). 266 If the designer truly can not chose, use of the factory- provided ROM 267 address is suggested. 269 If the address can not be determined, an octet string of zero length 270 should be returned. 272 The address is stored in binary in this object. The address is 273 stored in "canonical" bit order, that is, the Group Bit is positioned 274 as the low-order bit of the first octet. Thus, the first byte of a 275 multicast address would have the bit 0x01 set. 277 3.2.6. ifType 279 This MIB applies to interfaces which have any of the following ifType 280 values: 282 ethernetCsmacd(6) 283 iso88023Csmacd(7) 284 starLan(11) 286 It is RECOMMENDED that all Ethernet-like interfaces use an ifType of 287 ethernetCsmacd(6) regardless of the speed that the interface is 288 running or the link-layer encapsulation in use. iso88023Csmacd(7) 289 and starLan(11) are supported for backwards compatability. 291 There are three other interface types defined in the IANAifType-MIB 292 for 100 Mbit Ethernet. They are fastEther(62), fastEtherFX(69), and 293 gigabitEthernet(117). This document takes the position that an 294 Ethernet is an Ethernet, and Ethernet interfaces SHOULD always have 295 the same value of ifType. Information on the particular flavor of 296 Ethernet that an interface is running is available from ifSpeed in 297 the Interfaces MIB, and ifMauType in the 802.3 MAU MIB. An 298 Ethernet-like interface SHOULD NOT use the fastEther(62), 299 fastEtherFX(69), or gigabitEthernet(117) ifTypes. 301 Interfaces with any of the supported ifType values map to the 302 EtherLike-MIB in the same manner. Which compliance statement an 303 interface should implement is dependent on the maximum speed 304 supported on the interface. The EtherLike-MIB etherCompliance 305 compliance statement applies to all Ethernet-like interfaces whose 306 maximum supported speed is 10 Mbit/sec or less. There are no 307 implementation differences. Similarly, the EtherLike-MIB 308 ether100MbsCompliance compliance statement applies to all Ethernet- 309 like interfaces whose maximum supported speed is 100Mbit/sec. 311 An interface that is capable of operating at 100Mbit/sec MUST 312 implement the ether100MbsCompliance compliance statement, even if it 313 is currently operating at a lower speed. Counters in the 314 ether100MbsCompliance compliance statement that only apply to 100 315 Mbit interfaces would simply not increment when the interface is 316 operating at a lower speed. 318 3.2.7. Specific Interface MIB Objects 320 The following table provides specific implementation guidelines for 321 applying the interface group objects to ethernet-like media. 323 Object 324 ifIndex Each ethernet-like interface is 325 represented by an ifEntry. The 326 dot3StatsTable in this MIB module is 327 indexed by dot3StatsIndex. The interface 328 identified by a particular value of 329 dot3StatsIndex is the same interface as 330 identified by the same value of ifIndex. 332 ifDescr Refer to [28]. 334 ifType Refer to section 3.2.6. 336 ifMtu 1500 octets. NOTE: This is the MTU as 337 seen by the MAC client. When a higher 338 layer protocol, like IP, is running over 339 Ethernet, this is the MTU that will be 340 seen by that higher layer protocol. 341 However, when using the IEEE 802.2 LLC 342 protocol, higher layer protocols will 343 see a different MTU. In particular, an 344 LLC type 1 client protocol will see 345 an MTU of 1497 octets, and a protocol 346 running over SNAP will see an MTU of 347 1492 octets. 349 ifSpeed The current operational speed of the 350 interface in bits per second. For 351 current ethernet-like interfaces, this 352 will be equal to 1,000,000 (1 million), 353 10,000,000 (10 million), 100,000,000 354 (100 million), or 1,000,000,000 (1 355 billion). If the interface implements 356 auto-negotiation, auto-negotiation is 357 enabled for this interface, and the 358 interface has not yet negotiated to an 359 operational speed, this object SHOULD 360 reflect the maximum speed supported by 361 the interface. Note that this object 362 MUST NOT indicate a doubled value when 363 operating in full-duplex mode. It MUST 364 indicate the correct line speed 365 regardless of the current duplex mode. 366 The correct object to use to determine 367 the duplex mode of the interface is the 368 ifMauType object in the 802.3 MAU MIB. 370 ifPhysAddress Refer to section 3.2.5. 372 ifAdminStatus Write access is not required. Support 373 for 'testing' is not required. 375 ifOperStatus The operational state of the interface. 376 Support for 'testing' is not required. 377 The value 'dormant' has no meaning for 378 an ethernet-like interface. 380 ifLastChange Refer to [28]. 382 ifInOctets The number of octets in valid MAC frames 383 received on this interface, including 384 the MAC header and FCS. 386 ifInUcastPkts Refer to [28]. 388 ifInDiscards Refer to [28]. 390 ifInErrors The sum for this interface of 391 dot3StatsAlignmentErrors, 392 dot3StatsFCSErrors, 393 dot3StatsFrameTooLongs, 394 dot3StatsInternalMacReceiveErrors and 395 dot3StatsSymbolErrors. 397 ifInUnknownProtos Refer to [28]. 399 ifOutOctets The number of octets transmitted in 400 valid MAC frames on this interface, 401 including the MAC header and FCS. 403 ifOutUcastPkts Refer to [28]. 405 ifOutDiscards Refer to [28]. 407 ifOutErrors The sum for this interface of: 408 dot3StatsSQETestErrors, 409 dot3StatsLateCollisions, 410 dot3StatsExcessiveCollisions, 411 dot3StatsInternalMacTransmitErrors and 412 dot3StatsCarrierSenseErrors. 414 ifName Locally-significant textual name for the 415 interface (e.g. lan0). 417 ifInMulticastPkts Refer to [28]. 419 ifInBroadcastPkts Refer to [28]. 421 ifOutMulticastPkts Refer to [28]. 423 ifOutBroadcastPkts Refer to [28]. 425 ifHCInOctets 64-bit versions of counters. Required 426 ifHCOutOctets for ethernet-like interfaces that are 427 capable of operating at 20Mbit/sec or 428 faster, even if the interface is 429 currently operating at less than 430 20Mbit/sec. 432 ifHCInUcastPkts 64-bit versions of packet counters. 433 ifHCInMulticastPkts Support for these counters is not 434 ifHCInBroadcastPkts required for the interface types 435 ifHCOutUcastPkts supported by this MIB. They are only 436 ifHCOutMulticastPkts required for interfaces capable of 437 ifHCOutBroadcastPkts operating at 640Mbit/sec or faster. 438 Note that a future revision of this 439 document may support faster interfaces, 440 and therefore may require support for 441 these counters. 443 ifLinkUpDownTrapEnable Refer to [28]. Default is 'enabled' 445 ifHighSpeed The current operational speed of the 446 interface in millions of bits per 447 second. For current ethernet-like 448 interfaces, this will be equal to 1, 10, 449 100, or 1,000. If the interface 450 implements auto-negotiation, 451 auto-negotiation is enabled for this 452 interface, and the interface has not yet 453 negotiated to an operational speed, this 454 object SHOULD reflect the maximum speed 455 supported by the interface. Note that 456 this object MUST NOT indicate a doubled 457 value when operating in full-duplex 458 mode. It MUST indicate the correct line 459 speed regardless of the current duplex 460 mode. The correct object to use to 461 determine the duplex mode of the 462 interface is the ifMauType object in the 463 802.3 MAU MIB. 465 ifPromiscuousMode Refer to [28]. 467 ifConnectorPresent This will normally be 'true'. 469 ifAlias Refer to [28]. 471 ifCounterDiscontinuityTime Refer to [28]. 473 ifStackHigherLayer Refer to section 3.2.1. 474 ifStackLowerLayer 475 ifStackStatus 477 ifRcvAddressAddress Refer to section 3.2.4. 478 ifRcvAddressStatus 479 ifRcvAddressType 481 3.3. Relation to the 802.3 MAU MIB 483 Support for the mauModIfCompl compliance statement of the MAU-MIB 484 [30] is REQUIRED for Ethernet-like interfaces. This MIB is needed in 485 order to allow applications to determine the current MAU type in use 486 by the interface. The MAU type indicates not only the media type in 487 use, but also indicates whether the interface is operating in half- 488 duplex or full-duplex mode. Implementing this MIB module without 489 implementing the MAU-MIB would leave applications with no standard 490 way to determine the duplex mode of the interface. 492 3.4. Mapping of IEEE 802.3 Managed Objects 494 IEEE 802.3 Managed Object Corresponding SNMP Object 496 oMacEntity 497 .aMACID dot3StatsIndex or 498 IF-MIB - ifIndex 499 .aFramesTransmittedOK IF-MIB - ifOutUCastPkts + 500 ifOutMulticastPkts + 501 ifOutBroadcastPkts 502 .aSingleCollisionFrames dot3StatsSingleCollisionFrames 503 .aMultipleCollisionFrames dot3StatsMultipleCollisionFrames 504 .aFramesReceivedOK IF-MIB - ifInUcastPkts + 505 ifInMulticastPkts + 506 ifInBroadcastPkts 507 .aFrameCheckSequenceErrors dot3StatsFCSErrors 508 .aAlignmentErrors dot3StatsAlignmentErrors 509 .aOctetsTransmittedOK IF-MIB - ifOutOctets* 510 .aFramesWithDeferredXmissions dot3StatsDeferredTransmissions 511 .aLateCollisions dot3StatsLateCollisions 512 .aFramesAbortedDueToXSColls dot3StatsExcessiveCollisions 513 .aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors 514 .aCarrierSenseErrors dot3StatsCarrierSenseErrors 515 .aOctetsReceivedOK IF-MIB - ifInOctets* 516 .aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors 517 .aPromiscuousStatus IF-MIB - ifPromiscuousMode 518 .aReadMulticastAddressList IF-MIB - ifRcvAddressTable 519 .aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts 520 .aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts 521 .aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts 522 .aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts 523 .aFrameTooLongErrors dot3StatsFrameTooLongs 524 .aReadWriteMACAddress IF-MIB - ifPhysAddress 525 .aCollisionFrames dot3CollFrequencies 526 .acAddGroupAddress IF-MIB - ifRcvAddressTable 527 .acDeleteGroupAddress IF-MIB - ifRcvAddressTable 528 .acExecuteSelfTest dot3TestLoopBack 530 oPHYEntity 531 .aSQETestErrors dot3StatsSQETestErrors 532 .aSymbolErrorDuringCarrier dot3StatsSymbolErrors 534 * Note that the octet counters in IF-MIB do not exactly match the 535 definition of the octet counters in IEEE 802.3. aOctetsTransmittedOK 536 and aOctetsReceivedOK count only the octets in the clientData and Pad 537 fields, whereas ifInOctets and ifOutOctets include the entire MAC 538 frame, including MAC header and FCS. However, the IF-MIB counters 539 can be derived from the IEEE 802.3 counters as follows: 541 ifInOctets = aOctetsReceivedOK + (18 * aFramesReceivedOK) 542 ifOutOctets = aOctetsTransmittedOK + (18 * aFramesTransmittedOK) 544 The following IEEE 802.3 managed objects have been removed from this 545 MIB module as a result of implementation feedback: 547 oMacEntity 548 .aFramesWithExcessiveDeferral 549 .aInRangeLengthErrors 550 .aOutOfRangeLengthField 551 .aMACEnableStatus 552 .aTransmitEnableStatus 553 .aMulticastReceiveStatus 554 .acInitializeMAC 556 Please see [22] for the detailed reasoning on why these objects were 557 removed. 559 4. Definitions 560 EtherLike-MIB DEFINITIONS ::= BEGIN 562 IMPORTS 563 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, 564 Counter32, Unsigned32, mib-2, transmission 565 FROM SNMPv2-SMI 566 MODULE-COMPLIANCE, OBJECT-GROUP 567 FROM SNMPv2-CONF 568 ifIndex, InterfaceIndex 569 FROM IF-MIB; 571 etherMIB MODULE-IDENTITY 572 LAST-UPDATED "9808042227Z" -- August 4, 1998 573 ORGANIZATION "IETF 802.3 Hub MIB Working Group" 574 CONTACT-INFO 575 "WG E-mail: hubmib@hprnd.rose.hp.com 576 To subscribe: hubmib-request@hprnd.rose.hp.com 578 Chair: Dan Romascanu 579 Postal: LANNET Ltd. 580 Atidum Technology Park, Bldg. 3 581 Tel Aviv 61131 582 Israel 583 Tel: +972 3 645 8414 584 E-mail: dromasca@lannet.com 586 Editor: John Flick 587 Postal: Hewlett-Packard Company 588 8000 Foothills Blvd. M/S 5556 589 Roseville, CA 95747-5556 590 USA 591 Tel: +1 916 785 4018 592 Fax: +1 916 785 3583 593 E-mail: johnf@rose.hp.com 595 Editor: Jeffrey Johnson 596 Postal: RedBack Networks 597 2570 North First Street, Suite 410 598 San Jose, CA, 95131 599 USA 600 Tel: +1 408 571 2699 601 Fax: +1 408 571 2698 602 E-Mail: jeff@redbacknetworks.com" 604 DESCRIPTION "The MIB module to describe generic objects for 605 Ethernet-like network interfaces. 607 The following reference is used throughout this 608 MIB module: 610 [IEEE 802.3 Std] refers to: 611 ISO/IEC 8802-3: 1996(E), (ANSI/IEEE 612 Std 802.3, 1996 Edition), 'Information 613 technology - Telecommunications and 614 information exchange between systems - Local 615 and metropolitan area networks - Specific 616 requirements - Part 3: Carrier sense 617 multiple access with collision detection 618 (CSMA/CD) access method and physical layer 619 specifications', July 1996. 621 as ammended by the following supplements: 623 IEEE Std 802.3u-1995, 'Media Access Control 624 (MAC) Parameters, Physical Layer, Medium 625 Attachment Units, and Repeater for 100Mb/s 626 Operation, Type 100BASE-T', October 1995. 628 IEEE Std 802.3x-1997 and IEEE Std 629 802.3y-1997, 'Specification for 802.3 Full 630 Duplex Operation and Physical Layer 631 Specification for 100Mbit/s Operation on Two 632 Pairs of Category 3 or Better Balanced 633 Twisted Pair Cable (100BASE-T2)', November 634 1997. 636 IEEE Draft 802.3z/D4.2, 'Media Access 637 Control (MAC) Parameters, Physical Layer, 638 Repeater and Management Parameters for 1000 639 Mb/s Operation', March 1998. 641 Of particular interest is Clause 30, '10Mb/s, 642 100Mb/s and 1000Mb/s Management', which is 643 specified in IEEE Draft 802.3z/D4.2." 645 REVISION "9808042227Z" 646 DESCRIPTION "Updated to include support for 1000 Mb/sec 647 interfaces and full-duplex interfaces." 649 REVISION "9806032150Z" 650 DESCRIPTION "Updated to include support for 100 Mb/sec 651 interfaces. Published as RFC 2358." 653 REVISION "9402030400Z" 654 DESCRIPTION "Version published as RFC 1650." 655 ::= { mib-2 35 } 657 etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 } 659 dot3 OBJECT IDENTIFIER ::= { transmission 7 } 661 -- the Ethernet-like Statistics group 663 dot3StatsTable OBJECT-TYPE 664 SYNTAX SEQUENCE OF Dot3StatsEntry 665 MAX-ACCESS not-accessible 666 STATUS current 667 DESCRIPTION "Statistics for a collection of ethernet-like 668 interfaces attached to a particular system." 669 ::= { dot3 2 } 671 dot3StatsEntry OBJECT-TYPE 672 SYNTAX Dot3StatsEntry 673 MAX-ACCESS not-accessible 674 STATUS current 675 DESCRIPTION "Statistics for a particular interface to an 676 ethernet-like medium." 677 INDEX { dot3StatsIndex } 678 ::= { dot3StatsTable 1 } 680 Dot3StatsEntry ::= 681 SEQUENCE { 682 dot3StatsIndex InterfaceIndex, 683 dot3StatsAlignmentErrors Counter32, 684 dot3StatsFCSErrors Counter32, 685 dot3StatsSingleCollisionFrames Counter32, 686 dot3StatsMultipleCollisionFrames Counter32, 687 dot3StatsSQETestErrors Counter32, 688 dot3StatsDeferredTransmissions Counter32, 689 dot3StatsLateCollisions Counter32, 690 dot3StatsExcessiveCollisions Counter32, 691 dot3StatsInternalMacTransmitErrors Counter32, 692 dot3StatsCarrierSenseErrors Counter32, 693 dot3StatsFrameTooLongs Counter32, 694 dot3StatsInternalMacReceiveErrors Counter32, 695 dot3StatsEtherChipSet OBJECT IDENTIFIER, 696 dot3StatsSymbolErrors Counter32 697 } 699 dot3StatsIndex OBJECT-TYPE 700 SYNTAX InterfaceIndex 701 MAX-ACCESS read-only 702 STATUS current 703 DESCRIPTION "An index value that uniquely identifies an 704 interface to an ethernet-like medium. The 705 interface identified by a particular value of 706 this index is the same interface as identified 707 by the same value of ifIndex." 708 REFERENCE "RFC 2233, ifIndex" 709 ::= { dot3StatsEntry 1 } 711 dot3StatsAlignmentErrors OBJECT-TYPE 712 SYNTAX Counter32 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION "A count of frames received on a particular 716 interface that are not an integral number of 717 octets in length and do not pass the FCS check. 719 The count represented by an instance of this 720 object is incremented when the alignmentError 721 status is returned by the MAC service to the 722 LLC (or other MAC user). Received frames for 723 which multiple error conditions obtain are, 724 according to the conventions of IEEE 802.3 725 Layer Management, counted exclusively according 726 to the error status presented to the LLC. 728 This counter does not increment for 8-bit wide 729 group encoding schemes." 730 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.7, 731 aAlignmentErrors" 732 ::= { dot3StatsEntry 2 } 734 dot3StatsFCSErrors OBJECT-TYPE 735 SYNTAX Counter32 736 MAX-ACCESS read-only 737 STATUS current 738 DESCRIPTION "A count of frames received on a particular 739 interface that are an integral number of octets 740 in length but do not pass the FCS check. This 741 count does not include frames received with 742 frame-too-long or frame-too-short error. 744 The count represented by an instance of this 745 object is incremented when the frameCheckError 746 status is returned by the MAC service to the 747 LLC (or other MAC user). Received frames for 748 which multiple error conditions obtain are, 749 according to the conventions of IEEE 802.3 750 Layer Management, counted exclusively according 751 to the error status presented to the LLC. 753 Note: Coding errors detected by the physical 754 layer for speeds above 10 Mb/s will cause the 755 frame to fail the FCS check." 756 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.6, 757 aFrameCheckSequenceErrors." 758 ::= { dot3StatsEntry 3 } 760 dot3StatsSingleCollisionFrames OBJECT-TYPE 761 SYNTAX Counter32 762 MAX-ACCESS read-only 763 STATUS current 764 DESCRIPTION "A count of successfully transmitted frames on 765 a particular interface for which transmission 766 is inhibited by exactly one collision. 768 A frame that is counted by an instance of this 769 object is also counted by the corresponding 770 instance of either the ifOutUcastPkts, 771 ifOutMulticastPkts, or ifOutBroadcastPkts, 772 and is not counted by the corresponding 773 instance of the dot3StatsMultipleCollisionFrames 774 object. 776 This counter does not increment when the 777 interface is operating in full-duplex mode." 778 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.3, 779 aSingleCollisionFrames." 780 ::= { dot3StatsEntry 4 } 782 dot3StatsMultipleCollisionFrames OBJECT-TYPE 783 SYNTAX Counter32 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION "A count of successfully transmitted frames on 787 a particular interface for which transmission 788 is inhibited by more than one collision. 790 A frame that is counted by an instance of this 791 object is also counted by the corresponding 792 instance of either the ifOutUcastPkts, 793 ifOutMulticastPkts, or ifOutBroadcastPkts, 794 and is not counted by the corresponding 795 instance of the dot3StatsSingleCollisionFrames 796 object. 798 This counter does not increment when the 799 interface is operating in full-duplex mode." 801 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.4, 802 aMultipleCollisionFrames." 803 ::= { dot3StatsEntry 5 } 805 dot3StatsSQETestErrors OBJECT-TYPE 806 SYNTAX Counter32 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION "A count of times that the SQE TEST ERROR 810 message is generated by the PLS sublayer for a 811 particular interface. The SQE TEST ERROR 812 is set in accordance with the rules for 813 verification of the SQE detection mechanism in 814 the PLS Carrier Sense Function as described in 815 ANSI/IEEE 802.3-1996, section 7.2.4.6. 817 This counter does not increment on interfaces 818 operating at speeds greater than 10 Mb/s, or on 819 interfaces operating in full-duplex mode." 820 REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4, 821 aSQETestErrors." 822 ::= { dot3StatsEntry 6 } 824 dot3StatsDeferredTransmissions OBJECT-TYPE 825 SYNTAX Counter32 826 MAX-ACCESS read-only 827 STATUS current 828 DESCRIPTION "A count of frames for which the first 829 transmission attempt on a particular interface 830 is delayed because the medium is busy. 832 The count represented by an instance of this 833 object does not include frames involved in 834 collisions. 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.9, 839 aFramesWithDeferredXmissions." 840 ::= { dot3StatsEntry 7 } 842 dot3StatsLateCollisions OBJECT-TYPE 843 SYNTAX Counter32 844 MAX-ACCESS read-only 845 STATUS current 846 DESCRIPTION "The number of times that a collision is 847 detected on a particular interface later than 848 one slotTime into the transmission of a packet. 850 A (late) collision included in a count 851 represented by an instance of this object is 852 also considered as a (generic) collision for 853 purposes of other collision-related 854 statistics. 856 This counter does not increment when the 857 interface is operating in full-duplex mode." 858 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.10, 859 aLateCollisions." 860 ::= { dot3StatsEntry 8 } 862 dot3StatsExcessiveCollisions OBJECT-TYPE 863 SYNTAX Counter32 864 MAX-ACCESS read-only 865 STATUS current 866 DESCRIPTION "A count of frames for which transmission on a 867 particular interface fails due to excessive 868 collisions. 870 This counter does not increment when the 871 interface is operating in full-duplex mode." 872 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.11, 873 aFramesAbortedDueToXSColls." 874 ::= { dot3StatsEntry 9 } 876 dot3StatsInternalMacTransmitErrors OBJECT-TYPE 877 SYNTAX Counter32 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION "A count of frames for which transmission on a 881 particular interface fails due to an internal 882 MAC sublayer transmit error. A frame is only 883 counted by an instance of this object if it is 884 not counted by the corresponding instance of 885 either the dot3StatsLateCollisions object, the 886 dot3StatsExcessiveCollisions object, or the 887 dot3StatsCarrierSenseErrors object. 889 The precise meaning of the count represented by 890 an instance of this object is implementation- 891 specific. In particular, an instance of this 892 object may represent a count of transmission 893 errors on a particular interface that are not 894 otherwise counted." 895 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.12, 896 aFramesLostDueToIntMACXmitError." 897 ::= { dot3StatsEntry 10 } 899 dot3StatsCarrierSenseErrors OBJECT-TYPE 900 SYNTAX Counter32 901 MAX-ACCESS read-only 902 STATUS current 903 DESCRIPTION "The number of times that the carrier sense 904 condition was lost or never asserted when 905 attempting to transmit a frame on a particular 906 interface. 908 The count represented by an instance of this 909 object is incremented at most once per 910 transmission attempt, even if the carrier sense 911 condition fluctuates during a transmission 912 attempt. 914 This counter does not increment when the 915 interface is operating in full-duplex mode." 916 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.13, 917 aCarrierSenseErrors." 918 ::= { dot3StatsEntry 11 } 920 -- { dot3StatsEntry 12 } is not assigned 922 dot3StatsFrameTooLongs OBJECT-TYPE 923 SYNTAX Counter32 924 MAX-ACCESS read-only 925 STATUS current 926 DESCRIPTION "A count of frames received on a particular 927 interface that exceed the maximum permitted 928 frame size. 930 The count represented by an instance of this 931 object is incremented when the frameTooLong 932 status is returned by the MAC service to the 933 LLC (or other MAC user). Received frames for 934 which multiple error conditions obtain are, 935 according to the conventions of IEEE 802.3 936 Layer Management, counted exclusively according 937 to the error status presented to the LLC." 938 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.25, 939 aFrameTooLongErrors." 940 ::= { dot3StatsEntry 13 } 942 -- { dot3StatsEntry 14 } is not assigned 943 -- { dot3StatsEntry 15 } is not assigned 945 dot3StatsInternalMacReceiveErrors OBJECT-TYPE 946 SYNTAX Counter32 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION "A count of frames for which reception on a 950 particular interface fails due to an internal 951 MAC sublayer receive error. A frame is only 952 counted by an instance of this object if it is 953 not counted by the corresponding instance of 954 either the dot3StatsFrameTooLongs object, the 955 dot3StatsAlignmentErrors object, or the 956 dot3StatsFCSErrors object. 958 The precise meaning of the count represented by 959 an instance of this object is implementation- 960 specific. In particular, an instance of this 961 object may represent a count of receive errors 962 on a particular interface that are not 963 otherwise counted." 964 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15, 965 aFramesLostDueToIntMACRcvError." 966 ::= { dot3StatsEntry 16 } 968 dot3StatsEtherChipSet OBJECT-TYPE 969 SYNTAX OBJECT IDENTIFIER 970 MAX-ACCESS read-only 971 STATUS current 972 DESCRIPTION "This object contains an OBJECT IDENTIFIER 973 which identifies the chipset used to 974 realize the interface. Ethernet-like 975 interfaces are typically built out of 976 several different chips. The MIB implementor 977 is presented with a decision of which chip 978 to identify via this object. The implementor 979 should identify the chip which is usually 980 called the Medium Access Control chip. 981 If no such chip is easily identifiable, 982 the implementor should identify the chip 983 which actually gathers the transmit 984 and receive statistics and error 985 indications. This would allow a 986 manager station to correlate the 987 statistics and the chip generating 988 them, giving it the ability to take 989 into account any known anomalies 990 in the chip." 992 ::= { dot3StatsEntry 17 } 994 dot3StatsSymbolErrors OBJECT-TYPE 995 SYNTAX Counter32 996 MAX-ACCESS read-only 997 STATUS current 998 DESCRIPTION "For an interface operating at 100 Mb/s, the 999 number of times there was an invalid data symbol 1000 when a valid carrier was present. 1002 For an interface operating in half-duplex mode 1003 at 1000 Mb/s, the number of times the receiving 1004 media is non-idle (a carrier event) for a period 1005 of time equal to or greater than slotTime, and 1006 during which there was at least one occurrence 1007 of an event that causes the PHY to indicate 1008 'Data reception error' or 'carrier extend error' 1009 on the GMII. 1011 For an interface operating in full-duplex mode 1012 at 1000 Mb/s, the number of times the receiving 1013 media is non-idle a carrier event) for a period 1014 of time equal to or greater than minFrameSize, 1015 and during which there was at least one 1016 occurrence of an event that causes the PHY to 1017 indicate 'Data reception error' on the GMII. 1019 The count represented by an instance of this 1020 object is incremented at most once per carrier 1021 event, even if multiple symbol errors occur 1022 during the carrier event. This count does 1023 not increment if a collision is present." 1024 REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, 1025 aSymbolErrorDuringCarrier." 1026 ::= { dot3StatsEntry 18 } 1028 -- the Ethernet-like Collision Statistics group 1030 -- Implementation of this group is optional; it is appropriate 1031 -- for all systems which have the necessary metering 1033 dot3CollTable OBJECT-TYPE 1034 SYNTAX SEQUENCE OF Dot3CollEntry 1035 MAX-ACCESS not-accessible 1036 STATUS current 1037 DESCRIPTION "A collection of collision histograms for a 1038 particular set of interfaces." 1039 REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.30, 1040 aCollisionFrames." 1041 ::= { dot3 5 } 1043 dot3CollEntry OBJECT-TYPE 1044 SYNTAX Dot3CollEntry 1045 MAX-ACCESS not-accessible 1046 STATUS current 1047 DESCRIPTION "A cell in the histogram of per-frame 1048 collisions for a particular interface. An 1049 instance of this object represents the 1050 frequency of individual MAC frames for which 1051 the transmission (successful or otherwise) on a 1052 particular interface is accompanied by a 1053 particular number of media collisions." 1054 INDEX { ifIndex, dot3CollCount } 1055 ::= { dot3CollTable 1 } 1057 Dot3CollEntry ::= 1058 SEQUENCE { 1059 dot3CollCount INTEGER, 1060 dot3CollFrequencies Counter32 1061 } 1063 -- { dot3CollEntry 1 } is no longer in use 1065 dot3CollCount OBJECT-TYPE 1066 SYNTAX INTEGER (1..16) 1067 MAX-ACCESS not-accessible 1068 STATUS current 1069 DESCRIPTION "The number of per-frame media collisions for 1070 which a particular collision histogram cell 1071 represents the frequency on a particular 1072 interface." 1073 ::= { dot3CollEntry 2 } 1075 dot3CollFrequencies OBJECT-TYPE 1076 SYNTAX Counter32 1077 MAX-ACCESS read-only 1078 STATUS current 1079 DESCRIPTION "A count of individual MAC frames for which the 1080 transmission (successful or otherwise) on a 1081 particular interface occurs after the 1082 frame has experienced exactly the number 1083 of collisions in the associated 1084 dot3CollCount object. 1086 For example, a frame which is transmitted 1087 on interface 77 after experiencing 1088 exactly 4 collisions would be indicated 1089 by incrementing only dot3CollFrequencies.77.4. 1090 No other instance of dot3CollFrequencies would 1091 be incremented in this example. 1093 This counter does not increment when the 1094 interface is operating in full-duplex mode." 1095 ::= { dot3CollEntry 3 } 1097 dot3ControlTable OBJECT-TYPE 1098 SYNTAX SEQUENCE OF Dot3ControlEntry 1099 MAX-ACCESS not-accessible 1100 STATUS current 1101 DESCRIPTION "A table of descriptive and status information 1102 about the MAC Control sublayer on the 1103 ethernet-like interfaces attached to a 1104 particular system." 1105 ::= { dot3 9 } 1107 dot3ControlEntry OBJECT-TYPE 1108 SYNTAX Dot3ControlEntry 1109 MAX-ACCESS not-accessible 1110 STATUS current 1111 DESCRIPTION "An entry in the table, containing information 1112 about the MAC Control sublayer on a single 1113 ethernet-like interface." 1114 INDEX { dot3StatsIndex } 1115 ::= { dot3ControlTable 1 } 1117 Dot3ControlEntry ::= 1118 SEQUENCE { 1119 dot3ControlFunctionsSupported BITS, 1120 dot3ControlInUnknownOpcodes Counter32, 1121 dot3ControlPauseMode INTEGER, 1122 dot3ControlPauseLinkDelayAllowance Unsigned32, 1123 dot3ControlInPauseFrames Counter32, 1124 dot3ControlOutPauseFrames Counter32 1125 } 1127 dot3ControlFunctionsSupported OBJECT-TYPE 1128 SYNTAX BITS { 1129 pause(0) 1130 } 1131 MAX-ACCESS read-write 1132 STATUS current 1133 DESCRIPTION "A list of the possible MAC Control functions 1134 implemented for this interface." 1135 REFERENCE "[IEEE 802.3 Std.], 30.3.3.2, 1136 aMACControlFunctionsSupported." 1137 ::= { dot3ControlEntry 1 } 1139 dot3ControlInUnknownOpcodes OBJECT-TYPE 1140 SYNTAX Counter32 1141 MAX-ACCESS read-only 1142 STATUS current 1143 DESCRIPTION "A count of MAC Control frames received on this 1144 interface that contain an opcode that is not 1145 supported by this device." 1146 REFERENCE "[IEEE 802.3 Std.], 30.3.3.5, 1147 aUnsupportedOpcodesReceived" 1148 ::= { dot3ControlEntry 2 } 1150 dot3ControlPauseMode OBJECT-TYPE 1151 SYNTAX INTEGER { 1152 disabled(1), 1153 enabledXmit(2), 1154 enabledRcv(3), 1155 enabledXmitAndRcv(4) 1156 } 1157 MAX-ACCESS read-only 1158 STATUS current 1159 DESCRIPTION "This object reflects the PAUSE mode currently 1160 in use on this interface. Interfaces operating 1161 at less than 1000 Mb/s will never return 1162 'enabledXmit(2)' or 'enabledRcv(3)'. Interfaces 1163 which have not yet completed auto-negotiation 1164 should return the value 'disabled(1)'." 1165 ::= { dot3ControlEntry 3 } 1167 dot3ControlPauseLinkDelayAllowance OBJECT-TYPE 1168 SYNTAX Unsigned32 (0..4294967295) 1169 MAX-ACCESS read-write 1170 STATUS current 1171 DESCRIPTION "The allowance, in bit times, made by the PAUSE 1172 MAC Control entity for round-trip propagation 1173 delay of the full-duplex link." 1174 REFERENCE "[IEEE 802.3 Std.], 30.3.4.1, 1175 aPAUSELinkDelayAllowance." 1176 ::= { dot3ControlEntry 4 } 1178 dot3ControlInPauseFrames OBJECT-TYPE 1179 SYNTAX Counter32 1180 MAX-ACCESS read-only 1181 STATUS current 1182 DESCRIPTION "A count of MAC Control frames received on this 1183 interface with an opcode indicating the PAUSE 1184 operation. 1186 This counter does not increment when the 1187 interface is operating in half-duplex mode." 1188 REFERENCE "[IEEE 802.3 Std.], 30.3.4.3, 1189 aPAUSEMACCtrlFramesReceived." 1190 ::= { dot3ControlEntry 5 } 1192 dot3ControlOutPauseFrames OBJECT-TYPE 1193 SYNTAX Counter32 1194 MAX-ACCESS read-only 1195 STATUS current 1196 DESCRIPTION "A count of MAC Control frames transmitted on 1197 this interface with an opcode indicating the 1198 PAUSE operation. 1200 This counter does not increment when the 1201 interface is operating in half-duplex mode." 1202 REFERENCE "[IEEE 802.3 Std.], 30.3.4.2, 1203 aPAUSEMACCtrlFramesTransmitted." 1204 ::= { dot3ControlEntry 6 } 1206 -- 802.3 Tests 1208 dot3Tests OBJECT IDENTIFIER ::= { dot3 6 } 1210 dot3Errors OBJECT IDENTIFIER ::= { dot3 7 } 1212 -- TDR Test 1214 dot3TestTdr OBJECT-IDENTITY 1215 STATUS current 1216 DESCRIPTION "The Time-Domain Reflectometry (TDR) test is 1217 specific to ethernet-like interfaces of type 1218 10Base5 and 10Base2. The TDR value may be 1219 useful in determining the approximate distance 1220 to a cable fault. It is advisable to repeat 1221 this test to check for a consistent resulting 1222 TDR value, to verify that there is a fault. 1224 A TDR test returns as its result the time 1225 interval, measured in 10 MHz ticks or 100 nsec 1226 units, between the start of TDR test 1227 transmission and the subsequent detection of a 1228 collision or deassertion of carrier. On 1229 successful completion of a TDR test, the result 1230 is stored as the value of an appropriate 1231 instance of an appropriate vendor specific MIB 1232 object, and the OBJECT IDENTIFIER of that 1233 instance is stored in the appropriate instance 1234 of the appropriate test result code object 1235 (thereby indicating where the result has been 1236 stored)." 1237 ::= { dot3Tests 1 } 1239 -- Loopback Test 1241 dot3TestLoopBack OBJECT-IDENTITY 1242 STATUS current 1243 DESCRIPTION "This test configures the MAC chip and executes 1244 an internal loopback test of memory, data paths, 1245 and the MAC chip logic. This loopback test can 1246 only be executed if the interface is offline. 1247 Once the test has completed, the MAC chip should 1248 be reinitialized for network operation, but it 1249 should remain offline. 1251 If an error occurs during a test, the 1252 appropriate test result object will be set 1253 to indicate a failure. The two OBJECT 1254 IDENTIFIER values dot3ErrorInitError and 1255 dot3ErrorLoopbackError may be used to provided 1256 more information as values for an appropriate 1257 test result code object." 1258 ::= { dot3Tests 2 } 1260 dot3ErrorInitError OBJECT-IDENTITY 1261 STATUS current 1262 DESCRIPTION "Couldn't initialize MAC chip for test." 1263 ::= { dot3Errors 1 } 1265 dot3ErrorLoopbackError OBJECT-IDENTITY 1266 STATUS current 1267 DESCRIPTION "Expected data not received (or not received 1268 correctly) in loopback test." 1269 ::= { dot3Errors 2 } 1271 -- 802.3 Hardware Chipsets 1273 -- The object dot3StatsEtherChipSet is provided to 1274 -- identify the MAC hardware used to communicate on an 1275 -- interface. The following hardware chipsets are 1276 -- registered: 1278 dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 } 1280 dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 } 1282 dot3ChipSetAMD7990 OBJECT-IDENTITY 1283 STATUS current 1284 DESCRIPTION "The authoritative identifier for the Advanced 1285 Micro Devices Am7990 Local Area Network 1286 Controller for Ethernet (LANCE)." 1287 ::= { dot3ChipSetAMD 1 } 1289 dot3ChipSetAMD79900 OBJECT-IDENTITY 1290 STATUS current 1291 DESCRIPTION "The authoritative identifier for the Advanced 1292 Micro Devices Am79900 chip." 1293 ::= { dot3ChipSetAMD 2 } 1295 dot3ChipSetAMD79C940 OBJECT-IDENTITY 1296 STATUS current 1297 DESCRIPTION "The authoritative identifier for the Advanced 1298 Micro Devices Am79C940 Media Access Controller 1299 for Ethernet (MACE)." 1300 ::= { dot3ChipSetAMD 3 } 1302 dot3ChipSetAMD79C90 OBJECT-IDENTITY 1303 STATUS current 1304 DESCRIPTION "The authoritative identifier for the Advanced 1305 Micro Devices Am79C90 CMOS Local Area Network 1306 Controller for Ethernet (C-LANCE)." 1307 ::= { dot3ChipSetAMD 4 } 1309 dot3ChipSetAMD79C960 OBJECT-IDENTITY 1310 STATUS current 1311 DESCRIPTION "The authoritative identifier for the Advanced 1312 Micro Devices Am79C960 PCnet-ISA Single Chip 1313 Ethernet Controller for ISA." 1314 ::= { dot3ChipSetAMD 5 } 1316 dot3ChipSetAMD79C961 OBJECT-IDENTITY 1317 STATUS current 1318 DESCRIPTION "The authoritative identifier for the Advanced 1319 Micro Devices Am79C961 PCnet-ISA+ Single Chip 1320 Plug & Play Full-Duplex Ethernet Controller 1321 for ISA." 1323 ::= { dot3ChipSetAMD 6 } 1325 dot3ChipSetAMD79C961A OBJECT-IDENTITY 1326 STATUS current 1327 DESCRIPTION "The authoritative identifier for the Advanced 1328 Micro Devices Am79C961A PCnet-ISA II Single Chip 1329 Plug & Play Full-Duplex Ethernet Controller 1330 for ISA." 1331 ::= { dot3ChipSetAMD 7 } 1333 dot3ChipSetAMD79C965 OBJECT-IDENTITY 1334 STATUS current 1335 DESCRIPTION "The authoritative identifier for the Advanced 1336 Micro Devices Am79C965 PCnet-32 Single Chip 1337 Ethernet Controller for PCI." 1338 ::= { dot3ChipSetAMD 8 } 1340 dot3ChipSetAMD79C970 OBJECT-IDENTITY 1341 STATUS current 1342 DESCRIPTION "The authoritative identifier for the Advanced 1343 Micro Devices Am79C970 PCnet PCI Single Chip 1344 Ethernet Controller for PCI Local Bus." 1345 ::= { dot3ChipSetAMD 9 } 1347 dot3ChipSetAMD79C970A OBJECT-IDENTITY 1348 STATUS current 1349 DESCRIPTION "The authoritative identifier for the Advanced 1350 Micro Devices AM79C970A PCnet PCI II Single Chip 1351 Full-Duplex Ethernet Controller for PCI Local 1352 Bus." 1353 ::= { dot3ChipSetAMD 10 } 1355 dot3ChipSetAMD79C971 OBJECT-IDENTITY 1356 STATUS current 1357 DESCRIPTION "The authoritative identifier for the Advanced 1358 Micro Devices Am79C971 PCnet-FAST Single Chip 1359 Full-Duplex 10/100 Mbps Ethernet Controller for 1360 PCI Local Bus." 1361 ::= { dot3ChipSetAMD 11 } 1363 dot3ChipSetAMD79C972 OBJECT-IDENTITY 1364 STATUS current 1365 DESCRIPTION "The authoritative identifier for the Advanced 1366 Micro Devices Am79C972 PCnet-FAST+ Enhanced 1367 10/100 Mbps PCI Ethernet Controller with OnNow 1368 Support." 1369 ::= { dot3ChipSetAMD 12 } 1371 dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 } 1373 dot3ChipSetIntel82586 OBJECT-IDENTITY 1374 STATUS current 1375 DESCRIPTION "The authoritative identifier for the Intel 1376 82586 IEEE 802.3 Ethernet LAN Coprocessor." 1377 ::= { dot3ChipSetIntel 1 } 1379 dot3ChipSetIntel82596 OBJECT-IDENTITY 1380 STATUS current 1381 DESCRIPTION "The authoritative identifier for the Intel 1382 82596 High-Performance 32-Bit Local Area Network 1383 Coprocessor." 1384 ::= { dot3ChipSetIntel 2 } 1386 dot3ChipSetIntel82595 OBJECT-IDENTITY 1387 STATUS current 1388 DESCRIPTION "The authoritative identifier for the Intel 1389 82595 High Integration Ethernet Controller." 1390 ::= { dot3ChipSetIntel 3 } 1392 dot3ChipSetIntel82557 OBJECT-IDENTITY 1393 STATUS current 1394 DESCRIPTION "The authoritative identifier for the Intel 1395 82557 Fast Ethernet PCI Bus Lan Controller." 1396 ::= { dot3ChipSetIntel 4 } 1398 dot3ChipSetIntel82558 OBJECT-IDENTITY 1399 STATUS current 1400 DESCRIPTION "The authoritative identifier for the Intel 1401 82558 Fast Ethernet PCI Bus LAN Controller with 1402 Integrated PHY." 1403 ::= { dot3ChipSetIntel 5 } 1405 dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 } 1407 dot3ChipSetSeeq8003 OBJECT-IDENTITY 1408 STATUS current 1409 DESCRIPTION "The authoritative identifier for the SEEQ 1410 8003 chip set." 1411 ::= { dot3ChipSetSeeq 1 } 1413 dot3ChipSetSeeq80C03 OBJECT-IDENTITY 1414 STATUS current 1415 DESCRIPTION "The authoritative identifier for the SEEQ 1416 80C03 Full-Duplex CMOS Ethernet Data Link 1417 Controller (MAC)." 1418 ::= { dot3ChipSetSeeq 2 } 1420 dot3ChipSetSeeq84C30 OBJECT-IDENTITY 1421 STATUS current 1422 DESCRIPTION "The authoritative identifier for the SEEQ 1423 4-Port 84C30 Full-Duplex CMOS Ethernet 10 1424 MBit/Sec Data Link Controller (MAC)." 1425 ::= { dot3ChipSetSeeq 3 } 1427 dot3ChipSetSeeq8431 OBJECT-IDENTITY 1428 STATUS current 1429 DESCRIPTION "The authoritative identifier for the SEEQ 1430 4-Port 8431 Full-Duplex CMOS Ethernet 10 1431 MBit/Sec Data Link Controller (MAC)." 1432 ::= { dot3ChipSetSeeq 4 } 1434 dot3ChipSetSeeq80C300 OBJECT-IDENTITY 1435 STATUS current 1436 DESCRIPTION "The authoritative identifier for the SEEQ 1437 80C300 Full-Duplex CMOS Ethernet 10/100 1438 Mbit/Sec Data Link Controller (MAC)." 1439 ::= { dot3ChipSetSeeq 5 } 1441 dot3ChipSetSeeq84C300 OBJECT-IDENTITY 1442 STATUS current 1443 DESCRIPTION "The authoritative identifier for the SEEQ 1444 4-Port 84C300 Fast Ethernet Controller (MAC)." 1445 ::= { dot3ChipSetSeeq 6 } 1447 dot3ChipSetSeeq84301 OBJECT-IDENTITY 1448 STATUS current 1449 DESCRIPTION "The authoritative identifier for the SEEQ 1450 4-Port 84301 Fast Ethernet Controller (MAC)." 1451 ::= { dot3ChipSetSeeq 7 } 1453 dot3ChipSetSeeq84302 OBJECT-IDENTITY 1454 STATUS current 1455 DESCRIPTION "The authoritative identifier for the SEEQ 1456 4-Port 84302 Fast Ethernet Controller (MAC)." 1457 ::= { dot3ChipSetSeeq 8 } 1459 dot3ChipSetSeeq8100 OBJECT-IDENTITY 1460 STATUS current 1461 DESCRIPTION "The authoritative identifier for the SEEQ 1462 8100 Gigabit Ethernet Controller (MAC & PCS)." 1463 ::= { dot3ChipSetSeeq 9 } 1465 dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 } 1467 dot3ChipSetNational8390 OBJECT-IDENTITY 1468 STATUS current 1469 DESCRIPTION "The authoritative identifier for the National 1470 Semiconductor DP8390 Network Interface 1471 Controller." 1472 ::= { dot3ChipSetNational 1 } 1474 dot3ChipSetNationalSonic OBJECT-IDENTITY 1475 STATUS current 1476 DESCRIPTION "The authoritative identifier for the National 1477 Semiconductor DP83932 Systems-Oriented Network 1478 Interface Controller (SONIC)." 1479 ::= { dot3ChipSetNational 2 } 1481 dot3ChipSetNational83901 OBJECT-IDENTITY 1482 STATUS current 1483 DESCRIPTION "The authoritative identifier for the National 1484 Semiconductor DP83901 Serial Network Interface 1485 Controller (SNIC)." 1486 ::= { dot3ChipSetNational 3 } 1488 dot3ChipSetNational83902 OBJECT-IDENTITY 1489 STATUS current 1490 DESCRIPTION "The authoritative identifier for the National 1491 Semiconductor DP83902 Serial Network Interface 1492 Controller for Twisted Pair (ST-NIC)." 1493 ::= { dot3ChipSetNational 4 } 1495 dot3ChipSetNational83905 OBJECT-IDENTITY 1496 STATUS current 1497 DESCRIPTION "The authoritative identifier for the National 1498 Semiconductor DP83905 AT Local Area Network 1499 Twisted-Pair Interface (AT/LANTIC)." 1500 ::= { dot3ChipSetNational 5 } 1502 dot3ChipSetNational83907 OBJECT-IDENTITY 1503 STATUS current 1504 DESCRIPTION "The authoritative identifier for the National 1505 Semiconductor DP83907 AT Twisted-Pair Enhanced 1506 Coaxial Network Interface Controller 1507 (AT/LANTIC II)." 1508 ::= { dot3ChipSetNational 6 } 1510 dot3ChipSetNational83916 OBJECT-IDENTITY 1511 STATUS current 1512 DESCRIPTION "The authoritative identifier for the National 1513 Semiconductor DP83916 Systems-Oriented Network 1514 Interface Controller (SONIC-16)." 1515 ::= { dot3ChipSetNational 7 } 1517 dot3ChipSetNational83934 OBJECT-IDENTITY 1518 STATUS current 1519 DESCRIPTION "The authoritative identifier for the National 1520 Semiconductor DP83934 Systems-Oriented Network 1521 Interface Controller with Twisted Pair Interface 1522 (SONIC-T)." 1523 ::= { dot3ChipSetNational 8 } 1525 dot3ChipSetNational83936 OBJECT-IDENTITY 1526 STATUS current 1527 DESCRIPTION "The authoritative identifier for the National 1528 Semiconductor DP83936AVUL Full-Duplex Systems- 1529 Oriented Network Interface Controller with 1530 Twisted Pair Interface (SONIC-T)." 1531 ::= { dot3ChipSetNational 9 } 1533 dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 } 1535 dot3ChipSetFujitsu86950 OBJECT-IDENTITY 1536 STATUS current 1537 DESCRIPTION "The authoritative identifier for the Fujitsu 1538 86950 chip." 1539 ::= { dot3ChipSetFujitsu 1 } 1541 dot3ChipSetFujitsu86960 OBJECT-IDENTITY 1542 STATUS current 1543 DESCRIPTION "The authoritative identifier for the Fujitsu 1544 MB86960 Network Interface Controller with 1545 Encoder/Decoder (NICE)." 1546 ::= { dot3ChipSetFujitsu 2 } 1548 dot3ChipSetFujitsu86964 OBJECT-IDENTITY 1549 STATUS current 1550 DESCRIPTION "The authoritative identifier for the Fujitsu 1551 MB86964 Ethernet Controller with 10BASE-T 1552 Tranceiver." 1553 ::= { dot3ChipSetFujitsu 3 } 1555 dot3ChipSetFujitsu86965A OBJECT-IDENTITY 1556 STATUS current 1557 DESCRIPTION "The authoritative identifier for the Fujitsu 1558 MB86965A EtherCoupler Single-Chip Ethernet 1559 Controller." 1560 ::= { dot3ChipSetFujitsu 4 } 1562 dot3ChipSetFujitsu86965B OBJECT-IDENTITY 1563 STATUS current 1564 DESCRIPTION "The authoritative identifier for the Fujitsu 1565 MB86965B EtherCoupler Single-Chip Ethernet 1566 Controller (supports full-duplex)." 1567 ::= { dot3ChipSetFujitsu 5 } 1569 dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 } 1571 dot3ChipSetDigitalDC21040 OBJECT-IDENTITY 1572 STATUS current 1573 DESCRIPTION "The authoritative identifier for the Digital 1574 Semiconductor DC21040 chip." 1575 ::= { dot3ChipSetDigital 1 } 1577 dot3ChipSetDigital21041 OBJECT-IDENTITY 1578 STATUS current 1579 DESCRIPTION "The authoritative identifier for the Digital 1580 Semiconductor 21041 PCI Ethernet LAN 1581 Controller." 1582 ::= { dot3ChipSetDigital 2 } 1584 dot3ChipSetDigital21140 OBJECT-IDENTITY 1585 STATUS current 1586 DESCRIPTION "The authoritative identifier for the Digital 1587 Semiconductor 21140 PCI Fast Ethernet LAN 1588 Controller." 1589 ::= { dot3ChipSetDigital 3 } 1591 dot3ChipSetDigital21143 OBJECT-IDENTITY 1592 STATUS current 1593 DESCRIPTION "The authoritative identifier for the Digital 1594 Semiconductor 21143 PCI/CardBus 10/100-Mb/s 1595 Ethernet LAN Controller." 1596 ::= { dot3ChipSetDigital 4 } 1598 dot3ChipSetDigital21340 OBJECT-IDENTITY 1599 STATUS current 1600 DESCRIPTION "The authoritative identifier for the Digital 1601 Semiconductor 21340 10/100-MB/s managed buffered 1602 port switch." 1603 ::= { dot3ChipSetDigital 5 } 1605 dot3ChipSetDigital21440 OBJECT-IDENTITY 1606 STATUS current 1607 DESCRIPTION "The authoritative identifier for the Digital 1608 Semiconductor 21440 Multiport 10/100Mbps 1609 Ethernet Controller." 1610 ::= { dot3ChipSetDigital 6 } 1612 dot3ChipSetDigital21540 OBJECT-IDENTITY 1613 STATUS current 1614 DESCRIPTION "The authoritative identifier for the Digital 1615 Semiconductor 21540 PCI/CardBus Ethernet LAN 1616 Controller with Modem Interface." 1617 ::= { dot3ChipSetDigital 7 } 1619 dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 } 1621 dot3ChipSetTIE100 OBJECT-IDENTITY 1622 STATUS current 1623 DESCRIPTION "The authoritative identifier for the Texas 1624 Instruments TNETE100 ThunderLAN PCI Fast 1625 Ethernet Controller." 1626 ::= { dot3ChipSetTI 1 } 1628 dot3ChipSetTIE110 OBJECT-IDENTITY 1629 STATUS current 1630 DESCRIPTION "The authoritative identifier for the Texas 1631 Instruments TNETE110 ThunderLAN PCI 10BASE-T 1632 Ethernet Adapter." 1633 ::= { dot3ChipSetTI 2 } 1635 dot3ChipSetTIX3100 OBJECT-IDENTITY 1636 STATUS current 1637 DESCRIPTION "The authoritative identifier for the Texas 1638 Instruments TNETX3100 Desktop ThunderSWITCH 1639 8/2." 1640 ::= { dot3ChipSetTI 3 } 1642 dot3ChipSetTIX3150 OBJECT-IDENTITY 1643 STATUS current 1644 DESCRIPTION "The authoritative identifier for the Texas 1645 Instruments TNETX3150 ThunderSWITCH 12/3." 1646 ::= { dot3ChipSetTI 4 } 1648 dot3ChipSetTIX3270 OBJECT-IDENTITY 1649 STATUS current 1650 DESCRIPTION "The authoritative identifier for the Texas 1651 Instruments TNETX3270 ThunderSWITCH 24/3." 1652 ::= { dot3ChipSetTI 5 } 1654 dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 } 1656 dot3ChipSetToshibaTC35815F OBJECT-IDENTITY 1657 STATUS current 1658 DESCRIPTION "The authoritative identifier for the Toshiba 1659 TC35815F PCI-Based 100/10Mbps Ethernet 1660 Controller." 1662 ::= { dot3ChipSetToshiba 1 } 1664 dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 } 1666 dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY 1667 STATUS current 1668 DESCRIPTION "The authoritative identifier for the Lucent 1669 Technologies ATT1MX10 (Spinnaker) Quad MAC and 1670 Tranceiver for Ethernet Frame Switching." 1671 ::= { dot3ChipSetLucent 1 } 1673 dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY 1674 STATUS current 1675 DESCRIPTION "The authoritative identifier for the Lucent 1676 Technologies LUC3M08 Eight Ethernet MACs for 1677 10/100 Mbits/s Frame Switching." 1678 ::= { dot3ChipSetLucent 2 } 1680 dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 } 1682 dot3ChipSetGalileoGT48001 OBJECT-IDENTITY 1683 STATUS current 1684 DESCRIPTION "The authoritative identifier for the Galileo 1685 Technology GT-48001A Switched Ethernet 1686 Controller." 1687 ::= { dot3ChipSetGalileo 1 } 1689 dot3ChipSetGalileoGT48002 OBJECT-IDENTITY 1690 STATUS current 1691 DESCRIPTION "The authoritative identifier for the Galileo 1692 Technology GT-48002A Switched Fast Ethernet 1693 Controller." 1694 ::= { dot3ChipSetGalileo 2 } 1696 dot3ChipSetGalileoGT48004 OBJECT-IDENTITY 1697 STATUS current 1698 DESCRIPTION "The authoritative identifier for the Galileo 1699 Technology GT-48004A Four Port Fast Ethernet 1700 Switch for Multiport 10/100BASE-X Systems." 1701 ::= { dot3ChipSetGalileo 3 } 1703 dot3ChipSetGalileoGT48207 OBJECT-IDENTITY 1704 STATUS current 1705 DESCRIPTION "The authoritative identifier for the Galileo 1706 Technology GT-48207 Low-Cost 10 Port Switched 1707 Ethernet Controller for 10+10/100BASE-X." 1708 ::= { dot3ChipSetGalileo 4 } 1710 dot3ChipSetGalileoGT48208 OBJECT-IDENTITY 1711 STATUS current 1712 DESCRIPTION "The authoritative identifier for the Galileo 1713 Technology GT-48208 Advanced 10 Port Switched 1714 Ethernet Controller for 10+10/100BASE-X." 1715 ::= { dot3ChipSetGalileo 5 } 1717 dot3ChipSetGalileoGT48212 OBJECT-IDENTITY 1718 STATUS current 1719 DESCRIPTION "The authoritative identifier for the Galileo 1720 Technology GT-48212 Advanced 14 Port Switched 1721 Ethernet Controller for 10+10/100BASE-X." 1722 ::= { dot3ChipSetGalileo 6 } 1724 dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 } 1726 dot3ChipSetJatoJT1001 OBJECT-IDENTITY 1727 STATUS current 1728 DESCRIPTION "The authoritative identifier for the Jato 1729 Technologies JT1001 GigEMAC Server 1730 10/100/1000Mbps Ethernet Controller with PCI 1731 interface." 1732 ::= { dot3ChipSetJato 1 } 1734 dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 } 1736 dot3ChipSetXaQtiXQ11800FP OBJECT-IDENTITY 1737 STATUS current 1738 DESCRIPTION "The authoritative identifier for the XaQTI 1739 XQ11800FP XMAC II Gigabit Ethernet Media Access 1740 Controller." 1741 ::= { dot3ChipSetXaQti 1 } 1743 dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY 1744 STATUS current 1745 DESCRIPTION "The authoritative identifier for the XaQTI 1746 XQ18110FP GigaPower Protocol Accelerator." 1747 ::= { dot3ChipSetXaQti 2 } 1749 -- For those chipsets not represented above, OBJECT IDENTIFIER 1750 -- assignment is required in other documentation, e.g., 1751 -- assignment within that part of the registration tree 1752 -- delegated to individual enterprises (see RFC 1155 and 1753 -- RFC 1902). 1754 -- 1755 -- In the future, management of chipset registrations may be 1756 -- delegated to the Internet Assigned Numbers Authority (IANA). 1758 -- conformance information 1760 etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 } 1762 etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 } 1763 etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 } 1765 -- compliance statements 1767 etherCompliance MODULE-COMPLIANCE 1768 STATUS current 1769 DESCRIPTION "The compliance statement for managed network 1770 entities which have ethernet-like network 1771 interfaces." 1773 MODULE -- this module 1774 MANDATORY-GROUPS { etherStatsGroup } 1776 GROUP etherCollisionTableGroup 1777 DESCRIPTION "This group is optional. It is appropriate 1778 for all systems which have the necessary 1779 metering. Implementation in such systems is 1780 highly recommended." 1781 ::= { etherCompliances 1 } 1783 ether100MbsCompliance MODULE-COMPLIANCE 1784 STATUS current 1785 DESCRIPTION "The compliance statement for managed network 1786 entities which have 100 Mb/sec ethernet-like 1787 network interfaces." 1789 MODULE -- this module 1790 MANDATORY-GROUPS { etherStats100MbsGroup } 1792 GROUP etherCollisionTableGroup 1793 DESCRIPTION "This group is optional. It is appropriate 1794 for all systems which have the necessary 1795 metering. Implementation in such systems is 1796 highly recommended." 1797 ::= { etherCompliances 2 } 1799 -- units of conformance 1801 etherStatsGroup OBJECT-GROUP 1802 OBJECTS { dot3StatsIndex, 1803 dot3StatsAlignmentErrors, 1804 dot3StatsFCSErrors, 1805 dot3StatsSingleCollisionFrames, 1806 dot3StatsMultipleCollisionFrames, 1807 dot3StatsSQETestErrors, 1808 dot3StatsDeferredTransmissions, 1809 dot3StatsLateCollisions, 1810 dot3StatsExcessiveCollisions, 1811 dot3StatsInternalMacTransmitErrors, 1812 dot3StatsCarrierSenseErrors, 1813 dot3StatsFrameTooLongs, 1814 dot3StatsInternalMacReceiveErrors, 1815 dot3StatsEtherChipSet 1816 } 1817 STATUS current 1818 DESCRIPTION "A collection of objects providing information 1819 applicable to all ethernet-like network 1820 interfaces." 1821 ::= { etherGroups 1 } 1823 etherCollisionTableGroup OBJECT-GROUP 1824 OBJECTS { dot3CollFrequencies 1825 } 1826 STATUS current 1827 DESCRIPTION "A collection of objects providing a histogram 1828 of packets successfully transmitted after 1829 experiencing exactly N collisions." 1830 ::= { etherGroups 2 } 1832 etherStats100MbsGroup OBJECT-GROUP 1833 OBJECTS { dot3StatsIndex, 1834 dot3StatsAlignmentErrors, 1835 dot3StatsFCSErrors, 1836 dot3StatsSingleCollisionFrames, 1837 dot3StatsMultipleCollisionFrames, 1838 dot3StatsDeferredTransmissions, 1839 dot3StatsLateCollisions, 1840 dot3StatsExcessiveCollisions, 1841 dot3StatsInternalMacTransmitErrors, 1842 dot3StatsCarrierSenseErrors, 1843 dot3StatsFrameTooLongs, 1844 dot3StatsInternalMacReceiveErrors, 1845 dot3StatsEtherChipSet, 1846 dot3StatsSymbolErrors 1847 } 1848 STATUS current 1849 DESCRIPTION "A collection of objects providing information 1850 applicable to 100 Mb/sec ethernet-like network 1851 interfaces." 1852 ::= { etherGroups 3 } 1854 etherControlGroup OBJECT-GROUP 1855 OBJECTS { dot3ControlFunctionsSupported, 1856 dot3ControlInUnknownOpcodes 1857 } 1858 STATUS current 1859 DESCRIPTION "A collection of objects providing information 1860 about the MAC Control sublayer on ethernet-like 1861 network interfaces." 1862 ::= { etherGroups 4 } 1864 etherControlPauseGroup OBJECT-GROUP 1865 OBJECTS { dot3ControlPauseMode, 1866 dot3ControlPauseLinkDelayAllowance, 1867 dot3ControlInPauseFrames, 1868 dot3ControlOutPauseFrames 1869 } 1870 STATUS current 1871 DESCRIPTION "A collection of objects providing information 1872 about the MAC Control PAUSE function on 1873 ethernet-like network interfaces." 1874 ::= { etherGroups 5 } 1876 END 1878 5. Intellectual Property 1880 The IETF takes no position regarding the validity or scope of any 1881 intellectual property or other rights that might be claimed to 1882 pertain to the implementation or use of the technology described in 1883 this document or the extent to which any license under such rights 1884 might or might not be available; neither does it represent that it 1885 has made any effort to identify any such rights. Information on the 1886 IETF's procedures with respect to rights in standards-track and 1887 standards-related documentation can be found in BCP-11. Copies of 1888 claims of rights made available for publication and any assurances of 1889 licenses to be made available, or the result of an attempt made to 1890 obtain a general license or permission for the use of such 1891 proprietary rights by implementors or users of this specification can 1892 be obtained from the IETF Secretariat. 1894 The IETF invites any interested party to bring to its attention any 1895 copyrights, patents or patent applications, or other proprietary 1896 rights which may cover technology that may be required to practice 1897 this standard. Please address the information to the IETF Executive 1898 Director. 1900 6. Acknowledgements 1902 This document was produced by the 802.3 Hub MIB Working Group. 1904 This document is based on the Proposed Standard Ethernet MIB, RFC 1905 2358 [26], edited by John Flick of Hewlett-Packard and Jeffrey 1906 Johnson of RedBack Networks and produced by the Ethernet Interfaces 1907 and Hub MIB Working Group. It extends that document by providing 1908 support for full-duplex Ethernet interfaces as outlined in [18] and 1909 1000 Mb/sec Ethernet interfaces as outlined in [19]. 1911 RFC 2358, in turn, is almost completely based on both the Standard 1912 Ethernet MIB, RFC 1643 [24], and the Proposed Standard Ethernet MIB 1913 using the SNMPv2 SMI, RFC 1650 [25], both of which were edited by 1914 Frank Kastenholz of FTP Software and produced by the Ethernet MIB 1915 Working Group. RFC 2358 extends those documents by providing support 1916 for 100 Mb/sec ethernet interfaces as outlined in [17]. 1918 RFC 1643 and RFC 1650, in turn, are based on the Draft Standard 1919 Ethernet MIB, RFC 1398 [23], also edited by Frank Kastenholz and 1920 produced by the Ethernet MIB Working Group. 1922 RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, 1923 RFC 1284 [21], which was edited by John Cook of Chipcom and produced 1924 by the Transmission MIB Working Group. The Ethernet MIB Working 1925 Group gathered implementation experience of the variables specified 1926 in RFC 1284, documented that experience in RFC 1369 [22], and used 1927 that information to develop this revised MIB. 1929 RFC 1284, in turn, is based on a document written by Frank 1930 Kastenholz, then of Interlan, entitled IEEE 802.3 Layer Management 1931 Draft M compatible MIB for TCP/IP Networks [20]. This document was 1932 modestly reworked, initially by the SNMP Working Group, and then by 1933 the Transmission Working Group, to reflect the current conventions 1934 for defining objects for MIB interfaces. James Davin, of the MIT 1935 Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN 1936 Systems, contributed to later drafts of this memo. Marshall Rose of 1937 Performance Systems International, Inc. converted the document into 1938 RFC 1212 [3] concise format. Anil Rijsinghani of DEC contributed text 1939 that more adequately describes the TDR test. Thanks to Frank 1940 Kastenholz of Interlan and Louis Steinberg of IBM for their 1941 experimentation. 1943 7. References 1945 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1946 Describing SNMP Management Frameworks", RFC 2271, Cabletron 1947 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1948 January 1998 1950 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1951 Management Information for TCP/IP-based Internets", STD 16, 1952 RFC 1155, Performance Systems International, Hughes LAN Systems, 1953 May 1990 1955 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, 1956 RFC 1212, Performance Systems International, Hughes LAN Systems, 1957 March 1991 1959 [4] M. Rose, "A Convention for Defining Traps for use with the 1960 SNMP", RFC 1215, Performance Systems International, March 1991 1962 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1963 "Structure of Management Information for Version 2 of the Simple 1964 Network Management Protocol (SNMPv2)", RFC 1902, SNMP Research, 1965 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1966 International Network Services, January 1996. 1968 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 1969 Conventions for Version 2 of the Simple Network Management 1970 Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco 1971 Systems, Inc., Dover Beach Consulting, Inc., International 1972 Network Services, January 1996. 1974 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1975 "Conformance Statements for Version 2 of the Simple Network 1976 Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., 1977 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1978 Network Services, January 1996. 1980 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1981 Network Management Protocol", STD 15, RFC 1157, SNMP Research, 1982 Performance Systems International, Performance Systems 1983 International, MIT Laboratory for Computer Science, May 1990. 1985 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1986 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 1987 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 1988 Inc., International Network Services, January 1996. 1990 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1991 "Transport Mappings for Version 2 of the Simple Network 1992 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 1993 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 1994 Network Services, January 1996. 1996 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1997 Processing and Dispatching for the Simple Network Management 1998 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron 1999 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 2000 January 1998. 2002 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 2003 for version 3 of the Simple Network Management Protocol 2004 (SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. 2006 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2007 Operations for Version 2 of the Simple Network Management 2008 Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco 2009 Systems, Inc., Dover Beach Consulting, Inc., International 2010 Network Services, January 1996. 2012 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2013 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 2014 Systems, January 1998 2016 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2017 Control Model (VACM) for the Simple Network Management Protocol 2018 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, 2019 Inc., Cisco Systems, Inc., January 1998 2021 [16] International Standard ISO/IEC 8802-3: 1996(E), (ANSI/IEEE Std 2022 802.3, 1996 Edition), "Information technology - 2023 Telecommunications and information exchange between systems - 2024 Local and metropolitan area networks - Specific requirements - 2025 Part 3: Carrier sense multiple access with collision detection 2026 (CSMA/CD) access method and physical layer specifications", July 2027 1996. 2029 [17] IEEE, IEEE Std 802.3u-1995, "Media Access Control (MAC) 2030 Parameters, Physical Layer, Medium Attachment Units, and 2031 Repeater for 100Mb/s Operation, Type 100BASE-T", Supplement to 2032 ISO/IEC 8802-3: 1993 (ANSI/IEEE Std 802.3, 1993 Edition), 2033 October 1995. 2035 [18] IEEE, IEEE Std 802.3x-1997 and IEEE Std 802.3y-1997, 2036 "Specification for 802.3 Full Duplex Operation and Physical 2037 Layer Specification for 100Mbit/s Operation on Two Pairs of 2038 Category 3 or Better Balanced Twisted Pair Cable (100BASE-T2)", 2039 Supplement to ISO/IEC 8802-3: 1996 (ANSI/IEEE Std 802.3, 1996 2040 Edition), November 1997. 2042 [19] IEEE, IEEE Draft 802.3z/D4.2, "Media Access Control (MAC) 2043 Parameters, Physical Layer, Repeater and Management Parameters 2044 for 1000 Mb/s Operation", Supplement to ISO/IEC 8802-3: 1996 2045 (ANSI/IEEE Std 802.3, 1996 Edition), March 1998. 2047 [20] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible 2048 MIB for TCP/IP Networks", electronic mail message to mib- 2049 wg@nnsc.nsf.net, 9 June 1989. 2051 [21] Cook, J., "Definitions of Managed Objects for Ethernet-Like 2052 Interface Types", RFC 1284, Chipcom Corporation, December 1991. 2054 [22] Kastenholz, F., "Implementation Notes and Experience for The 2055 Internet Ethernet MIB", RFC 1369, FTP Software, October 1992. 2057 [23] Kastenholz, F., "Definitions of Managed Objects for the 2058 Ethernet-like Interface Types", RFC 1398, FTP Software, Inc., 2059 January 1993. 2061 [24] Kastenholz, F., "Definitions of Managed Objects for the 2062 Ethernet-like Interface Types", STD 50, RFC 1643, FTP Software, 2063 Inc., July 1994. 2065 [25] Kastenholz, F., "Definitions of Managed Objects for the 2066 Ethernet-like Interface Types using SMIv2", RFC 1650, 2067 FTP Software, Inc., August 1994. 2069 [26] Flick, J., and J. Johnson, "Definitions of Managed Objects 2070 for the Ethernet-like Interface Types", RFC 2358, 2071 Hewlett-Packard Company, RedBack Networks, June 1998. 2073 [27] McCloghrie, K., and M. Rose, Editors, "Management Information 2074 Base for Network Management of TCP/IP-based internets: MIB-II", 2075 STD 17, RFC 1213, March 1991. 2077 [28] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB 2078 using SMIv2", RFC 2233, Cisco Systems, FTP Software, 2079 November 1997. 2081 [29] Bradner, S., "Key words for use in RFCs to Indicate 2082 Requirements Levels", BCP 14, RFC 2119, March 1997. 2084 [30] deGraaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and 2085 S. Roberts, "Definitions of Managed Objects for IEEE 802.3 2086 Medium Attachment Units (MAUs) using SMIv2", RFC 2239, 2087 3Com Corporation, Madge Networks (Israel) Ltd., Cisco Systems 2088 Inc., Cisco Systems Inc., Farallon Computing Inc., November 2089 1997. 2091 8. Security Considerations 2093 There are no management objects defined in this MIB that have a MAX- 2094 ACCESS clause of read-write and/or read-create. So, if this MIB is 2095 implemented correctly, then there is no risk that an intruder can 2096 alter or create any management objects of this MIB via direct SNMP 2097 SET operations. 2099 There are a number of managed objects in this MIB that may be 2100 considered to contain sensitive information. In particular, the 2101 dot3StatsEtherChipSet object may be considered sensitive in many 2102 environments, since it would allow an intruder to obtain information 2103 about which vendor's equipment is in use on the network. 2105 Therefore, it may be important in some environments to control read 2106 access to these objects and possibly to even encrypt the values of 2107 these object when sending them over the network via SNMP. Not all 2108 versions of SNMP provide features for such a secure environment. 2110 SNMPv1 by itself is such an insecure environment. Even if the 2111 network itself is secure (for example by using IPSec), even then, 2112 there is no control as to who on the secure network is allowed to 2113 access and GET (read) the objects in this MIB. 2115 It is recommended that the implementors consider the security 2116 features as provided by the SNMPv3 framework. Specifically, the use 2117 of the User-based Security Model RFC 2274 [12] and the View-based 2118 Access Control Model RFC 2275 [15] is recommended. 2120 It is then a customer/user responsibility to ensure that the SNMP 2121 entity giving access to an instance of this MIB, is properly 2122 configured to give access to those objects only to those principals 2123 (users) that have legitimate rights to access them. 2125 9. Author's Addresses 2127 John Flick 2128 Hewlett-Packard Company 2129 8000 Foothills Blvd. M/S 5556 2130 Roseville, CA 95747-5556 2132 Phone: +1 916 785 4018 2133 Email: johnf@rose.hp.com 2135 Jeffrey Johnson 2136 RedBack Networks 2137 2570 North First Street, Suite 410 2138 San Jose, CA, 95131, USA 2140 Phone: +1 408 571 2699 2141 EMail: jeff@redbacknetworks.com 2143 A. Change Log 2145 A.1. Changes since RFC 2358 2147 This section enumerates changes made to RFC 2358 to produce this 2148 document. 2150 (1) Section 2 has been replaced with the current SNMP 2151 Management Framework boilerplate. 2153 (2) The ifMtu mapping has been clarified. 2155 (3) The relationship between the IEEE 802.3 octet counters 2156 and the IF-MIB octet counters has been clarified. 2158 (4) REFERENCE clauses have been updated to reflect the 2159 actual IEEE 802.3 managed object that each MIB object 2160 is based on. 2162 (5) The following object DESCRIPTION clauses have been 2163 updated to reflect that they do not increment in 2164 full-duplex mode: dot3StatsSingleCollisionFrames, 2165 dot3StatsMultipleCollisionFrames, dot3StatsSQETestErrors, 2166 dot3StatsDeferredTransmissions, dot3StatsLateCollisions, 2167 dot3StatsExcessiveCollisions, dot3StatsCarrierSenseErrors, 2168 dot3CollFrequencies. 2170 (6) The following object DESCRIPTION clauses have been 2171 updated to reflect behaviour on full-duplex and 2172 1000 Mb/s interfaces: dot3StatsAlignmentErrors, 2173 dot3StatsFCSErrors, dot3StatsSQETestErrors, 2174 dot3StatsLateCollisions, dot3StatsSymbolErrors. 2176 (7) A new table, dot3ControlTable, has been added. 2178 (8) Two new conformance groups, etherControlGroup and 2179 etherControlPauseGroup, have been added. 2181 A.2. Changes between RFC 1650 and RFC 2358 2183 This section enumerates changes made to RFC 1650 to produce RFC 2358. 2185 (1) The MODULE-IDENTITY has been updated to reflect the changes 2186 in the MIB. 2188 (2) A new object, dot3StatsSymbolErrors, has been added. 2190 (3) The definition of the object dot3StatsIndex has been 2191 converted to use the SMIv2 OBJECT-TYPE macro. 2193 (4) A new conformance group, etherStats100MbsGroup, has been 2194 added. 2196 (5) A new compliance statement, ether100MbsCompliance, has 2197 been added. 2199 (6) The Acknowledgements were extended to provide a more 2200 complete history of the origin of this document. 2202 (7) The discussion of ifType has been expanded. 2204 (8) A section on mapping of Interfaces MIB objects has 2205 been added. 2207 (9) A section defining the relationship of this MIB to 2208 the MAU MIB has been added. 2210 (10) A section on the mapping of IEEE 802.3 managed objects 2211 to this MIB and the Interfaces MIB has been added. 2213 (11) Converted the dot3Tests, dot3Errors, and dot3ChipSets 2214 OIDs to use the OBJECT-IDENTITY macro. 2216 (12) Added to the list of registered dot3ChipSets. 2218 (13) An intellectual property notice and copyright notice 2219 were added, as required by RFC 2026. 2221 B. Full Copyright Statement 2223 This document and translations of it may be copied and furnished to 2224 others, and derivative works that comment on or otherwise explain it 2225 or assist in its implementation may be prepared, copied, published 2226 and distributed, in whole or in part, without restriction of any 2227 kind, provided that the above copyright notice and this paragraph are 2228 included on all such copies and derivative works. However, this 2229 document itself may not be modified in any way, such as by removing 2230 the copyright notice or references to the Internet Society or other 2231 Internet organizations, except as needed for the purpose of 2232 developing Internet standards in which case the procedures for 2233 copyrights defined in the Internet Standards process must be 2234 followed, or as required to translate it into languages other than 2235 English. 2237 The limited permissions granted above are perpetual and will not be 2238 revoked by the Internet Society or its successors or assigns. 2240 This document and the information contained herein is provided on an 2241 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2242 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2243 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2244 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2245 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.