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