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