idnits 2.17.1 draft-ietf-hubmib-mau-mib-v2-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. == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. -- The abstract seems to indicate that this document obsoletes RFC2239, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (March 1999) is 9168 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '15') (Obsoleted by RFC 2575) -- Possible downref: Non-RFC (?) normative reference: ref. '16' ** Obsolete normative reference: RFC 2233 (ref. '19') (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 2239 (ref. '21') (Obsoleted by RFC 2668) ** Obsolete normative reference: RFC 1515 (ref. '22') (Obsoleted by RFC 3636) == Outdated reference: A later version (-04) exists of draft-ietf-hubmib-etherif-mib-v2-02 Summary: 24 errors (**), 0 flaws (~~), 4 warnings (==), 4 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 Lucent Technologies 10 D. McMaster 11 Cisco Systems, Inc. 12 K. McCloghrie 13 Cisco Systems, Inc. 14 S. Roberts 15 Farallon Computing, Inc. 16 March 1999 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 and is in full conformance with 26 all provisions of Section 10 of RFC2026. Internet-Drafts are working 27 documents of the Internet Engineering Task Force (IETF), its areas, 28 and its working groups. Note that other groups may also distribute 29 working documents as Internet-Drafts. 31 Internet-Drafts are draft documents valid for a maximum of six months 32 and may be updated, replaced, or obsoleted by other documents at any 33 time. It is inappropriate to use Internet- Drafts as reference 34 material or to cite them other than as "work in progress." 36 To view the list Internet-Draft Shadow Directories, see 37 http://www.ietf.org/shadow.html. 39 Copyright Notice 41 Copyright (C) The Internet Society (1999). All Rights Reserved. 43 Abstract 45 This memo defines a portion of the Management Information Base (MIB) 46 for use with network management protocols in the Internet community. 47 This memo obsoletes RFC 2239, ''Definitions of Managed Objects for 48 IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2''. This memo 49 extends that specification by including management information useful 50 for the management of 1000 Mb/s MAUs. 52 Ethernet technology, as defined by the 802.3 Working Group of the 53 IEEE, continues to evolve, with scalable increases in speed, new 54 types of cabling and interfaces, and new features. This evolution 55 may require changes in the managed objects in order to reflect this 56 new functionality. This document, as with other documents issued by 57 this working group, reflects a certain stage in the evolution of 58 Ethernet technology. In the future, this document might be revised, 59 or new documents might be issued by the Ethernet Interfaces and Hub 60 MIB Working Group, in order to reflect the evolution of Ethernet 61 technology. 63 Distribution of this memo is unlimited. Please forward comments to 64 hubmib@hprnd.rose.hp.com. 66 Table of Contents 68 1. Introduction ............................................... 2 69 2. The SNMP Management Framework .............................. 3 70 3. Overview ................................................... 4 71 3.1. Relationship to RFC 2239 ................................. 4 72 3.2. Relationship to RFC 1515 ................................. 4 73 3.3. MAU Management ........................................... 4 74 3.4. Relationship to Other MIBs ............................... 5 75 3.4.1. Relationship to the Interfaces MIB ..................... 5 76 3.4.2. Relationship to the 802.3 Repeater MIB ................. 5 77 3.5. Management of Internal MAUs .............................. 5 78 4. Definitions ................................................ 6 79 5. Intellectual Property ...................................... 47 80 6. Acknowledgements ........................................... 48 81 7. References ................................................. 48 82 8. Security Considerations .................................... 51 83 9. Authors' Addresses ......................................... 51 84 A. Change Log ................................................. 53 85 B. Full Copyright Statement ................................... 54 87 1. Introduction 89 This memo defines a portion of the Management Information Base (MIB) 90 for use with network management protocols in the Internet community. 91 In particular, it defines objects for managing IEEE 802.3 Medium 92 Attachment Units (MAUs). 94 This memo also includes a MIB module. This MIB module extends the 95 list of managed objects specified in the earlier version of this MIB: 96 RFC 2239 [21]. 98 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 99 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 100 document are to be interpreted as described in [20]. 102 2. The SNMP Management Framework 104 The SNMP Management Framework presently consists of five major 105 components: 107 o An overall architecture, described in RFC 2271 [1]. 109 o Mechanisms for describing and naming objects and events for the 110 purpose of management. The first version of this Structure of 111 Management Information (SMI) is called SMIv1 and described in 112 RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 113 called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 114 1904 [7]. 116 o Message protocols for transferring management information. The 117 first version of the SNMP message protocol is called SNMPv1 and 118 described in RFC 1157 [8]. A second version of the SNMP message 119 protocol, which is not an Internet standards track protocol, is 120 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 121 The third version of the message protocol is called SNMPv3 and 122 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 124 o Protocol operations for accessing management information. The 125 first set of protocol operations and associated PDU formats is 126 described in RFC 1157 [8]. A second set of protocol operations 127 and associated PDU formats is described in RFC 1905 [13]. 129 o A set of fundamental applications described in RFC 2273 [14] and 130 the view-based access control mechanism described in RFC 2275 131 [15]. 133 Managed objects are accessed via a virtual information store, termed 134 the Management Information Base or MIB. Objects in the MIB are 135 defined using the mechanisms defined in the SMI. 137 This memo specifies a MIB module that is compliant to the SMIv2. A 138 MIB conforming to the SMIv1 can be produced through the appropriate 139 translations. The resulting translated MIB must be semantically 140 equivalent, except where objects or events are omitted because no 141 translation is possible (use of Counter64). Some machine readable 142 information in SMIv2 will be converted into textual descriptions in 143 SMIv1 during the translation process. However, this loss of machine 144 readable information is not considered to change the semantics of the 145 MIB. 147 3. Overview 149 3.1. Relationship to RFC 2239 151 This MIB is intended to be a superset of that defined by RFC 2239 152 [21], which will go to historic status. This MIB includes all of the 153 objects contained in that MIB, plus several new ones which provide 154 additional capabilities. Implementors are encouraged to support all 155 applicable conformance groups in order to make the best use of the 156 new functionality provided by this MIB. The new objects provide 157 management support for: 159 o management of 1000 Mb/s devices 161 o management of PAUSE negotiation 163 o management of remote fault status 165 3.2. Relationship to RFC 1515 167 RFC 2239 was a replacement for RFC 1515 [22], which is now historic. 168 RFC 2239 defined a superset of RFC 1515 which contained all of the 169 objects defined in RFC 1515, plus several new ones which provided 170 additional capabilities. The new objects in RFC 2239 provided 171 management support for: 173 o management of 100 Mb/s devices 175 o auto-negotiation on interface MAUs 177 o jack management 179 3.3. MAU Management 181 Instances of these object types represent attributes of an IEEE 802.3 182 MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD 183 standard [16]. These MAUs may be connected to IEEE 802.3 repeaters 184 or to 802.3 (Ethernet-like) interfaces. For convenience this document 185 refers to these devices as "repeater MAUs" and "interface MAUs." 187 The definitions presented here are based on Section 30.5, "Layer 188 Management for 10, 100 & 1000 Mb/s Medium Attachment Units (MAUs)", 189 and Annex 30A, "GDMO Specifications for 802.3 managed object classes" 190 of IEEE Std. 802.3, 1998 edition [16]. That specification includes 191 definitions for 10Mb/s, 100Mb/s and 1000Mb/s devices. This 192 specification is intended to serve the same purpose: to provide for 193 management of all types of Ethernet/802.3 MAUs. 195 3.4. Relationship to Other MIBs 197 It is assumed that an agent implementing this MIB will also implement 198 (at least) the 'system' group defined in MIB-II [18]. The following 199 sections identify other MIBs that such an agent should implement. 201 3.4.1. Relationship to the Interfaces MIB. 203 The sections of this document that define interface MAU-related 204 objects specify an extension to the Interfaces MIB [19]. An agent 205 implementing these interface-MAU related objects MUST also implement 206 the relevant groups of Interface MIB. The value of the object 207 ifMauIfIndex is the same as the value of 'ifIndex' used to 208 instantiate the interface to which the given MAU is connected. 210 It is expected that an agent implementing the interface-MAU related 211 objects in this MIB will also implement the Ethernet-like Interfaces 212 MIB, [23]. 214 (Note that repeater ports are not represented as interfaces in the 215 Interface MIB.) 217 3.4.2. Relationship to the 802.3 Repeater MIB 219 The section of this document that defines repeater MAU-related 220 objects specifies an extension to the 802.3 Repeater MIB defined in 221 [17]. An agent implementing these repeater-MAU related objects MUST 222 also implement the 802.3 Repeater MIB. 224 The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to 225 instantiate a repeater MAU variable SHALL be the same as the values 226 of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the 227 port to which the given MAU is connected. 229 3.5. Management of Internal MAUs 231 In some situations, a MAU can be "internal" -- i.e., its 232 functionality is implemented entirely within a device. For example, 233 a managed repeater may contain an internal repeater-MAU and/or an 234 internal interface-MAU through which management communications 235 originating on one of the repeater's external ports pass in order to 236 reach the management agent associated with the repeater. Such 237 internal MAUs may or may not be managed. If they are managed, 238 objects describing their attributes should appear in the appropriate 239 MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs and 240 dot3IfMauBasicGroup for internal interface-MAUs. 242 4. Definitions 244 MAU-MIB DEFINITIONS ::= BEGIN 246 IMPORTS 247 Counter32, Integer32, 248 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 249 OBJECT-IDENTITY, mib-2 250 FROM SNMPv2-SMI 251 TruthValue, TEXTUAL-CONVENTION 252 FROM SNMPv2-TC 253 OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP 254 FROM SNMPv2-CONF; 256 mauMod MODULE-IDENTITY 257 LAST-UPDATED "9901280031Z" -- January 28, 1999 258 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 259 Working Group" 260 CONTACT-INFO 261 "WG E-mail: hubmib@hprnd.rose.hp.com 262 To subscribe: hubmib-request@hprnd.rose.hp.com 264 Chair: Dan Romascanu 265 Postal: Lucent Technologies 266 Atidim Technology Park, Bldg. 3 267 Tel Aviv 61131 268 Israel 269 Tel: +972 3 645 8414, 6458458 270 Fax: +972 3 648 7146 271 E-mail: dromasca@lucent.com 273 Editors: Andrew Smith 274 Postal: Extreme Networks, Inc. 275 10460 Bandley Drive 276 Cupertino, CA 95014 277 USA 278 Tel: +1 408 342 0999 279 E-mail: andrew@extremenetworks.com 281 John Flick 282 Postal: Hewlett-Packard Company 283 8000 Foothills Blvd. M/S 5557 284 Roseville, CA 95747-5557 285 USA 286 Tel: +1 916 785 4018 287 Fax: +1 916 785 1199 288 E-mail: johnf@rose.hp.com 290 Kathryn de Graaf 291 Postal: Argon Networks 292 25 Porter Road 293 Littleton, MA 01460 294 USA 295 Tel: +1 978 486 0665 x163 296 Fax: +1 978 486 9379 297 E-mail: kdegraaf@argon.com" 298 DESCRIPTION "Management information for 802.3 MAUs. 300 The following reference is used throughout 301 this MIB module: 303 [IEEE 802.3 Std] refers to 304 IEEE Std 802.3, 1998 Edition: 'Information 305 technology - Telecommunications and 306 information exchange between systems - 307 Local and metropolitan area networks - 308 Specific requirements - Part 3: Carrier 309 sense multiple access with collision 310 detection (CSMA/CD) access method and 311 physical layer specifications', 312 September 1998. 314 Of particular interest is Clause 30, '10Mb/s, 315 100Mb/s and 1000Mb/s Management'." 317 REVISION "9901280031Z" -- January 28, 1999 318 DESCRIPTION "Updated to include support for 1000 Mb/sec 319 MAUs and flow control negotiation." 321 REVISION "9710310000Z" -- October 31, 1997 322 DESCRIPTION "Version published as RFC 2239." 324 ::= { snmpDot3MauMgt 6 } 326 snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } 328 -- textual conventions 330 JackType ::= TEXTUAL-CONVENTION 331 STATUS current 332 DESCRIPTION "Common enumeration values for repeater 333 and interface MAU jack types." 334 SYNTAX INTEGER { 335 other(1), 336 rj45(2), 337 rj45S(3), -- rj45 shielded 338 db9(4), 339 bnc(5), 340 fAUI(6), -- female aui 341 mAUI(7), -- male aui 342 fiberSC(8), 343 fiberMIC(9), 344 fiberST(10), 345 telco(11), 346 mtrj(12), -- fiber MT-RJ 347 hssdc(13) -- fiber channel style-2 348 } 350 dot3RpMauBasicGroup 351 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } 352 dot3IfMauBasicGroup 353 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } 354 dot3BroadMauBasicGroup 355 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } 357 dot3IfMauAutoNegGroup 358 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } 360 -- object identities for MAU types 361 -- (see rpMauType and ifMauType for usage) 363 dot3MauType 364 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } 366 dot3MauTypeAUI OBJECT-IDENTITY 367 STATUS current 368 DESCRIPTION "no internal MAU, view from AUI" 369 ::= { dot3MauType 1 } 371 dot3MauType10Base5 OBJECT-IDENTITY 372 STATUS current 373 DESCRIPTION "thick coax MAU (per 802.3 section 8)" 374 ::= { dot3MauType 2 } 376 dot3MauTypeFoirl OBJECT-IDENTITY 377 STATUS current 378 DESCRIPTION "FOIRL MAU (per 802.3 section 9.9)" 379 ::= { dot3MauType 3 } 381 dot3MauType10Base2 OBJECT-IDENTITY 382 STATUS current 383 DESCRIPTION "thin coax MAU (per 802.3 section 10)" 384 ::= { dot3MauType 4 } 386 dot3MauType10BaseT OBJECT-IDENTITY 387 STATUS current 388 DESCRIPTION "UTP MAU (per 802.3 section 14)" 389 ::= { dot3MauType 5 } 391 dot3MauType10BaseFP OBJECT-IDENTITY 392 STATUS current 393 DESCRIPTION "passive fiber MAU (per 802.3 section 16)" 394 ::= { dot3MauType 6 } 396 dot3MauType10BaseFB OBJECT-IDENTITY 397 STATUS current 398 DESCRIPTION "sync fiber MAU (per 802.3 section 17)" 399 ::= { dot3MauType 7 } 401 dot3MauType10BaseFL OBJECT-IDENTITY 402 STATUS current 403 DESCRIPTION "async fiber MAU (per 802.3 section 18)" 404 ::= { dot3MauType 8 } 406 dot3MauType10Broad36 OBJECT-IDENTITY 407 STATUS current 408 DESCRIPTION "broadband DTE MAU (per 802.3 section 11). 409 Note that 10BROAD36 MAUs can be attached to 410 interfaces but not to repeaters." 411 ::= { dot3MauType 9 } 413 ------ new since RFC 1515: 415 dot3MauType10BaseTHD OBJECT-IDENTITY 416 STATUS current 417 DESCRIPTION "UTP MAU (per 802.3 section 14), half duplex 418 mode" 419 ::= { dot3MauType 10 } 421 dot3MauType10BaseTFD OBJECT-IDENTITY 422 STATUS current 423 DESCRIPTION "UTP MAU (per 802.3 section 14), full duplex 424 mode" 425 ::= { dot3MauType 11 } 427 dot3MauType10BaseFLHD OBJECT-IDENTITY 428 STATUS current 429 DESCRIPTION "async fiber MAU (per 802.3 section 18), half 430 duplex mode" 431 ::= { dot3MauType 12 } 433 dot3MauType10BaseFLFD OBJECT-IDENTITY 434 STATUS current 435 DESCRIPTION "async fiber MAU (per 802.3 section 18), full 436 duplex mode" 437 ::= { dot3MauType 13 } 439 dot3MauType100BaseT4 OBJECT-IDENTITY 440 STATUS current 441 DESCRIPTION "4 pair categ. 3 UTP (per 802.3 section 23)" 442 ::= { dot3MauType 14 } 444 dot3MauType100BaseTXHD OBJECT-IDENTITY 445 STATUS current 446 DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), 447 half duplex mode" 448 ::= { dot3MauType 15 } 450 dot3MauType100BaseTXFD OBJECT-IDENTITY 451 STATUS current 452 DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), 453 full duplex mode" 454 ::= { dot3MauType 16 } 456 dot3MauType100BaseFXHD OBJECT-IDENTITY 457 STATUS current 458 DESCRIPTION "X fiber over PMT (per 802.3 section 26), half 459 duplex mode" 460 ::= { dot3MauType 17 } 462 dot3MauType100BaseFXFD OBJECT-IDENTITY 463 STATUS current 464 DESCRIPTION "X fiber over PMT (per 802.3 section 26), full 465 duplex mode" 466 ::= { dot3MauType 18 } 468 dot3MauType100BaseT2HD OBJECT-IDENTITY 469 STATUS current 470 DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32), 471 half duplex mode" 473 ::= { dot3MauType 19 } 475 dot3MauType100BaseT2FD OBJECT-IDENTITY 476 STATUS current 477 DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32), 478 full duplex mode" 479 ::= { dot3MauType 20 } 481 ------ new since RFC 2239: 483 dot3MauType1000BaseXHD OBJECT-IDENTITY 484 STATUS current 485 DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, 486 half duplex mode" 487 ::= { dot3MauType 21 } 489 dot3MauType1000BaseXFD OBJECT-IDENTITY 490 STATUS current 491 DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, 492 full duplex mode" 493 ::= { dot3MauType 22 } 495 dot3MauType1000BaseLXHD OBJECT-IDENTITY 496 STATUS current 497 DESCRIPTION "Fiber over long-wavelength laser (per 802.3 498 section 38), half duplex mode" 499 ::= { dot3MauType 23 } 501 dot3MauType1000BaseLXFD OBJECT-IDENTITY 502 STATUS current 503 DESCRIPTION "Fiber over long-wavelength laser (per 802.3 504 section 38), full duplex mode" 505 ::= { dot3MauType 24 } 507 dot3MauType1000BaseSXHD OBJECT-IDENTITY 508 STATUS current 509 DESCRIPTION "Fiber over short-wavelength laser (per 802.3 510 section 38), half duplex mode" 511 ::= { dot3MauType 25 } 513 dot3MauType1000BaseSXFD OBJECT-IDENTITY 514 STATUS current 515 DESCRIPTION "Fiber over short-wavelength laser (per 802.3 516 section 38), full duplex mode" 517 ::= { dot3MauType 26 } 519 dot3MauType1000BaseCXHD OBJECT-IDENTITY 520 STATUS current 521 DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 522 section 39), half duplex mode" 523 ::= { dot3MauType 27 } 525 dot3MauType1000BaseCXFD OBJECT-IDENTITY 526 STATUS current 527 DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 528 section 39), full duplex mode" 529 ::= { dot3MauType 28 } 531 dot3MauType1000BaseTHD OBJECT-IDENTITY 532 STATUS current 533 DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section 534 40), half duplex mode" 535 ::= { dot3MauType 29 } 537 dot3MauType1000BaseTFD OBJECT-IDENTITY 538 STATUS current 539 DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section 540 40), full duplex mode" 541 ::= { dot3MauType 30 } 543 -- 544 -- The Basic Repeater MAU Table 545 -- 547 rpMauTable OBJECT-TYPE 548 SYNTAX SEQUENCE OF RpMauEntry 549 MAX-ACCESS not-accessible 550 STATUS current 551 DESCRIPTION "Table of descriptive and status information 552 about the MAU(s) attached to the ports of a 553 repeater." 554 ::= { dot3RpMauBasicGroup 1 } 556 rpMauEntry OBJECT-TYPE 557 SYNTAX RpMauEntry 558 MAX-ACCESS not-accessible 559 STATUS current 560 DESCRIPTION "An entry in the table, containing information 561 about a single MAU." 562 INDEX { rpMauGroupIndex, 563 rpMauPortIndex, 564 rpMauIndex 565 } 566 ::= { rpMauTable 1 } 568 RpMauEntry ::= 569 SEQUENCE { 570 rpMauGroupIndex Integer32, 571 rpMauPortIndex Integer32, 572 rpMauIndex Integer32, 573 rpMauType OBJECT IDENTIFIER, 574 rpMauStatus INTEGER, 575 rpMauMediaAvailable INTEGER, 576 rpMauMediaAvailableStateExits Counter32, 577 rpMauJabberState INTEGER, 578 rpMauJabberingStateEnters Counter32, 579 rpMauFalseCarriers Counter32 580 } 582 rpMauGroupIndex OBJECT-TYPE 583 SYNTAX Integer32 (1..2147483647) 584 MAX-ACCESS read-only 585 STATUS current 586 DESCRIPTION "This variable uniquely identifies the group 587 containing the port to which the MAU described 588 by this entry is connected. 590 Note: In practice, a group will generally be 591 a field-replaceable unit (i.e., module, card, 592 or board) that can fit in the physical system 593 enclosure, and the group number will correspond 594 to a number marked on the physical enclosure. 596 The group denoted by a particular value of this 597 object is the same as the group denoted by the 598 same value of rptrGroupIndex." 599 REFERENCE "Reference RFC 2108, rptrGroupIndex." 600 ::= { rpMauEntry 1 } 602 rpMauPortIndex OBJECT-TYPE 603 SYNTAX Integer32 (1..2147483647) 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION "This variable uniquely identifies the repeater 607 port within group rpMauGroupIndex to which the 608 MAU described by this entry is connected." 609 REFERENCE "Reference RFC 2108, rptrPortIndex." 610 ::= { rpMauEntry 2 } 612 rpMauIndex OBJECT-TYPE 613 SYNTAX Integer32 (1..2147483647) 614 MAX-ACCESS read-only 615 STATUS current 616 DESCRIPTION "This variable uniquely identifies the MAU 617 described by this entry from among other 618 MAUs connected to the same port 619 (rpMauPortIndex)." 620 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 621 ::= { rpMauEntry 3 } 623 rpMauType OBJECT-TYPE 624 SYNTAX OBJECT IDENTIFIER 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION "This object identifies the MAU type. An 628 initial set of MAU types are defined above. The 629 assignment of OBJECT IDENTIFIERs to new types of 630 MAUs is managed by the IANA. If the MAU type is 631 unknown, the object identifier 633 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 635 is returned. Note that unknownMauType is a 636 syntactically valid object identifier, and any 637 conformant implementation of ASN.1 and the BER 638 must be able to generate and recognize this 639 value." 640 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." 641 ::= { rpMauEntry 4 } 643 rpMauStatus OBJECT-TYPE 644 SYNTAX INTEGER { 645 other(1), 646 unknown(2), 647 operational(3), 648 standby(4), 649 shutdown(5), 650 reset(6) 651 } 652 MAX-ACCESS read-write 653 STATUS current 654 DESCRIPTION "The current state of the MAU. This object MAY 655 be implemented as a read-only object by those 656 agents and MAUs that do not implement software 657 control of the MAU state. Some agents may not 658 support setting the value of this object to some 659 of the enumerated values. 661 The value other(1) is returned if the MAU is in 662 a state other than one of the states 2 through 663 6. 665 The value unknown(2) is returned when the MAU's 666 true state is unknown; for example, when it is 667 being initialized. 669 A MAU in the operational(3) state is fully 670 functional, operates, and passes signals to its 671 attached DTE or repeater port in accordance to 672 its specification. 674 A MAU in standby(4) state forces DI and CI to 675 idle and the media transmitter to idle or fault, 676 if supported. Standby(4) mode only applies to 677 link type MAUs. The state of 678 rpMauMediaAvailable is unaffected. 680 A MAU in shutdown(5) state assumes the same 681 condition on DI, CI, and the media transmitter 682 as though it were powered down or not connected. 683 The MAU MAY return other(1) value for the 684 rpMauJabberState and rpMauMediaAvailable objects 685 when it is in this state. For an AUI, this 686 state will remove power from the AUI. 688 Setting this variable to the value reset(6) 689 resets the MAU in the same manner as a 690 power-off, power-on cycle of at least one-half 691 second would. The agent is not required to 692 return the value reset (6). 694 Setting this variable to the value 695 operational(3), standby(4), or shutdown(5) 696 causes the MAU to assume the respective state 697 except that setting a mixing-type MAU or an AUI 698 to standby(4) will cause the MAU to enter the 699 shutdown state." 700 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, 701 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 702 acResetMAU." 703 ::= { rpMauEntry 5 } 705 rpMauMediaAvailable OBJECT-TYPE 706 SYNTAX INTEGER { 707 other(1), 708 unknown(2), 709 available(3), 710 notAvailable(4), 711 remoteFault(5), 712 invalidSignal(6), 713 remoteJabber(7), 714 remoteLinkLoss(8), 715 remoteTest(9), 716 offline(10), 717 autoNegError(11) 718 } 719 MAX-ACCESS read-only 720 STATUS current 721 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 722 10BASE-T, 10BASE-F) then this is equivalent to 723 the link test fail state/low light function. 724 For an AUI or a coax (including broadband) MAU 725 this indicates whether or not loopback is 726 detected on the DI circuit. The value of this 727 attribute persists between packets for MAU types 728 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 730 The value other(1) is returned if the 731 mediaAvailable state is not one of 2 through 6. 733 The value unknown(2) is returned when the MAU's 734 true state is unknown; for example, when it is 735 being initialized. At power-up or following a 736 reset, the value of this attribute will be 737 unknown for AUI, coax, and 10BASE-FP MAUs. For 738 these MAUs loopback will be tested on each 739 transmission during which no collision is 740 detected. If DI is receiving input when DO 741 returns to IDL after a transmission and there 742 has been no collision during the transmission 743 then loopback will be detected. The value of 744 this attribute will only change during 745 non-collided transmissions for AUI, coax, and 746 10BASE-FP MAUs. 748 For 100Mbps and 1000Mbps MAUs, the enumerations 749 match the states within the respective link 750 integrity state diagrams, fig 32-16, 23-12 and 751 24-15 of sections 32, 23 and 24 of [2]. Any MAU 752 which implements management of auto-negotiation 753 will map remote fault indication to remote 754 fault. 756 The value available(3) indicates that the link, 757 light, or loopback is normal. The value 758 notAvailable(4) indicates link loss, low light, 759 or no loopback. 761 The value remoteFault(5) indicates that a fault 762 has been detected at the remote end of the link. 763 This value applies to 10BASE-FB, 100BASE-T4 Far 764 End Fault Indication and non-specified remote 765 faults from a system running auto-negotiation. 766 The values remoteJabber(7), remoteLinkLoss(8), 767 and remoteTest(9) SHOULD be used instead of 768 remoteFault(5) where the reason for remote fault 769 is identified in the remote signaling protocol. 771 The value invalidSignal(6) indicates that an 772 invalid signal has been received from the other 773 end of the link. InvalidSignal(6) applies only 774 to MAUs of type 10BASE-FB. 776 Where an IEEE Std 802.3u-1995 clause 22 MII 777 is present, a logic one in the remote fault bit 778 (reference section 22.2.4.2.8 of that document) 779 maps to the value remoteFault(5), and a logic 780 zero in the link status bit (reference section 781 22.2.4.2.10 of that document) maps to the value 782 notAvailable(4). The value notAvailable(4) 783 takes precedence over the value remoteFault(5). 785 Any MAU that implements management of clause 37 786 Auto-Negotiation will map the received Remote 787 Fault (RF1 and RF2) bit values for Offline to 788 offline(10), Link Failure to remoteFault(5) and 789 Auto-Negotiation Error to autoNegError(11)." 791 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." 792 ::= { rpMauEntry 6 } 794 rpMauMediaAvailableStateExits OBJECT-TYPE 795 SYNTAX Counter32 796 MAX-ACCESS read-only 797 STATUS current 798 DESCRIPTION "A count of the number of times that 799 rpMauMediaAvailable for this MAU instance leaves 800 the state available(3)." 801 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, 802 aLoseMediaCounter." 803 ::= { rpMauEntry 7 } 805 rpMauJabberState OBJECT-TYPE 806 SYNTAX INTEGER { 807 other(1), 808 unknown(2), 809 noJabber(3), 810 jabbering(4) 811 } 812 MAX-ACCESS read-only 813 STATUS current 814 DESCRIPTION "The value other(1) is returned if the jabber 815 state is not 2, 3, or 4. The agent MUST always 816 return other(1) for MAU type dot3MauTypeAUI. 818 The value unknown(2) is returned when the MAU's 819 true state is unknown; for example, when it is 820 being initialized. 822 If the MAU is not jabbering the agent returns 823 noJabber(3). This is the 'normal' state. 825 If the MAU is in jabber state the agent returns 826 the jabbering(4) value." 827 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 828 aJabber.jabberFlag." 829 ::= { rpMauEntry 8 } 831 rpMauJabberingStateEnters OBJECT-TYPE 832 SYNTAX Counter32 833 MAX-ACCESS read-only 834 STATUS current 835 DESCRIPTION "A count of the number of times that 836 mauJabberState for this MAU instance enters the 837 state jabbering(4). For MAUs of type 838 dot3MauTypeAUI, dot3MauType100BaseT4, 839 dot3MauType100BaseTX, dot3MauType100BaseFX and 840 all 1000Mbps types, this counter will always 841 indicate zero." 842 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 843 aJabber.jabberCounter." 844 ::= { rpMauEntry 9 } 846 rpMauFalseCarriers OBJECT-TYPE 847 SYNTAX Counter32 848 MAX-ACCESS read-only 849 STATUS current 850 DESCRIPTION "A count of the number of false carrier events 851 during IDLE in 100BASE-X links. This counter 852 does not increment at the symbol rate. It can 853 increment after a valid carrier completion at a 854 maximum rate of once per 100 ms until the next 855 carrier event. 857 This counter increments only for MAUs of type 858 dot3MauType100BaseT4, dot3MauType100BaseTX, and 859 dot3MauType100BaseFX and all 1000Mbps types. 860 For all other MAU types, this counter will 861 always indicate zero. 863 The approximate minimum time for rollover of 864 this counter is 7.4 hours." 865 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers." 866 ::= { rpMauEntry 10 } 868 -- The rpJackTable applies to MAUs attached to repeaters 869 -- which have one or more external jacks (connectors). 871 rpJackTable OBJECT-TYPE 872 SYNTAX SEQUENCE OF RpJackEntry 873 MAX-ACCESS not-accessible 874 STATUS current 875 DESCRIPTION "Information about the external jacks attached 876 to MAUs attached to the ports of a repeater." 877 ::= { dot3RpMauBasicGroup 2 } 879 rpJackEntry OBJECT-TYPE 880 SYNTAX RpJackEntry 881 MAX-ACCESS not-accessible 882 STATUS current 883 DESCRIPTION "An entry in the table, containing information 884 about a particular jack." 885 INDEX { rpMauGroupIndex, 886 rpMauPortIndex, 887 rpMauIndex, 888 rpJackIndex 889 } 890 ::= { rpJackTable 1 } 892 RpJackEntry ::= 893 SEQUENCE { 894 rpJackIndex Integer32, 895 rpJackType JackType 896 } 898 rpJackIndex OBJECT-TYPE 899 SYNTAX Integer32 (1..2147483647) 900 MAX-ACCESS not-accessible 901 STATUS current 902 DESCRIPTION "This variable uniquely identifies the jack 903 described by this entry from among other jacks 904 attached to the same MAU (rpMauIndex)." 905 ::= { rpJackEntry 1 } 907 rpJackType OBJECT-TYPE 908 SYNTAX JackType 909 MAX-ACCESS read-only 910 STATUS current 911 DESCRIPTION "The jack connector type, as it appears on the 912 outside of the system." 913 ::= { rpJackEntry 2 } 915 -- 916 -- The Basic Interface MAU Table 917 -- 919 ifMauTable OBJECT-TYPE 920 SYNTAX SEQUENCE OF IfMauEntry 921 MAX-ACCESS not-accessible 922 STATUS current 923 DESCRIPTION "Table of descriptive and status information 924 about MAU(s) attached to an interface." 925 ::= { dot3IfMauBasicGroup 1 } 927 ifMauEntry OBJECT-TYPE 928 SYNTAX IfMauEntry 929 MAX-ACCESS not-accessible 930 STATUS current 931 DESCRIPTION "An entry in the table, containing information 932 about a single MAU." 933 INDEX { ifMauIfIndex, 934 ifMauIndex 935 } 936 ::= { ifMauTable 1 } 938 IfMauEntry ::= 939 SEQUENCE { 940 ifMauIfIndex Integer32, 941 ifMauIndex Integer32, 942 ifMauType OBJECT IDENTIFIER, 943 ifMauStatus INTEGER, 944 ifMauMediaAvailable INTEGER, 945 ifMauMediaAvailableStateExits Counter32, 946 ifMauJabberState INTEGER, 947 ifMauJabberingStateEnters Counter32, 948 ifMauFalseCarriers Counter32, 949 ifMauTypeList Integer32, 950 ifMauDefaultType OBJECT IDENTIFIER, 951 ifMauAutoNegSupported TruthValue, 952 ifMauTypeListBits BITS 953 } 955 ifMauIfIndex OBJECT-TYPE 956 SYNTAX Integer32 (1..2147483647) 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION "This variable uniquely identifies the interface 960 to which the MAU described by this entry is 961 connected." 962 REFERENCE "RFC 1213, ifIndex" 963 ::= { ifMauEntry 1 } 965 ifMauIndex OBJECT-TYPE 966 SYNTAX Integer32 (1..2147483647) 967 MAX-ACCESS read-only 968 STATUS current 969 DESCRIPTION "This variable uniquely identifies the MAU 970 described by this entry from among other MAUs 971 connected to the same interface (ifMauIfIndex)." 972 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 973 ::= { ifMauEntry 2 } 975 ifMauType OBJECT-TYPE 976 SYNTAX OBJECT IDENTIFIER 977 MAX-ACCESS read-only 978 STATUS current 979 DESCRIPTION "This object identifies the 10 or 100 Mb/s 980 baseband or broadband MAU type. An initial set 981 of MAU types are defined above. The assignment 982 of OBJECT IDENTIFIERs to new types of MAUs is 983 managed by the IANA. If the MAU type is 984 unknown, the object identifier 986 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 988 is returned. Note that unknownMauType is a 989 syntactically valid object identifier, and any 990 conformant implementation of ASN.1 and the BER 991 must be able to generate and recognize this 992 value. 994 This object represents the operational type of 995 the MAU, as determined by either (1) the result 996 of the auto-negotiation function or (2) if 997 auto-negotiation is not enabled or is not 998 implemented for this MAU, by the value of the 999 object ifMauDefaultType. In case (2), a set to 1000 the object ifMauDefaultType will force the MAU 1001 into the new operating mode." 1002 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." 1003 ::= { ifMauEntry 3 } 1005 ifMauStatus OBJECT-TYPE 1006 SYNTAX INTEGER { 1007 other(1), 1008 unknown(2), 1009 operational(3), 1010 standby(4), 1011 shutdown(5), 1012 reset(6) 1013 } 1014 MAX-ACCESS read-write 1015 STATUS current 1016 DESCRIPTION "The current state of the MAU. This object MAY 1017 be implemented as a read-only object by those 1018 agents and MAUs that do not implement software 1019 control of the MAU state. Some agents may not 1020 support setting the value of this object to some 1021 of the enumerated values. 1023 The value other(1) is returned if the MAU is in 1024 a state other than one of the states 2 through 1025 6. 1027 The value unknown(2) is returned when the MAU's 1028 true state is unknown; for example, when it is 1029 being initialized. 1031 A MAU in the operational(3) state is fully 1032 functional, operates, and passes signals to its 1033 attached DTE or repeater port in accordance to 1034 its specification. 1036 A MAU in standby(4) state forces DI and CI to 1037 idle and the media transmitter to idle or fault, 1038 if supported. Standby(4) mode only applies to 1039 link type MAUs. The state of 1040 ifMauMediaAvailable is unaffected. 1042 A MAU in shutdown(5) state assumes the same 1043 condition on DI, CI, and the media transmitter 1044 as though it were powered down or not connected. 1045 The MAU MAY return other(1) value for the 1046 ifMauJabberState and ifMauMediaAvailable objects 1047 when it is in this state. For an AUI, this 1048 state will remove power from the AUI. 1050 Setting this variable to the value reset(6) 1051 resets the MAU in the same manner as a 1052 power-off, power-on cycle of at least one-half 1053 second would. The agent is not required to 1054 return the value reset (6). 1056 Setting this variable to the value 1057 operational(3), standby(4), or shutdown(5) 1058 causes the MAU to assume the respective state 1059 except that setting a mixing-type MAU or an AUI 1060 to standby(4) will cause the MAU to enter the 1061 shutdown state." 1062 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, 1063 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 1064 acResetMAU." 1065 ::= { ifMauEntry 4 } 1067 ifMauMediaAvailable OBJECT-TYPE 1068 SYNTAX INTEGER { 1069 other(1), 1070 unknown(2), 1071 available(3), 1072 notAvailable(4), 1073 remoteFault(5), 1074 invalidSignal(6), 1075 remoteJabber(7), 1076 remoteLinkLoss(8), 1077 remoteTest(9), 1078 offline(10), 1079 autoNegError(11) 1080 } 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 1084 10BASE-T, 10BASE-F) then this is equivalent to 1085 the link test fail state/low light function. 1086 For an AUI or a coax (including broadband) MAU 1087 this indicates whether or not loopback is 1088 detected on the DI circuit. The value of this 1089 attribute persists between packets for MAU types 1090 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 1092 The value other(1) is returned if the 1093 mediaAvailable state is not one of 2 through 6. 1095 The value unknown(2) is returned when the MAU's 1096 true state is unknown; for example, when it is 1097 being initialized. At power-up or following a 1098 reset, the value of this attribute will be 1099 unknown for AUI, coax, and 10BASE-FP MAUs. For 1100 these MAUs loopback will be tested on each 1101 transmission during which no collision is 1102 detected. If DI is receiving input when DO 1103 returns to IDL after a transmission and there 1104 has been no collision during the transmission 1105 then loopback will be detected. The value of 1106 this attribute will only change during 1107 non-collided transmissions for AUI, coax, and 1108 10BASE-FP MAUs. 1110 For 100Mbps and 1000Mbps MAUs, the enumerations 1111 match the states within the respective link 1112 integrity state diagrams, fig 32-16, 23-12 and 1113 24-15 of sections 32, 23 and 24 of [2]. Any MAU 1114 which implements management of auto-negotiation 1115 will map remote fault indication to remote 1116 fault. 1118 The value available(3) indicates that the link, 1119 light, or loopback is normal. The value 1120 notAvailable(4) indicates link loss, low light, 1121 or no loopback. 1123 The value remoteFault(5) indicates that a fault 1124 has been detected at the remote end of the link. 1125 This value applies to 10BASE-FB, 100BASE-T4 Far 1126 End Fault Indication and non-specified remote 1127 faults from a system running auto-negotiation. 1128 The values remoteJabber(7), remoteLinkLoss(8), 1129 and remoteTest(9) SHOULD be used instead of 1130 remoteFault(5) where the reason for remote fault 1131 is identified in the remote signaling protocol. 1133 The value invalidSignal(6) indicates that an 1134 invalid signal has been received from the other 1135 end of the link. InvalidSignal(6) applies only 1136 to MAUs of type 10BASE-FB. 1138 Where an IEEE Std 802.3u-1995 clause 22 MII 1139 is present, a logic one in the remote fault bit 1140 (reference section 22.2.4.2.8 of that document) 1141 maps to the value remoteFault(5), and a logic 1142 zero in the link status bit (reference section 1143 22.2.4.2.10 of that document) maps to the value 1144 notAvailable(4). The value notAvailable(4) 1145 takes precedence over the value remoteFault(5). 1147 Any MAU that implements management of clause 37 1148 Auto-Negotiation will map the received RF1 and 1149 RF2 bit values for Offline to offline(10), Link 1150 Failure to remoteFault(5) and Auto-Negotiation 1151 Error to autoNegError(11)." 1152 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." 1153 ::= { ifMauEntry 5 } 1155 ifMauMediaAvailableStateExits OBJECT-TYPE 1156 SYNTAX Counter32 1157 MAX-ACCESS read-only 1158 STATUS current 1159 DESCRIPTION "A count of the number of times that 1160 ifMauMediaAvailable for this MAU instance leaves 1161 the state available(3)." 1162 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, 1163 aLoseMediaCounter." 1164 ::= { ifMauEntry 6 } 1166 ifMauJabberState OBJECT-TYPE 1167 SYNTAX INTEGER { 1168 other(1), 1169 unknown(2), 1170 noJabber(3), 1171 jabbering(4) 1172 } 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION "The value other(1) is returned if the jabber 1176 state is not 2, 3, or 4. The agent MUST always 1177 return other(1) for MAU type dot3MauTypeAUI. 1179 The value unknown(2) is returned when the MAU's 1180 true state is unknown; for example, when it is 1181 being initialized. 1183 If the MAU is not jabbering the agent returns 1184 noJabber(3). This is the 'normal' state. 1186 If the MAU is in jabber state the agent returns 1187 the jabbering(4) value." 1188 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1189 aJabber.jabberFlag." 1190 ::= { ifMauEntry 7 } 1192 ifMauJabberingStateEnters OBJECT-TYPE 1193 SYNTAX Counter32 1194 MAX-ACCESS read-only 1195 STATUS current 1196 DESCRIPTION "A count of the number of times that 1197 mauJabberState for this MAU instance enters the 1198 state jabbering(4). This counter will always 1199 indicate zero for MAUs of type dot1MauTypeAUI 1200 and those of speeds above 10Mbps." 1201 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1202 aJabber.jabberCounter." 1203 ::= { ifMauEntry 8 } 1205 ifMauFalseCarriers OBJECT-TYPE 1206 SYNTAX Counter32 1207 MAX-ACCESS read-only 1208 STATUS current 1209 DESCRIPTION "A count of the number of false carrier events 1210 during IDLE in 100BASE-X and 1000BASE-X links. 1212 For all other MAU types, this counter will 1213 always indicate zero. This counter does not 1214 increment at the symbol rate. 1216 It can increment after a valid carrier 1217 completion at a maximum rate of once per 100 ms 1218 for 100BASE-X and once per 10us for 1000BASE-X 1219 until the next CarrierEvent." 1220 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers." 1221 ::= { ifMauEntry 9 } 1223 ifMauTypeList OBJECT-TYPE 1224 SYNTAX Integer32 1225 MAX-ACCESS read-only 1226 STATUS deprecated 1227 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1229 A value that uniquely identifies the set of 1230 possible IEEE 802.3 types that the MAU could be. 1231 The value is a sum which initially takes the 1232 value zero. Then, for each type capability of 1233 this MAU, 2 raised to the power noted below is 1234 added to the sum. For example, a MAU which has 1235 the capability to be only 10BASE-T would have a 1236 value of 512 (2**9). In contrast, a MAU which 1237 supports both 10Base-T (full duplex) and 1238 100BASE-TX (full duplex) would have a value of 1239 ((2**11) + (2**16)) or 67584. 1241 The powers of 2 assigned to the capabilities are 1242 these: 1244 Power Capability 1245 0 other or unknown 1246 1 AUI 1247 2 10BASE-5 1248 3 FOIRL 1249 4 10BASE-2 1250 5 10BASE-T duplex mode unknown 1251 6 10BASE-FP 1252 7 10BASE-FB 1253 8 10BASE-FL duplex mode unknown 1254 9 10BROAD36 1255 10 10BASE-T half duplex mode 1256 11 10BASE-T full duplex mode 1257 12 10BASE-FL half duplex mode 1258 13 10BASE-FL full duplex mode 1259 14 100BASE-T4 1260 15 100BASE-TX half duplex mode 1261 16 100BASE-TX full duplex mode 1262 17 100BASE-FX half duplex mode 1263 18 100BASE-FX full duplex mode 1264 19 100BASE-T2 half duplex mode 1265 20 100BASE-T2 full duplex mode 1267 If auto-negotiation is present on this MAU, this 1268 object will map to ifMauAutoNegCapability. 1270 This object has been deprecated in favour of 1271 ifMauTypeListBits." 1272 ::= { ifMauEntry 10 } 1274 ifMauDefaultType OBJECT-TYPE 1275 SYNTAX OBJECT IDENTIFIER 1276 MAX-ACCESS read-write 1277 STATUS current 1278 DESCRIPTION "This object identifies the default 1279 administrative baseband MAU type, to be used in 1280 conjunction with the operational MAU type 1281 denoted by ifMauType. 1283 The set of possible values for this object is 1284 the same as the set defined for the ifMauType 1285 object. 1287 This object represents the 1288 administratively-configured type of the MAU. If 1289 auto-negotiation is not enabled or is not 1290 implemented for this MAU, the value of this 1291 object determines the operational type of the 1292 MAU. In this case, a set to this object will 1293 force the MAU into the specified operating mode. 1295 If auto-negotiation is implemented and enabled 1296 for this MAU, the operational type of the MAU 1297 is determined by auto-negotiation, and the value 1298 of this object denotes the type to which the MAU 1299 will automatically revert if/when 1300 auto-negotiation is later disabled. 1302 NOTE TO IMPLEMENTORS: It may be necessary to 1303 provide for underlying hardware implementations 1304 which do not follow the exact behavior specified 1305 above. In particular, when 1306 ifMauAutoNegAdminStatus transitions from enabled 1307 to disabled, the agent implementation MUST 1308 ensure that the operational type of the MAU (as 1309 reported by ifMauType) correctly transitions to 1310 the value specified by this object, rather than 1311 continuing to operate at the value earlier 1312 determined by the auto-negotiation function." 1313 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID, and 1314 22.2.4.1.4." 1315 ::= { ifMauEntry 11 } 1317 ifMauAutoNegSupported OBJECT-TYPE 1318 SYNTAX TruthValue 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION "This object indicates whether or not 1322 auto-negotiation is supported on this MAU." 1323 ::= { ifMauEntry 12 } 1325 ifMauTypeListBits OBJECT-TYPE 1326 SYNTAX BITS { 1327 bOther(0), -- other or unknown 1328 bAUI(1), -- AUI 1329 b10base5(2), -- 10BASE-5 1330 bFoirl(3), -- FOIRL 1332 b10base2(4), -- 10BASE-2 1333 b10baseT(5), -- 10BASE-T duplex mode unknown 1334 b10baseFP(6), -- 10BASE-FP 1335 b10baseFB(7), -- 10BASE-FB 1336 b10baseFL(8), -- 10BASE-FL duplex mode unknown 1337 b10broad36(9), -- 10BROAD36 1338 b10baseTHD(10), -- 10BASE-T half duplex mode 1339 b10baseTFD(11), -- 10BASE-T full duplex mode 1340 b10baseFLHD(12), -- 10BASE-FL half duplex mode 1341 b10baseFLFD(13), -- 10BASE-FL full duplex mode 1343 b100baseT4(14), -- 100BASE-T4 1344 b100baseTXHD(15), -- 100BASE-TX half duplex mode 1345 b100baseTXFD(16), -- 100BASE-TX full duplex mode 1346 b100baseFXHD(17), -- 100BASE-FX half duplex mode 1347 b100baseFXFD(18), -- 100BASE-FX full duplex mode 1348 b100baseT2HD(19), -- 100BASE-T2 half duplex mode 1349 b100baseT2FD(20), -- 100BASE-T2 full duplex mode 1351 b1000baseXHD(21), -- 1000BASE-X half duplex mode 1352 b1000baseXFD(22), -- 1000BASE-X full duplex mode 1353 b1000baseLXHD(23), -- 1000BASE-LX half duplex mode 1354 b1000baseLXFD(24), -- 1000BASE-LX full duplex mode 1355 b1000baseSXHD(25), -- 1000BASE-SX half duplex mode 1356 b1000baseSXFD(26), -- 1000BASE-SX full duplex mode 1357 b1000baseCXHD(27), -- 1000BASE-CX half duplex mode 1358 b1000baseCXFD(28), -- 1000BASE-CX full duplex mode 1359 b1000baseTHD(29), -- 1000BASE-T half duplex mode 1360 b1000baseTFD(30) -- 1000BASE-T full duplex mode 1361 } 1362 MAX-ACCESS read-only 1363 STATUS current 1364 DESCRIPTION "A value that uniquely identifies the set of 1365 possible IEEE 802.3 types that the MAU could be. 1366 If auto-negotiation is present on this MAU, this 1367 object will map to ifMauAutoNegCapability." 1368 ::= { ifMauEntry 13 } 1370 -- The ifJackTable applies to MAUs attached to interfaces 1371 -- which have one or more external jacks (connectors). 1373 ifJackTable OBJECT-TYPE 1374 SYNTAX SEQUENCE OF IfJackEntry 1375 MAX-ACCESS not-accessible 1376 STATUS current 1377 DESCRIPTION "Information about the external jacks attached 1378 to MAUs attached to an interface." 1379 ::= { dot3IfMauBasicGroup 2 } 1381 ifJackEntry OBJECT-TYPE 1382 SYNTAX IfJackEntry 1383 MAX-ACCESS not-accessible 1384 STATUS current 1385 DESCRIPTION "An entry in the table, containing information 1386 about a particular jack." 1387 INDEX { ifMauIfIndex, 1388 ifMauIndex, 1389 ifJackIndex 1390 } 1391 ::= { ifJackTable 1 } 1393 IfJackEntry ::= 1394 SEQUENCE { 1395 ifJackIndex Integer32, 1396 ifJackType JackType 1397 } 1399 ifJackIndex OBJECT-TYPE 1400 SYNTAX Integer32 (1..2147483647) 1401 MAX-ACCESS not-accessible 1402 STATUS current 1403 DESCRIPTION "This variable uniquely identifies the jack 1404 described by this entry from among other jacks 1405 attached to the same MAU." 1406 ::= { ifJackEntry 1 } 1408 ifJackType OBJECT-TYPE 1409 SYNTAX JackType 1410 MAX-ACCESS read-only 1411 STATUS current 1412 DESCRIPTION "The jack connector type, as it appears on the 1413 outside of the system." 1414 ::= { ifJackEntry 2 } 1416 -- The ifMauAutoNegTable applies to systems in which 1417 -- auto-negotiation is supported on one or more MAUs 1418 -- attached to interfaces. Note that if auto-negotiation 1419 -- is present and enabled, the ifMauType object reflects 1420 -- the result of the auto-negotiation function. 1422 ifMauAutoNegTable OBJECT-TYPE 1423 SYNTAX SEQUENCE OF IfMauAutoNegEntry 1424 MAX-ACCESS not-accessible 1425 STATUS current 1426 DESCRIPTION "Configuration and status objects for the 1427 auto-negotiation function of MAUs attached to 1428 interfaces." 1429 ::= { dot3IfMauAutoNegGroup 1 } 1431 ifMauAutoNegEntry OBJECT-TYPE 1432 SYNTAX IfMauAutoNegEntry 1433 MAX-ACCESS not-accessible 1434 STATUS current 1435 DESCRIPTION "An entry in the table, containing configuration 1436 and status information for the auto-negotiation 1437 function of a particular MAU." 1438 INDEX { ifMauIfIndex, 1439 ifMauIndex 1440 } 1441 ::= { ifMauAutoNegTable 1 } 1443 IfMauAutoNegEntry ::= 1444 SEQUENCE { 1445 ifMauAutoNegAdminStatus INTEGER, 1446 ifMauAutoNegRemoteSignaling INTEGER, 1447 ifMauAutoNegConfig INTEGER, 1448 ifMauAutoNegCapability Integer32, 1449 ifMauAutoNegCapAdvertised Integer32, 1450 ifMauAutoNegCapReceived Integer32, 1451 ifMauAutoNegRestart INTEGER, 1452 ifMauAutoNegCapabilityBits BITS, 1453 ifMauAutoNegCapAdvertisedBits BITS, 1454 ifMauAutoNegCapReceivedBits BITS, 1455 ifMauAutoNegRemoteFaultAdvertised INTEGER, 1456 ifMauAutoNegRemoteFaultReceived INTEGER 1457 } 1459 ifMauAutoNegAdminStatus OBJECT-TYPE 1460 SYNTAX INTEGER { 1461 enabled(1), 1462 disabled(2) 1463 } 1464 MAX-ACCESS read-write 1465 STATUS current 1466 DESCRIPTION "Setting this object to enabled(1) will cause 1467 the interface which has the auto-negotiation 1468 signaling ability to be enabled. 1470 If the value of this object is disabled(2) then 1471 the interface will act as it would if it had no 1472 auto-negotiation signaling. Under these 1473 conditions, an IEEE 802.3 MAU will immediately 1474 be forced to the state indicated by the value of 1475 the object ifMauDefaultType. 1477 NOTE TO IMPLEMENTORS: When 1478 ifMauAutoNegAdminStatus transitions from enabled 1479 to disabled, the agent implementation MUST 1480 ensure that the operational type of the MAU (as 1481 reported by ifMauType) correctly transitions to 1482 the value specified by the ifMauDefaultType 1483 object, rather than continuing to operate at the 1484 value earlier determined by the auto-negotiation 1485 function." 1486 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.2, 1487 aAutoNegAdminState and 30.6.1.2.2, 1488 acAutoNegAdminControl." 1489 ::= { ifMauAutoNegEntry 1 } 1491 ifMauAutoNegRemoteSignaling OBJECT-TYPE 1492 SYNTAX INTEGER { 1493 detected(1), 1494 notdetected(2) 1495 } 1496 MAX-ACCESS read-only 1497 STATUS current 1498 DESCRIPTION "A value indicating whether the remote end of 1499 the link is using auto-negotiation signaling. It 1500 takes the value detected(1) if and only if, 1501 during the previous link negotiation, FLP Bursts 1502 were received." 1503 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.3, 1504 aAutoNegRemoteSignaling." 1505 ::= { ifMauAutoNegEntry 2 } 1507 ifMauAutoNegConfig OBJECT-TYPE 1508 SYNTAX INTEGER { 1509 other(1), 1510 configuring(2), 1511 complete(3), 1512 disabled(4), 1513 parallelDetectFail(5) 1514 } 1515 MAX-ACCESS read-only 1516 STATUS current 1517 DESCRIPTION "A value indicating the current status of the 1518 auto-negotiation process. The enumeration 1519 parallelDetectFail(5) maps to a failure in 1520 parallel detection as defined in 28.2.3.1 of 1521 [IEEE 802.3 Std]." 1522 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4, 1523 aAutoNegAutoConfig." 1524 ::= { ifMauAutoNegEntry 4 } 1526 ifMauAutoNegCapability OBJECT-TYPE 1527 SYNTAX Integer32 1528 MAX-ACCESS read-only 1529 STATUS deprecated 1530 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1532 A value that uniquely identifies the set of 1533 capabilities of the local auto-negotiation 1534 entity. The value is a sum which initially 1535 takes the value zero. Then, for each capability 1536 of this interface, 2 raised to the power noted 1537 below is added to the sum. For example, an 1538 interface which has the capability to support 1539 only 100Base-TX half duplex would have a value 1540 of 32768 (2**15). In contrast, an interface 1541 which supports both 100Base-TX half duplex and 1542 and 100Base-TX full duplex would have a value of 1543 98304 ((2**15) + (2**16)). 1545 The powers of 2 assigned to the capabilities are 1546 these: 1548 Power Capability 1549 0 other or unknown 1550 (1-9) (reserved) 1551 10 10BASE-T half duplex mode 1552 11 10BASE-T full duplex mode 1553 12 (reserved) 1554 13 (reserved) 1555 14 100BASE-T4 1556 15 100BASE-TX half duplex mode 1557 16 100BASE-TX full duplex mode 1558 17 (reserved) 1559 18 (reserved) 1560 19 100BASE-T2 half duplex mode 1561 20 100BASE-T2 full duplex mode 1563 Note that interfaces that support this MIB may 1564 have capabilities that extend beyond the scope 1565 of this MIB. 1567 This object has been deprecated in favour of 1568 ifMauAutoNegCapabilityBits" 1569 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, 1570 aAutoNegLocalTechnologyAbility." 1571 ::= { ifMauAutoNegEntry 5 } 1573 ifMauAutoNegCapAdvertised OBJECT-TYPE 1574 SYNTAX Integer32 1575 MAX-ACCESS read-write 1576 STATUS deprecated 1577 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1579 A value that uniquely identifies the set of 1580 capabilities advertised by the local 1581 auto-negotiation entity. Refer to 1582 ifMauAutoNegCapability for a description of the 1583 possible values of this object. 1585 Capabilities in this object that are not 1586 available in ifMauAutoNegCapability cannot be 1587 enabled. 1589 This object has been deprecated in favour of 1590 ifMauAutoNegCapAdvertisedBits" 1591 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 1592 aAutoNegAdvertisedTechnologyAbility." 1593 ::= { ifMauAutoNegEntry 6 } 1595 ifMauAutoNegCapReceived OBJECT-TYPE 1596 SYNTAX Integer32 1597 MAX-ACCESS read-only 1598 STATUS deprecated 1599 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1601 A value that uniquely identifies the set of 1602 capabilities received from the remote 1603 auto-negotiation entity. Refer to 1604 ifMauAutoNegCapability for a description of the 1605 possible values of this object. 1607 Note that interfaces that support this MIB may 1608 be attached to remote auto-negotiation entities 1609 which have capabilities beyond the scope of this 1610 MIB. 1612 This object has been deprecated in favour of 1613 ifMauAutoNegCapReceivedBits" 1614 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 1615 aAutoNegReceivedTechnologyAbility." 1616 ::= { ifMauAutoNegEntry 7 } 1618 ifMauAutoNegRestart OBJECT-TYPE 1619 SYNTAX INTEGER { 1620 restart(1), 1621 norestart(2) 1623 } 1624 MAX-ACCESS read-write 1625 STATUS current 1626 DESCRIPTION "If the value of this object is set to 1627 restart(1) then this will force auto-negotiation 1628 to begin link renegotiation. If auto-negotiation 1629 signaling is disabled, a write to this object 1630 has no effect. 1632 Setting the value of this object to norestart(2) 1633 has no effect." 1634 REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1, 1635 acAutoNegRestartAutoConfig." 1636 ::= { ifMauAutoNegEntry 8 } 1638 ifMauAutoNegCapabilityBits OBJECT-TYPE 1639 SYNTAX BITS { 1640 bOther(0), -- other or unknown 1641 b10baseT(1), -- 10BASE-T half duplex mode 1642 b10baseTFD(2), -- 10BASE-T full duplex mode 1643 b100baseT4(3), -- 100BASE-T4 1644 b100baseTX(4), -- 100BASE-TX half duplex mode 1645 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1646 b100baseT2(6), -- 100BASE-T2 half duplex mode 1647 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1648 bfdxPause(8), -- PAUSE for full-duplex links 1649 bfdxAPause(9), -- Asymmetric PAUSE for full-duplex 1650 -- links 1651 bfdxSPause(10), -- Symmetric PAUSE for full-duplex 1652 -- links 1653 bfdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1654 -- full-duplex links 1655 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1656 -- duplex mode 1657 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1658 -- duplex mode 1659 b1000baseT(14), -- 1000BASE-T half duplex mode 1660 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1661 } 1662 MAX-ACCESS read-only 1663 STATUS current 1664 DESCRIPTION "A value that uniquely identifies the set of 1665 capabilities of the local auto-negotiation 1666 entity. Note that interfaces that support this 1667 MIB may have capabilities that extend beyond the 1668 scope of this MIB." 1669 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, 1670 aAutoNegLocalTechnologyAbility." 1672 ::= { ifMauAutoNegEntry 9 } 1674 ifMauAutoNegCapAdvertisedBits OBJECT-TYPE 1675 SYNTAX BITS { 1676 bOther(0), -- other or unknown 1677 b10baseT(1), -- 10BASE-T half duplex mode 1678 b10baseTFD(2), -- 10BASE-T full duplex mode 1679 b100baseT4(3), -- 100BASE-T4 1680 b100baseTX(4), -- 100BASE-TX half duplex mode 1681 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1682 b100baseT2(6), -- 100BASE-T2 half duplex mode 1683 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1684 bFdxPause(8), -- PAUSE for full-duplex links 1685 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 1686 -- links 1687 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 1688 -- links 1689 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1690 -- full-duplex links 1691 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1692 -- duplex mode 1693 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1694 -- duplex mode 1695 b1000baseT(14), -- 1000BASE-T half duplex mode 1696 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1697 } 1698 MAX-ACCESS read-write 1699 STATUS current 1700 DESCRIPTION "A value that uniquely identifies the set of 1701 capabilities advertised by the local 1702 auto-negotiation entity. 1704 Capabilities in this object that are not 1705 available in ifMauAutoNegCapability cannot be 1706 enabled." 1707 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 1708 aAutoNegAdvertisedTechnologyAbility." 1709 ::= { ifMauAutoNegEntry 10 } 1711 ifMauAutoNegCapReceivedBits OBJECT-TYPE 1712 SYNTAX BITS { 1713 bOther(0), -- other or unknown 1714 b10baseT(1), -- 10BASE-T half duplex mode 1715 b10baseTFD(2), -- 10BASE-T full duplex mode 1716 b100baseT4(3), -- 100BASE-T4 1717 b100baseTX(4), -- 100BASE-TX half duplex mode 1718 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1719 b100baseT2(6), -- 100BASE-T2 half duplex mode 1720 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1721 bFdxPause(8), -- PAUSE for full-duplex links 1722 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 1723 -- links 1724 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 1725 -- links 1726 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1727 -- full-duplex links 1728 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1729 -- duplex mode 1730 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1731 -- duplex mode 1732 b1000baseT(14), -- 1000BASE-T half duplex mode 1733 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1734 } 1735 MAX-ACCESS read-only 1736 STATUS current 1737 DESCRIPTION "A value that uniquely identifies the set of 1738 capabilities received from the remote 1739 auto-negotiation entity. 1741 Note that interfaces that support this MIB may 1742 be attached to remote auto-negotiation entities 1743 which have capabilities beyond the scope of this 1744 MIB." 1745 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 1746 aAutoNegReceivedTechnologyAbility." 1747 ::= { ifMauAutoNegEntry 11 } 1749 ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE 1750 SYNTAX INTEGER { 1751 noError(1), 1752 offline(2), 1753 linkFailure(3), 1754 autoNegError(4) 1755 } 1756 MAX-ACCESS read-write 1757 STATUS current 1758 DESCRIPTION "A value that identifies any local fault 1759 indications that this MAU has detected and will 1760 advertise at the next auto-negotiation 1761 interaction for 1000Mbps MAUs." 1762 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 1763 aAutoNegAdvertisedTechnologyAbility." 1764 ::= { ifMauAutoNegEntry 12 } 1766 ifMauAutoNegRemoteFaultReceived OBJECT-TYPE 1767 SYNTAX INTEGER { 1768 noError(1), 1769 offline(2), 1770 linkFailure(3), 1771 autoNegError(4) 1772 } 1773 MAX-ACCESS read-only 1774 STATUS current 1775 DESCRIPTION "A value that identifies any fault indications 1776 received from the far end of a link by the 1777 local auto-negotiation entity for 1000Mbps 1778 MAUs." 1779 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 1780 aAutoNegReceivedTechnologyAbility." 1781 ::= { ifMauAutoNegEntry 13 } 1783 -- 1784 -- The Basic Broadband MAU Table 1785 -- 1787 broadMauBasicTable OBJECT-TYPE 1788 SYNTAX SEQUENCE OF BroadMauBasicEntry 1789 MAX-ACCESS not-accessible 1790 STATUS deprecated 1791 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1793 Table of descriptive and status information 1794 about the broadband MAUs connected to 1795 interfaces." 1796 ::= { dot3BroadMauBasicGroup 1 } 1798 broadMauBasicEntry OBJECT-TYPE 1799 SYNTAX BroadMauBasicEntry 1800 MAX-ACCESS not-accessible 1801 STATUS deprecated 1802 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1804 An entry in the table, containing information 1805 about a single broadband MAU." 1806 INDEX { broadMauIfIndex, 1807 broadMauIndex 1808 } 1809 ::= { broadMauBasicTable 1 } 1811 BroadMauBasicEntry ::= 1812 SEQUENCE { 1813 broadMauIfIndex Integer32, 1814 broadMauIndex Integer32, 1815 broadMauXmtRcvSplitType INTEGER, 1816 broadMauXmtCarrierFreq Integer32, 1817 broadMauTranslationFreq Integer32 1818 } 1820 broadMauIfIndex OBJECT-TYPE 1821 SYNTAX Integer32 (1..2147483647) 1822 MAX-ACCESS read-only 1823 STATUS deprecated 1824 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1826 This variable uniquely identifies the interface 1827 to which the MAU described by this entry is 1828 connected." 1829 REFERENCE "Reference RFC 1213, ifIndex." 1830 ::= { broadMauBasicEntry 1 } 1832 broadMauIndex OBJECT-TYPE 1833 SYNTAX Integer32 (1..2147483647) 1834 MAX-ACCESS read-only 1835 STATUS deprecated 1836 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1838 This variable uniquely identifies the MAU 1839 connected to interface broadMauIfIndex that is 1840 described by this entry." 1841 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 1842 ::= { broadMauBasicEntry 2 } 1844 broadMauXmtRcvSplitType OBJECT-TYPE 1845 SYNTAX INTEGER { 1846 other(1), 1847 single(2), 1848 dual(3) 1849 } 1850 MAX-ACCESS read-only 1851 STATUS deprecated 1852 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1854 This object indicates the type of frequency 1855 multiplexing/cabling system used to separate the 1856 transmit and receive paths for the 10BROAD36 1857 MAU. 1859 The value other(1) is returned if the split type 1860 is not either single or dual. 1862 The value single(2) indicates a single cable 1863 system. The value dual(3) indicates a dual 1864 cable system, offset normally zero." 1865 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.8, 1866 aBbMAUXmitRcvSplitType." 1867 ::= { broadMauBasicEntry 3 } 1869 broadMauXmtCarrierFreq OBJECT-TYPE 1870 SYNTAX Integer32 1871 MAX-ACCESS read-only 1872 STATUS deprecated 1873 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1875 This variable indicates the transmit carrier 1876 frequency of the 10BROAD36 MAU in MHz/4; that 1877 is, in units of 250 kHz." 1878 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, 1879 aBroadbandFrequencies.xmitCarrierFrequency." 1880 ::= { broadMauBasicEntry 4 } 1882 broadMauTranslationFreq OBJECT-TYPE 1883 SYNTAX Integer32 1884 MAX-ACCESS read-only 1885 STATUS deprecated 1886 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1888 This variable indicates the translation offset 1889 frequency of the 10BROAD36 MAU in MHz/4; that 1890 is, in units of 250 kHz." 1891 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, 1892 aBroadbandFrequencies.translationFrequency." 1893 ::= { broadMauBasicEntry 5 } 1895 -- Notifications for use by 802.3 MAUs 1897 snmpDot3MauTraps OBJECT IDENTIFIER ::= { snmpDot3MauMgt 0 } 1899 rpMauJabberTrap NOTIFICATION-TYPE 1900 OBJECTS { rpMauJabberState } 1901 STATUS current 1902 DESCRIPTION "This trap is sent whenever a managed repeater 1903 MAU enters the jabber state. 1905 The agent MUST throttle the generation of 1906 consecutive rpMauJabberTraps so that there is at 1907 least a five-second gap between them." 1908 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1909 notification." 1910 ::= { snmpDot3MauTraps 1 } 1912 ifMauJabberTrap NOTIFICATION-TYPE 1913 OBJECTS { ifMauJabberState } 1914 STATUS current 1915 DESCRIPTION "This trap is sent whenever a managed interface 1916 MAU enters the jabber state. 1918 The agent MUST throttle the generation of 1919 consecutive ifMauJabberTraps so that there is at 1920 least a five-second gap between them." 1921 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1922 notification." 1923 ::= { snmpDot3MauTraps 2 } 1925 -- Conformance information 1927 mauModConf 1928 OBJECT IDENTIFIER ::= { mauMod 1 } 1929 mauModCompls 1930 OBJECT IDENTIFIER ::= { mauModConf 1 } 1931 mauModObjGrps 1932 OBJECT IDENTIFIER ::= { mauModConf 2 } 1933 mauModNotGrps 1934 OBJECT IDENTIFIER ::= { mauModConf 3 } 1936 -- Object groups 1938 mauRpGrpBasic OBJECT-GROUP 1939 OBJECTS { rpMauGroupIndex, 1940 rpMauPortIndex, 1941 rpMauIndex, 1942 rpMauType, 1943 rpMauStatus, 1944 rpMauMediaAvailable, 1945 rpMauMediaAvailableStateExits, 1946 rpMauJabberState, 1947 rpMauJabberingStateEnters 1948 } 1949 STATUS current 1950 DESCRIPTION "Basic conformance group for MAUs attached to 1951 repeater ports. This group is also the 1952 conformance specification for RFC 1515 1953 implementations." 1954 ::= { mauModObjGrps 1 } 1956 mauRpGrp100Mbs OBJECT-GROUP 1957 OBJECTS { rpMauFalseCarriers } 1958 STATUS current 1959 DESCRIPTION "Conformance group for MAUs attached to 1960 repeater ports with 100 Mb/s or greater 1961 capability." 1962 ::= { mauModObjGrps 2 } 1964 mauRpGrpJack OBJECT-GROUP 1965 OBJECTS { rpJackType } 1966 STATUS current 1967 DESCRIPTION "Conformance group for MAUs attached to 1968 repeater ports with managed jacks." 1969 ::= { mauModObjGrps 3 } 1971 mauIfGrpBasic OBJECT-GROUP 1972 OBJECTS { ifMauIfIndex, 1973 ifMauIndex, 1974 ifMauType, 1975 ifMauStatus, 1976 ifMauMediaAvailable, 1977 ifMauMediaAvailableStateExits, 1978 ifMauJabberState, 1979 ifMauJabberingStateEnters 1980 } 1981 STATUS current 1982 DESCRIPTION "Basic conformance group for MAUs attached to 1983 interfaces. This group also provides a 1984 conformance specification for RFC 1515 1985 implementations." 1986 ::= { mauModObjGrps 4 } 1988 mauIfGrp100Mbs OBJECT-GROUP 1989 OBJECTS { ifMauFalseCarriers, 1990 ifMauTypeList, 1991 ifMauDefaultType, 1992 ifMauAutoNegSupported 1993 } 1994 STATUS deprecated 1995 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 1997 Conformance group for MAUs attached to 1998 interfaces with 100 Mb/s capability. 2000 This object group has been deprecated in favor 2001 of mauIfGrpHighCapacity." 2002 ::= { mauModObjGrps 5 } 2004 mauIfGrpJack OBJECT-GROUP 2005 OBJECTS { ifJackType } 2006 STATUS current 2007 DESCRIPTION "Conformance group for MAUs attached to 2008 interfaces with managed jacks." 2009 ::= { mauModObjGrps 6 } 2011 mauIfGrpAutoNeg OBJECT-GROUP 2012 OBJECTS { ifMauAutoNegAdminStatus, 2013 ifMauAutoNegRemoteSignaling, 2014 ifMauAutoNegConfig, 2015 ifMauAutoNegCapability, 2016 ifMauAutoNegCapAdvertised, 2017 ifMauAutoNegCapReceived, 2018 ifMauAutoNegRestart 2019 } 2020 STATUS deprecated 2021 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2023 Conformance group for MAUs attached to 2024 interfaces with managed auto-negotiation. 2026 This object group has been deprecated in favor 2027 of mauIfGrpAutoNeg2." 2028 ::= { mauModObjGrps 7 } 2030 mauBroadBasic OBJECT-GROUP 2031 OBJECTS { broadMauIfIndex, 2032 broadMauIndex, 2033 broadMauXmtRcvSplitType, 2034 broadMauXmtCarrierFreq, 2035 broadMauTranslationFreq 2036 } 2037 STATUS deprecated 2038 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2040 Conformance group for broadband MAUs attached 2041 to interfaces. 2043 This object group is deprecated. There have 2044 been no reported implementations of this group, 2045 and it was felt to be unlikely that there will 2046 be any future implementations." 2047 ::= { mauModObjGrps 8 } 2049 mauIfGrpHighCapacity OBJECT-GROUP 2050 OBJECTS { ifMauFalseCarriers, 2051 ifMauTypeListBits, 2052 ifMauDefaultType, 2053 ifMauAutoNegSupported 2054 } 2055 STATUS current 2056 DESCRIPTION "Conformance group for MAUs attached to 2057 interfaces with 100 Mb/s or greater capability." 2058 ::= { mauModObjGrps 9 } 2060 mauIfGrpAutoNeg2 OBJECT-GROUP 2061 OBJECTS { ifMauAutoNegAdminStatus, 2062 ifMauAutoNegRemoteSignaling, 2063 ifMauAutoNegConfig, 2064 ifMauAutoNegCapabilityBits, 2065 ifMauAutoNegCapAdvertisedBits, 2066 ifMauAutoNegCapReceivedBits, 2067 ifMauAutoNegRestart 2068 } 2069 STATUS current 2070 DESCRIPTION "Conformance group for MAUs attached to 2071 interfaces with managed auto-negotiation." 2072 ::= { mauModObjGrps 10 } 2074 mauIfGrpAutoNeg1000Mbps OBJECT-GROUP 2075 OBJECTS { ifMauAutoNegRemoteFaultAdvertised, 2076 ifMauAutoNegRemoteFaultReceived 2077 } 2078 STATUS current 2079 DESCRIPTION "Conformance group for 1000Mbps MAUs attached to 2080 interfaces with managed auto-negotiation." 2081 ::= { mauModObjGrps 11 } 2083 -- Notification groups 2085 rpMauNotifications NOTIFICATION-GROUP 2086 NOTIFICATIONS { rpMauJabberTrap } 2087 STATUS current 2088 DESCRIPTION "Notifications for repeater MAUs." 2089 ::= { mauModNotGrps 1 } 2091 ifMauNotifications NOTIFICATION-GROUP 2092 NOTIFICATIONS { ifMauJabberTrap } 2093 STATUS current 2094 DESCRIPTION "Notifications for interface MAUs." 2095 ::= { mauModNotGrps 2 } 2097 -- Compliances 2098 mauModRpCompl MODULE-COMPLIANCE 2099 STATUS deprecated 2100 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2102 Compliance for MAUs attached to repeater 2103 ports. 2105 This compliance is deprecated and replaced by 2106 mauModRpCompl2, which corrects an oversight by 2107 allowing rpMauStatus to be implemented 2108 read-only." 2110 MODULE -- this module 2111 MANDATORY-GROUPS { mauRpGrpBasic } 2113 GROUP mauRpGrp100Mbs 2114 DESCRIPTION "Implementation of this optional group is 2115 recommended for MAUs which have 100Mb/s or 2116 greater capability." 2118 GROUP mauRpGrpJack 2119 DESCRIPTION "Implementation of this optional group is 2120 recommended for MAUs which have one or more 2121 external jacks." 2123 GROUP rpMauNotifications 2124 DESCRIPTION "Implementation of this group is recommended 2125 for MAUs attached to repeater ports." 2126 ::= { mauModCompls 1 } 2128 mauModIfCompl MODULE-COMPLIANCE 2129 STATUS deprecated 2130 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2132 Compliance for MAUs attached to interfaces. 2134 This compliance is deprecated and replaced by 2135 mauModIfCompl2." 2137 MODULE -- this module 2138 MANDATORY-GROUPS { mauIfGrpBasic } 2140 GROUP mauIfGrp100Mbs 2141 DESCRIPTION "Implementation of this optional group is 2142 recommended for MAUs which have 100Mb/s 2143 capability." 2145 GROUP mauIfGrpJack 2146 DESCRIPTION "Implementation of this optional group is 2147 recommended for MAUs which have one or more 2148 external jacks." 2150 GROUP mauIfGrpAutoNeg 2151 DESCRIPTION "Implementation of this group is mandatory 2152 for MAUs which support managed 2153 auto-negotiation." 2155 GROUP mauBroadBasic 2156 DESCRIPTION "Implementation of this group is mandatory 2157 for broadband MAUs." 2159 GROUP ifMauNotifications 2160 DESCRIPTION "Implementation of this group is recommended 2161 for MAUs attached to interfaces." 2162 ::= { mauModCompls 2 } 2164 mauModIfCompl2 MODULE-COMPLIANCE 2165 STATUS current 2166 DESCRIPTION "Compliance for MAUs attached to interfaces." 2168 MODULE -- this module 2169 MANDATORY-GROUPS { mauIfGrpBasic } 2171 GROUP mauIfGrpHighCapacity 2172 DESCRIPTION "Implementation of this optional group is 2173 recommended for MAUs which have 100Mb/s 2174 or greater capability." 2176 GROUP mauIfGrpJack 2177 DESCRIPTION "Implementation of this optional group is 2178 recommended for MAUs which have one or more 2179 external jacks." 2181 GROUP mauIfGrpAutoNeg2 2182 DESCRIPTION "Implementation of this group is mandatory 2183 for MAUs which support managed 2184 auto-negotiation." 2186 GROUP mauIfGrpAutoNeg1000Mbps 2187 DESCRIPTION "Implementation of this group is mandatory 2188 for MAUs which have 1000Mb/s or greater 2189 capability and support managed 2190 auto-negotiation." 2192 GROUP ifMauNotifications 2193 DESCRIPTION "Implementation of this group is recommended 2194 for MAUs attached to interfaces." 2196 OBJECT ifMauStatus 2197 MIN-ACCESS read-only 2198 DESCRIPTION "Write access is not required." 2199 ::= { mauModCompls 3 } 2201 mauModRpCompl2 MODULE-COMPLIANCE 2202 STATUS current 2203 DESCRIPTION "Compliance for MAUs attached to repeater 2204 ports." 2206 MODULE -- this module 2207 MANDATORY-GROUPS { mauRpGrpBasic } 2209 GROUP mauRpGrp100Mbs 2210 DESCRIPTION "Implementation of this optional group is 2211 recommended for MAUs which have 100Mb/s or 2212 greater capability." 2214 GROUP mauRpGrpJack 2215 DESCRIPTION "Implementation of this optional group is 2216 recommended for MAUs which have one or more 2217 external jacks." 2219 GROUP rpMauNotifications 2220 DESCRIPTION "Implementation of this group is recommended 2221 for MAUs attached to repeater ports." 2223 OBJECT rpMauStatus 2224 MIN-ACCESS read-only 2225 DESCRIPTION "Write access is not required." 2226 ::= { mauModCompls 4 } 2228 END 2230 5. Intellectual Property 2232 The IETF takes no position regarding the validity or scope of any 2233 intellectual property or other rights that might be claimed to 2234 pertain to the implementation or use of the technology described in 2235 this document or the extent to which any license under such rights 2236 might or might not be available; neither does it represent that it 2237 has made any effort to identify any such rights. Information on the 2238 IETF's procedures with respect to rights in standards-track and 2239 standards-related documentation can be found in BCP-11. Copies of 2240 claims of rights made available for publication and any assurances of 2241 licenses to be made available, or the result of an attempt made to 2242 obtain a general license or permission for the use of such 2243 proprietary rights by implementors or users of this specification can 2244 be obtained from the IETF Secretariat. 2246 The IETF invites any interested party to bring to its attention any 2247 copyrights, patents or patent applications, or other proprietary 2248 rights which may cover technology that may be required to practice 2249 this standard. Please address the information to the IETF Executive 2250 Director. 2252 6. Acknowledgements 2254 This document was produced by the IETF Ethernet Interfaces and Hub 2255 MIB Working Group, whose efforts were greatly advanced by the 2256 contributions of the following people: 2258 Chuck Black 2259 John Flick 2260 Jeff Johnson 2261 Leon Leong 2262 Mike Lui 2263 Dave Perkins 2264 Geoff Thompson 2265 Maurice Turcotte 2266 Paul Woodruff 2268 Special thanks as well to Dave Perkins for his excellent work on the 2269 SMICng compiler, which made it easy to take advantage of the latest 2270 SNMPv2 constructs in this MIB. 2272 7. References 2274 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 2275 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2276 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 2277 January 1998 2279 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 2280 Management Information for TCP/IP-based Internets", STD 16, 2281 RFC 1155, Performance Systems International, Hughes LAN Systems, 2282 May 1990 2284 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, 2285 RFC 1212, Performance Systems International, Hughes LAN Systems, 2286 March 1991 2288 [4] M. Rose, "A Convention for Defining Traps for use with the 2289 SNMP", RFC 1215, Performance Systems International, March 1991 2291 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2292 "Structure of Management Information for Version 2 of the Simple 2293 Network Management Protocol (SNMPv2)", RFC 1902, SNMP Research, 2294 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 2295 International Network Services, January 1996. 2297 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 2298 Conventions for Version 2 of the Simple Network Management 2299 Protocol (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco 2300 Systems, Inc., Dover Beach Consulting, Inc., International 2301 Network Services, January 1996. 2303 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2304 "Conformance Statements for Version 2 of the Simple Network 2305 Management Protocol (SNMPv2)", RFC 1904, SNMP Research, Inc., 2306 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 2307 Network Services, January 1996. 2309 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 2310 Network Management Protocol", STD 15, RFC 1157, SNMP Research, 2311 Performance Systems International, Performance Systems 2312 International, MIT Laboratory for Computer Science, May 1990. 2314 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2315 "Introduction to Community-based SNMPv2", RFC 1901, SNMP 2316 Research, Inc., Cisco Systems, Inc., Dover Beach Consulting, 2317 Inc., International Network Services, January 1996. 2319 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 2320 "Transport Mappings for Version 2 of the Simple Network 2321 Management Protocol (SNMPv2)", RFC 1906, SNMP Research, Inc., 2322 Cisco Systems, Inc., Dover Beach Consulting, Inc., International 2323 Network Services, January 1996. 2325 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 2326 Processing and Dispatching for the Simple Network Management 2327 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron 2328 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 2329 January 1998. 2331 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 2332 for version 3 of the Simple Network Management Protocol 2333 (SNMPv3)", RFC 2274, IBM T. J. Watson Research, January 1998. 2335 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 2336 Operations for Version 2 of the Simple Network Management 2337 Protocol (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco 2338 Systems, Inc., Dover Beach Consulting, Inc., International 2339 Network Services, January 1996. 2341 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 2342 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 2343 Systems, January 1998 2345 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 2346 Control Model (VACM) for the Simple Network Management Protocol 2347 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, 2348 Inc., Cisco Systems, Inc., January 1998 2350 [16] IEEE, IEEE Std 802.3, 1998 Edition: "Information technology - 2351 Telecommunications and information exchange between systems - 2352 Local and metropolitan area networks - Specific requirements - 2353 Part 3: Carrier sense multiple access with collision detection 2354 (CSMA/CD) access method and physical layer specifications" 2355 (incorporating ANSI/IEEE Std. 802.3, 1996 Edition, IEEE Std. 2356 802.3r-1996, 802.3u-1995, 802.3x&y-1997, 802.3z-1998, and 2357 802.3aa-1998), September 1998. 2359 [17] de Graaf, K., D. Romascanu, D. McMaster, and K. McCloghrie, 2360 "Definitions of Managed Objects for IEEE 802.3 Repeater Devices 2361 using SMIv2", RFC 2108, 3Com Corporation, Madge Networks 2362 (Israel) Ltd., Coloma Communications, Cisco Systems, Inc., 2363 February 1997. 2365 [18] McCloghrie, K., and M. Rose, Editors, "Management Information 2366 Base for Network Management of TCP/IP-based internets: MIB-II", 2367 STD 17, RFC 1213, Hughes LAN Systems, Performance Systems 2368 International, March 1991. 2370 [19] McCloghrie, K., and Kastenholtz, F., "The Interfaces Group MIB 2371 using SMIv2", RFC 2233, Cisco Systems, FTP Software, November 2372 1997. 2374 [20] Bradner, S., "Key words for use in RFCs to Indicate 2375 Requirements Levels", BCP 14, RFC 2119, March 1997. 2377 [21] de Graaf, K., Romascanu, D., McMaster, D., K. McCloghrie, 2378 S. Roberts, "Definitions of Managed Objects 2379 for IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", 2380 RFC 2239, 3Com Corporation, Madge Networks Ltd., Cisco Systems 2381 Inc., Cisco Systems Inc., Farallon Computing, Inc., 2382 November 1997. 2384 [22] McMaster, D., K. McCloghrie and S. Roberts, "Definitions of 2385 Managed Objects for IEEE 802.3 Medium Attachment Units 2386 (MAUs)", RFC 1515, SynOptics Communications, Inc., Hughes LAN 2387 Systems, Inc., Farallon Computing, Inc., September 1993. 2389 [23] Flick, J., and J. Johnson, "Definitions of Managed Objects for 2390 the Ethernet-like Interface Types", work in progress, 2391 draft-ietf-hubmib-etherif-mib-v2-02.txt, Hewlett-Packard 2392 Company, RedBack Networks, January, 1999. 2394 8. Security Considerations 2396 There are a number of management objects defined in this MIB that 2397 have a MAX-ACCESS clause of read-write. Setting these objects can 2398 have a serious effect on the operation of the network, including: 2400 enabling or disabling a MAU 2401 changing a MAU's default type 2402 enabling, disabling or restarting autonegotiation 2403 modifying the capabilities that a MAU advertizes during 2404 autonegotiation. 2406 Such objects may be considered sensitive or vulnerable in some 2407 network environments. The support for SET operations in a non-secure 2408 environment without proper protection can have a negative effect on 2409 network operations. 2411 SNMPv1 by itself is such an insecure environment. Even if the 2412 network itself is secure (for example by using IPSec), even then, 2413 there is no control as to who on the secure network is allowed to 2414 access and GET/SET (read/change/create/delete) the objects in this 2415 MIB. 2417 It is recommended that the implementers consider the security 2418 features as provided by the SNMPv3 framework. Specifically, the use 2419 of the User-based Security Model RFC 2274 [12] and the View-based 2420 Access Control Model RFC 2275 [15] is recommended. 2422 It is then a customer/user responsibility to ensure that the SNMP 2423 entity giving access to an instance of this MIB, is properly 2424 configured to give access to those objects only to those principals 2425 (users) that have legitimate rights to access them. 2427 9. Authors' Addresses 2429 Andrew Smith 2430 Extreme Networks, Inc. 2431 10460 Bandley Drive 2432 Cupertino, CA 95014, USA 2433 Tel: +1 408 342 0999 2434 E-Mail: andrew@extremenetworks.com 2436 John Flick 2437 Hewlett-Packard Company 2438 8000 Foothills Blvd. M/S 5557 2439 Roseville, CA 95747-5557 2440 Phone: +1 916 785 4018 2441 E-mail: johnf@rose.hp.com 2443 Kathryn de Graaf 2444 Argon Networks 2445 25 Porter Road 2446 Littleton, MA 01460 USA 2447 Tel: +1 978 486 0665 x163 2448 Fax: +1 978 486 9379 2449 E-mail: kdegraaf@argon.com 2451 Dan Romascanu 2452 Lucent Technologies 2453 Atidim Technology Park, Bldg. 3 2454 Tel Aviv 61131 2455 Israel 2456 Tel: 972 3 645 8414, 6458458 2457 Fax: 972 3 648 7146 2458 E-mail: dromasca@lucent.com 2460 Donna McMaster 2461 Cisco Systems Inc. 2462 170 West Tasman Drive 2463 San Jose, CA 95134 2464 Tel: +1 408 526 5260 2465 E-Mail: mcmaster@cisco.com 2467 Keith McCloghrie 2468 Cisco Systems Inc. 2469 170 West Tasman Drive 2470 San Jose, CA 95134 2471 Tel: +1 408 526 5260 2472 E-Mail: kzm@cisco.com 2474 Sam Roberts 2475 Farallon Computing, Inc. 2476 2470 Mariner Square Loop 2477 Alameda, CA 94501-1010 2478 Tel: +1 510 814 5215 2479 E-Mail: sroberts@farallon.com 2481 A. Change Log 2483 This section enumerates the changes made to RFC 2239 to produce this 2484 document. 2486 (1) The MODULE-IDENTITY has been updated to reflect the changes 2487 in the MIB. 2489 (2) OBJECT-IDENTITY definitions have been added for gigabit MAU 2490 types. 2492 (3) The ifMauTypeList, ifMauAutoNegCapability, 2493 ifMauAutoNegCapAdvertised and ifMauAutoNegCapReceived 2494 objects have been deprecated and replaced by 2495 ifMauTypeListBits, ifMauAutoNegCapabilityBits, 2496 ifMauAutoNegCapAdvertisedBits and 2497 ifMauAutoNegCapReceivedBits. 2499 (4) Two new objects, ifMauAutoNegRemoteFaultAdvertised and 2500 ifMauAutoNegRemoteFaultReceived have been added. 2502 (5) Enumerations for 'offline' and 'autoNegError' have been 2503 added for the rpMauMediaAvailable and ifMauMediaAvailable 2504 objects. 2506 (6) The broadMauBasicTable and mauBroadBasic object group have 2507 been deprecated. 2509 (7) The mauIfGrp100Mbs and mauIfGrpAutoNeg object groups have 2510 been deprecated and replaced by mauIfGrpHighCapacity and 2511 mauIfGrpAutoNeg2. 2513 (8) A new object group, mauIfGrpAutoNeg1000Mbps, has been added. 2515 (9) The mauModIfCompl and mauModRpCompl compliances have been 2516 deprecated and replaced by mauModIfCompl2 and 2517 mauModRpCompl2. 2519 (10) Added section on relationship to RFC 2239. 2521 (11) Updated the SNMP Network Management Framework boilerplate. 2523 (12) Refer to the Interfaces MIB, rather than the interfaces 2524 group of MIB-II. 2526 (13) Updated references to refer to latest edition of IEEE 802.3. 2528 (14) An intellectual property notice was added, as required by 2529 RFC 2026. 2531 B. Full Copyright Statement 2533 This document and translations of it may be copied and furnished to 2534 others, and derivative works that comment on or otherwise explain it 2535 or assist in its implementation may be prepared, copied, published 2536 and distributed, in whole or in part, without restriction of any 2537 kind, provided that the above copyright notice and this paragraph are 2538 included on all such copies and derivative works. However, this 2539 document itself may not be modified in any way, such as by removing 2540 the copyright notice or references to the Internet Society or other 2541 Internet organizations, except as needed for the purpose of 2542 developing Internet standards in which case the procedures for 2543 copyrights defined in the Internet Standards process must be 2544 followed, or as required to translate it into languages other than 2545 English. 2547 The limited permissions granted above are perpetual and will not be 2548 revoked by the Internet Society or its successors or assigns. 2550 This document and the information contained herein is provided on an 2551 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2552 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2553 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2554 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2555 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.