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