idnits 2.17.1 draft-ietf-hubmib-etherif-mib-07.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. -- The abstract seems to indicate that this document obsoletes RFC1650, 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 475 has weird spacing: '...issions dot...' == Line 481 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 (June 1998) is 9441 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1' ** Obsolete normative reference: RFC 1902 (ref. '2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '3') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '4') (Obsoleted by RFC 2580) -- Possible downref: Non-RFC (?) normative reference: ref. '5' -- Possible downref: Non-RFC (?) normative reference: ref. '6' -- Possible downref: Non-RFC (?) normative reference: ref. '7' ** Obsolete normative reference: RFC 1284 (ref. '8') (Obsoleted by RFC 1398) ** Obsolete normative reference: RFC 1398 (ref. '9') (Obsoleted by RFC 1623) ** Obsolete normative reference: RFC 1643 (ref. '10') (Obsoleted by RFC 3638) ** Obsolete normative reference: RFC 1650 (ref. '11') (Obsoleted by RFC 2358) ** Obsolete normative reference: RFC 2233 (ref. '12') (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 2239 (ref. '14') (Obsoleted by RFC 2668) ** Downref: Normative reference to an Informational RFC: RFC 1369 (ref. '15') ** Obsolete normative reference: RFC 2274 (ref. '17') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (ref. '18') (Obsoleted by RFC 2575) Summary: 20 errors (**), 0 flaws (~~), 4 warnings (==), 7 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 June 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 1650 ''Definitions of Managed Objects for the 40 Ethernet-like Interface Types using SMIv2.'' This memo extends that 41 specification by including management information useful for the 42 management of 100 Mb/s 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 Network Management Framework ...................... 3 62 2.1. Object Definitions ....................................... 3 63 3. Overview ................................................... 3 64 3.1. Relation to MIB-2 ........................................ 4 65 3.2. Relation to the Interfaces MIB ........................... 4 66 3.2.1. Layering Model ......................................... 4 67 3.2.2. Virtual Circuits ....................................... 5 68 3.2.3. ifTestTable ............................................ 5 69 3.2.4. ifRcvAddressTable ...................................... 5 70 3.2.5. ifPhysAddress .......................................... 5 71 3.2.6. ifType ................................................. 6 72 3.2.7. Specific Interface MIB Objects ......................... 7 73 3.3. Relation to the 802.3 MAU MIB ............................ 10 74 3.4. Mapping of IEEE 802.3 Managed Objects .................... 10 75 4. Definitions ................................................ 12 76 5. Intellectual Property ...................................... 34 77 6. Acknowledgements ........................................... 35 78 7. References ................................................. 35 79 8. Security Considerations .................................... 37 80 9. Author's Addresses ......................................... 38 81 A. Change Log ................................................. 38 82 B. Full Copyright Statement ................................... 39 84 1. Introduction 86 This memo defines a portion of the Management Information Base (MIB) 87 for use with network management protocols in the Internet community. 88 In particular, it defines objects for managing ethernet-like 89 interfaces. 91 This memo also includes a MIB module. This MIB module extends the 92 list of managed objects specified in the earlier version of this MIB: 93 RFC1650 [11]. 95 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 96 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 97 document are to be interpreted as described in [13]. 99 2. The SNMP Network Management Framework 101 The SNMP Network Management Framework consists of several components. 102 For the purpose of this specification, the applicable components of 103 the Framework are the SMI and related documents [2, 3, 4], which 104 define the mechanisms used for describing and naming objects for the 105 purpose of management. 107 The Framework permits new objects to be defined for the purpose of 108 experimentation and evaluation. 110 2.1. Object Definitions 112 Managed objects are accessed via a virtual information store, termed 113 the Management Information Base or MIB. Objects in the MIB are 114 defined using the subset of Abstract Syntax Notation One (ASN.1) [1] 115 defined in the SMI [2]. In particular, each object object type is 116 named by an OBJECT IDENTIFIER, an administratively assigned name. 117 The object type together with an object instance serves to uniquely 118 identify a specific instantiation of the object. For human 119 convenience, we often use a textual string, termed the descriptor, to 120 refer to the object type. 122 3. Overview 124 Instances of these object types represent attributes of an interface 125 to an ethernet-like communications medium. At present, ethernet-like 126 media are identified by the following values of the ifType object in 127 the Interfaces MIB [12]: 129 ethernetCsmacd(6) 130 iso88023Csmacd(7) 131 starLan(11) 133 The definitions presented here are based on the IEEE 802.3 Layer 134 Management Specification [5], as originally interpreted by Frank 135 Kastenholz then of Interlan in [7]. Implementors of these MIB 136 objects should note that the IEEE document explicitly describes (in 137 the form of Pascal pseudocode) when, where, and how various MAC 138 attributes are measured. The IEEE document also describes the 139 effects of MAC actions that may be invoked by manipulating instances 140 of the MIB objects defined here. 142 To the extent that some of the attributes defined in [5] are 143 represented by previously defined objects in MIB-2 [16] or in the 144 Interfaces MIB [12], such attributes are not redundantly represented 145 by objects defined in this memo. Among the attributes represented by 146 objects defined in other memos are the number of octets transmitted 147 or received on a particular interface, the number of frames 148 transmitted or received on a particular interface, the promiscuous 149 status of an interface, the MAC address of an interface, and 150 multicast information associated with an interface. 152 3.1. Relation to MIB-2 154 This section applies only when this MIB is used in conjunction with 155 the "old" (RFC 1213) [16] interface group. 157 The relationship between an ethernet-like interface and an interface 158 in the context of the Internet-standard MIB is one-to-one. As such, 159 the value of an ifIndex object instance can be directly used to 160 identify corresponding instances of the objects defined herein. 162 For agents which implement the (now deprecated) ifSpecific object, an 163 instance of that object that is associated with an ethernet-like 164 interface has the OBJECT IDENTIFIER value: 166 dot3 OBJECT IDENTIFER ::= { transmission 7 } 168 3.2. Relation to the Interfaces MIB 170 The Interface MIB [12] requires that any MIB which is an adjunct of 171 the Interface MIB clarify specific areas within the Interface MIB. 172 These areas were intentionally left vague in the Interface MIB to 173 avoid over constraining the MIB, thereby precluding management of 174 certain media-types. 176 Section 3.3 of [12] enumerates several areas which a media-specific 177 MIB must clarify. Each of these areas is addressed in a following 178 subsection. The implementor is referred to [12] in order to 179 understand the general intent of these areas. 181 3.2.1. Layering Model 183 This MIB does not provide for layering. There are no sublayers. 185 EDITOR'S NOTE: 187 One could foresee the development of an 802.2 and enet-transceiver 188 MIB. They could be higher and lower sublayers, respectively. All 189 that THIS document should do is allude to the possibilities and urge 190 the implementor to be aware of the possibility and that they may have 191 requirements which supersede the requirements in this document. 193 3.2.2. Virtual Circuits 195 This medium does not support virtual circuits and this area is not 196 applicable to this MIB. 198 3.2.3. ifTestTable 200 This MIB defines two tests for media which are instrumented with this 201 MIB; TDR and Loopback. Implementation of these tests is not 202 required. Many common interface chips do not support one or both of 203 these tests. 205 These two tests are provided as a convenience, allowing a common 206 method to invoke the test. 208 Standard MIBs do not include objects in which to return the results 209 of the TDR test. Any needed objects MUST be provided in the vendor 210 specific MIB. 212 Note that the ifTestTable is now deprecated. Work is underway to 213 define a replacement MIB for system and interface testing. It is 214 expected that the tests defined in this document will be usable in 215 this replacement MIB. 217 3.2.4. ifRcvAddressTable 219 This table contains all IEEE 802.3 addresses, unicast, multicast, and 220 broadcast, for which this interface will receive packets and forward 221 them up to a higher layer entity for local consumption. The format 222 of the address, contained in ifRcvAddressAddress, is the same as for 223 ifPhysAddress. 225 In the event that the interface is part of a MAC bridge, this table 226 does not include unicast addresses which are accepted for possible 227 forwarding out some other port. This table is explicitly not 228 intended to provide a bridge address filtering mechanism. 230 3.2.5. ifPhysAddress 231 This object contains the IEEE 802.3 address which is placed in the 232 source-address field of any Ethernet, Starlan, or IEEE 802.3 frames 233 that originate at this interface. Usually this will be kept in ROM 234 on the interface hardware. Some systems may set this address via 235 software. 237 In a system where there are several such addresses the designer has a 238 tougher choice. The address chosen should be the one most likely to 239 be of use to network management (e.g. the address placed in ARP 240 responses for systems which are primarily IP systems). 242 If the designer truly can not chose, use of the factory- provided ROM 243 address is suggested. 245 If the address can not be determined, an octet string of zero length 246 should be returned. 248 The address is stored in binary in this object. The address is 249 stored in "canonical" bit order, that is, the Group Bit is positioned 250 as the low-order bit of the first octet. Thus, the first byte of a 251 multicast address would have the bit 0x01 set. 253 3.2.6. ifType 255 This MIB applies to interfaces which have any of the following ifType 256 values: 258 ethernetCsmacd(6) 259 iso88023Csmacd(7) 260 starLan(11) 262 It is RECOMMENDED that all Ethernet-like interfaces use an ifType of 263 ethernetCsmacd(6) regardless of the speed that the interface is 264 running or the link-layer encapsulation in use. iso88023Csmacd(7) 265 and starLan(11) are supported for backwards compatability. 267 There are two other interface types defined in the IANAifType-MIB for 268 100 Mbit Ethernet. They are fastEther(62), and fastEtherFX(69). 269 This document takes the position that an Ethernet is an Ethernet, and 270 Ethernet interfaces SHOULD always have the same value of ifType. 271 Information on the particular flavor of Ethernet that an interface is 272 running is available from ifSpeed in the Interfaces MIB, and 273 ifMauType in the 802.3 MAU MIB. An Ethernet-like interface SHOULD 274 NOT use the fastEther(62) or fastEtherFX(69) ifTypes. 276 Interfaces with any of the supported ifType values map to the 277 EtherLike-MIB in the same manner. Which compliance statement an 278 interface should implement is dependent on the maximum speed 279 supported on the interface. The EtherLike-MIB etherCompliance 280 compliance statement applies to all Ethernet-like interfaces whose 281 maximum supported speed is 10 Mbit/sec or less. There are no 282 implementation differences. Similarly, the EtherLike-MIB 283 ether100MbsCompliance compliance statement applies to all Ethernet- 284 like interfaces whose maximum supported speed is 100Mbit/sec. 286 An interface that is capable of operating at 100Mbit/sec MUST 287 implement the ether100MbsCompliance compliance statement, even if it 288 is currently operating at a lower speed. Counters in the 289 ether100MbsCompliance compliance statement that only apply to 100 290 Mbit interfaces would simply not increment when the interface is 291 operating at a lower speed. 293 3.2.7. Specific Interface MIB Objects 295 The following table provides specific implementation guidelines for 296 applying the interface group objects to ethernet-like media. 298 Object 300 ifIndex Each ethernet-like interface is 301 represented by an ifEntry. The 302 dot3StatsTable in this MIB module is 303 indexed by dot3StatsIndex. The interface 304 identified by a particular value of 305 dot3StatsIndex is the same interface as 306 identified by the same value of ifIndex. 308 ifDescr Refer to [12]. 310 ifType Refer to section 3.2.6. 312 ifMtu 1500 octets. 314 ifSpeed The current operational speed of the 315 interface in bits per second. For 316 current ethernet-like interfaces, this 317 will be equal to 1,000,000 (1 million), 318 10,000,000 (10 million), or 100,000,000 319 (100 million). If the interface 320 implements auto-negotiation, 321 auto-negotiation is enabled for this 322 interface, and the interface has not yet 323 negotiated to an operational speed, this 324 object SHOULD reflect the maximum speed 325 supported by the interface. Note that 326 this object MUST NOT indicate a doubled 327 value when operating in full-duplex 328 mode. It MUST indicate the correct 329 line speed regardless of the current 330 duplex mode. The correct object to use 331 to determine the duplex mode of the 332 interface is the ifMauType object in the 333 802.3 MAU MIB. 335 ifPhysAddress Refer to section 3.2.5. 337 ifAdminStatus Write access is not required. Support 338 for 'testing' is not required. 340 ifOperStatus The operational state of the interface. 341 Support for 'testing' is not required. 342 The value 'dormant' has no meaning for 343 an ethernet-like interface. 345 ifLastChange Refer to [12]. 347 ifInOctets The number of octets in valid MAC frames 348 received on this interface, including 349 the MAC header and FCS. 351 ifInUcastPkts Refer to [12]. 353 ifInDiscards Refer to [12]. 355 ifInErrors The sum for this interface of 356 dot3StatsAlignmentErrors, 357 dot3StatsFCSErrors, 358 dot3StatsFrameTooLongs, 359 dot3StatsInternalMacReceiveErrors and 360 dot3StatsSymbolErrors. 362 ifInUnknownProtos Refer to [12]. 364 ifOutOctets The number of octets transmitted in 365 valid MAC frames on this interface, 366 including the MAC header and FCS. 368 ifOutUcastPkts Refer to [12]. 370 ifOutDiscards Refer to [12]. 372 ifOutErrors The sum for this interface of: 374 dot3StatsSQETestErrors, 375 dot3StatsLateCollisions, 376 dot3StatsExcessiveCollisions, 377 dot3StatsInternalMacTransmitErrors and 378 dot3StatsCarrierSenseErrors. 380 ifName Locally-significant textual name for the 381 interface (e.g. lan0). 383 ifInMulticastPkts Refer to [12]. 385 ifInBroadcastPkts Refer to [12]. 387 ifOutMulticastPkts Refer to [12]. 389 ifOutBroadcastPkts Refer to [12]. 391 ifHCInOctets 64-bit versions of counters. Required 392 ifHCOutOctets for ethernet-like interfaces that are 393 capable of operating at 20Mbit/sec or 394 faster, even if the interface is 395 currently operating at less than 396 20Mbit/sec. 398 ifHCInUcastPkts 64-bit versions of packet counters. 399 ifHCInMulticastPkts Support for these counters is not 400 ifHCInBroadcastPkts required for the interface types 401 ifHCOutUcastPkts supported by this MIB. They are only 402 ifHCOutMulticastPkts required for interfaces capable of 403 ifHCOutBroadcastPkts operating at 640Mbit/sec or faster. 404 Note that a future revision of this 405 document may support faster interfaces, 406 and therefore may require support for 407 these counters. 409 ifLinkUpDownTrapEnable Refer to [12]. Default is 'enabled' 411 ifHighSpeed The current operational speed of the 412 interface in millions of bits per 413 second. For current ethernet-like 414 interfaces, this will be equal to 1, 10, 415 or 100. If the interface implements 416 auto-negotiation, auto-negotiation is 417 enabled for this interface, and the 418 interface has not yet negotiated to an 419 operational speed, this object SHOULD 420 reflect the maximum speed supported by 421 the interface. Note that this object 422 MUST NOT indicate a doubled value when 423 operating in full-duplex mode. It MUST 424 indicate the correct line speed 425 regardless of the current duplex mode. 426 The correct object to use to determine 427 the duplex mode of the interface is the 428 ifMauType object in the 802.3 MAU MIB. 430 ifPromiscuousMode Refer to [12]. 432 ifConnectorPresent This will normally be 'true'. 434 ifAlias Refer to [12]. 436 ifCounterDiscontinuityTime Refer to [12]. 438 ifStackHigherLayer Refer to section 3.2.1. 439 ifStackLowerLayer 440 ifStackStatus 442 ifRcvAddressAddress Refer to section 3.2.4. 443 ifRcvAddressStatus 444 ifRcvAddressType 446 3.3. Relation to the 802.3 MAU MIB 448 Support for the mauModIfCompl compliance statement of the MAU-MIB 449 [14] is REQUIRED for Ethernet-like interfaces. This MIB is needed in 450 order to allow applications to determine the current MAU type in use 451 by the interface. The MAU type indicates not only the media type in 452 use, but also indicates whether the interface is operating in half- 453 duplex or full-duplex mode. Implementing this MIB module without 454 implementing the MAU-MIB would leave applications with no standard 455 way to determine the duplex mode of the interface. 457 3.4. Mapping of IEEE 802.3 Managed Objects 459 IEEE 802.3 Managed Object Corresponding SNMP Object 461 oMacEntity 462 .aMACID dot3StatsIndex or 463 IF-MIB - ifIndex 464 .aFramesTransmittedOK IF-MIB - ifOutUCastPkts + 465 ifOutMulticastPkts + 466 ifOutBroadcastPkts 467 .aSingleCollisionFrames dot3StatsSingleCollisionFrames 468 .aMultipleCollisionFrames dot3StatsMultipleCollisionFrames 469 .aFramesReceivedOK IF-MIB - ifInUcastPkts + 470 ifInMulticastPkts + 471 ifInBroadcastPkts 472 .aFrameCheckSequenceErrors dot3StatsFCSErrors 473 .aAlignmentErrors dot3StatsAlignmentErrors 474 .aOctetsTransmittedOK IF-MIB - ifOutOctets 475 .aFramesWithDeferredXmissions dot3StatsDeferredTransmissions 476 .aLateCollisions dot3StatsLateCollisions 477 .aFramesAbortedDueToXSColls dot3StatsExcessiveCollisions 478 .aFramesLostDueToIntMACXmitError dot3StatsInternalMacTransmitErrors 479 .aCarrierSenseErrors dot3StatsCarrierSenseErrors 480 .aOctetsReceivedOK IF-MIB - ifInOctets 481 .aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors 482 .aPromiscuousStatus IF-MIB - ifPromiscuousMode 483 .aReadMulticastAddressList IF-MIB - ifRcvAddressTable 484 .aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts 485 .aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts 486 .aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts 487 .aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts 488 .aFrameTooLongErrors dot3StatsFrameTooLongs 489 .aReadWriteMACAddress IF-MIB - ifPhysAddress 490 .aCollisionFrames dot3CollFrequencies 491 .acAddGroupAddress IF-MIB - ifRcvAddressTable 492 .acDeleteGroupAddress IF-MIB - ifRcvAddressTable 493 .acExecuteSelfTest dot3TestLoopBack 495 oPHYEntity 496 .aSQETestErrors dot3StatsSQETestErrors 497 .aSymbolErrorDuringCarrier dot3StatsSymbolErrors 499 The following IEEE 802.3 managed objects have been removed from this 500 MIB module as a result of implementation feedback: 502 oMacEntity 503 .aFramesWithExcessiveDeferral 504 .aInRangeLengthErrors 505 .aOutOfRangeLengthField 506 .aMACEnableStatus 507 .aTransmitEnableStatus 508 .aMulticastReceiveStatus 509 .acInitializeMAC 511 Please see [15] for the detailed reasoning on why these objects were 512 removed. 514 4. Definitions 516 EtherLike-MIB DEFINITIONS ::= BEGIN 518 IMPORTS 519 MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, 520 Counter32, mib-2, transmission 521 FROM SNMPv2-SMI 522 MODULE-COMPLIANCE, OBJECT-GROUP 523 FROM SNMPv2-CONF 524 ifIndex, InterfaceIndex 525 FROM IF-MIB; 527 etherMIB MODULE-IDENTITY 528 LAST-UPDATED "9806032150Z" -- June 3, 1998 529 ORGANIZATION "IETF 802.3 Hub MIB Working Group" 530 CONTACT-INFO 531 "WG E-mail: hubmib@hprnd.rose.hp.com 532 To subscribe: hubmib-request@hprnd.rose.hp.com 534 Chair: Dan Romascanu 535 Postal: LANNET Ltd. 536 Atidum Technology Park, Bldg. 3 537 Tel Aviv 61131 538 Israel 539 Tel: +972 3 645 8414 540 E-mail: dromasca@lannet.com 542 Editor: John Flick 543 Postal: Hewlett-Packard Company 544 8000 Foothills Blvd. M/S 5556 545 Roseville, CA 95747-5556 546 USA 547 Tel: +1 916 785 4018 548 Fax: +1 916 785 3583 549 E-mail: johnf@hprnd.rose.hp.com 551 Editor: Jeffrey Johnson 552 Postal: RedBack Networks 553 2570 North First Street, Suite 410 554 San Jose, CA, 95131 555 USA 556 Tel: +1 408 571 2699 557 Fax: +1 408 571 2698 558 E-Mail: jeff@redbacknetworks.com" 560 DESCRIPTION "The MIB module to describe generic objects for 561 Ethernet-like network interfaces. This MIB is an 562 updated version of the Ethernet-like MIB in RFC 563 1650." 565 REVISION "9806032150Z" 566 DESCRIPTION "Updated to include support for 100 Mb/sec 567 interfaces." 569 REVISION "9402030400Z" 570 DESCRIPTION "Version published as RFC 1650." 571 ::= { mib-2 35 } 573 etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 } 575 dot3 OBJECT IDENTIFIER ::= { transmission 7 } 577 -- the Ethernet-like Statistics group 579 dot3StatsTable OBJECT-TYPE 580 SYNTAX SEQUENCE OF Dot3StatsEntry 581 MAX-ACCESS not-accessible 582 STATUS current 583 DESCRIPTION "Statistics for a collection of ethernet-like 584 interfaces attached to a particular system." 585 ::= { dot3 2 } 587 dot3StatsEntry OBJECT-TYPE 588 SYNTAX Dot3StatsEntry 589 MAX-ACCESS not-accessible 590 STATUS current 591 DESCRIPTION "Statistics for a particular interface to an 592 ethernet-like medium." 593 INDEX { dot3StatsIndex } 594 ::= { dot3StatsTable 1 } 596 Dot3StatsEntry ::= 597 SEQUENCE { 598 dot3StatsIndex InterfaceIndex, 599 dot3StatsAlignmentErrors Counter32, 600 dot3StatsFCSErrors Counter32, 601 dot3StatsSingleCollisionFrames Counter32, 602 dot3StatsMultipleCollisionFrames Counter32, 603 dot3StatsSQETestErrors Counter32, 604 dot3StatsDeferredTransmissions Counter32, 605 dot3StatsLateCollisions Counter32, 606 dot3StatsExcessiveCollisions Counter32, 607 dot3StatsInternalMacTransmitErrors Counter32, 608 dot3StatsCarrierSenseErrors Counter32, 609 dot3StatsFrameTooLongs Counter32, 610 dot3StatsInternalMacReceiveErrors Counter32, 611 dot3StatsEtherChipSet OBJECT IDENTIFIER, 612 dot3StatsSymbolErrors Counter32 613 } 615 dot3StatsIndex OBJECT-TYPE 616 SYNTAX InterfaceIndex 617 MAX-ACCESS read-only 618 STATUS current 619 DESCRIPTION "An index value that uniquely identifies an 620 interface to an ethernet-like medium. The 621 interface identified by a particular value of 622 this index is the same interface as identified 623 by the same value of ifIndex." 624 ::= { dot3StatsEntry 1 } 626 dot3StatsAlignmentErrors OBJECT-TYPE 627 SYNTAX Counter32 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION "A count of frames received on a particular 631 interface that are not an integral number of 632 octets in length and do not pass the FCS check. 634 The count represented by an instance of this 635 object is incremented when the alignmentError 636 status is returned by the MAC service to the 637 LLC (or other MAC user). Received frames for 638 which multiple error conditions obtain are, 639 according to the conventions of IEEE 802.3 640 Layer Management, counted exclusively according 641 to the error status presented to the LLC." 642 REFERENCE "IEEE 802.3 Layer Management" 643 ::= { dot3StatsEntry 2 } 645 dot3StatsFCSErrors OBJECT-TYPE 646 SYNTAX Counter32 647 MAX-ACCESS read-only 648 STATUS current 649 DESCRIPTION "A count of frames received on a particular 650 interface that are an integral number of octets 651 in length but do not pass the FCS check. 653 The count represented by an instance of this 654 object is incremented when the frameCheckError 655 status is returned by the MAC service to the 656 LLC (or other MAC user). Received frames for 657 which multiple error conditions obtain are, 658 according to the conventions of IEEE 802.3 659 Layer Management, counted exclusively according 660 to the error status presented to the LLC." 661 REFERENCE "IEEE 802.3 Layer Management" 662 ::= { dot3StatsEntry 3 } 664 dot3StatsSingleCollisionFrames OBJECT-TYPE 665 SYNTAX Counter32 666 MAX-ACCESS read-only 667 STATUS current 668 DESCRIPTION "A count of successfully transmitted frames on 669 a particular interface for which transmission 670 is inhibited by exactly one collision. 672 A frame that is counted by an instance of this 673 object is also counted by the corresponding 674 instance of either the ifOutUcastPkts, 675 ifOutMulticastPkts, or ifOutBroadcastPkts, 676 and is not counted by the corresponding 677 instance of the dot3StatsMultipleCollisionFrames 678 object." 679 REFERENCE "IEEE 802.3 Layer Management" 680 ::= { dot3StatsEntry 4 } 682 dot3StatsMultipleCollisionFrames OBJECT-TYPE 683 SYNTAX Counter32 684 MAX-ACCESS read-only 685 STATUS current 686 DESCRIPTION "A count of successfully transmitted frames on 687 a particular interface for which transmission 688 is inhibited by more than one collision. 690 A frame that is counted by an instance of this 691 object is also counted by the corresponding 692 instance of either the ifOutUcastPkts, 693 ifOutMulticastPkts, or ifOutBroadcastPkts, 694 and is not counted by the corresponding 695 instance of the dot3StatsSingleCollisionFrames 696 object." 697 REFERENCE "IEEE 802.3 Layer Management" 698 ::= { dot3StatsEntry 5 } 700 dot3StatsSQETestErrors OBJECT-TYPE 701 SYNTAX Counter32 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION "A count of times that the SQE TEST ERROR 705 message is generated by the PLS sublayer for a 706 particular interface. The SQE TEST ERROR 707 message is defined in section 7.2.2.2.4 of 708 ANSI/IEEE 802.3-1985 and its generation is 709 described in section 7.2.4.6 of the same 710 document." 711 REFERENCE "ANSI/IEEE Std 802.3-1985 Carrier Sense 712 Multiple Access with Collision Detection Access 713 Method and Physical Layer Specifications" 714 ::= { dot3StatsEntry 6 } 716 dot3StatsDeferredTransmissions OBJECT-TYPE 717 SYNTAX Counter32 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION "A count of frames for which the first 721 transmission attempt on a particular interface 722 is delayed because the medium is busy. 724 The count represented by an instance of this 725 object does not include frames involved in 726 collisions." 727 REFERENCE "IEEE 802.3 Layer Management" 728 ::= { dot3StatsEntry 7 } 730 dot3StatsLateCollisions OBJECT-TYPE 731 SYNTAX Counter32 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION "The number of times that a collision is 735 detected on a particular interface later than 736 512 bit-times into the transmission of a 737 packet. 739 Five hundred and twelve bit-times corresponds 740 to 51.2 microseconds on a 10 Mbit/s system. A 741 (late) collision included in a count 742 represented by an instance of this object is 743 also considered as a (generic) collision for 744 purposes of other collision-related 745 statistics." 746 REFERENCE "IEEE 802.3 Layer Management" 747 ::= { dot3StatsEntry 8 } 749 dot3StatsExcessiveCollisions OBJECT-TYPE 750 SYNTAX Counter32 751 MAX-ACCESS read-only 752 STATUS current 753 DESCRIPTION "A count of frames for which transmission on a 754 particular interface fails due to excessive 755 collisions." 756 REFERENCE "IEEE 802.3 Layer Management" 757 ::= { dot3StatsEntry 9 } 759 dot3StatsInternalMacTransmitErrors OBJECT-TYPE 760 SYNTAX Counter32 761 MAX-ACCESS read-only 762 STATUS current 763 DESCRIPTION "A count of frames for which transmission on a 764 particular interface fails due to an internal 765 MAC sublayer transmit error. A frame is only 766 counted by an instance of this object if it is 767 not counted by the corresponding instance of 768 either the dot3StatsLateCollisions object, the 769 dot3StatsExcessiveCollisions object, or the 770 dot3StatsCarrierSenseErrors object. 772 The precise meaning of the count represented by 773 an instance of this object is implementation- 774 specific. In particular, an instance of this 775 object may represent a count of transmission 776 errors on a particular interface that are not 777 otherwise counted." 778 REFERENCE "IEEE 802.3 Layer Management" 779 ::= { dot3StatsEntry 10 } 781 dot3StatsCarrierSenseErrors OBJECT-TYPE 782 SYNTAX Counter32 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION "The number of times that the carrier sense 786 condition was lost or never asserted when 787 attempting to transmit a frame on a particular 788 interface. 790 The count represented by an instance of this 791 object is incremented at most once per 792 transmission attempt, even if the carrier sense 793 condition fluctuates during a transmission 794 attempt." 795 REFERENCE "IEEE 802.3 Layer Management" 796 ::= { dot3StatsEntry 11 } 798 -- { dot3StatsEntry 12 } is not assigned 799 dot3StatsFrameTooLongs OBJECT-TYPE 800 SYNTAX Counter32 801 MAX-ACCESS read-only 802 STATUS current 803 DESCRIPTION "A count of frames received on a particular 804 interface that exceed the maximum permitted 805 frame size. 807 The count represented by an instance of this 808 object is incremented when the frameTooLong 809 status is returned by the MAC service to the 810 LLC (or other MAC user). Received frames for 811 which multiple error conditions obtain are, 812 according to the conventions of IEEE 802.3 813 Layer Management, counted exclusively according 814 to the error status presented to the LLC." 815 REFERENCE "IEEE 802.3 Layer Management" 816 ::= { dot3StatsEntry 13 } 818 -- { dot3StatsEntry 14 } is not assigned 820 -- { dot3StatsEntry 15 } is not assigned 822 dot3StatsInternalMacReceiveErrors OBJECT-TYPE 823 SYNTAX Counter32 824 MAX-ACCESS read-only 825 STATUS current 826 DESCRIPTION "A count of frames for which reception on a 827 particular interface fails due to an internal 828 MAC sublayer receive error. A frame is only 829 counted by an instance of this object if it is 830 not counted by the corresponding instance of 831 either the dot3StatsFrameTooLongs object, the 832 dot3StatsAlignmentErrors object, or the 833 dot3StatsFCSErrors object. 834 The precise meaning of the count represented by 835 an instance of this object is implementation- 836 specific. In particular, an instance of this 837 object may represent a count of receive errors 838 on a particular interface that are not 839 otherwise counted." 840 REFERENCE "IEEE 802.3 Layer Management" 841 ::= { dot3StatsEntry 16 } 843 dot3StatsEtherChipSet OBJECT-TYPE 844 SYNTAX OBJECT IDENTIFIER 845 MAX-ACCESS read-only 846 STATUS current 847 DESCRIPTION "This object contains an OBJECT IDENTIFIER 848 which identifies the chipset used to 849 realize the interface. Ethernet-like 850 interfaces are typically built out of 851 several different chips. The MIB implementor 852 is presented with a decision of which chip 853 to identify via this object. The implementor 854 should identify the chip which is usually 855 called the Medium Access Control chip. 856 If no such chip is easily identifiable, 857 the implementor should identify the chip 858 which actually gathers the transmit 859 and receive statistics and error 860 indications. This would allow a 861 manager station to correlate the 862 statistics and the chip generating 863 them, giving it the ability to take 864 into account any known anomalies 865 in the chip." 866 ::= { dot3StatsEntry 17 } 868 dot3StatsSymbolErrors OBJECT-TYPE 869 SYNTAX Counter32 870 MAX-ACCESS read-only 871 STATUS current 872 DESCRIPTION "The number of times there was an invalid data 873 symbol when a valid carrier was present on a 874 particular interface. 876 The count represented by an instance of this 877 object is incremented at most once per carrier 878 event, even if multiple symbol errors occur 879 during the carrier event." 880 REFERENCE "IEEE 802.3u-1995 10 & 100 Mb/s Management" 881 ::= { dot3StatsEntry 18 } 883 -- the Ethernet-like Collision Statistics group 885 -- Implementation of this group is optional; it is appropriate 886 -- for all systems which have the necessary metering 888 dot3CollTable OBJECT-TYPE 889 SYNTAX SEQUENCE OF Dot3CollEntry 890 MAX-ACCESS not-accessible 891 STATUS current 892 DESCRIPTION "A collection of collision histograms for a 893 particular set of interfaces." 894 ::= { dot3 5 } 896 dot3CollEntry OBJECT-TYPE 897 SYNTAX Dot3CollEntry 898 MAX-ACCESS not-accessible 899 STATUS current 900 DESCRIPTION "A cell in the histogram of per-frame 901 collisions for a particular interface. An 902 instance of this object represents the 903 frequency of individual MAC frames for which 904 the transmission (successful or otherwise) on a 905 particular interface is accompanied by a 906 particular number of media collisions." 907 INDEX { ifIndex, dot3CollCount } 908 ::= { dot3CollTable 1 } 910 Dot3CollEntry ::= 911 SEQUENCE { 912 dot3CollCount INTEGER, 913 dot3CollFrequencies Counter32 914 } 916 -- { dot3CollEntry 1 } is no longer in use 918 dot3CollCount OBJECT-TYPE 919 SYNTAX INTEGER (1..16) 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION "The number of per-frame media collisions for 923 which a particular collision histogram cell 924 represents the frequency on a particular 925 interface." 926 ::= { dot3CollEntry 2 } 928 dot3CollFrequencies OBJECT-TYPE 929 SYNTAX Counter32 930 MAX-ACCESS read-only 931 STATUS current 932 DESCRIPTION "A count of individual MAC frames for which the 933 transmission (successful or otherwise) on a 934 particular interface occurs after the 935 frame has experienced exactly the number 936 of collisions in the associated 937 dot3CollCount object. 939 For example, a frame which is transmitted 940 on interface 77 after experiencing 941 exactly 4 collisions would be indicated 942 by incrementing only dot3CollFrequencies.77.4. 944 No other instance of dot3CollFrequencies would 945 be incremented in this example." 946 ::= { dot3CollEntry 3 } 948 -- 802.3 Tests 950 dot3Tests OBJECT IDENTIFIER ::= { dot3 6 } 952 dot3Errors OBJECT IDENTIFIER ::= { dot3 7 } 954 -- TDR Test 956 dot3TestTdr OBJECT-IDENTITY 957 STATUS current 958 DESCRIPTION "The Time-Domain Reflectometry (TDR) test is 959 specific to ethernet-like interfaces of type 960 10Base5 and 10Base2. The TDR value may be 961 useful in determining the approximate distance 962 to a cable fault. It is advisable to repeat 963 this test to check for a consistent resulting 964 TDR value, to verify that there is a fault. 966 A TDR test returns as its result the time 967 interval, measured in 10 MHz ticks or 100 nsec 968 units, between the start of TDR test 969 transmission and the subsequent detection of a 970 collision or deassertion of carrier. On 971 successful completion of a TDR test, the result 972 is stored as the value of an appropriate 973 instance of an appropriate vendor specific MIB 974 object, and the OBJECT IDENTIFIER of that 975 instance is stored in the appropriate instance 976 of the appropriate test result code object 977 (thereby indicating where the result has been 978 stored)." 979 ::= { dot3Tests 1 } 981 -- Loopback Test 983 dot3TestLoopBack OBJECT-IDENTITY 984 STATUS current 985 DESCRIPTION "This test configures the MAC chip and executes 986 an internal loopback test of memory, data paths, 987 and the MAC chip logic. This loopback test can 988 only be executed if the interface is offline. 989 Once the test has completed, the MAC chip should 990 be reinitialized for network operation, but it 991 should remain offline. 993 If an error occurs during a test, the 994 appropriate test result object will be set 995 to indicate a failure. The two OBJECT 996 IDENTIFIER values dot3ErrorInitError and 997 dot3ErrorLoopbackError may be used to provided 998 more information as values for an appropriate 999 test result code object." 1000 ::= { dot3Tests 2 } 1002 dot3ErrorInitError OBJECT-IDENTITY 1003 STATUS current 1004 DESCRIPTION "Couldn't initialize MAC chip for test." 1005 ::= { dot3Errors 1 } 1007 dot3ErrorLoopbackError OBJECT-IDENTITY 1008 STATUS current 1009 DESCRIPTION "Expected data not received (or not received 1010 correctly) in loopback test." 1011 ::= { dot3Errors 2 } 1013 -- 802.3 Hardware Chipsets 1015 -- The object dot3StatsEtherChipSet is provided to 1016 -- identify the MAC hardware used to communicate on an 1017 -- interface. The following hardware chipsets are 1018 -- registered: 1020 dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 } 1022 dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 } 1024 dot3ChipSetAMD7990 OBJECT-IDENTITY 1025 STATUS current 1026 DESCRIPTION "The authoritative identifier for the Advanced 1027 Micro Devices Am7990 Local Area Network 1028 Controller for Ethernet (LANCE)." 1029 ::= { dot3ChipSetAMD 1 } 1031 dot3ChipSetAMD79900 OBJECT-IDENTITY 1032 STATUS current 1033 DESCRIPTION "The authoritative identifier for the Advanced 1034 Micro Devices Am79900 chip." 1035 ::= { dot3ChipSetAMD 2 } 1037 dot3ChipSetAMD79C940 OBJECT-IDENTITY 1038 STATUS current 1039 DESCRIPTION "The authoritative identifier for the Advanced 1040 Micro Devices Am79C940 Media Access Controller 1041 for Ethernet (MACE)." 1042 ::= { dot3ChipSetAMD 3 } 1044 dot3ChipSetAMD79C90 OBJECT-IDENTITY 1045 STATUS current 1046 DESCRIPTION "The authoritative identifier for the Advanced 1047 Micro Devices Am79C90 CMOS Local Area Network 1048 Controller for Ethernet (C-LANCE)." 1049 ::= { dot3ChipSetAMD 4 } 1051 dot3ChipSetAMD79C960 OBJECT-IDENTITY 1052 STATUS current 1053 DESCRIPTION "The authoritative identifier for the Advanced 1054 Micro Devices Am79C960 PCnet-ISA Single Chip 1055 Ethernet Controller for ISA." 1056 ::= { dot3ChipSetAMD 5 } 1058 dot3ChipSetAMD79C961 OBJECT-IDENTITY 1059 STATUS current 1060 DESCRIPTION "The authoritative identifier for the Advanced 1061 Micro Devices Am79C961 PCnet-ISA+ Single Chip 1062 Plug & Play Full-Duplex Ethernet Controller 1063 for ISA." 1064 ::= { dot3ChipSetAMD 6 } 1066 dot3ChipSetAMD79C961A OBJECT-IDENTITY 1067 STATUS current 1068 DESCRIPTION "The authoritative identifier for the Advanced 1069 Micro Devices Am79C961A PCnet-ISA II Single Chip 1070 Plug & Play Full-Duplex Ethernet Controller 1071 for ISA." 1072 ::= { dot3ChipSetAMD 7 } 1074 dot3ChipSetAMD79C965 OBJECT-IDENTITY 1075 STATUS current 1076 DESCRIPTION "The authoritative identifier for the Advanced 1077 Micro Devices Am79C965 PCnet-32 Single Chip 1078 Ethernet Controller for PCI." 1079 ::= { dot3ChipSetAMD 8 } 1081 dot3ChipSetAMD79C970 OBJECT-IDENTITY 1082 STATUS current 1083 DESCRIPTION "The authoritative identifier for the Advanced 1084 Micro Devices Am79C970 PCnet PCI Single Chip 1085 Ethernet Controller for PCI Local Bus." 1087 ::= { dot3ChipSetAMD 9 } 1089 dot3ChipSetAMD79C970A OBJECT-IDENTITY 1090 STATUS current 1091 DESCRIPTION "The authoritative identifier for the Advanced 1092 Micro Devices AM79C970A PCnet PCI II Single Chip 1093 Full-Duplex Ethernet Controller for PCI Local 1094 Bus." 1095 ::= { dot3ChipSetAMD 10 } 1097 dot3ChipSetAMD79C971 OBJECT-IDENTITY 1098 STATUS current 1099 DESCRIPTION "The authoritative identifier for the Advanced 1100 Micro Devices Am79C971 PCnet-FAST Single Chip 1101 Full-Duplex 10/100 Mbps Ethernet Controller for 1102 PCI Local Bus." 1103 ::= { dot3ChipSetAMD 11 } 1105 dot3ChipSetAMD79C972 OBJECT-IDENTITY 1106 STATUS current 1107 DESCRIPTION "The authoritative identifier for the Advanced 1108 Micro Devices Am79C972 PCnet-FAST+ Enhanced 1109 10/100 Mbps PCI Ethernet Controller with OnNow 1110 Support." 1111 ::= { dot3ChipSetAMD 12 } 1113 dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 } 1115 dot3ChipSetIntel82586 OBJECT-IDENTITY 1116 STATUS current 1117 DESCRIPTION "The authoritative identifier for the Intel 1118 82586 IEEE 802.3 Ethernet LAN Coprocessor." 1119 ::= { dot3ChipSetIntel 1 } 1121 dot3ChipSetIntel82596 OBJECT-IDENTITY 1122 STATUS current 1123 DESCRIPTION "The authoritative identifier for the Intel 1124 82596 High-Performance 32-Bit Local Area Network 1125 Coprocessor." 1126 ::= { dot3ChipSetIntel 2 } 1128 dot3ChipSetIntel82595 OBJECT-IDENTITY 1129 STATUS current 1130 DESCRIPTION "The authoritative identifier for the Intel 1131 82595 High Integration Ethernet Controller." 1132 ::= { dot3ChipSetIntel 3 } 1134 dot3ChipSetIntel82557 OBJECT-IDENTITY 1135 STATUS current 1136 DESCRIPTION "The authoritative identifier for the Intel 1137 82557 Fast Ethernet PCI Bus Lan Controller." 1138 ::= { dot3ChipSetIntel 4 } 1140 dot3ChipSetIntel82558 OBJECT-IDENTITY 1141 STATUS current 1142 DESCRIPTION "The authoritative identifier for the Intel 1143 82558 Fast Ethernet PCI Bus LAN Controller with 1144 Integrated PHY." 1145 ::= { dot3ChipSetIntel 5 } 1147 dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 } 1149 dot3ChipSetSeeq8003 OBJECT-IDENTITY 1150 STATUS current 1151 DESCRIPTION "The authoritative identifier for the SEEQ 1152 8003 chip set." 1153 ::= { dot3ChipSetSeeq 1 } 1155 dot3ChipSetSeeq80C03 OBJECT-IDENTITY 1156 STATUS current 1157 DESCRIPTION "The authoritative identifier for the SEEQ 1158 80C03 Full-Duplex CMOS Ethernet Data Link 1159 Controller (MAC)." 1160 ::= { dot3ChipSetSeeq 2 } 1162 dot3ChipSetSeeq84C30 OBJECT-IDENTITY 1163 STATUS current 1164 DESCRIPTION "The authoritative identifier for the SEEQ 1165 4-Port 84C30 Full-Duplex CMOS Ethernet 10 1166 MBit/Sec Data Link Controller (MAC)." 1167 ::= { dot3ChipSetSeeq 3 } 1169 dot3ChipSetSeeq8431 OBJECT-IDENTITY 1170 STATUS current 1171 DESCRIPTION "The authoritative identifier for the SEEQ 1172 4-Port 8431 Full-Duplex CMOS Ethernet 10 1173 MBit/Sec Data Link Controller (MAC)." 1174 ::= { dot3ChipSetSeeq 4 } 1176 dot3ChipSetSeeq80C300 OBJECT-IDENTITY 1177 STATUS current 1178 DESCRIPTION "The authoritative identifier for the SEEQ 1179 80C300 Full-Duplex CMOS Ethernet 10/100 1180 Mbit/Sec Data Link Controller (MAC)." 1181 ::= { dot3ChipSetSeeq 5 } 1183 dot3ChipSetSeeq84C300 OBJECT-IDENTITY 1184 STATUS current 1185 DESCRIPTION "The authoritative identifier for the SEEQ 1186 4-Port 84C300 Fast Ethernet Controller (MAC)." 1187 ::= { dot3ChipSetSeeq 6 } 1189 dot3ChipSetSeeq84301 OBJECT-IDENTITY 1190 STATUS current 1191 DESCRIPTION "The authoritative identifier for the SEEQ 1192 4-Port 84301 Fast Ethernet Controller (MAC)." 1193 ::= { dot3ChipSetSeeq 7 } 1195 dot3ChipSetSeeq84302 OBJECT-IDENTITY 1196 STATUS current 1197 DESCRIPTION "The authoritative identifier for the SEEQ 1198 4-Port 84302 Fast Ethernet Controller (MAC)." 1199 ::= { dot3ChipSetSeeq 8 } 1201 dot3ChipSetSeeq8100 OBJECT-IDENTITY 1202 STATUS current 1203 DESCRIPTION "The authoritative identifier for the SEEQ 1204 8100 Gigabit Ethernet Controller (MAC & PCS)." 1205 ::= { dot3ChipSetSeeq 9 } 1207 dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 } 1209 dot3ChipSetNational8390 OBJECT-IDENTITY 1210 STATUS current 1211 DESCRIPTION "The authoritative identifier for the National 1212 Semiconductor DP8390 Network Interface 1213 Controller." 1214 ::= { dot3ChipSetNational 1 } 1216 dot3ChipSetNationalSonic OBJECT-IDENTITY 1217 STATUS current 1218 DESCRIPTION "The authoritative identifier for the National 1219 Semiconductor DP83932 Systems-Oriented Network 1220 Interface Controller (SONIC)." 1221 ::= { dot3ChipSetNational 2 } 1223 dot3ChipSetNational83901 OBJECT-IDENTITY 1224 STATUS current 1225 DESCRIPTION "The authoritative identifier for the National 1226 Semiconductor DP83901 Serial Network Interface 1227 Controller (SNIC)." 1228 ::= { dot3ChipSetNational 3 } 1230 dot3ChipSetNational83902 OBJECT-IDENTITY 1231 STATUS current 1232 DESCRIPTION "The authoritative identifier for the National 1233 Semiconductor DP83902 Serial Network Interface 1234 Controller for Twisted Pair (ST-NIC)." 1235 ::= { dot3ChipSetNational 4 } 1237 dot3ChipSetNational83905 OBJECT-IDENTITY 1238 STATUS current 1239 DESCRIPTION "The authoritative identifier for the National 1240 Semiconductor DP83905 AT Local Area Network 1241 Twisted-Pair Interface (AT/LANTIC)." 1242 ::= { dot3ChipSetNational 5 } 1244 dot3ChipSetNational83907 OBJECT-IDENTITY 1245 STATUS current 1246 DESCRIPTION "The authoritative identifier for the National 1247 Semiconductor DP83907 AT Twisted-Pair Enhanced 1248 Coaxial Network Interface Controller 1249 (AT/LANTIC II)." 1250 ::= { dot3ChipSetNational 6 } 1252 dot3ChipSetNational83916 OBJECT-IDENTITY 1253 STATUS current 1254 DESCRIPTION "The authoritative identifier for the National 1255 Semiconductor DP83916 Systems-Oriented Network 1256 Interface Controller (SONIC-16)." 1257 ::= { dot3ChipSetNational 7 } 1259 dot3ChipSetNational83934 OBJECT-IDENTITY 1260 STATUS current 1261 DESCRIPTION "The authoritative identifier for the National 1262 Semiconductor DP83934 Systems-Oriented Network 1263 Interface Controller with Twisted Pair Interface 1264 (SONIC-T)." 1265 ::= { dot3ChipSetNational 8 } 1267 dot3ChipSetNational83936 OBJECT-IDENTITY 1268 STATUS current 1269 DESCRIPTION "The authoritative identifier for the National 1270 Semiconductor DP83936AVUL Full-Duplex Systems- 1271 Oriented Network Interface Controller with 1272 Twisted Pair Interface (SONIC-T)." 1273 ::= { dot3ChipSetNational 9 } 1275 dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 } 1277 dot3ChipSetFujitsu86950 OBJECT-IDENTITY 1278 STATUS current 1279 DESCRIPTION "The authoritative identifier for the Fujitsu 1280 86950 chip." 1281 ::= { dot3ChipSetFujitsu 1 } 1283 dot3ChipSetFujitsu86960 OBJECT-IDENTITY 1284 STATUS current 1285 DESCRIPTION "The authoritative identifier for the Fujitsu 1286 MB86960 Network Interface Controller with 1287 Encoder/Decoder (NICE)." 1288 ::= { dot3ChipSetFujitsu 2 } 1290 dot3ChipSetFujitsu86964 OBJECT-IDENTITY 1291 STATUS current 1292 DESCRIPTION "The authoritative identifier for the Fujitsu 1293 MB86964 Ethernet Controller with 10BASE-T 1294 Tranceiver." 1295 ::= { dot3ChipSetFujitsu 3 } 1297 dot3ChipSetFujitsu86965A OBJECT-IDENTITY 1298 STATUS current 1299 DESCRIPTION "The authoritative identifier for the Fujitsu 1300 MB86965A EtherCoupler Single-Chip Ethernet 1301 Controller." 1302 ::= { dot3ChipSetFujitsu 4 } 1304 dot3ChipSetFujitsu86965B OBJECT-IDENTITY 1305 STATUS current 1306 DESCRIPTION "The authoritative identifier for the Fujitsu 1307 MB86965B EtherCoupler Single-Chip Ethernet 1308 Controller (supports full-duplex)." 1309 ::= { dot3ChipSetFujitsu 5 } 1311 dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 } 1313 dot3ChipSetDigitalDC21040 OBJECT-IDENTITY 1314 STATUS current 1315 DESCRIPTION "The authoritative identifier for the Digital 1316 Semiconductor DC21040 chip." 1317 ::= { dot3ChipSetDigital 1 } 1319 dot3ChipSetDigital21041 OBJECT-IDENTITY 1320 STATUS current 1321 DESCRIPTION "The authoritative identifier for the Digital 1322 Semiconductor 21041 PCI Ethernet LAN 1323 Controller." 1324 ::= { dot3ChipSetDigital 2 } 1326 dot3ChipSetDigital21140 OBJECT-IDENTITY 1327 STATUS current 1328 DESCRIPTION "The authoritative identifier for the Digital 1329 Semiconductor 21140 PCI Fast Ethernet LAN 1330 Controller." 1331 ::= { dot3ChipSetDigital 3 } 1333 dot3ChipSetDigital21143 OBJECT-IDENTITY 1334 STATUS current 1335 DESCRIPTION "The authoritative identifier for the Digital 1336 Semiconductor 21143 PCI/CardBus 10/100-Mb/s 1337 Ethernet LAN Controller." 1338 ::= { dot3ChipSetDigital 4 } 1340 dot3ChipSetDigital21340 OBJECT-IDENTITY 1341 STATUS current 1342 DESCRIPTION "The authoritative identifier for the Digital 1343 Semiconductor 21340 10/100-MB/s managed buffered 1344 port switch." 1345 ::= { dot3ChipSetDigital 5 } 1347 dot3ChipSetDigital21440 OBJECT-IDENTITY 1348 STATUS current 1349 DESCRIPTION "The authoritative identifier for the Digital 1350 Semiconductor 21440 Multiport 10/100Mbps 1351 Ethernet Controller." 1352 ::= { dot3ChipSetDigital 6 } 1354 dot3ChipSetDigital21540 OBJECT-IDENTITY 1355 STATUS current 1356 DESCRIPTION "The authoritative identifier for the Digital 1357 Semiconductor 21540 PCI/CardBus Ethernet LAN 1358 Controller with Modem Interface." 1359 ::= { dot3ChipSetDigital 7 } 1361 dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 } 1363 dot3ChipSetTIE100 OBJECT-IDENTITY 1364 STATUS current 1365 DESCRIPTION "The authoritative identifier for the Texas 1366 Instruments TNETE100 ThunderLAN PCI Fast 1367 Ethernet Controller." 1368 ::= { dot3ChipSetTI 1 } 1370 dot3ChipSetTIE110 OBJECT-IDENTITY 1371 STATUS current 1372 DESCRIPTION "The authoritative identifier for the Texas 1373 Instruments TNETE110 ThunderLAN PCI 10BASE-T 1374 Ethernet Adapter." 1376 ::= { dot3ChipSetTI 2 } 1378 dot3ChipSetTIX3100 OBJECT-IDENTITY 1379 STATUS current 1380 DESCRIPTION "The authoritative identifier for the Texas 1381 Instruments TNETX3100 Desktop ThunderSWITCH 1382 8/2." 1383 ::= { dot3ChipSetTI 3 } 1385 dot3ChipSetTIX3150 OBJECT-IDENTITY 1386 STATUS current 1387 DESCRIPTION "The authoritative identifier for the Texas 1388 Instruments TNETX3150 ThunderSWITCH 12/3." 1389 ::= { dot3ChipSetTI 4 } 1391 dot3ChipSetTIX3270 OBJECT-IDENTITY 1392 STATUS current 1393 DESCRIPTION "The authoritative identifier for the Texas 1394 Instruments TNETX3270 ThunderSWITCH 24/3." 1395 ::= { dot3ChipSetTI 5 } 1397 dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 } 1399 dot3ChipSetToshibaTC35815F OBJECT-IDENTITY 1400 STATUS current 1401 DESCRIPTION "The authoritative identifier for the Toshiba 1402 TC35815F PCI-Based 100/10Mbps Ethernet 1403 Controller." 1404 ::= { dot3ChipSetToshiba 1 } 1406 dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 } 1408 dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY 1409 STATUS current 1410 DESCRIPTION "The authoritative identifier for the Lucent 1411 Technologies ATT1MX10 (Spinnaker) Quad MAC and 1412 Tranceiver for Ethernet Frame Switching." 1413 ::= { dot3ChipSetLucent 1 } 1415 dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY 1416 STATUS current 1417 DESCRIPTION "The authoritative identifier for the Lucent 1418 Technologies LUC3M08 Eight Ethernet MACs for 1419 10/100 Mbits/s Frame Switching." 1420 ::= { dot3ChipSetLucent 2 } 1422 dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 } 1423 dot3ChipSetGalileoGT48001 OBJECT-IDENTITY 1424 STATUS current 1425 DESCRIPTION "The authoritative identifier for the Galileo 1426 Technology GT-48001A Switched Ethernet 1427 Controller." 1428 ::= { dot3ChipSetGalileo 1 } 1430 dot3ChipSetGalileoGT48002 OBJECT-IDENTITY 1431 STATUS current 1432 DESCRIPTION "The authoritative identifier for the Galileo 1433 Technology GT-48002A Switched Fast Ethernet 1434 Controller." 1435 ::= { dot3ChipSetGalileo 2 } 1437 dot3ChipSetGalileoGT48004 OBJECT-IDENTITY 1438 STATUS current 1439 DESCRIPTION "The authoritative identifier for the Galileo 1440 Technology GT-48004A Four Port Fast Ethernet 1441 Switch for Multiport 10/100BASE-X Systems." 1442 ::= { dot3ChipSetGalileo 3 } 1444 dot3ChipSetGalileoGT48207 OBJECT-IDENTITY 1445 STATUS current 1446 DESCRIPTION "The authoritative identifier for the Galileo 1447 Technology GT-48207 Low-Cost 10 Port Switched 1448 Ethernet Controller for 10+10/100BASE-X." 1449 ::= { dot3ChipSetGalileo 4 } 1451 dot3ChipSetGalileoGT48208 OBJECT-IDENTITY 1452 STATUS current 1453 DESCRIPTION "The authoritative identifier for the Galileo 1454 Technology GT-48208 Advanced 10 Port Switched 1455 Ethernet Controller for 10+10/100BASE-X." 1456 ::= { dot3ChipSetGalileo 5 } 1458 dot3ChipSetGalileoGT48212 OBJECT-IDENTITY 1459 STATUS current 1460 DESCRIPTION "The authoritative identifier for the Galileo 1461 Technology GT-48212 Advanced 14 Port Switched 1462 Ethernet Controller for 10+10/100BASE-X." 1463 ::= { dot3ChipSetGalileo 6 } 1465 dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 } 1467 dot3ChipSetJatoJT1001 OBJECT-IDENTITY 1468 STATUS current 1469 DESCRIPTION "The authoritative identifier for the Jato 1470 Technologies JT1001 GigEMAC Server 1471 10/100/1000Mbps Ethernet Controller with PCI 1472 interface." 1473 ::= { dot3ChipSetJato 1 } 1475 dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 } 1477 dot3ChipSetXaQtiXQ11800FP OBJECT-IDENTITY 1478 STATUS current 1479 DESCRIPTION "The authoritative identifier for the XaQTI 1480 XQ11800FP XMAC II Gigabit Ethernet Media Access 1481 Controller." 1482 ::= { dot3ChipSetXaQti 1 } 1484 dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY 1485 STATUS current 1486 DESCRIPTION "The authoritative identifier for the XaQTI 1487 XQ18110FP GigaPower Protocol Accelerator." 1488 ::= { dot3ChipSetXaQti 2 } 1490 -- For those chipsets not represented above, OBJECT IDENTIFIER 1491 -- assignment is required in other documentation, e.g., 1492 -- assignment within that part of the registration tree 1493 -- delegated to individual enterprises (see RFC 1155 and 1494 -- RFC 1902). 1495 -- 1496 -- In the future, management of chipset registrations may be 1497 -- delegated to the Internet Assigned Numbers Authority (IANA). 1499 -- conformance information 1501 etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 } 1503 etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 } 1504 etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 } 1506 -- compliance statements 1508 etherCompliance MODULE-COMPLIANCE 1509 STATUS current 1510 DESCRIPTION "The compliance statement for managed network 1511 entities which have ethernet-like network 1512 interfaces." 1514 MODULE -- this module 1515 MANDATORY-GROUPS { etherStatsGroup } 1517 GROUP etherCollisionTableGroup 1518 DESCRIPTION "This group is optional. It is appropriate 1519 for all systems which have the necessary 1520 metering. Implementation in such systems is 1521 highly recommended." 1522 ::= { etherCompliances 1 } 1524 ether100MbsCompliance MODULE-COMPLIANCE 1525 STATUS current 1526 DESCRIPTION "The compliance statement for managed network 1527 entities which have 100 Mb/sec ethernet-like 1528 network interfaces." 1530 MODULE -- this module 1531 MANDATORY-GROUPS { etherStats100MbsGroup } 1533 GROUP etherCollisionTableGroup 1534 DESCRIPTION "This group is optional. It is appropriate 1535 for all systems which have the necessary 1536 metering. Implementation in such systems is 1537 highly recommended." 1538 ::= { etherCompliances 2 } 1540 -- units of conformance 1542 etherStatsGroup OBJECT-GROUP 1543 OBJECTS { dot3StatsIndex, 1544 dot3StatsAlignmentErrors, 1545 dot3StatsFCSErrors, 1546 dot3StatsSingleCollisionFrames, 1547 dot3StatsMultipleCollisionFrames, 1548 dot3StatsSQETestErrors, 1549 dot3StatsDeferredTransmissions, 1550 dot3StatsLateCollisions, 1551 dot3StatsExcessiveCollisions, 1552 dot3StatsInternalMacTransmitErrors, 1553 dot3StatsCarrierSenseErrors, 1554 dot3StatsFrameTooLongs, 1555 dot3StatsInternalMacReceiveErrors, 1556 dot3StatsEtherChipSet 1557 } 1558 STATUS current 1559 DESCRIPTION "A collection of objects providing information 1560 applicable to all ethernet-like network 1561 interfaces." 1562 ::= { etherGroups 1 } 1564 etherCollisionTableGroup OBJECT-GROUP 1565 OBJECTS { dot3CollFrequencies 1566 } 1567 STATUS current 1568 DESCRIPTION "A collection of objects providing a histogram 1569 of packets successfully transmitted after 1570 experiencing exactly N collisions." 1571 ::= { etherGroups 2 } 1573 etherStats100MbsGroup OBJECT-GROUP 1574 OBJECTS { dot3StatsIndex, 1575 dot3StatsAlignmentErrors, 1576 dot3StatsFCSErrors, 1577 dot3StatsSingleCollisionFrames, 1578 dot3StatsMultipleCollisionFrames, 1579 dot3StatsDeferredTransmissions, 1580 dot3StatsLateCollisions, 1581 dot3StatsExcessiveCollisions, 1582 dot3StatsInternalMacTransmitErrors, 1583 dot3StatsCarrierSenseErrors, 1584 dot3StatsFrameTooLongs, 1585 dot3StatsInternalMacReceiveErrors, 1586 dot3StatsEtherChipSet, 1587 dot3StatsSymbolErrors 1588 } 1589 STATUS current 1590 DESCRIPTION "A collection of objects providing information 1591 applicable to 100 Mb/sec ethernet-like network 1592 interfaces." 1593 ::= { etherGroups 3 } 1595 END 1597 5. Intellectual Property 1599 The IETF takes no position regarding the validity or scope of any 1600 intellectual property or other rights that might be claimed to 1601 pertain to the implementation or use of the technology described in 1602 this document or the extent to which any license under such rights 1603 might or might not be available; neither does it represent that it 1604 has made any effort to identify any such rights. Information on the 1605 IETF's procedures with respect to rights in standards-track and 1606 standards-related documentation can be found in BCP-11. Copies of 1607 claims of rights made available for publication and any assurances of 1608 licenses to be made available, or the result of an attempt made to 1609 obtain a general license or permission for the use of such 1610 proprietary rights by implementors or users of this specification can 1611 be obtained from the IETF Secretariat. 1613 The IETF invites any interested party to bring to its attention any 1614 copyrights, patents or patent applications, or other proprietary 1615 rights which may cover technology that may be required to practice 1616 this standard. Please address the information to the IETF Executive 1617 Director. 1619 6. Acknowledgements 1621 This document was produced by the 802.3 Hub MIB Working Group. 1623 This document is almost completely based on both the Standard 1624 Ethernet MIB, RFC 1643 [10], and the Proposed Standard Ethernet MIB 1625 using the SNMPv2 SMI, RFC 1650 [11], both of which were edited by 1626 Frank Kastenholz of FTP Software and produced by the Ethernet MIB 1627 Working Group. This document extends those documents by providing 1628 support for 100 Mb/sec ethernet interfaces as outlined in [6]. 1630 RFC 1643 and RFC 1650, in turn, are based on the Draft Standard 1631 Ethernet MIB, RFC 1398 [9], also edited by Frank Kastenholz and 1632 produced by the Ethernet MIB Working Group. 1634 RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, 1635 RFC 1284 [8], which was edited by John Cook of Chipcom and produced 1636 by the Transmission MIB Working Group. The Ethernet MIB Working 1637 Group gathered implementation experience of the variables specified 1638 in RFC 1284 and used that information to develop this revised MIB. 1640 RFC 1284, in turn, is based on a document written by Frank 1641 Kastenholz, then of Interlan, entitled IEEE 802.3 Layer Management 1642 Draft M compatible MIB for TCP/IP Networks [7]. This document has 1643 been modestly reworked, initially by the SNMP Working Group, and then 1644 by the Transmission Working Group, to reflect the current conventions 1645 for defining objects for MIB interfaces. James Davin, of the MIT 1646 Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN 1647 Systems, contributed to later drafts of this memo. Marshall Rose of 1648 Performance Systems International, Inc. converted the document into 1649 its current concise format. Anil Rijsinghani of DEC contributed text 1650 that more adequately describes the TDR test. Thanks to Frank 1651 Kastenholz of Interlan and Louis Steinberg of IBM for their 1652 experimentation. 1654 7. References 1656 [1] Information processing systems - Open Systems Interconnection - 1657 Specification of Abstract Syntax Notation One (ASN.1), 1658 International Organization for Standardization, International 1659 Standard 8824, December 1987. 1661 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1662 S. Waldbusser, "Structure of Management Information for Version 1663 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1664 January 1996. 1666 [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1667 S. Waldbusser, "Textual Conventions for Version 2 of the Simple 1668 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1670 [4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1671 S. Waldbusser, "Conformance Statements for Version 2 of the 1672 Simple Network Management Protocol (SNMPv2)", RFC 1904, 1673 January 1996. 1675 [5] IEEE, IEEE 802.3 Layer Management, November 1988. 1677 [6] IEEE, IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, 1678 Supplement to IEEE Std 802.3, October 26, 1995. 1680 [7] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible 1681 MIB for TCP/IP Networks", electronic mail message to mib- 1682 wg@nnsc.nsf.net, 9 June 1989. 1684 [8] Cook, J., "Definitions of Managed Objects for Ethernet-Like 1685 Interface Types", RFC 1284, Chipcom Corporation, December 1991. 1687 [9] Kastenholz, F., "Definitions of Managed Objects for the 1688 Ethernet-like Interface Types", RFC 1398, FTP Software, Inc., 1689 January 1993. 1691 [10] Kastenholz, F., "Definitions of Managed Objects for the 1692 Ethernet-like Interface Types", RFC 1643, FTP Software, Inc., 1693 July 1994. 1695 [11] Kastenholz, F., "Definitions of Managed Objects for the 1696 Ethernet-like Interface Types using SMIv2", RFC 1650, 1697 FTP Software, Inc., August 1994. 1699 [12] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB 1700 using SMIv2", RFC 2233, Cisco Systems, FTP Software, 1701 November 1997. 1703 [13] Bradner, S., "Key words for use in RFCs to Indicate 1704 Requirements Levels", BCP 14, RFC 2119, March 1997. 1706 [14] deGraaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and 1707 S. Roberts, "Definitions of Managed Objects for IEEE 802.3 1708 Medium Attachment Units (MAUs) using SMIv2", RFC 2239, 1709 3Com Corporation, Madge Networks (Israel) Ltd., Cisco Systems 1710 Inc., Cisco Systems Inc., Farallon Computing Inc., November 1711 1997. 1713 [15] Kastenholz, F., "Implementation Notes and Experience for The 1714 Internet Ethernet MIB", RFC 1369, FTP Software, October 1992. 1716 [16] McCloghrie, K., and M. Rose, Editors, "Management Information 1717 Base for Network Management of TCP/IP-based internets: MIB-II", 1718 STD 17, RFC 1213, Hughes LAN Systems, Performance Systems 1719 International, March 1991. 1721 [17] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1722 for version 3 of the Simple Network Management Protocol 1723 (SNMPv3)", RFC 2274, January 1998. 1725 [18] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1726 Control Model for the Simple Network Management Protocol 1727 (SNMP)", RFC 2275, January 1998. 1729 8. Security Considerations 1731 There are no management objects defined in this MIB that have a MAX- 1732 ACCESS clause of read-write and/or read-create. So, if this MIB is 1733 implemented correctly, then there is no risk that an intruder can 1734 alter or create any management objects of this MIB via direct SNMP 1735 SET operations. 1737 There are a number of managed objects in this MIB that may be 1738 considered to contain sensitive information. In particular, the 1739 dot3StatsEtherChipSet object may be considered sensitive in many 1740 environments, since it would allow an intruder to obtain information 1741 about which vendor's equipment is in use on the network. 1743 Therefore, it may be important in some environments to control read 1744 access to these objects and possibly to even encrypt the values of 1745 these object when sending them over the network via SNMP. Not all 1746 versions of SNMP provide features for such a secure environment. 1748 SNMPv1 by itself is such an insecure environment. Even if the 1749 network itself is secure (for example by using IPSec), even then, 1750 there is no control as to who on the secure network is allowed to 1751 access and GET (read) the objects in this MIB. 1753 It is recommended that the implementors consider the security 1754 features as provided by the SNMPv3 framework. Specifically, the use 1755 of the User-based Security Model RFC 2274 [17] and the View-based 1756 Access Control Model RFC 2275 [18] is recommended. 1758 It is then a customer/user responsibility to ensure that the SNMP 1759 entity giving access to an instance of this MIB, is properly 1760 configured to give access to those objects only to those principals 1761 (users) that have legitimate rights to access them. 1763 9. Author's Addresses 1765 John Flick 1766 Hewlett-Packard Company 1767 8000 Foothills Blvd. M/S 5556 1768 Roseville, CA 95747-5556 1770 Phone: +1 916 785 4018 1771 Email: johnf@hprnd.rose.hp.com 1773 Jeffrey Johnson 1774 RedBack Networks 1775 2570 North First Street, Suite 410 1776 San Jose, CA, 95131, USA 1778 Phone: +1 408 571 2699 1779 EMail: jeff@redbacknetworks.com 1781 A. Change Log 1783 This section enumerates changes made to RFC 1650 to produce this 1784 document. 1786 (1) The MODULE-IDENTITY has been updated to reflect the changes 1787 in the MIB. 1789 (2) A new object, dot3StatsSymbolErrors, has been added. 1791 (3) The definition of the object dot3StatsIndex has been 1792 converted to use the SMIv2 OBJECT-TYPE macro. 1794 (4) A new conformance group, etherStats100MbsGroup, has been 1795 added. 1797 (5) A new compliance statement, ether100MbsCompliance, has 1798 been added. 1800 (6) The Acknowledgements were extended to provide a more 1801 complete history of the origin of this document. 1803 (7) The discussion of ifType has been expanded. 1805 (8) A section on mapping of Interfaces MIB objects has 1806 been added. 1808 (9) A section defining the relationship of this MIB to 1809 the MAU MIB has been added. 1811 (10) A section on the mapping of IEEE 802.3 managed objects 1812 to this MIB and the Interfaces MIB has been added. 1814 (11) Converted the dot3Tests, dot3Errors, and dot3ChipSets 1815 OIDs to use the OBJECT-IDENTITY macro. 1817 (12) Added to the list of registered dot3ChipSets. 1819 (13) An intellectual property notice and copyright notice 1820 were added, as required by RFC 2026. 1822 B. Full Copyright Statement 1824 This document and translations of it may be copied and furnished to 1825 others, and derivative works that comment on or otherwise explain it 1826 or assist in its implementation may be prepared, copied, published 1827 and distributed, in whole or in part, without restriction of any 1828 kind, provided that the above copyright notice and this paragraph are 1829 included on all such copies and derivative works. However, this 1830 document itself may not be modified in any way, such as by removing 1831 the copyright notice or references to the Internet Society or other 1832 Internet organizations, except as needed for the purpose of 1833 developing Internet standards in which case the procedures for 1834 copyrights defined in the Internet Standards process must be 1835 followed, or as required to translate it into languages other than 1836 English. 1838 The limited permissions granted above are perpetual and will not be 1839 revoked by the Internet Society or its successors or assigns. 1841 This document and the information contained herein is provided on an 1842 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1843 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1844 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1845 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1846 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.