idnits 2.17.1 draft-ietf-hubmib-mau-mib-v3-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: ---------------------------------------------------------------------------- ** 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 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.) == 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 RFC1515, but the header doesn't have an 'Obsoletes:' line to match this. -- The abstract seems to indicate that this document obsoletes RFC2668, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 286 has weird spacing: '...Ability ifMa...' == Line 303 has weird spacing: '...Ability isoe...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 2003) is 7706 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. 'IEEE802.3' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.3ae' == Outdated reference: A later version (-03) exists of draft-ietf-hubmib-etherif-mib-v3-02 -- Obsolete informational reference (is this intentional?): RFC 2668 (Obsoleted by RFC 3636) -- Obsolete informational reference (is this intentional?): RFC 2239 (Obsoleted by RFC 2668) -- Obsolete informational reference (is this intentional?): RFC 1515 (Obsoleted by RFC 3636) == Outdated reference: A later version (-07) exists of draft-ietf-hubmib-wis-mib-04 Summary: 4 errors (**), 0 flaws (~~), 8 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Ethernet Interfaces and Hub MIB Working Group J. Flick 3 INTERNET DRAFT Hewlett-Packard Company 4 March 2003 6 Definitions of Managed Objects for 7 IEEE 802.3 Medium Attachment Units (MAUs) 9 11 Status of this Memo 13 This document is an Internet-Draft and is in full conformance with 14 all provisions of Section 10 of RFC2026. 16 Internet-Drafts are working documents of the Internet Engineering 17 Task Force (IETF), its areas, and its working groups. Note that 18 other groups may also distribute working documents as Internet- 19 Drafts. 21 Internet-Drafts are draft documents valid for a maximum of six months 22 and may be updated, replaced, or obsoleted by other documents at any 23 time. It is inappropriate to use Internet- Drafts as reference 24 material or to cite them other than as "work in progress." 26 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 To view the list Internet-Draft Shadow Directories, see 30 http://www.ietf.org/shadow.html. 32 Copyright Notice 34 Copyright (C) The Internet Society (2002). All Rights Reserved. 36 Abstract 38 This memo defines a portion of the Management Information Base (MIB) 39 for use with network management protocols in the Internet community. 40 In particular, it defines objects for managing IEEE 802.3 Medium 41 Attachment Units (MAUs). 43 This memo obsoletes RFC 2668. This memo extends that specification 44 by including management information useful for the management of 10 45 gigabit per second (Gb/s) MAUs. This memo also obsoletes RFC 1515. 47 Distribution of this memo is unlimited. Please forward comments to 48 hubmib@ietf.org. 50 Table of Contents 52 1. Introduction ............................................... 2 53 2. The Internet-Standard Management Framework ................. 3 54 3. Overview ................................................... 3 55 3.1. Relationship to RFC 2668 ................................. 3 56 3.2. Relationship to RFC 2239 ................................. 4 57 3.3. Relationship to RFC 1515 ................................. 4 58 3.4. Relationship to Other MIBs ............................... 4 59 3.4.1. Relationship to the Interfaces MIB ..................... 4 60 3.4.2. Relationship to the 802.3 Repeater MIB ................. 5 61 3.5. Management of Internal MAUs .............................. 5 62 3.6. Mapping of IEEE 802.3 Managed Objects .................... 6 63 4. Definitions ................................................ 7 64 5. Intellectual Property ...................................... 56 65 6. Acknowledgements ........................................... 56 66 7. Normative References ....................................... 57 67 8. Informative References ..................................... 58 68 9. Security Considerations .................................... 58 69 10. Authors' Addresses ........................................ 59 70 A. Change Log ................................................. 60 71 A.1. Changes since RFC 2668 ................................... 60 72 A.2. Changes between RFC 2239 and RFC 2668 .................... 60 73 B. Full Copyright Statement ................................... 62 75 1. Introduction 77 This memo defines a portion of the Management Information Base (MIB) 78 for use with network management protocols in the Internet community. 79 In particular, it defines objects for managing IEEE 802.3 Medium 80 Attachment Units (MAUs). 82 This memo also includes a MIB module. This MIB module extends the 83 list of managed objects specified in the earlier version of this MIB 84 module, RFC 2668 [RFC2668]. 86 Ethernet technology, as defined by the 802.3 Working Group of the 87 IEEE, continues to evolve, with scalable increases in speed, new 88 types of cabling and interfaces, and new features. This evolution 89 may require changes in the managed objects in order to reflect this 90 new functionality. This document, as with other documents issued by 91 this working group, reflects a certain stage in the evolution of 92 Ethernet technology. In the future, this document might be revised, 93 or new documents might be issued by the Ethernet Interfaces and Hub 94 MIB Working Group, in order to reflect the evolution of Ethernet 95 technology. 97 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 98 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 99 document are to be interpreted as described in [RFC2119]. 101 2. The Internet-Standard Management Framework 103 For a detailed overview of the documents that describe the current 104 Internet-Standard Management Framework, please refer to section 7 of 105 RFC 3410 [RFC3410]. 107 Managed objects are accessed via a virtual information store, termed 108 the Management Information Base or MIB. MIB objects are generally 109 accessed through the Simple Network Management Protocol (SNMP). 110 Objects in the MIB are defined using the mechanisms defined in the 111 Structure of Management Information (SMI). This memo specifies a MIB 112 module that is compliant to the SMIv2, which is described in STD 58, 113 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 114 [RFC2580]. 116 3. Overview 118 Instances of these object types represent attributes of an IEEE 802.3 119 MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD 120 standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3 121 repeaters or to 802.3 (Ethernet-like) interfaces. For convenience 122 this document refers to these devices as "repeater MAUs" and 123 "interface MAUs." 125 The definitions presented here are based on Section 30.5, "Layer 126 Management for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Medium 127 Attachment Units (MAUs)", Section 30.6, "Management for link Auto- 128 Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed 129 object classes" of IEEE Std. 802.3, 2002 edition [IEEE802.3], as 130 amended by IEEE Std. 802.3ae-2002 [IEEE802.3ae]. That specification 131 includes definitions for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s 132 devices. This specification is intended to serve the same purpose: to 133 provide for management of all types of Ethernet/802.3 MAUs. 135 3.1. Relationship to RFC 2668 137 This MIB is intended to be a superset of that defined by RFC 2668 138 [RFC2668]. This MIB includes all of the objects contained in that 139 MIB, with new and updated definitions which provide support for 140 additional capabilities. Implementors are encouraged to support all 141 applicable conformance groups in order to make the best use of the 142 new functionality provided by this MIB. The new and updated 143 definitions provide management support for 10 Gb/s devices. 145 3.2. Relationship to RFC 2239 147 RFC 2668 was a replacement for RFC 2239 [RFC2239]. RFC 2668 defined 148 a superset of that defined by RFC 2239, which contained all of the 149 objects defined in RFC 2239, plus several new ones which provide 150 additional capabilities. The new objects provided management support 151 for: 153 o management of 1000 Mb/s devices 155 o management of PAUSE negotiation 157 o management of remote fault status 159 3.3. Relationship to RFC 1515 161 RFC 2239 was a replacement for RFC 1515 [RFC1515]. RFC 2239 defined 162 a superset of RFC 1515 which contained all of the objects defined in 163 RFC 1515, plus several new ones which provided additional 164 capabilities. The new objects in RFC 2239 provided management 165 support for: 167 o management of 100 Mb/s devices 169 o auto-negotiation on interface MAUs 171 o jack management 173 3.4. Relationship to Other MIBs 175 It is assumed that an agent implementing this MIB will also implement 176 (at least) the 'system' group defined in the SNMPv2 MIB [RFC3418]. 177 The following sections identify other MIBs that such an agent should 178 implement. 180 3.4.1. Relationship to the Interfaces MIB. 182 The sections of this document that define interface MAU-related 183 objects specify an extension to the Interfaces MIB [RFC2863]. An 184 agent implementing these interface-MAU related objects MUST also 185 implement the relevant groups of the ifCompliance3 MODULE-COMPLIANCE 186 statement of the Interface MIB. The value of the object ifMauIfIndex 187 is the same as the value of 'ifIndex' used to instantiate the 188 interface to which the given MAU is connected. 190 It is REQUIRED that an agent implementing the interface-MAU related 191 objects in this MIB will also fully comply with the dot3Compliance2 192 MODULE-COMPLIANCE statement of the Ethernet-like Interfaces MIB, 193 [ETHERIF]. Furthermore, when the interface-MAU related objects are 194 used to manage a 10GBASE-W PHY -- i.e., when ifMauType is equal to 195 dot3MauType10GigBaseW or any other 10GBASE-W variant -- then the 196 agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB 197 [ETHERWIS] and must follow the interface layering model specified 198 therein. In that case the value of the object ifMauIfIndex is the 199 same as the value of 'ifIndex' for the layer at the top of the stack, 200 i.e., for the ifTable entry that has 'ifType' equal to 201 ethernetCsmacd(6). If the interface-MAU related objects are used to 202 manage a PHY that allows the MAU type to be changed dynamically, then 203 the agent SHALL create ifTable, ifStackTable, and ifInvStackTable 204 entries that pertain to the WIS when ifMauDefaultType is changed to a 205 10GBASEW variant (i.e., one of dot3MauType10GigBaseW, 206 dot3MauType10GigBaseEW, dot3MauType10GigBaseLW, or 207 dot3MauType10GigBaseSW) from any other type, and shall destroy the 208 WIS-related entries when ifMauDefaultType is changed to a non- 209 10GBASE-W type. The agent SHALL also change the values of 210 'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry indexed 211 by ifMauIfIndex as specified in [ETHERIF] and [ETHERWIS] when 212 ifMauDefaultType is manipulated in this way but SHALL NOT otherwise 213 alter that entry. 215 (Note that repeater ports are not represented as interfaces in the 216 Interface MIB.) 218 3.4.2. Relationship to the 802.3 Repeater MIB 220 The section of this document that defines repeater MAU-related 221 objects specifies an extension to the 802.3 Repeater MIB defined in 222 [RFC2108]. An agent implementing these repeater-MAU related objects 223 MUST also comply with the snmpRptrModCompl compliance statement of 224 the 802.3 Repeater MIB. 226 The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to 227 instantiate a repeater MAU variable SHALL be the same as the values 228 of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the 229 port to which the given MAU is connected. 231 3.5. Management of Internal MAUs 233 In some situations, a MAU can be "internal" -- i.e., its 234 functionality is implemented entirely within a device. For example, 235 a managed repeater may contain an internal repeater-MAU and/or an 236 internal interface-MAU through which management communications 237 originating on one of the repeater's external ports pass in order to 238 reach the management agent associated with the repeater. Such 239 internal MAUs may or may not be managed. If they are managed, 240 objects describing their attributes should appear in the appropriate 241 MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs and 242 dot3IfMauBasicGroup for internal interface-MAUs. 244 3.6. Mapping of IEEE 802.3 Managed Objects 246 IEEE 802.3 Managed Object Corresponding SNMP Object 248 oMAU 249 .aMAUID rpMauIndex or 250 ifMauIndex or 251 broadMauIndex 252 .aMAUType rpMauType or 253 ifMauType 254 .aMAUTypeList ifMauTypeListBits 255 .aMediaAvailable rpMauMediaAvailable or 256 ifMauMediaAvailable 257 .aLoseMediaCounter rpMauMediaAvailableStateExits 258 or 259 ifMauMediaAvailableStateExits 260 .aJabber rpMauJabberState and 261 rpMauJabberingStateEnters or 262 ifMauJabberState and 263 ifMauJabberingStateEnters 264 .aMAUAdminState rpMauStatus or 265 ifMauStatus 266 .aBbMAUXmitRcvSplitType broadMauXmtRcvSplitType 267 .aBroadbandFrequencies broadMauXmtCarrierFreq and 268 broadMauTranslationFreq 269 .aFalseCarriers rpMauFalseCarriers or 270 ifMauFalseCarriers 271 .acResetMAU rpMauStatus or 272 ifMauStatus 273 .acMAUAdminControl rpMauStatus or 274 ifMauStatus 275 .nJabber rpMauJabberTrap or 276 ifMauJabberTrap 278 oAutoNegotiation 279 .aAutoNegID ifMauIndex 280 .aAutoNegAdminState ifMauAutoNegAdminStatus 281 .aAutoNegRemoteSignalling ifMauAutoNegRemoteSignalling 282 .aAutoNegAutoConfig ifMauAutoNegConfig 283 .aAutoNegLocalTechnologyAbility ifMauAutoNegCapabilityBits 284 .aAutoNegAdvertisedTechnologyAbility ifMauAutoNegAdvertisedBits and 285 ifMauAutoNegRemoteFaultAdvertised 286 .aAutoNegReceivedTechnologyAbility ifMauAutoNegReceivedBits and 287 ifMauAutoNegRemoteFaultReceived 288 .acAutoNegRestartAutoConfig ifMauAutoNegRestart 289 .acAutoNegAdminControl ifMauAutoNegAdminStatus 291 The following IEEE 802.3 managed objects have not been included in 292 this MIB for the following reasons. 294 IEEE 802.3 Managed Object Corresponding SNMP Object 296 oMAU 297 .aIdleErrorCount Only useful for 100BaseT2, 298 which is not widely 299 implemented. 301 oAutoNegotiation 302 .aAutoNegLocalSelectorAbility Only needed for support of 303 .aAutoNegAdvertisedSelectorAbility isoethernet (802.9a), which is 304 .aAutoNegReceivedSelectorAbility not supported by this MIB. 306 4. Definitions 308 MAU-MIB DEFINITIONS ::= BEGIN 310 IMPORTS 311 Counter32, Integer32, Counter64, 312 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 313 OBJECT-IDENTITY, mib-2 314 FROM SNMPv2-SMI 315 TruthValue, AutonomousType, TEXTUAL-CONVENTION 316 FROM SNMPv2-TC 317 OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP 318 FROM SNMPv2-CONF 319 InterfaceIndex 320 FROM IF-MIB; 322 mauMod MODULE-IDENTITY 323 LAST-UPDATED "200302280000Z" -- February 28, 2003 324 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 325 Working Group" 326 CONTACT-INFO 327 "WG E-mail: hubmib@ietf.org 328 To subscribe: hubmib-request@ietf.org 329 Chair: Dan Romascanu 330 Postal: Avaya Inc. 331 Atidim Technology Park, Bldg. 3 332 Tel Aviv 61131 333 Israel 334 Tel: +972 3 645 8414 335 E-mail: dromasca@avaya.com 337 Editor: John Flick 338 Postal: Hewlett-Packard Company 339 8000 Foothills Blvd. M/S 5557 340 Roseville, CA 95747-5557 341 USA 342 Tel: +1 916 785 4018 343 Fax: +1 916 785 1199 344 E-mail: johnf@rose.hp.com" 345 DESCRIPTION "Management information for 802.3 MAUs. 347 The following reference is used throughout 348 this MIB module: 350 [IEEE 802.3 Std] refers to: 351 IEEE Std 802.3, 2002 Edition: 'IEEE Standard 352 for Information technology - 353 Telecommunications and information exchange 354 between systems - Local and metropolitan 355 area networks - Specific requirements - 356 Part 3: Carrier sense multiple access with 357 collision detection (CSMA/CD) access method 358 and physical layer specifications', as 359 amended by IEEE Std 802.3ae-2002: 360 'Amendment: Media Access Control (MAC) 361 Parameters, Physical Layer, and Management 362 Parameters for 10 Gb/s Operation', August, 363 2002. 365 Of particular interest is Clause 30, '10Mb/s, 366 100Mb/s, 1000Mb/s and 10 Gb/s Management'. 368 Copyright (C) The Internet Society (2003). This 369 version of this MIB module is part of RFC XXXX; 370 see the RFC itself for full legal notices." 371 -- RFC Ed.: Replace XXXX with the actual RFC number & remove 372 -- this note 374 REVISION "200302280000Z" -- February 28, 2003 375 DESCRIPTION "Updated to include support for 10 Gb/s MAUs. 376 This resulted in the following revisions: 378 - Added OBJECT-IDENTITY definitions for 379 10 gigabit MAU types 380 - Added fiberLC jack type to JackType TC 381 - Extended ifMauTypeListBits with bits for 382 the 10 gigabit MAU types 383 - Added enumerations to ifMauMediaAvailable, 384 and updated its DESCRIPTION to reflect 385 behaviour at 10 Gb/s 386 - Added 64-bit version of ifMauFalseCarriers 387 and added mauIfGrpHCStats object group to 388 contain the new object 389 - Deprecated mauModIfCompl2 and replaced it 390 with mauModIfCompl3, which includes the new 391 object group 393 This version published as RFC XXXX." 394 -- RFC Ed.: Replace XXXX with the actual RFC number & remove 395 -- this note 397 REVISION "199908240400Z" -- August 24, 1999 398 DESCRIPTION "This version published as RFC 2668. Updated 399 to include support for 1000 Mb/sec 400 MAUs and flow control negotiation." 402 REVISION "199710310000Z" -- October 31, 1997 403 DESCRIPTION "Version published as RFC 2239." 405 REVISION "199309300000Z" -- September30, 1993 406 DESCRIPTION "Initial version, published as RFC 1515." 408 ::= { snmpDot3MauMgt 6 } 410 snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } 412 -- textual conventions 414 JackType ::= TEXTUAL-CONVENTION 415 STATUS current 416 DESCRIPTION "Common enumeration values for repeater 417 and interface MAU jack types." 418 SYNTAX INTEGER { 419 other(1), 420 rj45(2), 421 rj45S(3), -- rj45 shielded 422 db9(4), 423 bnc(5), 424 fAUI(6), -- female aui 425 mAUI(7), -- male aui 426 fiberSC(8), 427 fiberMIC(9), 428 fiberST(10), 429 telco(11), 430 mtrj(12), -- fiber MT-RJ 431 hssdc(13), -- fiber channel style-2 432 fiberLC(14) 433 } 435 dot3RpMauBasicGroup 436 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } 437 dot3IfMauBasicGroup 438 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } 439 dot3BroadMauBasicGroup 440 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } 442 dot3IfMauAutoNegGroup 443 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } 445 -- object identities for MAU types 446 -- (see rpMauType and ifMauType for usage) 448 dot3MauType 449 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } 451 dot3MauTypeAUI OBJECT-IDENTITY 452 STATUS current 453 DESCRIPTION "no internal MAU, view from AUI" 454 REFERENCE "[IEEE 802.3 Std.], Section 7" 455 ::= { dot3MauType 1 } 457 dot3MauType10Base5 OBJECT-IDENTITY 458 STATUS current 459 DESCRIPTION "thick coax MAU" 460 REFERENCE "[IEEE 802.3 Std.], Section 7" 461 ::= { dot3MauType 2 } 463 dot3MauTypeFoirl OBJECT-IDENTITY 464 STATUS current 465 DESCRIPTION "FOIRL MAU" 466 REFERENCE "[IEEE 802.3 Std.], Section 9.9" 467 ::= { dot3MauType 3 } 469 dot3MauType10Base2 OBJECT-IDENTITY 470 STATUS current 471 DESCRIPTION "thin coax MAU" 472 REFERENCE "[IEEE 802.3 Std.], Section 10" 473 ::= { dot3MauType 4 } 475 dot3MauType10BaseT OBJECT-IDENTITY 476 STATUS current 477 DESCRIPTION "UTP MAU. 478 Note that it is strongly recommended that 479 agents return either dot3MauType10BaseTHD or 480 dot3MauType10BaseTFD if the duplex mode is 481 known. However, management applications should 482 be prepared to receive this MAU type value from 483 older agent implementations." 484 REFERENCE "[IEEE 802.3 Std.], Section 14" 485 ::= { dot3MauType 5 } 487 dot3MauType10BaseFP OBJECT-IDENTITY 488 STATUS current 489 DESCRIPTION "passive fiber MAU" 490 REFERENCE "[IEEE 802.3 Std.], Section 16" 491 ::= { dot3MauType 6 } 493 dot3MauType10BaseFB OBJECT-IDENTITY 494 STATUS current 495 DESCRIPTION "sync fiber MAU" 496 REFERENCE "[IEEE 802.3 Std.], Section 17" 497 ::= { dot3MauType 7 } 499 dot3MauType10BaseFL OBJECT-IDENTITY 500 STATUS current 501 DESCRIPTION "async fiber MAU. 502 Note that it is strongly recommended that 503 agents return either dot3MauType10BaseFLHD or 504 dot3MauType10BaseFLFD if the duplex mode is 505 known. However, management applications should 506 be prepared to receive this MAU type value from 507 older agent implementations." 508 REFERENCE "[IEEE 802.3 Std.], Section 18" 509 ::= { dot3MauType 8 } 511 dot3MauType10Broad36 OBJECT-IDENTITY 512 STATUS current 513 DESCRIPTION "broadband DTE MAU. 514 Note that 10BROAD36 MAUs can be attached to 515 interfaces but not to repeaters." 516 REFERENCE "[IEEE 802.3 Std.], Section 11" 517 ::= { dot3MauType 9 } 519 ------ new since RFC 1515: 521 dot3MauType10BaseTHD OBJECT-IDENTITY 522 STATUS current 523 DESCRIPTION "UTP MAU, half duplex mode" 524 REFERENCE "[IEEE 802.3 Std.], Section 14" 525 ::= { dot3MauType 10 } 527 dot3MauType10BaseTFD OBJECT-IDENTITY 528 STATUS current 529 DESCRIPTION "UTP MAU, full duplex mode" 530 REFERENCE "[IEEE 802.3 Std.], Section 14" 531 ::= { dot3MauType 11 } 533 dot3MauType10BaseFLHD OBJECT-IDENTITY 534 STATUS current 535 DESCRIPTION "async fiber MAU, half duplex mode" 536 REFERENCE "[IEEE 802.3 Std.], Section 18" 537 ::= { dot3MauType 12 } 539 dot3MauType10BaseFLFD OBJECT-IDENTITY 540 STATUS current 541 DESCRIPTION "async fiber MAU, full duplex mode" 542 REFERENCE "[IEEE 802.3 Std.], Section 18" 543 ::= { dot3MauType 13 } 545 dot3MauType100BaseT4 OBJECT-IDENTITY 546 STATUS current 547 DESCRIPTION "4 pair category 3 UTP" 548 REFERENCE "[IEEE 802.3 Std.], Section 23" 549 ::= { dot3MauType 14 } 551 dot3MauType100BaseTXHD OBJECT-IDENTITY 552 STATUS current 553 DESCRIPTION "2 pair category 5 UTP, half duplex mode" 554 REFERENCE "[IEEE 802.3 Std.], Section 25" 555 ::= { dot3MauType 15 } 557 dot3MauType100BaseTXFD OBJECT-IDENTITY 558 STATUS current 559 DESCRIPTION "2 pair category 5 UTP, full duplex mode" 560 REFERENCE "[IEEE 802.3 Std.], Section 25" 561 ::= { dot3MauType 16 } 563 dot3MauType100BaseFXHD OBJECT-IDENTITY 564 STATUS current 565 DESCRIPTION "X fiber over PMT, half duplex mode" 566 REFERENCE "[IEEE 802.3 Std.], Section 26" 567 ::= { dot3MauType 17 } 569 dot3MauType100BaseFXFD OBJECT-IDENTITY 570 STATUS current 571 DESCRIPTION "X fiber over PMT, full duplex mode" 572 REFERENCE "[IEEE 802.3 Std.], Section 26" 573 ::= { dot3MauType 18 } 575 dot3MauType100BaseT2HD OBJECT-IDENTITY 576 STATUS current 577 DESCRIPTION "2 pair category 3 UTP, half duplex mode" 578 REFERENCE "[IEEE 802.3 Std.], Section 32" 579 ::= { dot3MauType 19 } 581 dot3MauType100BaseT2FD OBJECT-IDENTITY 582 STATUS current 583 DESCRIPTION "2 pair category 3 UTP, full duplex mode" 584 REFERENCE "[IEEE 802.3 Std.], Section 32" 585 ::= { dot3MauType 20 } 587 ------ new since RFC 2239: 589 dot3MauType1000BaseXHD OBJECT-IDENTITY 590 STATUS current 591 DESCRIPTION "PCS/PMA, unknown PMD, half duplex mode" 592 REFERENCE "[IEEE 802.3 Std.], Section 36" 593 ::= { dot3MauType 21 } 595 dot3MauType1000BaseXFD OBJECT-IDENTITY 596 STATUS current 597 DESCRIPTION "PCS/PMA, unknown PMD, full duplex mode" 598 REFERENCE "[IEEE 802.3 Std.], Section 36" 599 ::= { dot3MauType 22 } 601 dot3MauType1000BaseLXHD OBJECT-IDENTITY 602 STATUS current 603 DESCRIPTION "Fiber over long-wavelength laser, half duplex 604 mode" 605 REFERENCE "[IEEE 802.3 Std.], Section 38" 606 ::= { dot3MauType 23 } 608 dot3MauType1000BaseLXFD OBJECT-IDENTITY 609 STATUS current 610 DESCRIPTION "Fiber over long-wavelength laser, full duplex 611 mode" 612 REFERENCE "[IEEE 802.3 Std.], Section 38" 613 ::= { dot3MauType 24 } 615 dot3MauType1000BaseSXHD OBJECT-IDENTITY 616 STATUS current 617 DESCRIPTION "Fiber over short-wavelength laser, half 618 duplex mode" 619 REFERENCE "[IEEE 802.3 Std.], Section 38" 620 ::= { dot3MauType 25 } 622 dot3MauType1000BaseSXFD OBJECT-IDENTITY 623 STATUS current 624 DESCRIPTION "Fiber over short-wavelength laser, full 625 duplex mode" 626 REFERENCE "[IEEE 802.3 Std.], Section 38" 627 ::= { dot3MauType 26 } 629 dot3MauType1000BaseCXHD OBJECT-IDENTITY 630 STATUS current 631 DESCRIPTION "Copper over 150-Ohm balanced cable, half 632 duplex mode" 633 REFERENCE "[IEEE 802.3 Std.], Section 39" 634 ::= { dot3MauType 27 } 636 dot3MauType1000BaseCXFD OBJECT-IDENTITY 637 STATUS current 638 DESCRIPTION "Copper over 150-Ohm balanced cable, full 639 duplex mode" 640 REFERENCE "[IEEE 802.3 Std.], Section 39" 641 ::= { dot3MauType 28 } 643 dot3MauType1000BaseTHD OBJECT-IDENTITY 644 STATUS current 645 DESCRIPTION "Four-pair Category 5 UTP, half duplex mode" 646 REFERENCE "[IEEE 802.3 Std.], Section 40" 647 ::= { dot3MauType 29 } 649 dot3MauType1000BaseTFD OBJECT-IDENTITY 650 STATUS current 651 DESCRIPTION "Four-pair Category 5 UTP, full duplex mode" 652 REFERENCE "[IEEE 802.3 Std.], Section 40" 653 ::= { dot3MauType 30 } 655 ------ new since RFC 2668: 657 dot3MauType10GigBaseX OBJECT-IDENTITY 658 STATUS current 659 DESCRIPTION "X PCS/PMA, unknown PMD." 660 REFERENCE "[IEEE 802.3 Std.], Section 48" 661 ::= { dot3MauType 31 } 663 dot3MauType10GigBaseLX4 OBJECT-IDENTITY 664 STATUS current 665 DESCRIPTION "X fiber over WWDM optics" 666 REFERENCE "[IEEE 802.3 Std.], Section 53" 667 ::= { dot3MauType 32 } 669 dot3MauType10GigBaseR OBJECT-IDENTITY 670 STATUS current 671 DESCRIPTION "R PCS/PMA, unknown PMD." 672 REFERENCE "[IEEE 802.3 Std.], Section 49" 673 ::= { dot3MauType 33 } 675 dot3MauType10GigBaseER OBJECT-IDENTITY 676 STATUS current 677 DESCRIPTION "R fiber over 1550 nm optics" 678 REFERENCE "[IEEE 802.3 Std.], Section 52" 679 ::= { dot3MauType 34 } 681 dot3MauType10GigBaseLR OBJECT-IDENTITY 682 STATUS current 683 DESCRIPTION "R fiber over 1310 nm optics" 684 REFERENCE "[IEEE 802.3 Std.], Section 52" 685 ::= { dot3MauType 35 } 687 dot3MauType10GigBaseSR OBJECT-IDENTITY 688 STATUS current 689 DESCRIPTION "R fiber over 850 nm optics" 690 REFERENCE "[IEEE 802.3 Std.], Section 52" 691 ::= { dot3MauType 36 } 693 dot3MauType10GigBaseW OBJECT-IDENTITY 694 STATUS current 695 DESCRIPTION "W PCS/PMA, unknown PMD." 696 REFERENCE "[IEEE 802.3 Std.], Section 49 and 50" 697 ::= { dot3MauType 37 } 699 dot3MauType10GigBaseEW OBJECT-IDENTITY 700 STATUS current 701 DESCRIPTION "W fiber over 1550 nm optics" 702 REFERENCE "[IEEE 802.3 Std.], Section 52" 703 ::= { dot3MauType 38 } 705 dot3MauType10GigBaseLW OBJECT-IDENTITY 706 STATUS current 707 DESCRIPTION "W fiber over 1310 nm optics" 708 REFERENCE "[IEEE 802.3 Std.], Section 52" 709 ::= { dot3MauType 39 } 711 dot3MauType10GigBaseSW OBJECT-IDENTITY 712 STATUS current 713 DESCRIPTION "W fiber over 850 nm optics" 714 REFERENCE "[IEEE 802.3 Std.], Section 52" 715 ::= { dot3MauType 40 } 717 -- 718 -- The Basic Repeater MAU Table 719 -- 721 rpMauTable OBJECT-TYPE 722 SYNTAX SEQUENCE OF RpMauEntry 723 MAX-ACCESS not-accessible 724 STATUS current 725 DESCRIPTION "Table of descriptive and status information 726 about the MAU(s) attached to the ports of a 727 repeater." 728 ::= { dot3RpMauBasicGroup 1 } 730 rpMauEntry OBJECT-TYPE 731 SYNTAX RpMauEntry 732 MAX-ACCESS not-accessible 733 STATUS current 734 DESCRIPTION "An entry in the table, containing information 735 about a single MAU." 736 INDEX { rpMauGroupIndex, 737 rpMauPortIndex, 738 rpMauIndex 739 } 740 ::= { rpMauTable 1 } 742 RpMauEntry ::= 743 SEQUENCE { 744 rpMauGroupIndex Integer32, 745 rpMauPortIndex Integer32, 746 rpMauIndex Integer32, 747 rpMauType AutonomousType, 748 rpMauStatus INTEGER, 749 rpMauMediaAvailable INTEGER, 750 rpMauMediaAvailableStateExits Counter32, 751 rpMauJabberState INTEGER, 752 rpMauJabberingStateEnters Counter32, 753 rpMauFalseCarriers Counter32 754 } 756 rpMauGroupIndex OBJECT-TYPE 757 SYNTAX Integer32 (1..2147483647) 758 MAX-ACCESS read-only -- read-only since originally an 759 -- SMIv1 index 760 STATUS current 761 DESCRIPTION "This variable uniquely identifies the group 762 containing the port to which the MAU described 763 by this entry is connected. 765 Note: In practice, a group will generally be 766 a field-replaceable unit (i.e., module, card, 767 or board) that can fit in the physical system 768 enclosure, and the group number will correspond 769 to a number marked on the physical enclosure. 771 The group denoted by a particular value of this 772 object is the same as the group denoted by the 773 same value of rptrGroupIndex." 774 REFERENCE "Reference RFC 2108, rptrGroupIndex." 775 ::= { rpMauEntry 1 } 777 rpMauPortIndex OBJECT-TYPE 778 SYNTAX Integer32 (1..2147483647) 779 MAX-ACCESS read-only -- read-only since originally an 780 -- SMIv1 index 781 STATUS current 782 DESCRIPTION "This variable uniquely identifies the repeater 783 port within group rpMauGroupIndex to which the 784 MAU described by this entry is connected." 785 REFERENCE "Reference RFC 2108, rptrPortIndex." 786 ::= { rpMauEntry 2 } 788 rpMauIndex OBJECT-TYPE 789 SYNTAX Integer32 (1..2147483647) 790 MAX-ACCESS read-only -- read-only since originally an 791 -- SMIv1 index 792 STATUS current 793 DESCRIPTION "This variable uniquely identifies the MAU 794 described by this entry from among other 795 MAUs connected to the same port 796 (rpMauPortIndex)." 797 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 798 ::= { rpMauEntry 3 } 800 rpMauType OBJECT-TYPE 801 SYNTAX AutonomousType 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION "This object identifies the MAU type. An 805 initial set of MAU types are defined above. The 806 assignment of OBJECT IDENTIFIERs to new types of 807 MAUs is managed by the IANA. If the MAU type is 808 unknown, the object identifier 810 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 812 is returned. Note that unknownMauType is a 813 syntactically valid object identifier, and any 814 conformant implementation of ASN.1 and the BER 815 must be able to generate and recognize this 816 value." 817 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." 818 ::= { rpMauEntry 4 } 820 rpMauStatus OBJECT-TYPE 821 SYNTAX INTEGER { 822 other(1), 823 unknown(2), 824 operational(3), 825 standby(4), 826 shutdown(5), 827 reset(6) 828 } 829 MAX-ACCESS read-write 830 STATUS current 831 DESCRIPTION "The current state of the MAU. This object MAY 832 be implemented as a read-only object by those 833 agents and MAUs that do not implement software 834 control of the MAU state. Some agents may not 835 support setting the value of this object to some 836 of the enumerated values. 838 The value other(1) is returned if the MAU is in 839 a state other than one of the states 2 through 840 6. 842 The value unknown(2) is returned when the MAU's 843 true state is unknown; for example, when it is 844 being initialized. 846 A MAU in the operational(3) state is fully 847 functional, operates, and passes signals to its 848 attached DTE or repeater port in accordance to 849 its specification. 851 A MAU in standby(4) state forces DI and CI to 852 idle and the media transmitter to idle or fault, 853 if supported. Standby(4) mode only applies to 854 link type MAUs. The state of 855 rpMauMediaAvailable is unaffected. 857 A MAU in shutdown(5) state assumes the same 858 condition on DI, CI, and the media transmitter 859 as though it were powered down or not connected. 860 The MAU MAY return other(1) value for the 861 rpMauJabberState and rpMauMediaAvailable objects 862 when it is in this state. For an AUI, this 863 state will remove power from the AUI. 865 Setting this variable to the value reset(6) 866 resets the MAU in the same manner as a 867 power-off, power-on cycle of at least one-half 868 second would. The agent is not required to 869 return the value reset (6). 871 Setting this variable to the value 872 operational(3), standby(4), or shutdown(5) 873 causes the MAU to assume the respective state 874 except that setting a mixing-type MAU or an AUI 875 to standby(4) will cause the MAU to enter the 876 shutdown state." 877 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, 878 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 879 acResetMAU." 880 ::= { rpMauEntry 5 } 882 rpMauMediaAvailable OBJECT-TYPE 883 SYNTAX INTEGER { 884 other(1), 885 unknown(2), 886 available(3), 887 notAvailable(4), 888 remoteFault(5), 889 invalidSignal(6), 890 remoteJabber(7), 891 remoteLinkLoss(8), 892 remoteTest(9), 893 offline(10), 894 autoNegError(11) 895 } 896 MAX-ACCESS read-only 897 STATUS current 898 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 899 10BASE-T, 10BASE-F) then this is equivalent to 900 the link test fail state/low light function. 901 For an AUI or a coax (including broadband) MAU 902 this indicates whether or not loopback is 903 detected on the DI circuit. The value of this 904 attribute persists between packets for MAU types 905 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 907 The value other(1) is returned if the 908 mediaAvailable state is not one of 2 through 11. 910 The value unknown(2) is returned when the MAU's 911 true state is unknown; for example, when it is 912 being initialized. At power-up or following a 913 reset, the value of this attribute will be 914 unknown for AUI, coax, and 10BASE-FP MAUs. For 915 these MAUs loopback will be tested on each 916 transmission during which no collision is 917 detected. If DI is receiving input when DO 918 returns to IDL after a transmission and there 919 has been no collision during the transmission 920 then loopback will be detected. The value of 921 this attribute will only change during 922 non-collided transmissions for AUI, coax, and 923 10BASE-FP MAUs. 925 For 100Mbps and 1000Mbps MAUs, the enumerations 926 match the states within the respective link 927 integrity state diagrams, fig 32-16, 23-12 and 928 24-15 of sections 32, 23 and 24 of [IEEE802.3]. 929 Any MAU which implements management of 930 auto-negotiation will map remote fault 931 indication to remote fault. 933 The value available(3) indicates that the link, 934 light, or loopback is normal. The value 935 notAvailable(4) indicates link loss, low light, 936 or no loopback. 938 The value remoteFault(5) indicates that a fault 939 has been detected at the remote end of the link. 940 This value applies to 10BASE-FB, 100BASE-T4 Far 941 End Fault Indication and non-specified remote 942 faults from a system running auto-negotiation. 943 The values remoteJabber(7), remoteLinkLoss(8), 944 and remoteTest(9) SHOULD be used instead of 945 remoteFault(5) where the reason for remote fault 946 is identified in the remote signaling protocol. 948 The value invalidSignal(6) indicates that an 949 invalid signal has been received from the other 950 end of the link. invalidSignal(6) applies only 951 to MAUs of type 10BASE-FB. 953 Where an IEEE Std 802.3-2002 clause 22 MII 954 is present, a logic one in the remote fault bit 955 (reference section 22.2.4.2.8 of that document) 956 maps to the value remoteFault(5), and a logic 957 zero in the link status bit (reference section 958 22.2.4.2.10 of that document) maps to the value 959 notAvailable(4). The value notAvailable(4) 960 takes precedence over the value remoteFault(5). 962 Any MAU that implements management of clause 37 963 Auto-Negotiation will map the received Remote 964 Fault (RF1 and RF2) bit values for Offline to 965 offline(10), Link Failure to remoteFault(5) and 966 Auto-Negotiation Error to autoNegError(11)." 968 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." 969 ::= { rpMauEntry 6 } 971 rpMauMediaAvailableStateExits OBJECT-TYPE 972 SYNTAX Counter32 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION "A count of the number of times that 976 rpMauMediaAvailable for this MAU instance leaves 977 the state available(3). 979 Discontinuities in the value of this counter can 980 occur at re-initialization of the management 981 system, and at other times as indicated by the 982 value of rptrMonitorPortLastChange." 983 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, 984 aLoseMediaCounter. 985 RFC 2108, rptrMonitorPortLastChange" 986 ::= { rpMauEntry 7 } 988 rpMauJabberState OBJECT-TYPE 989 SYNTAX INTEGER { 990 other(1), 991 unknown(2), 992 noJabber(3), 993 jabbering(4) 994 } 995 MAX-ACCESS read-only 996 STATUS current 997 DESCRIPTION "The value other(1) is returned if the jabber 998 state is not 2, 3, or 4. The agent MUST always 999 return other(1) for MAU type dot3MauTypeAUI. 1001 The value unknown(2) is returned when the MAU's 1002 true state is unknown; for example, when it is 1003 being initialized. 1005 If the MAU is not jabbering the agent returns 1006 noJabber(3). This is the 'normal' state. 1008 If the MAU is in jabber state the agent returns 1009 the jabbering(4) value." 1010 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1011 aJabber.jabberFlag." 1012 ::= { rpMauEntry 8 } 1014 rpMauJabberingStateEnters OBJECT-TYPE 1015 SYNTAX Counter32 1016 MAX-ACCESS read-only 1017 STATUS current 1018 DESCRIPTION "A count of the number of times that 1019 mauJabberState for this MAU instance enters the 1020 state jabbering(4). For MAUs of type 1021 dot3MauTypeAUI, dot3MauType100BaseT4, 1022 dot3MauType100BaseTX, dot3MauType100BaseFX and 1023 all 1000Mbps types, this counter will always 1024 indicate zero. 1026 Discontinuities in the value of this counter can 1027 occur at re-initialization of the management 1028 system, and at other times as indicated by the 1029 value of rptrMonitorPortLastChange." 1030 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1031 aJabber.jabberCounter. 1032 RFC 2108, rptrMonitorPortLastChange" 1033 ::= { rpMauEntry 9 } 1035 rpMauFalseCarriers OBJECT-TYPE 1036 SYNTAX Counter32 1037 MAX-ACCESS read-only 1038 STATUS current 1039 DESCRIPTION "A count of the number of false carrier events 1040 during IDLE in 100BASE-X links. This counter 1041 does not increment at the symbol rate. It can 1042 increment after a valid carrier completion at a 1043 maximum rate of once per 100 ms until the next 1044 carrier event. 1046 This counter increments only for MAUs of type 1047 dot3MauType100BaseT4, dot3MauType100BaseTX, and 1048 dot3MauType100BaseFX and all 1000Mbps types. 1049 For all other MAU types, this counter will 1050 always indicate zero. 1052 The approximate minimum time for rollover of 1053 this counter is 7.4 hours. 1055 Discontinuities in the value of this counter can 1056 occur at re-initialization of the management 1057 system, and at other times as indicated by the 1058 value of rptrMonitorPortLastChange." 1059 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. 1060 RFC 2108, rptrMonitorPortLastChange" 1061 ::= { rpMauEntry 10 } 1063 -- The rpJackTable applies to MAUs attached to repeaters 1064 -- which have one or more external jacks (connectors). 1066 rpJackTable OBJECT-TYPE 1067 SYNTAX SEQUENCE OF RpJackEntry 1068 MAX-ACCESS not-accessible 1069 STATUS current 1070 DESCRIPTION "Information about the external jacks attached 1071 to MAUs attached to the ports of a repeater." 1072 ::= { dot3RpMauBasicGroup 2 } 1074 rpJackEntry OBJECT-TYPE 1075 SYNTAX RpJackEntry 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION "An entry in the table, containing information 1079 about a particular jack." 1080 INDEX { rpMauGroupIndex, 1081 rpMauPortIndex, 1082 rpMauIndex, 1083 rpJackIndex 1084 } 1085 ::= { rpJackTable 1 } 1087 RpJackEntry ::= 1088 SEQUENCE { 1089 rpJackIndex Integer32, 1090 rpJackType JackType 1091 } 1093 rpJackIndex OBJECT-TYPE 1094 SYNTAX Integer32 (1..2147483647) 1095 MAX-ACCESS not-accessible 1096 STATUS current 1097 DESCRIPTION "This variable uniquely identifies the jack 1098 described by this entry from among other jacks 1099 attached to the same MAU (rpMauIndex)." 1100 ::= { rpJackEntry 1 } 1102 rpJackType OBJECT-TYPE 1103 SYNTAX JackType 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION "The jack connector type, as it appears on the 1107 outside of the system." 1108 ::= { rpJackEntry 2 } 1110 -- 1111 -- The Basic Interface MAU Table 1112 -- 1114 ifMauTable OBJECT-TYPE 1115 SYNTAX SEQUENCE OF IfMauEntry 1116 MAX-ACCESS not-accessible 1117 STATUS current 1118 DESCRIPTION "Table of descriptive and status information 1119 about MAU(s) attached to an interface." 1120 ::= { dot3IfMauBasicGroup 1 } 1122 ifMauEntry OBJECT-TYPE 1123 SYNTAX IfMauEntry 1124 MAX-ACCESS not-accessible 1125 STATUS current 1126 DESCRIPTION "An entry in the table, containing information 1127 about a single MAU." 1128 INDEX { ifMauIfIndex, 1129 ifMauIndex 1130 } 1131 ::= { ifMauTable 1 } 1133 IfMauEntry ::= 1134 SEQUENCE { 1135 ifMauIfIndex InterfaceIndex, 1136 ifMauIndex Integer32, 1137 ifMauType AutonomousType, 1138 ifMauStatus INTEGER, 1139 ifMauMediaAvailable INTEGER, 1140 ifMauMediaAvailableStateExits Counter32, 1141 ifMauJabberState INTEGER, 1142 ifMauJabberingStateEnters Counter32, 1143 ifMauFalseCarriers Counter32, 1144 ifMauTypeList Integer32, 1145 ifMauDefaultType AutonomousType, 1146 ifMauAutoNegSupported TruthValue, 1147 ifMauTypeListBits BITS, 1148 ifMauHCFalseCarriers Counter64 1149 } 1151 ifMauIfIndex OBJECT-TYPE 1152 SYNTAX InterfaceIndex 1153 MAX-ACCESS read-only -- read-only since originally an 1154 -- SMIv1 index 1155 STATUS current 1156 DESCRIPTION "This variable uniquely identifies the interface 1157 to which the MAU described by this entry is 1158 connected." 1159 REFERENCE "RFC 2863, ifIndex" 1160 ::= { ifMauEntry 1 } 1162 ifMauIndex OBJECT-TYPE 1163 SYNTAX Integer32 (1..2147483647) 1164 MAX-ACCESS read-only -- read-only since originally an 1165 -- SMIv1 index 1166 STATUS current 1167 DESCRIPTION "This variable uniquely identifies the MAU 1168 described by this entry from among other MAUs 1169 connected to the same interface (ifMauIfIndex)." 1170 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 1171 ::= { ifMauEntry 2 } 1173 ifMauType OBJECT-TYPE 1174 SYNTAX AutonomousType 1175 MAX-ACCESS read-only 1176 STATUS current 1177 DESCRIPTION "This object identifies the MAU type. An 1178 initial set of MAU types are defined above. The 1179 assignment of OBJECT IDENTIFIERs to new types of 1180 MAUs is managed by the IANA. If the MAU type is 1181 unknown, the object identifier 1183 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 1185 is returned. Note that unknownMauType is a 1186 syntactically valid object identifier, and any 1187 conformant implementation of ASN.1 and the BER 1188 must be able to generate and recognize this 1189 value. 1191 This object represents the operational type of 1192 the MAU, as determined by either (1) the result 1193 of the auto-negotiation function or (2) if 1194 auto-negotiation is not enabled or is not 1195 implemented for this MAU, by the value of the 1196 object ifMauDefaultType. In case (2), a set to 1197 the object ifMauDefaultType will force the MAU 1198 into the new operating mode." 1199 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." 1200 ::= { ifMauEntry 3 } 1202 ifMauStatus OBJECT-TYPE 1203 SYNTAX INTEGER { 1204 other(1), 1205 unknown(2), 1206 operational(3), 1207 standby(4), 1208 shutdown(5), 1209 reset(6) 1210 } 1211 MAX-ACCESS read-write 1212 STATUS current 1213 DESCRIPTION "The current state of the MAU. This object MAY 1214 be implemented as a read-only object by those 1215 agents and MAUs that do not implement software 1216 control of the MAU state. Some agents may not 1217 support setting the value of this object to some 1218 of the enumerated values. 1220 The value other(1) is returned if the MAU is in 1221 a state other than one of the states 2 through 1222 6. 1224 The value unknown(2) is returned when the MAU's 1225 true state is unknown; for example, when it is 1226 being initialized. 1228 A MAU in the operational(3) state is fully 1229 functional, operates, and passes signals to its 1230 attached DTE or repeater port in accordance to 1231 its specification. 1233 A MAU in standby(4) state forces DI and CI to 1234 idle and the media transmitter to idle or fault, 1235 if supported. Standby(4) mode only applies to 1236 link type MAUs. The state of 1237 ifMauMediaAvailable is unaffected. 1239 A MAU in shutdown(5) state assumes the same 1240 condition on DI, CI, and the media transmitter 1241 as though it were powered down or not connected. 1242 The MAU MAY return other(1) value for the 1243 ifMauJabberState and ifMauMediaAvailable objects 1244 when it is in this state. For an AUI, this 1245 state will remove power from the AUI. 1247 Setting this variable to the value reset(6) 1248 resets the MAU in the same manner as a 1249 power-off, power-on cycle of at least one-half 1250 second would. The agent is not required to 1251 return the value reset (6). 1253 Setting this variable to the value 1254 operational(3), standby(4), or shutdown(5) 1255 causes the MAU to assume the respective state 1256 except that setting a mixing-type MAU or an AUI 1257 to standby(4) will cause the MAU to enter the 1258 shutdown state." 1259 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, 1260 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 1261 acResetMAU." 1262 ::= { ifMauEntry 4 } 1264 ifMauMediaAvailable OBJECT-TYPE 1265 SYNTAX INTEGER { 1266 other(1), 1267 unknown(2), 1268 available(3), 1269 notAvailable(4), 1270 remoteFault(5), 1271 invalidSignal(6), 1272 remoteJabber(7), 1273 remoteLinkLoss(8), 1274 remoteTest(9), 1275 offline(10), 1276 autoNegError(11), 1277 pmdLinkFault(12), 1278 wisFrameLoss(13), 1279 wisSignalLoss(14), 1280 pcsLinkFault(15), 1281 excessiveBER(16), 1282 dxsLinkFault(17), 1283 pxsLinkFault(18) 1285 } 1286 MAX-ACCESS read-only 1287 STATUS current 1288 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 1289 10BASE-T, 10BASE-F) then this is equivalent to 1290 the link test fail state/low light function. 1291 For an AUI or a coax (including broadband) MAU 1292 this indicates whether or not loopback is 1293 detected on the DI circuit. The value of this 1294 attribute persists between packets for MAU types 1295 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 1297 The value other(1) is returned if the 1298 mediaAvailable state is not one of 2 through 18. 1300 The value unknown(2) is returned when the MAU's 1301 true state is unknown; for example, when it is 1302 being initialized. At power-up or following a 1303 reset, the value of this attribute will be 1304 unknown for AUI, coax, and 10BASE-FP MAUs. For 1305 these MAUs loopback will be tested on each 1306 transmission during which no collision is 1307 detected. If DI is receiving input when DO 1308 returns to IDL after a transmission and there 1309 has been no collision during the transmission 1310 then loopback will be detected. The value of 1311 this attribute will only change during 1312 non-collided transmissions for AUI, coax, and 1313 10BASE-FP MAUs. 1315 For 100Mbps and 1000Mbps MAUs, the enumerations 1316 match the states within the respective link 1317 integrity state diagrams, fig 32-16, 23-12 and 1318 24-15 of sections 32, 23 and 24 of [IEEE802.3]. 1319 Any MAU which implements management of 1320 auto-negotiation will map remote fault 1321 indication to remote fault. 1323 The value available(3) indicates that the link, 1324 light, or loopback is normal. The value 1325 notAvailable(4) indicates link loss, low light, 1326 or no loopback. 1328 The value remoteFault(5) indicates that a fault 1329 has been detected at the remote end of the link. 1330 This value applies to 10BASE-FB, 100BASE-T4 Far 1331 End Fault Indication and non-specified remote 1332 faults from a system running auto-negotiation. 1334 The values remoteJabber(7), remoteLinkLoss(8), 1335 and remoteTest(9) SHOULD be used instead of 1336 remoteFault(5) where the reason for remote fault 1337 is identified in the remote signaling protocol. 1339 The value invalidSignal(6) indicates that an 1340 invalid signal has been received from the other 1341 end of the link. invalidSignal(6) applies only 1342 to MAUs of type 10BASE-FB. 1344 Where an IEEE Std 802.3-2002 clause 22 MII 1345 is present, a logic one in the remote fault bit 1346 (reference section 22.2.4.2.8 of that document) 1347 maps to the value remoteFault(5), and a logic 1348 zero in the link status bit (reference section 1349 22.2.4.2.10 of that document) maps to the value 1350 notAvailable(4). The value notAvailable(4) 1351 takes precedence over the value remoteFault(5). 1353 Any MAU that implements management of clause 37 1354 Auto-Negotiation will map the received RF1 and 1355 RF2 bit values for Offline to offline(10), Link 1356 Failure to remoteFault(5) and Auto-Negotiation 1357 Error to autoNegError(11). 1359 For 10 Gb/s, the enumerations map to the states 1360 within the Reconciliation Sublayer state diagram 1361 as follows: 1362 NoFault maps to the enumeration 'available(3)' 1363 LocalFault maps to the enumeration 1364 'notAvailable(4)' 1365 RemoteFault maps to the enumeration 1366 'remoteFault(5)' 1367 The enumerations 'pmdLinkFault(12)', 1368 'wisFrameLoss(13)', 'wisSignalLoss(14)', 1369 'pcsLinkFault(15)', 'excessiveBER(16)', and 1370 'dxsLinkFault(17)' and 'pxsLinkFault(18)' should 1371 be used instead of the enumeration 1372 'notAvailable(4)' where the reason for the local 1373 fault can be identified through the use of the 1374 MDIO Interface. Where multiple reasons for the 1375 local fault state can be identified only the 1376 highest precedence error should be reported. 1377 The precedence in descending order is as 1378 follows: 1379 pxsLinkFault 1380 pmdLinkFault 1381 wisFrameLoss 1382 wisSignalLoss 1383 pcsLinkFault 1384 excessiveBER 1385 dxsLinkFault" 1386 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." 1387 ::= { ifMauEntry 5 } 1389 ifMauMediaAvailableStateExits OBJECT-TYPE 1390 SYNTAX Counter32 1391 MAX-ACCESS read-only 1392 STATUS current 1393 DESCRIPTION "A count of the number of times that 1394 ifMauMediaAvailable for this MAU instance leaves 1395 the state available(3). 1397 Discontinuities in the value of this counter can 1398 occur at re-initialization of the management 1399 system, and at other times as indicated by the 1400 value of ifCounterDiscontinuityTime." 1401 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, 1402 aLoseMediaCounter. 1403 RFC 2863, ifCounterDiscontinuityTime." 1404 ::= { ifMauEntry 6 } 1406 ifMauJabberState OBJECT-TYPE 1407 SYNTAX INTEGER { 1408 other(1), 1409 unknown(2), 1410 noJabber(3), 1411 jabbering(4) 1412 } 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION "The value other(1) is returned if the jabber 1416 state is not 2, 3, or 4. The agent MUST always 1417 return other(1) for MAU type dot3MauTypeAUI. 1419 The value unknown(2) is returned when the MAU's 1420 true state is unknown; for example, when it is 1421 being initialized. 1423 If the MAU is not jabbering the agent returns 1424 noJabber(3). This is the 'normal' state. 1426 If the MAU is in jabber state the agent returns 1427 the jabbering(4) value." 1428 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1429 aJabber.jabberFlag." 1431 ::= { ifMauEntry 7 } 1433 ifMauJabberingStateEnters OBJECT-TYPE 1434 SYNTAX Counter32 1435 MAX-ACCESS read-only 1436 STATUS current 1437 DESCRIPTION "A count of the number of times that 1438 mauJabberState for this MAU instance enters the 1439 state jabbering(4). This counter will always 1440 indicate zero for MAUs of type dot3MauTypeAUI 1441 and those of speeds above 10Mbps. 1443 Discontinuities in the value of this counter can 1444 occur at re-initialization of the management 1445 system, and at other times as indicated by the 1446 value of ifCounterDiscontinuityTime." 1447 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1448 aJabber.jabberCounter. 1449 RFC 2863, ifCounterDiscontinuityTime." 1450 ::= { ifMauEntry 8 } 1452 ifMauFalseCarriers OBJECT-TYPE 1453 SYNTAX Counter32 1454 MAX-ACCESS read-only 1455 STATUS current 1456 DESCRIPTION "A count of the number of false carrier events 1457 during IDLE in 100BASE-X and 1000BASE-X links. 1459 For all other MAU types, this counter will 1460 always indicate zero. This counter does not 1461 increment at the symbol rate. 1463 It can increment after a valid carrier 1464 completion at a maximum rate of once per 100 ms 1465 for 100BASE-X and once per 10us for 1000BASE-X 1466 until the next CarrierEvent. 1468 This counter can roll over very quickly. A 1469 management station is advised to poll the 1470 ifMauHCFalseCarriers instead of this counter in 1471 order to avoid loss of information. 1473 Discontinuities in the value of this counter can 1474 occur at re-initialization of the management 1475 system, and at other times as indicated by the 1476 value of ifCounterDiscontinuityTime." 1477 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. 1478 RFC 2863, ifCounterDiscontinuityTime." 1480 ::= { ifMauEntry 9 } 1482 ifMauTypeList OBJECT-TYPE 1483 SYNTAX Integer32 1484 MAX-ACCESS read-only 1485 STATUS deprecated 1486 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1488 This object has been deprecated in favour of 1489 ifMauTypeListBits. 1491 A value that uniquely identifies the set of 1492 possible IEEE 802.3 types that the MAU could be. 1493 The value is a sum which initially takes the 1494 value zero. Then, for each type capability of 1495 this MAU, 2 raised to the power noted below is 1496 added to the sum. For example, a MAU which has 1497 the capability to be only 10BASE-T would have a 1498 value of 512 (2**9). In contrast, a MAU which 1499 supports both 10Base-T (full duplex) and 1500 100BASE-TX (full duplex) would have a value of 1501 ((2**11) + (2**16)) or 67584. 1503 The powers of 2 assigned to the capabilities are 1504 these: 1506 Power Capability 1507 0 other or unknown 1508 1 AUI 1509 2 10BASE-5 1510 3 FOIRL 1511 4 10BASE-2 1512 5 10BASE-T duplex mode unknown 1513 6 10BASE-FP 1514 7 10BASE-FB 1515 8 10BASE-FL duplex mode unknown 1516 9 10BROAD36 1517 10 10BASE-T half duplex mode 1518 11 10BASE-T full duplex mode 1519 12 10BASE-FL half duplex mode 1520 13 10BASE-FL full duplex mode 1521 14 100BASE-T4 1522 15 100BASE-TX half duplex mode 1523 16 100BASE-TX full duplex mode 1524 17 100BASE-FX half duplex mode 1525 18 100BASE-FX full duplex mode 1526 19 100BASE-T2 half duplex mode 1527 20 100BASE-T2 full duplex mode 1529 If auto-negotiation is present on this MAU, this 1530 object will map to ifMauAutoNegCapability." 1531 ::= { ifMauEntry 10 } 1533 ifMauDefaultType OBJECT-TYPE 1534 SYNTAX AutonomousType 1535 MAX-ACCESS read-write 1536 STATUS current 1537 DESCRIPTION "This object identifies the default 1538 administrative baseband MAU type, to be used in 1539 conjunction with the operational MAU type 1540 denoted by ifMauType. 1542 The set of possible values for this object is 1543 the same as the set defined for the ifMauType 1544 object. 1546 This object represents the 1547 administratively-configured type of the MAU. If 1548 auto-negotiation is not enabled or is not 1549 implemented for this MAU, the value of this 1550 object determines the operational type of the 1551 MAU. In this case, a set to this object will 1552 force the MAU into the specified operating mode. 1554 If auto-negotiation is implemented and enabled 1555 for this MAU, the operational type of the MAU 1556 is determined by auto-negotiation, and the value 1557 of this object denotes the type to which the MAU 1558 will automatically revert if/when 1559 auto-negotiation is later disabled. 1561 NOTE TO IMPLEMENTORS: It may be necessary to 1562 provide for underlying hardware implementations 1563 which do not follow the exact behavior specified 1564 above. In particular, when 1565 ifMauAutoNegAdminStatus transitions from enabled 1566 to disabled, the agent implementation MUST 1567 ensure that the operational type of the MAU (as 1568 reported by ifMauType) correctly transitions to 1569 the value specified by this object, rather than 1570 continuing to operate at the value earlier 1571 determined by the auto-negotiation function." 1572 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID, and 1573 22.2.4.1.4." 1574 ::= { ifMauEntry 11 } 1576 ifMauAutoNegSupported OBJECT-TYPE 1577 SYNTAX TruthValue 1578 MAX-ACCESS read-only 1579 STATUS current 1580 DESCRIPTION "This object indicates whether or not 1581 auto-negotiation is supported on this MAU." 1582 ::= { ifMauEntry 12 } 1584 ifMauTypeListBits OBJECT-TYPE 1585 SYNTAX BITS { 1586 bOther(0), -- other or unknown 1587 bAUI(1), -- AUI 1588 b10base5(2), -- 10BASE-5 1589 bFoirl(3), -- FOIRL 1591 b10base2(4), -- 10BASE-2 1592 b10baseT(5), -- 10BASE-T duplex mode unknown 1593 b10baseFP(6), -- 10BASE-FP 1594 b10baseFB(7), -- 10BASE-FB 1595 b10baseFL(8), -- 10BASE-FL duplex mode unknown 1596 b10broad36(9), -- 10BROAD36 1597 b10baseTHD(10), -- 10BASE-T half duplex mode 1598 b10baseTFD(11), -- 10BASE-T full duplex mode 1599 b10baseFLHD(12), -- 10BASE-FL half duplex mode 1600 b10baseFLFD(13), -- 10BASE-FL full duplex mode 1602 b100baseT4(14), -- 100BASE-T4 1603 b100baseTXHD(15), -- 100BASE-TX half duplex mode 1604 b100baseTXFD(16), -- 100BASE-TX full duplex mode 1605 b100baseFXHD(17), -- 100BASE-FX half duplex mode 1606 b100baseFXFD(18), -- 100BASE-FX full duplex mode 1607 b100baseT2HD(19), -- 100BASE-T2 half duplex mode 1608 b100baseT2FD(20), -- 100BASE-T2 full duplex mode 1610 b1000baseXHD(21), -- 1000BASE-X half duplex mode 1611 b1000baseXFD(22), -- 1000BASE-X full duplex mode 1612 b1000baseLXHD(23), -- 1000BASE-LX half duplex mode 1613 b1000baseLXFD(24), -- 1000BASE-LX full duplex mode 1614 b1000baseSXHD(25), -- 1000BASE-SX half duplex mode 1615 b1000baseSXFD(26), -- 1000BASE-SX full duplex mode 1616 b1000baseCXHD(27), -- 1000BASE-CX half duplex mode 1617 b1000baseCXFD(28), -- 1000BASE-CX full duplex mode 1618 b1000baseTHD(29), -- 1000BASE-T half duplex mode 1619 b1000baseTFD(30), -- 1000BASE-T full duplex mode 1621 b10GbaseX(31), -- 10GBASE-X 1622 b10GbaseLX4(32), -- 10GBASE-LX4 1623 b10GbaseR(33), -- 10GBASE-R 1624 b10GbaseER(34), -- 10GBASE-ER 1625 b10GbaseLR(35), -- 10GBASE-LR 1626 b10GbaseSR(36), -- 10GBASE-SR 1627 b10GbaseW(37), -- 10GBASE-W 1628 b10GbaseEW(38), -- 10GBASE-EW 1629 b10GbaseLW(39), -- 10GBASE-LW 1630 b10GbaseSW(40) -- 10GBASE-SW 1631 } 1632 MAX-ACCESS read-only 1633 STATUS current 1634 DESCRIPTION "A value that uniquely identifies the set of 1635 possible IEEE 802.3 types that the MAU could be. 1636 If auto-negotiation is present on this MAU, this 1637 object will map to ifMauAutoNegCapabilityBits. 1639 Note that this MAU may be capable of operating 1640 as a MAU type that is beyond the scope of this 1641 MIB. This is indicated by returning the 1642 bit value bOther in addition to any bit values 1643 for capabilities that are listed above." 1644 ::= { ifMauEntry 13 } 1646 ifMauHCFalseCarriers OBJECT-TYPE 1647 SYNTAX Counter64 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION "A count of the number of false carrier events 1651 during IDLE in 100BASE-X and 1000BASE-X links. 1653 For all other MAU types, this counter will 1654 always indicate zero. This counter does not 1655 increment at the symbol rate. 1657 This counter is a 64 bit version of 1658 ifMauFalseCarriers. Since the 32 bit version of 1659 this counter can roll over very quickly, 1660 management stations are advised to poll the 1661 64 bit version instead in order to avoid loss 1662 of information. 1664 Discontinuities in the value of this counter can 1665 occur at re-initialization of the management 1666 system, and at other times as indicated by the 1667 value of ifCounterDiscontinuityTime." 1668 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. 1669 RFC 2863, ifCounterDiscontinuityTime." 1670 ::= { ifMauEntry 14 } 1672 -- The ifJackTable applies to MAUs attached to interfaces 1673 -- which have one or more external jacks (connectors). 1675 ifJackTable OBJECT-TYPE 1676 SYNTAX SEQUENCE OF IfJackEntry 1677 MAX-ACCESS not-accessible 1678 STATUS current 1679 DESCRIPTION "Information about the external jacks attached 1680 to MAUs attached to an interface." 1681 ::= { dot3IfMauBasicGroup 2 } 1683 ifJackEntry OBJECT-TYPE 1684 SYNTAX IfJackEntry 1685 MAX-ACCESS not-accessible 1686 STATUS current 1687 DESCRIPTION "An entry in the table, containing information 1688 about a particular jack." 1689 INDEX { ifMauIfIndex, 1690 ifMauIndex, 1691 ifJackIndex 1692 } 1693 ::= { ifJackTable 1 } 1695 IfJackEntry ::= 1696 SEQUENCE { 1697 ifJackIndex Integer32, 1698 ifJackType JackType 1699 } 1701 ifJackIndex OBJECT-TYPE 1702 SYNTAX Integer32 (1..2147483647) 1703 MAX-ACCESS not-accessible 1704 STATUS current 1705 DESCRIPTION "This variable uniquely identifies the jack 1706 described by this entry from among other jacks 1707 attached to the same MAU." 1708 ::= { ifJackEntry 1 } 1710 ifJackType OBJECT-TYPE 1711 SYNTAX JackType 1712 MAX-ACCESS read-only 1713 STATUS current 1714 DESCRIPTION "The jack connector type, as it appears on the 1715 outside of the system." 1716 ::= { ifJackEntry 2 } 1718 -- 1719 -- The MAU Auto-Negotiation Table 1720 -- 1722 ifMauAutoNegTable OBJECT-TYPE 1723 SYNTAX SEQUENCE OF IfMauAutoNegEntry 1724 MAX-ACCESS not-accessible 1725 STATUS current 1726 DESCRIPTION "Configuration and status objects for the 1727 auto-negotiation function of MAUs attached to 1728 interfaces. 1730 The ifMauAutoNegTable applies to systems in 1731 which auto-negotiation is supported on one or 1732 more MAUs attached to interfaces. Note that if 1733 auto-negotiation is present and enabled, the 1734 ifMauType object reflects the result of the 1735 auto-negotiation function." 1736 ::= { dot3IfMauAutoNegGroup 1 } 1738 ifMauAutoNegEntry OBJECT-TYPE 1739 SYNTAX IfMauAutoNegEntry 1740 MAX-ACCESS not-accessible 1741 STATUS current 1742 DESCRIPTION "An entry in the table, containing configuration 1743 and status information for the auto-negotiation 1744 function of a particular MAU." 1745 INDEX { ifMauIfIndex, 1746 ifMauIndex 1747 } 1748 ::= { ifMauAutoNegTable 1 } 1750 IfMauAutoNegEntry ::= 1751 SEQUENCE { 1752 ifMauAutoNegAdminStatus INTEGER, 1753 ifMauAutoNegRemoteSignaling INTEGER, 1754 ifMauAutoNegConfig INTEGER, 1755 ifMauAutoNegCapability Integer32, 1756 ifMauAutoNegCapAdvertised Integer32, 1757 ifMauAutoNegCapReceived Integer32, 1758 ifMauAutoNegRestart INTEGER, 1759 ifMauAutoNegCapabilityBits BITS, 1760 ifMauAutoNegCapAdvertisedBits BITS, 1761 ifMauAutoNegCapReceivedBits BITS, 1762 ifMauAutoNegRemoteFaultAdvertised INTEGER, 1763 ifMauAutoNegRemoteFaultReceived INTEGER 1764 } 1766 ifMauAutoNegAdminStatus OBJECT-TYPE 1767 SYNTAX INTEGER { 1768 enabled(1), 1769 disabled(2) 1770 } 1771 MAX-ACCESS read-write 1772 STATUS current 1773 DESCRIPTION "Setting this object to enabled(1) will cause 1774 the interface which has the auto-negotiation 1775 signaling ability to be enabled. 1777 If the value of this object is disabled(2) then 1778 the interface will act as it would if it had no 1779 auto-negotiation signaling. Under these 1780 conditions, an IEEE 802.3 MAU will immediately 1781 be forced to the state indicated by the value of 1782 the object ifMauDefaultType. 1784 NOTE TO IMPLEMENTORS: When 1785 ifMauAutoNegAdminStatus transitions from enabled 1786 to disabled, the agent implementation MUST 1787 ensure that the operational type of the MAU (as 1788 reported by ifMauType) correctly transitions to 1789 the value specified by the ifMauDefaultType 1790 object, rather than continuing to operate at the 1791 value earlier determined by the auto-negotiation 1792 function." 1793 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.2, 1794 aAutoNegAdminState and 30.6.1.2.2, 1795 acAutoNegAdminControl." 1796 ::= { ifMauAutoNegEntry 1 } 1798 ifMauAutoNegRemoteSignaling OBJECT-TYPE 1799 SYNTAX INTEGER { 1800 detected(1), 1801 notdetected(2) 1802 } 1803 MAX-ACCESS read-only 1804 STATUS current 1805 DESCRIPTION "A value indicating whether the remote end of 1806 the link is using auto-negotiation signaling. It 1807 takes the value detected(1) if and only if, 1808 during the previous link negotiation, FLP Bursts 1809 were received." 1810 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.3, 1811 aAutoNegRemoteSignaling." 1812 ::= { ifMauAutoNegEntry 2 } 1814 ifMauAutoNegConfig OBJECT-TYPE 1815 SYNTAX INTEGER { 1816 other(1), 1817 configuring(2), 1818 complete(3), 1819 disabled(4), 1820 parallelDetectFail(5) 1821 } 1822 MAX-ACCESS read-only 1823 STATUS current 1824 DESCRIPTION "A value indicating the current status of the 1825 auto-negotiation process. The enumeration 1826 parallelDetectFail(5) maps to a failure in 1827 parallel detection as defined in 28.2.3.1 of 1828 [IEEE 802.3 Std]." 1829 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4, 1830 aAutoNegAutoConfig." 1831 ::= { ifMauAutoNegEntry 4 } 1833 ifMauAutoNegCapability OBJECT-TYPE 1834 SYNTAX Integer32 1835 MAX-ACCESS read-only 1836 STATUS deprecated 1837 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1839 This object has been deprecated in favour of 1840 ifMauAutoNegCapabilityBits. 1842 A value that uniquely identifies the set of 1843 capabilities of the local auto-negotiation 1844 entity. The value is a sum which initially 1845 takes the value zero. Then, for each capability 1846 of this interface, 2 raised to the power noted 1847 below is added to the sum. For example, an 1848 interface which has the capability to support 1849 only 100Base-TX half duplex would have a value 1850 of 32768 (2**15). In contrast, an interface 1851 which supports both 100Base-TX half duplex and 1852 and 100Base-TX full duplex would have a value of 1853 98304 ((2**15) + (2**16)). 1855 The powers of 2 assigned to the capabilities are 1856 these: 1858 Power Capability 1859 0 other or unknown 1860 (1-9) (reserved) 1861 10 10BASE-T half duplex mode 1862 11 10BASE-T full duplex mode 1863 12 (reserved) 1864 13 (reserved) 1865 14 100BASE-T4 1866 15 100BASE-TX half duplex mode 1867 16 100BASE-TX full duplex mode 1868 17 (reserved) 1869 18 (reserved) 1870 19 100BASE-T2 half duplex mode 1871 20 100BASE-T2 full duplex mode 1873 Note that interfaces that support this MIB may 1874 have capabilities that extend beyond the scope 1875 of this MIB." 1876 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, 1877 aAutoNegLocalTechnologyAbility." 1878 ::= { ifMauAutoNegEntry 5 } 1880 ifMauAutoNegCapAdvertised OBJECT-TYPE 1881 SYNTAX Integer32 1882 MAX-ACCESS read-write 1883 STATUS deprecated 1884 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1886 This object has been deprecated in favour of 1887 ifMauAutoNegCapAdvertisedBits. 1889 A value that uniquely identifies the set of 1890 capabilities advertised by the local 1891 auto-negotiation entity. Refer to 1892 ifMauAutoNegCapability for a description of the 1893 possible values of this object. 1895 Capabilities in this object that are not 1896 available in ifMauAutoNegCapability cannot be 1897 enabled." 1898 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 1899 aAutoNegAdvertisedTechnologyAbility." 1900 ::= { ifMauAutoNegEntry 6 } 1902 ifMauAutoNegCapReceived OBJECT-TYPE 1903 SYNTAX Integer32 1904 MAX-ACCESS read-only 1905 STATUS deprecated 1906 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1908 This object has been deprecated in favour of 1909 ifMauAutoNegCapReceivedBits. 1911 A value that uniquely identifies the set of 1912 capabilities received from the remote 1913 auto-negotiation entity. Refer to 1914 ifMauAutoNegCapability for a description of the 1915 possible values of this object. 1917 Note that interfaces that support this MIB may 1918 be attached to remote auto-negotiation entities 1919 which have capabilities beyond the scope of this 1920 MIB." 1921 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 1922 aAutoNegReceivedTechnologyAbility." 1923 ::= { ifMauAutoNegEntry 7 } 1925 ifMauAutoNegRestart OBJECT-TYPE 1926 SYNTAX INTEGER { 1927 restart(1), 1928 norestart(2) 1929 } 1930 MAX-ACCESS read-write 1931 STATUS current 1932 DESCRIPTION "If the value of this object is set to 1933 restart(1) then this will force auto-negotiation 1934 to begin link renegotiation. If auto-negotiation 1935 signaling is disabled, a write to this object 1936 has no effect. 1938 Setting the value of this object to norestart(2) 1939 has no effect." 1940 REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1, 1941 acAutoNegRestartAutoConfig." 1942 ::= { ifMauAutoNegEntry 8 } 1944 ifMauAutoNegCapabilityBits OBJECT-TYPE 1945 SYNTAX BITS { 1946 bOther(0), -- other or unknown 1947 b10baseT(1), -- 10BASE-T half duplex mode 1948 b10baseTFD(2), -- 10BASE-T full duplex mode 1949 b100baseT4(3), -- 100BASE-T4 1950 b100baseTX(4), -- 100BASE-TX half duplex mode 1951 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1952 b100baseT2(6), -- 100BASE-T2 half duplex mode 1953 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1954 bfdxPause(8), -- PAUSE for full-duplex links 1955 bfdxAPause(9), -- Asymmetric PAUSE for full-duplex 1956 -- links 1957 bfdxSPause(10), -- Symmetric PAUSE for full-duplex 1958 -- links 1960 bfdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1961 -- full-duplex links 1962 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1963 -- duplex mode 1964 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1965 -- duplex mode 1966 b1000baseT(14), -- 1000BASE-T half duplex mode 1967 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1968 } 1969 MAX-ACCESS read-only 1970 STATUS current 1971 DESCRIPTION "A value that uniquely identifies the set of 1972 capabilities of the local auto-negotiation 1973 entity. Note that interfaces that support this 1974 MIB may have capabilities that extend beyond the 1975 scope of this MIB. 1977 Note that the local auto-negotiation entity may 1978 support some capabilities beyond the scope of 1979 this MIB. This is indicated by returning the 1980 bit value bOther in addition to any bit values 1981 for capabilities that are listed above." 1982 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, 1983 aAutoNegLocalTechnologyAbility." 1984 ::= { ifMauAutoNegEntry 9 } 1986 ifMauAutoNegCapAdvertisedBits OBJECT-TYPE 1987 SYNTAX BITS { 1988 bOther(0), -- other or unknown 1989 b10baseT(1), -- 10BASE-T half duplex mode 1990 b10baseTFD(2), -- 10BASE-T full duplex mode 1991 b100baseT4(3), -- 100BASE-T4 1992 b100baseTX(4), -- 100BASE-TX half duplex mode 1993 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1994 b100baseT2(6), -- 100BASE-T2 half duplex mode 1995 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1996 bFdxPause(8), -- PAUSE for full-duplex links 1997 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 1998 -- links 1999 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 2000 -- links 2001 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 2002 -- full-duplex links 2003 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 2004 -- duplex mode 2005 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 2006 -- duplex mode 2007 b1000baseT(14), -- 1000BASE-T half duplex mode 2008 b1000baseTFD(15) -- 1000BASE-T full duplex mode 2009 } 2010 MAX-ACCESS read-write 2011 STATUS current 2012 DESCRIPTION "A value that uniquely identifies the set of 2013 capabilities advertised by the local 2014 auto-negotiation entity. 2016 Capabilities in this object that are not 2017 available in ifMauAutoNegCapabilityBits cannot 2018 be enabled. 2020 Note that the local auto-negotiation entity may 2021 advertise some capabilities beyond the scope of 2022 this MIB. This is indicated by returning the 2023 bit value bOther in addition to any bit values 2024 for capabilities that are listed above." 2025 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 2026 aAutoNegAdvertisedTechnologyAbility." 2027 ::= { ifMauAutoNegEntry 10 } 2029 ifMauAutoNegCapReceivedBits OBJECT-TYPE 2030 SYNTAX BITS { 2031 bOther(0), -- other or unknown 2032 b10baseT(1), -- 10BASE-T half duplex mode 2033 b10baseTFD(2), -- 10BASE-T full duplex mode 2034 b100baseT4(3), -- 100BASE-T4 2035 b100baseTX(4), -- 100BASE-TX half duplex mode 2036 b100baseTXFD(5), -- 100BASE-TX full duplex mode 2037 b100baseT2(6), -- 100BASE-T2 half duplex mode 2038 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 2039 bFdxPause(8), -- PAUSE for full-duplex links 2040 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 2041 -- links 2042 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 2043 -- links 2044 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 2045 -- full-duplex links 2046 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 2047 -- duplex mode 2048 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 2049 -- duplex mode 2050 b1000baseT(14), -- 1000BASE-T half duplex mode 2051 b1000baseTFD(15) -- 1000BASE-T full duplex mode 2052 } 2053 MAX-ACCESS read-only 2054 STATUS current 2055 DESCRIPTION "A value that uniquely identifies the set of 2056 capabilities received from the remote 2057 auto-negotiation entity. 2059 Note that interfaces that support this MIB may 2060 be attached to remote auto-negotiation entities 2061 which have capabilities beyond the scope of this 2062 MIB. This is indicated by returning the bit 2063 value bOther in addition to any bit values for 2064 capabilities that are listed above." 2065 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 2066 aAutoNegReceivedTechnologyAbility." 2067 ::= { ifMauAutoNegEntry 11 } 2069 ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE 2070 SYNTAX INTEGER { 2071 noError(1), 2072 offline(2), 2073 linkFailure(3), 2074 autoNegError(4) 2075 } 2076 MAX-ACCESS read-write 2077 STATUS current 2078 DESCRIPTION "A value that identifies any local fault 2079 indications that this MAU has detected and will 2080 advertise at the next auto-negotiation 2081 interaction for 1000Mbps MAUs." 2082 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 2083 aAutoNegAdvertisedTechnologyAbility." 2084 ::= { ifMauAutoNegEntry 12 } 2086 ifMauAutoNegRemoteFaultReceived OBJECT-TYPE 2087 SYNTAX INTEGER { 2088 noError(1), 2089 offline(2), 2090 linkFailure(3), 2091 autoNegError(4) 2092 } 2093 MAX-ACCESS read-only 2094 STATUS current 2095 DESCRIPTION "A value that identifies any fault indications 2096 received from the far end of a link by the 2097 local auto-negotiation entity for 1000Mbps 2098 MAUs." 2099 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 2100 aAutoNegReceivedTechnologyAbility." 2101 ::= { ifMauAutoNegEntry 13 } 2103 -- 2104 -- The Basic Broadband MAU Table 2105 -- 2107 broadMauBasicTable OBJECT-TYPE 2108 SYNTAX SEQUENCE OF BroadMauBasicEntry 2109 MAX-ACCESS not-accessible 2110 STATUS deprecated 2111 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2113 This entire table has been deprecated. There 2114 have been no reported implementations of this 2115 table, and it is unlikely that there ever will 2116 be. IEEE recommends that broadband MAU types 2117 should not be used for new installations. 2119 Table of descriptive and status information 2120 about the broadband MAUs connected to 2121 interfaces." 2122 ::= { dot3BroadMauBasicGroup 1 } 2124 broadMauBasicEntry OBJECT-TYPE 2125 SYNTAX BroadMauBasicEntry 2126 MAX-ACCESS not-accessible 2127 STATUS deprecated 2128 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2130 An entry in the table, containing information 2131 about a single broadband MAU." 2132 INDEX { broadMauIfIndex, 2133 broadMauIndex 2134 } 2135 ::= { broadMauBasicTable 1 } 2137 BroadMauBasicEntry ::= 2138 SEQUENCE { 2139 broadMauIfIndex InterfaceIndex, 2140 broadMauIndex Integer32, 2141 broadMauXmtRcvSplitType INTEGER, 2142 broadMauXmtCarrierFreq Integer32, 2143 broadMauTranslationFreq Integer32 2144 } 2146 broadMauIfIndex OBJECT-TYPE 2147 SYNTAX InterfaceIndex 2148 MAX-ACCESS read-only -- read-only since originally an 2149 -- SMIv1 index 2150 STATUS deprecated 2151 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2153 This variable uniquely identifies the interface 2154 to which the MAU described by this entry is 2155 connected." 2156 REFERENCE "Reference RFC 2863, ifIndex." 2157 ::= { broadMauBasicEntry 1 } 2159 broadMauIndex OBJECT-TYPE 2160 SYNTAX Integer32 (1..2147483647) 2161 MAX-ACCESS read-only -- read-only since originally an 2162 -- SMIv1 index 2163 STATUS deprecated 2164 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2166 This variable uniquely identifies the MAU 2167 connected to interface broadMauIfIndex that is 2168 described by this entry." 2169 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 2170 ::= { broadMauBasicEntry 2 } 2172 broadMauXmtRcvSplitType OBJECT-TYPE 2173 SYNTAX INTEGER { 2174 other(1), 2175 single(2), 2176 dual(3) 2177 } 2178 MAX-ACCESS read-only 2179 STATUS deprecated 2180 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2182 This object indicates the type of frequency 2183 multiplexing/cabling system used to separate the 2184 transmit and receive paths for the 10BROAD36 2185 MAU. 2187 The value other(1) is returned if the split type 2188 is not either single or dual. 2190 The value single(2) indicates a single cable 2191 system. The value dual(3) indicates a dual 2192 cable system, offset normally zero." 2193 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.8, 2194 aBbMAUXmitRcvSplitType." 2195 ::= { broadMauBasicEntry 3 } 2197 broadMauXmtCarrierFreq OBJECT-TYPE 2198 SYNTAX Integer32 2199 MAX-ACCESS read-only 2200 STATUS deprecated 2201 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2203 This variable indicates the transmit carrier 2204 frequency of the 10BROAD36 MAU in MHz/4; that 2205 is, in units of 250 kHz." 2206 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, 2207 aBroadbandFrequencies.xmitCarrierFrequency." 2208 ::= { broadMauBasicEntry 4 } 2210 broadMauTranslationFreq OBJECT-TYPE 2211 SYNTAX Integer32 2212 MAX-ACCESS read-only 2213 STATUS deprecated 2214 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2216 This variable indicates the translation offset 2217 frequency of the 10BROAD36 MAU in MHz/4; that 2218 is, in units of 250 kHz." 2219 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, 2220 aBroadbandFrequencies.translationFrequency." 2221 ::= { broadMauBasicEntry 5 } 2223 -- Notifications for use by 802.3 MAUs 2225 snmpDot3MauTraps OBJECT IDENTIFIER ::= { snmpDot3MauMgt 0 } 2227 rpMauJabberTrap NOTIFICATION-TYPE 2228 OBJECTS { rpMauJabberState } 2229 STATUS current 2230 DESCRIPTION "This trap is sent whenever a managed repeater 2231 MAU enters the jabber state. 2233 The agent MUST throttle the generation of 2234 consecutive rpMauJabberTraps so that there is at 2235 least a five-second gap between them." 2236 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 2237 notification." 2238 ::= { snmpDot3MauTraps 1 } 2240 ifMauJabberTrap NOTIFICATION-TYPE 2241 OBJECTS { ifMauJabberState } 2242 STATUS current 2243 DESCRIPTION "This trap is sent whenever a managed interface 2244 MAU enters the jabber state. 2246 The agent MUST throttle the generation of 2247 consecutive ifMauJabberTraps so that there is at 2248 least a five-second gap between them." 2249 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 2250 notification." 2251 ::= { snmpDot3MauTraps 2 } 2253 -- Conformance information 2255 mauModConf 2256 OBJECT IDENTIFIER ::= { mauMod 1 } 2257 mauModCompls 2258 OBJECT IDENTIFIER ::= { mauModConf 1 } 2259 mauModObjGrps 2260 OBJECT IDENTIFIER ::= { mauModConf 2 } 2261 mauModNotGrps 2262 OBJECT IDENTIFIER ::= { mauModConf 3 } 2264 -- Object groups 2266 mauRpGrpBasic OBJECT-GROUP 2267 OBJECTS { rpMauGroupIndex, 2268 rpMauPortIndex, 2269 rpMauIndex, 2270 rpMauType, 2271 rpMauStatus, 2272 rpMauMediaAvailable, 2273 rpMauMediaAvailableStateExits, 2274 rpMauJabberState, 2275 rpMauJabberingStateEnters 2276 } 2277 STATUS current 2278 DESCRIPTION "Basic conformance group for MAUs attached to 2279 repeater ports. This group is also the 2280 conformance specification for RFC 1515 2281 implementations." 2282 ::= { mauModObjGrps 1 } 2284 mauRpGrp100Mbs OBJECT-GROUP 2285 OBJECTS { rpMauFalseCarriers } 2286 STATUS current 2287 DESCRIPTION "Conformance group for MAUs attached to 2288 repeater ports with 100 Mb/s or greater 2289 capability." 2290 ::= { mauModObjGrps 2 } 2292 mauRpGrpJack OBJECT-GROUP 2293 OBJECTS { rpJackType } 2294 STATUS current 2295 DESCRIPTION "Conformance group for MAUs attached to 2296 repeater ports with managed jacks." 2297 ::= { mauModObjGrps 3 } 2299 mauIfGrpBasic OBJECT-GROUP 2300 OBJECTS { ifMauIfIndex, 2301 ifMauIndex, 2302 ifMauType, 2303 ifMauStatus, 2304 ifMauMediaAvailable, 2305 ifMauMediaAvailableStateExits, 2306 ifMauJabberState, 2307 ifMauJabberingStateEnters 2308 } 2309 STATUS current 2310 DESCRIPTION "Basic conformance group for MAUs attached to 2311 interfaces. This group also provides a 2312 conformance specification for RFC 1515 2313 implementations." 2314 ::= { mauModObjGrps 4 } 2316 mauIfGrp100Mbs OBJECT-GROUP 2317 OBJECTS { ifMauFalseCarriers, 2318 ifMauTypeList, 2319 ifMauDefaultType, 2320 ifMauAutoNegSupported 2321 } 2322 STATUS deprecated 2323 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2325 Conformance group for MAUs attached to 2326 interfaces with 100 Mb/s capability. 2328 This object group has been deprecated in favor 2329 of mauIfGrpHighCapacity." 2330 ::= { mauModObjGrps 5 } 2332 mauIfGrpJack OBJECT-GROUP 2333 OBJECTS { ifJackType } 2334 STATUS current 2335 DESCRIPTION "Conformance group for MAUs attached to 2336 interfaces with managed jacks." 2337 ::= { mauModObjGrps 6 } 2339 mauIfGrpAutoNeg OBJECT-GROUP 2340 OBJECTS { ifMauAutoNegAdminStatus, 2341 ifMauAutoNegRemoteSignaling, 2342 ifMauAutoNegConfig, 2343 ifMauAutoNegCapability, 2344 ifMauAutoNegCapAdvertised, 2345 ifMauAutoNegCapReceived, 2346 ifMauAutoNegRestart 2347 } 2348 STATUS deprecated 2349 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2351 Conformance group for MAUs attached to 2352 interfaces with managed auto-negotiation. 2354 This object group has been deprecated in favor 2355 of mauIfGrpAutoNeg2." 2356 ::= { mauModObjGrps 7 } 2358 mauBroadBasic OBJECT-GROUP 2359 OBJECTS { broadMauIfIndex, 2360 broadMauIndex, 2361 broadMauXmtRcvSplitType, 2362 broadMauXmtCarrierFreq, 2363 broadMauTranslationFreq 2364 } 2365 STATUS deprecated 2366 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2368 Conformance group for broadband MAUs attached 2369 to interfaces. 2371 This object group is deprecated. There have 2372 been no reported implementations of this group, 2373 and it was felt to be unlikely that there will 2374 be any future implementations." 2375 ::= { mauModObjGrps 8 } 2377 mauIfGrpHighCapacity OBJECT-GROUP 2378 OBJECTS { ifMauFalseCarriers, 2379 ifMauTypeListBits, 2380 ifMauDefaultType, 2381 ifMauAutoNegSupported 2382 } 2383 STATUS current 2384 DESCRIPTION "Conformance group for MAUs attached to 2385 interfaces with 100 Mb/s or greater capability." 2386 ::= { mauModObjGrps 9 } 2388 mauIfGrpAutoNeg2 OBJECT-GROUP 2389 OBJECTS { ifMauAutoNegAdminStatus, 2390 ifMauAutoNegRemoteSignaling, 2391 ifMauAutoNegConfig, 2392 ifMauAutoNegCapabilityBits, 2393 ifMauAutoNegCapAdvertisedBits, 2394 ifMauAutoNegCapReceivedBits, 2395 ifMauAutoNegRestart 2396 } 2397 STATUS current 2398 DESCRIPTION "Conformance group for MAUs attached to 2399 interfaces with managed auto-negotiation." 2400 ::= { mauModObjGrps 10 } 2402 mauIfGrpAutoNeg1000Mbps OBJECT-GROUP 2403 OBJECTS { ifMauAutoNegRemoteFaultAdvertised, 2404 ifMauAutoNegRemoteFaultReceived 2405 } 2406 STATUS current 2407 DESCRIPTION "Conformance group for 1000Mbps MAUs attached to 2408 interfaces with managed auto-negotiation." 2409 ::= { mauModObjGrps 11 } 2411 mauIfGrpHCStats OBJECT-GROUP 2412 OBJECTS { ifMauHCFalseCarriers } 2413 STATUS current 2414 DESCRIPTION "Conformance for high capacity statistics for 2415 MAUs attached to interfaces" 2416 ::= { mauModObjGrps 12 } 2418 -- Notification groups 2420 rpMauNotifications NOTIFICATION-GROUP 2421 NOTIFICATIONS { rpMauJabberTrap } 2422 STATUS current 2423 DESCRIPTION "Notifications for repeater MAUs." 2424 ::= { mauModNotGrps 1 } 2426 ifMauNotifications NOTIFICATION-GROUP 2427 NOTIFICATIONS { ifMauJabberTrap } 2428 STATUS current 2429 DESCRIPTION "Notifications for interface MAUs." 2430 ::= { mauModNotGrps 2 } 2432 -- Compliances 2433 mauModRpCompl MODULE-COMPLIANCE 2434 STATUS deprecated 2435 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2437 Compliance for MAUs attached to repeater 2438 ports. 2440 This compliance is deprecated and replaced by 2441 mauModRpCompl2, which corrects an oversight by 2442 allowing rpMauStatus to be implemented 2443 read-only." 2445 MODULE -- this module 2446 MANDATORY-GROUPS { mauRpGrpBasic } 2448 GROUP mauRpGrp100Mbs 2449 DESCRIPTION "Implementation of this optional group is 2450 recommended for MAUs which have 100Mb/s or 2451 greater capability." 2453 GROUP mauRpGrpJack 2454 DESCRIPTION "Implementation of this optional group is 2455 recommended for MAUs which have one or more 2456 external jacks." 2458 GROUP rpMauNotifications 2459 DESCRIPTION "Implementation of this group is recommended 2460 for MAUs attached to repeater ports." 2461 ::= { mauModCompls 1 } 2463 mauModIfCompl MODULE-COMPLIANCE 2464 STATUS deprecated 2465 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2467 Compliance for MAUs attached to interfaces. 2469 This compliance is deprecated and replaced by 2470 mauModIfCompl2." 2472 MODULE -- this module 2473 MANDATORY-GROUPS { mauIfGrpBasic } 2475 GROUP mauIfGrp100Mbs 2476 DESCRIPTION "Implementation of this optional group is 2477 recommended for MAUs which have 100Mb/s 2478 capability." 2480 GROUP mauIfGrpJack 2481 DESCRIPTION "Implementation of this optional group is 2482 recommended for MAUs which have one or more 2483 external jacks." 2485 GROUP mauIfGrpAutoNeg 2486 DESCRIPTION "Implementation of this group is mandatory 2487 for MAUs which support managed 2488 auto-negotiation." 2490 GROUP mauBroadBasic 2491 DESCRIPTION "Implementation of this group is mandatory 2492 for broadband MAUs." 2494 GROUP ifMauNotifications 2495 DESCRIPTION "Implementation of this group is recommended 2496 for MAUs attached to interfaces." 2497 ::= { mauModCompls 2 } 2499 mauModIfCompl2 MODULE-COMPLIANCE 2500 STATUS deprecated 2501 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2503 Compliance for MAUs attached to interfaces. 2505 This compliance is deprecated and replaced by 2506 mauModIfCompl3." 2508 MODULE -- this module 2509 MANDATORY-GROUPS { mauIfGrpBasic } 2511 GROUP mauIfGrpHighCapacity 2512 DESCRIPTION "Implementation of this optional group is 2513 recommended for MAUs which have 100Mb/s 2514 or greater capability." 2516 GROUP mauIfGrpJack 2517 DESCRIPTION "Implementation of this optional group is 2518 recommended for MAUs which have one or more 2519 external jacks." 2521 GROUP mauIfGrpAutoNeg2 2522 DESCRIPTION "Implementation of this group is mandatory 2523 for MAUs which support managed 2524 auto-negotiation." 2526 GROUP mauIfGrpAutoNeg1000Mbps 2527 DESCRIPTION "Implementation of this group is mandatory 2528 for MAUs which have 1000Mb/s or greater 2529 capability and support managed 2530 auto-negotiation." 2532 GROUP ifMauNotifications 2533 DESCRIPTION "Implementation of this group is recommended 2534 for MAUs attached to interfaces." 2536 OBJECT ifMauStatus 2537 MIN-ACCESS read-only 2538 DESCRIPTION "Write access is not required." 2539 ::= { mauModCompls 3 } 2541 mauModRpCompl2 MODULE-COMPLIANCE 2542 STATUS current 2543 DESCRIPTION "Compliance for MAUs attached to repeater 2544 ports. 2546 Note that compliance with this compliance 2547 statement requires compliance with the 2548 snmpRptrModCompl MODULE-COMPLIANCE statement of 2549 the SNMP-REPEATER-MIB [RFC2108]." 2551 MODULE -- this module 2552 MANDATORY-GROUPS { mauRpGrpBasic } 2554 GROUP mauRpGrp100Mbs 2555 DESCRIPTION "Implementation of this optional group is 2556 recommended for MAUs which have 100Mb/s or 2557 greater capability." 2559 GROUP mauRpGrpJack 2560 DESCRIPTION "Implementation of this optional group is 2561 recommended for MAUs which have one or more 2562 external jacks." 2564 GROUP rpMauNotifications 2565 DESCRIPTION "Implementation of this group is recommended 2566 for MAUs attached to repeater ports." 2568 OBJECT rpMauStatus 2569 MIN-ACCESS read-only 2570 DESCRIPTION "Write access is not required." 2571 ::= { mauModCompls 4 } 2573 mauModIfCompl3 MODULE-COMPLIANCE 2574 STATUS current 2575 DESCRIPTION "Compliance for MAUs attached to interfaces. 2577 Note that compliance with this compliance 2578 statement requires compliance with the 2579 ifCompliance3 MODULE-COMPLIANCE statement of the 2580 IF-MIB [RFC2863] and the dot3Compliance2 2581 MODULE-COMPLIANCE statement of the 2582 EtherLike-MIB [ETHERIF]." 2584 MODULE -- this module 2585 MANDATORY-GROUPS { mauIfGrpBasic } 2587 GROUP mauIfGrpHighCapacity 2588 DESCRIPTION "Implementation of this optional group is 2589 recommended for MAUs which have 100Mb/s 2590 or greater capability." 2592 GROUP mauIfGrpHCStats 2593 DESCRIPTION "Implemention of this group is mandatory 2594 for MAUs which have 1000Mb/s capacity, and 2595 is recommended for MAUs which have 100Mb/s 2596 capacity." 2598 GROUP mauIfGrpJack 2599 DESCRIPTION "Implementation of this optional group is 2600 recommended for MAUs which have one or more 2601 external jacks." 2603 GROUP mauIfGrpAutoNeg2 2604 DESCRIPTION "Implementation of this group is mandatory 2605 for MAUs which support managed 2606 auto-negotiation." 2608 GROUP mauIfGrpAutoNeg1000Mbps 2609 DESCRIPTION "Implementation of this group is mandatory 2610 for MAUs which have 1000Mb/s or greater 2611 capability and support managed 2612 auto-negotiation." 2614 GROUP ifMauNotifications 2615 DESCRIPTION "Implementation of this group is recommended 2616 for MAUs attached to interfaces." 2618 OBJECT ifMauStatus 2619 MIN-ACCESS read-only 2620 DESCRIPTION "Write access is not required." 2621 ::= { mauModCompls 5 } 2623 END 2625 5. Intellectual Property 2627 The IETF takes no position regarding the validity or scope of any 2628 intellectual property or other rights that might be claimed to 2629 pertain to the implementation or use of the technology described in 2630 this document or the extent to which any license under such rights 2631 might or might not be available; neither does it represent that it 2632 has made any effort to identify any such rights. Information on the 2633 IETF's procedures with respect to rights in standards-track and 2634 standards-related documentation can be found in BCP-11. Copies of 2635 claims of rights made available for publication and any assurances of 2636 licenses to be made available, or the result of an attempt made to 2637 obtain a general license or permission for the use of such 2638 proprietary rights by implementors or users of this specification can 2639 be obtained from the IETF Secretariat. 2641 The IETF invites any interested party to bring to its attention any 2642 copyrights, patents or patent applications, or other proprietary 2643 rights which may cover technology that may be required to practice 2644 this standard. Please address the information to the IETF Executive 2645 Director. 2647 6. Acknowledgements 2649 This document was produced by the IETF Ethernet Interfaces and Hub 2650 MIB Working Group, whose efforts were greatly advanced by the 2651 contributions of the following people: 2653 Mike Ayers 2654 Mike Heard 2655 Chuck Black 2656 John Flick 2657 Jeff Johnson 2658 Kam Lam 2659 Leon Leong 2660 Mike Lui 2661 Kerry McDonald 2662 K.C. Norseth 2663 Dave Perkins 2664 Dan Romascanu 2665 Andrew Smith 2666 Kaj Tesink 2667 Geoff Thompson 2668 Maurice Turcotte 2669 Paul Woodruff 2671 This document is based on the Proposed Standard MAU MIB, RFC 2668 2673 [RFC2668], edited by John Flick of Hewlett-Packard and Andrew Smith, 2674 then of Extreme Networks, and produced by the Ethernet Interfaces and 2675 Hub MIB Working Group. It extends that document by providing 2676 suppport for 10 Gb/s MAUs as defined in [IEEE802.3ae]. 2678 RFC 2668, in turn, was based on the Proposed Standard MAU MIB, RFC 2679 2239 [RFC2239], edited by Kathryn de Graaf, then of 3Com, and Dan 2680 Romascanu, then of Madge Networks, and produced by the Ethernet 2681 Interfaces and Hub MIB Working Group. It extended that document by 2682 providing support for 1000 Mb/sec MAUs as defined in [IEEE802.3]. 2684 RFC 2239, in turn, was based on the Proposed Standard MAU MIB, RFC 2685 1515 [RFC1515], edited by Donna McMaster, then of SynOptics 2686 Communications, Keith McCloghrie, then of Hughes LAN Systems, and Sam 2687 Roberts, then of Farallon Computing, and produced by the Hub MIB 2688 Working Group. It extends that document by providing support for 100 2689 Mb/sec MAUs, full duplex MAUs, and auto-negotiation, as defined in 2690 [IEEE802.3]. 2692 7. Normative References 2694 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2695 Requirements Levels", BCP 14, RFC 2119, March 1997. 2697 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2698 J., Rose, M. and S. Waldbusser, "Structure of 2699 Management Information Version 2 (SMIv2)", STD 58, RFC 2700 2578, April 1999. 2702 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2703 J., Rose, M. and S. Waldbusser, "Textual Conventions 2704 for SMIv2", STD 58, RFC 2579, April 1999. 2706 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2707 J., Rose, M. and S. Waldbusser, "Conformance Statements 2708 for SMIv2", STD 58, RFC 2580, April 1999. 2710 [IEEE802.3] IEEE, IEEE Std 802.3, 2002 Edition: "Carrier Sense 2711 Multiple Access with Collision Detection (CSMA/CD) 2712 Access Method and Physical Layer Specifications", 2713 March 2002. 2715 [IEEE802.3ae] IEEE, IEEE Std 802.3ae-2002, "Amendment: Media 2716 Access Control (MAC) Parameters, Physical Layers, 2717 and Management Parameters for 10 Gb/s Operation", 2718 August, 2002. 2720 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces 2721 Group MIB using SMIv2", RFC 2863, June 2000. 2723 [RFC2108] de Graaf, K., D. Romascanu, D. McMaster, and K. 2724 McCloghrie, "Definitions of Managed Objects for IEEE 2725 802.3 Repeater Devices using SMIv2", RFC 2108, February 2726 1997. 2728 [ETHERIF] Flick, J., "Definitions of Managed Objects for the 2729 Ethernet-like Interface Types", work in progress, 2730 draft-ietf-hubmib-etherif-mib-v3-02.txt, March, 2003. 2732 8. Informative References 2734 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2735 "Introduction and Applicability Statements for 2736 Internet-Standard Network Management Framework", 2737 RFC 3410, December 2002. 2739 [RFC3418] Presuhn, R., Case, J., McCloghrie, K., Rose, M. and S. 2740 Waldbusser, "Management Information Base (MIB) for the 2741 Simple Network Management Protocol (SNMP)", RFC 3418, 2742 December 2002. 2744 [RFC2668] Smith, A., Flick, J., deGraaf, K., Romascanu, D., 2745 McMaster, D., McCloghrie, K. and S. Roberts, 2746 "Definitions of Managed Objects for IEEE 802.3 Medium 2747 Attachment Units (MAUs)", RFC 2668, August 1999. 2749 [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, 2750 K. and S. Roberts, "Definitions of Managed Objects for 2751 IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", 2752 RFC 2239, November 1997. 2754 [RFC1515] McMaster, D., McCloghrie, K. and S. Roberts, 2755 "Definitions of Managed Objects for IEEE 802.3 Medium 2756 Attachment Units (MAUs)", RFC 1515, September 1993. 2758 [ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald, 2759 K., Norseth, K. C., and K. Tesink, "Definitions of 2760 Managed Objects for the Ethernet WAN Interface 2761 Sublayer", work in progress, 2762 draft-ietf-hubmib-wis-mib-04.txt, May 2002. 2764 9. Security Considerations 2766 There are a number of management objects defined in this MIB that 2767 have a MAX-ACCESS clause of read-write. Setting these objects can 2768 have a serious effect on the operation of the network, including: 2770 enabling or disabling a MAU 2771 changing a MAU's default type 2772 enabling, disabling or restarting autonegotiation 2773 modifying the capabilities that a MAU advertizes during 2774 autonegotiation. 2776 Such objects may be considered sensitive or vulnerable in some 2777 network environments. The support for SET operations in a non-secure 2778 environment without proper protection can have a negative effect on 2779 network operations. 2781 Some of the readable objects in this MIB module (i.e., objects with a 2782 MAX-ACCESS other than not-accessible) may be considered sensitive or 2783 vulnerable in some network environments. In some environments it may 2784 be undesirable to allow unauthorized parties to access statistics or 2785 status information about individual links in a network. It is thus 2786 important to control even GET and/or NOTIFY access to these objects 2787 and possibly to even encrypt the values of these objects when sending 2788 them over the network via SNMP. 2790 SNMP versions prior to SNMPv3 did not include adequate security. 2791 Even if the network itself is secure (for example by using IPSec), 2792 even then, there is no control as to who on the secure network is 2793 allowed to access and GET/SET (read/change/create/delete) the objects 2794 in this MIB module. 2796 It is recommended that the implementors consider the security 2797 features as provided by the SNMPv3 framework (see [RFC3410], section 2798 8), including full support for the SNMPv3 cryptographic mechanisms 2799 (for authentication and privacy). 2801 Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT 2802 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2803 enable cryptographic security. It is then a customer/operator 2804 responsibility to ensure that the SNMP entity giving access to an 2805 instance of this MIB module is properly configured to give access to 2806 the objects only to those principals (users) that have legitimate 2807 rights to indeed GET or SET (change/create/delete) them. 2809 10. Authors' Addresses 2811 John Flick 2812 Hewlett-Packard Company 2813 8000 Foothills Blvd. M/S 5557 2814 Roseville, CA 95747-5557 2815 Phone: +1 916 785 4018 2816 E-mail: johnf@rose.hp.com 2818 A. Change Log 2820 A.1. Changes since RFC 2668 2822 This section enumerates changes made to RFC 2668 to produce this 2823 document. 2825 (1) Updated references to the IEEE 802.3 standard to 2826 refer to the 2000 edition. 2828 (2) Added reference to 802.3ae. 2830 (3) Updated WG e-mail address. 2832 (4) The following DESCRIPTION clauses have been updated 2833 to reflect behaviour on 10 Gb/s interfaces: 2834 ifMauMediaAvailable. 2836 (5) OBJECT-IDENTITY definitions have been added for 10 gigabit 2837 MAU types. 2839 (6) Enumerations for 'pmdLinkFault', 'wisFrameLoss', 2840 'wisSignalLoss', pcsLinkFault', excessiveBER', 2841 'dxsLinkFault' and 'pxsLinkFault' have been 2842 added for the ifMauMediaAvailable object. 2844 (7) ifMauTypeListBits has been extended with bits for the 2845 10 Gb/s MAU types. 2847 (8) The MODULE-IDENTITY clause has been updated to 2848 reflect the changes in the MIB module. 2850 (9) MIB boilerplate in section 2 has been updated to the 2851 latest approved text. 2853 (10) Added 64-bit version of ifMauFalseCarriers, and updated 2854 compliances accordingly. 2856 (11) Added section on mapping of IEEE managed objects to the 2857 objects in this MIB module. 2859 A.2. Changes between RFC 2239 and RFC 2668 2860 This section enumerates the changes made to RFC 2239 to produce RFC 2861 2668. 2863 (1) The MODULE-IDENTITY has been updated to reflect the changes 2864 in the MIB. 2866 (2) OBJECT-IDENTITY definitions have been added for gigabit MAU 2867 types. 2869 (3) The ifMauTypeList, ifMauAutoNegCapability, 2870 ifMauAutoNegCapAdvertised and ifMauAutoNegCapReceived 2871 objects have been deprecated and replaced by 2872 ifMauTypeListBits, ifMauAutoNegCapabilityBits, 2873 ifMauAutoNegCapAdvertisedBits and 2874 ifMauAutoNegCapReceivedBits. 2876 (4) Two new objects, ifMauAutoNegRemoteFaultAdvertised and 2877 ifMauAutoNegRemoteFaultReceived have been added. 2879 (5) Enumerations for 'offline' and 'autoNegError' have been 2880 added for the rpMauMediaAvailable and ifMauMediaAvailable 2881 objects. 2883 (6) The broadMauBasicTable and mauBroadBasic object group have 2884 been deprecated. 2886 (7) The mauIfGrp100Mbs and mauIfGrpAutoNeg object groups have 2887 been deprecated and replaced by mauIfGrpHighCapacity and 2888 mauIfGrpAutoNeg2. 2890 (8) A new object group, mauIfGrpAutoNeg1000Mbps, has been added. 2892 (9) The mauModIfCompl and mauModRpCompl compliances have been 2893 deprecated and replaced by mauModIfCompl2 and 2894 mauModRpCompl2. 2896 (10) Added section on relationship to RFC 2239. 2898 (11) Updated the SNMP Network Management Framework boilerplate. 2900 (12) Refer to the Interfaces MIB, rather than the interfaces 2901 group of MIB-II. 2903 (13) Updated references to refer to latest edition of IEEE 802.3. 2905 (14) An intellectual property notice was added, as required by 2906 RFC 2026. 2908 B. Full Copyright Statement 2910 Copyright (C) The Internet Society (2002). All Rights Reserved. 2912 This document and translations of it may be copied and furnished to 2913 others, and derivative works that comment on or otherwise explain it 2914 or assist in its implementation may be prepared, copied, published 2915 and distributed, in whole or in part, without restriction of any 2916 kind, provided that the above copyright notice and this paragraph are 2917 included on all such copies and derivative works. However, this 2918 document itself may not be modified in any way, such as by removing 2919 the copyright notice or references to the Internet Society or other 2920 Internet organizations, except as needed for the purpose of 2921 developing Internet standards in which case the procedures for 2922 copyrights defined in the Internet Standards process must be 2923 followed, or as required to translate it into languages other than 2924 English. 2926 The limited permissions granted above are perpetual and will not be 2927 revoked by the Internet Society or its successors or assigns. 2929 This document and the information contained herein is provided on an 2930 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 2931 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 2932 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 2933 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 2934 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.