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