idnits 2.17.1 draft-ietf-hubmib-rfc3636bis-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5 on line 3193. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 3170. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 3177. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 3183. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == 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 RFC3636, but the header doesn't have an 'Obsoletes:' line to match this. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (October 24, 2005) is 6758 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.3' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.3ae' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.3ah' -- Possible downref: Non-RFC (?) normative reference: ref. 'IEEE802.3ak' ** Obsolete normative reference: RFC 2434 (Obsoleted by RFC 5226) -- Obsolete informational reference (is this intentional?): RFC 1515 (Obsoleted by RFC 3636) -- Obsolete informational reference (is this intentional?): RFC 2239 (Obsoleted by RFC 2668) -- Obsolete informational reference (is this intentional?): RFC 2668 (Obsoleted by RFC 3636) -- Obsolete informational reference (is this intentional?): RFC 3636 (Obsoleted by RFC 4836) Summary: 4 errors (**), 0 flaws (~~), 4 warnings (==), 16 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group E. Beili 3 Internet-Draft Actelis Networks 4 Expires: April 27, 2006 October 24, 2005 6 Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units 7 (MAUs) 8 draft-ietf-hubmib-rfc3636bis-02.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on April 27, 2006. 35 Copyright Notice 37 Copyright (C) The Internet Society (2005). 39 Abstract 41 This memo defines a portion of the Management Information Base (MIB) 42 for use with network management protocols in the Internet community. 43 In particular, it defines objects for managing IEEE 802.3 Medium 44 Attachment Units (MAUs). This memo obsoletes RFC 3636. It amends 45 that specification by moving MAU type OBJECT-IDENTITY definitions and 46 relevant textual conventions into a separate Internet Assigned Number 47 Authority (IANA) maintained MIB module. In addition, management 48 information is added to enable support for Ethernet in the First Mile 49 (EFM) and 10GBASE-CX4 MAUs. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. The Internet-Standard Management Framework . . . . . . . . . . 3 55 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 56 3.1. Relationship to RFC 3636 . . . . . . . . . . . . . . . . . 4 57 3.2. Relationship to RFC 2668 . . . . . . . . . . . . . . . . . 5 58 3.3. Relationship to RFC 2239 . . . . . . . . . . . . . . . . . 5 59 3.4. Relationship to RFC 1515 . . . . . . . . . . . . . . . . . 5 60 3.5. Relationship to other MIBs . . . . . . . . . . . . . . . . 5 61 3.5.1. Relationship to the Interfaces MIB . . . . . . . . . . 6 62 3.5.2. Relationship to the 802.3 Repeater MIB module . . . . 6 63 3.6. Management of Internal MAUs . . . . . . . . . . . . . . . 7 64 3.7. Management of IEEE 802.3 Managed Objects . . . . . . . . . 7 65 3.8. Addition of new MAU Types . . . . . . . . . . . . . . . . 8 66 3.8.1. dot3MauType OBJECT-IDENTITIES . . . . . . . . . . . . 8 67 3.8.2. IANAifMauTypeListBits Textual Convention . . . . . . . 9 68 3.8.3. JackType Textual Convention . . . . . . . . . . . . . 9 69 4. MAU MIB Definitions . . . . . . . . . . . . . . . . . . . . . 9 70 5. IANA-maintained MAU TC Definitions . . . . . . . . . . . . . . 51 71 6. Security Considerations . . . . . . . . . . . . . . . . . . . 62 72 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 63 73 8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 64 74 9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 64 75 9.1. Normative References . . . . . . . . . . . . . . . . . . . 64 76 9.2. Informative References . . . . . . . . . . . . . . . . . . 66 77 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 67 78 Intellectual Property and Copyright Statements . . . . . . . . . . 68 80 1. Introduction 82 This memo defines a portion of the Management Information Base (MIB) 83 for use with network management protocols in the Internet community. 84 In particular, it defines objects for managing IEEE 802.3 Medium 85 Attachment Units (MAUs). 87 The previous version of this memo, RFC 3636 [RFC3636], defined a 88 single MIB module. This memo splits the original MIB module into 89 two, putting frequently updated object identities and textual 90 conventions into a separate, IANA-maintained MIB module, in order to 91 decrease re-issues of the basic MIB module. 93 The first version of the IANA-maintained MIB module also extends the 94 list of managed objects to support Ethernet in the First Mile (EFM) 95 and 10GBASE-CX4 interfaces. 97 Ethernet technology, as defined by the 802.3 Working Group of the 98 IEEE, continues to evolve, with scalable increases in speed, new 99 types of cabling and interfaces, and new features. This evolution 100 may require changes in the managed objects in order to reflect this 101 new functionality. This document, as with other documents issued by 102 this working group, reflects a certain stage in the evolution of 103 Ethernet technology. In the future, this document might be revised, 104 or new documents might be issued by the Ethernet Interfaces and Hub 105 MIB Working Group, in order to reflect the evolution of Ethernet 106 technology. 108 2. The Internet-Standard Management Framework 110 For a detailed overview of the documents that describe the current 111 Internet-Standard Management Framework, please refer to section 7 of 112 RFC 3410 [RFC3410]. 114 Managed objects are accessed via a virtual information store, termed 115 the Management Information Base or MIB. MIB objects are generally 116 accessed through the Simple Network Management Protocol (SNMP). 117 Objects in the MIB are defined using the mechanisms defined in the 118 Structure of Management Information (SMI). This memo specifies a MIB 119 module that is compliant to the SMIv2, which is described in STD 58, 120 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 121 [RFC2580]. 123 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 124 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 125 document are to be interpreted as described in RFC 2119 [RFC2119]. 127 3. Overview 129 Instances of these object types represent attributes of an IEEE 802.3 130 MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD 131 standard [IEEE802.3]. These MAUs may be connected to IEEE 802.3 132 repeaters or to 802.3 (Ethernet-like) interfaces. For convenience 133 this document refers to these devices as "repeater MAUs" and 134 "interface MAUs." 136 The definitions presented here are based on Section 30.5, "Layer 137 Management for 10 Mb/s, 100 Mb/s, 1000 Mb/s and 10 Gb/s Medium 138 Attachment Units (MAUs)", Section 30.6, "Management for link Auto- 139 Negotiation", and Annex 30A, "GDMO Specifications for 802.3 managed 140 object classes" of IEEE Std. 802.3, 2002 edition [IEEE802.3], as 141 amended by IEEE Std. 802.3ae-2002 [IEEE802.3ae], IEEE Std. 802.3ah- 142 2004 [IEEE802.3ah] and IEEE Std. 802.3ak-2004 [IEEE802.3ak]. This 143 specification is intended to provide for management of all types of 144 Ethernet/802.3 MAUs. 146 3.1. Relationship to RFC 3636 148 The management definitions provided in this memo are intended to be a 149 superset of those defined by RFC 3636 [RFC3636]. 151 In order to decrease re-issues of this document due to the new MAU 152 type and/or Jack type introduction, all relevant object identities 153 and textual conventions have been moved to a separate, IANA- 154 maintained MIB module IANA-MAU-MIB, the first version of which is 155 defined in this memo. Thus when a new MAU type and/or Jack type is 156 defined by the IEEE 802.3 working group, only the IANA-maintained 157 module needs to be revised, leaving the basic MAU-MIB module defined 158 in this memo unchanged. 160 In addition, the new definitions are added to the IANA-maintained MIB 161 module, to support Ethernet in the First Mile (EFM) and 10GBASE-CX4 162 interfaces, defined in IEEE Std 802.3ah-2004 [IEEE802.3ah] and IEEE 163 Std 802.3ak-2004 [IEEE802.3ak] respectively. 165 It should be noted that the changes made in this revision will not be 166 entirely backward-compatible with MIB modules that currently import 167 MAU type object identity descriptors from the MAU-MIB; such modules 168 will need to be revised to import those DESCRIPTORS from the IANA- 169 MAU-MIB. Similarly, any management applications that process the 170 object identity definitions (e.g., to present the DESCRIPTION text to 171 a user) will need to be get those definitions from the IANA-MAU-MIB 172 instead of the MAU-MIB. While it is true that changes that require 173 such adjustments are not strictly compliant with the SMIv2 rules 174 governing MIB module revisions (see [RFC2578] Section 10), in this 175 case continued high maintenance costs that would result from not 176 making these changes maked the deviation from the rules justified. 177 It should be noted that the working group was not able to find any 178 examples of MIB modules or management applications that would 179 actually be negatively affected by the changes. 181 3.2. Relationship to RFC 2668 183 RFC 3636 was a replacement for RFC 2668 [RFC2668]. RFC 3636 included 184 all of the objects contained in RFC 2668, plus new and updated 185 definitions to provide management support for 10 Gb/s devices. 187 3.3. Relationship to RFC 2239 189 RFC 2668 was a replacement for RFC 2239 [RFC2239]. RFC 2668 defined 190 a superset of that defined by RFC 2239, which contained all of the 191 objects defined in RFC 2239, plus several new ones which provide 192 additional capabilities. The new objects provided management support 193 for: 195 o management of 1000 Mb/s devices 197 o management of PAUSE negotiation 199 o management of remote fault status 201 3.4. Relationship to RFC 1515 203 RFC 2239 was a replacement for RFC 1515 [RFC1515]. RFC 2239 defined 204 a superset of RFC 1515 which contained all of the objects defined in 205 RFC 1515, plus several new ones which provided additional 206 capabilities. The new objects in RFC 2239 provided management 207 support for: 209 o management of 100 Mb/s devices 211 o auto-negotiation on interface MAUs 213 o jack management 215 3.5. Relationship to other MIBs 217 It is assumed that an agent implementing this MIB will also implement 218 (at least) the 'system' group defined in the SNMPv2 MIB [RFC3418]. 219 The following sections identify other MIBs that such an agent should 220 implement. 222 3.5.1. Relationship to the Interfaces MIB 224 The sections of this document that define interface MAU-related 225 objects specify an extension to the Interfaces MIB [RFC2863]. An 226 agent implementing these interface-MAU related objects MUST also 227 implement the relevant groups of the ifCompliance3 MODULE-COMPLIANCE 228 statement of the Interface MIB. The value of the object ifMauIfIndex 229 is the same as the value of 'ifIndex' used to instantiate the 230 interface to which the given MAU is connected. 232 It is REQUIRED that an agent implementing the interface-MAU related 233 objects in this MIB will also fully comply with the dot3Compliance2 234 MODULE-COMPLIANCE statement of the Ethernet-like Interfaces MIB, 235 [RFC3635]. Furthermore, when the interface-MAU related objects are 236 used to manage a 10GBASE-W PHY -- i.e., when ifMauType is equal to 237 dot3MauType10GigBaseW or any other 10GBASE-W variant -- then the 238 agent MUST also support the Ethernet WAN Interface Sublayer (WIS) MIB 239 [RFC3637] and must follow the interface layering model specified 240 therein. In that case the value of the object ifMauIfIndex is the 241 same as the value of 'ifIndex' for the layer at the top of the stack, 242 i.e., for the ifTable entry that has 'ifType' equal to 243 ethernetCsmacd(6). If the interface-MAU related objects are used to 244 manage a PHY that allows the MAU type to be changed dynamically, then 245 the agent SHALL create ifTable, ifStackTable, and ifInvStackTable 246 entries that pertain to the WIS when ifMauDefaultType is changed to a 247 10GBASEW variant (i.e., one of dot3MauType10GigBaseW, 248 dot3MauType10GigBaseEW, dot3MauType10GigBaseLW, or 249 dot3MauType10GigBaseSW) from any other type, and shall destroy the 250 WIS-related entries when ifMauDefaultType is changed to a non- 251 10GBASE-W type. The agent SHALL also change the values of 252 'ifConnectorPresent' and 'ifHighSpeed' in the ifTable entry indexed 253 by ifMauIfIndex as specified in [RFC3635] and [RFC3637] when 254 ifMauDefaultType is manipulated in this way but SHALL NOT otherwise 255 alter that entry. 257 (Note that repeater ports are not represented as interfaces in the 258 Interface MIB.) 260 3.5.2. Relationship to the 802.3 Repeater MIB module 262 The section of this document that defines repeater MAU-related 263 objects specifies an extension to the 802.3 Repeater MIB defined in 264 [RFC2108]. An agent implementing these repeater-MAU related objects 265 MUST also comply with the snmpRptrModCompl compliance statement of 266 the 802.3 Repeater MIB module. 268 The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to 269 instantiate a repeater MAU variable SHALL be the same as the values 270 of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate the 271 port to which the given MAU is connected. 273 3.6. Management of Internal MAUs 275 In some situations, a MAU can be "internal" -- i.e., its 276 functionality is implemented entirely within a device. For example, 277 a managed repeater may contain an internal repeater-MAU and/or an 278 internal interface-MAU through which management communications 279 originating on one of the repeater's external ports pass in order to 280 reach the management agent associated with the repeater. Such 281 internal MAUs may or may not be managed. If they are managed, 282 objects describing their attributes should appear in the appropriate 283 MIB subtree: dot3RpMauBasicGroup for internal repeater-MAUs and 284 dot3IfMauBasicGroup for internal interface-MAUs. 286 3.7. Management of IEEE 802.3 Managed Objects 288 +----------------------------------+--------------------------------+ 289 | IEEE 802.3 Managed Object | Corresponding SNMP Object | 290 +----------------------------------+--------------------------------+ 291 | oMAU | | 292 | .aMAUID | rpMauIndex or ifMauIndex or | 293 | | broadMauIndex | 294 | .aMAUType | rpMauType or ifMauType | 295 | .aMAUTypeList | ifMauTypeListBits | 296 | .aMediaAvailable | rpMauMediaAvailable or | 297 | | ifMauMediaAvailable | 298 | .aLoseMediaCounter | rpMauMediaAvailableStateExits | 299 | | or | 300 | | ifMauMediaAvailableStateExits | 301 | .aJabber | rpMauJabberState and | 302 | | rpMauJabberingStateEnters or | 303 | | ifMauJabberState and | 304 | | ifMauJabberingStateEnters | 305 | .aMAUAdminState | rpMauStatus or ifMauStatus | 306 | .aBbMAUXmitRcvSplitType | broadMauXmtRcvSplitType | 307 | .aBroadbandFrequencies | broadMauXmtCarrierFreq and | 308 | | broadMauTranslationFreq | 309 | .aFalseCarriers | rpMauFalseCarriers or | 310 | | ifMauFalseCarriers | 311 | .acResetMAU | rpMauStatus or ifMauStatus | 312 | .acMAUAdminControl | rpMauStatus or ifMauStatus | 313 | .nJabber | rpMauJabberTrap or | 314 | | ifMauJabberTrap | 315 | oAutoNegotiation | | 316 | .aAutoNegID | ifMauIndex | 317 | .aAutoNegAdminState | ifMauAutoNegAdminStatus | 318 | .aAutoNegRemoteSignalling | ifMauAutoNegRemoteSignalling | 319 | .aAutoNegAutoConfig | ifMauAutoNegConfig | 320 | .aAutoNegLocalTechnologyAbility | ifMauAutoNegCapabilityBits | 321 | .aAutoNegAdvertisedTechnologyAbi | ifMauAutoNegAdvertisedBits and | 322 | lity | ifMauAutoNegRemoteFaultAdverti | 323 | | sed | 324 | .aAutoNegReceivedTechnologyAbili | ifMauAutoNegReceivedBits and | 325 | ty | ifMauAutoNegRemoteFaultReceive | 326 | | d | 327 | .acAutoNegRestartAutoConfig | ifMauAutoNegRestart | 328 | .acAutoNegAdminControl | ifMauAutoNegAdminStatus | 329 +----------------------------------+--------------------------------+ 331 Table 1 333 The following IEEE 802.3 managed objects have not been included in 334 this MIB for the following reasons. 336 +------------------------------------+------------------------------+ 337 | IEEE 802.3 Managed Object | Corresponding SNMP Object | 338 +------------------------------------+------------------------------+ 339 | oMAU | | 340 | .aIdleErrorCount | Only useful for 100BaseT2, | 341 | | which is not widely | 342 | | implemented. | 343 | oAutoNegotiation | | 344 | .aAutoNegLocalSelectorAbility | Only needed for support of | 345 | | isoethernet (802.9a), which | 346 | | is not supported by this | 347 | | MIB. | 348 | .aAutoNegAdvertisedSelectorAbility | | 349 | .aAutoNegReceivedSelectorAbility | | 350 +------------------------------------+------------------------------+ 352 Table 2 354 3.8. Addition of new MAU Types 356 3.8.1. dot3MauType OBJECT-IDENTITIES 358 The dot3MauType OBJECT IDENTIFIER and its OBJECT-IDENTITY definitions 359 has been moved from the MAU-MIB into the IANA-maintained IANA-MAU- 360 MIB, first version of which is defined in this memo. 362 When a new IEEE 802.3 MAU is defined, IANA can re-issue a version of 363 IANA-MAU-MIB with the new dot3MauType OBJECT-IDENTITY and its 364 matching IANAifMauTypeListBits textual convention value and, 365 possibly, with a new IANAifJackType value. 367 An Expert Review, as defined in RFC 2434 [RFC2434], is REQUIRED for 368 the addition of the new MAU and/or Jack types. 370 In some cases new MAU types may require additional managed objects or 371 may have side effects on the behavior of existing managed objects. 372 In such cases a standards-track specification (which may be a new 373 document or a revision of this document) is also REQUIRED. Any such 374 document is REQUIRED to note any special properties of the MAU types 375 that it defines - for example, side effects on the ifStackTable as 376 noted in this document for 10GBASE-W MAUs. 378 3.8.2. IANAifMauTypeListBits Textual Convention 380 The syntax of ifMauTypeListBits is changed to be a textual 381 convention, such that the enumerated integer values are now defined 382 in the textual convention, IANAifMauTypeListBits, which can be re- 383 specified (with additional values) in the IANA-maintained MIB module, 384 without issuing a new version of this document. 386 3.8.3. JackType Textual Convention 388 The JackType Textual Convention has been deprecated in favor of 389 IANAifJackType defined in the IANA-maintained MIB module, so the new 390 Jack types can be added (when defined by IEEE 802.3) without issuing 391 a new version of this document. 393 4. MAU MIB Definitions 395 MAU-MIB DEFINITIONS ::= BEGIN 397 IMPORTS 398 Counter32, Integer32, Counter64, 399 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 400 FROM SNMPv2-SMI -- RFC 2578 401 TruthValue, AutonomousType, TEXTUAL-CONVENTION 402 FROM SNMPv2-TC -- RFC 2579 403 OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP 404 FROM SNMPv2-CONF -- RFC 2580 405 InterfaceIndex 406 FROM IF-MIB -- RFC 2863 407 IANAifMauTypeListBits, IANAifJackType 408 FROM IANA-MAU-MIB -- RFC 3636bis 409 -- EdNote: Replace RFC 3636bis above with the URL of the 410 -- actual IANA-maintained module & remove this note. 411 ; 413 mauMod MODULE-IDENTITY 414 LAST-UPDATED "200510240000Z" -- Oct 24, 2005 415 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working Group" 416 CONTACT-INFO 417 "WG charter: 418 http://www.ietf.org/html.charters/hubmib-charter.html 420 Mailing Lists: 421 General Discussion: hubmib@ietf.org 422 To Subscribe: hubmib-request@ietf.org 423 In Body: subscribe your_email_address 425 Chair: Dan Romascanu 426 Postal: Avaya 427 Atidim Technology Park, Bldg. 3 428 Tel Aviv 61131 429 Israel 430 Tel: +972 3 645 8414 431 E-mail: dromasca@avaya.com 433 Editor: Edward Beili 434 Postal: Actelis Networks Inc. 435 25 Bazel St., P.O.B. 10173 436 Petach-Tikva 10173 437 Israel 438 Tel: +972-3-924-3491 439 E-mail: edward.beili@actelis.com" 441 DESCRIPTION 442 "Management information for 802.3 MAUs. 444 The following reference is used throughout this MIB module: 446 [IEEE 802.3 Std] refers to: 447 IEEE Std 802.3, 2002 Edition: 'IEEE Standard 448 for Information technology - 449 Telecommunications and information exchange 450 between systems - Local and metropolitan 451 area networks - Specific requirements - 452 Part 3: Carrier sense multiple access with 453 collision detection (CSMA/CD) access method 454 and physical layer specifications', as 455 amended by IEEE Std 802.3ae-2002: 456 'Amendment: Media Access Control (MAC) 457 Parameters, Physical Layer, and Management 458 Parameters for 10 Gb/s Operation', August, 459 2002. 461 Of particular interest is Clause 30, '10Mb/s, 462 100Mb/s, 1000Mb/s and 10 Gb/s Management'. 464 Copyright (C) The Internet Society (2004). This 465 version of this MIB module is part of RFC XXXX; 466 see the RFC itself for full legal notices." 468 REVISION "200510240000Z" -- Oct 24, 2005 469 DESCRIPTION "Updated to reference IANA maintaned textual 470 conventions for MAU types and jack types, 471 instead of using internally defined values. 473 This version is published as RFC XXXX." 474 -- EdNote: Replace XXXX with the actual RFC number 475 -- & remove this note. 477 REVISION "200309190000Z" -- September 19, 2003 478 DESCRIPTION "Updated to include support for 10 Gb/s MAUs. 479 This resulted in the following revisions: 480 - Added OBJECT-IDENTITY definitions for 481 10 gigabit MAU types 482 - Added fiberLC jack type to JackType TC 483 - Extended ifMauTypeListBits with bits for 484 the 10 gigabit MAU types 485 - Added enumerations to ifMauMediaAvailable, 486 and updated its DESCRIPTION to reflect 487 behaviour at 10 Gb/s 488 - Added 64-bit version of ifMauFalseCarriers 489 and added mauIfGrpHCStats object group to 490 contain the new object 491 - Deprecated mauModIfCompl2 and replaced it 492 with mauModIfCompl3, which includes the new 493 object group 495 This version published as RFC 3636." 497 REVISION "199908240400Z" -- August 24, 1999 498 DESCRIPTION "This version published as RFC 2668. Updated 499 to include support for 1000 Mb/sec 500 MAUs and flow control negotiation." 502 REVISION "199710310000Z" -- October 31, 1997 503 DESCRIPTION "Version published as RFC 2239." 505 REVISION "199309300000Z" -- September 30, 1993 506 DESCRIPTION "Initial version, published as RFC 1515." 508 ::= { snmpDot3MauMgt 6 } 510 snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } 512 -- Textual Conventions 514 JackType ::= TEXTUAL-CONVENTION 515 STATUS deprecated 516 DESCRIPTION "********* THIS TC IS DEPRECATED ********** 518 This TC has been deprecated in favour of 519 IANAifJackType. 521 Common enumeration values for repeater 522 and interface MAU jack types." 523 SYNTAX INTEGER { 524 other(1), 525 rj45(2), 526 rj45S(3), -- rj45 shielded 527 db9(4), 528 bnc(5), 529 fAUI(6), -- female aui 530 mAUI(7), -- male aui 531 fiberSC(8), 532 fiberMIC(9), 533 fiberST(10), 534 telco(11), 535 mtrj(12), -- fiber MT-RJ 536 hssdc(13), -- fiber channel style-2 537 fiberLC(14) 538 } 540 dot3RpMauBasicGroup 541 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } 542 dot3IfMauBasicGroup 543 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } 544 dot3BroadMauBasicGroup 545 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } 547 -- OIDs under the following branch are reserved for 548 -- the IANA-MAU-MIB to assign as MAU type values: 549 -- { snmpDot3MauMgt 4 } 551 dot3IfMauAutoNegGroup 552 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } 554 -- the following OID is the MODULE-IDENTITY value 555 -- for this MIB module: { snmpDot3MauMgt 6 } 557 -- the following OID is the MODULE-IDENTITY value 558 -- for the IANA-MAU-MIB: { snmpDot3MauMgt 7 } 560 -- 561 -- The Basic Repeater MAU Table 562 -- 564 rpMauTable OBJECT-TYPE 565 SYNTAX SEQUENCE OF RpMauEntry 566 MAX-ACCESS not-accessible 567 STATUS current 568 DESCRIPTION "Table of descriptive and status information 569 about the MAU(s) attached to the ports of a 570 repeater." 571 ::= { dot3RpMauBasicGroup 1 } 573 rpMauEntry OBJECT-TYPE 574 SYNTAX RpMauEntry 575 MAX-ACCESS not-accessible 576 STATUS current 577 DESCRIPTION "An entry in the table, containing information 578 about a single MAU." 579 INDEX { rpMauGroupIndex, 580 rpMauPortIndex, 581 rpMauIndex 582 } 583 ::= { rpMauTable 1 } 585 RpMauEntry ::= 586 SEQUENCE { 587 rpMauGroupIndex Integer32, 588 rpMauPortIndex Integer32, 589 rpMauIndex Integer32, 590 rpMauType AutonomousType, 591 rpMauStatus INTEGER, 592 rpMauMediaAvailable INTEGER, 593 rpMauMediaAvailableStateExits Counter32, 594 rpMauJabberState INTEGER, 595 rpMauJabberingStateEnters Counter32, 596 rpMauFalseCarriers Counter32 597 } 599 rpMauGroupIndex OBJECT-TYPE 600 SYNTAX Integer32 (1..2147483647) 601 MAX-ACCESS read-only -- read-only since originally an 602 -- SMIv1 index 603 STATUS current 604 DESCRIPTION "This variable uniquely identifies the group 605 containing the port to which the MAU described 606 by this entry is connected. 608 Note: In practice, a group will generally be 609 a field-replaceable unit (i.e., module, card, 610 or board) that can fit in the physical system 611 enclosure, and the group number will correspond 612 to a number marked on the physical enclosure. 614 The group denoted by a particular value of this 615 object is the same as the group denoted by the 616 same value of rptrGroupIndex." 617 REFERENCE "Reference RFC 2108, rptrGroupIndex." 618 ::= { rpMauEntry 1 } 620 rpMauPortIndex OBJECT-TYPE 621 SYNTAX Integer32 (1..2147483647) 622 MAX-ACCESS read-only -- read-only since originally an 623 -- SMIv1 index 624 STATUS current 625 DESCRIPTION "This variable uniquely identifies the repeater 626 port within group rpMauGroupIndex to which the 627 MAU described by this entry is connected." 628 REFERENCE "Reference RFC 2108, rptrPortIndex." 629 ::= { rpMauEntry 2 } 631 rpMauIndex OBJECT-TYPE 632 SYNTAX Integer32 (1..2147483647) 633 MAX-ACCESS read-only -- read-only since originally an 634 -- SMIv1 index 635 STATUS current 636 DESCRIPTION "This variable uniquely identifies the MAU 637 described by this entry from among other 638 MAUs connected to the same port 639 (rpMauPortIndex)." 640 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 641 ::= { rpMauEntry 3 } 643 rpMauType OBJECT-TYPE 644 SYNTAX AutonomousType 645 MAX-ACCESS read-only 646 STATUS current 647 DESCRIPTION "This object identifies the MAU type. Values for 648 standard IEEE 802.3 MAU types are defined in the 649 IANA maintained IANA-MAU-MIB module, as 650 OBJECT-IDENTITIES of dot3MauType. 651 If the MAU type is unknown, the object identifier 652 zeroDotZero is returned." 653 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." 654 ::= { rpMauEntry 4 } 656 rpMauStatus OBJECT-TYPE 657 SYNTAX INTEGER { 658 other(1), 659 unknown(2), 660 operational(3), 661 standby(4), 662 shutdown(5), 663 reset(6) 664 } 665 MAX-ACCESS read-write 666 STATUS current 667 DESCRIPTION "The current state of the MAU. This object MAY 668 be implemented as a read-only object by those 669 agents and MAUs that do not implement software 670 control of the MAU state. Some agents may not 671 support setting the value of this object to some 672 of the enumerated values. 674 The value other(1) is returned if the MAU is in 675 a state other than one of the states 2 through 676 6. 678 The value unknown(2) is returned when the MAU's 679 true state is unknown; for example, when it is 680 being initialized. 682 A MAU in the operational(3) state is fully 683 functional, operates, and passes signals to its 684 attached DTE or repeater port in accordance to 685 its specification. 687 A MAU in standby(4) state forces DI and CI to 688 idle and the media transmitter to idle or fault, 689 if supported. Standby(4) mode only applies to 690 link type MAUs. The state of 691 rpMauMediaAvailable is unaffected. 693 A MAU in shutdown(5) state assumes the same 694 condition on DI, CI, and the media transmitter 695 as though it were powered down or not connected. 696 The MAU MAY return other(1) value for the 697 rpMauJabberState and rpMauMediaAvailable objects 698 when it is in this state. For an AUI, this 699 state will remove power from the AUI. 701 Setting this variable to the value reset(6) 702 resets the MAU in the same manner as a 703 power-off, power-on cycle of at least one-half 704 second would. The agent is not required to 705 return the value reset (6). 707 Setting this variable to the value 708 operational(3), standby(4), or shutdown(5) 709 causes the MAU to assume the respective state 710 except that setting a mixing-type MAU or an AUI 711 to standby(4) will cause the MAU to enter the 712 shutdown state." 713 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, 714 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 715 acResetMAU." 716 ::= { rpMauEntry 5 } 718 rpMauMediaAvailable OBJECT-TYPE 719 SYNTAX INTEGER { 720 other(1), 721 unknown(2), 722 available(3), 723 notAvailable(4), 724 remoteFault(5), 725 invalidSignal(6), 726 remoteJabber(7), 727 remoteLinkLoss(8), 728 remoteTest(9), 729 offline(10), 730 autoNegError(11) 731 } 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 735 10BASE-T, 10BASE-F) then this is equivalent to 736 the link test fail state/low light function. 737 For an AUI or a coax (including broadband) MAU 738 this indicates whether or not loopback is 739 detected on the DI circuit. The value of this 740 attribute persists between packets for MAU types 741 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 743 The value other(1) is returned if the 744 mediaAvailable state is not one of 2 through 11. 746 The value unknown(2) is returned when the MAU's 747 true state is unknown; for example, when it is 748 being initialized. At power-up or following a 749 reset, the value of this attribute will be 750 unknown for AUI, coax, and 10BASE-FP MAUs. For 751 these MAUs loopback will be tested on each 752 transmission during which no collision is 753 detected. If DI is receiving input when DO 754 returns to IDL after a transmission and there 755 has been no collision during the transmission 756 then loopback will be detected. The value of 757 this attribute will only change during 758 non-collided transmissions for AUI, coax, and 759 10BASE-FP MAUs. 761 For 100Mbps and 1000Mbps MAUs, the enumerations 762 match the states within the respective link 763 integrity state diagrams, fig 32-16, 23-12 and 764 24-15 of sections 32, 23 and 24 of [IEEE802.3]. 765 Any MAU which implements management of 766 auto-negotiation will map remote fault 767 indication to remote fault. 769 The value available(3) indicates that the link, 770 light, or loopback is normal. The value 771 notAvailable(4) indicates link loss, low light, 772 or no loopback. 774 The value remoteFault(5) indicates that a fault 775 has been detected at the remote end of the link. 776 This value applies to 10BASE-FB, 100BASE-T4 Far 777 End Fault Indication and non-specified remote 778 faults from a system running auto-negotiation. 779 The values remoteJabber(7), remoteLinkLoss(8), 780 and remoteTest(9) SHOULD be used instead of 781 remoteFault(5) where the reason for remote fault 782 is identified in the remote signaling protocol. 784 The value invalidSignal(6) indicates that an 785 invalid signal has been received from the other 786 end of the link. invalidSignal(6) applies only 787 to MAUs of type 10BASE-FB. 789 Where an IEEE Std 802.3-2002 clause 22 MII 790 is present, a logic one in the remote fault bit 791 (reference section 22.2.4.2.8 of that document) 792 maps to the value remoteFault(5), and a logic 793 zero in the link status bit (reference section 794 22.2.4.2.10 of that document) maps to the value 795 notAvailable(4). The value notAvailable(4) 796 takes precedence over the value remoteFault(5). 798 Any MAU that implements management of clause 37 799 Auto-Negotiation will map the received Remote 800 Fault (RF1 and RF2) bit values for Offline to 801 offline(10), Link Failure to remoteFault(5) and 802 Auto-Negotiation Error to autoNegError(11)." 804 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." 805 ::= { rpMauEntry 6 } 807 rpMauMediaAvailableStateExits OBJECT-TYPE 808 SYNTAX Counter32 809 MAX-ACCESS read-only 810 STATUS current 811 DESCRIPTION "A count of the number of times that 812 rpMauMediaAvailable for this MAU instance leaves 813 the state available(3). 815 Discontinuities in the value of this counter can 816 occur at re-initialization of the management 817 system, and at other times as indicated by the 818 value of rptrMonitorPortLastChange." 819 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, 820 aLoseMediaCounter. 821 RFC 2108, rptrMonitorPortLastChange" 822 ::= { rpMauEntry 7 } 824 rpMauJabberState OBJECT-TYPE 825 SYNTAX INTEGER { 826 other(1), 827 unknown(2), 828 noJabber(3), 829 jabbering(4) 830 } 831 MAX-ACCESS read-only 832 STATUS current 833 DESCRIPTION "The value other(1) is returned if the jabber 834 state is not 2, 3, or 4. The agent MUST always 835 return other(1) for MAU type dot3MauTypeAUI. 837 The value unknown(2) is returned when the MAU's 838 true state is unknown; for example, when it is 839 being initialized. 841 If the MAU is not jabbering the agent returns 842 noJabber(3). This is the 'normal' state. 844 If the MAU is in jabber state the agent returns 845 the jabbering(4) value." 847 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 848 aJabber.jabberFlag." 849 ::= { rpMauEntry 8 } 851 rpMauJabberingStateEnters OBJECT-TYPE 852 SYNTAX Counter32 853 MAX-ACCESS read-only 854 STATUS current 855 DESCRIPTION "A count of the number of times that 856 mauJabberState for this MAU instance enters the 857 state jabbering(4). For MAUs of type 858 dot3MauTypeAUI, dot3MauType100BaseT4, 859 dot3MauType100BaseTX, dot3MauType100BaseFX and 860 all 1000Mbps types, this counter will always 861 indicate zero. 863 Discontinuities in the value of this counter can 864 occur at re-initialization of the management 865 system, and at other times as indicated by the 866 value of rptrMonitorPortLastChange." 867 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 868 aJabber.jabberCounter. 869 RFC 2108, rptrMonitorPortLastChange" 870 ::= { rpMauEntry 9 } 872 rpMauFalseCarriers OBJECT-TYPE 873 SYNTAX Counter32 874 MAX-ACCESS read-only 875 STATUS current 876 DESCRIPTION "A count of the number of false carrier events 877 during IDLE in 100BASE-X links. This counter 878 does not increment at the symbol rate. It can 879 increment after a valid carrier completion at a 880 maximum rate of once per 100 ms until the next 881 carrier event. 883 This counter increments only for MAUs of type 884 dot3MauType100BaseT4, dot3MauType100BaseTX, and 885 dot3MauType100BaseFX and all 1000Mbps types. 887 For all other MAU types, this counter will 888 always indicate zero. 890 The approximate minimum time for rollover of 891 this counter is 7.4 hours. 893 Discontinuities in the value of this counter can 894 occur at re-initialization of the management 895 system, and at other times as indicated by the 896 value of rptrMonitorPortLastChange." 897 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. 898 RFC 2108, rptrMonitorPortLastChange" 899 ::= { rpMauEntry 10 } 901 -- The rpJackTable applies to MAUs attached to repeaters 902 -- which have one or more external jacks (connectors). 904 rpJackTable OBJECT-TYPE 905 SYNTAX SEQUENCE OF RpJackEntry 906 MAX-ACCESS not-accessible 907 STATUS current 908 DESCRIPTION "Information about the external jacks attached 909 to MAUs attached to the ports of a repeater." 910 ::= { dot3RpMauBasicGroup 2 } 912 rpJackEntry OBJECT-TYPE 913 SYNTAX RpJackEntry 914 MAX-ACCESS not-accessible 915 STATUS current 916 DESCRIPTION "An entry in the table, containing information 917 about a particular jack." 918 INDEX { rpMauGroupIndex, 919 rpMauPortIndex, 920 rpMauIndex, 921 rpJackIndex 922 } 923 ::= { rpJackTable 1 } 925 RpJackEntry ::= 926 SEQUENCE { 927 rpJackIndex Integer32, 928 rpJackType IANAifJackType 929 } 931 rpJackIndex OBJECT-TYPE 932 SYNTAX Integer32 (1..2147483647) 933 MAX-ACCESS not-accessible 934 STATUS current 935 DESCRIPTION "This variable uniquely identifies the jack 936 described by this entry from among other jacks 937 attached to the same MAU (rpMauIndex)." 938 ::= { rpJackEntry 1 } 940 rpJackType OBJECT-TYPE 941 SYNTAX IANAifJackType 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION "The jack connector type, as it appears on the 945 outside of the system." 946 ::= { rpJackEntry 2 } 948 -- 949 -- The Basic Interface MAU Table 950 -- 952 ifMauTable OBJECT-TYPE 953 SYNTAX SEQUENCE OF IfMauEntry 954 MAX-ACCESS not-accessible 955 STATUS current 956 DESCRIPTION "Table of descriptive and status information 957 about MAU(s) attached to an interface." 958 ::= { dot3IfMauBasicGroup 1 } 960 ifMauEntry OBJECT-TYPE 961 SYNTAX IfMauEntry 962 MAX-ACCESS not-accessible 963 STATUS current 964 DESCRIPTION "An entry in the table, containing information 965 about a single MAU." 966 INDEX { ifMauIfIndex, 967 ifMauIndex 968 } 969 ::= { ifMauTable 1 } 971 IfMauEntry ::= 972 SEQUENCE { 973 ifMauIfIndex InterfaceIndex, 974 ifMauIndex Integer32, 975 ifMauType AutonomousType, 976 ifMauStatus INTEGER, 977 ifMauMediaAvailable INTEGER, 978 ifMauMediaAvailableStateExits Counter32, 979 ifMauJabberState INTEGER, 980 ifMauJabberingStateEnters Counter32, 981 ifMauFalseCarriers Counter32, 982 ifMauTypeList Integer32, 983 ifMauDefaultType AutonomousType, 984 ifMauAutoNegSupported TruthValue, 985 ifMauTypeListBits IANAifMauTypeListBits, 986 ifMauHCFalseCarriers Counter64 987 } 989 ifMauIfIndex OBJECT-TYPE 990 SYNTAX InterfaceIndex 991 MAX-ACCESS read-only -- read-only since originally an 992 -- SMIv1 index 993 STATUS current 994 DESCRIPTION "This variable uniquely identifies the interface 995 to which the MAU described by this entry is 996 connected." 997 REFERENCE "RFC 2863, ifIndex" 998 ::= { ifMauEntry 1 } 1000 ifMauIndex OBJECT-TYPE 1001 SYNTAX Integer32 (1..2147483647) 1002 MAX-ACCESS read-only -- read-only since originally an 1003 -- SMIv1 index 1004 STATUS current 1005 DESCRIPTION "This variable uniquely identifies the MAU 1006 described by this entry from among other MAUs 1007 connected to the same interface (ifMauIfIndex)." 1008 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 1009 ::= { ifMauEntry 2 } 1011 ifMauType OBJECT-TYPE 1012 SYNTAX AutonomousType 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION "This object identifies the MAU type. Values for 1016 standard IEEE 802.3 MAU types are defined in the 1017 IANA maintained IANA-MAU-MIB module, as 1018 OBJECT-IDENTITIES of dot3MauType. 1019 If the MAU type is unknown, the object identifier 1020 zeroDotZero is returned. 1022 This object represents the operational type of 1023 the MAU, as determined by either (1) the result 1024 of the auto-negotiation function or (2) if 1025 auto-negotiation is not enabled or is not 1026 implemented for this MAU, by the value of the 1027 object ifMauDefaultType. In case (2), a set to 1028 the object ifMauDefaultType will force the MAU 1029 into the new operating mode." 1030 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.2, aMAUType." 1031 ::= { ifMauEntry 3 } 1033 ifMauStatus OBJECT-TYPE 1034 SYNTAX INTEGER { 1035 other(1), 1036 unknown(2), 1037 operational(3), 1038 standby(4), 1039 shutdown(5), 1040 reset(6) 1041 } 1042 MAX-ACCESS read-write 1043 STATUS current 1044 DESCRIPTION "The current state of the MAU. This object MAY 1045 be implemented as a read-only object by those 1046 agents and MAUs that do not implement software 1047 control of the MAU state. Some agents may not 1048 support setting the value of this object to some 1049 of the enumerated values. 1051 The value other(1) is returned if the MAU is in 1052 a state other than one of the states 2 through 1053 6. 1055 The value unknown(2) is returned when the MAU's 1056 true state is unknown; for example, when it is 1057 being initialized. 1059 A MAU in the operational(3) state is fully 1060 functional, operates, and passes signals to its 1061 attached DTE or repeater port in accordance to 1062 its specification. 1064 A MAU in standby(4) state forces DI and CI to 1065 idle and the media transmitter to idle or fault, 1066 if supported. Standby(4) mode only applies to 1067 link type MAUs. The state of 1068 ifMauMediaAvailable is unaffected. 1070 A MAU in shutdown(5) state assumes the same 1071 condition on DI, CI, and the media transmitter 1072 as though it were powered down or not connected. 1073 The MAU MAY return other(1) value for the 1074 ifMauJabberState and ifMauMediaAvailable objects 1075 when it is in this state. For an AUI, this 1076 state will remove power from the AUI. 1078 Setting this variable to the value reset(6) 1079 resets the MAU in the same manner as a 1080 power-off, power-on cycle of at least one-half 1081 second would. The agent is not required to 1082 return the value reset (6). 1084 Setting this variable to the value 1085 operational(3), standby(4), or shutdown(5) 1086 causes the MAU to assume the respective state 1087 except that setting a mixing-type MAU or an AUI 1088 to standby(4) will cause the MAU to enter the 1089 shutdown state." 1090 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.7, aMAUAdminState, 1091 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 1092 acResetMAU." 1093 ::= { ifMauEntry 4 } 1095 ifMauMediaAvailable OBJECT-TYPE 1096 SYNTAX INTEGER { 1097 other(1), 1098 unknown(2), 1099 available(3), 1100 notAvailable(4), 1101 remoteFault(5), 1102 invalidSignal(6), 1103 remoteJabber(7), 1104 remoteLinkLoss(8), 1105 remoteTest(9), 1106 offline(10), 1107 autoNegError(11), 1108 pmdLinkFault(12), 1109 wisFrameLoss(13), 1110 wisSignalLoss(14), 1111 pcsLinkFault(15), 1112 excessiveBER(16), 1113 dxsLinkFault(17), 1114 pxsLinkFault(18) 1115 } 1116 MAX-ACCESS read-only 1117 STATUS current 1118 DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 1119 10BASE-T, 10BASE-F) then this is equivalent to 1120 the link test fail state/low light function. 1121 For an AUI or a coax (including broadband) MAU 1122 this indicates whether or not loopback is 1123 detected on the DI circuit. The value of this 1124 attribute persists between packets for MAU types 1125 AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 1127 The value other(1) is returned if the 1128 mediaAvailable state is not one of 2 through 18. 1130 The value unknown(2) is returned when the MAU's 1131 true state is unknown; for example, when it is 1132 being initialized. At power-up or following a 1133 reset, the value of this attribute will be 1134 unknown for AUI, coax, and 10BASE-FP MAUs. For 1135 these MAUs loopback will be tested on each 1136 transmission during which no collision is 1137 detected. If DI is receiving input when DO 1138 returns to IDL after a transmission and there 1139 has been no collision during the transmission 1140 then loopback will be detected. The value of 1141 this attribute will only change during 1142 non-collided transmissions for AUI, coax, and 1143 10BASE-FP MAUs. 1145 For 100Mbps and 1000Mbps MAUs, the enumerations 1146 match the states within the respective link 1147 integrity state diagrams, fig 32-16, 23-12 and 1148 24-15 of sections 32, 23 and 24 of [IEEE802.3]. 1149 Any MAU which implements management of 1150 auto-negotiation will map remote fault 1151 indication to remote fault. 1153 The value available(3) indicates that the link, 1154 light, or loopback is normal. The value 1155 notAvailable(4) indicates link loss, low light, 1156 or no loopback. 1158 The value remoteFault(5) indicates that a fault 1159 has been detected at the remote end of the link. 1160 This value applies to 10BASE-FB, 100BASE-T4 Far 1161 End Fault Indication and non-specified remote 1162 faults from a system running auto-negotiation. 1163 The values remoteJabber(7), remoteLinkLoss(8), 1164 and remoteTest(9) SHOULD be used instead of 1165 remoteFault(5) where the reason for remote fault 1166 is identified in the remote signaling protocol. 1167 The value invalidSignal(6) indicates that an 1168 invalid signal has been received from the other 1169 end of the link. invalidSignal(6) applies only 1170 to MAUs of type 10BASE-FB. 1172 Where an IEEE Std 802.3-2002 clause 22 MII 1173 is present, a logic one in the remote fault bit 1174 (reference section 22.2.4.2.8 of that document) 1175 maps to the value remoteFault(5), and a logic 1176 zero in the link status bit (reference section 1177 22.2.4.2.10 of that document) maps to the value 1178 notAvailable(4). The value notAvailable(4) 1179 takes precedence over the value remoteFault(5). 1181 Any MAU that implements management of clause 37 1182 Auto-Negotiation will map the received RF1 and 1183 RF2 bit values for Offline to offline(10), Link 1184 Failure to remoteFault(5) and Auto-Negotiation 1185 Error to autoNegError(11). 1187 For 10 Gb/s, the enumerations map to the states 1188 within the Reconciliation Sublayer state diagram 1189 as follows: 1190 NoFault maps to the enumeration 'available(3)' 1191 LocalFault maps to the enumeration 1192 'notAvailable(4)' 1193 RemoteFault maps to the enumeration 1194 'remoteFault(5)' 1195 The enumerations 'pmdLinkFault(12)', 1196 'wisFrameLoss(13)', 'wisSignalLoss(14)', 1197 'pcsLinkFault(15)', 'excessiveBER(16)', and 1198 'dxsLinkFault(17)' and 'pxsLinkFault(18)' should 1199 be used instead of the enumeration 1200 'notAvailable(4)' where the reason for the local 1201 fault can be identified through the use of the 1202 MDIO Interface. Where multiple reasons for the 1203 local fault state can be identified only the 1204 highest precedence error should be reported. 1205 The precedence in descending order is as 1206 follows: 1207 pxsLinkFault 1208 pmdLinkFault 1209 wisFrameLoss 1210 wisSignalLoss 1211 pcsLinkFault 1212 excessiveBER 1213 dxsLinkFault" 1214 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.4, aMediaAvailable." 1216 ::= { ifMauEntry 5 } 1218 ifMauMediaAvailableStateExits OBJECT-TYPE 1219 SYNTAX Counter32 1220 MAX-ACCESS read-only 1221 STATUS current 1222 DESCRIPTION "A count of the number of times that 1223 ifMauMediaAvailable for this MAU instance leaves 1224 the state available(3). 1226 Discontinuities in the value of this counter can 1227 occur at re-initialization of the management 1228 system, and at other times as indicated by the 1229 value of ifCounterDiscontinuityTime." 1230 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.5, 1231 aLoseMediaCounter. 1232 RFC 2863, ifCounterDiscontinuityTime." 1233 ::= { ifMauEntry 6 } 1235 ifMauJabberState OBJECT-TYPE 1236 SYNTAX INTEGER { 1237 other(1), 1238 unknown(2), 1239 noJabber(3), 1240 jabbering(4) 1241 } 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION "The value other(1) is returned if the jabber 1245 state is not 2, 3, or 4. The agent MUST always 1246 return other(1) for MAU type dot3MauTypeAUI. 1248 The value unknown(2) is returned when the MAU's 1249 true state is unknown; for example, when it is 1250 being initialized. 1252 If the MAU is not jabbering the agent returns 1253 noJabber(3). This is the 'normal' state. 1255 If the MAU is in jabber state the agent returns 1256 the jabbering(4) value." 1257 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1258 aJabber.jabberFlag." 1259 ::= { ifMauEntry 7 } 1261 ifMauJabberingStateEnters OBJECT-TYPE 1262 SYNTAX Counter32 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION "A count of the number of times that 1266 mauJabberState for this MAU instance enters the 1267 state jabbering(4). This counter will always 1268 indicate zero for MAUs of type dot3MauTypeAUI 1269 and those of speeds above 10Mbps. 1271 Discontinuities in the value of this counter can 1272 occur at re-initialization of the management 1273 system, and at other times as indicated by the 1274 value of ifCounterDiscontinuityTime." 1275 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.6, 1276 aJabber.jabberCounter. 1277 RFC 2863, ifCounterDiscontinuityTime." 1278 ::= { ifMauEntry 8 } 1280 ifMauFalseCarriers OBJECT-TYPE 1281 SYNTAX Counter32 1282 MAX-ACCESS read-only 1283 STATUS current 1284 DESCRIPTION "A count of the number of false carrier events 1285 during IDLE in 100BASE-X and 1000BASE-X links. 1287 For all other MAU types, this counter will 1288 always indicate zero. This counter does not 1289 increment at the symbol rate. 1291 It can increment after a valid carrier 1292 completion at a maximum rate of once per 100 ms 1293 for 100BASE-X and once per 10us for 1000BASE-X 1294 until the next CarrierEvent. 1296 This counter can roll over very quickly. A 1297 management station is advised to poll the 1298 ifMauHCFalseCarriers instead of this counter in 1299 order to avoid loss of information. 1301 Discontinuities in the value of this counter can 1302 occur at re-initialization of the management 1303 system, and at other times as indicated by the 1304 value of ifCounterDiscontinuityTime." 1305 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. 1306 RFC 2863, ifCounterDiscontinuityTime." 1307 ::= { ifMauEntry 9 } 1309 ifMauTypeList OBJECT-TYPE 1310 SYNTAX Integer32 1311 MAX-ACCESS read-only 1312 STATUS deprecated 1313 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1315 This object has been deprecated in favour of 1316 ifMauTypeListBits. 1318 A value that uniquely identifies the set of 1319 possible IEEE 802.3 types that the MAU could be. 1320 The value is a sum which initially takes the 1321 value zero. Then, for each type capability of 1322 this MAU, 2 raised to the power noted below is 1323 added to the sum. For example, a MAU which has 1324 the capability to be only 10BASE-T would have a 1325 value of 512 (2**9). In contrast, a MAU which 1326 supports both 10Base-T (full duplex) and 1327 100BASE-TX (full duplex) would have a value of 1328 ((2**11) + (2**16)) or 67584. 1330 The powers of 2 assigned to the capabilities are 1331 these: 1333 Power Capability 1334 0 other or unknown 1335 1 AUI 1336 2 10BASE-5 1337 3 FOIRL 1338 4 10BASE-2 1339 5 10BASE-T duplex mode unknown 1340 6 10BASE-FP 1341 7 10BASE-FB 1342 8 10BASE-FL duplex mode unknown 1343 9 10BROAD36 1344 10 10BASE-T half duplex mode 1345 11 10BASE-T full duplex mode 1346 12 10BASE-FL half duplex mode 1347 13 10BASE-FL full duplex mode 1348 14 100BASE-T4 1349 15 100BASE-TX half duplex mode 1350 16 100BASE-TX full duplex mode 1351 17 100BASE-FX half duplex mode 1352 18 100BASE-FX full duplex mode 1353 19 100BASE-T2 half duplex mode 1354 20 100BASE-T2 full duplex mode 1356 If auto-negotiation is present on this MAU, this 1357 object will map to ifMauAutoNegCapability." 1358 ::= { ifMauEntry 10 } 1360 ifMauDefaultType OBJECT-TYPE 1361 SYNTAX AutonomousType 1362 MAX-ACCESS read-write 1363 STATUS current 1364 DESCRIPTION "This object identifies the default 1365 administrative baseband MAU type, to be used in 1366 conjunction with the operational MAU type 1367 denoted by ifMauType. 1369 The set of possible values for this object is 1370 the same as the set defined for the ifMauType 1371 object. 1373 This object represents the 1374 administratively-configured type of the MAU. If 1375 auto-negotiation is not enabled or is not 1376 implemented for this MAU, the value of this 1377 object determines the operational type of the 1378 MAU. In this case, a set to this object will 1379 force the MAU into the specified operating mode. 1381 If auto-negotiation is implemented and enabled 1382 for this MAU, the operational type of the MAU 1383 is determined by auto-negotiation, and the value 1384 of this object denotes the type to which the MAU 1385 will automatically revert if/when 1386 auto-negotiation is later disabled. 1388 NOTE TO IMPLEMENTORS: It may be necessary to 1389 provide for underlying hardware implementations 1390 which do not follow the exact behavior specified 1391 above. In particular, when 1392 ifMauAutoNegAdminStatus transitions from enabled 1393 to disabled, the agent implementation MUST 1394 ensure that the operational type of the MAU (as 1395 reported by ifMauType) correctly transitions to 1396 the value specified by this object, rather than 1397 continuing to operate at the value earlier 1398 determined by the auto-negotiation function." 1399 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID, and 1400 22.2.4.1.4." 1401 ::= { ifMauEntry 11 } 1403 ifMauAutoNegSupported OBJECT-TYPE 1404 SYNTAX TruthValue 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION "This object indicates whether or not 1408 auto-negotiation is supported on this MAU." 1409 ::= { ifMauEntry 12 } 1411 ifMauTypeListBits OBJECT-TYPE 1412 SYNTAX IANAifMauTypeListBits 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION "A value that uniquely identifies the set of 1416 possible IEEE 802.3 types that the MAU could be. 1417 If auto-negotiation is present on this MAU, this 1418 object will map to ifMauAutoNegCapabilityBits. 1420 Note that this MAU may be capable of operating 1421 as a MAU type that is beyond the scope of this 1422 MIB. This is indicated by returning the 1423 bit value bOther in addition to any bit values 1424 for standard capabilities that are listed in the 1425 IANAifMauTypeListBits TC." 1426 ::= { ifMauEntry 13 } 1428 ifMauHCFalseCarriers OBJECT-TYPE 1429 SYNTAX Counter64 1430 MAX-ACCESS read-only 1431 STATUS current 1432 DESCRIPTION "A count of the number of false carrier events 1433 during IDLE in 100BASE-X and 1000BASE-X links. 1435 For all other MAU types, this counter will 1436 always indicate zero. This counter does not 1437 increment at the symbol rate. 1439 This counter is a 64 bit version of 1440 ifMauFalseCarriers. Since the 32 bit version of 1441 this counter can roll over very quickly, 1442 management stations are advised to poll the 1443 64 bit version instead in order to avoid loss 1444 of information. 1446 Discontinuities in the value of this counter can 1447 occur at re-initialization of the management 1448 system, and at other times as indicated by the 1449 value of ifCounterDiscontinuityTime." 1450 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.10, aFalseCarriers. 1451 RFC 2863, ifCounterDiscontinuityTime." 1452 ::= { ifMauEntry 14 } 1454 -- The ifJackTable applies to MAUs attached to interfaces 1455 -- which have one or more external jacks (connectors). 1457 ifJackTable OBJECT-TYPE 1458 SYNTAX SEQUENCE OF IfJackEntry 1459 MAX-ACCESS not-accessible 1460 STATUS current 1461 DESCRIPTION "Information about the external jacks attached 1462 to MAUs attached to an interface." 1463 ::= { dot3IfMauBasicGroup 2 } 1465 ifJackEntry OBJECT-TYPE 1466 SYNTAX IfJackEntry 1467 MAX-ACCESS not-accessible 1468 STATUS current 1469 DESCRIPTION "An entry in the table, containing information 1470 about a particular jack." 1471 INDEX { ifMauIfIndex, 1472 ifMauIndex, 1473 ifJackIndex 1474 } 1475 ::= { ifJackTable 1 } 1477 IfJackEntry ::= 1478 SEQUENCE { 1479 ifJackIndex Integer32, 1480 ifJackType IANAifJackType 1481 } 1483 ifJackIndex OBJECT-TYPE 1484 SYNTAX Integer32 (1..2147483647) 1485 MAX-ACCESS not-accessible 1486 STATUS current 1487 DESCRIPTION "This variable uniquely identifies the jack 1488 described by this entry from among other jacks 1489 attached to the same MAU." 1490 ::= { ifJackEntry 1 } 1492 ifJackType OBJECT-TYPE 1493 SYNTAX IANAifJackType 1494 MAX-ACCESS read-only 1495 STATUS current 1496 DESCRIPTION "The jack connector type, as it appears on the 1497 outside of the system." 1498 ::= { ifJackEntry 2 } 1500 -- 1501 -- The MAU Auto-Negotiation Table 1502 -- 1504 ifMauAutoNegTable OBJECT-TYPE 1505 SYNTAX SEQUENCE OF IfMauAutoNegEntry 1506 MAX-ACCESS not-accessible 1507 STATUS current 1508 DESCRIPTION "Configuration and status objects for the 1509 auto-negotiation function of MAUs attached to 1510 interfaces. 1512 The ifMauAutoNegTable applies to systems in 1513 which auto-negotiation is supported on one or 1514 more MAUs attached to interfaces. Note that if 1515 auto-negotiation is present and enabled, the 1516 ifMauType object reflects the result of the 1517 auto-negotiation function." 1518 ::= { dot3IfMauAutoNegGroup 1 } 1520 ifMauAutoNegEntry OBJECT-TYPE 1521 SYNTAX IfMauAutoNegEntry 1522 MAX-ACCESS not-accessible 1523 STATUS current 1524 DESCRIPTION "An entry in the table, containing configuration 1525 and status information for the auto-negotiation 1526 function of a particular MAU." 1527 INDEX { ifMauIfIndex, 1528 ifMauIndex 1529 } 1530 ::= { ifMauAutoNegTable 1 } 1532 IfMauAutoNegEntry ::= 1533 SEQUENCE { 1534 ifMauAutoNegAdminStatus INTEGER, 1535 ifMauAutoNegRemoteSignaling INTEGER, 1536 ifMauAutoNegConfig INTEGER, 1537 ifMauAutoNegCapability Integer32, 1538 ifMauAutoNegCapAdvertised Integer32, 1539 ifMauAutoNegCapReceived Integer32, 1540 ifMauAutoNegRestart INTEGER, 1541 ifMauAutoNegCapabilityBits BITS, 1542 ifMauAutoNegCapAdvertisedBits BITS, 1543 ifMauAutoNegCapReceivedBits BITS, 1544 ifMauAutoNegRemoteFaultAdvertised INTEGER, 1545 ifMauAutoNegRemoteFaultReceived INTEGER 1546 } 1548 ifMauAutoNegAdminStatus OBJECT-TYPE 1549 SYNTAX INTEGER { 1550 enabled(1), 1551 disabled(2) 1552 } 1553 MAX-ACCESS read-write 1554 STATUS current 1555 DESCRIPTION "Setting this object to enabled(1) will cause 1556 the interface which has the auto-negotiation 1557 signaling ability to be enabled. 1559 If the value of this object is disabled(2) then 1560 the interface will act as it would if it had no 1561 auto-negotiation signaling. Under these 1562 conditions, an IEEE 802.3 MAU will immediately 1563 be forced to the state indicated by the value of 1564 the object ifMauDefaultType. 1566 NOTE TO IMPLEMENTORS: When 1567 ifMauAutoNegAdminStatus transitions from enabled 1568 to disabled, the agent implementation MUST 1569 ensure that the operational type of the MAU (as 1570 reported by ifMauType) correctly transitions to 1571 the value specified by the ifMauDefaultType 1572 object, rather than continuing to operate at the 1573 value earlier determined by the auto-negotiation 1574 function." 1575 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.2, 1576 aAutoNegAdminState and 30.6.1.2.2, 1577 acAutoNegAdminControl." 1578 ::= { ifMauAutoNegEntry 1 } 1580 ifMauAutoNegRemoteSignaling OBJECT-TYPE 1581 SYNTAX INTEGER { 1582 detected(1), 1583 notdetected(2) 1584 } 1585 MAX-ACCESS read-only 1586 STATUS current 1587 DESCRIPTION "A value indicating whether the remote end of 1588 the link is using auto-negotiation signaling. It 1589 takes the value detected(1) if and only if, 1590 during the previous link negotiation, FLP Bursts 1591 were received." 1592 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.3, 1593 aAutoNegRemoteSignaling." 1594 ::= { ifMauAutoNegEntry 2 } 1596 ifMauAutoNegConfig OBJECT-TYPE 1597 SYNTAX INTEGER { 1598 other(1), 1599 configuring(2), 1600 complete(3), 1601 disabled(4), 1602 parallelDetectFail(5) 1603 } 1604 MAX-ACCESS read-only 1605 STATUS current 1606 DESCRIPTION "A value indicating the current status of the 1607 auto-negotiation process. The enumeration 1608 parallelDetectFail(5) maps to a failure in 1609 parallel detection as defined in 28.2.3.1 of 1610 [IEEE 802.3 Std]." 1611 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.4, 1612 aAutoNegAutoConfig." 1613 ::= { ifMauAutoNegEntry 4 } 1615 ifMauAutoNegCapability OBJECT-TYPE 1616 SYNTAX Integer32 1617 MAX-ACCESS read-only 1618 STATUS deprecated 1619 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1621 This object has been deprecated in favour of 1622 ifMauAutoNegCapabilityBits. 1624 A value that uniquely identifies the set of 1625 capabilities of the local auto-negotiation 1626 entity. The value is a sum which initially 1627 takes the value zero. Then, for each capability 1628 of this interface, 2 raised to the power noted 1629 below is added to the sum. For example, an 1630 interface which has the capability to support 1631 only 100Base-TX half duplex would have a value 1632 of 32768 (2**15). In contrast, an interface 1633 which supports both 100Base-TX half duplex and 1634 and 100Base-TX full duplex would have a value of 1635 98304 ((2**15) + (2**16)). 1637 The powers of 2 assigned to the capabilities are 1638 these: 1640 Power Capability 1641 0 other or unknown 1642 (1-9) (reserved) 1643 10 10BASE-T half duplex mode 1644 11 10BASE-T full duplex mode 1645 12 (reserved) 1646 13 (reserved) 1647 14 100BASE-T4 1648 15 100BASE-TX half duplex mode 1649 16 100BASE-TX full duplex mode 1650 17 (reserved) 1651 18 (reserved) 1652 19 100BASE-T2 half duplex mode 1653 20 100BASE-T2 full duplex mode 1655 Note that interfaces that support this MIB may 1656 have capabilities that extend beyond the scope 1657 of this MIB." 1658 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, 1659 aAutoNegLocalTechnologyAbility." 1660 ::= { ifMauAutoNegEntry 5 } 1662 ifMauAutoNegCapAdvertised OBJECT-TYPE 1663 SYNTAX Integer32 1664 MAX-ACCESS read-write 1665 STATUS deprecated 1666 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1668 This object has been deprecated in favour of 1669 ifMauAutoNegCapAdvertisedBits. 1671 A value that uniquely identifies the set of 1672 capabilities advertised by the local 1673 auto-negotiation entity. Refer to 1674 ifMauAutoNegCapability for a description of the 1675 possible values of this object. 1677 Capabilities in this object that are not 1678 available in ifMauAutoNegCapability cannot be 1679 enabled." 1680 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 1681 aAutoNegAdvertisedTechnologyAbility." 1682 ::= { ifMauAutoNegEntry 6 } 1684 ifMauAutoNegCapReceived OBJECT-TYPE 1685 SYNTAX Integer32 1686 MAX-ACCESS read-only 1687 STATUS deprecated 1688 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1690 This object has been deprecated in favour of 1691 ifMauAutoNegCapReceivedBits. 1693 A value that uniquely identifies the set of 1694 capabilities received from the remote 1695 auto-negotiation entity. Refer to 1696 ifMauAutoNegCapability for a description of the 1697 possible values of this object. 1699 Note that interfaces that support this MIB may 1700 be attached to remote auto-negotiation entities 1701 which have capabilities beyond the scope of this 1702 MIB." 1703 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 1704 aAutoNegReceivedTechnologyAbility." 1705 ::= { ifMauAutoNegEntry 7 } 1707 ifMauAutoNegRestart OBJECT-TYPE 1708 SYNTAX INTEGER { 1709 restart(1), 1710 norestart(2) 1711 } 1713 MAX-ACCESS read-write 1714 STATUS current 1715 DESCRIPTION "If the value of this object is set to 1716 restart(1) then this will force auto-negotiation 1717 to begin link renegotiation. If auto-negotiation 1718 signaling is disabled, a write to this object 1719 has no effect. 1720 Setting the value of this object to norestart(2) 1721 has no effect." 1722 REFERENCE "[IEEE 802.3 Std], 30.6.1.2.1, 1723 acAutoNegRestartAutoConfig." 1724 ::= { ifMauAutoNegEntry 8 } 1726 ifMauAutoNegCapabilityBits OBJECT-TYPE 1727 SYNTAX BITS { 1728 bOther(0), -- other or unknown 1729 b10baseT(1), -- 10BASE-T half duplex mode 1730 b10baseTFD(2), -- 10BASE-T full duplex mode 1731 b100baseT4(3), -- 100BASE-T4 1732 b100baseTX(4), -- 100BASE-TX half duplex mode 1733 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1734 b100baseT2(6), -- 100BASE-T2 half duplex mode 1735 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1736 bfdxPause(8), -- PAUSE for full-duplex links 1737 bfdxAPause(9), -- Asymmetric PAUSE for full-duplex 1738 -- links 1739 bfdxSPause(10), -- Symmetric PAUSE for full-duplex 1740 -- links 1741 bfdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1742 -- full-duplex links 1743 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1744 -- duplex mode 1745 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1746 -- duplex mode 1747 b1000baseT(14), -- 1000BASE-T half duplex mode 1748 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1749 } 1750 MAX-ACCESS read-only 1751 STATUS current 1752 DESCRIPTION "A value that uniquely identifies the set of 1753 capabilities of the local auto-negotiation 1754 entity. Note that interfaces that support this 1755 MIB may have capabilities that extend beyond the 1756 scope of this MIB. 1758 Note that the local auto-negotiation entity may 1759 support some capabilities beyond the scope of 1760 this MIB. This is indicated by returning the 1761 bit value bOther in addition to any bit values 1762 for capabilities that are listed above." 1763 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.5, 1764 aAutoNegLocalTechnologyAbility." 1765 ::= { ifMauAutoNegEntry 9 } 1767 ifMauAutoNegCapAdvertisedBits OBJECT-TYPE 1769 SYNTAX BITS { 1770 bOther(0), -- other or unknown 1771 b10baseT(1), -- 10BASE-T half duplex mode 1772 b10baseTFD(2), -- 10BASE-T full duplex mode 1773 b100baseT4(3), -- 100BASE-T4 1774 b100baseTX(4), -- 100BASE-TX half duplex mode 1775 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1776 b100baseT2(6), -- 100BASE-T2 half duplex mode 1777 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1778 bFdxPause(8), -- PAUSE for full-duplex links 1779 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 1780 -- links 1781 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 1782 -- links 1783 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1784 -- full-duplex links 1785 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1786 -- duplex mode 1787 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1788 -- duplex mode 1789 b1000baseT(14), -- 1000BASE-T half duplex mode 1790 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1791 } 1792 MAX-ACCESS read-write 1793 STATUS current 1794 DESCRIPTION "A value that uniquely identifies the set of 1795 capabilities advertised by the local 1796 auto-negotiation entity. 1798 Capabilities in this object that are not 1799 available in ifMauAutoNegCapabilityBits cannot 1800 be enabled. 1802 Note that the local auto-negotiation entity may 1803 advertise some capabilities beyond the scope of 1804 this MIB. This is indicated by returning the 1805 bit value bOther in addition to any bit values 1806 for capabilities that are listed above." 1807 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 1808 aAutoNegAdvertisedTechnologyAbility." 1810 ::= { ifMauAutoNegEntry 10 } 1812 ifMauAutoNegCapReceivedBits OBJECT-TYPE 1813 SYNTAX BITS { 1814 bOther(0), -- other or unknown 1815 b10baseT(1), -- 10BASE-T half duplex mode 1816 b10baseTFD(2), -- 10BASE-T full duplex mode 1817 b100baseT4(3), -- 100BASE-T4 1818 b100baseTX(4), -- 100BASE-TX half duplex mode 1819 b100baseTXFD(5), -- 100BASE-TX full duplex mode 1820 b100baseT2(6), -- 100BASE-T2 half duplex mode 1821 b100baseT2FD(7), -- 100BASE-T2 full duplex mode 1822 bFdxPause(8), -- PAUSE for full-duplex links 1823 bFdxAPause(9), -- Asymmetric PAUSE for full-duplex 1824 -- links 1825 bFdxSPause(10), -- Symmetric PAUSE for full-duplex 1826 -- links 1827 bFdxBPause(11), -- Asymmetric and Symmetric PAUSE for 1828 -- full-duplex links 1829 b1000baseX(12), -- 1000BASE-X, -LX, -SX, -CX half 1830 -- duplex mode 1831 b1000baseXFD(13), -- 1000BASE-X, -LX, -SX, -CX full 1832 -- duplex mode 1833 b1000baseT(14), -- 1000BASE-T half duplex mode 1834 b1000baseTFD(15) -- 1000BASE-T full duplex mode 1835 } 1836 MAX-ACCESS read-only 1837 STATUS current 1838 DESCRIPTION "A value that uniquely identifies the set of 1839 capabilities received from the remote 1840 auto-negotiation entity. 1841 Note that interfaces that support this MIB may 1842 be attached to remote auto-negotiation entities 1843 which have capabilities beyond the scope of this 1844 MIB. This is indicated by returning the bit 1845 value bOther in addition to any bit values for 1846 capabilities that are listed above." 1847 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 1848 aAutoNegReceivedTechnologyAbility." 1849 ::= { ifMauAutoNegEntry 11 } 1851 ifMauAutoNegRemoteFaultAdvertised OBJECT-TYPE 1852 SYNTAX INTEGER { 1853 noError(1), 1854 offline(2), 1855 linkFailure(3), 1856 autoNegError(4) 1857 } 1859 MAX-ACCESS read-write 1860 STATUS current 1861 DESCRIPTION "A value that identifies any local fault 1862 indications that this MAU has detected and will 1863 advertise at the next auto-negotiation 1864 interaction for 1000Mbps MAUs." 1865 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.6, 1866 aAutoNegAdvertisedTechnologyAbility." 1867 ::= { ifMauAutoNegEntry 12 } 1869 ifMauAutoNegRemoteFaultReceived OBJECT-TYPE 1870 SYNTAX INTEGER { 1871 noError(1), 1872 offline(2), 1873 linkFailure(3), 1874 autoNegError(4) 1875 } 1876 MAX-ACCESS read-only 1877 STATUS current 1878 DESCRIPTION "A value that identifies any fault indications 1879 received from the far end of a link by the 1880 local auto-negotiation entity for 1000Mbps 1881 MAUs." 1882 REFERENCE "[IEEE 802.3 Std], 30.6.1.1.7, 1883 aAutoNegReceivedTechnologyAbility." 1884 ::= { ifMauAutoNegEntry 13 } 1886 -- 1887 -- The Basic Broadband MAU Table 1888 -- 1890 broadMauBasicTable OBJECT-TYPE 1891 SYNTAX SEQUENCE OF BroadMauBasicEntry 1892 MAX-ACCESS not-accessible 1893 STATUS deprecated 1894 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1896 This entire table has been deprecated. There 1897 have been no reported implementations of this 1898 table, and it is unlikely that there ever will 1899 be. IEEE recommends that broadband MAU types 1900 should not be used for new installations. 1902 Table of descriptive and status information 1903 about the broadband MAUs connected to 1904 interfaces." 1905 ::= { dot3BroadMauBasicGroup 1 } 1907 broadMauBasicEntry OBJECT-TYPE 1908 SYNTAX BroadMauBasicEntry 1909 MAX-ACCESS not-accessible 1910 STATUS deprecated 1911 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1913 An entry in the table, containing information 1914 about a single broadband MAU." 1915 INDEX { broadMauIfIndex, 1916 broadMauIndex 1917 } 1918 ::= { broadMauBasicTable 1 } 1920 BroadMauBasicEntry ::= 1921 SEQUENCE { 1922 broadMauIfIndex InterfaceIndex, 1923 broadMauIndex Integer32, 1924 broadMauXmtRcvSplitType INTEGER, 1925 broadMauXmtCarrierFreq Integer32, 1926 broadMauTranslationFreq Integer32 1927 } 1929 broadMauIfIndex OBJECT-TYPE 1930 SYNTAX InterfaceIndex 1931 MAX-ACCESS read-only -- read-only since originally an 1932 -- SMIv1 index 1933 STATUS deprecated 1934 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1936 This variable uniquely identifies the interface 1937 to which the MAU described by this entry is 1938 connected." 1939 REFERENCE "Reference RFC 2863, ifIndex." 1940 ::= { broadMauBasicEntry 1 } 1942 broadMauIndex OBJECT-TYPE 1943 SYNTAX Integer32 (1..2147483647) 1944 MAX-ACCESS read-only -- read-only since originally an 1945 -- SMIv1 index 1946 STATUS deprecated 1947 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1949 This variable uniquely identifies the MAU 1950 connected to interface broadMauIfIndex that is 1951 described by this entry." 1952 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.1, aMAUID." 1953 ::= { broadMauBasicEntry 2 } 1955 broadMauXmtRcvSplitType OBJECT-TYPE 1956 SYNTAX INTEGER { 1957 other(1), 1958 single(2), 1959 dual(3) 1960 } 1961 MAX-ACCESS read-only 1962 STATUS deprecated 1963 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1965 This object indicates the type of frequency 1966 multiplexing/cabling system used to separate the 1967 transmit and receive paths for the 10BROAD36 1968 MAU. 1970 The value other(1) is returned if the split type 1971 is not either single or dual. 1973 The value single(2) indicates a single cable 1974 system. The value dual(3) indicates a dual 1975 cable system, offset normally zero." 1976 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.8, 1977 aBbMAUXmitRcvSplitType." 1978 ::= { broadMauBasicEntry 3 } 1980 broadMauXmtCarrierFreq OBJECT-TYPE 1981 SYNTAX Integer32 1982 MAX-ACCESS read-only 1983 STATUS deprecated 1984 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1986 This variable indicates the transmit carrier 1987 frequency of the 10BROAD36 MAU in MHz/4; that 1988 is, in units of 250 kHz." 1989 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, 1990 aBroadbandFrequencies.xmitCarrierFrequency." 1991 ::= { broadMauBasicEntry 4 } 1993 broadMauTranslationFreq OBJECT-TYPE 1994 SYNTAX Integer32 1995 MAX-ACCESS read-only 1996 STATUS deprecated 1997 DESCRIPTION "********* THIS OBJECT IS DEPRECATED ********** 1999 This variable indicates the translation offset 2000 frequency of the 10BROAD36 MAU in MHz/4; that 2001 is, in units of 250 kHz." 2002 REFERENCE "[IEEE 802.3 Std], 30.5.1.1.9, 2003 aBroadbandFrequencies.translationFrequency." 2004 ::= { broadMauBasicEntry 5 } 2006 -- Notifications for use by 802.3 MAUs 2008 snmpDot3MauTraps OBJECT IDENTIFIER ::= { snmpDot3MauMgt 0 } 2010 rpMauJabberTrap NOTIFICATION-TYPE 2011 OBJECTS { rpMauJabberState } 2012 STATUS current 2013 DESCRIPTION "This trap is sent whenever a managed repeater 2014 MAU enters the jabber state. 2016 The agent MUST throttle the generation of 2017 consecutive rpMauJabberTraps so that there is at 2018 least a five-second gap between them." 2019 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 2020 notification." 2021 ::= { snmpDot3MauTraps 1 } 2023 ifMauJabberTrap NOTIFICATION-TYPE 2024 OBJECTS { ifMauJabberState } 2025 STATUS current 2026 DESCRIPTION "This trap is sent whenever a managed interface 2027 MAU enters the jabber state. 2029 The agent MUST throttle the generation of 2030 consecutive ifMauJabberTraps so that there is at 2031 least a five-second gap between them." 2033 REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 2034 notification." 2035 ::= { snmpDot3MauTraps 2 } 2037 -- Conformance information 2039 mauModConf 2040 OBJECT IDENTIFIER ::= { mauMod 1 } 2041 mauModCompls 2042 OBJECT IDENTIFIER ::= { mauModConf 1 } 2043 mauModObjGrps 2044 OBJECT IDENTIFIER ::= { mauModConf 2 } 2045 mauModNotGrps 2046 OBJECT IDENTIFIER ::= { mauModConf 3 } 2048 -- Object groups 2050 mauRpGrpBasic OBJECT-GROUP 2051 OBJECTS { rpMauGroupIndex, 2052 rpMauPortIndex, 2053 rpMauIndex, 2054 rpMauType, 2055 rpMauStatus, 2056 rpMauMediaAvailable, 2057 rpMauMediaAvailableStateExits, 2058 rpMauJabberState, 2059 rpMauJabberingStateEnters 2060 } 2061 STATUS current 2062 DESCRIPTION "Basic conformance group for MAUs attached to 2063 repeater ports. This group is also the 2064 conformance specification for RFC 1515 2065 implementations." 2066 ::= { mauModObjGrps 1 } 2068 mauRpGrp100Mbs OBJECT-GROUP 2069 OBJECTS { rpMauFalseCarriers } 2070 STATUS current 2071 DESCRIPTION "Conformance group for MAUs attached to 2072 repeater ports with 100 Mb/s or greater 2073 capability." 2074 ::= { mauModObjGrps 2 } 2076 mauRpGrpJack OBJECT-GROUP 2077 OBJECTS { rpJackType } 2078 STATUS current 2079 DESCRIPTION "Conformance group for MAUs attached to 2080 repeater ports with managed jacks." 2081 ::= { mauModObjGrps 3 } 2083 mauIfGrpBasic OBJECT-GROUP 2084 OBJECTS { ifMauIfIndex, 2085 ifMauIndex, 2086 ifMauType, 2087 ifMauStatus, 2088 ifMauMediaAvailable, 2089 ifMauMediaAvailableStateExits, 2090 ifMauJabberState, 2091 ifMauJabberingStateEnters 2092 } 2093 STATUS current 2094 DESCRIPTION "Basic conformance group for MAUs attached to 2095 interfaces. This group also provides a 2096 conformance specification for RFC 1515 2097 implementations." 2098 ::= { mauModObjGrps 4 } 2100 mauIfGrp100Mbs OBJECT-GROUP 2101 OBJECTS { ifMauFalseCarriers, 2102 ifMauTypeList, 2103 ifMauDefaultType, 2104 ifMauAutoNegSupported 2105 } 2107 STATUS deprecated 2108 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2110 Conformance group for MAUs attached to 2111 interfaces with 100 Mb/s capability. 2113 This object group has been deprecated in favor 2114 of mauIfGrpHighCapacity." 2115 ::= { mauModObjGrps 5 } 2117 mauIfGrpJack OBJECT-GROUP 2118 OBJECTS { ifJackType } 2119 STATUS current 2120 DESCRIPTION "Conformance group for MAUs attached to 2121 interfaces with managed jacks." 2122 ::= { mauModObjGrps 6 } 2124 mauIfGrpAutoNeg OBJECT-GROUP 2125 OBJECTS { ifMauAutoNegAdminStatus, 2126 ifMauAutoNegRemoteSignaling, 2127 ifMauAutoNegConfig, 2128 ifMauAutoNegCapability, 2129 ifMauAutoNegCapAdvertised, 2130 ifMauAutoNegCapReceived, 2131 ifMauAutoNegRestart 2132 } 2133 STATUS deprecated 2134 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2136 Conformance group for MAUs attached to 2137 interfaces with managed auto-negotiation. 2139 This object group has been deprecated in favor 2140 of mauIfGrpAutoNeg2." 2141 ::= { mauModObjGrps 7 } 2143 mauBroadBasic OBJECT-GROUP 2144 OBJECTS { broadMauIfIndex, 2145 broadMauIndex, 2146 broadMauXmtRcvSplitType, 2147 broadMauXmtCarrierFreq, 2148 broadMauTranslationFreq 2149 } 2150 STATUS deprecated 2151 DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** 2153 Conformance group for broadband MAUs attached 2154 to interfaces. 2156 This object group is deprecated. There have 2157 been no reported implementations of this group, 2158 and it was felt to be unlikely that there will 2159 be any future implementations." 2160 ::= { mauModObjGrps 8 } 2162 mauIfGrpHighCapacity OBJECT-GROUP 2163 OBJECTS { ifMauFalseCarriers, 2164 ifMauTypeListBits, 2165 ifMauDefaultType, 2166 ifMauAutoNegSupported 2167 } 2168 STATUS current 2169 DESCRIPTION "Conformance group for MAUs attached to 2170 interfaces with 100 Mb/s or greater capability." 2171 ::= { mauModObjGrps 9 } 2173 mauIfGrpAutoNeg2 OBJECT-GROUP 2174 OBJECTS { ifMauAutoNegAdminStatus, 2175 ifMauAutoNegRemoteSignaling, 2176 ifMauAutoNegConfig, 2177 ifMauAutoNegCapabilityBits, 2178 ifMauAutoNegCapAdvertisedBits, 2179 ifMauAutoNegCapReceivedBits, 2180 ifMauAutoNegRestart 2181 } 2182 STATUS current 2183 DESCRIPTION "Conformance group for MAUs attached to 2184 interfaces with managed auto-negotiation." 2185 ::= { mauModObjGrps 10 } 2187 mauIfGrpAutoNeg1000Mbps OBJECT-GROUP 2188 OBJECTS { ifMauAutoNegRemoteFaultAdvertised, 2189 ifMauAutoNegRemoteFaultReceived 2190 } 2191 STATUS current 2192 DESCRIPTION "Conformance group for 1000Mbps MAUs attached to 2193 interfaces with managed auto-negotiation." 2194 ::= { mauModObjGrps 11 } 2196 mauIfGrpHCStats OBJECT-GROUP 2197 OBJECTS { ifMauHCFalseCarriers } 2198 STATUS current 2199 DESCRIPTION "Conformance for high capacity statistics for 2200 MAUs attached to interfaces" 2201 ::= { mauModObjGrps 12 } 2203 -- Notification groups 2205 rpMauNotifications NOTIFICATION-GROUP 2206 NOTIFICATIONS { rpMauJabberTrap } 2207 STATUS current 2208 DESCRIPTION "Notifications for repeater MAUs." 2209 ::= { mauModNotGrps 1 } 2211 ifMauNotifications NOTIFICATION-GROUP 2212 NOTIFICATIONS { ifMauJabberTrap } 2213 STATUS current 2214 DESCRIPTION "Notifications for interface MAUs." 2215 ::= { mauModNotGrps 2 } 2217 -- Compliances 2219 mauModRpCompl MODULE-COMPLIANCE 2220 STATUS deprecated 2221 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2222 Compliance for MAUs attached to repeater 2223 ports. 2225 This compliance is deprecated and replaced by 2226 mauModRpCompl2, which corrects an oversight by 2227 allowing rpMauStatus to be implemented 2228 read-only." 2230 MODULE -- this module 2231 MANDATORY-GROUPS { mauRpGrpBasic } 2233 GROUP mauRpGrp100Mbs 2234 DESCRIPTION "Implementation of this optional group is 2235 recommended for MAUs which have 100Mb/s or 2236 greater capability." 2238 GROUP mauRpGrpJack 2239 DESCRIPTION "Implementation of this optional group is 2240 recommended for MAUs which have one or more 2241 external jacks." 2243 GROUP rpMauNotifications 2244 DESCRIPTION "Implementation of this group is recommended 2245 for MAUs attached to repeater ports." 2246 ::= { mauModCompls 1 } 2248 mauModIfCompl MODULE-COMPLIANCE 2249 STATUS deprecated 2250 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2252 Compliance for MAUs attached to interfaces. 2253 This compliance is deprecated and replaced by 2254 mauModIfCompl2." 2256 MODULE -- this module 2257 MANDATORY-GROUPS { mauIfGrpBasic } 2259 GROUP mauIfGrp100Mbs 2260 DESCRIPTION "Implementation of this optional group is 2261 recommended for MAUs which have 100Mb/s 2262 capability." 2264 GROUP mauIfGrpJack 2265 DESCRIPTION "Implementation of this optional group is 2266 recommended for MAUs which have one or more 2267 external jacks." 2269 GROUP mauIfGrpAutoNeg 2270 DESCRIPTION "Implementation of this group is mandatory 2271 for MAUs which support managed 2272 auto-negotiation." 2274 GROUP mauBroadBasic 2275 DESCRIPTION "Implementation of this group is mandatory 2276 for broadband MAUs." 2278 GROUP ifMauNotifications 2279 DESCRIPTION "Implementation of this group is recommended 2280 for MAUs attached to interfaces." 2281 ::= { mauModCompls 2 } 2283 mauModIfCompl2 MODULE-COMPLIANCE 2284 STATUS deprecated 2285 DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** 2287 Compliance for MAUs attached to interfaces. 2289 This compliance is deprecated and replaced by 2290 mauModIfCompl3." 2292 MODULE -- this module 2293 MANDATORY-GROUPS { mauIfGrpBasic } 2295 GROUP mauIfGrpHighCapacity 2296 DESCRIPTION "Implementation of this optional group is 2297 recommended for MAUs which have 100Mb/s 2298 or greater capability." 2300 GROUP mauIfGrpJack 2302 DESCRIPTION "Implementation of this optional group is 2303 recommended for MAUs which have one or more 2304 external jacks." 2306 GROUP mauIfGrpAutoNeg2 2307 DESCRIPTION "Implementation of this group is mandatory 2308 for MAUs which support managed 2309 auto-negotiation." 2311 GROUP mauIfGrpAutoNeg1000Mbps 2312 DESCRIPTION "Implementation of this group is mandatory 2313 for MAUs which have 1000Mb/s or greater 2314 capability and support managed 2315 auto-negotiation." 2317 GROUP ifMauNotifications 2318 DESCRIPTION "Implementation of this group is recommended 2319 for MAUs attached to interfaces." 2321 OBJECT ifMauStatus 2322 MIN-ACCESS read-only 2323 DESCRIPTION "Write access is not required." 2324 ::= { mauModCompls 3 } 2326 mauModRpCompl2 MODULE-COMPLIANCE 2327 STATUS current 2328 DESCRIPTION "Compliance for MAUs attached to repeater 2329 ports. 2331 Note that compliance with this compliance 2332 statement requires compliance with the 2333 snmpRptrModCompl MODULE-COMPLIANCE statement of 2334 the SNMP-REPEATER-MIB (RFC 2108)." 2336 MODULE -- this module 2337 MANDATORY-GROUPS { mauRpGrpBasic } 2339 GROUP mauRpGrp100Mbs 2340 DESCRIPTION "Implementation of this optional group is 2341 recommended for MAUs which have 100Mb/s or 2342 greater capability." 2344 GROUP mauRpGrpJack 2345 DESCRIPTION "Implementation of this optional group is 2346 recommended for MAUs which have one or more 2347 external jacks." 2349 GROUP rpMauNotifications 2351 DESCRIPTION "Implementation of this group is recommended 2352 for MAUs attached to repeater ports." 2354 OBJECT rpMauStatus 2355 MIN-ACCESS read-only 2356 DESCRIPTION "Write access is not required." 2357 ::= { mauModCompls 4 } 2359 mauModIfCompl3 MODULE-COMPLIANCE 2360 STATUS current 2361 DESCRIPTION "Compliance for MAUs attached to interfaces. 2363 Note that compliance with this compliance 2364 statement requires compliance with the 2365 ifCompliance3 MODULE-COMPLIANCE statement of the 2366 IF-MIB (RFC 2863) and the dot3Compliance2 2367 MODULE-COMPLIANCE statement of the 2368 EtherLike-MIB (RFC3635)." 2370 MODULE -- this module 2371 MANDATORY-GROUPS { mauIfGrpBasic } 2373 GROUP mauIfGrpHighCapacity 2374 DESCRIPTION "Implementation of this optional group is 2375 recommended for MAUs which have 100Mb/s 2376 or greater capability." 2378 GROUP mauIfGrpHCStats 2379 DESCRIPTION "Implementation of this group is mandatory 2380 for MAUs which have 1000Mb/s capacity, and 2381 is recommended for MAUs which have 100Mb/s 2382 capacity." 2384 GROUP mauIfGrpJack 2385 DESCRIPTION "Implementation of this optional group is 2386 recommended for MAUs which have one or more 2387 external jacks." 2389 GROUP mauIfGrpAutoNeg2 2390 DESCRIPTION "Implementation of this group is mandatory 2391 for MAUs which support managed 2392 auto-negotiation." 2394 GROUP mauIfGrpAutoNeg1000Mbps 2395 DESCRIPTION "Implementation of this group is mandatory 2396 for MAUs which have 1000Mb/s or greater 2397 capability and support managed 2398 auto-negotiation." 2400 GROUP ifMauNotifications 2401 DESCRIPTION "Implementation of this group is recommended 2402 for MAUs attached to interfaces." 2404 OBJECT ifMauStatus 2405 MIN-ACCESS read-only 2406 DESCRIPTION "Write access is not required." 2407 ::= { mauModCompls 5 } 2409 END 2411 5. IANA-maintained MAU TC Definitions 2413 IANA-MAU-MIB DEFINITIONS ::= BEGIN 2415 IMPORTS 2416 MODULE-IDENTITY, OBJECT-IDENTITY, mib-2 2417 FROM SNMPv2-SMI 2418 TEXTUAL-CONVENTION 2419 FROM SNMPv2-TC 2420 ; 2422 ianaMauMIB MODULE-IDENTITY 2423 LAST-UPDATED "200510240000Z" -- Oct 24, 2005 2424 ORGANIZATION "IANA" 2425 CONTACT-INFO " Internet Assigned Numbers Authority 2427 Postal: ICANN 2428 4676 Admiralty Way, Suite 330 2429 Marina del Rey, CA 90292 2431 Tel: +1 310 823 9358 2432 E-Mail: iana@iana.org" 2434 DESCRIPTION 2435 "This MIB module defines dot3MauType OBJECT-IDENTITIES and 2436 IANAifMauListBits and IANAifJackType Textual Conventions, 2437 specifying enumerated values of the ifMauTypeListBits and 2438 ifJackType objects respectively, defined in the MAU-MIB. 2440 It is intended that each new MAU type and/or Jack type defined 2441 by the IEEE 802.3 working group and approved for publication 2442 in a revision of IEEE Std 802.3 will be added to this MIB 2443 module, provided that it is suitable for being managed by the 2444 base objects in the MAU-MIB. An Expert Review, as defined in 2445 RFC 2434 [RFC2434], is REQUIRED for such additions. 2447 The following reference is used throughout this MIB module: 2449 [IEEE 802.3 Std] refers to: 2450 IEEE Std 802.3, 2002 Edition: 'IEEE Standard for 2451 Information technology - Telecommunications and information 2452 exchange between systems - Local and metropolitan area 2453 networks - Specific requirements - 2454 Part 3: Carrier sense multiple access with collision 2455 detection (CSMA/CD) access method and physical layer 2456 specifications', as amended by the following specifications: 2457 IEEE Std 802.3ae-2002: 2458 'Amendment: Media Access Control (MAC) Parameters, 2459 Physical Layer, and Management Parameters for 10 Gb/s 2460 Operation', August 2002; 2461 IEEE Std 802.3ak-2004: 2462 'Amendment: Media Access Control (MAC) Parameters, 2463 Physical Layer, and Management Parameters for 10 Gb/s 2464 Operation, Type 10GBASE-CX4', March 2004; 2465 IEEE Std 802.3ah-2004: 2466 'Amendment: Media Access Control Parameters, Physical 2467 Layers and Management Parameters for Subscriber Access 2468 Networks', September 2004;. 2470 This reference should be updated as appropriate when new 2471 MAU types and/or Jack types are added to this MIB module. 2473 Copyright (C) The Internet Society (2005). 2474 The initial version of this MIB module was published in 2475 RFC XXXX; for full legal notices see the RFC itself. 2476 Supplementary information may be available at: 2477 http://www.ietf.org/copyrights/ianamib.html" 2479 REVISION "200510240000Z" -- Oct 24, 2005 2480 DESCRIPTION "Initial version of this MIB as published in 2481 RFC XXX." 2483 -- EdNote: Replace XXXX with the actual RFC number & remove this note 2484 ::= { mib-2 snmpDot3MauMgt(26) 7 } -- mauMod+1 2486 -- Textual Conventions 2488 IANAifMauTypeListBits ::= TEXTUAL-CONVENTION 2489 STATUS current 2490 DESCRIPTION 2491 "This data type is used as the syntax of the ifMauTypeListBits 2492 object in the (updated) definition of MAU-MIB's ifMauTable. 2494 The most recent version of this textual convention is 2495 available in the on-line version of this MIB module 2496 on the IANA web site. 2498 Requests for new values should be made to IANA via email 2499 (iana@iana.org). 2501 Note that changes in this textual convention SHALL be 2502 synchronized with relevant changes in the dot3MauType 2503 OBJECT-IDENTITIES." 2504 SYNTAX BITS { 2505 bOther(0), -- other or unknown 2506 bAUI(1), -- AUI 2507 b10base5(2), -- 10BASE-5 2508 bFoirl(3), -- FOIRL 2510 b10base2(4), -- 10BASE-2 2511 b10baseT(5), -- 10BASE-T duplex mode unknown 2512 b10baseFP(6), -- 10BASE-FP 2513 b10baseFB(7), -- 10BASE-FB 2514 b10baseFL(8), -- 10BASE-FL duplex mode unknown 2515 b10broad36(9), -- 10BROAD36 2516 b10baseTHD(10), -- 10BASE-T half duplex mode 2517 b10baseTFD(11), -- 10BASE-T full duplex mode 2518 b10baseFLHD(12), -- 10BASE-FL half duplex mode 2519 b10baseFLFD(13), -- 10BASE-FL full duplex mode 2520 b100baseT4(14), -- 100BASE-T4 2521 b100baseTXHD(15), -- 100BASE-TX half duplex mode 2522 b100baseTXFD(16), -- 100BASE-TX full duplex mode 2523 b100baseFXHD(17), -- 100BASE-FX half duplex mode 2524 b100baseFXFD(18), -- 100BASE-FX full duplex mode 2525 b100baseT2HD(19), -- 100BASE-T2 half duplex mode 2526 b100baseT2FD(20), -- 100BASE-T2 full duplex mode 2528 b1000baseXHD(21), -- 1000BASE-X half duplex mode 2529 b1000baseXFD(22), -- 1000BASE-X full duplex mode 2530 b1000baseLXHD(23), -- 1000BASE-LX half duplex mode 2531 b1000baseLXFD(24), -- 1000BASE-LX full duplex mode 2532 b1000baseSXHD(25), -- 1000BASE-SX half duplex mode 2533 b1000baseSXFD(26), -- 1000BASE-SX full duplex mode 2534 b1000baseCXHD(27), -- 1000BASE-CX half duplex mode 2535 b1000baseCXFD(28), -- 1000BASE-CX full duplex mode 2536 b1000baseTHD(29), -- 1000BASE-T half duplex mode 2537 b1000baseTFD(30), -- 1000BASE-T full duplex mode 2539 b10GbaseX(31), -- 10GBASE-X 2540 b10GbaseLX4(32), -- 10GBASE-LX4 2541 b10GbaseR(33), -- 10GBASE-R 2542 b10GbaseER(34), -- 10GBASE-ER 2543 b10GbaseLR(35), -- 10GBASE-LR 2544 b10GbaseSR(36), -- 10GBASE-SR 2545 b10GbaseW(37), -- 10GBASE-W 2546 b10GbaseEW(38), -- 10GBASE-EW 2547 b10GbaseLW(39), -- 10GBASE-LW 2548 b10GbaseSW(40), -- 10GBASE-SW 2549 -- new since RFC 3636 2550 b10GbaseCX4(41), -- 10GBASE-CX4 2551 b2BaseTL(42), -- 2BASE-TL 2552 b10PassTS(43), -- 10PASS-TS 2553 b100BaseBX10D(44), -- 100BASE-BX10D 2554 b100BaseBX10U(45), -- 100BASE-BX10U 2555 b100BaseLX10(46), -- 100BASE-LX10 2556 b1000BaseBX10D(47), -- 1000BASE-BX10D 2557 b1000BaseBX10U(48), -- 1000BASE-BX10U 2558 b1000BaseLX10(49), -- 1000BASE-LX10 2559 b1000BasePX10D(50), -- 1000BASE-PX10D 2560 b1000BasePX10U(51), -- 1000BASE-PX10U 2561 b1000BasePX20D(52), -- 1000BASE-PX20D 2562 b1000BasePX20U(53) -- 1000BASE-PX20U 2563 } 2565 IANAifJackType ::= TEXTUAL-CONVENTION 2566 STATUS current 2567 DESCRIPTION 2568 "Common enumeration values for repeater and interface MAU 2569 jack types. This data type is used as the syntax of the 2570 ifJackType and rpJackType objects in the (updated) definition 2571 of MAU-MIB's ifJackTable and RpJackTable respectively. 2573 The most recent version of this textual convention is 2574 available in the on-line version of this MIB module 2575 on the IANA web site. 2577 Requests for new values should be made to IANA via email 2578 (iana@iana.org)." 2580 SYNTAX INTEGER { 2581 other(1), 2582 rj45(2), 2583 rj45S(3), -- rj45 shielded 2584 db9(4), 2585 bnc(5), 2586 fAUI(6), -- female aui 2587 mAUI(7), -- male aui 2588 fiberSC(8), 2589 fiberMIC(9), 2590 fiberST(10), 2591 telco(11), 2592 mtrj(12), -- fiber MT-RJ 2593 hssdc(13), -- fiber channel style-2 2594 fiberLC(14), 2595 -- new since RFC 3636 2596 cx4(15) -- IB4X for 10GBASE-CX4 2597 } 2599 -- OBJECT IDENTITIES for MAU types 2600 -- (see rpMauType and ifMauType of MAU-MIB for usage) 2601 -- The following definitions has been moved from RFC 3636 and 2602 -- no longer appear in its revision. 2604 dot3MauType OBJECT IDENTIFIER ::= { mib-2 snmpDot3MauMgt(26) 4 } 2606 dot3MauTypeAUI OBJECT-IDENTITY 2607 STATUS current 2608 DESCRIPTION "no internal MAU, view from AUI" 2609 REFERENCE "[IEEE 802.3 Std.], Section 7" 2610 ::= { dot3MauType 1 } 2612 dot3MauType10Base5 OBJECT-IDENTITY 2613 STATUS current 2614 DESCRIPTION "thick coax MAU" 2615 REFERENCE "[IEEE 802.3 Std.], Section 7" 2616 ::= { dot3MauType 2 } 2618 dot3MauTypeFoirl OBJECT-IDENTITY 2619 STATUS current 2620 DESCRIPTION "FOIRL MAU" 2621 REFERENCE "[IEEE 802.3 Std.], Section 9.9" 2622 ::= { dot3MauType 3 } 2624 dot3MauType10Base2 OBJECT-IDENTITY 2625 STATUS current 2626 DESCRIPTION "thin coax MAU" 2627 REFERENCE "[IEEE 802.3 Std.], Section 10" 2628 ::= { dot3MauType 4 } 2630 dot3MauType10BaseT OBJECT-IDENTITY 2631 STATUS current 2632 DESCRIPTION "UTP MAU. 2633 Note that it is strongly recommended that 2634 agents return either dot3MauType10BaseTHD or 2635 dot3MauType10BaseTFD if the duplex mode is 2636 known. However, management applications should 2637 be prepared to receive this MAU type value from 2638 older agent implementations." 2639 REFERENCE "[IEEE 802.3 Std.], Section 14" 2640 ::= { dot3MauType 5 } 2642 dot3MauType10BaseFP OBJECT-IDENTITY 2643 STATUS current 2644 DESCRIPTION "passive fiber MAU" 2645 REFERENCE "[IEEE 802.3 Std.], Section 16" 2646 ::= { dot3MauType 6 } 2648 dot3MauType10BaseFB OBJECT-IDENTITY 2649 STATUS current 2650 DESCRIPTION "sync fiber MAU" 2651 REFERENCE "[IEEE 802.3 Std.], Section 17" 2652 ::= { dot3MauType 7 } 2654 dot3MauType10BaseFL OBJECT-IDENTITY 2655 STATUS current 2656 DESCRIPTION "async fiber MAU. 2657 Note that it is strongly recommended that 2658 agents return either dot3MauType10BaseFLHD or 2659 dot3MauType10BaseFLFD if the duplex mode is 2660 known. However, management applications should 2661 be prepared to receive this MAU type value from 2662 older agent implementations." 2663 REFERENCE "[IEEE 802.3 Std.], Section 18" 2664 ::= { dot3MauType 8 } 2666 dot3MauType10Broad36 OBJECT-IDENTITY 2667 STATUS current 2668 DESCRIPTION "broadband DTE MAU. 2669 Note that 10BROAD36 MAUs can be attached to 2670 interfaces but not to repeaters." 2671 REFERENCE "[IEEE 802.3 Std.], Section 11" 2672 ::= { dot3MauType 9 } 2674 ------ new since RFC 1515: 2675 dot3MauType10BaseTHD OBJECT-IDENTITY 2676 STATUS current 2677 DESCRIPTION "UTP MAU, half duplex mode" 2678 REFERENCE "[IEEE 802.3 Std.], Section 14" 2679 ::= { dot3MauType 10 } 2681 dot3MauType10BaseTFD OBJECT-IDENTITY 2682 STATUS current 2683 DESCRIPTION "UTP MAU, full duplex mode" 2684 REFERENCE "[IEEE 802.3 Std.], Section 14" 2685 ::= { dot3MauType 11 } 2687 dot3MauType10BaseFLHD OBJECT-IDENTITY 2688 STATUS current 2689 DESCRIPTION "async fiber MAU, half duplex mode" 2690 REFERENCE "[IEEE 802.3 Std.], Section 18" 2691 ::= { dot3MauType 12 } 2693 dot3MauType10BaseFLFD OBJECT-IDENTITY 2694 STATUS current 2695 DESCRIPTION "async fiber MAU, full duplex mode" 2696 REFERENCE "[IEEE 802.3 Std.], Section 18" 2697 ::= { dot3MauType 13 } 2699 dot3MauType100BaseT4 OBJECT-IDENTITY 2700 STATUS current 2701 DESCRIPTION "4 pair category 3 UTP" 2702 REFERENCE "[IEEE 802.3 Std.], Section 23" 2703 ::= { dot3MauType 14 } 2705 dot3MauType100BaseTXHD OBJECT-IDENTITY 2706 STATUS current 2707 DESCRIPTION "2 pair category 5 UTP, half duplex mode" 2708 REFERENCE "[IEEE 802.3 Std.], Section 25" 2709 ::= { dot3MauType 15 } 2711 dot3MauType100BaseTXFD OBJECT-IDENTITY 2712 STATUS current 2713 DESCRIPTION "2 pair category 5 UTP, full duplex mode" 2714 REFERENCE "[IEEE 802.3 Std.], Section 25" 2715 ::= { dot3MauType 16 } 2717 dot3MauType100BaseFXHD OBJECT-IDENTITY 2718 STATUS current 2719 DESCRIPTION "X fiber over PMT, half duplex mode" 2720 REFERENCE "[IEEE 802.3 Std.], Section 26" 2721 ::= { dot3MauType 17 } 2723 dot3MauType100BaseFXFD OBJECT-IDENTITY 2724 STATUS current 2725 DESCRIPTION "X fiber over PMT, full duplex mode" 2726 REFERENCE "[IEEE 802.3 Std.], Section 26" 2727 ::= { dot3MauType 18 } 2729 dot3MauType100BaseT2HD OBJECT-IDENTITY 2730 STATUS current 2731 DESCRIPTION "2 pair category 3 UTP, half duplex mode" 2732 REFERENCE "[IEEE 802.3 Std.], Section 32" 2733 ::= { dot3MauType 19 } 2735 dot3MauType100BaseT2FD OBJECT-IDENTITY 2736 STATUS current 2737 DESCRIPTION "2 pair category 3 UTP, full duplex mode" 2738 REFERENCE "[IEEE 802.3 Std.], Section 32" 2739 ::= { dot3MauType 20 } 2741 ------ new since RFC 2239: 2742 dot3MauType1000BaseXHD OBJECT-IDENTITY 2743 STATUS current 2744 DESCRIPTION "PCS/PMA, unknown PMD, half duplex mode" 2745 REFERENCE "[IEEE 802.3 Std.], Section 36" 2746 ::= { dot3MauType 21 } 2748 dot3MauType1000BaseXFD OBJECT-IDENTITY 2749 STATUS current 2750 DESCRIPTION "PCS/PMA, unknown PMD, full duplex mode" 2751 REFERENCE "[IEEE 802.3 Std.], Section 36" 2752 ::= { dot3MauType 22 } 2754 dot3MauType1000BaseLXHD OBJECT-IDENTITY 2755 STATUS current 2756 DESCRIPTION "Fiber over long-wavelength laser, half duplex 2757 mode" 2758 REFERENCE "[IEEE 802.3 Std.], Section 38" 2759 ::= { dot3MauType 23 } 2761 dot3MauType1000BaseLXFD OBJECT-IDENTITY 2762 STATUS current 2763 DESCRIPTION "Fiber over long-wavelength laser, full duplex 2764 mode" 2765 REFERENCE "[IEEE 802.3 Std.], Section 38" 2766 ::= { dot3MauType 24 } 2768 dot3MauType1000BaseSXHD OBJECT-IDENTITY 2769 STATUS current 2770 DESCRIPTION "Fiber over short-wavelength laser, half 2771 duplex mode" 2773 REFERENCE "[IEEE 802.3 Std.], Section 38" 2774 ::= { dot3MauType 25 } 2776 dot3MauType1000BaseSXFD OBJECT-IDENTITY 2777 STATUS current 2778 DESCRIPTION "Fiber over short-wavelength laser, full 2779 duplex mode" 2780 REFERENCE "[IEEE 802.3 Std.], Section 38" 2781 ::= { dot3MauType 26 } 2783 dot3MauType1000BaseCXHD OBJECT-IDENTITY 2784 STATUS current 2785 DESCRIPTION "Copper over 150-Ohm balanced cable, half 2786 duplex mode" 2787 REFERENCE "[IEEE 802.3 Std.], Section 39" 2788 ::= { dot3MauType 27 } 2790 dot3MauType1000BaseCXFD OBJECT-IDENTITY 2791 STATUS current 2792 DESCRIPTION "Copper over 150-Ohm balanced cable, full 2793 duplex mode" 2794 REFERENCE "[IEEE 802.3 Std.], Section 39" 2795 ::= { dot3MauType 28 } 2797 dot3MauType1000BaseTHD OBJECT-IDENTITY 2798 STATUS current 2799 DESCRIPTION "Four-pair Category 5 UTP, half duplex mode" 2800 REFERENCE "[IEEE 802.3 Std.], Section 40" 2801 ::= { dot3MauType 29 } 2803 dot3MauType1000BaseTFD OBJECT-IDENTITY 2804 STATUS current 2805 DESCRIPTION "Four-pair Category 5 UTP, full duplex mode" 2806 REFERENCE "[IEEE 802.3 Std.], Section 40" 2807 ::= { dot3MauType 30 } 2809 ------ new since RFC 2668: 2810 dot3MauType10GigBaseX OBJECT-IDENTITY 2811 STATUS current 2812 DESCRIPTION "X PCS/PMA, unknown PMD." 2813 REFERENCE "[IEEE 802.3 Std.], Section 48" 2814 ::= { dot3MauType 31 } 2816 dot3MauType10GigBaseLX4 OBJECT-IDENTITY 2817 STATUS current 2818 DESCRIPTION "X fiber over WWDM optics" 2819 REFERENCE "[IEEE 802.3 Std.], Section 53" 2820 ::= { dot3MauType 32 } 2822 dot3MauType10GigBaseR OBJECT-IDENTITY 2823 STATUS current 2824 DESCRIPTION "R PCS/PMA, unknown PMD." 2825 REFERENCE "[IEEE 802.3 Std.], Section 49" 2826 ::= { dot3MauType 33 } 2828 dot3MauType10GigBaseER OBJECT-IDENTITY 2829 STATUS current 2830 DESCRIPTION "R fiber over 1550 nm optics" 2831 REFERENCE "[IEEE 802.3 Std.], Section 52" 2832 ::= { dot3MauType 34 } 2834 dot3MauType10GigBaseLR OBJECT-IDENTITY 2835 STATUS current 2836 DESCRIPTION "R fiber over 1310 nm optics" 2837 REFERENCE "[IEEE 802.3 Std.], Section 52" 2838 ::= { dot3MauType 35 } 2840 dot3MauType10GigBaseSR OBJECT-IDENTITY 2841 STATUS current 2842 DESCRIPTION "R fiber over 850 nm optics" 2843 REFERENCE "[IEEE 802.3 Std.], Section 52" 2844 ::= { dot3MauType 36 } 2846 dot3MauType10GigBaseW OBJECT-IDENTITY 2847 STATUS current 2848 DESCRIPTION "W PCS/PMA, unknown PMD." 2849 REFERENCE "[IEEE 802.3 Std.], Section 49 and 50" 2850 ::= { dot3MauType 37 } 2852 dot3MauType10GigBaseEW OBJECT-IDENTITY 2853 STATUS current 2854 DESCRIPTION "W fiber over 1550 nm optics" 2855 REFERENCE "[IEEE 802.3 Std.], Section 52" 2856 ::= { dot3MauType 38 } 2858 dot3MauType10GigBaseLW OBJECT-IDENTITY 2859 STATUS current 2860 DESCRIPTION "W fiber over 1310 nm optics" 2861 REFERENCE "[IEEE 802.3 Std.], Section 52" 2862 ::= { dot3MauType 39 } 2864 dot3MauType10GigBaseSW OBJECT-IDENTITY 2865 STATUS current 2866 DESCRIPTION "W fiber over 850 nm optics" 2867 REFERENCE "[IEEE 802.3 Std.], Section 52" 2868 ::= { dot3MauType 40 } 2870 ------ new since RFC 3636: 2871 dot3MauType10GigBaseCX4 OBJECT-IDENTITY 2872 STATUS current 2873 DESCRIPTION "X copper over 8 pair 100-Ohm balanced cable" 2874 REFERENCE "[IEEE 802.3 Std.], Section 54" 2875 ::= { dot3MauType 41 } 2877 dot3MauType2BaseTL OBJECT-IDENTITY 2878 STATUS current 2879 DESCRIPTION "Voice grade UTP copper, up to 2700m " 2880 REFERENCE "[IEEE 802.3 Std.], Sections 61 and 63" 2881 ::= { dot3MauType 42 } 2883 dot3MauType10PassTS OBJECT-IDENTITY 2884 STATUS current 2885 DESCRIPTION "Voice grade UTP copper, up to 750m" 2886 REFERENCE "[IEEE 802.3 Std.], Sections 61 and 62" 2887 ::= { dot3MauType 43 } 2889 dot3MauType100BaseBX10D OBJECT-IDENTITY 2890 STATUS current 2891 DESCRIPTION "One single-mode fiber OLT" 2892 REFERENCE "[IEEE 802.3 Std.], Section 58" 2893 ::= { dot3MauType 44 } 2895 dot3MauType100BaseBX10U OBJECT-IDENTITY 2896 STATUS current 2897 DESCRIPTION "One single-mode fiber ONU" 2898 REFERENCE "[IEEE 802.3 Std.], Section 58" 2899 ::= { dot3MauType 45 } 2901 dot3MauType100BaseLX10 OBJECT-IDENTITY 2902 STATUS current 2903 DESCRIPTION "Two fiber" 2904 REFERENCE "[IEEE 802.3 Std.], Section 58" 2905 ::= { dot3MauType 46 } 2907 dot3MauType1000BaseBX10D OBJECT-IDENTITY 2908 STATUS current 2909 DESCRIPTION "One single-mode fiber OLT" 2910 REFERENCE "[IEEE 802.3 Std.], Section 59" 2911 ::= { dot3MauType 47 } 2913 dot3MauType1000BaseBX10U OBJECT-IDENTITY 2914 STATUS current 2915 DESCRIPTION "One single-mode fiber ONU" 2916 REFERENCE "[IEEE 802.3 Std.], Section 59" 2917 ::= { dot3MauType 48 } 2919 dot3MauType1000BaseLX10 OBJECT-IDENTITY 2920 STATUS current 2921 DESCRIPTION "Two fiber 10km" 2922 REFERENCE "[IEEE 802.3 Std.], Section 59" 2923 ::= { dot3MauType 49 } 2925 dot3MauType1000BasePX10D OBJECT-IDENTITY 2926 STATUS current 2927 DESCRIPTION "One single-mode fiber OMP OLT 10km" 2928 REFERENCE "[IEEE 802.3 Std.], Section 60" 2929 ::= { dot3MauType 50 } 2931 dot3MauType1000BasePX10U OBJECT-IDENTITY 2932 STATUS current 2933 DESCRIPTION "One single-mode fiber OMP ONU 10km" 2934 REFERENCE "[IEEE 802.3 Std.], Section 60" 2935 ::= { dot3MauType 51 } 2937 dot3MauType1000BasePX20D OBJECT-IDENTITY 2938 STATUS current 2939 DESCRIPTION "One single-mode fiber OMP OLT 20km" 2940 REFERENCE "[IEEE 802.3 Std.], Section 60" 2941 ::= { dot3MauType 52 } 2943 dot3MauType1000BasePX20U OBJECT-IDENTITY 2944 STATUS current 2945 DESCRIPTION "One single-mode fiber OMP ONU 20km" 2946 REFERENCE "[IEEE 802.3 Std.], Section 60" 2947 ::= { dot3MauType 53 } 2949 END 2951 6. Security Considerations 2953 There are a number of management objects defined in this MIB that 2954 have a MAX-ACCESS clause of read-write. Setting these objects can 2955 have a serious effect on the operation of the network, including: 2957 o enabling or disabling a MAU 2959 o changing a MAU's default type 2961 o enabling, disabling or restarting autonegotiation 2962 o modifying the capabilities that a MAU advertizes during 2963 autonegotiation. 2965 Such objects may be considered sensitive or vulnerable in some 2966 network environments. The support for SET operations in a non-secure 2967 environment without proper protection can have a negative effect on 2968 network operations. 2970 Some of the readable objects in this MIB module (i.e., objects with a 2971 MAX-ACCESS other than not-accessible) may be considered sensitive or 2972 vulnerable in some network environments. In some environments it may 2973 be undesirable to allow unauthorized parties to access statistics or 2974 status information about individual links in a network. It is thus 2975 important to control even GET and/or NOTIFY access to these objects 2976 and possibly to even encrypt the values of these objects when sending 2977 them over the network via SNMP. 2979 SNMP versions prior to SNMPv3 did not include adequate security. 2980 Even if the network itself is secure (for example by using IPSec), 2981 even then, there is no control as to who on the secure network is 2982 allowed to access and GET/SET (read/change/create/delete) the objects 2983 in this MIB module. 2985 It is recommended that the implementors consider the security 2986 features as provided by the SNMPv3 framework (see [RFC3410], section 2987 8), including full support for the SNMPv3 cryptographic mechanisms 2988 (for authentication and privacy). 2990 Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT 2991 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2992 enable cryptographic security. It is then a customer/operator 2993 responsibility to ensure that the SNMP entity giving access to an 2994 instance of this MIB module is properly configured to give access to 2995 the objects only to those principals (users) that have legitimate 2996 rights to indeed GET or SET (change/create/delete) them. 2998 7. IANA Considerations 3000 This document defines first version of the IANA-maintained MIB 3001 module. It is intended that each new MAU type and/or Jack type 3002 defined by the IEEE 802.3 working group and approved for publication 3003 in a revision of IEEE Std 802.3 will be added to the IANA-maintaned 3004 module. An Expert Review, as defined in RFC 2434 [RFC2434], is 3005 REQUIRED. 3007 8. Acknowledgments 3009 This document was produced by the IETF Ethernet Interfaces and Hub 3010 MIB Working Group, whose efforts were greatly advanced by the 3011 contributions of the following people: 3013 Mike Heard 3015 John Flick 3017 Dan Romascanu 3019 This document is based on the Proposed Standard MAU MIB, RFC 3636 3020 [RFC3636], edited by John Flick of Hewlett-Packard, and produced by 3021 the Ethernet Interfaces and Hub MIB Working Group. It extends that 3022 document by moving the object identities and textual conventions for 3023 MAU types into a IANA-maintained MIB module. In addition, support is 3024 provided for the EFM and 10GBASE-CX4 MAUs as defined in [IEEE802.3ah] 3025 and [IEEE802.3ak] respectively. 3027 RFC 3636, in turn, was based on the Proposed Standard MAU MIB, RFC 3028 2668 [RFC2668], edited by John Flick of Hewlett-Packard and Andrew 3029 Smith, then of Extreme Networks, and produced by the Ethernet 3030 Interfaces and Hub MIB Working Group. It extends that document by 3031 providing support for 10 Gb/s MAUs as defined in [IEEE802.3ae]. 3033 RFC 2668, in turn, was based on the Proposed Standard MAU MIB, RFC 3034 2239 [RFC2239], edited by Kathryn de Graaf, then of 3Com, and Dan 3035 Romascanu, then of Madge Networks, and produced by the Ethernet 3036 Interfaces and Hub MIB Working Group. It extended that document by 3037 providing support for 1000 Mb/sec MAUs as defined in [IEEE802.3]. 3039 RFC 2239, in turn, was based on the Proposed Standard MAU MIB, RFC 3040 1515 [RFC1515], edited by Donna McMaster, then of SynOptics 3041 Communications, Keith McCloghrie, then of Hughes LAN Systems, and Sam 3042 Roberts, then of Farallon Computing, and produced by the Hub MIB 3043 Working Group. It extends that document by providing support for 100 3044 Mb/sec MAUs, full duplex MAUs, and auto-negotiation, as defined in 3045 [IEEE802.3]. 3047 9. References 3049 9.1. Normative References 3051 [IEEE802.3] 3052 IEEE, "IEEE Standard for Information technology - 3053 Telecommunications and information exchange between 3054 systems - Local and metropolitan area networks - Specific 3055 requirements - Part 3: Carrier sense multiple access with 3056 collision detection (CSMA/CD) access method and physical 3057 layer specifications", IEEE Std 802.3-2002, March 2002. 3059 [IEEE802.3ae] 3060 IEEE, "IEEE Standard for Information technology - 3061 Telecommunications and information exchange between 3062 systems - Local and metropolitan area networks - Specific 3063 requirements - Part 3: Carrier sense multiple access with 3064 collision detection (CSMA/CD) access method and physical 3065 layer specifications - Media Access Control (MAC) 3066 Parameters, Physical Layer and Management Parameters for 3067 10 Gb/s Operation", IEEE Std 802.3ae-2002, August 2002. 3069 [IEEE802.3ah] 3070 IEEE, "Information technology - Telecommunications and 3071 information exchange between systems - Local and 3072 metropolitan area networks - Specific requirements - Part 3073 3: Carrier sense multiple access with collision detection 3074 (CSMA/CD) access method and physical layer specifications 3075 - Media Access Control Parameters, Physical Layers and 3076 Management Parameters for Subscriber Access Networks", 3077 IEEE Std 802.3ah-2004, September 2004. 3079 [IEEE802.3ak] 3080 IEEE, "IEEE Standard for Information technology - 3081 Telecommunications and information exchange between 3082 systems - Local and metropolitan area networks - Specific 3083 requirements - Part 3: Carrier sense multiple access with 3084 collision detection (CSMA/CD) access method and physical 3085 layer specifications - Physical Layer and Management 3086 Parameters for 10Gb/s Operation, Type 10GBASE-CX4", IEEE 3087 Std 802.3ak-2004, March 2004. 3089 [RFC2108] de Graaf, K., Romascanu, D., McMaster, D., and K. 3090 McCloghrie, "Definitions of Managed Objects for IEEE 802.3 3091 Repeater Devices using SMIv2", RFC 2108, February 1997. 3093 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3094 Requirement Levels", BCP 14, RFC 2119, March 1997. 3096 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an 3097 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 3098 October 1998. 3100 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3101 McCloghrie, K., Rose, M., and S. Waldbusser, "Structure of 3102 Management Information Version 2 (SMIv2)", STD 58, 3103 RFC 2578, April 1999. 3105 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3106 McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 3107 Conventions for SMIv2", STD 58, RFC 2579, April 1999. 3109 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 3110 "Conformance Statements for SMIv2", STD 58, RFC 2580, 3111 April 1999. 3113 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 3114 MIB", RFC 2863, June 2000. 3116 [RFC3635] Flick, J., "Definitions of Managed Objects for the 3117 Ethernet-like Interface Types", RFC 3635, September 2003. 3119 9.2. Informative References 3121 [RFC1515] McMaster, D., McCloghrie, K., and S. Roberts, "Definitions 3122 of Managed Objects for IEEE 802.3 Medium Attachment Units 3123 (MAUs)", RFC 1515, September 1993. 3125 [RFC2239] de Graaf, K., Romascanu, D., McMaster, D., McCloghrie, K., 3126 and S. Roberts, "Definitions of Managed Objects for IEEE 3127 802.3 Medium Attachment Units (MAUs) using SMIv2", 3128 RFC 2239, November 1997. 3130 [RFC2668] Smith, A., Flick, J., de Graaf, K., Romascanu, D., 3131 McMaster, D., McCloghrie, K., and S. Roberts, "Definitions 3132 of Managed Objects for IEEE 802.3 Medium Attachment Units 3133 (MAUs)", RFC 2668, August 1999. 3135 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 3136 "Introduction and Applicability Statements for Internet- 3137 Standard Management Framework", RFC 3410, December 2002. 3139 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 3140 Simple Network Management Protocol (SNMP)", STD 62, 3141 RFC 3418, December 2002. 3143 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 3144 Medium Attachment Units (MAUs)", RFC 3636, September 2003. 3146 [RFC3637] Heard, C., "Definitions of Managed Objects for the 3147 Ethernet WAN Interface Sublayer", RFC 3637, 3148 September 2003. 3150 Author's Address 3152 Edward Beili 3153 Actelis Networks 3154 Bazel 25 3155 Petach-Tikva 3156 Israel 3158 Phone: +972-3-924-3491 3159 Email: edward.beili@actelis.com 3161 Intellectual Property Statement 3163 The IETF takes no position regarding the validity or scope of any 3164 Intellectual Property Rights or other rights that might be claimed to 3165 pertain to the implementation or use of the technology described in 3166 this document or the extent to which any license under such rights 3167 might or might not be available; nor does it represent that it has 3168 made any independent effort to identify any such rights. Information 3169 on the procedures with respect to rights in RFC documents can be 3170 found in BCP 78 and BCP 79. 3172 Copies of IPR disclosures made to the IETF Secretariat and any 3173 assurances of licenses to be made available, or the result of an 3174 attempt made to obtain a general license or permission for the use of 3175 such proprietary rights by implementers or users of this 3176 specification can be obtained from the IETF on-line IPR repository at 3177 http://www.ietf.org/ipr. 3179 The IETF invites any interested party to bring to its attention any 3180 copyrights, patents or patent applications, or other proprietary 3181 rights that may cover technology that may be required to implement 3182 this standard. Please address the information to the IETF at 3183 ietf-ipr@ietf.org. 3185 Disclaimer of Validity 3187 This document and the information contained herein are provided on an 3188 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 3189 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 3190 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 3191 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 3192 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 3193 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 3195 Copyright Statement 3197 Copyright (C) The Internet Society (2005). This document is subject 3198 to the rights, licenses and restrictions contained in BCP 78, and 3199 except as set forth therein, the authors retain all their rights. 3201 Acknowledgment 3203 Funding for the RFC Editor function is currently provided by the 3204 Internet Society.