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