idnits 2.17.1 draft-ietf-hubmib-mau-mib-v3-02.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 is 1 instance of too long lines in the document, the longest one being 2 characters in excess of 72. == 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 335 has weird spacing: '...Ability ifMa...' == Line 352 has weird spacing: '...Ability isoe...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 2002) is 8010 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) -- Looks like a reference, but probably isn't: '16' on line 1324 -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.3' == Outdated reference: A later version (-03) exists of draft-ietf-hubmib-etherif-mib-v3-02 -- Obsolete informational reference (is this intentional?): RFC 2571 (Obsoleted by RFC 3411) -- Obsolete informational reference (is this intentional?): RFC 1906 (Obsoleted by RFC 3417) -- Obsolete informational reference (is this intentional?): RFC 2572 (Obsoleted by RFC 3412) -- Obsolete informational reference (is this intentional?): RFC 2574 (Obsoleted by RFC 3414) -- Obsolete informational reference (is this intentional?): RFC 1905 (Obsoleted by RFC 3416) -- Obsolete informational reference (is this intentional?): RFC 2573 (Obsoleted by RFC 3413) -- Obsolete informational reference (is this intentional?): RFC 2575 (Obsoleted by RFC 3415) -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) -- Obsolete informational reference (is this intentional?): RFC 1907 (Obsoleted by RFC 3418) -- 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: 5 errors (**), 0 flaws (~~), 7 warnings (==), 18 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Ethernet Interfaces and Hub MIB Working Group Editor of this version: 3 INTERNET DRAFT J. Flick 4 Hewlett-Packard Company 6 Editors of previous versions: 7 A. Smith 8 Allegro Networks 9 J. Flick 10 Hewlett-Packard Company 11 K. de Graaf 12 Argon Networks 13 D. Romascanu 14 Avaya Inc. 15 D. McMaster 16 Cisco Systems, Inc. 17 K. McCloghrie 18 Cisco Systems, Inc. 19 S. Roberts 20 Farallon Computing, Inc. 21 May 2002 23 Definitions of Managed Objects for 24 IEEE 802.3 Medium Attachment Units (MAUs) 26 28 Status of this Memo 30 This document is an Internet-Draft and is in full conformance with 31 all provisions of Section 10 of RFC2026. 33 Internet-Drafts are working documents of the Internet Engineering 34 Task Force (IETF), its areas, and its working groups. Note that 35 other groups may also distribute working documents as Internet- 36 Drafts. 38 Internet-Drafts are draft documents valid for a maximum of six months 39 and may be updated, replaced, or obsoleted by other documents at any 40 time. It is inappropriate to use Internet- Drafts as reference 41 material or to cite them other than as "work in progress." 43 The list of current Internet-Drafts can be accessed at 44 http://www.ietf.org/ietf/1id-abstracts.txt 46 To view the list Internet-Draft Shadow Directories, see 47 http://www.ietf.org/shadow.html. 49 Copyright Notice 51 Copyright (C) The Internet Society (2002). All Rights Reserved. 53 Abstract 55 This memo defines a portion of the Management Information Base (MIB) 56 for use with network management protocols in the Internet community. 57 This memo obsoletes RFC 2668, ''Definitions of Managed Objects for 58 IEEE 802.3 Medium Attachment Units (MAUs)''. This memo extends that 59 specification by including management information useful for the 60 management of 10 gigabit per second (Gb/s) MAUs. This memo also 61 obsoletes RFC 1515, ''Definitions of Managed Objects for IEEE 802.3 62 Medium Attachment Units (MAUs)''. 64 Ethernet technology, as defined by the 802.3 Working Group of the 65 IEEE, continues to evolve, with scalable increases in speed, new 66 types of cabling and interfaces, and new features. This evolution 67 may require changes in the managed objects in order to reflect this 68 new functionality. This document, as with other documents issued by 69 this working group, reflects a certain stage in the evolution of 70 Ethernet technology. In the future, this document might be revised, 71 or new documents might be issued by the Ethernet Interfaces and Hub 72 MIB Working Group, in order to reflect the evolution of Ethernet 73 technology. 75 Distribution of this memo is unlimited. Please forward comments to 76 hubmib@ietf.org. 78 Table of Contents 80 1. Introduction ............................................... 3 81 2. The SNMP Management Framework .............................. 3 82 3. Overview ................................................... 4 83 3.1. Relationship to RFC 2668 ................................. 4 84 3.2. Relationship to RFC 2239 ................................. 5 85 3.3. Relationship to RFC 1515 ................................. 5 86 3.5. Relationship to Other MIBs ............................... 5 87 3.5.1. Relationship to the Interfaces MIB ..................... 5 88 3.5.2. Relationship to the 802.3 Repeater MIB ................. 6 89 3.6. Management of Internal MAUs .............................. 6 90 3.7. Mapping of IEEE 802.3 Managed Objects .................... 7 91 4. Definitions ................................................ 8 92 5. Intellectual Property ...................................... 55 93 6. Acknowledgements ........................................... 56 94 7. References ................................................. 56 95 8. Security Considerations .................................... 59 96 9. Authors' Addresses ......................................... 59 97 A. Change Log ................................................. 59 98 A.1. Changes since RFC 2668 ................................... 59 99 A.2. Changes between RFC 2239 and RFC 2668 .................... 60 100 B. Full Copyright Statement ................................... 61 102 1. Introduction 104 This memo defines a portion of the Management Information Base (MIB) 105 for use with network management protocols in the Internet community. 106 In particular, it defines objects for managing IEEE 802.3 Medium 107 Attachment Units (MAUs). 109 This memo also includes a MIB module. This MIB module extends the 110 list of managed objects specified in the earlier version of this MIB: 111 RFC 2668 [RFC2668]. 113 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 114 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 115 document are to be interpreted as described in [RFC2119]. 117 2. The SNMP Management Framework 119 The SNMP Management Framework presently consists of five major 120 components: 122 o An overall architecture, described in RFC 2571 [RFC2571]. 124 o Mechanisms for describing and naming objects and events for the 125 purpose of management. The first version of this Structure of 126 Management Information (SMI) is called SMIv1 and described in 127 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 128 1215 [RFC1215]. The second version, called SMIv2, is described 129 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 130 STD 58, RFC 2580 [RFC2580]. 132 o Message protocols for transferring management information. The 133 first version of the SNMP message protocol is called SNMPv1 and 134 described in STD 15, RFC 1157 [RFC1157]. A second version of 135 the SNMP message protocol, which is not an Internet standards 136 track protocol, is called SNMPv2c and described in RFC 1901 137 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 138 message protocol is called SNMPv3 and described in RFC 1906 139 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 141 o Protocol operations for accessing management information. The 142 first set of protocol operations and associated PDU formats is 143 described in STD 15, RFC 1157 [RFC1157]. A second set of 144 protocol operations and associated PDU formats is described in 145 RFC 1905 [RFC1905]. 147 o A set of fundamental applications described in RFC 2573 148 [RFC2573] and the view-based access control mechanism described 149 in RFC 2575 [RFC2575]. 151 A more detailed introduction to the current SNMP Management Framework 152 can be found in RFC 2570 [RFC2570]. 154 Managed objects are accessed via a virtual information store, termed 155 the Management Information Base or MIB. Objects in the MIB are 156 defined using the mechanisms defined in the SMI. 158 This memo specifies a MIB module that is compliant to the SMIv2. A 159 MIB conforming to the SMIv1 can be produced through the appropriate 160 translations. The resulting translated MIB must be semantically 161 equivalent, except where objects or events are omitted because no 162 translation is possible (use of Counter64). Some machine readable 163 information in SMIv2 will be converted into textual descriptions in 164 SMIv1 during the translation process. However, this loss of machine 165 readable information is not considered to change the semantics of the 166 MIB. 168 3. Overview 170 Instances of these object types represent attributes of an IEEE 802.3 171 MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD 172 standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3 173 repeaters or to 802.3 (Ethernet-like) interfaces. For convenience 174 this document refers to these devices as "repeater MAUs" and 175 "interface MAUs." 177 The definitions presented here are based on Section 30.5, "Layer 178 Management for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Medium 179 Attachment Units (MAUs)", Section 30.6, "Management for link Auto- 180 Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed 181 object classes" of IEEE Std. 802.3, 2000 edition [IEEE802.3], as 182 amended by IEEE Draft P802.3ae/D4.3 [P802.3ae]. That specification 183 includes definitions for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s 184 devices. This specification is intended to serve the same purpose: to 185 provide for management of all types of Ethernet/802.3 MAUs. 187 3.1. Relationship to RFC 2668 188 This MIB is intended to be a superset of that defined by RFC 2668 189 [RFC2668], which will go to historic status. This MIB includes all 190 of the objects contained in that MIB, with new and updated 191 definitions which provide support for additional capabilities. 192 Implementors are encouraged to support all applicable conformance 193 groups in order to make the best use of the new functionality 194 provided by this MIB. The new and updated definitions provide 195 management support for 10 Gb/s devices. 197 3.2. Relationship to RFC 2239 199 RFC 2668 was a replacement for RFC 2239 [RFC2239], which is now 200 historic. RFC 2668 defined a superset of that defined by RFC 2239 201 [RFC2239], which contained all of the objects defined in RFC 2239, 202 plus several new ones which provide additional capabilities. The new 203 objects provided management support for: 205 o management of 1000 Mb/s devices 207 o management of PAUSE negotiation 209 o management of remote fault status 211 3.3. Relationship to RFC 1515 213 RFC 2239 was a replacement for RFC 1515 [RFC1515], which is now 214 historic. RFC 2239 defined a superset of RFC 1515 which contained 215 all of the objects defined in RFC 1515, plus several new ones which 216 provided additional capabilities. The new objects in RFC 2239 217 provided management support for: 219 o management of 100 Mb/s devices 221 o auto-negotiation on interface MAUs 223 o jack management 225 3.5. Relationship to Other MIBs 227 It is assumed that an agent implementing this MIB will also implement 228 (at least) the 'system' group defined in the SNMPv2 MIB [RFC1907]. 229 The following sections identify other MIBs that such an agent should 230 implement. 232 3.5.1. Relationship to the Interfaces MIB. 234 The sections of this document that define interface MAU-related 235 objects specify an extension to the Interfaces MIB [RFC2863]. An 236 agent implementing these interface-MAU related objects MUST also 237 implement the relevant groups of Interface MIB. The value of the 238 object ifMauIfIndex is the same as the value of 'ifIndex' used to 239 instantiate the interface to which the given MAU is connected. 241 It is REQUIRED that an agent implementing the interface-MAU related 242 objects in this MIB will also implement the Ethernet-like Interfaces 243 MIB, [ETHERIF]. Furthermore, when the interface-MAU related objects 244 are used to manage a 10GBASE-W PHY -- i.e., when ifMauType is equal 245 to dot3MauType10GigBaseW or any other 10GBASE-W variant -- then the 246 agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB 247 [ETHERWIS] and must follow the interface layering model specified 248 therein. In that case the value of the object ifMauIfIndex is the 249 same as the value of 'ifIndex' for the layer at the top of the stack, 250 i.e., for the ifTable entry that has 'ifType' equal to 251 ethernetCsmacd(6). If the interface-MAU related objects are used to 252 manage a PHY that allows the MAU type to be changed dynamically, then 253 the agent SHALL create ifTable, ifStackTable, and ifInvStackTable 254 entries that pertain to the WIS when ifMauDefaultType is changed to a 255 10GBASEW variant (i.e., one of dot3MauType10GigBaseW, 256 dot3MauType10GigBaseEW, dot3MauType10GigBaseLW, or 257 dot3MauType10GigBaseSW) from any other type, and shall destroy the 258 WIS-related entries when ifMauDefaultType is changed to a non- 259 10GBASE-W type. The agent SHALL also change the values of 260 'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry indexed 261 by ifMauIfIndex as specified in [ETHERIF] and [ETHERWIS] when 262 ifMauDefaultType is manipulated in this way but SHALL NOT otherwise 263 alter that entry. 265 (Note that repeater ports are not represented as interfaces in the 266 Interface MIB.) 268 3.5.2. Relationship to the 802.3 Repeater MIB 270 The section of this document that defines repeater MAU-related 271 objects specifies an extension to the 802.3 Repeater MIB defined in 272 [RFC2108]. An agent implementing these repeater-MAU related objects 273 MUST also implement the 802.3 Repeater MIB. 275 The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to 276 instantiate a repeater MAU variable SHALL be the same as the values 277 of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the 278 port to which the given MAU is connected. 280 3.6. Management of Internal MAUs 282 In some situations, a MAU can be "internal" -- i.e., its 283 functionality is implemented entirely within a device. For example, 284 a managed repeater may contain an internal repeater-MAU and/or an 285 internal interface-MAU through which management communications 286 originating on one of the repeater's external ports pass in order to 287 reach the management agent associated with the repeater. Such 288 internal MAUs may or may not be managed. If they are managed, 289 objects describing their attributes should appear in the appropriate 290 MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs and 291 dot3IfMauBasicGroup for internal interface-MAUs. 293 3.7. Mapping of IEEE 802.3 Managed Objects 295 IEEE 802.3 Managed Object Corresponding SNMP Object 297 oMAU 298 .aMAUID rpMauIndex or 299 ifMauIndex or 300 broadMauIndex 301 .aMAUType rpMauType or 302 ifMauType 303 .aMAUTypeList ifMauTypeListBits 304 .aMediaAvailable rpMauMediaAvailable or 305 ifMauMediaAvailable 306 .aLoseMediaCounter rpMauMediaAvailableStateExits 307 or 308 ifMauMediaAvailableStateExits 309 .aJabber rpMauJabberState and 310 rpMauJabberingStateEnters or 311 ifMauJabberState and 312 ifMauJabberingStateEnters 313 .aMAUAdminState rpMauStatus or 314 ifMauStatus 315 .aBbMAUXmitRcvSplitType broadMauXmtRcvSplitType 316 .aBroadbandFrequencies broadMauXmtCarrierFreq and 317 broadMauTranslationFreq 318 .aFalseCarriers rpMauFalseCarriers or 319 ifMauFalseCarriers 320 .acResetMAU rpMauStatus or 321 ifMauStatus 322 .acMAUAdminControl rpMauStatus or 323 ifMauStatus 324 .nJabber rpMauJabberTrap or 325 ifMauJabberTrap 327 oAutoNegotiation 328 .aAutoNegID ifMauIndex 329 .aAutoNegAdminState ifMauAutoNegAdminStatus 330 .aAutoNegRemoteSignalling ifMauAutoNegRemoteSignalling 331 .aAutoNegAutoConfig ifMauAutoNegConfig 332 .aAutoNegLocalTechnologyAbility ifMauAutoNegCapabilityBits 333 .aAutoNegAdvertisedTechnologyAbility ifMauAutoNegAdvertisedBits and 334 ifMauAutoNegRemoteFaultAdvertised 335 .aAutoNegReceivedTechnologyAbility ifMauAutoNegReceivedBits and 336 ifMauAutoNegRemoteFaultReceived 337 .acAutoNegRestartAutoConfig ifMauAutoNegRestart 338 .acAutoNegAdminControl ifMauAutoNegAdminStatus 340 The following IEEE 802.3 managed objects have not been included in 341 this MIB for the following reasons. 343 IEEE 802.3 Managed Object Corresponding SNMP Object 345 oMAU 346 .aIdleErrorCount Only useful for 100BaseT2, 347 which is not widely 348 implemented. 350 oAutoNegotiation 351 .aAutoNegLocalSelectorAbility Only needed for support of 352 .aAutoNegAdvertisedSelectorAbility isoethernet (802.9a), which is 353 .aAutoNegReceivedSelectorAbility not supported by this MIB. 355 4. Definitions 357 MAU-MIB DEFINITIONS ::= BEGIN 359 IMPORTS 360 Counter32, Integer32, Counter64, 361 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, 362 OBJECT-IDENTITY, mib-2 363 FROM SNMPv2-SMI 364 TruthValue, TEXTUAL-CONVENTION 365 FROM SNMPv2-TC 366 OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP 367 FROM SNMPv2-CONF 368 InterfaceIndex 369 FROM IF-MIB; 371 mauMod MODULE-IDENTITY 372 LAST-UPDATED "200205100000Z" -- May 10, 2002 373 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 374 Working Group" 375 CONTACT-INFO 376 "WG E-mail: hubmib@ietf.org 378 To subscribe: hubmib-request@ietf.org 380 Chair: Dan Romascanu 381 Postal: Avaya Inc. 382 Atidim Technology Park, Bldg. 3 383 Tel Aviv 61131 384 Israel 385 Tel: +972 3 645 8414 386 E-mail: dromasca@avaya.com 388 Editor: John Flick 389 Postal: Hewlett-Packard Company 390 8000 Foothills Blvd. M/S 5557 391 Roseville, CA 95747-5557 392 USA 393 Tel: +1 916 785 4018 394 Fax: +1 916 785 1199 395 E-mail: johnf@rose.hp.com" 396 DESCRIPTION "Management information for 802.3 MAUs. 398 The following reference is used throughout 399 this MIB module: 401 [IEEE 802.3 Std] refers to 402 IEEE Std 802.3, 2000 Edition: 'IEEE Standard 403 for Information technology - 404 Telecommunications and information exchange 405 between systems - Local and metropolitan 406 area networks - Specific requirements - 407 Part 3: Carrier sense multiple access with 408 collision detection (CSMA/CD) access method 409 and physical layer specifications', as 410 amended by IEEE Draft P802.3ae/D4.3: 411 'Supplement to Carrier Sense Multiple Access 412 with Collision Detection (CSMA/CD) Access 413 Method & Physica Layer Specifications - 414 Media Access Control (MAC) Parameters, 415 Physical Layer, and Management Parameters 416 for 10 Gb/s Operation', April 2002. 418 Of particular interest is Clause 30, '10Mb/s, 419 100Mb/s, 1000Mb/s and 10 Gb/s Management'." 421 REVISION "200205100000Z" -- May 10, 2002 422 DESCRIPTION "This version published as RFC XXXX. Updated 423 to include support for 10 Gb/s MAUs." 425 REVISION "9908240400Z" -- August 24, 1999 426 DESCRIPTION "This version published as RFC 2668. Updated 427 to include support for 1000 Mb/sec 428 MAUs and flow control negotiation." 430 REVISION "9710310000Z" -- October 31, 1997 431 DESCRIPTION "Version published as RFC 2239." 433 REVISION "9309300000Z" -- September30, 1993 434 DESCRIPTION "Initial version, published as RFC 1515." 436 ::= { snmpDot3MauMgt 6 } 438 snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } 440 -- textual conventions 442 JackType ::= TEXTUAL-CONVENTION 443 STATUS current 444 DESCRIPTION "Common enumeration values for repeater 445 and interface MAU jack types." 446 SYNTAX INTEGER { 447 other(1), 448 rj45(2), 449 rj45S(3), -- rj45 shielded 450 db9(4), 451 bnc(5), 452 fAUI(6), -- female aui 453 mAUI(7), -- male aui 454 fiberSC(8), 455 fiberMIC(9), 456 fiberST(10), 457 telco(11), 458 mtrj(12), -- fiber MT-RJ 459 hssdc(13), -- fiber channel style-2 460 fiberLC(14) 461 } 463 dot3RpMauBasicGroup 464 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } 465 dot3IfMauBasicGroup 466 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } 467 dot3BroadMauBasicGroup 468 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } 470 dot3IfMauAutoNegGroup 471 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } 473 -- object identities for MAU types 474 -- (see rpMauType and ifMauType for usage) 476 dot3MauType 477 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } 479 dot3MauTypeAUI OBJECT-IDENTITY 480 STATUS current 481 DESCRIPTION "no internal MAU, view from AUI" 482 ::= { dot3MauType 1 } 484 dot3MauType10Base5 OBJECT-IDENTITY 485 STATUS current 486 DESCRIPTION "thick coax MAU (per 802.3 section 8)" 487 ::= { dot3MauType 2 } 489 dot3MauTypeFoirl OBJECT-IDENTITY 490 STATUS current 491 DESCRIPTION "FOIRL MAU (per 802.3 section 9.9)" 492 ::= { dot3MauType 3 } 494 dot3MauType10Base2 OBJECT-IDENTITY 495 STATUS current 496 DESCRIPTION "thin coax MAU (per 802.3 section 10)" 497 ::= { dot3MauType 4 } 499 dot3MauType10BaseT OBJECT-IDENTITY 500 STATUS current 501 DESCRIPTION "UTP MAU (per 802.3 section 14). 502 Note that it is strongly recommended that 503 agents return either dot3MauType10BaseTHD or 504 dot3MauType10BaseTFD 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 ::= { dot3MauType 5 } 510 dot3MauType10BaseFP OBJECT-IDENTITY 511 STATUS current 512 DESCRIPTION "passive fiber MAU (per 802.3 section 16)" 513 ::= { dot3MauType 6 } 515 dot3MauType10BaseFB OBJECT-IDENTITY 516 STATUS current 517 DESCRIPTION "sync fiber MAU (per 802.3 section 17)" 518 ::= { dot3MauType 7 } 520 dot3MauType10BaseFL OBJECT-IDENTITY 521 STATUS current 522 DESCRIPTION "async fiber MAU (per 802.3 section 18) 523 Note that it is strongly recommended that 524 agents return either dot3MauType10BaseFLHD or 525 dot3MauType10BaseFLFD if the duplex mode is 526 known. However, management applications should 527 be prepared to receive this MAU type value from 528 older agent implementations." 529 ::= { dot3MauType 8 } 531 dot3MauType10Broad36 OBJECT-IDENTITY 532 STATUS current 533 DESCRIPTION "broadband DTE MAU (per 802.3 section 11). 534 Note that 10BROAD36 MAUs can be attached to 535 interfaces but not to repeaters." 536 ::= { dot3MauType 9 } 538 ------ new since RFC 1515: 540 dot3MauType10BaseTHD OBJECT-IDENTITY 541 STATUS current 542 DESCRIPTION "UTP MAU (per 802.3 section 14), half duplex 543 mode" 544 ::= { dot3MauType 10 } 546 dot3MauType10BaseTFD OBJECT-IDENTITY 547 STATUS current 548 DESCRIPTION "UTP MAU (per 802.3 section 14), full duplex 549 mode" 550 ::= { dot3MauType 11 } 552 dot3MauType10BaseFLHD OBJECT-IDENTITY 553 STATUS current 554 DESCRIPTION "async fiber MAU (per 802.3 section 18), half 555 duplex mode" 556 ::= { dot3MauType 12 } 558 dot3MauType10BaseFLFD OBJECT-IDENTITY 559 STATUS current 560 DESCRIPTION "async fiber MAU (per 802.3 section 18), full 561 duplex mode" 562 ::= { dot3MauType 13 } 564 dot3MauType100BaseT4 OBJECT-IDENTITY 565 STATUS current 566 DESCRIPTION "4 pair categ. 3 UTP (per 802.3 section 23)" 567 ::= { dot3MauType 14 } 569 dot3MauType100BaseTXHD OBJECT-IDENTITY 570 STATUS current 571 DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), 572 half duplex mode" 573 ::= { dot3MauType 15 } 575 dot3MauType100BaseTXFD OBJECT-IDENTITY 576 STATUS current 577 DESCRIPTION "2 pair categ. 5 UTP (per 802.3 section 25), 578 full duplex mode" 579 ::= { dot3MauType 16 } 581 dot3MauType100BaseFXHD OBJECT-IDENTITY 582 STATUS current 583 DESCRIPTION "X fiber over PMT (per 802.3 section 26), half 584 duplex mode" 585 ::= { dot3MauType 17 } 587 dot3MauType100BaseFXFD OBJECT-IDENTITY 588 STATUS current 589 DESCRIPTION "X fiber over PMT (per 802.3 section 26), full 590 duplex mode" 591 ::= { dot3MauType 18 } 593 dot3MauType100BaseT2HD OBJECT-IDENTITY 594 STATUS current 595 DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32), 596 half duplex mode" 597 ::= { dot3MauType 19 } 599 dot3MauType100BaseT2FD OBJECT-IDENTITY 600 STATUS current 601 DESCRIPTION "2 pair categ. 3 UTP (per 802.3 section 32), 602 full duplex mode" 603 ::= { dot3MauType 20 } 605 ------ new since RFC 2239: 607 dot3MauType1000BaseXHD OBJECT-IDENTITY 608 STATUS current 609 DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, 610 half duplex mode" 611 ::= { dot3MauType 21 } 613 dot3MauType1000BaseXFD OBJECT-IDENTITY 614 STATUS current 615 DESCRIPTION "PCS/PMA (per 802.3 section 36), unknown PMD, 616 full duplex mode" 618 ::= { dot3MauType 22 } 620 dot3MauType1000BaseLXHD OBJECT-IDENTITY 621 STATUS current 622 DESCRIPTION "Fiber over long-wavelength laser (per 802.3 623 section 38), half duplex mode" 624 ::= { dot3MauType 23 } 626 dot3MauType1000BaseLXFD OBJECT-IDENTITY 627 STATUS current 628 DESCRIPTION "Fiber over long-wavelength laser (per 802.3 629 section 38), full duplex mode" 630 ::= { dot3MauType 24 } 632 dot3MauType1000BaseSXHD OBJECT-IDENTITY 633 STATUS current 634 DESCRIPTION "Fiber over short-wavelength laser (per 802.3 635 section 38), half duplex mode" 636 ::= { dot3MauType 25 } 638 dot3MauType1000BaseSXFD OBJECT-IDENTITY 639 STATUS current 640 DESCRIPTION "Fiber over short-wavelength laser (per 802.3 641 section 38), full duplex mode" 642 ::= { dot3MauType 26 } 644 dot3MauType1000BaseCXHD OBJECT-IDENTITY 645 STATUS current 646 DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 647 section 39), half duplex mode" 648 ::= { dot3MauType 27 } 650 dot3MauType1000BaseCXFD OBJECT-IDENTITY 651 STATUS current 652 DESCRIPTION "Copper over 150-Ohm balanced cable (per 802.3 653 section 39), full duplex mode" 654 ::= { dot3MauType 28 } 656 dot3MauType1000BaseTHD OBJECT-IDENTITY 657 STATUS current 658 DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section 659 40), half duplex mode" 660 ::= { dot3MauType 29 } 662 dot3MauType1000BaseTFD OBJECT-IDENTITY 663 STATUS current 664 DESCRIPTION "Four-pair Category 5 UTP (per 802.3 section 665 40), full duplex mode" 667 ::= { dot3MauType 30 } 669 ------ new since RFC 2668: 671 dot3MauType10GigBaseX OBJECT-IDENTITY 672 STATUS current 673 DESCRIPTION "X PCS/PMA (per 802.3 section 48), unknown PMD." 674 ::= { dot3MauType 31 } 676 dot3MauType10GigBaseLX4 OBJECT-IDENTITY 677 STATUS current 678 DESCRIPTION "X fiber over WWDM optics (per 802.3 section 679 53)" 680 ::= { dot3MauType 32 } 682 dot3MauType10GigBaseR OBJECT-IDENTITY 683 STATUS current 684 DESCRIPTION "R PCS/PMA (per 802.3 section 49), unknown PMD." 685 ::= { dot3MauType 33 } 687 dot3MauType10GigBaseER OBJECT-IDENTITY 688 STATUS current 689 DESCRIPTION "R fiber over 1550 nm optics (per 802.3 section 690 52)" 691 ::= { dot3MauType 34 } 693 dot3MauType10GigBaseLR OBJECT-IDENTITY 694 STATUS current 695 DESCRIPTION "R fiber over 1310 nm optics (per 802.3 section 696 52)" 697 ::= { dot3MauType 35 } 699 dot3MauType10GigBaseSR OBJECT-IDENTITY 700 STATUS current 701 DESCRIPTION "R fiber over 850 nm optics (per 802.3 section 702 52)" 703 ::= { dot3MauType 36 } 705 dot3MauType10GigBaseW OBJECT-IDENTITY 706 STATUS current 707 DESCRIPTION "W PCS/PMA (per 802.3 section 49 and 50), 708 unknown PMD." 709 ::= { dot3MauType 37 } 711 dot3MauType10GigBaseEW OBJECT-IDENTITY 712 STATUS current 713 DESCRIPTION "W fiber over 1550 nm optics (per 802.3 section 714 52)" 716 ::= { dot3MauType 38 } 718 dot3MauType10GigBaseLW OBJECT-IDENTITY 719 STATUS current 720 DESCRIPTION "W fiber over 1310 nm optics (per 802.3 section 721 52)" 722 ::= { dot3MauType 39 } 724 dot3MauType10GigBaseSW OBJECT-IDENTITY 725 STATUS current 726 DESCRIPTION "W fiber over 850 nm optics (per 802.3 section 727 52)" 728 ::= { dot3MauType 40 } 730 -- 731 -- The Basic Repeater MAU Table 732 -- 734 rpMauTable OBJECT-TYPE 735 SYNTAX SEQUENCE OF RpMauEntry 736 MAX-ACCESS not-accessible 737 STATUS current 738 DESCRIPTION "Table of descriptive and status information 739 about the MAU(s) attached to the ports of a 740 repeater." 741 ::= { dot3RpMauBasicGroup 1 } 743 rpMauEntry OBJECT-TYPE 744 SYNTAX RpMauEntry 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION "An entry in the table, containing information 748 about a single MAU." 749 INDEX { rpMauGroupIndex, 750 rpMauPortIndex, 751 rpMauIndex 752 } 753 ::= { rpMauTable 1 } 755 RpMauEntry ::= 756 SEQUENCE { 757 rpMauGroupIndex Integer32, 758 rpMauPortIndex Integer32, 759 rpMauIndex Integer32, 760 rpMauType OBJECT IDENTIFIER, 761 rpMauStatus INTEGER, 762 rpMauMediaAvailable INTEGER, 763 rpMauMediaAvailableStateExits Counter32, 764 rpMauJabberState INTEGER, 765 rpMauJabberingStateEnters Counter32, 766 rpMauFalseCarriers Counter32 767 } 769 rpMauGroupIndex OBJECT-TYPE 770 SYNTAX Integer32 (1..2147483647) 771 MAX-ACCESS read-only 772 STATUS current 773 DESCRIPTION "This variable uniquely identifies the group 774 containing the port to which the MAU described 775 by this entry is connected. 777 Note: In practice, a group will generally be 778 a field-replaceable unit (i.e., module, card, 779 or board) that can fit in the physical system 780 enclosure, and the group number will correspond 781 to a number marked on the physical enclosure. 783 The group denoted by a particular value of this 784 object is the same as the group denoted by the 785 same value of rptrGroupIndex." 786 REFERENCE "Reference RFC 2108, rptrGroupIndex." 787 ::= { rpMauEntry 1 } 789 rpMauPortIndex OBJECT-TYPE 790 SYNTAX Integer32 (1..2147483647) 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION "This variable uniquely identifies the repeater 794 port within group rpMauGroupIndex to which the 795 MAU described by this entry is connected." 796 REFERENCE "Reference RFC 2108, rptrPortIndex." 797 ::= { rpMauEntry 2 } 799 rpMauIndex OBJECT-TYPE 800 SYNTAX Integer32 (1..2147483647) 801 MAX-ACCESS read-only 802 STATUS current 803 DESCRIPTION "This variable uniquely identifies the MAU 804 described by this entry from among other 805 MAUs connected to the same port 806 (rpMauPortIndex)." 807 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 808 ::= { rpMauEntry 3 } 810 rpMauType OBJECT-TYPE 811 SYNTAX OBJECT IDENTIFIER 812 MAX-ACCESS read-only 813 STATUS current 814 DESCRIPTION "This object identifies the MAU type. An 815 initial set of MAU types are defined above. The 816 assignment of OBJECT IDENTIFIERs to new types of 817 MAUs is managed by the IANA. If the MAU type is 818 unknown, the object identifier 820 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 822 is returned. Note that unknownMauType is a 823 syntactically valid object identifier, and any 824 conformant implementation of ASN.1 and the BER 825 must be able to generate and recognize this 826 value." 827 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." 828 ::= { rpMauEntry 4 } 830 rpMauStatus OBJECT-TYPE 831 SYNTAX INTEGER { 832 other(1), 833 unknown(2), 834 operational(3), 835 standby(4), 836 shutdown(5), 837 reset(6) 838 } 839 MAX-ACCESS read-write 840 STATUS current 841 DESCRIPTION "The current state of the MAU. This object MAY 842 be implemented as a read-only object by those 843 agents and MAUs that do not implement software 844 control of the MAU state. Some agents may not 845 support setting the value of this object to some 846 of the enumerated values. 848 The value other(1) is returned if the MAU is in 849 a state other than one of the states 2 through 850 6. 852 The value unknown(2) is returned when the MAU's 853 true state is unknown; for example, when it is 854 being initialized. 856 A MAU in the operational(3) state is fully 857 functional, operates, and passes signals to its 858 attached DTE or repeater port in accordance to 859 its specification. 861 A MAU in standby(4) state forces DI and CI to 862 idle and the media transmitter to idle or fault, 863 if supported. Standby(4) mode only applies to 864 link type MAUs. The state of 865 rpMauMediaAvailable is unaffected. 867 A MAU in shutdown(5) state assumes the same 868 condition on DI, CI, and the media transmitter 869 as though it were powered down or not connected. 870 The MAU MAY return other(1) value for the 871 rpMauJabberState and rpMauMediaAvailable objects 872 when it is in this state. For an AUI, this 873 state will remove power from the AUI. 875 Setting this variable to the value reset(6) 876 resets the MAU in the same manner as a 877 power-off, power-on cycle of at least one-half 878 second would. The agent is not required to 879 return the value reset (6). 881 Setting this variable to the value 882 operational(3), standby(4), or shutdown(5) 883 causes the MAU to assume the respective state 884 except that setting a mixing-type MAU or an AUI 885 to standby(4) will cause the MAU to enter the 886 shutdown state." 887 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, 888 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 889 acResetMAU." 890 ::= { rpMauEntry 5 } 892 rpMauMediaAvailable OBJECT-TYPE 893 SYNTAX INTEGER { 894 other(1), 895 unknown(2), 896 available(3), 897 notAvailable(4), 898 remoteFault(5), 899 invalidSignal(6), 900 remoteJabber(7), 901 remoteLinkLoss(8), 902 remoteTest(9), 903 offline(10), 904 autoNegError(11) 905 } 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 909 10BASE-T, 10BASE-F) then this is equivalent to 910 the link test fail state/low light function. 911 For an AUI or a coax (including broadband) MAU 912 this indicates whether or not loopback is 913 detected on the DI circuit. The value of this 914 attribute persists between packets for MAU types 915 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 917 The value other(1) is returned if the 918 mediaAvailable state is not one of 2 through 11. 920 The value unknown(2) is returned when the MAU's 921 true state is unknown; for example, when it is 922 being initialized. At power-up or following a 923 reset, the value of this attribute will be 924 unknown for AUI, coax, and 10BASE-FP MAUs. For 925 these MAUs loopback will be tested on each 926 transmission during which no collision is 927 detected. If DI is receiving input when DO 928 returns to IDL after a transmission and there 929 has been no collision during the transmission 930 then loopback will be detected. The value of 931 this attribute will only change during 932 non-collided transmissions for AUI, coax, and 933 10BASE-FP MAUs. 935 For 100Mbps and 1000Mbps MAUs, the enumerations 936 match the states within the respective link 937 integrity state diagrams, fig 32-16, 23-12 and 938 24-15 of sections 32, 23 and 24 of [16]. Any 939 MAU which implements management of 940 auto-negotiation will map remote fault 941 indication to remote fault. 943 The value available(3) indicates that the link, 944 light, or loopback is normal. The value 945 notAvailable(4) indicates link loss, low light, 946 or no loopback. 948 The value remoteFault(5) indicates that a fault 949 has been detected at the remote end of the link. 950 This value applies to 10BASE-FB, 100BASE-T4 Far 951 End Fault Indication and non-specified remote 952 faults from a system running auto-negotiation. 953 The values remoteJabber(7), remoteLinkLoss(8), 954 and remoteTest(9) SHOULD be used instead of 955 remoteFault(5) where the reason for remote fault 956 is identified in the remote signaling protocol. 958 The value invalidSignal(6) indicates that an 959 invalid signal has been received from the other 960 end of the link. InvalidSignal(6) applies only 961 to MAUs of type 10BASE-FB. 963 Where an IEEE Std 802.3u-1995 clause 22 MII 964 is present, a logic one in the remote fault bit 965 (reference section 22.2.4.2.8 of that document) 966 maps to the value remoteFault(5), and a logic 967 zero in the link status bit (reference section 968 22.2.4.2.10 of that document) maps to the value 969 notAvailable(4). The value notAvailable(4) 970 takes precedence over the value remoteFault(5). 972 Any MAU that implements management of clause 37 973 Auto-Negotiation will map the received Remote 974 Fault (RF1 and RF2) bit values for Offline to 975 offline(10), Link Failure to remoteFault(5) and 976 Auto-Negotiation Error to autoNegError(11)." 978 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." 979 ::= { rpMauEntry 6 } 981 rpMauMediaAvailableStateExits OBJECT-TYPE 982 SYNTAX Counter32 983 MAX-ACCESS read-only 984 STATUS current 985 DESCRIPTION "A count of the number of times that 986 rpMauMediaAvailable for this MAU instance leaves 987 the state available(3). 989 Discontinuities in the value of this counter can 990 occur at re-initialization of the management 991 system, and at other times as indicated by the 992 value of rptrMonitorPortLastChange." 993 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, 994 aLoseMediaCounter. 995 RFC 2108, rptrMonitorPortLastChange" 996 ::= { rpMauEntry 7 } 998 rpMauJabberState OBJECT-TYPE 999 SYNTAX INTEGER { 1000 other(1), 1001 unknown(2), 1002 noJabber(3), 1003 jabbering(4) 1004 } 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION "The value other(1) is returned if the jabber 1008 state is not 2, 3, or 4. The agent MUST always 1009 return other(1) for MAU type dot3MauTypeAUI. 1011 The value unknown(2) is returned when the MAU's 1012 true state is unknown; for example, when it is 1013 being initialized. 1015 If the MAU is not jabbering the agent returns 1016 noJabber(3). This is the 'normal' state. 1018 If the MAU is in jabber state the agent returns 1019 the jabbering(4) value." 1020 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1021 aJabber.jabberFlag." 1022 ::= { rpMauEntry 8 } 1024 rpMauJabberingStateEnters OBJECT-TYPE 1025 SYNTAX Counter32 1026 MAX-ACCESS read-only 1027 STATUS current 1028 DESCRIPTION "A count of the number of times that 1029 mauJabberState for this MAU instance enters the 1030 state jabbering(4). For MAUs of type 1031 dot3MauTypeAUI, dot3MauType100BaseT4, 1032 dot3MauType100BaseTX, dot3MauType100BaseFX and 1033 all 1000Mbps types, this counter will always 1034 indicate zero. 1036 Discontinuities in the value of this counter can 1037 occur at re-initialization of the management 1038 system, and at other times as indicated by the 1039 value of rptrMonitorPortLastChange." 1040 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1041 aJabber.jabberCounter. 1042 RFC 2108, rptrMonitorPortLastChange" 1043 ::= { rpMauEntry 9 } 1045 rpMauFalseCarriers OBJECT-TYPE 1046 SYNTAX Counter32 1047 MAX-ACCESS read-only 1048 STATUS current 1049 DESCRIPTION "A count of the number of false carrier events 1050 during IDLE in 100BASE-X links. This counter 1051 does not increment at the symbol rate. It can 1052 increment after a valid carrier completion at a 1053 maximum rate of once per 100 ms until the next 1054 carrier event. 1056 This counter increments only for MAUs of type 1057 dot3MauType100BaseT4, dot3MauType100BaseTX, and 1058 dot3MauType100BaseFX and all 1000Mbps types. 1059 For all other MAU types, this counter will 1060 always indicate zero. 1062 The approximate minimum time for rollover of 1063 this counter is 7.4 hours. 1065 Discontinuities in the value of this counter can 1066 occur at re-initialization of the management 1067 system, and at other times as indicated by the 1068 value of rptrMonitorPortLastChange." 1069 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. 1070 RFC 2108, rptrMonitorPortLastChange" 1071 ::= { rpMauEntry 10 } 1073 -- The rpJackTable applies to MAUs attached to repeaters 1074 -- which have one or more external jacks (connectors). 1076 rpJackTable OBJECT-TYPE 1077 SYNTAX SEQUENCE OF RpJackEntry 1078 MAX-ACCESS not-accessible 1079 STATUS current 1080 DESCRIPTION "Information about the external jacks attached 1081 to MAUs attached to the ports of a repeater." 1082 ::= { dot3RpMauBasicGroup 2 } 1084 rpJackEntry OBJECT-TYPE 1085 SYNTAX RpJackEntry 1086 MAX-ACCESS not-accessible 1087 STATUS current 1088 DESCRIPTION "An entry in the table, containing information 1089 about a particular jack." 1090 INDEX { rpMauGroupIndex, 1091 rpMauPortIndex, 1092 rpMauIndex, 1093 rpJackIndex 1094 } 1095 ::= { rpJackTable 1 } 1097 RpJackEntry ::= 1098 SEQUENCE { 1099 rpJackIndex Integer32, 1100 rpJackType JackType 1101 } 1103 rpJackIndex OBJECT-TYPE 1104 SYNTAX Integer32 (1..2147483647) 1105 MAX-ACCESS not-accessible 1106 STATUS current 1107 DESCRIPTION "This variable uniquely identifies the jack 1108 described by this entry from among other jacks 1109 attached to the same MAU (rpMauIndex)." 1110 ::= { rpJackEntry 1 } 1112 rpJackType OBJECT-TYPE 1113 SYNTAX JackType 1114 MAX-ACCESS read-only 1115 STATUS current 1116 DESCRIPTION "The jack connector type, as it appears on the 1117 outside of the system." 1118 ::= { rpJackEntry 2 } 1120 -- 1121 -- The Basic Interface MAU Table 1122 -- 1124 ifMauTable OBJECT-TYPE 1125 SYNTAX SEQUENCE OF IfMauEntry 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION "Table of descriptive and status information 1129 about MAU(s) attached to an interface." 1130 ::= { dot3IfMauBasicGroup 1 } 1132 ifMauEntry OBJECT-TYPE 1133 SYNTAX IfMauEntry 1134 MAX-ACCESS not-accessible 1135 STATUS current 1136 DESCRIPTION "An entry in the table, containing information 1137 about a single MAU." 1138 INDEX { ifMauIfIndex, 1139 ifMauIndex 1140 } 1141 ::= { ifMauTable 1 } 1143 IfMauEntry ::= 1144 SEQUENCE { 1145 ifMauIfIndex InterfaceIndex, 1146 ifMauIndex Integer32, 1147 ifMauType OBJECT IDENTIFIER, 1148 ifMauStatus INTEGER, 1149 ifMauMediaAvailable INTEGER, 1150 ifMauMediaAvailableStateExits Counter32, 1151 ifMauJabberState INTEGER, 1152 ifMauJabberingStateEnters Counter32, 1153 ifMauFalseCarriers Counter32, 1154 ifMauTypeList Integer32, 1155 ifMauDefaultType OBJECT IDENTIFIER, 1156 ifMauAutoNegSupported TruthValue, 1157 ifMauTypeListBits BITS, 1158 ifMauHCFalseCarriers Counter64 1159 } 1161 ifMauIfIndex OBJECT-TYPE 1162 SYNTAX InterfaceIndex 1163 MAX-ACCESS read-only 1164 STATUS current 1165 DESCRIPTION "This variable uniquely identifies the interface 1166 to which the MAU described by this entry is 1167 connected." 1168 REFERENCE "RFC 2863, ifIndex" 1169 ::= { ifMauEntry 1 } 1171 ifMauIndex OBJECT-TYPE 1172 SYNTAX Integer32 (1..2147483647) 1173 MAX-ACCESS read-only 1174 STATUS current 1175 DESCRIPTION "This variable uniquely identifies the MAU 1176 described by this entry from among other MAUs 1177 connected to the same interface (ifMauIfIndex)." 1178 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 1179 ::= { ifMauEntry 2 } 1181 ifMauType OBJECT-TYPE 1182 SYNTAX OBJECT IDENTIFIER 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION "This object identifies the MAU type. An 1186 initial set of MAU types are defined above. The 1187 assignment of OBJECT IDENTIFIERs to new types of 1188 MAUs is managed by the IANA. If the MAU type is 1189 unknown, the object identifier 1191 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 1192 is returned. Note that unknownMauType is a 1193 syntactically valid object identifier, and any 1194 conformant implementation of ASN.1 and the BER 1195 must be able to generate and recognize this 1196 value. 1198 This object represents the operational type of 1199 the MAU, as determined by either (1) the result 1200 of the auto-negotiation function or (2) if 1201 auto-negotiation is not enabled or is not 1202 implemented for this MAU, by the value of the 1203 object ifMauDefaultType. In case (2), a set to 1204 the object ifMauDefaultType will force the MAU 1205 into the new operating mode." 1206 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." 1207 ::= { ifMauEntry 3 } 1209 ifMauStatus OBJECT-TYPE 1210 SYNTAX INTEGER { 1211 other(1), 1212 unknown(2), 1213 operational(3), 1214 standby(4), 1215 shutdown(5), 1216 reset(6) 1217 } 1218 MAX-ACCESS read-write 1219 STATUS current 1220 DESCRIPTION "The current state of the MAU. This object MAY 1221 be implemented as a read-only object by those 1222 agents and MAUs that do not implement software 1223 control of the MAU state. Some agents may not 1224 support setting the value of this object to some 1225 of the enumerated values. 1227 The value other(1) is returned if the MAU is in 1228 a state other than one of the states 2 through 1229 6. 1231 The value unknown(2) is returned when the MAU's 1232 true state is unknown; for example, when it is 1233 being initialized. 1235 A MAU in the operational(3) state is fully 1236 functional, operates, and passes signals to its 1237 attached DTE or repeater port in accordance to 1238 its specification. 1240 A MAU in standby(4) state forces DI and CI to 1241 idle and the media transmitter to idle or fault, 1242 if supported. Standby(4) mode only applies to 1243 link type MAUs. The state of 1244 ifMauMediaAvailable is unaffected. 1246 A MAU in shutdown(5) state assumes the same 1247 condition on DI, CI, and the media transmitter 1248 as though it were powered down or not connected. 1249 The MAU MAY return other(1) value for the 1250 ifMauJabberState and ifMauMediaAvailable objects 1251 when it is in this state. For an AUI, this 1252 state will remove power from the AUI. 1254 Setting this variable to the value reset(6) 1255 resets the MAU in the same manner as a 1256 power-off, power-on cycle of at least one-half 1257 second would. The agent is not required to 1258 return the value reset (6). 1260 Setting this variable to the value 1261 operational(3), standby(4), or shutdown(5) 1262 causes the MAU to assume the respective state 1263 except that setting a mixing-type MAU or an AUI 1264 to standby(4) will cause the MAU to enter the 1265 shutdown state." 1266 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, 1267 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 1268 acResetMAU." 1269 ::= { ifMauEntry 4 } 1271 ifMauMediaAvailable OBJECT-TYPE 1272 SYNTAX INTEGER { 1273 other(1), 1274 unknown(2), 1275 available(3), 1276 notAvailable(4), 1277 remoteFault(5), 1278 invalidSignal(6), 1279 remoteJabber(7), 1280 remoteLinkLoss(8), 1281 remoteTest(9), 1282 offline(10), 1283 autoNegError(11), 1284 pmdLinkFault(12), 1285 wisFrameLoss(13), 1286 wisSignalLoss(14), 1287 pcsLinkFault(15), 1288 excessiveBER(16), 1289 dxsLinkFault(17), 1290 pxsLinkFault(18) 1291 } 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 1295 10BASE-T, 10BASE-F) then this is equivalent to 1296 the link test fail state/low light function. 1297 For an AUI or a coax (including broadband) MAU 1298 this indicates whether or not loopback is 1299 detected on the DI circuit. The value of this 1300 attribute persists between packets for MAU types 1301 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 1303 The value other(1) is returned if the 1304 mediaAvailable state is not one of 2 through 18. 1306 The value unknown(2) is returned when the MAU's 1307 true state is unknown; for example, when it is 1308 being initialized. At power-up or following a 1309 reset, the value of this attribute will be 1310 unknown for AUI, coax, and 10BASE-FP MAUs. For 1311 these MAUs loopback will be tested on each 1312 transmission during which no collision is 1313 detected. If DI is receiving input when DO 1314 returns to IDL after a transmission and there 1315 has been no collision during the transmission 1316 then loopback will be detected. The value of 1317 this attribute will only change during 1318 non-collided transmissions for AUI, coax, and 1319 10BASE-FP MAUs. 1321 For 100Mbps and 1000Mbps MAUs, the enumerations 1322 match the states within the respective link 1323 integrity state diagrams, fig 32-16, 23-12 and 1324 24-15 of sections 32, 23 and 24 of [16]. Any 1325 MAU which implements management of 1326 auto-negotiation will map remote fault 1327 indication to remote fault. 1329 The value available(3) indicates that the link, 1330 light, or loopback is normal. The value 1331 notAvailable(4) indicates link loss, low light, 1332 or no loopback. 1334 The value remoteFault(5) indicates that a fault 1335 has been detected at the remote end of the link. 1337 This value applies to 10BASE-FB, 100BASE-T4 Far 1338 End Fault Indication and non-specified remote 1339 faults from a system running auto-negotiation. 1340 The values remoteJabber(7), remoteLinkLoss(8), 1341 and remoteTest(9) SHOULD be used instead of 1342 remoteFault(5) where the reason for remote fault 1343 is identified in the remote signaling protocol. 1345 The value invalidSignal(6) indicates that an 1346 invalid signal has been received from the other 1347 end of the link. InvalidSignal(6) applies only 1348 to MAUs of type 10BASE-FB. 1350 Where an IEEE Std 802.3u-1995 clause 22 MII 1351 is present, a logic one in the remote fault bit 1352 (reference section 22.2.4.2.8 of that document) 1353 maps to the value remoteFault(5), and a logic 1354 zero in the link status bit (reference section 1355 22.2.4.2.10 of that document) maps to the value 1356 notAvailable(4). The value notAvailable(4) 1357 takes precedence over the value remoteFault(5). 1359 Any MAU that implements management of clause 37 1360 Auto-Negotiation will map the received RF1 and 1361 RF2 bit values for Offline to offline(10), Link 1362 Failure to remoteFault(5) and Auto-Negotiation 1363 Error to autoNegError(11). 1365 For 10 Gb/s, the enumerations map to the states 1366 within the Reconciliation Sublayer state diagram 1367 as follows: 1368 NoFault maps to the enumeration 'available(3)' 1369 LocalFault maps to the enumeration 1370 'notAvailable(4)' 1371 RemoteFault maps to the enumeration 1372 'remoteFault(5)' 1373 The enumerations 'pmdLinkFault(12)', 1374 'wisFrameLoss(13)', 'wisSignalLoss(14)', 1375 'pcsLinkFault(15)', 'excessiveBER(16)', and 1376 'dxsLinkFault(17)' and 'pxsLinkFault(18)' should 1377 be used instead of the enumeration 1378 'notAvailable(4)' where the reason for the local 1379 fault can be identified through the use of the 1380 MDIO Interface. Where multiple reasons for the 1381 local fault state can be identified only the 1382 highest precedence error should be reported. 1383 The precedence in descending order is as 1384 follows: 1386 pxsLinkFault 1387 pmdLinkFault 1388 wisFrameLoss 1389 wisSignalLoss 1390 pcsLinkFault 1391 excessiveBER 1392 dxsLinkFault" 1393 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." 1394 ::= { ifMauEntry 5 } 1396 ifMauMediaAvailableStateExits OBJECT-TYPE 1397 SYNTAX Counter32 1398 MAX-ACCESS read-only 1399 STATUS current 1400 DESCRIPTION "A count of the number of times that 1401 ifMauMediaAvailable for this MAU instance leaves 1402 the state available(3). 1404 Discontinuities in the value of this counter can 1405 occur at re-initialization of the management 1406 system, and at other times as indicated by the 1407 value of ifCounterDiscontinuityTime." 1408 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, 1409 aLoseMediaCounter. 1410 RFC 2863, ifCounterDiscontinuityTime." 1411 ::= { ifMauEntry 6 } 1413 ifMauJabberState OBJECT-TYPE 1414 SYNTAX INTEGER { 1415 other(1), 1416 unknown(2), 1417 noJabber(3), 1418 jabbering(4) 1419 } 1420 MAX-ACCESS read-only 1421 STATUS current 1422 DESCRIPTION "The value other(1) is returned if the jabber 1423 state is not 2, 3, or 4. The agent MUST always 1424 return other(1) for MAU type dot3MauTypeAUI. 1426 The value unknown(2) is returned when the MAU's 1427 true state is unknown; for example, when it is 1428 being initialized. 1430 If the MAU is not jabbering the agent returns 1431 noJabber(3). This is the 'normal' state. 1433 If the MAU is in jabber state the agent returns 1434 the jabbering(4) value." 1435 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1436 aJabber.jabberFlag." 1437 ::= { ifMauEntry 7 } 1439 ifMauJabberingStateEnters OBJECT-TYPE 1440 SYNTAX Counter32 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION "A count of the number of times that 1444 mauJabberState for this MAU instance enters the 1445 state jabbering(4). This counter will always 1446 indicate zero for MAUs of type dot3MauTypeAUI 1447 and those of speeds above 10Mbps. 1449 Discontinuities in the value of this counter can 1450 occur at re-initialization of the management 1451 system, and at other times as indicated by the 1452 value of ifCounterDiscontinuityTime." 1453 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1454 aJabber.jabberCounter. 1455 RFC 2863, ifCounterDiscontinuityTime." 1456 ::= { ifMauEntry 8 } 1458 ifMauFalseCarriers OBJECT-TYPE 1459 SYNTAX Counter32 1460 MAX-ACCESS read-only 1461 STATUS current 1462 DESCRIPTION "A count of the number of false carrier events 1463 during IDLE in 100BASE-X and 1000BASE-X links. 1465 For all other MAU types, this counter will 1466 always indicate zero. This counter does not 1467 increment at the symbol rate. 1469 It can increment after a valid carrier 1470 completion at a maximum rate of once per 100 ms 1471 for 100BASE-X and once per 10us for 1000BASE-X 1472 until the next CarrierEvent. 1474 This counter can roll over very quickly. A 1475 management station is advised to poll the 1476 ifMauHCFalseCarriers instead of this counter in 1477 order to avoid loss of information. 1479 Discontinuities in the value of this counter can 1480 occur at re-initialization of the management 1481 system, and at other times as indicated by the 1482 value of ifCounterDiscontinuityTime." 1483 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. 1484 RFC 2863, ifCounterDiscontinuityTime." 1485 ::= { ifMauEntry 9 } 1487 ifMauTypeList OBJECT-TYPE 1488 SYNTAX Integer32 1489 MAX-ACCESS read-only 1490 STATUS deprecated 1491 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1493 A value that uniquely identifies the set of 1494 possible IEEE 802.3 types that the MAU could be. 1495 The value is a sum which initially takes the 1496 value zero. Then, for each type capability of 1497 this MAU, 2 raised to the power noted below is 1498 added to the sum. For example, a MAU which has 1499 the capability to be only 10BASE-T would have a 1500 value of 512 (2**9). In contrast, a MAU which 1501 supports both 10Base-T (full duplex) and 1502 100BASE-TX (full duplex) would have a value of 1503 ((2**11) + (2**16)) or 67584. 1505 The powers of 2 assigned to the capabilities are 1506 these: 1508 Power Capability 1509 0 other or unknown 1510 1 AUI 1511 2 10BASE-5 1512 3 FOIRL 1513 4 10BASE-2 1514 5 10BASE-T duplex mode unknown 1515 6 10BASE-FP 1516 7 10BASE-FB 1517 8 10BASE-FL duplex mode unknown 1518 9 10BROAD36 1519 10 10BASE-T half duplex mode 1520 11 10BASE-T full duplex mode 1521 12 10BASE-FL half duplex mode 1522 13 10BASE-FL full duplex mode 1523 14 100BASE-T4 1524 15 100BASE-TX half duplex mode 1525 16 100BASE-TX full duplex mode 1526 17 100BASE-FX half duplex mode 1527 18 100BASE-FX full duplex mode 1528 19 100BASE-T2 half duplex mode 1529 20 100BASE-T2 full duplex mode 1531 If auto-negotiation is present on this MAU, this 1532 object will map to ifMauAutoNegCapability. 1534 This object has been deprecated in favour of 1535 ifMauTypeListBits." 1536 ::= { ifMauEntry 10 } 1538 ifMauDefaultType OBJECT-TYPE 1539 SYNTAX OBJECT IDENTIFIER 1540 MAX-ACCESS read-write 1541 STATUS current 1542 DESCRIPTION "This object identifies the default 1543 administrative baseband MAU type, to be used in 1544 conjunction with the operational MAU type 1545 denoted by ifMauType. 1547 The set of possible values for this object is 1548 the same as the set defined for the ifMauType 1549 object. 1551 This object represents the 1552 administratively-configured type of the MAU. If 1553 auto-negotiation is not enabled or is not 1554 implemented for this MAU, the value of this 1555 object determines the operational type of the 1556 MAU. In this case, a set to this object will 1557 force the MAU into the specified operating mode. 1559 If auto-negotiation is implemented and enabled 1560 for this MAU, the operational type of the MAU 1561 is determined by auto-negotiation, and the value 1562 of this object denotes the type to which the MAU 1563 will automatically revert if/when 1564 auto-negotiation is later disabled. 1566 NOTE TO IMPLEMENTORS: It may be necessary to 1567 provide for underlying hardware implementations 1568 which do not follow the exact behavior specified 1569 above. In particular, when 1570 ifMauAutoNegAdminStatus transitions from enabled 1571 to disabled, the agent implementation MUST 1572 ensure that the operational type of the MAU (as 1573 reported by ifMauType) correctly transitions to 1574 the value specified by this object, rather than 1575 continuing to operate at the value earlier 1576 determined by the auto-negotiation function." 1577 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID, and 1578 22.2.4.1.4." 1580 ::= { ifMauEntry 11 } 1582 ifMauAutoNegSupported OBJECT-TYPE 1583 SYNTAX TruthValue 1584 MAX-ACCESS read-only 1585 STATUS current 1586 DESCRIPTION "This object indicates whether or not 1587 auto-negotiation is supported on this MAU." 1588 ::= { ifMauEntry 12 } 1590 ifMauTypeListBits OBJECT-TYPE 1591 SYNTAX BITS { 1592 bOther(0), -- other or unknown 1593 bAUI(1), -- AUI 1594 b10base5(2), -- 10BASE-5 1595 bFoirl(3), -- FOIRL 1597 b10base2(4), -- 10BASE-2 1598 b10baseT(5), -- 10BASE-T duplex mode unknown 1599 b10baseFP(6), -- 10BASE-FP 1600 b10baseFB(7), -- 10BASE-FB 1601 b10baseFL(8), -- 10BASE-FL duplex mode unknown 1602 b10broad36(9), -- 10BROAD36 1603 b10baseTHD(10), -- 10BASE-T half duplex mode 1604 b10baseTFD(11), -- 10BASE-T full duplex mode 1605 b10baseFLHD(12), -- 10BASE-FL half duplex mode 1606 b10baseFLFD(13), -- 10BASE-FL full duplex mode 1608 b100baseT4(14), -- 100BASE-T4 1609 b100baseTXHD(15), -- 100BASE-TX half duplex mode 1610 b100baseTXFD(16), -- 100BASE-TX full duplex mode 1611 b100baseFXHD(17), -- 100BASE-FX half duplex mode 1612 b100baseFXFD(18), -- 100BASE-FX full duplex mode 1613 b100baseT2HD(19), -- 100BASE-T2 half duplex mode 1614 b100baseT2FD(20), -- 100BASE-T2 full duplex mode 1616 b1000baseXHD(21), -- 1000BASE-X half duplex mode 1617 b1000baseXFD(22), -- 1000BASE-X full duplex mode 1618 b1000baseLXHD(23), -- 1000BASE-LX half duplex mode 1619 b1000baseLXFD(24), -- 1000BASE-LX full duplex mode 1620 b1000baseSXHD(25), -- 1000BASE-SX half duplex mode 1621 b1000baseSXFD(26), -- 1000BASE-SX full duplex mode 1622 b1000baseCXHD(27), -- 1000BASE-CX half duplex mode 1623 b1000baseCXFD(28), -- 1000BASE-CX full duplex mode 1624 b1000baseTHD(29), -- 1000BASE-T half duplex mode 1625 b1000baseTFD(30), -- 1000BASE-T full duplex mode 1627 b10GbaseX(31), -- 10GBASE-X 1628 b10GbaseLX4(32), -- 10GBASE-LX4 1629 b10GbaseR(33), -- 10GBASE-R 1630 b10GbaseER(34), -- 10GBASE-ER 1631 b10GbaseLR(35), -- 10GBASE-LR 1632 b10GbaseSR(36), -- 10GBASE-SR 1633 b10GbaseW(37), -- 10GBASE-W 1634 b10GbaseEW(38), -- 10GBASE-EW 1635 b10GbaseLW(39), -- 10GBASE-LW 1636 b10GbaseSW(40) -- 10GBASE-SW 1637 } 1638 MAX-ACCESS read-only 1639 STATUS current 1640 DESCRIPTION "A value that uniquely identifies the set of 1641 possible IEEE 802.3 types that the MAU could be. 1642 If auto-negotiation is present on this MAU, this 1643 object will map to ifMauAutoNegCapability. 1645 Note that this MAU may be capable of operating 1646 as a MAU type that is beyond the scope of this 1647 MIB. This is indicated by returning the 1648 bit value bOther in addition to any bit values 1649 for capabilities that are listed above." 1650 ::= { ifMauEntry 13 } 1652 ifMauHCFalseCarriers OBJECT-TYPE 1653 SYNTAX Counter64 1654 MAX-ACCESS read-only 1655 STATUS current 1656 DESCRIPTION "A count of the number of false carrier events 1657 during IDLE in 100BASE-X and 1000BASE-X links. 1659 For all other MAU types, this counter will 1660 always indicate zero. This counter does not 1661 increment at the symbol rate. 1663 This counter is a 64 bit version of 1664 ifMauFalseCarriers. Since the 32 bit version of 1665 this counter can roll over very quickly, 1666 management stations are advised to poll the 1667 64 bit version instead in order to avoid loss 1668 of information. 1670 Discontinuities in the value of this counter can 1671 occur at re-initialization of the management 1672 system, and at other times as indicated by the 1673 value of ifCounterDiscontinuityTime." 1674 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. 1675 RFC 2863, ifCounterDiscontinuityTime." 1677 ::= { ifMauEntry 14 } 1679 -- The ifJackTable applies to MAUs attached to interfaces 1680 -- which have one or more external jacks (connectors). 1682 ifJackTable OBJECT-TYPE 1683 SYNTAX SEQUENCE OF IfJackEntry 1684 MAX-ACCESS not-accessible 1685 STATUS current 1686 DESCRIPTION "Information about the external jacks attached 1687 to MAUs attached to an interface." 1688 ::= { dot3IfMauBasicGroup 2 } 1690 ifJackEntry OBJECT-TYPE 1691 SYNTAX IfJackEntry 1692 MAX-ACCESS not-accessible 1693 STATUS current 1694 DESCRIPTION "An entry in the table, containing information 1695 about a particular jack." 1696 INDEX { ifMauIfIndex, 1697 ifMauIndex, 1698 ifJackIndex 1699 } 1700 ::= { ifJackTable 1 } 1702 IfJackEntry ::= 1703 SEQUENCE { 1704 ifJackIndex Integer32, 1705 ifJackType JackType 1706 } 1708 ifJackIndex OBJECT-TYPE 1709 SYNTAX Integer32 (1..2147483647) 1710 MAX-ACCESS not-accessible 1711 STATUS current 1712 DESCRIPTION "This variable uniquely identifies the jack 1713 described by this entry from among other jacks 1714 attached to the same MAU." 1715 ::= { ifJackEntry 1 } 1717 ifJackType OBJECT-TYPE 1718 SYNTAX JackType 1719 MAX-ACCESS read-only 1720 STATUS current 1721 DESCRIPTION "The jack connector type, as it appears on the 1722 outside of the system." 1724 ::= { ifJackEntry 2 } 1726 -- The ifMauAutoNegTable applies to systems in which 1727 -- auto-negotiation is supported on one or more MAUs 1728 -- attached to interfaces. Note that if auto-negotiation 1729 -- is present and enabled, the ifMauType object reflects 1730 -- the result of the auto-negotiation function. 1732 ifMauAutoNegTable OBJECT-TYPE 1733 SYNTAX SEQUENCE OF IfMauAutoNegEntry 1734 MAX-ACCESS not-accessible 1735 STATUS current 1736 DESCRIPTION "Configuration and status objects for the 1737 auto-negotiation function of MAUs attached to 1738 interfaces." 1739 ::= { dot3IfMauAutoNegGroup 1 } 1741 ifMauAutoNegEntry OBJECT-TYPE 1742 SYNTAX IfMauAutoNegEntry 1743 MAX-ACCESS not-accessible 1744 STATUS current 1745 DESCRIPTION "An entry in the table, containing configuration 1746 and status information for the auto-negotiation 1747 function of a particular MAU." 1748 INDEX { ifMauIfIndex, 1749 ifMauIndex 1750 } 1751 ::= { ifMauAutoNegTable 1 } 1753 IfMauAutoNegEntry ::= 1754 SEQUENCE { 1755 ifMauAutoNegAdminStatus INTEGER, 1756 ifMauAutoNegRemoteSignaling INTEGER, 1757 ifMauAutoNegConfig INTEGER, 1758 ifMauAutoNegCapability Integer32, 1759 ifMauAutoNegCapAdvertised Integer32, 1760 ifMauAutoNegCapReceived Integer32, 1761 ifMauAutoNegRestart INTEGER, 1762 ifMauAutoNegCapabilityBits BITS, 1763 ifMauAutoNegCapAdvertisedBits BITS, 1764 ifMauAutoNegCapReceivedBits BITS, 1765 ifMauAutoNegRemoteFaultAdvertised INTEGER, 1766 ifMauAutoNegRemoteFaultReceived INTEGER 1767 } 1769 ifMauAutoNegAdminStatus OBJECT-TYPE 1770 SYNTAX INTEGER { 1771 enabled(1), 1772 disabled(2) 1773 } 1774 MAX-ACCESS read-write 1775 STATUS current 1776 DESCRIPTION "Setting this object to enabled(1) will cause 1777 the interface which has the auto-negotiation 1778 signaling ability to be enabled. 1780 If the value of this object is disabled(2) then 1781 the interface will act as it would if it had no 1782 auto-negotiation signaling. Under these 1783 conditions, an IEEE 802.3 MAU will immediately 1784 be forced to the state indicated by the value of 1785 the object ifMauDefaultType. 1787 NOTE TO IMPLEMENTORS: When 1788 ifMauAutoNegAdminStatus transitions from enabled 1789 to disabled, the agent implementation MUST 1790 ensure that the operational type of the MAU (as 1791 reported by ifMauType) correctly transitions to 1792 the value specified by the ifMauDefaultType 1793 object, rather than continuing to operate at the 1794 value earlier determined by the auto-negotiation 1795 function." 1796 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.2, 1797 aAutoNegAdminState and 30.6.1.2.2, 1798 acAutoNegAdminControl." 1799 ::= { ifMauAutoNegEntry 1 } 1801 ifMauAutoNegRemoteSignaling OBJECT-TYPE 1802 SYNTAX INTEGER { 1803 detected(1), 1804 notdetected(2) 1805 } 1806 MAX-ACCESS read-only 1807 STATUS current 1808 DESCRIPTION "A value indicating whether the remote end of 1809 the link is using auto-negotiation signaling. It 1810 takes the value detected(1) if and only if, 1811 during the previous link negotiation, FLP Bursts 1812 were received." 1813 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.3, 1814 aAutoNegRemoteSignaling." 1815 ::= { ifMauAutoNegEntry 2 } 1817 ifMauAutoNegConfig OBJECT-TYPE 1818 SYNTAX INTEGER { 1819 other(1), 1820 configuring(2), 1821 complete(3), 1822 disabled(4), 1823 parallelDetectFail(5) 1824 } 1825 MAX-ACCESS read-only 1826 STATUS current 1827 DESCRIPTION "A value indicating the current status of the 1828 auto-negotiation process. The enumeration 1829 parallelDetectFail(5) maps to a failure in 1830 parallel detection as defined in 28.2.3.1 of 1831 [IEEE 802.3 Std]." 1832 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4, 1833 aAutoNegAutoConfig." 1834 ::= { ifMauAutoNegEntry 4 } 1836 ifMauAutoNegCapability OBJECT-TYPE 1837 SYNTAX Integer32 1838 MAX-ACCESS read-only 1839 STATUS deprecated 1840 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 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. 1877 This object has been deprecated in favour of 1878 ifMauAutoNegCapabilityBits" 1879 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, 1880 aAutoNegLocalTechnologyAbility." 1881 ::= { ifMauAutoNegEntry 5 } 1883 ifMauAutoNegCapAdvertised OBJECT-TYPE 1884 SYNTAX Integer32 1885 MAX-ACCESS read-write 1886 STATUS deprecated 1887 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 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. 1899 This object has been deprecated in favour of 1900 ifMauAutoNegCapAdvertisedBits" 1901 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 1902 aAutoNegAdvertisedTechnologyAbility." 1903 ::= { ifMauAutoNegEntry 6 } 1905 ifMauAutoNegCapReceived OBJECT-TYPE 1906 SYNTAX Integer32 1907 MAX-ACCESS read-only 1908 STATUS deprecated 1909 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 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. 1922 This object has been deprecated in favour of 1923 ifMauAutoNegCapReceivedBits" 1924 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 1925 aAutoNegReceivedTechnologyAbility." 1926 ::= { ifMauAutoNegEntry 7 } 1928 ifMauAutoNegRestart OBJECT-TYPE 1929 SYNTAX INTEGER { 1930 restart(1), 1931 norestart(2) 1932 } 1933 MAX-ACCESS read-write 1934 STATUS current 1935 DESCRIPTION "If the value of this object is set to 1936 restart(1) then this will force auto-negotiation 1937 to begin link renegotiation. If auto-negotiation 1938 signaling is disabled, a write to this object 1939 has no effect. 1941 Setting the value of this object to norestart(2) 1942 has no effect." 1943 REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1, 1944 acAutoNegRestartAutoConfig." 1945 ::= { ifMauAutoNegEntry 8 } 1947 ifMauAutoNegCapabilityBits OBJECT-TYPE 1948 SYNTAX BITS { 1949 bOther(0), -- other or unknown 1950 b10baseT(1), -- 10BASE-T half duplex mode 1951 b10baseTFD(2), -- 10BASE-T full duplex mode 1952 b100baseT4(3), -- 100BASE-T4 1953 b100baseTX(4), -- 100BASE-TX half duplex mode 1954 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1955 b100baseT2(6), -- 100BASE-T2 half duplex mode 1956 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1957 bfdxPause(8), -- PAUSE for full-duplex links 1958 bfdxAPause(9), -- Asymmetric PAUSE for full-duplex 1959 -- links 1960 bfdxSPause(10), -- Symmetric PAUSE for full-duplex 1961 -- links 1963 bfdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1964 -- full-duplex links 1965 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1966 -- duplex mode 1967 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1968 -- duplex mode 1969 b1000baseT(14), -- 1000BASE-T half duplex mode 1970 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1971 } 1972 MAX-ACCESS read-only 1973 STATUS current 1974 DESCRIPTION "A value that uniquely identifies the set of 1975 capabilities of the local auto-negotiation 1976 entity. Note that interfaces that support this 1977 MIB may have capabilities that extend beyond the 1978 scope of this MIB. 1980 Note that the local auto-negotiation entity may 1981 support some capabilities beyond the scope of 1982 this MIB. This is indicated by returning the 1983 bit value bOther in addition to any bit values 1984 for capabilities that are listed above." 1985 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, 1986 aAutoNegLocalTechnologyAbility." 1987 ::= { ifMauAutoNegEntry 9 } 1989 ifMauAutoNegCapAdvertisedBits OBJECT-TYPE 1990 SYNTAX BITS { 1991 bOther(0), -- other or unknown 1992 b10baseT(1), -- 10BASE-T half duplex mode 1993 b10baseTFD(2), -- 10BASE-T full duplex mode 1994 b100baseT4(3), -- 100BASE-T4 1995 b100baseTX(4), -- 100BASE-TX half duplex mode 1996 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1997 b100baseT2(6), -- 100BASE-T2 half duplex mode 1998 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1999 bFdxPause(8), -- PAUSE for full-duplex links 2000 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 2001 -- links 2002 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 2003 -- links 2004 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 2005 -- full-duplex links 2006 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 2007 -- duplex mode 2008 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 2009 -- duplex mode 2010 b1000baseT(14), -- 1000BASE-T half duplex mode 2011 b1000baseTFD(15) -- 1000BASE-T full duplex mode 2012 } 2013 MAX-ACCESS read-write 2014 STATUS current 2015 DESCRIPTION "A value that uniquely identifies the set of 2016 capabilities advertised by the local 2017 auto-negotiation entity. 2019 Capabilities in this object that are not 2020 available in ifMauAutoNegCapabilityBits cannot 2021 be enabled. 2023 Note that the local auto-negotiation entity may 2024 advertise some capabilities beyond the scope of 2025 this MIB. This is indicated by returning the 2026 bit value bOther in addition to any bit values 2027 for capabilities that are listed above." 2028 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 2029 aAutoNegAdvertisedTechnologyAbility." 2030 ::= { ifMauAutoNegEntry 10 } 2032 ifMauAutoNegCapReceivedBits OBJECT-TYPE 2033 SYNTAX BITS { 2034 bOther(0), -- other or unknown 2035 b10baseT(1), -- 10BASE-T half duplex mode 2036 b10baseTFD(2), -- 10BASE-T full duplex mode 2037 b100baseT4(3), -- 100BASE-T4 2038 b100baseTX(4), -- 100BASE-TX half duplex mode 2039 b100baseTXFD(5), -- 100BASE-TX full duplex mode 2040 b100baseT2(6), -- 100BASE-T2 half duplex mode 2041 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 2042 bFdxPause(8), -- PAUSE for full-duplex links 2043 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 2044 -- links 2045 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 2046 -- links 2047 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 2048 -- full-duplex links 2049 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 2050 -- duplex mode 2051 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 2052 -- duplex mode 2053 b1000baseT(14), -- 1000BASE-T half duplex mode 2054 b1000baseTFD(15) -- 1000BASE-T full duplex mode 2055 } 2056 MAX-ACCESS read-only 2057 STATUS current 2058 DESCRIPTION "A value that uniquely identifies the set of 2059 capabilities received from the remote 2060 auto-negotiation entity. 2062 Note that interfaces that support this MIB may 2063 be attached to remote auto-negotiation entities 2064 which have capabilities beyond the scope of this 2065 MIB. This is indicated by returning the bit 2066 value bOther in addition to any bit values for 2067 capabilities that are listed above." 2068 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 2069 aAutoNegReceivedTechnologyAbility." 2070 ::= { ifMauAutoNegEntry 11 } 2072 ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE 2073 SYNTAX INTEGER { 2074 noError(1), 2075 offline(2), 2076 linkFailure(3), 2077 autoNegError(4) 2078 } 2079 MAX-ACCESS read-write 2080 STATUS current 2081 DESCRIPTION "A value that identifies any local fault 2082 indications that this MAU has detected and will 2083 advertise at the next auto-negotiation 2084 interaction for 1000Mbps MAUs." 2085 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 2086 aAutoNegAdvertisedTechnologyAbility." 2087 ::= { ifMauAutoNegEntry 12 } 2089 ifMauAutoNegRemoteFaultReceived OBJECT-TYPE 2090 SYNTAX INTEGER { 2091 noError(1), 2092 offline(2), 2093 linkFailure(3), 2094 autoNegError(4) 2095 } 2096 MAX-ACCESS read-only 2097 STATUS current 2098 DESCRIPTION "A value that identifies any fault indications 2099 received from the far end of a link by the 2100 local auto-negotiation entity for 1000Mbps 2101 MAUs." 2102 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 2103 aAutoNegReceivedTechnologyAbility." 2104 ::= { ifMauAutoNegEntry 13 } 2106 -- 2107 -- The Basic Broadband MAU Table 2108 -- 2110 broadMauBasicTable OBJECT-TYPE 2111 SYNTAX SEQUENCE OF BroadMauBasicEntry 2112 MAX-ACCESS not-accessible 2113 STATUS deprecated 2114 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2116 Table of descriptive and status information 2117 about the broadband MAUs connected to 2118 interfaces." 2119 ::= { dot3BroadMauBasicGroup 1 } 2121 broadMauBasicEntry OBJECT-TYPE 2122 SYNTAX BroadMauBasicEntry 2123 MAX-ACCESS not-accessible 2124 STATUS deprecated 2125 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2127 An entry in the table, containing information 2128 about a single broadband MAU." 2129 INDEX { broadMauIfIndex, 2130 broadMauIndex 2131 } 2132 ::= { broadMauBasicTable 1 } 2134 BroadMauBasicEntry ::= 2135 SEQUENCE { 2136 broadMauIfIndex InterfaceIndex, 2137 broadMauIndex Integer32, 2138 broadMauXmtRcvSplitType INTEGER, 2139 broadMauXmtCarrierFreq Integer32, 2140 broadMauTranslationFreq Integer32 2141 } 2143 broadMauIfIndex OBJECT-TYPE 2144 SYNTAX InterfaceIndex 2145 MAX-ACCESS read-only 2146 STATUS deprecated 2147 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2149 This variable uniquely identifies the interface 2150 to which the MAU described by this entry is 2151 connected." 2152 REFERENCE "Reference RFC 2863, ifIndex." 2153 ::= { broadMauBasicEntry 1 } 2155 broadMauIndex OBJECT-TYPE 2156 SYNTAX Integer32 (1..2147483647) 2157 MAX-ACCESS read-only 2158 STATUS deprecated 2159 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2161 This variable uniquely identifies the MAU 2162 connected to interface broadMauIfIndex that is 2163 described by this entry." 2164 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 2165 ::= { broadMauBasicEntry 2 } 2167 broadMauXmtRcvSplitType OBJECT-TYPE 2168 SYNTAX INTEGER { 2169 other(1), 2170 single(2), 2171 dual(3) 2172 } 2173 MAX-ACCESS read-only 2174 STATUS deprecated 2175 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2177 This object indicates the type of frequency 2178 multiplexing/cabling system used to separate the 2179 transmit and receive paths for the 10BROAD36 2180 MAU. 2182 The value other(1) is returned if the split type 2183 is not either single or dual. 2185 The value single(2) indicates a single cable 2186 system. The value dual(3) indicates a dual 2187 cable system, offset normally zero." 2188 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.8, 2189 aBbMAUXmitRcvSplitType." 2190 ::= { broadMauBasicEntry 3 } 2192 broadMauXmtCarrierFreq OBJECT-TYPE 2193 SYNTAX Integer32 2194 MAX-ACCESS read-only 2195 STATUS deprecated 2196 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2198 This variable indicates the transmit carrier 2199 frequency of the 10BROAD36 MAU in MHz/4; that 2200 is, in units of 250 kHz." 2201 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, 2202 aBroadbandFrequencies.xmitCarrierFrequency." 2204 ::= { broadMauBasicEntry 4 } 2206 broadMauTranslationFreq OBJECT-TYPE 2207 SYNTAX Integer32 2208 MAX-ACCESS read-only 2209 STATUS deprecated 2210 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 2212 This variable indicates the translation offset 2213 frequency of the 10BROAD36 MAU in MHz/4; that 2214 is, in units of 250 kHz." 2215 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, 2216 aBroadbandFrequencies.translationFrequency." 2217 ::= { broadMauBasicEntry 5 } 2219 -- Notifications for use by 802.3 MAUs 2221 snmpDot3MauTraps OBJECT IDENTIFIER ::= { snmpDot3MauMgt 0 } 2223 rpMauJabberTrap NOTIFICATION-TYPE 2224 OBJECTS { rpMauJabberState } 2225 STATUS current 2226 DESCRIPTION "This trap is sent whenever a managed repeater 2227 MAU enters the jabber state. 2229 The agent MUST throttle the generation of 2230 consecutive rpMauJabberTraps so that there is at 2231 least a five-second gap between them." 2232 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 2233 notification." 2234 ::= { snmpDot3MauTraps 1 } 2236 ifMauJabberTrap NOTIFICATION-TYPE 2237 OBJECTS { ifMauJabberState } 2238 STATUS current 2239 DESCRIPTION "This trap is sent whenever a managed interface 2240 MAU enters the jabber state. 2242 The agent MUST throttle the generation of 2243 consecutive ifMauJabberTraps so that there is at 2244 least a five-second gap between them." 2245 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 2246 notification." 2247 ::= { snmpDot3MauTraps 2 } 2249 -- Conformance information 2251 mauModConf 2252 OBJECT IDENTIFIER ::= { mauMod 1 } 2253 mauModCompls 2254 OBJECT IDENTIFIER ::= { mauModConf 1 } 2255 mauModObjGrps 2256 OBJECT IDENTIFIER ::= { mauModConf 2 } 2257 mauModNotGrps 2258 OBJECT IDENTIFIER ::= { mauModConf 3 } 2260 -- Object groups 2262 mauRpGrpBasic OBJECT-GROUP 2263 OBJECTS { rpMauGroupIndex, 2264 rpMauPortIndex, 2265 rpMauIndex, 2266 rpMauType, 2267 rpMauStatus, 2268 rpMauMediaAvailable, 2269 rpMauMediaAvailableStateExits, 2270 rpMauJabberState, 2271 rpMauJabberingStateEnters 2272 } 2273 STATUS current 2274 DESCRIPTION "Basic conformance group for MAUs attached to 2275 repeater ports. This group is also the 2276 conformance specification for RFC 1515 2277 implementations." 2278 ::= { mauModObjGrps 1 } 2280 mauRpGrp100Mbs OBJECT-GROUP 2281 OBJECTS { rpMauFalseCarriers } 2282 STATUS current 2283 DESCRIPTION "Conformance group for MAUs attached to 2284 repeater ports with 100 Mb/s or greater 2285 capability." 2286 ::= { mauModObjGrps 2 } 2288 mauRpGrpJack OBJECT-GROUP 2289 OBJECTS { rpJackType } 2290 STATUS current 2291 DESCRIPTION "Conformance group for MAUs attached to 2292 repeater ports with managed jacks." 2293 ::= { mauModObjGrps 3 } 2295 mauIfGrpBasic OBJECT-GROUP 2296 OBJECTS { ifMauIfIndex, 2297 ifMauIndex, 2298 ifMauType, 2299 ifMauStatus, 2300 ifMauMediaAvailable, 2301 ifMauMediaAvailableStateExits, 2302 ifMauJabberState, 2303 ifMauJabberingStateEnters 2304 } 2305 STATUS current 2306 DESCRIPTION "Basic conformance group for MAUs attached to 2307 interfaces. This group also provides a 2308 conformance specification for RFC 1515 2309 implementations." 2310 ::= { mauModObjGrps 4 } 2312 mauIfGrp100Mbs OBJECT-GROUP 2313 OBJECTS { ifMauFalseCarriers, 2314 ifMauTypeList, 2315 ifMauDefaultType, 2316 ifMauAutoNegSupported 2317 } 2318 STATUS deprecated 2319 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2321 Conformance group for MAUs attached to 2322 interfaces with 100 Mb/s capability. 2324 This object group has been deprecated in favor 2325 of mauIfGrpHighCapacity." 2326 ::= { mauModObjGrps 5 } 2328 mauIfGrpJack OBJECT-GROUP 2329 OBJECTS { ifJackType } 2330 STATUS current 2331 DESCRIPTION "Conformance group for MAUs attached to 2332 interfaces with managed jacks." 2333 ::= { mauModObjGrps 6 } 2335 mauIfGrpAutoNeg OBJECT-GROUP 2336 OBJECTS { ifMauAutoNegAdminStatus, 2337 ifMauAutoNegRemoteSignaling, 2338 ifMauAutoNegConfig, 2339 ifMauAutoNegCapability, 2340 ifMauAutoNegCapAdvertised, 2341 ifMauAutoNegCapReceived, 2342 ifMauAutoNegRestart 2343 } 2345 STATUS deprecated 2346 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2348 Conformance group for MAUs attached to 2349 interfaces with managed auto-negotiation. 2351 This object group has been deprecated in favor 2352 of mauIfGrpAutoNeg2." 2353 ::= { mauModObjGrps 7 } 2355 mauBroadBasic OBJECT-GROUP 2356 OBJECTS { broadMauIfIndex, 2357 broadMauIndex, 2358 broadMauXmtRcvSplitType, 2359 broadMauXmtCarrierFreq, 2360 broadMauTranslationFreq 2361 } 2362 STATUS deprecated 2363 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2365 Conformance group for broadband MAUs attached 2366 to interfaces. 2368 This object group is deprecated. There have 2369 been no reported implementations of this group, 2370 and it was felt to be unlikely that there will 2371 be any future implementations." 2372 ::= { mauModObjGrps 8 } 2374 mauIfGrpHighCapacity OBJECT-GROUP 2375 OBJECTS { ifMauFalseCarriers, 2376 ifMauTypeListBits, 2377 ifMauDefaultType, 2378 ifMauAutoNegSupported 2379 } 2380 STATUS current 2381 DESCRIPTION "Conformance group for MAUs attached to 2382 interfaces with 100 Mb/s or greater capability." 2383 ::= { mauModObjGrps 9 } 2385 mauIfGrpAutoNeg2 OBJECT-GROUP 2386 OBJECTS { ifMauAutoNegAdminStatus, 2387 ifMauAutoNegRemoteSignaling, 2388 ifMauAutoNegConfig, 2389 ifMauAutoNegCapabilityBits, 2390 ifMauAutoNegCapAdvertisedBits, 2391 ifMauAutoNegCapReceivedBits, 2392 ifMauAutoNegRestart 2394 } 2395 STATUS current 2396 DESCRIPTION "Conformance group for MAUs attached to 2397 interfaces with managed auto-negotiation." 2398 ::= { mauModObjGrps 10 } 2400 mauIfGrpAutoNeg1000Mbps OBJECT-GROUP 2401 OBJECTS { ifMauAutoNegRemoteFaultAdvertised, 2402 ifMauAutoNegRemoteFaultReceived 2403 } 2404 STATUS current 2405 DESCRIPTION "Conformance group for 1000Mbps MAUs attached to 2406 interfaces with managed auto-negotiation." 2407 ::= { mauModObjGrps 11 } 2409 mauIfGrpHCStats OBJECT-GROUP 2410 OBJECTS { ifMauHCFalseCarriers } 2411 STATUS current 2412 DESCRIPTION "Conformance for high capacity statistics for 2413 MAUs attached to interfaces" 2414 ::= { mauModObjGrps 12 } 2416 -- Notification groups 2418 rpMauNotifications NOTIFICATION-GROUP 2419 NOTIFICATIONS { rpMauJabberTrap } 2420 STATUS current 2421 DESCRIPTION "Notifications for repeater MAUs." 2422 ::= { mauModNotGrps 1 } 2424 ifMauNotifications NOTIFICATION-GROUP 2425 NOTIFICATIONS { ifMauJabberTrap } 2426 STATUS current 2427 DESCRIPTION "Notifications for interface MAUs." 2428 ::= { mauModNotGrps 2 } 2430 -- Compliances 2432 mauModRpCompl MODULE-COMPLIANCE 2433 STATUS deprecated 2434 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2436 Compliance for MAUs attached to repeater 2437 ports. 2439 This compliance is deprecated and replaced by 2440 mauModRpCompl2, which corrects an oversight by 2441 allowing rpMauStatus to be implemented 2442 read-only." 2444 MODULE -- this module 2445 MANDATORY-GROUPS { mauRpGrpBasic } 2447 GROUP mauRpGrp100Mbs 2448 DESCRIPTION "Implementation of this optional group is 2449 recommended for MAUs which have 100Mb/s or 2450 greater capability." 2452 GROUP mauRpGrpJack 2453 DESCRIPTION "Implementation of this optional group is 2454 recommended for MAUs which have one or more 2455 external jacks." 2457 GROUP rpMauNotifications 2458 DESCRIPTION "Implementation of this group is recommended 2459 for MAUs attached to repeater ports." 2460 ::= { mauModCompls 1 } 2462 mauModIfCompl MODULE-COMPLIANCE 2463 STATUS deprecated 2464 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2466 Compliance for MAUs attached to interfaces. 2468 This compliance is deprecated and replaced by 2469 mauModIfCompl2." 2471 MODULE -- this module 2472 MANDATORY-GROUPS { mauIfGrpBasic } 2474 GROUP mauIfGrp100Mbs 2475 DESCRIPTION "Implementation of this optional group is 2476 recommended for MAUs which have 100Mb/s 2477 capability." 2479 GROUP mauIfGrpJack 2480 DESCRIPTION "Implementation of this optional group is 2481 recommended for MAUs which have one or more 2482 external jacks." 2484 GROUP mauIfGrpAutoNeg 2485 DESCRIPTION "Implementation of this group is mandatory 2486 for MAUs which support managed 2487 auto-negotiation." 2489 GROUP mauBroadBasic 2490 DESCRIPTION "Implementation of this group is mandatory 2491 for broadband MAUs." 2493 GROUP ifMauNotifications 2494 DESCRIPTION "Implementation of this group is recommended 2495 for MAUs attached to interfaces." 2496 ::= { mauModCompls 2 } 2498 mauModIfCompl2 MODULE-COMPLIANCE 2499 STATUS deprecated 2500 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2502 Compliance for MAUs attached to interfaces." 2504 MODULE -- this module 2505 MANDATORY-GROUPS { mauIfGrpBasic } 2507 GROUP mauIfGrpHighCapacity 2508 DESCRIPTION "Implementation of this optional group is 2509 recommended for MAUs which have 100Mb/s 2510 or greater capability." 2512 GROUP mauIfGrpJack 2513 DESCRIPTION "Implementation of this optional group is 2514 recommended for MAUs which have one or more 2515 external jacks." 2517 GROUP mauIfGrpAutoNeg2 2518 DESCRIPTION "Implementation of this group is mandatory 2519 for MAUs which support managed 2520 auto-negotiation." 2522 GROUP mauIfGrpAutoNeg1000Mbps 2523 DESCRIPTION "Implementation of this group is mandatory 2524 for MAUs which have 1000Mb/s or greater 2525 capability and support managed 2526 auto-negotiation." 2528 GROUP ifMauNotifications 2529 DESCRIPTION "Implementation of this group is recommended 2530 for MAUs attached to interfaces." 2532 OBJECT ifMauStatus 2533 MIN-ACCESS read-only 2534 DESCRIPTION "Write access is not required." 2536 ::= { mauModCompls 3 } 2538 mauModRpCompl2 MODULE-COMPLIANCE 2539 STATUS current 2540 DESCRIPTION "Compliance for MAUs attached to repeater 2541 ports." 2543 MODULE -- this module 2544 MANDATORY-GROUPS { mauRpGrpBasic } 2546 GROUP mauRpGrp100Mbs 2547 DESCRIPTION "Implementation of this optional group is 2548 recommended for MAUs which have 100Mb/s or 2549 greater capability." 2551 GROUP mauRpGrpJack 2552 DESCRIPTION "Implementation of this optional group is 2553 recommended for MAUs which have one or more 2554 external jacks." 2556 GROUP rpMauNotifications 2557 DESCRIPTION "Implementation of this group is recommended 2558 for MAUs attached to repeater ports." 2560 OBJECT rpMauStatus 2561 MIN-ACCESS read-only 2562 DESCRIPTION "Write access is not required." 2563 ::= { mauModCompls 4 } 2565 mauModIfCompl3 MODULE-COMPLIANCE 2566 STATUS current 2567 DESCRIPTION "Compliance for MAUs attached to interfaces." 2569 MODULE -- this module 2570 MANDATORY-GROUPS { mauIfGrpBasic } 2572 GROUP mauIfGrpHighCapacity 2573 DESCRIPTION "Implementation of this optional group is 2574 recommended for MAUs which have 100Mb/s 2575 or greater capability." 2577 GROUP mauIfGrpHCStats 2578 DESCRIPTION "Implemention of this group is mandatory 2579 for MAUs which have 1000Mb/s capacity, and 2580 is recommended for MAUs which have 100Mb/s 2581 capacity." 2583 GROUP mauIfGrpJack 2584 DESCRIPTION "Implementation of this optional group is 2585 recommended for MAUs which have one or more 2586 external jacks." 2588 GROUP mauIfGrpAutoNeg2 2589 DESCRIPTION "Implementation of this group is mandatory 2590 for MAUs which support managed 2591 auto-negotiation." 2593 GROUP mauIfGrpAutoNeg1000Mbps 2594 DESCRIPTION "Implementation of this group is mandatory 2595 for MAUs which have 1000Mb/s or greater 2596 capability and support managed 2597 auto-negotiation." 2599 GROUP ifMauNotifications 2600 DESCRIPTION "Implementation of this group is recommended 2601 for MAUs attached to interfaces." 2603 OBJECT ifMauStatus 2604 MIN-ACCESS read-only 2605 DESCRIPTION "Write access is not required." 2606 ::= { mauModCompls 5 } 2608 END 2610 5. Intellectual Property 2612 The IETF takes no position regarding the validity or scope of any 2613 intellectual property or other rights that might be claimed to 2614 pertain to the implementation or use of the technology described in 2615 this document or the extent to which any license under such rights 2616 might or might not be available; neither does it represent that it 2617 has made any effort to identify any such rights. Information on the 2618 IETF's procedures with respect to rights in standards-track and 2619 standards-related documentation can be found in BCP-11. Copies of 2620 claims of rights made available for publication and any assurances of 2621 licenses to be made available, or the result of an attempt made to 2622 obtain a general license or permission for the use of such 2623 proprietary rights by implementors or users of this specification can 2624 be obtained from the IETF Secretariat. 2626 The IETF invites any interested party to bring to its attention any 2627 copyrights, patents or patent applications, or other proprietary 2628 rights which may cover technology that may be required to practice 2629 this standard. Please address the information to the IETF Executive 2630 Director. 2632 6. Acknowledgements 2634 This document was produced by the IETF Ethernet Interfaces and Hub 2635 MIB Working Group, whose efforts were greatly advanced by the 2636 contributions of the following people: 2638 Mike Ayers 2639 Mike Heard 2640 Chuck Black 2641 John Flick 2642 Jeff Johnson 2643 Kam Lam 2644 Leon Leong 2645 Mike Lui 2646 Kerry McDonald 2647 K.C. Norseth 2648 Dave Perkins 2649 Dan Romascanu 2650 Andrew Smith 2651 Kaj Tesink 2652 Geoff Thompson 2653 Maurice Turcotte 2654 Paul Woodruff 2656 7. References 2658 Normative References 2660 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2661 J., Rose, M. and S. Waldbusser, "Structure of Management 2662 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 2663 1999. 2665 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2666 J., Rose, M. and S. Waldbusser, "Textual Conventions for 2667 SMIv2", STD 58, RFC 2579, April 1999. 2669 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 2670 J., Rose, M. and S. Waldbusser, "Conformance Statements 2671 for SMIv2", STD 58, RFC 2580, April 1999. 2673 [IEEE802.3] IEEE, IEEE Std 802.3, 2000 Edition: "Information 2674 technology - Telecommunications and information exchange 2675 between systems - Local and metropolitan area networks - 2676 Specific requirements - Part 3: Carrier sense multiple 2677 access with collision detection (CSMA/CD) access method 2678 and physical layer specifications", (Adopted by ISO/IEC 2679 and redesignated as ISO/IEC 8802-3:2000(E), 2000. 2681 [P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, 2682 IEEE Draft P802.3ae/D4.3, April 2002, work in 2683 progress. 2685 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2686 MIB using SMIv2", RFC 2863, June 2000. 2688 [RFC2108] de Graaf, K., D. Romascanu, D. McMaster, and K. 2689 McCloghrie, "Definitions of Managed Objects for IEEE 2690 802.3 Repeater Devices using SMIv2", RFC 2108, February 2691 1997. 2693 [ETHERIF] Flick, J., "Definitions of Managed Objects for the 2694 Ethernet-like Interface Types", work in progress, 2695 draft-ietf-hubmib-etherif-mib-v3-02.txt, May, 2002. 2697 Non-Normative References 2699 [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An 2700 Architecture for Describing SNMP Management Frameworks", 2701 RFC 2571, April 1999. 2703 [RFC1155] Rose, M. and K. McCloghrie, "Structure and 2704 Identification of Management Information for 2705 TCP/IP-based Internets", STD 16, RFC 1155, May 1990. 2707 [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions", 2708 STD 16, RFC 1212, March 1991. 2710 [RFC1215] Rose, M., "A Convention for Defining Traps for use with 2711 the SNMP", RFC 1215, March 1991. 2713 [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin, 2714 "Simple Network Management Protocol", STD 15, RFC 1157, 2715 May 1990. 2717 [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 2718 "Introduction to Community-based SNMPv2", RFC 1901, 2719 January 1996. 2721 [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 2722 "Transport Mappings for Version 2 of the Simple Network 2723 Management Protocol (SNMPv2)", RFC 1906, January 1996. 2725 [RFC2572] Case, J., Harrington, D., Presuhn R. and B. Wijnen, 2726 "Message Processing and Dispatching for the Simple 2727 Network Management Protocol (SNMP)", RFC 2572, May 1999. 2729 [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model 2730 (USM) for version 3 of the Simple Network Management 2731 Protocol (SNMPv3)", RFC 2574, May 1999. 2733 [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 2734 "Protocol Operations for Version 2 of the Simple Network 2735 Management Protocol (SNMPv2)", RFC 1905, January 1996. 2737 [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 2738 Applications", RFC 2573, May 1999. 2740 [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 2741 Access Control Model (VACM) for the Simple Network 2742 Management Protocol (SNMP)", RFC 2575, May 1999. 2744 [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, 2745 "Introduction to Version 3 of the Internet-Standard 2746 Network Management Framework", RFC 2570, April 1999. 2748 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2749 Requirements Levels", BCP 14, RFC 2119, March 1997. 2751 [RFC1907] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, 2752 "Management Information Base for Version 2 of the 2753 Simple Network Management Protocol (SNMPv2)", RFC 1907, 2754 January 1996. 2756 [RFC2668] Smith, A., Flick, J., deGraaf, K., Romascanu, D., 2757 McMaster, D., McCloghrie, K. and S. Roberts, 2758 "Definitions of Managed Objects for IEEE 802.3 Medium 2759 Attachment Units (MAUs)", RFC 2668, August 1999. 2761 [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, 2762 K. and S. Roberts, "Definitions of Managed Objects for 2763 IEEE 802.3 Medium Attachment Units (MAUs) using SMIv2", 2764 RFC 2239, November 1997. 2766 [RFC1515] McMaster, D., McCloghrie, K. and S. Roberts, 2767 "Definitions of Managed Objects for IEEE 802.3 Medium 2768 Attachment Units (MAUs)", RFC 1515, September 1993. 2770 [ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald, 2771 K., Norseth, K. C., and K. Tesink, "Definitions of 2772 Managed Objects for the Ethernet WAN Interface 2773 Sublayer", work in progress, 2774 draft-ietf-hubmib-wis-mib-04.txt, May 2002. 2776 8. Security Considerations 2778 There are a number of management objects defined in this MIB that 2779 have a MAX-ACCESS clause of read-write. Setting these objects can 2780 have a serious effect on the operation of the network, including: 2782 enabling or disabling a MAU 2783 changing a MAU's default type 2784 enabling, disabling or restarting autonegotiation 2785 modifying the capabilities that a MAU advertizes during 2786 autonegotiation. 2788 Such objects may be considered sensitive or vulnerable in some 2789 network environments. The support for SET operations in a non-secure 2790 environment without proper protection can have a negative effect on 2791 network operations. 2793 SNMPv1 by itself is such an insecure environment. Even if the 2794 network itself is secure (for example by using IPSec), even then, 2795 there is no control as to who on the secure network is allowed to 2796 access and GET/SET (read/change/create/delete) the objects in this 2797 MIB. 2799 It is recommended that the implementers consider the security 2800 features as provided by the SNMPv3 framework. Specifically, the use 2801 of the User-based Security Model RFC 2574 [RFC2574] and the View- 2802 based Access Control Model RFC 2575 [RFC2575] is recommended. 2804 It is then a customer/user responsibility to ensure that the SNMP 2805 entity giving access to an instance of this MIB, is properly 2806 configured to give access to those objects only to those principals 2807 (users) that have legitimate rights to access them. 2809 9. 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 2821 This section enumerates changes made to RFC 2668 to produce this 2822 document. 2824 (1) Updated references to the IEEE 802.3 standard to 2825 refer to the 2000 edition. 2827 (2) Added reference to 802.3ae. 2829 (3) Updated WG e-mail address. 2831 (4) The following DESCRIPTION clauses have been updated 2832 to reflect behaviour on 10 Gb/s interfaces: 2833 ifMauMediaAvailable. 2835 (5) OBJECT-IDENTITY definitions have been added for 10 gigabit 2836 MAU types. 2838 (6) Enumerations for 'pmdLinkFault', 'wisFrameLoss', 2839 'wisSignalLoss', pcsLinkFault', excessiveBER', 2840 'dxsLinkFault' and 'pxsLinkFault' have been 2841 added for the ifMauMediaAvailable object. 2843 (7) ifMauTypeListBits has been extended with bits for the 2844 10 Gb/s MAU types. 2846 (8) The MODULE-IDENTITY clause has been updated to 2847 reflect the changes in the MIB module. 2849 (9) MIB boilerplate in section 2 has been updated to the 2850 latest approved text. 2852 (10) Added 64-bit version of ifMauFalseCarriers, and updated 2853 compliances accordingly. 2855 (11) Added section on mapping of IEEE managed objects to the 2856 objects in this MIB module. 2858 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.