idnits 2.17.1 draft-ietf-hubmib-mau-mib-v2-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 5 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 9475 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' -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '4' ** Obsolete normative reference: RFC 2233 (ref. '6') (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 1902 (ref. '7') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '8') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '9') (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 1905 (ref. '10') (Obsoleted by RFC 3416) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '11') ** Obsolete normative reference: RFC 2271 (ref. '12') (Obsoleted by RFC 2571) ** Obsolete normative reference: RFC 2272 (ref. '13') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2274 (ref. '15') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (ref. '16') (Obsoleted by RFC 2575) ** Obsolete normative reference: RFC 2239 (ref. '18') (Obsoleted by RFC 2668) ** Obsolete normative reference: RFC 1515 (ref. '19') (Obsoleted by RFC 3636) == Outdated reference: A later version (-07) exists of draft-ietf-hubmib-etherif-mib-04 Summary: 21 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Hub MIB Working Group A. Smith 3 INTERNET DRAFT Extreme Networks, Inc. 4 J. Flick 5 Hewlett-Packard Company 6 K. de Graaf 7 Argon Networks 8 D. Romascanu 9 LANNET Ltd. 10 D. McMaster 11 Cisco Systems, Inc. 12 K. McCloghrie 13 Cisco Systems, Inc. 14 S. Roberts 15 Farallon Computing, Inc. 16 May 1998 18 Definitions of Managed Objects for IEEE 802.3 19 Medium Attachment Units (MAUs) using SMIv2 21 23 Status of this Memo 25 This document is an Internet-Draft. Internet-Drafts are working 26 documents of the Internet Engineering Task Force (IETF), its areas, 27 and its working groups. Note that other groups may also distribute 28 working documents as Internet-Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet- Drafts as reference 33 material or to cite them other than as "work in progress." 35 To view the entire list of current Internet-Drafts, please check the 36 "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow 37 Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern 38 Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific 39 Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). 41 Copyright Notice 43 Copyright (C) The Internet Society (1998). All Rights Reserved. 45 Abstract 47 This memo defines an experimental portion of the Management 48 Information Base (MIB) for use with network management protocols in 49 the Internet community. In particular, it defines objects for 50 managing 10, 100 and 1000Mb/second Medium Attachment Units (MAUs) 51 based on IEEE Draft P802.3/D4.2 Section 30, "10, 100 & 1000 Mb/s 52 Management," March 1998. 54 This memo does not specify a standard for the Internet community. 55 Distribution of this memo is unlimited. Please forward comments to 56 hubmib@hprnd.rose.hp.com. 58 Table of Contents 60 1. Introduction ............................................... 2 61 2. The SNMP Network Management Framework ...................... 3 62 2.1. Object Definitions ....................................... 3 63 3. Change Log ................................................. 3 64 4. Overview ................................................... 4 65 4.1. Relationship to RFC 2239 ................................. 4 66 4.2. Relationship to RFC 1515 ................................. 5 67 4.3. MAU Management ........................................... 5 68 4.4. Relationship to Other MIBs ............................... 5 69 4.4.1. Relationship to the Interfaces MIB ..................... 6 70 4.4.2. Relationship to the 802.3 Repeater MIB ................. 6 71 4.5. Management of Internal MAUs .............................. 6 72 5. Definitions ................................................ 6 73 6. Intellectual Property ...................................... 47 74 7. Acknowledgements ........................................... 47 75 8. References ................................................. 48 76 9. Security Considerations .................................... 50 77 10 Authors' Addresses ......................................... 50 78 11. Full Copyright Statement .................................. 51 80 1. Introduction 82 This memo defines a portion of the Management Information Base (MIB) 83 for use with network management protocols in the Internet community. 84 In particular, it defines objects for managing IEEE 802.3 Medium 85 Attachment Units (MAUs). 87 This memo also includes a MIB module. This MIB module extends the 88 list of managed objects specified in the earlier version of this MIB: 89 RFC 2239 [18]. 91 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 92 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 93 document are to be interpreted as described in [17]. 95 2. The SNMP Network Management Framework 97 The SNMP Network Management Framework presently consists of six major 98 components. They are: 100 o the overall architecture, described in RFC 2271 [12]. 102 o the SMI, described in RFC 1902 [7], - the mechanisms used for 103 describing and naming objects for the purpose of management. 105 o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed 106 objects for the Internet suite of protocols. 108 o the protocol, RFC 1157 [11] and/or RFC 1905 [10] and/or 109 RFC 2272 [13] -- the protocol for accessing managed 110 information. 112 o the user-based security model defined in RFC 2274 [15]. 114 o the view-based access control model defined in RFC 2275 [16]. 116 Textual conventions are defined in RFC 1903 [8], and conformance 117 statements are defined in RFC 1904 [9]. Common applications are 118 defined in RFC 2273 [14]. 120 The Framework permits new objects to be defined for the purpose of 121 experimentation and evaluation. 123 This memo specifies a MIB module that is compliant to the SNMPv2 SMI. 124 A semantically identical MIB conforming to the SNMPv1 SMI can be 125 produced through the appropriate translation. 127 2.1. Object Definitions 129 Managed objects are accessed via a virtual information store, termed 130 the Management Information Base or MIB. Objects in the MIB are 131 defined using the subset of Abstract Syntax Notation One (ASN.1) [4] 132 defined in the SMI. In particular, each object type is named by an 133 OBJECT IDENTIFIER, an administratively assigned name. The object 134 type together with an object instance serves to uniquely identify a 135 specific instantiation of the object. For human convenience, we 136 often use a textual string, termed the descriptor, to refer to the 137 object type. 139 3. Change Log 140 This section enumerates the changes made to RFC 2239 to produce this 141 document. 143 (1) The MODULE-IDENTITY has been updated to reflect the changes 144 in the MIB. 146 (2) OBJECT-IDENTITY definitions have been added for gigabit MAU 147 types. 149 (3) The ifMauTypeList, ifMauAutoNegCapability, 150 ifMauAutoNegCapAdvertised and ifMauAutoNegCapReceived 151 objects have been deprecated and replaced by 152 ifMauTypeListBits, ifMauAutoNegCapabilityBits, 153 ifMauAutoNegCapAdvertisedBits and 154 ifMauAutoNegCapReceivedBits. 156 (4) Two new objects, ifMauAutoNegRemoteFaultAdvertised and 157 ifMauAutoNegRemoteFaultReceived have been added. 159 (5) Enumerations for 'offline' and 'autoNegError' have been 160 added for the rpMauMediaAvailable and ifMauMediaAvailable 161 objects. 163 (6) The mauIfGrp100Mbs and mauIfGrpAutoNeg object groups have 164 been deprecated and replaced by mauIfGrpHighCapacity and 165 mauIfGrpAutoNeg2. 167 (7) A new object group, mauIfGrpAutoNeg1000Mbps, has been added. 169 (8) The mauModIfCompl compliance has been deprecated and 170 replaced by mauModIfCompl2. 172 (9) Added section on relationship to RFC 2239. 174 (10) Updated the SNMP Network Management Framework boilerplate. 176 (11) Refer to the Interfaces MIB, rather than the interfaces 177 group of MIB-II. 179 (12) An intellectual property notice was added, as required by 180 RFC 2026. 182 4. Overview 184 4.1. Relationship to RFC 2239 186 This MIB is intended to be a superset of that defined by RFC 2239 188 [18], which will go to historic status. This MIB includes all of the 189 objects contained in that MIB, plus several new ones which provide 190 additional capabilities. Implementors are encouraged to support all 191 applicable conformance groups in order to make the best use of the 192 new functionality provided by this MIB. The new objects provide 193 management support for: 195 o management of 1000 Mb/s interface devices 197 o management of PAUSE negotiation 199 o management of remote fault status 201 4.2. Relationship to RFC 1515 203 RFC 2239 was a replacement for RFC 1515 [19], which is now historic. 204 RFC 2239 defined a superset of RFC 1515 which contained all of the 205 objects defined in RFC 1515, plus several new ones which provided 206 additional capabilities. The new objects in RFC 2239 provided 207 management support for: 209 o management of 100 Mb/s devices 211 o auto-negotiation on interface MAUs 213 o jack management 215 4.3. MAU Management 217 Instances of these object types represent attributes of an IEEE 802.3 218 MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD 219 standard [1] and [2]. These MAUs may be connected to IEEE 802.3 220 repeaters or to 802.3 (Ethernet-like) interfaces. For convenience 221 this document refers to these devices as "repeater MAUs" and 222 "interface MAUs." 224 The definitions presented here are based on Section 30.5, "Layer 225 Management for 10, 100 & 1000 Mb/s Medium Attachment Units (MAUs)", 226 and Annex 30A, "GDMO Specifications for 802.3 managed objects" of 227 IEEE Draft P802.3z/D4.2 [2]. That specification includes definitions 228 for 10Mb/s, 100Mb/s and 1000Mb/s devices. This specification is 229 intended to serve the same purpose: to provide for management of all 230 types of Ethernet/802.3 MAUs. 232 4.4. Relationship to Other MIBs 234 It is assumed that an agent implementing this MIB will also implement 235 (at least) the 'system' group defined in MIB-II [5]. The following 236 sections identify other MIBs that such an agent should implement. 238 4.4.1. Relationship to the Interfaces MIB. 240 The sections of this document that define interface MAU-related 241 objects specify an extension to the Interfaces MIB [6]. An agent 242 implementing these interface-MAU related objects MUST also implement 243 the relevant groups of Interface MIB. The value of the object 244 ifMauIfIndex is the same as the value of 'ifIndex' used to 245 instantiate the interface to which the given MAU is connected. 247 It is expected that an agent implementing the interface-MAU related 248 objects in this MIB will also implement the Ethernet-like Interfaces 249 MIB, [20]. 251 (Note that repeater ports are not represented as interfaces in the 252 Interface MIB.) 254 4.4.2. Relationship to the 802.3 Repeater MIB 256 The section of this document that defines repeater MAU-related 257 objects specifies an extension to the 802.3 Repeater MIB defined in 258 [3]. An agent implementing these repeater-MAU related objects MUST 259 also implement the 802.3 Repeater MIB. 261 The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to 262 instantiate a repeater MAU variable shall be the same as the values 263 of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the 264 port to which the given MAU is connected. 266 4.5. Management of Internal MAUs 268 In some situations, a MAU can be "internal" -- i.e., its 269 functionality is implemented entirely within a device. For example, 270 a managed repeater may contain an internal repeater-MAU and/or an 271 internal interface-MAU through which management communications 272 originating on one of the repeater's external ports pass in order to 273 reach the management agent associated with the repeater. Such 274 internal MAUs may or may not be managed. If they are managed, 275 objects describing their attributes should appear in the appropriate 276 MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs and 277 dot3IfMauBasicGroup for internal interface-MAUs. 279 5. Definitions 281 MAU-MIB DEFINITIONS ::= BEGIN 282 IMPORTS 283 Counter32, Integer32, 284 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 285 OBJECT-IDENTITY, mib-2 286 FROM SNMPv2-SMI 287 TruthValue, TEXTUAL-CONVENTION 288 FROM SNMPv2-TC 289 OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP 290 FROM SNMPv2-CONF; 292 mauMod MODULE-IDENTITY 293 LAST-UPDATED "9805122217Z" -- May 12, 1998 294 ORGANIZATION "IETF IEEE 802.3 Hub MIB Working Group" 295 CONTACT-INFO 296 "WG E-mail: hubmib@hprnd.rose.hp.com 297 To subscribe: hubmib-request@hprnd.rose.hp.com 299 Chair: Dan Romascanu 300 Postal: LANNET Ltd. 301 Atidim Technology Park, Bldg. 3 302 Tel Aviv 61131 303 Israel 304 Tel: +972 3 645 8414, 6458458 305 Fax: +972 3 648 7146 306 E-mail: dromasca@lannet.com 308 Editors: Andrew Smith 309 Postal: Extreme Networks, Inc. 310 10460 Bandley Drive 311 Cupertino, CA 95014 312 USA 313 Tel: +1 408 342 0999 314 E-mail: andrew@extremenetworks.com 316 John Flick 317 Postal: Hewlett-Packard Company 318 8000 Foothills Blvd. M/S 5556 319 Roseville, CA 95747-5556 320 USA 321 Tel: +1 916 785 4018 322 Fax: +1 916 785 3583 323 E-mail: johnf@rose.hp.com 325 Kathryn de Graaf 326 Postal: Argon Networks 327 25 Porter Road 328 Littleton, MA 01460 329 USA 331 Tel: +1 978 486 0665 x163 332 Fax: +1 978 486 9379 333 E-mail: kdegraaf@argon.com" 334 DESCRIPTION "Management information for 802.3 MAUs. 336 The following references are used throughout 337 this MIB module: 339 [IEEE 802.3 Std] 340 refers to IEEE 802.3/ISO 8802-3 Information 341 processing systems - Local area networks - 342 Part 3: Carrier sense multiple access with 343 collision detection (CSMA/CD) access method 344 and physical layer specifications (1993), 345 and to IEEE Draft P802.3z/D4.2 - MAC 346 Parameters, Physical Layer, Repeater and 347 Management Parameters for 1000 Mb/s 348 Operation, Supplement to IEEE Std 802.3, 349 March 1998. 351 [IEEE 802.3 Mgt] 352 refers to IEEE Draft P802.3z/D4.2 - 10 Mb/s, 353 100 Mb/s & 1000 Mb/s Management, Section 30 - 354 Supplement to IEEE Std 802.3." 356 REVISION "9805122217Z" 357 DESCRIPTION "Updated to include support for 1000 Mb/sec 358 MAUs and flow control negotiation." 360 REVISION "9710310000Z" 361 DESCRIPTION "Version published as RFC 2239." 363 ::= { snmpDot3MauMgt 6 } 365 snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } 367 -- textual conventions 369 JackType ::= TEXTUAL-CONVENTION 370 STATUS current 371 DESCRIPTION "Common enumeration values for repeater 372 and interface MAU jack types." 373 SYNTAX INTEGER { 374 other(1), 375 rj45(2), 376 rj45S(3), -- rj45 shielded 377 db9(4), 378 bnc(5), 379 fAUI(6), -- female aui 380 mAUI(7), -- male aui 381 fiberSC(8), 382 fiberMIC(9), 383 fiberST(10), 384 telco(11) 385 } 387 dot3RpMauBasicGroup 388 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } 389 dot3IfMauBasicGroup 390 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } 391 dot3BroadMauBasicGroup 392 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } 394 dot3IfMauAutoNegGroup 395 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } 397 -- object identities for MAU types 398 -- (see rpMauType and ifMauType for usage) 400 dot3MauType 401 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } 403 dot3MauTypeAUI OBJECT-IDENTITY 404 STATUS current 405 DESCRIPTION "no internal MAU, view from AUI" 406 ::= { dot3MauType 1 } 408 dot3MauType10Base5 OBJECT-IDENTITY 409 STATUS current 410 DESCRIPTION "thick coax MAU (per 802.3 section 8)" 411 ::= { dot3MauType 2 } 413 dot3MauTypeFoirl OBJECT-IDENTITY 414 STATUS current 415 DESCRIPTION "FOIRL MAU (per 802.3 section 9.9)" 416 ::= { dot3MauType 3 } 418 dot3MauType10Base2 OBJECT-IDENTITY 419 STATUS current 420 DESCRIPTION "thin coax MAU (per 802.3 section 10)" 421 ::= { dot3MauType 4 } 423 dot3MauType10BaseT OBJECT-IDENTITY 424 STATUS current 425 DESCRIPTION "UTP MAU (per 802.3 section 14)" 426 ::= { dot3MauType 5 } 428 dot3MauType10BaseFP OBJECT-IDENTITY 429 STATUS current 430 DESCRIPTION "passive fiber MAU (per 802.3 section 16)" 431 ::= { dot3MauType 6 } 433 dot3MauType10BaseFB OBJECT-IDENTITY 434 STATUS current 435 DESCRIPTION "sync fiber MAU (per 802.3 section 17)" 436 ::= { dot3MauType 7 } 438 dot3MauType10BaseFL OBJECT-IDENTITY 439 STATUS current 440 DESCRIPTION "async fiber MAU (per 802.3 section 18)" 441 ::= { dot3MauType 8 } 443 dot3MauType10Broad36 OBJECT-IDENTITY 444 STATUS current 445 DESCRIPTION "broadband DTE MAU (per 802.3 section 11). 446 Note that 10BROAD36 MAUs can be attached to 447 interfaces but not to repeaters." 448 ::= { dot3MauType 9 } 450 ------ new since RFC 1515: 452 dot3MauType10BaseTHD OBJECT-IDENTITY 453 STATUS current 454 DESCRIPTION "UTP MAU (per 802.3 section 14), half duplex 455 mode" 456 ::= { dot3MauType 10 } 458 dot3MauType10BaseTFD OBJECT-IDENTITY 459 STATUS current 460 DESCRIPTION "UTP MAU (per 802.3 section 14), full duplex 461 mode" 462 ::= { dot3MauType 11 } 464 dot3MauType10BaseFLHD OBJECT-IDENTITY 465 STATUS current 466 DESCRIPTION "async fiber MAU (per 802.3 section 18), half 467 duplex mode" 468 ::= { dot3MauType 12 } 470 dot3MauType10BaseFLFD OBJECT-IDENTITY 471 STATUS current 472 DESCRIPTION "async fiber MAU (per 802.3 section 18), full 473 duplex mode" 474 ::= { dot3MauType 13 } 476 dot3MauType100BaseT4 OBJECT-IDENTITY 477 STATUS current 478 DESCRIPTION "4 pair categ. 3 UTP (per 802.3 section 23)" 479 ::= { dot3MauType 14 } 481 dot3MauType100BaseTXHD OBJECT-IDENTITY 482 STATUS current 483 DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), 484 half duplex mode" 485 ::= { dot3MauType 15 } 487 dot3MauType100BaseTXFD OBJECT-IDENTITY 488 STATUS current 489 DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), 490 full duplex mode" 491 ::= { dot3MauType 16 } 493 dot3MauType100BaseFXHD OBJECT-IDENTITY 494 STATUS current 495 DESCRIPTION "X fiber over PMT (per 802.3 section 26), half 496 duplex mode" 497 ::= { dot3MauType 17 } 499 dot3MauType100BaseFXFD OBJECT-IDENTITY 500 STATUS current 501 DESCRIPTION "X fiber over PMT (per 802.3 section 26), full 502 duplex mode" 503 ::= { dot3MauType 18 } 505 dot3MauType100BaseT2HD OBJECT-IDENTITY 506 STATUS current 507 DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32), 508 half duplex mode" 509 ::= { dot3MauType 19 } 511 dot3MauType100BaseT2FD OBJECT-IDENTITY 512 STATUS current 513 DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32), 514 full duplex mode" 515 ::= { dot3MauType 20 } 517 ------ new since RFC 2239: 519 dot3MauType1000BaseXHD OBJECT-IDENTITY 520 STATUS current 521 DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, 522 half duplex mode" 523 ::= { dot3MauType 21 } 525 dot3MauType1000BaseXFD OBJECT-IDENTITY 526 STATUS current 527 DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, 528 full duplex mode" 529 ::= { dot3MauType 22 } 531 dot3MauType1000BaseLXHD OBJECT-IDENTITY 532 STATUS current 533 DESCRIPTION "Fiber over long-wavelength laser (per 802.3 534 section 38), half duplex mode" 535 ::= { dot3MauType 23 } 537 dot3MauType1000BaseLXFD OBJECT-IDENTITY 538 STATUS current 539 DESCRIPTION "Fiber over long-wavelength laser (per 802.3 540 section 38), full duplex mode" 541 ::= { dot3MauType 24 } 543 dot3MauType1000BaseSXHD OBJECT-IDENTITY 544 STATUS current 545 DESCRIPTION "Fiber over short-wavelength laser (per 802.3 546 section 38), half duplex mode" 547 ::= { dot3MauType 25 } 549 dot3MauType1000BaseSXFD OBJECT-IDENTITY 550 STATUS current 551 DESCRIPTION "Fiber over short-wavelength laser (per 802.3 552 section 38), full duplex mode" 553 ::= { dot3MauType 26 } 555 dot3MauType1000BaseCXHD OBJECT-IDENTITY 556 STATUS current 557 DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 558 section 39), half duplex mode" 559 ::= { dot3MauType 27 } 561 dot3MauType1000BaseCXFD OBJECT-IDENTITY 562 STATUS current 563 DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 564 section 39), full duplex mode" 565 ::= { dot3MauType 28 } 567 dot3MauType1000BaseTHD OBJECT-IDENTITY 568 STATUS current 569 DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section 570 40), half duplex mode" 571 ::= { dot3MauType 29 } 573 dot3MauType1000BaseTFD OBJECT-IDENTITY 574 STATUS current 575 DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section 576 40), full duplex mode" 577 ::= { dot3MauType 30 } 579 -- 580 -- The Basic Repeater MAU Table 581 -- 583 rpMauTable OBJECT-TYPE 584 SYNTAX SEQUENCE OF RpMauEntry 585 MAX-ACCESS not-accessible 586 STATUS current 587 DESCRIPTION "Table of descriptive and status information 588 about the MAU(s) attached to the ports of a 589 repeater." 590 ::= { dot3RpMauBasicGroup 1 } 592 rpMauEntry OBJECT-TYPE 593 SYNTAX RpMauEntry 594 MAX-ACCESS not-accessible 595 STATUS current 596 DESCRIPTION "An entry in the table, containing information 597 about a single MAU." 598 INDEX { rpMauGroupIndex, 599 rpMauPortIndex, 600 rpMauIndex 601 } 602 ::= { rpMauTable 1 } 604 RpMauEntry ::= 605 SEQUENCE { 606 rpMauGroupIndex Integer32, 607 rpMauPortIndex Integer32, 608 rpMauIndex Integer32, 609 rpMauType OBJECT IDENTIFIER, 610 rpMauStatus INTEGER, 611 rpMauMediaAvailable INTEGER, 612 rpMauMediaAvailableStateExits Counter32, 613 rpMauJabberState INTEGER, 614 rpMauJabberingStateEnters Counter32, 615 rpMauFalseCarriers Counter32 616 } 618 rpMauGroupIndex OBJECT-TYPE 619 SYNTAX Integer32 (1..2147483647) 620 MAX-ACCESS read-only 621 STATUS current 622 DESCRIPTION "This variable uniquely identifies the group 623 containing the port to which the MAU described 624 by this entry is connected. 626 Note: In practice, a group will generally be 627 a field-replaceable unit (i.e., module, card, 628 or board) that can fit in the physical system 629 enclosure, and the group number will correspond 630 to a number marked on the physical enclosure. 632 The group denoted by a particular value of this 633 object is the same as the group denoted by the 634 same value of rptrGroupIndex." 635 REFERENCE "Reference RFC 2108, rptrGroupIndex." 636 ::= { rpMauEntry 1 } 638 rpMauPortIndex OBJECT-TYPE 639 SYNTAX Integer32 (1..2147483647) 640 MAX-ACCESS read-only 641 STATUS current 642 DESCRIPTION "This variable uniquely identifies the repeater 643 port within group rpMauGroupIndex to which the 644 MAU described by this entry is connected." 645 REFERENCE "Reference RFC 2108, rptrPortIndex." 646 ::= { rpMauEntry 2 } 648 rpMauIndex OBJECT-TYPE 649 SYNTAX Integer32 (1..2147483647) 650 MAX-ACCESS read-only 651 STATUS current 652 DESCRIPTION "This variable uniquely identifies the MAU 653 described by this entry from among other 654 MAUs connected to the same port 655 (rpMauPortIndex)." 656 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 657 ::= { rpMauEntry 3 } 659 rpMauType OBJECT-TYPE 660 SYNTAX OBJECT IDENTIFIER 661 MAX-ACCESS read-only 662 STATUS current 663 DESCRIPTION "This object identifies the MAU type. An 664 initial set of MAU types are defined above. The 665 assignment of OBJECT IDENTIFIERs to new types of 666 MAUs is managed by the IANA. If the MAU type is 667 unknown, the object identifier 669 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 671 is returned. Note that unknownMauType is a 672 syntactically valid object identifier, and any 673 conformant implementation of ASN.1 and the BER 674 must be able to generate and recognize this 675 value." 676 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." 677 ::= { rpMauEntry 4 } 679 rpMauStatus OBJECT-TYPE 680 SYNTAX INTEGER { 681 other(1), 682 unknown(2), 683 operational(3), 684 standby(4), 685 shutdown(5), 686 reset(6) 687 } 688 MAX-ACCESS read-write 689 STATUS current 690 DESCRIPTION "The current state of the MAU. This object may 691 be implemented as a read-only object by those 692 agents and MAUs that do not implement software 693 control of the MAU state. Some agents may not 694 support setting the value of this object to some 695 of the enumerated values. 697 The value other(1) is returned if the MAU is in 698 a state other than one of the states 2 through 699 6. 701 The value unknown(2) is returned when the MAU's 702 true state is unknown; for example, when it is 703 being initialized. 705 A MAU in the operational(3) state is fully 706 functional, operates, and passes signals to its 707 attached DTE or repeater port in accordance to 708 its specification. 710 A MAU in standby(4) state forces DI and CI to 711 idle and the media transmitter to idle or fault, 712 if supported. Standby(4) mode only applies to 713 link type MAUs. The state of 714 rpMauMediaAvailable is unaffected. 716 A MAU in shutdown(5) state assumes the same 717 condition on DI, CI, and the media transmitter 718 as though it were powered down or not connected. 719 The MAU may return other(1) value for the 720 rpMauJabberState and rpMauMediaAvailable objects 721 when it is in this state. For an AUI, this 722 state will remove power from the AUI. 724 Setting this variable to the value reset(6) 725 resets the MAU in the same manner as a 726 power-off, power-on cycle of at least one-half 727 second would. The agent is not required to 728 return the value reset (6). 730 Setting this variable to the value 731 operational(3), standby(4), or shutdown(5) 732 causes the MAU to assume the respective state 733 except that setting a mixing-type MAU or an AUI 734 to standby(4) will cause the MAU to enter the 735 shutdown state." 736 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 737 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 738 acRESETMAU." 739 ::= { rpMauEntry 5 } 741 rpMauMediaAvailable OBJECT-TYPE 742 SYNTAX INTEGER { 743 other(1), 744 unknown(2), 745 available(3), 746 notAvailable(4), 747 remoteFault(5), 748 invalidSignal(6), 749 remoteJabber(7), 750 remoteLinkLoss(8), 751 remoteTest(9), 752 offline(10), 753 autoNegError(11) 754 } 755 MAX-ACCESS read-only 756 STATUS current 757 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 758 10BASE-T, 10BASE-F) then this is equivalent to 759 the link test fail state/low light function. 760 For an AUI or a coax (including broadband) MAU 761 this indicates whether or not loopback is 762 detected on the DI circuit. The value of this 763 attribute persists between packets for MAU types 764 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 766 The value other(1) is returned if the 767 mediaAvailable state is not one of 2 through 6. 769 The value unknown(2) is returned when the MAU's 770 true state is unknown; for example, when it is 771 being initialized. At power-up or following a 772 reset, the value of this attribute will be 773 unknown for AUI, coax, and 10BASE-FP MAUs. For 774 these MAUs loopback will be tested on each 775 transmission during which no collision is 776 detected. If DI is receiving input when DO 777 returns to IDL after a transmission and there 778 has been no collision during the transmission 779 then loopback will be detected. The value of 780 this attribute will only change during 781 non-collided transmissions for AUI, coax, and 782 10BASE-FP MAUs. 784 For 100Mbps and 1000Mbps MAUs, the enumerations 785 match the states within the respective link 786 integrity state diagrams, fig 32-16, 23-12 and 787 24-15 of sections 32, 23 and 24 of [2]. Any MAU 788 which implements management of auto-negotiation 789 will map remote fault indication to remote 790 fault. 792 The value available(3) indicates that the link, 793 light, or loopback is normal. The value 794 notAvailable(4) indicates link loss, low light, 795 or no loopback. 797 The value remoteFault(5) indicates that a fault 798 has been detected at the remote end of the link. 799 This value applies to 10BASE-FB, 100BASE-T4 Far 800 End Fault Indication and non-specified remote 801 faults from a system running auto-negotiation. 802 The values remoteJabber(7), remoteLinkLoss(8), 803 and remoteTest(9) should be used instead of 804 remoteFault(5) where the reason for remote fault 805 is identified in the remote signaling protocol. 807 The value invalidSignal(6) indicates that an 808 invalid signal has been received from the other 809 end of the link. InvalidSignal(6) applies only 810 to MAUs of type 10BASE-FB. 812 Where an IEEE Std 802.3u-1995 clause 22 MII 813 is present, a logic one in the remote fault bit 814 (reference section 22.2.4.2.8 of that document) 815 maps to the value remoteFault(5), and a logic 816 zero in the link status bit (reference section 817 22.2.4.2.10 of that document) maps to the value 818 notAvailable(4). The value notAvailable(4) 819 takes precedence over the value remoteFault(5). 821 Any MAU that implements management of clause 37 822 Auto-Negotiation will map the received Remote 823 Fault (RF1 and RF2) bit values for Offline to 824 offline(10), Link Failure to remoteFault(5) and 825 Auto-Negotiation Error to autoNegError(11)." 827 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." 828 ::= { rpMauEntry 6 } 830 rpMauMediaAvailableStateExits OBJECT-TYPE 831 SYNTAX Counter32 832 MAX-ACCESS read-only 833 STATUS current 834 DESCRIPTION "A count of the number of times that 835 rpMauMediaAvailable for this MAU instance leaves 836 the state available(3)." 837 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.5, 838 aLoseMediaCounter." 839 ::= { rpMauEntry 7 } 841 rpMauJabberState OBJECT-TYPE 842 SYNTAX INTEGER { 843 other(1), 844 unknown(2), 845 noJabber(3), 846 jabbering(4) 847 } 848 MAX-ACCESS read-only 849 STATUS current 850 DESCRIPTION "The value other(1) is returned if the jabber 851 state is not 2, 3, or 4. The agent must always 852 return other(1) for MAU type dot3MauTypeAUI. 854 The value unknown(2) is returned when the MAU's 855 true state is unknown; for example, when it is 856 being initialized. 858 If the MAU is not jabbering the agent returns 859 noJabber(3). This is the 'normal' state. 861 If the MAU is in jabber state the agent returns 862 the jabbering(4) value." 863 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, 864 aJabber.jabberFlag." 865 ::= { rpMauEntry 8 } 867 rpMauJabberingStateEnters OBJECT-TYPE 868 SYNTAX Counter32 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION "A count of the number of times that 872 mauJabberState for this MAU instance enters the 873 state jabbering(4). For MAUs of type 874 dot3MauTypeAUI, dot3MauType100BaseT4, 875 dot3MauType100BaseTX, dot3MauType100BaseFX and 876 all 1000Mbps types, this counter will always 877 indicate zero." 878 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, 879 aJabber.jabberCounter." 880 ::= { rpMauEntry 9 } 882 rpMauFalseCarriers OBJECT-TYPE 883 SYNTAX Counter32 884 MAX-ACCESS read-only 885 STATUS current 886 DESCRIPTION "A count of the number of false carrier events 887 during IDLE in 100BASE-X links. This counter 888 does not increment at the symbol rate. It can 889 increment after a valid carrier completion at a 890 maximum rate of once per 100 ms until the next 891 carrier event. 893 This counter increments only for MAUs of type 894 dot3MauType100BaseT4, dot3MauType100BaseTX, and 895 dot3MauType100BaseFX and all 1000Mbps types. 896 For all other MAU types, this counter will 897 always indicate zero. 899 The approximate minimum time for rollover of 900 this counter is 7.4 hours." 901 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." 902 ::= { rpMauEntry 10 } 904 -- The rpJackTable applies to MAUs attached to repeaters 905 -- which have one or more external jacks (connectors). 907 rpJackTable OBJECT-TYPE 908 SYNTAX SEQUENCE OF RpJackEntry 909 MAX-ACCESS not-accessible 910 STATUS current 911 DESCRIPTION "Information about the external jacks attached 912 to MAUs attached to the ports of a repeater." 913 ::= { dot3RpMauBasicGroup 2 } 915 rpJackEntry OBJECT-TYPE 916 SYNTAX RpJackEntry 917 MAX-ACCESS not-accessible 918 STATUS current 919 DESCRIPTION "An entry in the table, containing information 920 about a particular jack." 921 INDEX { rpMauGroupIndex, 922 rpMauPortIndex, 923 rpMauIndex, 924 rpJackIndex 925 } 926 ::= { rpJackTable 1 } 928 RpJackEntry ::= 929 SEQUENCE { 930 rpJackIndex Integer32, 931 rpJackType JackType 932 } 934 rpJackIndex OBJECT-TYPE 935 SYNTAX Integer32 (1..2147483647) 936 MAX-ACCESS not-accessible 937 STATUS current 938 DESCRIPTION "This variable uniquely identifies the jack 939 described by this entry from among other jacks 940 attached to the same MAU (rpMauIndex)." 941 ::= { rpJackEntry 1 } 943 rpJackType OBJECT-TYPE 944 SYNTAX JackType 945 MAX-ACCESS read-only 946 STATUS current 947 DESCRIPTION "The jack connector type, as it appears on the 948 outside of the system." 949 ::= { rpJackEntry 2 } 951 -- 952 -- The Basic Interface MAU Table 953 -- 955 ifMauTable OBJECT-TYPE 956 SYNTAX SEQUENCE OF IfMauEntry 957 MAX-ACCESS not-accessible 958 STATUS current 959 DESCRIPTION "Table of descriptive and status information 960 about MAU(s) attached to an interface." 961 ::= { dot3IfMauBasicGroup 1 } 963 ifMauEntry OBJECT-TYPE 964 SYNTAX IfMauEntry 965 MAX-ACCESS not-accessible 966 STATUS current 967 DESCRIPTION "An entry in the table, containing information 968 about a single MAU." 969 INDEX { ifMauIfIndex, 970 ifMauIndex 971 } 972 ::= { ifMauTable 1 } 974 IfMauEntry ::= 975 SEQUENCE { 976 ifMauIfIndex Integer32, 977 ifMauIndex Integer32, 978 ifMauType OBJECT IDENTIFIER, 979 ifMauStatus INTEGER, 980 ifMauMediaAvailable INTEGER, 981 ifMauMediaAvailableStateExits Counter32, 982 ifMauJabberState INTEGER, 983 ifMauJabberingStateEnters Counter32, 984 ifMauFalseCarriers Counter32, 985 ifMauTypeList Integer32, 986 ifMauDefaultType OBJECT IDENTIFIER, 987 ifMauAutoNegSupported TruthValue, 988 ifMauTypeListBits BITS 989 } 991 ifMauIfIndex OBJECT-TYPE 992 SYNTAX Integer32 (1..2147483647) 993 MAX-ACCESS read-only 994 STATUS current 995 DESCRIPTION "This variable uniquely identifies the interface 996 to which the MAU described by this entry is 997 connected." 998 REFERENCE "RFC 1213, ifIndex" 999 ::= { ifMauEntry 1 } 1001 ifMauIndex OBJECT-TYPE 1002 SYNTAX Integer32 (1..2147483647) 1003 MAX-ACCESS read-only 1004 STATUS current 1005 DESCRIPTION "This variable uniquely identifies the MAU 1006 described by this entry from among other MAUs 1007 connected to the same interface (ifMauIfIndex)." 1008 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 1009 ::= { ifMauEntry 2 } 1011 ifMauType OBJECT-TYPE 1012 SYNTAX OBJECT IDENTIFIER 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION "This object identifies the 10 or 100 Mb/s 1016 baseband or broadband MAU type. An initial set 1017 of MAU types are defined above. The assignment 1018 of OBJECT IDENTIFIERs to new types of MAUs is 1019 managed by the IANA. If the MAU type is 1020 unknown, the object identifier 1022 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 1024 is returned. Note that unknownMauType is a 1025 syntactically valid object identifier, and any 1026 conformant implementation of ASN.1 and the BER 1027 must be able to generate and recognize this 1028 value. 1030 This object represents the operational type of 1031 the MAU, as determined by either (1) the result 1032 of the auto-negotiation function or (2) if 1033 auto-negotiation is not enabled or is not 1034 implemented for this MAU, by the value of the 1035 object ifMauDefaultType. In case (2), a set to 1036 the object ifMauDefaultType will force the MAU 1037 into the new operating mode." 1038 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." 1039 ::= { ifMauEntry 3 } 1041 ifMauStatus OBJECT-TYPE 1042 SYNTAX INTEGER { 1043 other(1), 1044 unknown(2), 1045 operational(3), 1046 standby(4), 1047 shutdown(5), 1048 reset(6) 1049 } 1050 MAX-ACCESS read-write 1051 STATUS current 1052 DESCRIPTION "The current state of the MAU. This object may 1053 be implemented as a read-only object by those 1054 agents and MAUs that do not implement software 1055 control of the MAU state. Some agents may not 1056 support setting the value of this object to some 1057 of the enumerated values. 1059 The value other(1) is returned if the MAU is in 1060 a state other than one of the states 2 through 1061 6. 1063 The value unknown(2) is returned when the MAU's 1064 true state is unknown; for example, when it is 1065 being initialized. 1067 A MAU in the operational(3) state is fully 1068 functional, operates, and passes signals to its 1069 attached DTE or repeater port in accordance to 1070 its specification. 1072 A MAU in standby(4) state forces DI and CI to 1073 idle and the media transmitter to idle or fault, 1074 if supported. Standby(4) mode only applies to 1075 link type MAUs. The state of 1076 ifMauMediaAvailable is unaffected. 1078 A MAU in shutdown(5) state assumes the same 1079 condition on DI, CI, and the media transmitter 1080 as though it were powered down or not connected. 1081 The MAU may return other(1) value for the 1082 ifMauJabberState and ifMauMediaAvailable objects 1083 when it is in this state. For an AUI, this 1084 state will remove power from the AUI. 1086 Setting this variable to the value reset(6) 1087 resets the MAU in the same manner as a 1088 power-off, power-on cycle of at least one-half 1089 second would. The agent is not required to 1090 return the value reset (6). 1092 Setting this variable to the value 1093 operational(3), standby(4), or shutdown(5) 1094 causes the MAU to assume the respective state 1095 except that setting a mixing-type MAU or an AUI 1096 to standby(4) will cause the MAU to enter the 1097 shutdown state." 1098 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 1099 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 1100 acRESETMAU." 1101 ::= { ifMauEntry 4 } 1103 ifMauMediaAvailable OBJECT-TYPE 1104 SYNTAX INTEGER { 1105 other(1), 1106 unknown(2), 1107 available(3), 1108 notAvailable(4), 1109 remoteFault(5), 1110 invalidSignal(6), 1111 remoteJabber(7), 1112 remoteLinkLoss(8), 1113 remoteTest(9), 1114 offline(10), 1115 autoNegError(11) 1116 } 1117 MAX-ACCESS read-only 1118 STATUS current 1119 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 1120 10BASE-T, 10BASE-F) then this is equivalent to 1121 the link test fail state/low light function. 1122 For an AUI or a coax (including broadband) MAU 1123 this indicates whether or not loopback is 1124 detected on the DI circuit. The value of this 1125 attribute persists between packets for MAU types 1126 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 1128 The value other(1) is returned if the 1129 mediaAvailable state is not one of 2 through 6. 1131 The value unknown(2) is returned when the MAU's 1132 true state is unknown; for example, when it is 1133 being initialized. At power-up or following a 1134 reset, the value of this attribute will be 1135 unknown for AUI, coax, and 10BASE-FP MAUs. For 1136 these MAUs loopback will be tested on each 1137 transmission during which no collision is 1138 detected. If DI is receiving input when DO 1139 returns to IDL after a transmission and there 1140 has been no collision during the transmission 1141 then loopback will be detected. The value of 1142 this attribute will only change during 1143 non-collided transmissions for AUI, coax, and 1144 10BASE-FP MAUs. 1146 For 100Mbps and 1000Mbps MAUs, the enumerations 1147 match the states within the respective link 1148 integrity state diagrams, fig 32-16, 23-12 and 1149 24-15 of sections 32, 23 and 24 of [2]. Any MAU 1150 which implements management of auto-negotiation 1151 will map remote fault indication to remote 1152 fault. 1154 The value available(3) indicates that the link, 1155 light, or loopback is normal. The value 1156 notAvailable(4) indicates link loss, low light, 1157 or no loopback. 1159 The value remoteFault(5) indicates that a fault 1160 has been detected at the remote end of the link. 1161 This value applies to 10BASE-FB, 100BASE-T4 Far 1162 End Fault Indication and non-specified remote 1163 faults from a system running auto-negotiation. 1164 The values remoteJabber(7), remoteLinkLoss(8), 1165 and remoteTest(9) should be used instead of 1166 remoteFault(5) where the reason for remote fault 1167 is identified in the remote signaling protocol. 1169 The value invalidSignal(6) indicates that an 1170 invalid signal has been received from the other 1171 end of the link. InvalidSignal(6) applies only 1172 to MAUs of type 10BASE-FB. 1174 Where an IEEE Std 802.3u-1995 clause 22 MII 1175 is present, a logic one in the remote fault bit 1176 (reference section 22.2.4.2.8 of that document) 1177 maps to the value remoteFault(5), and a logic 1178 zero in the link status bit (reference section 1179 22.2.4.2.10 of that document) maps to the value 1180 notAvailable(4). The value notAvailable(4) 1181 takes precedence over the value remoteFault(5). 1183 Any MAU that implements management of clause 37 1184 Auto-Negotiation will map the received RF1 and 1185 RF2 bit values for Offline to offline(10), Link 1186 Failure to remoteFault(5) and Auto-Negotiation 1187 Error to autoNegError(11)." 1188 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." 1189 ::= { ifMauEntry 5 } 1191 ifMauMediaAvailableStateExits OBJECT-TYPE 1192 SYNTAX Counter32 1193 MAX-ACCESS read-only 1194 STATUS current 1195 DESCRIPTION "A count of the number of times that 1196 ifMauMediaAvailable for this MAU instance leaves 1197 the state available(3)." 1198 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.5, 1199 aLoseMediaCounter." 1200 ::= { ifMauEntry 6 } 1202 ifMauJabberState OBJECT-TYPE 1203 SYNTAX INTEGER { 1204 other(1), 1205 unknown(2), 1206 noJabber(3), 1207 jabbering(4) 1208 } 1209 MAX-ACCESS read-only 1210 STATUS current 1211 DESCRIPTION "The value other(1) is returned if the jabber 1212 state is not 2, 3, or 4. The agent must always 1213 return other(1) for MAU type dot3MauTypeAUI. 1215 The value unknown(2) is returned when the MAU's 1216 true state is unknown; for example, when it is 1217 being initialized. 1219 If the MAU is not jabbering the agent returns 1220 noJabber(3). This is the 'normal' state. 1222 If the MAU is in jabber state the agent returns 1223 the jabbering(4) value." 1224 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, 1225 aJabber.jabberFlag." 1226 ::= { ifMauEntry 7 } 1228 ifMauJabberingStateEnters OBJECT-TYPE 1229 SYNTAX Counter32 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION "A count of the number of times that 1233 mauJabberState for this MAU instance enters the 1234 state jabbering(4). This counter will always 1235 indicate zero for MAUs of type dot1MauTypeAUI 1236 and those of speeds above 10Mbps." 1237 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, 1238 aJabber.jabberCounter." 1240 ::= { ifMauEntry 8 } 1242 ifMauFalseCarriers OBJECT-TYPE 1243 SYNTAX Counter32 1244 MAX-ACCESS read-only 1245 STATUS current 1246 DESCRIPTION "A count of the number of false carrier events 1247 during IDLE in 100BASE-X and 1000BASE-X links. 1249 For all other MAU types, this counter will 1250 always indicate zero. This counter does not 1251 increment at the symbol rate. 1253 It can increment after a valid carrier 1254 completion at a maximum rate of once per 100 ms 1255 for 100BASE-X and once per 10us for 1000BASE-X 1256 until the next CarrierEvent." 1257 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." 1258 ::= { ifMauEntry 9 } 1260 ifMauTypeList OBJECT-TYPE 1261 SYNTAX Integer32 1262 MAX-ACCESS read-only 1263 STATUS deprecated 1264 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1266 A value that uniquely identifies the set of 1267 possible IEEE 802.3 types that the MAU could be. 1268 The value is a sum which initially takes the 1269 value zero. Then, for each type capability of 1270 this MAU, 2 raised to the power noted below is 1271 added to the sum. For example, a MAU which has 1272 the capability to be only 10BASE-T would have a 1273 value of 512 (2**9). In contrast, a MAU which 1274 supports both 10Base-T (full duplex) and 1275 100BASE-TX (full duplex) would have a value of 1276 ((2**11) + (2**16)) or 67584. 1278 The powers of 2 assigned to the capabilities are 1279 these: 1281 Power Capability 1282 0 other or unknown 1283 1 AUI 1284 2 10BASE-5 1285 3 FOIRL 1286 4 10BASE-2 1287 5 10BASE-T duplex mode unknown 1288 6 10BASE-FP 1289 7 10BASE-FB 1290 8 10BASE-FL duplex mode unknown 1291 9 10BROAD36 1292 10 10BASE-T half duplex mode 1293 11 10BASE-T full duplex mode 1294 12 10BASE-FL half duplex mode 1295 13 10BASE-FL full duplex mode 1296 14 100BASE-T4 1297 15 100BASE-TX half duplex mode 1298 16 100BASE-TX full duplex mode 1299 17 100BASE-FX half duplex mode 1300 18 100BASE-FX full duplex mode 1301 19 100BASE-T2 half duplex mode 1302 20 100BASE-T2 full duplex mode 1304 If auto-negotiation is present on this MAU, this 1305 object will map to ifMauAutoNegCapability. 1307 This object has been deprecated in favour of 1308 ifMauTypeListBits." 1309 ::= { ifMauEntry 10 } 1311 ifMauDefaultType OBJECT-TYPE 1312 SYNTAX OBJECT IDENTIFIER 1313 MAX-ACCESS read-write 1314 STATUS current 1315 DESCRIPTION "This object identifies the default 1316 administrative baseband MAU type, to be used in 1317 conjunction with the operational MAU type 1318 denoted by ifMauType. 1320 The set of possible values for this object is 1321 the same as the set defined for the ifMauType 1322 object. 1324 This object represents the 1325 administratively-configured type of the MAU. If 1326 auto-negotiation is not enabled or is not 1327 implemented for this MAU, the value of this 1328 object determines the operational type of the 1329 MAU. In this case, a set to this object will 1330 force the MAU into the specified operating mode. 1332 If auto-negotiation is implemented and enabled 1333 for this MAU, the operational type of the MAU 1334 is determined by auto-negotiation, and the value 1335 of this object denotes the type to which the MAU 1336 will automatically revert if/when 1337 auto-negotiation is later disabled. 1339 NOTE TO IMPLEMENTORS: It may be necessary to 1340 provide for underlying hardware implementations 1341 which do not follow the exact behavior specified 1342 above. In particular, when 1343 ifMauAutoNegAdminStatus transitions from enabled 1344 to disabled, the agent implementation must 1345 ensure that the operational type of the MAU (as 1346 reported by ifMauType) correctly transitions to 1347 the value specified by this object, rather than 1348 continuing to operate at the value earlier 1349 determined by the auto-negotiation function." 1350 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID, and 1351 [IEEE 802.3 Std], 22.2.4.1.4." 1352 ::= { ifMauEntry 11 } 1354 ifMauAutoNegSupported OBJECT-TYPE 1355 SYNTAX TruthValue 1356 MAX-ACCESS read-only 1357 STATUS current 1358 DESCRIPTION "This object indicates whether or not 1359 auto-negotiation is supported on this MAU." 1360 ::= { ifMauEntry 12 } 1362 ifMauTypeListBits OBJECT-TYPE 1363 SYNTAX BITS { 1364 bOther(0), -- other or unknown 1365 bAUI(1), -- AUI 1366 b10base5(2), -- 10BASE-5 1367 bFoirl(3), -- FOIRL 1369 b10base2(4), -- 10BASE-2 1370 b10baseT(5), -- 10BASE-T duplex mode unknown 1371 b10baseFP(6), -- 10BASE-FP 1372 b10baseFB(7), -- 10BASE-FB 1373 b10baseFL(8), -- 10BASE-FL duplex mode unknown 1374 b10broad36(9), -- 10BROAD36 1375 b10baseTHD(10), -- 10BASE-T half duplex mode 1376 b10baseTFD(11), -- 10BASE-T full duplex mode 1377 b10baseFLHD(12), -- 10BASE-FL half duplex mode 1378 b10baseFLFD(13), -- 10BASE-FL full duplex mode 1380 b100baseT4(14), -- 100BASE-T4 1381 b100baseTXHD(15), -- 100BASE-TX half duplex mode 1382 b100baseTXFD(16), -- 100BASE-TX full duplex mode 1383 b100baseFXHD(17), -- 100BASE-FX half duplex mode 1384 b100baseFXFD(18), -- 100BASE-FX full duplex mode 1385 b100baseT2HD(19), -- 100BASE-T2 half duplex mode 1386 b100baseT2FD(20), -- 100BASE-T2 full duplex mode 1388 b1000baseXHD(21), -- 1000BASE-X half duplex mode 1389 b1000baseXFD(22), -- 1000BASE-X full duplex mode 1390 b1000baseLXHD(23), -- 1000BASE-LX half duplex mode 1391 b1000baseLXFD(24), -- 1000BASE-LX full duplex mode 1392 b1000baseSXHD(25), -- 1000BASE-SX half duplex mode 1393 b1000baseSXFD(26), -- 1000BASE-SX full duplex mode 1394 b1000baseCXHD(27), -- 1000BASE-CX half duplex mode 1395 b1000baseCXFD(28), -- 1000BASE-CX full duplex mode 1396 b1000baseTHD(29), -- 1000BASE-T half duplex mode 1397 b1000baseTFD(30) -- 1000BASE-T full duplex mode 1398 } 1399 MAX-ACCESS read-only 1400 STATUS current 1401 DESCRIPTION "A value that uniquely identifies the set of 1402 possible IEEE 802.3 types that the MAU could be. 1403 If auto-negotiation is present on this MAU, this 1404 object will map to ifMauAutoNegCapability." 1405 ::= { ifMauEntry 13 } 1407 -- The ifJackTable applies to MAUs attached to interfaces 1408 -- which have one or more external jacks (connectors). 1410 ifJackTable OBJECT-TYPE 1411 SYNTAX SEQUENCE OF IfJackEntry 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION "Information about the external jacks attached 1415 to MAUs attached to an interface." 1416 ::= { dot3IfMauBasicGroup 2 } 1418 ifJackEntry OBJECT-TYPE 1419 SYNTAX IfJackEntry 1420 MAX-ACCESS not-accessible 1421 STATUS current 1422 DESCRIPTION "An entry in the table, containing information 1423 about a particular jack." 1424 INDEX { ifMauIfIndex, 1425 ifMauIndex, 1426 ifJackIndex 1427 } 1428 ::= { ifJackTable 1 } 1430 IfJackEntry ::= 1431 SEQUENCE { 1432 ifJackIndex Integer32, 1433 ifJackType JackType 1434 } 1436 ifJackIndex OBJECT-TYPE 1437 SYNTAX Integer32 (1..2147483647) 1438 MAX-ACCESS not-accessible 1439 STATUS current 1440 DESCRIPTION "This variable uniquely identifies the jack 1441 described by this entry from among other jacks 1442 attached to the same MAU." 1443 ::= { ifJackEntry 1 } 1445 ifJackType OBJECT-TYPE 1446 SYNTAX JackType 1447 MAX-ACCESS read-only 1448 STATUS current 1449 DESCRIPTION "The jack connector type, as it appears on the 1450 outside of the system." 1451 ::= { ifJackEntry 2 } 1453 -- The ifMauAutoNegTable applies to systems in which 1454 -- auto-negotiation is supported on one or more MAUs 1455 -- attached to interfaces. Note that if auto-negotiation 1456 -- is present and enabled, the ifMauType object reflects 1457 -- the result of the auto-negotiation function. 1459 ifMauAutoNegTable OBJECT-TYPE 1460 SYNTAX SEQUENCE OF IfMauAutoNegEntry 1461 MAX-ACCESS not-accessible 1462 STATUS current 1463 DESCRIPTION "Configuration and status objects for the 1464 auto-negotiation function of MAUs attached to 1465 interfaces." 1466 ::= { dot3IfMauAutoNegGroup 1 } 1468 ifMauAutoNegEntry OBJECT-TYPE 1469 SYNTAX IfMauAutoNegEntry 1470 MAX-ACCESS not-accessible 1471 STATUS current 1472 DESCRIPTION "An entry in the table, containing configuration 1473 and status information for the auto-negotiation 1474 function of a particular MAU." 1475 INDEX { ifMauIfIndex, 1476 ifMauIndex 1478 } 1479 ::= { ifMauAutoNegTable 1 } 1481 IfMauAutoNegEntry ::= 1482 SEQUENCE { 1483 ifMauAutoNegAdminStatus INTEGER, 1484 ifMauAutoNegRemoteSignaling INTEGER, 1485 ifMauAutoNegConfig INTEGER, 1486 ifMauAutoNegCapability Integer32, 1487 ifMauAutoNegCapAdvertised Integer32, 1488 ifMauAutoNegCapReceived Integer32, 1489 ifMauAutoNegRestart INTEGER, 1490 ifMauAutoNegCapabilityBits BITS, 1491 ifMauAutoNegCapAdvertisedBits BITS, 1492 ifMauAutoNegCapReceivedBits BITS, 1493 ifMauAutoNegRemoteFaultAdvertised INTEGER, 1494 ifMauAutoNegRemoteFaultReceived INTEGER 1495 } 1497 ifMauAutoNegAdminStatus OBJECT-TYPE 1498 SYNTAX INTEGER { 1499 enabled(1), 1500 disabled(2) 1501 } 1502 MAX-ACCESS read-write 1503 STATUS current 1504 DESCRIPTION "Setting this object to enabled(1) will cause 1505 the interface which has the auto-negotiation 1506 signaling ability to be enabled. 1508 If the value of this object is disabled(2) then 1509 the interface will act as it would if it had no 1510 auto-negotiation signaling. Under these 1511 conditions, an IEEE 802.3 MAU will immediately 1512 be forced to the state indicated by the value of 1513 the object ifMauDefaultType. 1515 NOTE TO IMPLEMENTORS: When 1516 ifMauAutoNegAdminStatus transitions from enabled 1517 to disabled, the agent implementation must 1518 ensure that the operational type of the MAU (as 1519 reported by ifMauType) correctly transitions to 1520 the value specified by the ifMauDefaultType 1521 object, rather than continuing to operate at the 1522 value earlier determined by the auto-negotiation 1523 function." 1524 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.2, 1525 aAutoNegAdminState and 30.6.1.2.2, 1526 acAutoNegAdminControl." 1527 ::= { ifMauAutoNegEntry 1 } 1529 ifMauAutoNegRemoteSignaling OBJECT-TYPE 1530 SYNTAX INTEGER { 1531 detected(1), 1532 notdetected(2) 1533 } 1534 MAX-ACCESS read-only 1535 STATUS current 1536 DESCRIPTION "A value indicating whether the remote end of 1537 the link is using auto-negotiation signaling. It 1538 takes the value detected(1) if and only if, 1539 during the previous link negotiation, FLP Bursts 1540 were received." 1541 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.3, 1542 aAutoNegRemoteSignaling." 1543 ::= { ifMauAutoNegEntry 2 } 1545 ifMauAutoNegConfig OBJECT-TYPE 1546 SYNTAX INTEGER { 1547 other(1), 1548 configuring(2), 1549 complete(3), 1550 disabled(4), 1551 parallelDetectFail(5) 1552 } 1553 MAX-ACCESS read-only 1554 STATUS current 1555 DESCRIPTION "A value indicating the current status of the 1556 auto-negotiation process. The enumeration 1557 parallelDetectFail(5) maps to a failure in 1558 parallel detection as defined in 28.2.3.1 of 1559 [IEEE 802.3 Std]." 1560 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.4, 1561 aAutoNegAutoConfig." 1562 ::= { ifMauAutoNegEntry 4 } 1564 ifMauAutoNegCapability OBJECT-TYPE 1565 SYNTAX Integer32 1566 MAX-ACCESS read-only 1567 STATUS deprecated 1568 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1570 A value that uniquely identifies the set of 1571 capabilities of the local auto-negotiation 1572 entity. The value is a sum which initially 1573 takes the value zero. Then, for each capability 1574 of this interface, 2 raised to the power noted 1575 below is added to the sum. For example, an 1576 interface which has the capability to support 1577 only 100Base-TX half duplex would have a value 1578 of 32768 (2**15). In contrast, an interface 1579 which supports both 100Base-TX half duplex and 1580 and 100Base-TX full duplex would have a value of 1581 98304 ((2**15) + (2**16)). 1583 The powers of 2 assigned to the capabilities are 1584 these: 1586 Power Capability 1587 0 other or unknown 1588 (1-9) (reserved) 1589 10 10BASE-T half duplex mode 1590 11 10BASE-T full duplex mode 1591 12 (reserved) 1592 13 (reserved) 1593 14 100BASE-T4 1594 15 100BASE-TX half duplex mode 1595 16 100BASE-TX full duplex mode 1596 17 (reserved) 1597 18 (reserved) 1598 19 100BASE-T2 half duplex mode 1599 20 100BASE-T2 full duplex mode 1601 Note that interfaces that support this MIB may 1602 have capabilities that extend beyond the scope 1603 of this MIB. 1605 This object has been deprecated in favour of 1606 ifMauAutoNegCapabilityBits" 1607 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.5, 1608 aAutoNegLocalTechnologyAbility." 1609 ::= { ifMauAutoNegEntry 5 } 1611 ifMauAutoNegCapAdvertised OBJECT-TYPE 1612 SYNTAX Integer32 1613 MAX-ACCESS read-write 1614 STATUS deprecated 1615 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1617 A value that uniquely identifies the set of 1618 capabilities advertised by the local 1619 auto-negotiation entity. Refer to 1620 ifMauAutoNegCapability for a description of the 1621 possible values of this object. 1623 Capabilities in this object that are not 1624 available in ifMauAutoNegCapability cannot be 1625 enabled. 1627 This object has been deprecated in favour of 1628 ifMauAutoNegCapAdvertisedBits" 1629 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.6, 1630 aAutoNegAdvertisedTechnologyAbility." 1631 ::= { ifMauAutoNegEntry 6 } 1633 ifMauAutoNegCapReceived OBJECT-TYPE 1634 SYNTAX Integer32 1635 MAX-ACCESS read-only 1636 STATUS deprecated 1637 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1639 A value that uniquely identifies the set of 1640 capabilities received from the remote 1641 auto-negotiation entity. Refer to 1642 ifMauAutoNegCapability for a description of the 1643 possible values of this object. 1645 Note that interfaces that support this MIB may 1646 be attached to remote auto-negotiation entities 1647 which have capabilities beyond the scope of this 1648 MIB. 1650 This object has been deprecated in favour of 1651 ifMauAutoNegCapReceivedBits" 1652 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.7, 1653 aAutoNegReceivedTechnologyAbility." 1654 ::= { ifMauAutoNegEntry 7 } 1656 ifMauAutoNegRestart OBJECT-TYPE 1657 SYNTAX INTEGER { 1658 restart(1), 1659 norestart(2) 1660 } 1661 MAX-ACCESS read-write 1662 STATUS current 1663 DESCRIPTION "If the value of this object is set to 1664 restart(1) then this will force auto-negotiation 1665 to begin link renegotiation. If auto-negotiation 1666 signaling is disabled, a write to this object 1667 has no effect. 1669 Setting the value of this object to norestart(2) 1670 has no effect." 1671 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.2.1, 1672 acAutoNegRestartAutoConfig." 1673 ::= { ifMauAutoNegEntry 8 } 1675 ifMauAutoNegCapabilityBits OBJECT-TYPE 1676 SYNTAX BITS { 1677 bOther(0), -- other or unknown 1678 b10baseT(1), -- 10BASE-T half duplex mode 1679 b10baseTFD(2), -- 10BASE-T full duplex mode 1680 b100baseT4(3), -- 100BASE-T4 1681 b100baseTX(4), -- 100BASE-TX half duplex mode 1682 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1683 b100baseT2(6), -- 100BASE-T2 half duplex mode 1684 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1685 bfdxPause(8), -- PAUSE for full-duplex links 1686 bfdxAPause(9), -- Asymmetric PAUSE for full-duplex 1687 -- links 1688 bfdxSPause(10), -- Symmetric PAUSE for full-duplex 1689 -- links 1690 bfdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1691 -- full-duplex links 1692 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1693 -- duplex mode 1694 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1695 -- duplex mode 1696 b1000baseT(14), -- 1000BASE-T half duplex mode 1697 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1698 } 1699 MAX-ACCESS read-only 1700 STATUS current 1701 DESCRIPTION "A value that uniquely identifies the set of 1702 capabilities of the local auto-negotiation 1703 entity. Note that interfaces that support this 1704 MIB may have capabilities that extend beyond the 1705 scope of this MIB." 1706 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.5, 1707 aAutoNegLocalTechnologyAbility." 1708 ::= { ifMauAutoNegEntry 9 } 1710 ifMauAutoNegCapAdvertisedBits OBJECT-TYPE 1711 SYNTAX BITS { 1712 bOther(0), -- other or unknown 1713 b10baseT(1), -- 10BASE-T half duplex mode 1714 b10baseTFD(2), -- 10BASE-T full duplex mode 1715 b100baseT4(3), -- 100BASE-T4 1716 b100baseTX(4), -- 100BASE-TX half duplex mode 1717 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1718 b100baseT2(6), -- 100BASE-T2 half duplex mode 1719 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1720 bFdxPause(8), -- PAUSE for full-duplex links 1721 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 1722 -- links 1723 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 1724 -- links 1725 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1726 -- full-duplex links 1727 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1728 -- duplex mode 1729 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1730 -- duplex mode 1731 b1000baseT(14), -- 1000BASE-T half duplex mode 1732 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1733 } 1734 MAX-ACCESS read-write 1735 STATUS current 1736 DESCRIPTION "A value that uniquely identifies the set of 1737 capabilities advertised by the local 1738 auto-negotiation entity. 1740 Capabilities in this object that are not 1741 available in ifMauAutoNegCapability cannot be 1742 enabled." 1743 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.6, 1744 aAutoNegAdvertisedTechnologyAbility." 1745 ::= { ifMauAutoNegEntry 10 } 1747 ifMauAutoNegCapReceivedBits OBJECT-TYPE 1748 SYNTAX BITS { 1749 bOther(0), -- other or unknown 1750 b10baseT(1), -- 10BASE-T half duplex mode 1751 b10baseTFD(2), -- 10BASE-T full duplex mode 1752 b100baseT4(3), -- 100BASE-T4 1753 b100baseTX(4), -- 100BASE-TX half duplex mode 1754 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1755 b100baseT2(6), -- 100BASE-T2 half duplex mode 1756 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1757 bFdxPause(8), -- PAUSE for full-duplex links 1758 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 1759 -- links 1760 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 1761 -- links 1762 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1763 -- full-duplex links 1764 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1765 -- duplex mode 1766 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1767 -- duplex mode 1768 b1000baseT(14), -- 1000BASE-T half duplex mode 1769 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1770 } 1771 MAX-ACCESS read-only 1772 STATUS current 1773 DESCRIPTION "A value that uniquely identifies the set of 1774 capabilities received from the remote 1775 auto-negotiation entity. 1777 Note that interfaces that support this MIB may 1778 be attached to remote auto-negotiation entities 1779 which have capabilities beyond the scope of this 1780 MIB." 1781 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.7, 1782 aAutoNegReceivedTechnologyAbility." 1783 ::= { ifMauAutoNegEntry 11 } 1785 ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE 1786 SYNTAX INTEGER { 1787 noError(1), 1788 offline(2), 1789 linkFailure(3), 1790 autoNegError(4) 1791 } 1792 MAX-ACCESS read-write 1793 STATUS current 1794 DESCRIPTION "A value that identifies any local fault 1795 indications that this MAU has detected and will 1796 advertise at the next auto-negotiation 1797 interaction for 1000Mbps MAUs." 1798 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.6, 1799 aAutoNegAdvertisedTechnologyAbility." 1800 ::= { ifMauAutoNegEntry 12 } 1802 ifMauAutoNegRemoteFaultReceived OBJECT-TYPE 1803 SYNTAX INTEGER { 1804 noError(1), 1805 offline(2), 1806 linkFailure(3), 1807 autoNegError(4) 1808 } 1809 MAX-ACCESS read-only 1810 STATUS current 1811 DESCRIPTION "A value that identifies any fault indications 1812 received from the far end of a link by the 1813 local auto-negotiation entity for 1000Mbps 1814 MAUs." 1815 REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.7, 1816 aAutoNegReceivedTechnologyAbility." 1817 ::= { ifMauAutoNegEntry 13 } 1819 -- 1820 -- The Basic Broadband MAU Table 1821 -- 1823 broadMauBasicTable OBJECT-TYPE 1824 SYNTAX SEQUENCE OF BroadMauBasicEntry 1825 MAX-ACCESS not-accessible 1826 STATUS current 1827 DESCRIPTION "Table of descriptive and status information 1828 about the broadband MAUs connected to 1829 interfaces." 1830 ::= { dot3BroadMauBasicGroup 1 } 1832 broadMauBasicEntry OBJECT-TYPE 1833 SYNTAX BroadMauBasicEntry 1834 MAX-ACCESS not-accessible 1835 STATUS current 1836 DESCRIPTION "An entry in the table, containing information 1837 about a single broadband MAU." 1838 INDEX { broadMauIfIndex, 1839 broadMauIndex 1840 } 1841 ::= { broadMauBasicTable 1 } 1843 BroadMauBasicEntry ::= 1844 SEQUENCE { 1845 broadMauIfIndex Integer32, 1846 broadMauIndex Integer32, 1847 broadMauXmtRcvSplitType INTEGER, 1848 broadMauXmtCarrierFreq Integer32, 1849 broadMauTranslationFreq Integer32 1850 } 1852 broadMauIfIndex OBJECT-TYPE 1853 SYNTAX Integer32 (1..2147483647) 1854 MAX-ACCESS read-only 1855 STATUS current 1856 DESCRIPTION "This variable uniquely identifies the interface 1857 to which the MAU described by this entry is 1858 connected." 1859 REFERENCE "Reference RFC 1213, ifIndex." 1860 ::= { broadMauBasicEntry 1 } 1862 broadMauIndex OBJECT-TYPE 1863 SYNTAX Integer32 (1..2147483647) 1864 MAX-ACCESS read-only 1865 STATUS current 1866 DESCRIPTION "This variable uniquely identifies the MAU 1867 connected to interface broadMauIfIndex that is 1868 described by this entry." 1869 REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1870 aMAUID." 1871 ::= { broadMauBasicEntry 2 } 1873 broadMauXmtRcvSplitType OBJECT-TYPE 1874 SYNTAX INTEGER { 1875 other(1), 1876 single(2), 1877 dual(3) 1878 } 1879 MAX-ACCESS read-only 1880 STATUS current 1881 DESCRIPTION "This object indicates the type of frequency 1882 multiplexing/cabling system used to separate the 1883 transmit and receive paths for the 10BROAD36 1884 MAU. 1886 The value other(1) is returned if the split type 1887 is not either single or dual. 1889 The value single(2) indicates a single cable 1890 system. The value dual(3) indicates a dual 1891 cable system, offset normally zero." 1892 REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1893 aBbMAUXmitRcvSplitType." 1894 ::= { broadMauBasicEntry 3 } 1896 broadMauXmtCarrierFreq OBJECT-TYPE 1897 SYNTAX Integer32 1898 MAX-ACCESS read-only 1899 STATUS current 1900 DESCRIPTION "This variable indicates the transmit carrier 1901 frequency of the 10BROAD36 MAU in MHz/4; that 1902 is, in units of 250 kHz." 1903 REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1904 aBroadbandFrequencies.xmitCarrierFrequency." 1905 ::= { broadMauBasicEntry 4 } 1907 broadMauTranslationFreq OBJECT-TYPE 1908 SYNTAX Integer32 1909 MAX-ACCESS read-only 1910 STATUS current 1911 DESCRIPTION "This variable indicates the translation offset 1912 frequency of the 10BROAD36 MAU in MHz/4; that 1913 is, in units of 250 kHz." 1914 REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1915 aBroadbandFrequencies.translationFrequency." 1916 ::= { broadMauBasicEntry 5 } 1918 -- Notifications for use by 802.3 MAUs 1920 snmpDot3MauTraps OBJECT IDENTIFIER ::= { snmpDot3MauMgt 0 } 1922 rpMauJabberTrap NOTIFICATION-TYPE 1923 OBJECTS { rpMauJabberState } 1924 STATUS current 1925 DESCRIPTION "This trap is sent whenever a managed repeater 1926 MAU enters the jabber state. 1928 The agent must throttle the generation of 1929 consecutive rpMauJabberTraps so that there is at 1930 least a five-second gap between them." 1931 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1932 notification." 1933 ::= { snmpDot3MauTraps 1 } 1935 ifMauJabberTrap NOTIFICATION-TYPE 1936 OBJECTS { ifMauJabberState } 1937 STATUS current 1938 DESCRIPTION "This trap is sent whenever a managed interface 1939 MAU enters the jabber state. 1941 The agent must throttle the generation of 1942 consecutive ifMauJabberTraps so that there is at 1943 least a five-second gap between them." 1944 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1945 notification." 1946 ::= { snmpDot3MauTraps 2 } 1948 -- Conformance information 1950 mauModConf 1951 OBJECT IDENTIFIER ::= { mauMod 1 } 1952 mauModCompls 1953 OBJECT IDENTIFIER ::= { mauModConf 1 } 1954 mauModObjGrps 1955 OBJECT IDENTIFIER ::= { mauModConf 2 } 1956 mauModNotGrps 1957 OBJECT IDENTIFIER ::= { mauModConf 3 } 1959 -- Object groups 1961 mauRpGrpBasic OBJECT-GROUP 1962 OBJECTS { rpMauGroupIndex, 1963 rpMauPortIndex, 1964 rpMauIndex, 1965 rpMauType, 1966 rpMauStatus, 1967 rpMauMediaAvailable, 1968 rpMauMediaAvailableStateExits, 1969 rpMauJabberState, 1970 rpMauJabberingStateEnters 1971 } 1972 STATUS current 1973 DESCRIPTION "Basic conformance group for MAUs attached to 1974 repeater ports. This group is also the 1975 conformance specification for RFC 1515 1976 implementations." 1977 ::= { mauModObjGrps 1 } 1979 mauRpGrp100Mbs OBJECT-GROUP 1980 OBJECTS { rpMauFalseCarriers } 1981 STATUS current 1982 DESCRIPTION "Conformance group for MAUs attached to 1983 repeater ports with 100 Mb/s or greater 1984 capability." 1985 ::= { mauModObjGrps 2 } 1987 mauRpGrpJack OBJECT-GROUP 1988 OBJECTS { rpJackType } 1989 STATUS current 1990 DESCRIPTION "Conformance group for MAUs attached to 1991 repeater ports with managed jacks." 1992 ::= { mauModObjGrps 3 } 1994 mauIfGrpBasic OBJECT-GROUP 1995 OBJECTS { ifMauIfIndex, 1996 ifMauIndex, 1997 ifMauType, 1998 ifMauStatus, 1999 ifMauMediaAvailable, 2000 ifMauMediaAvailableStateExits, 2001 ifMauJabberState, 2002 ifMauJabberingStateEnters 2003 } 2004 STATUS current 2005 DESCRIPTION "Basic conformance group for MAUs attached to 2006 interfaces. This group also provides a 2007 conformance specification for RFC 1515 2008 implementations." 2009 ::= { mauModObjGrps 4 } 2011 mauIfGrp100Mbs OBJECT-GROUP 2012 OBJECTS { ifMauFalseCarriers, 2013 ifMauTypeList, 2014 ifMauDefaultType, 2015 ifMauAutoNegSupported 2016 } 2017 STATUS deprecated 2018 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2020 Conformance group for MAUs attached to 2021 interfaces with 100 Mb/s capability. 2023 This object group has been deprecated in favor 2024 of mauIfGrpHighCapacity." 2025 ::= { mauModObjGrps 5 } 2027 mauIfGrpJack OBJECT-GROUP 2028 OBJECTS { ifJackType } 2029 STATUS current 2030 DESCRIPTION "Conformance group for MAUs attached to 2031 interfaces with managed jacks." 2032 ::= { mauModObjGrps 6 } 2034 mauIfGrpAutoNeg OBJECT-GROUP 2035 OBJECTS { ifMauAutoNegAdminStatus, 2036 ifMauAutoNegRemoteSignaling, 2037 ifMauAutoNegConfig, 2038 ifMauAutoNegCapability, 2039 ifMauAutoNegCapAdvertised, 2040 ifMauAutoNegCapReceived, 2041 ifMauAutoNegRestart 2042 } 2043 STATUS deprecated 2044 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2046 Conformance group for MAUs attached to 2047 interfaces with managed auto-negotiation. 2049 This object group has been deprecated in favor 2050 of mauIfGrpAutoNeg2." 2051 ::= { mauModObjGrps 7 } 2053 mauBroadBasic OBJECT-GROUP 2054 OBJECTS { broadMauIfIndex, 2055 broadMauIndex, 2056 broadMauXmtRcvSplitType, 2057 broadMauXmtCarrierFreq, 2058 broadMauTranslationFreq 2059 } 2060 STATUS current 2061 DESCRIPTION "Conformance group for broadband MAUs attached 2062 to interfaces." 2063 ::= { mauModObjGrps 8 } 2065 mauIfGrpHighCapacity OBJECT-GROUP 2066 OBJECTS { ifMauFalseCarriers, 2067 ifMauTypeListBits, 2068 ifMauDefaultType, 2069 ifMauAutoNegSupported 2070 } 2071 STATUS current 2072 DESCRIPTION "Conformance group for MAUs attached to 2073 interfaces with 100 Mb/s or greater capability." 2074 ::= { mauModObjGrps 9 } 2076 mauIfGrpAutoNeg2 OBJECT-GROUP 2077 OBJECTS { ifMauAutoNegAdminStatus, 2078 ifMauAutoNegRemoteSignaling, 2079 ifMauAutoNegConfig, 2080 ifMauAutoNegCapabilityBits, 2081 ifMauAutoNegCapAdvertisedBits, 2082 ifMauAutoNegCapReceivedBits, 2083 ifMauAutoNegRestart 2084 } 2085 STATUS current 2086 DESCRIPTION "Conformance group for MAUs attached to 2087 interfaces with managed auto-negotiation." 2088 ::= { mauModObjGrps 10 } 2090 mauIfGrpAutoNeg1000Mbps OBJECT-GROUP 2091 OBJECTS { ifMauAutoNegRemoteFaultAdvertised, 2092 ifMauAutoNegRemoteFaultReceived 2093 } 2094 STATUS current 2095 DESCRIPTION "Conformance group for 1000Mbps MAUs attached to 2096 interfaces with managed auto-negotiation." 2098 ::= { mauModObjGrps 11 } 2100 -- Notification groups 2102 rpMauNotifications NOTIFICATION-GROUP 2103 NOTIFICATIONS { rpMauJabberTrap } 2104 STATUS current 2105 DESCRIPTION "Notifications for repeater MAUs." 2106 ::= { mauModNotGrps 1 } 2108 ifMauNotifications NOTIFICATION-GROUP 2109 NOTIFICATIONS { ifMauJabberTrap } 2110 STATUS current 2111 DESCRIPTION "Notifications for interface MAUs." 2112 ::= { mauModNotGrps 2 } 2114 -- Compliances 2116 mauModRpCompl MODULE-COMPLIANCE 2117 STATUS current 2118 DESCRIPTION "Compliance for MAUs attached to repeater 2119 ports." 2121 MODULE -- this module 2122 MANDATORY-GROUPS { mauRpGrpBasic } 2124 GROUP mauRpGrp100Mbs 2125 DESCRIPTION "Implementation of this optional group is 2126 recommended for MAUs which have 100Mb/s or 2127 greater capability." 2129 GROUP mauRpGrpJack 2130 DESCRIPTION "Implementation of this optional group is 2131 recommended for MAUs which have one or more 2132 external jacks." 2134 GROUP rpMauNotifications 2135 DESCRIPTION "Implementation of this group is recommended 2136 for MAUs attached to repeater ports." 2137 ::= { mauModCompls 1 } 2139 mauModIfCompl MODULE-COMPLIANCE 2140 STATUS deprecated 2141 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2142 Compliance for MAUs attached to interfaces." 2144 MODULE -- this module 2145 MANDATORY-GROUPS { mauIfGrpBasic } 2147 GROUP mauIfGrp100Mbs 2148 DESCRIPTION "Implementation of this optional group is 2149 recommended for MAUs which have 100Mb/s 2150 capability." 2152 GROUP mauIfGrpJack 2153 DESCRIPTION "Implementation of this optional group is 2154 recommended for MAUs which have one or more 2155 external jacks." 2157 GROUP mauIfGrpAutoNeg 2158 DESCRIPTION "Implementation of this group is mandatory 2159 for MAUs which support managed 2160 auto-negotiation." 2162 GROUP mauBroadBasic 2163 DESCRIPTION "Implementation of this group is mandatory 2164 for broadband MAUs." 2166 GROUP ifMauNotifications 2167 DESCRIPTION "Implementation of this group is recommended 2168 for MAUs attached to interfaces." 2169 ::= { mauModCompls 2 } 2171 mauModIfCompl2 MODULE-COMPLIANCE 2172 STATUS current 2173 DESCRIPTION "Compliance for MAUs attached to interfaces." 2175 MODULE -- this module 2176 MANDATORY-GROUPS { mauIfGrpBasic } 2178 GROUP mauIfGrpHighCapacity 2179 DESCRIPTION "Implementation of this optional group is 2180 recommended for MAUs which have 100Mb/s 2181 or greater capability." 2183 GROUP mauIfGrpJack 2184 DESCRIPTION "Implementation of this optional group is 2185 recommended for MAUs which have one or more 2186 external jacks." 2188 GROUP mauIfGrpAutoNeg2 2189 DESCRIPTION "Implementation of this group is mandatory 2190 for MAUs which support managed 2191 auto-negotiation." 2193 GROUP mauIfGrpAutoNeg1000Mbps 2194 DESCRIPTION "Implementation of this group is mandatory 2195 for MAUs which have 1000Mb/s or greater 2196 capability and support managed 2197 auto-negotiation." 2199 GROUP mauBroadBasic 2200 DESCRIPTION "Implementation of this group is mandatory 2201 for broadband MAUs." 2203 GROUP ifMauNotifications 2204 DESCRIPTION "Implementation of this group is recommended 2205 for MAUs attached to interfaces." 2206 ::= { mauModCompls 3 } 2208 END 2210 6. Intellectual Property 2212 The IETF takes no position regarding the validity or scope of any 2213 intellectual property or other rights that might be claimed to 2214 pertain to the implementation or use of the technology described in 2215 this document or the extent to which any license under such rights 2216 might or might not be available; neither does it represent that it 2217 has made any effort to identify any such rights. Information on the 2218 IETF's procedures with respect to rights in standards-track and 2219 standards-related documentation can be found in BCP-11. Copies of 2220 claims of rights made available for publication and any assurances of 2221 licenses to be made available, or the result of an attempt made to 2222 obtain a general license or permission for the use of such 2223 proprietary rights by implementors or users of this specification can 2224 be obtained from the IETF Secretariat. 2226 The IETF invites any interested party to bring to its attention any 2227 copyrights, patents or patent applications, or other proprietary 2228 rights which may cover technology that may be required to practice 2229 this standard. Please address the information to the IETF Executive 2230 Director. 2232 7. Acknowledgements 2234 This document was produced by the IETF IEEE 802.3 Interfaces and Hub 2235 MIB Working Group, whose efforts were greatly advanced by the 2236 contributions of the following people: 2238 Chuck Black John Flick Jeff Johnson Leon Leong Mike Lui Dave Perkins 2239 Geoff Thompson Maurice Turcotte Paul Woodruff 2241 Special thanks as well to Dave Perkins for his excellent work on the 2242 SMICng compiler, which made it easy to take advantage of the latest 2243 SNMPv2 constructs in this MIB. 2245 8. References 2247 [1] IEEE 802.3/ISO 8802-3 Information processing systems - Local 2248 area networks - Part 3: Carrier sense multiple access with 2249 collision detection (CSMA/CD) access method and physical layer 2250 specifications, 1993. 2252 [2] IEEE Draft P802.3z/D4.2, "MAC Parameters, Physical Layer, 2253 Repeater and Management Parameters for 1000 Mb/s Operation" 2254 Supplement to IEEE Std 802.3, March 1998. 2256 [3] de Graaf, K., D. Romascanu, D. McMaster, and K. McCloghrie, 2257 "Definitions of Managed Objects for IEEE 802.3 Repeater Devices 2258 using SMIv2", RFC 2108, February 1997. 2260 [4] Information processing systems - Open Systems Interconnection - 2261 Specification of Abstract Syntax Notation One (ASN.1), 2262 International Organization for Standardization, International 2263 Standard 8824, December 1987. 2265 [5] McCloghrie, K., and M. Rose, Editors, "Management Information 2266 Base for Network Management of TCP/IP-based internets: MIB-II", 2267 STD 17, RFC 1213, Hughes LAN Systems, Performance Systems 2268 International, March 1991. 2270 [6] McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB 2271 using SMIv2", RFC 2233, Cisco Systems, FTP Software, November 2272 1997. 2274 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2275 S. Waldbusser, "Structure of Management Information for version 2276 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2277 January 1996. 2279 [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2280 S. Waldbusser, "Textual Conventions for version 2 of the Simple 2281 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 2283 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2284 S. Waldbusser, "Conformance Statements for version 2 of the 2285 Simple Network Management Protocol (SNMPv2)", RFC 1904, January 2286 1996. 2288 [10] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2289 S. Waldbusser, "Protocol Operations for version 2 of the Simple 2290 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 2292 [11] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 2293 Management Protocol", RFC 1157, SNMP Research, Performance 2294 Systems International, MIT Laboratory for Computer Science, May 2295 1990. 2297 [12] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for 2298 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2299 Systems, BMC Software, Inc., IBM T.J. Watson Research, January 2300 1998. 2302 [13] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and 2303 Dispatching for the Simple Network Management Protocol (SNMP)", 2304 RFC 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. 2305 Watson Research, January 1998. 2307 [14] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, 2308 SNMP Research, Inc., Secure Computing Corporation, Cisco 2309 Systems, January 1998. 2311 [15] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for 2312 version 3 of the Simple Network Management Protocol (SNMPv3)", 2313 RFC 2274, IBM T. J. Watson Research, January 1998. 2315 [16] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access 2316 Control Model (VACM) for the Simple Network Management Protocol 2317 (SNMP)", RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., 2318 Cisco Systems, Inc., January 1998. 2320 [17] Bradner, S., "Key words for use in RFCs to Indicate 2321 Requirements Levels", BCP 14, RFC 2119, March 1997. 2323 [18] de Graaf, K., Romascanu, D., McMaster, D., K. McCloghrie, 2324 S. Roberts, "Definitions of Managed Objects 2325 for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", 2326 RFC 2239, November 1997. 2328 [19] McMaster, D., K. McCloghrie and S. Roberts, "Definitions of 2329 Managed Objects for IEEE 802.3 Medium Attachment Units 2330 (MAUs)", RFC 1515, September 1993. 2332 [20] Flick, J., and J. Johnson, "Definitions of Managed Objects for 2333 the Ethernet-like Interface Types", work in progress, 2334 draft-ietf-hubmib-etherif-mib-04.txt, March, 1998. 2336 9. Security Considerations 2338 Certain management information defined in this MIB may be considered 2339 sensitive in some network environments. Therefore, authentication of 2340 received SNMP requests and controlled access to management 2341 information should be employed in such environments. The method for 2342 this authentication is a function of the SNMP Administrative 2343 Framework, and has not been expanded by this MIB. 2345 Several objects in this MIB allow write access. Setting these 2346 objects can have a serious effect on the operation of the network, 2347 including enabling or disabling a MAU, changing a MAU's default type, 2348 enabling, disabling or restarting autonegotiation, or modifying the 2349 capabilities that a MAU advertizes during autonegotiation. It is 2350 recommended that implementers seriously consider whether set 2351 operations should be allowed without providing, at a minimum, 2352 authentication of request origin. 2354 10 Authors' Addresses 2356 Andrew Smith 2357 Extreme Networks, Inc. 2358 10460 Bandley Drive 2359 Cupertino, CA 95014, USA 2360 Tel: +1 408 342 0999 2361 E-Mail: andrew@extremenetworks.com 2363 John Flick 2364 Hewlett-Packard Company 2365 8000 Foothills Blvd. M/S 5556 2366 Roseville, CA 95747-5556 2367 Phone: +1 916 785 4018 2368 E-mail: johnf@rose.hp.com 2370 Kathryn de Graaf 2371 Argon Networks 2372 25 Porter Road 2373 Littleton, MA 01460 USA 2374 Tel: +1 978 486 0665 x163 2375 Fax: +1 978 486 9379 2376 E-mail: kdegraaf@argon.com 2377 Dan Romascanu 2378 LANNET Ltd. 2379 Atidim Technology Park, Bldg. 3 2380 Tel Aviv 61131 2381 Israel 2382 Tel: 972 3 645 8414, 6458458 2383 Fax: 972 3 648 7146 2384 E-mail: dromasca@lannet.com 2386 Donna McMaster 2387 Cisco Systems Inc. 2388 170 West Tasman Drive 2389 San Jose, CA 95134 2390 Tel: +1 408 526 5260 2391 E-Mail: mcmaster@cisco.com 2393 Keith McCloghrie 2394 Cisco Systems Inc. 2395 170 West Tasman Drive 2396 San Jose, CA 95134 2397 Tel: +1 408 526 5260 2398 E-Mail: kzm@cisco.com 2400 Sam Roberts 2401 Farallon Computing, Inc. 2402 2470 Mariner Square Loop 2403 Alameda, CA 94501-1010 2404 Tel: +1 510 814 5215 2405 E-Mail: sroberts@farallon.com 2407 11. Full Copyright Statement 2409 This document and translations of it may be copied and furnished to 2410 others, and derivative works that comment on or otherwise explain it 2411 or assist in its implementation may be prepared, copied, published 2412 and distributed, in whole or in part, without restriction of any 2413 kind, provided that the above copyright notice and this paragraph are 2414 included on all such copies and derivative works. However, this 2415 document itself may not be modified in any way, such as by removing 2416 the copyright notice or references to the Internet Society or other 2417 Internet organizations, except as needed for the purpose of 2418 developing Internet standards in which case the procedures for 2419 copyrights defined in the Internet Standards process must be 2420 followed, or as required to translate it into languages other than 2421 English. 2423 The limited permissions granted above are perpetual and will not be 2424 revoked by the Internet Society or its successors or assigns. 2426 This document and the information contained herein is provided on an 2427 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2428 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2429 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2430 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2431 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.