idnits 2.17.1 draft-ietf-hubmib-mau-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-20) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 2) being 105 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 46 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Overview' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 6. Security Considerations' ) ** 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.) ** The document seems to lack an Authors' Addresses Section. ** There are 15 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** There are 45 instances of lines with control characters in the document. ** The abstract seems to contain references ([2], [3], [4], [5], [6], [7], [8], [9], [10], [11], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- -- 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 (23 August 1996) is 10102 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 section? '6' on line 1840 looks like a reference -- Missing reference section? '5' on line 1835 looks like a reference -- Missing reference section? '10' on line 1860 looks like a reference -- Missing reference section? '9' on line 1855 looks like a reference -- Missing reference section? '7' on line 1845 looks like a reference -- Missing reference section? '8' on line 1850 looks like a reference -- Missing reference section? '11' on line 1867 looks like a reference -- Missing reference section? '1' on line 1819 looks like a reference -- Missing reference section? '2' on line 1824 looks like a reference -- Missing reference section? '4' on line 1832 looks like a reference -- Missing reference section? '3' on line 1829 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 3 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Definitions of Managed Objects 2 for IEEE 802.3 Medium Attachment Units (MAUs) 4 23 August 1996 6 8 Donna McMaster 9 Livingston Enterprises 11 Keith McCloghrie 12 Cisco Systems Inc. 14 Sam Roberts 15 Farallon Computing, Inc. 17 Dan Romascanu 18 Madge Networks (Israel) Ltd. 20 Kathryn de Graaf 21 3Com Corporation 23 , 24 Status of this Memo 26 This document is an Internet-Draft. Internet-Drafts are 27 working documents of the Internet Engineering Task Force 28 (IETF), its areas, and its working groups. Note that other 29 groups may also distribute working documents as Internet- 30 Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six 33 months and may be updated, replaced, or obsoleted by other 34 documents at any time. It is not appropriate to use Internet- 35 Drafts as reference material or to cite them other than as a 36 "work in progress". 38 To learn the current status of any Internet-Draft, please 39 check the "1id-abstracts.txt" listing contained in the 40 Internet-Drafts Shadow Directories on ds.internic.net (US East 41 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 42 or munnari.oz.au (Pacific Rim). 44 Abstract 46 This memo defines an experimental portion of the Management 47 Information Base (MIB) for use with network management 48 protocols in the Internet community. In particular, it 49 defines objects for managing 10 and 100 Mb/second Medium 50 Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, 51 "10 & 100 Mb/s Management," October 26, 1995. 53 This memo does not specify a standard for the Internet 54 community. 56 1. The SNMPv2 Network Management Framework 58 The SNMPv2 Network Management Framework presently consists of 59 three major components. They are: 61 o the SMI, described in RFC 1902 [6] - the mechanisms used 62 for describing and naming objects for the purpose of 63 management. 65 , 67 o the MIB-II, STD 17, RFC 1213 [5] - the core set of 68 managed objects for the Internet suite of protocols. 70 o the protocol, RFC 1157 [10] and/or RFC 1905 [9] - the 71 protocol used for accessing managed information. 73 Textual conventions are defined in RFC 1903 [7], and 74 conformance statements are defined in RFC 1904 [8]. 76 The Framework permits new objects to be defined for the 77 purpose of experimentation and evaluation. 79 1.1. Object Definitions 81 Managed objects are accessed via a virtual information store, 82 termed the Management Information Base or MIB. Objects in the 83 MIB are defined using the subset of Abstract Syntax Notation 84 One (ASN.1) defined in the SMI. In particular, each object 85 type is named by an OBJECT IDENTIFIER, an administratively 86 assigned name. The object type together with an object 87 instance serves to uniquely identify a specific instantiation 88 of the object. For human convenience, we often use a textual 89 string, termed the descriptor, to refer to the object type. 91 , 92 2. Overview 94 2.1. Relationship to RFC 1515 96 This MIB is intended to be a superset of that defined by RFC 97 1515 [11], which will go to historic status. This MIB 98 includes all of the objects contained in that MIB, plus 99 several new ones which provide additional capabilities. 100 Implementors are encouraged to support all applicable 101 conformance groups in order to make the best use of the new 102 functionality provided by this MIB. The new objects provide 103 management support for: 105 o management of 100 Mb/s devices 107 o auto-negotiation 109 o jack management 111 2.2. MAU Management 113 Instances of these object types represent attributes of an 114 IEEE 802.3 MAU. Several types of MAUs are defined in the IEEE 115 802.3 CSMA/CD standard [1] and [2]. These MAUs may be 116 connected to IEEE 802.3 repeaters or to 802.3 (Ethernet-like) 117 interfaces. For convenience this document refers to these 118 devices as "repeater MAUs" and "interface MAUs." 120 The definitions presented here are based on Section 30.5, 121 "Layer Management for 10 & 100 Mb/s Medium Attachment Units 122 (MAUs)", and Annex 30A, "GDMO Specifications for 802.3 managed 123 objects" of IEEE Std 802.3u-1995. That specification includes 124 definitions for both 10Mb/s and 100Mb/s devices, and is 125 essentially a superset of the 10Mb/s definitions given by IEEE 126 802.3 Section 20. This specification is intended to serve the 127 same purpose: to provide for management of both 10Mb/s and 128 100Mb/s MAUs. 130 2.3. Relationship to Other MIBs 132 It is assumed that an agent implementing this MIB will also 133 implement (at least) the 'system' group defined in MIB-II [5]. 134 The following sections identify other MIBs that such an agent 136 , 137 should implement. 139 2.3.1. Relationship to the MIB-II 'interfaces' group 141 The sections of this document that define interface MAU- 142 related objects specify an extension to the 'interfaces' group 143 of MIB-II. An agent implementing these interface-MAU related 144 objects must also implement the 'interfaces' group of MIB-II. 145 The value of the object ifMauIfIndex is the same as the value 146 of 'ifIndex' used to instantiate the interface to which the 147 given MAU is connected. 149 It is expected that an agent implementing the interface-MAU 150 related objects in this MIB will also implement the Ethernet- 151 like Interfaces MIB, RFC 1650. 153 (Note that repeater ports are not represented as interfaces in 154 the sense of MIB-II's 'interfaces' group.) 156 2.3.2. Relationship to the 802.3 Repeater MIB 158 The section of this document that defines repeater MAU-related 159 objects specifies an extension to the 802.3 Repeater MIB 160 defined in [4]. An agent implementing these repeater-MAU 161 related objects must also implement the 802.3 Repeater MIB. 163 The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to 164 instantiate a repeater MAU variable shall be the same as the 165 values of 'rptrPortGroupIndex' and 'rptrPortIndex' used to 166 instantiate the port to which the given MAU is connected. 168 2.4. Management of Internal MAUs 170 In some situations, a MAU can be "internal" -- i.e., its 171 functionality is implemented entirely within a device. For 172 example, a managed repeater may contain an internal repeater- 173 MAU and/or an internal interface-MAU through which management 174 communications originating on one of the repeater's external 175 ports pass in order to reach the management agent associated 176 with the repeater. Such internal MAUs may or may not be 177 managed. If they are managed, objects describing their 178 attributes should appear in the appropriate MIB subtree: 180 , 181 dot3RpMauBasicGroup for internal repeater-MAUs and 182 dot3IfMauBasicGroup for internal interface-MAUs. 184 , 185 3. Definitions 187 MAU-MIB DEFINITIONS ::= BEGIN 189 IMPORTS 190 Counter32, Integer32, 191 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 192 FROM SNMPv2-SMI 193 TruthValue 194 FROM SNMPv2-TC 195 OBJECT-GROUP, MODULE-COMPLIANCE 196 FROM SNMPv2-CONF; 198 mauMod MODULE-IDENTITY 199 LAST-UPDATED "9608230000Z" 200 ORGANIZATION "IETF HUB MIB Working Group" 201 CONTACT-INFO 202 "WG E-mail: hubmib@hprnd.rose.hp.com 204 Chair: Dan Romascanu 205 Postal: Madge Networks (Israel) Ltd. 206 Atidim Technology Park, Bldg. 3 207 Tel Aviv 61131, Israel 208 Tel: 972-3-6458414, 6458458 209 Fax: 972-3-6487146 210 E-mail: dromasca@madge.com 212 Editor: Kathryn de Graaf 213 Postal: 3Com Corporation 214 118 Turnpike Rd. 215 Southborough, MA 01772 216 USA 217 Tel: (508)229-1627 218 Fax: (508)490-5882 219 E-mail: kdegraaf@isd.3com.com" 220 DESCRIPTION 221 "Management information for 802.3 MAUs. 223 The following references are used throughout this 224 MIB module: 226 [IEEE 802.3 Std] 227 refers to IEEE 802.3/ISO 8802-3 Information 228 processing systems - Local area networks - 230 , 231 Part 3: Carrier sense multiple access with 232 collision detection (CSMA/CD) access method 233 and physical layer specifications (1993), 234 and to IEEE Std 802.3u-1995, Supplement to 235 IEEE Std 802.3, clauses 22 through 29. 237 [IEEE 802.3 Mgt] 238 refers to IEEE 802.3u-1995, - 10 Mb/s & 239 100 Mb/s Management, Section 30 - 240 Supplement to IEEE Std 802.3." 241 ::= { snmpDot3MauMgt 6 } 243 snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } 245 dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } 246 dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } 247 dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } 249 dot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } 251 -- object identifiers for MAU types 252 -- (see rpMauType and ifMauType for usage) 254 dot3MauType 255 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } 256 dot3MauTypeAUI -- no internal MAU, view from AUI 257 OBJECT IDENTIFIER ::= { dot3MauType 1 } 258 dot3MauType10Base5 -- thick coax MAU (per 802.3 section 8) 259 OBJECT IDENTIFIER ::= { dot3MauType 2 } 260 dot3MauTypeFoirl -- FOIRL MAU (per 802.3 section 9.9) 261 OBJECT IDENTIFIER ::= { dot3MauType 3 } 262 dot3MauType10Base2 -- thin coax MAU (per 802.3 section 10) 263 OBJECT IDENTIFIER ::= { dot3MauType 4 } 264 dot3MauType10BaseT -- UTP MAU (per 802.3 section 14) 265 OBJECT IDENTIFIER ::= { dot3MauType 5 } 266 dot3MauType10BaseFP -- passive fiber MAU (per 802.3 section 16) 267 OBJECT IDENTIFIER ::= { dot3MauType 6 } 268 dot3MauType10BaseFB -- sync fiber MAU (per 802.3 section 17) 269 OBJECT IDENTIFIER ::= { dot3MauType 7 } 270 dot3MauType10BaseFL -- async fiber MAU (per 802.3 section 18) 271 OBJECT IDENTIFIER ::= { dot3MauType 8 } 273 , 275 dot3MauType10Broad36 -- broadband DTE MAU (per 802.3 section 11) 276 -- note that 10BROAD36 MAUs can be attached to interfaces but 277 -- not to repeaters 278 OBJECT IDENTIFIER ::= { dot3MauType 9 } 280 ------ new since RFC 1515: 282 dot3MauType10BaseTHD -- UTP MAU (per 802.3 section 14) 283 -- half duplex mode 284 OBJECT IDENTIFIER ::= { dot3MauType 10 } 286 dot3MauType10BaseTFD -- UTP MAU (per 802.3 section 14) 287 -- full duplex mode 288 OBJECT IDENTIFIER ::= { dot3MauType 11 } 290 dot3MauType10BaseFLHD -- async fiber MAU (per 802.3 section 18) 291 -- half duplex mode 292 OBJECT IDENTIFIER ::= { dot3MauType 12 } 294 dot3MauType10BaseFLFD -- async fiber MAU (per 802.3 section 18) 295 -- full duplex mode 296 OBJECT IDENTIFIER ::= { dot3MauType 13 } 298 dot3MauType100BaseT4 -- 4 pair categ. 3 UTP (per 802.3 section 23) 299 OBJECT IDENTIFIER ::= { dot3MauType 14 } 301 dot3MauType100BaseTXHD -- 2 pair categ. 5 UTP (per 802.3 section 25), 302 -- half duplex mode 303 OBJECT IDENTIFIER ::= { dot3MauType 15 } 305 dot3MauType100BaseTXFD -- 2 pair categ. 5 UTP (per 802.3 section 25), 306 -- full duplex mode 307 OBJECT IDENTIFIER ::= { dot3MauType 16 } 309 dot3MauType100BaseFXHD -- X fiber over PMT (per 802.3 section 26) 310 -- half duplex mode 311 OBJECT IDENTIFIER ::= { dot3MauType 17 } 313 dot3MauType100BaseFXFD -- X fiber over PMT (per 802.3 section 26) 314 -- full duplex mode 315 OBJECT IDENTIFIER ::= { dot3MauType 18 } 317 dot3MauType100BaseT2 318 OBJECT IDENTIFIER ::= { dot3MauType 19 } 320 , 322 -- 323 -- The Basic Repeater MAU Table 324 -- 326 rpMauTable OBJECT-TYPE 327 SYNTAX SEQUENCE OF RpMauEntry 328 MAX-ACCESS not-accessible 329 STATUS current 330 DESCRIPTION 331 "Table of descriptive and status information about 332 the MAU(s) attached to the ports of a repeater." 333 ::= { dot3RpMauBasicGroup 1 } 335 rpMauEntry OBJECT-TYPE 336 SYNTAX RpMauEntry 337 MAX-ACCESS not-accessible 338 STATUS current 339 DESCRIPTION 340 "An entry in the table, containing information 341 about a single MAU." 342 INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex } 343 ::= { rpMauTable 1 } 345 RpMauEntry ::= 346 SEQUENCE { 347 rpMauGroupIndex 348 Integer32, 349 rpMauPortIndex 350 Integer32, 351 rpMauIndex 352 Integer32, 353 rpMauType 354 OBJECT IDENTIFIER, 355 rpMauStatus 356 INTEGER, 357 rpMauMediaAvail 358 INTEGER, 359 rpMauMediaAvailStateExits 360 Counter32, 361 rpMauJabberState 362 INTEGER, 363 rpMauJabberingStateEnters 364 Counter32, 365 rpMauFalseCarriers 366 Counter32 368 , 370 } 372 rpMauGroupIndex OBJECT-TYPE 373 SYNTAX Integer32 (1..2147483647) 374 MAX-ACCESS read-only 375 STATUS current 376 DESCRIPTION 377 "This variable uniquely identifies the group 378 containing the port to which the MAU described by 379 this entry is connected. 381 Note: In practice, a group will generally be a 382 field-replaceable unit (i.e., module, card, or 383 board) that can fit in the physical system 384 enclosure, and the group number will correspond to 385 a number marked on the physical enclosure. 387 The group denoted by a particular value of this 388 object is the same as the group denoted by the 389 same value of rptrGroupIndex." 390 ::= { rpMauEntry 1 } 392 rpMauPortIndex OBJECT-TYPE 393 SYNTAX Integer32 (1..2147483647) 394 MAX-ACCESS read-only 395 STATUS current 396 DESCRIPTION 397 "This variable uniquely identifies the repeater 398 port within group rpMauGroupIndex to which the MAU 399 described by this entry is connected." 400 REFERENCE 401 "Reference RFC 1516, rptrPortIndex." 402 ::= { rpMauEntry 2 } 404 rpMauIndex OBJECT-TYPE 405 SYNTAX Integer32 (1..2147483647) 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION 409 "This variable uniquely identifies the MAU 410 described by this entry from among other MAUs 411 connected to the same port (rpMauPortIndex)." 412 REFERENCE 413 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 414 ::= { rpMauEntry 3 } 416 , 418 rpMauType OBJECT-TYPE 419 SYNTAX OBJECT IDENTIFIER 420 MAX-ACCESS read-only 421 STATUS current 422 DESCRIPTION 423 "This object identifies the 10 or 100 Mb/s 424 baseband MAU type. An initial set of MAU types 425 are defined above. The assignment of OBJECT 426 IDENTIFIERs to new types of MAUs is managed by the 427 IANA. If the MAU type is unknown, the object 428 identifier 430 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 432 is returned. Note that unknownMauType is a 433 syntactically valid object identifier, and any 434 conformant implementation of ASN.1 and the BER 435 must be able to generate and recognize this 436 value." 437 REFERENCE 438 "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." 439 ::= { rpMauEntry 4 } 441 rpMauStatus OBJECT-TYPE 442 SYNTAX INTEGER { 443 other(1), 444 unknown(2), 445 operational(3), 446 standby(4), 447 shutdown(5), 448 reset(6) 449 } 450 MAX-ACCESS read-write 451 STATUS current 452 DESCRIPTION 453 "The current state of the MAU. This object may be 454 implemented as a read-only object by those agents 455 and MAUs that do not implement software control of 456 the MAU state. Some agents may not support 457 setting the value of this object to some of the 458 enumerated values. 460 The value other(1) is returned if the MAU is in a 461 state other than one of the states 2 through 6. 463 , 464 The value unknown(2) is returned when the MAU's 465 true state is unknown; for example, when it is 466 being initialized. 468 A MAU in the operational(3) state is fully 469 functional, operates, and passes signals to its 470 attached DTE or repeater port in accordance to its 471 specification. 473 A MAU in standby(4) state forces DI and CI to idle 474 and the media transmitter to idle or fault, if 475 supported. Standby(4) mode only applies to link 476 type MAUs. The state of rpMauMediaAvail is 477 unaffected. 479 A MAU in shutdown(5) state assumes the same 480 condition on DI, CI, and the media transmitter as 481 though it were powered down or not connected. The 482 MAU may return other(1) value for the 483 rpMauJabberState and rpMauMediaAvail objects when 484 it is in this state. For an AUI, this state will 485 remove power from the AUI. 487 Setting this variable to the value reset(6) resets 488 the MAU in the same manner as a power-off, power- 489 on cycle of at least one-half second would. The 490 agent is not required to return the value reset 491 (6). 493 Setting this variable to the value operational(3), 494 standby(4), or shutdown(5) causes the MAU to 495 assume the respective state except that setting a 496 mixing-type MAU or an AUI to standby(4) will cause 497 the MAU to enter the shutdown state." 498 REFERENCE 499 "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 500 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 501 acRESETMAU." 502 ::= { rpMauEntry 5 } 504 rpMauMediaAvail OBJECT-TYPE 505 SYNTAX INTEGER { 506 other(1), 507 unknown(2), 508 available(3), 510 , 511 notAvailable(4), 512 remoteFault(5), 513 invalidSignal(6), 514 remoteJabber(7), 515 remoteLinkLoss(8), 516 remoteTest(9) 517 } 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "If the MAU is a link or fiber type (FOIRL, 522 10BASE-T, 10BASE-F) then this is equivalent to the 523 link test fail state/low light function. For an 524 AUI or a coax (including broadband) MAU this 525 indicates whether or not loopback is detected on 526 the DI circuit. The value of this attribute 527 persists between packets for MAU types AUI, 528 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 530 The value other(1) is returned if the mediaAvail 531 state is not one of 2 through 6. 533 The value unknown(2) is returned when the MAU's 534 true state is unknown; for example, when it is 535 being initialized. At power-up or following a 536 reset, the value of this attribute will be unknown 537 for AUI, coax, and 10BASE-FP MAUs. For these MAUs 538 loopback will be tested on each transmission 539 during which no collision is detected. If DI is 540 receiving input when DO returns to IDL after a 541 transmission and there has been no collision 542 during the transmission then loopback will be 543 detected. The value of this attribute will only 544 change during non-collided transmissions for AUI, 545 coax, and 10BASE-FP MAUs. 547 For 100BASE-T4, 100BASE-TX and 100BASE-FX the 548 enumerations match the states within the 549 respective link integrity state diagrams, fig 23- 550 12 and 24-15 of sections 23 and 24 of [2]. Any 551 MAU which implements management of auto- 552 negotiation will map remote fault indication to 553 remote fault. 555 The value available(3) indicates that the link, 557 , 558 light, or loopback is normal. The value 559 notAvailable(4) indicates link loss, low light, or 560 no loopback. 562 The value remoteFault(5) indicates that a fault 563 has been detected at the remote end of the link. 564 This value applies to 10BASE-FB, 100BASE-T4 Far 565 End Fault Indication and non-specified remote 566 faults from a system running auto-negotiation. 567 The values remoteJabber(7), remoteLinkLoss(8), and 568 remoteTest(9) should be used instead of 569 remoteFault(5) where the reason for remote fault 570 is identified in the remote signaling protocol. 572 The value invalidSignal(6) indicates that an 573 invalid signal has been received from the other 574 end of the link. InvalidSignal(6) applies only to 575 MAUs of type 10BASE-FB. 577 Where an IEEE Std 802.3u-1995 clause 22 MII is 578 present, a logic one in the remote fault bit 579 (reference section 22.2.4.2.8 of that document) 580 maps to the value remoteFault(5), and a logic zero 581 in the link status bit (reference section 582 22.2.4.2.10 of that document) maps to the value 583 notAvailable(4). The value notAvailable(4) takes 584 precedence over the value remoteFault(5)." 585 REFERENCE 586 "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." 587 ::= { rpMauEntry 6 } 589 rpMauMediaAvailStateExits OBJECT-TYPE 590 SYNTAX Counter32 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "A count of the number of times that 595 rpMauMediaAvail for this MAU instance leaves the 596 state available(3)." 597 REFERENCE 598 "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." 599 ::= { rpMauEntry 7 } 601 rpMauJabberState OBJECT-TYPE 602 SYNTAX INTEGER { 604 , 605 other(1), 606 unknown(2), 607 noJabber(3), 608 jabbering(4) 609 } 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The value other(1) is returned if the jabber 614 state is not 2, 3, or 4. The agent must always 615 return other(1) for MAU type dot3MauTypeAUI. 617 The value unknown(2) is returned when the MAU's 618 true state is unknown; for example, when it is 619 being initialized. 621 If the MAU is not jabbering the agent returns 622 noJabber(3). This is the 'normal' state. 624 If the MAU is in jabber state the agent returns 625 the jabbering(4) value." 626 REFERENCE 627 "[IEEE 802.3 Mgt], 30.5.1.1.6, 628 aJabber.jabberFlag." 629 ::= { rpMauEntry 8 } 631 rpMauJabberingStateEnters OBJECT-TYPE 632 SYNTAX Counter32 633 MAX-ACCESS read-only 634 STATUS current 635 DESCRIPTION 636 "A count of the number of times that 637 mauJabberState for this MAU instance enters the 638 state jabbering(4). For MAUs of type 639 dot3MauTypeAUI, dot3MauType100BaseT4, 640 dot3MauType100BaseTX, and dot3MauType100BaseFX, 641 this counter will always indicate zero." 642 REFERENCE 643 "[IEEE 802.3 Mgt], 30.5.1.1.6, 644 aJabber.jabberCounter." 645 ::= { rpMauEntry 9 } 647 rpMauFalseCarriers OBJECT-TYPE 648 SYNTAX Counter32 649 MAX-ACCESS read-only 651 , 652 STATUS current 653 DESCRIPTION 654 "A count of the number of false carrier events 655 during IDLE in 100BASE-X links. This counter does 656 not increment at the symbol rate. It can 657 increment after a valid carrier completion at a 658 maximum rate of once per 100 ms until the next 659 carrier event. 661 This counter increments only for MAUs of type 662 dot3MauType100BaseT4, dot3MauType100BaseTX, and 663 dot3MauType100BaseFX. For all other MAU types, 664 this counter will always indicate zero. 666 The approximate minimum time for rollover of this 667 counter is 7.4 hours." 668 REFERENCE 669 "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." 670 ::= { rpMauEntry 10 } 672 -- The rpJackTable applies to MAUs attached to repeaters 673 -- which have one or more external jacks (connectors). 675 rpJackTable OBJECT-TYPE 676 SYNTAX SEQUENCE OF RpJackEntry 677 MAX-ACCESS not-accessible 678 STATUS current 679 DESCRIPTION 680 "Information about the external jacks attached to 681 MAUs attached to the ports of a repeater." 682 ::= { dot3RpMauBasicGroup 2 } 684 rpJackEntry OBJECT-TYPE 685 SYNTAX RpJackEntry 686 MAX-ACCESS not-accessible 687 STATUS current 688 DESCRIPTION 689 "An entry in the table, containing information 690 about a particular jack." 691 INDEX { rpMauGroupIndex, 692 rpMauPortIndex, 693 rpMauIndex, 694 rpJackIndex } 695 ::= { rpJackTable 1 } 697 , 699 RpJackEntry ::= 700 SEQUENCE { 701 rpJackIndex 702 Integer32, 703 rpJackType 704 INTEGER 705 } 707 rpJackIndex OBJECT-TYPE 708 SYNTAX Integer32 (1..2147483647) 709 MAX-ACCESS not-accessible 710 STATUS current 711 DESCRIPTION 712 "This variable uniquely identifies the jack 713 described by this entry from among other jacks 714 attached to the same MAU (rpMauIndex)." 715 ::= { rpJackEntry 1 } 717 rpJackType OBJECT-TYPE 718 SYNTAX INTEGER { 719 other(1), 720 rj45(2), 721 rj45S(3), -- rj45 shielded 722 db9(4), 723 bnc(5), 724 fAUI(6), -- female aui 725 mAUI(7), -- male aui 726 fiberSC(8), 727 fiberMIC(9), 728 fiberST(10), 729 telco(11) 730 } 731 MAX-ACCESS read-only 732 STATUS current 733 DESCRIPTION 734 "The jack connector type, as it appears on the 735 outside of the system." 736 ::= { rpJackEntry 2 } 738 -- 739 -- The Basic Interface MAU Table 740 -- 742 ifMauTable OBJECT-TYPE 744 , 745 SYNTAX SEQUENCE OF IfMauEntry 746 MAX-ACCESS not-accessible 747 STATUS current 748 DESCRIPTION 749 "Table of descriptive and status information about 750 MAU(s) attached to an interface." 751 ::= { dot3IfMauBasicGroup 1 } 753 ifMauEntry OBJECT-TYPE 754 SYNTAX IfMauEntry 755 MAX-ACCESS not-accessible 756 STATUS current 757 DESCRIPTION 758 "An entry in the table, containing information 759 about a single MAU." 760 INDEX { ifMauIfIndex, ifMauIndex } 761 ::= { ifMauTable 1 } 763 IfMauEntry ::= 764 SEQUENCE { 765 ifMauIfIndex 766 Integer32, 767 ifMauIndex 768 Integer32, 769 ifMauType 770 OBJECT IDENTIFIER, 771 ifMauStatus 772 INTEGER, 773 ifMauMediaAvail 774 INTEGER, 775 ifMauMediaAvailStateExits 776 Counter32, 777 ifMauJabberState 778 INTEGER, 779 ifMauJabberingStateEnters 780 Counter32, 781 ifMauFalseCarriers 782 Counter32, 783 ifMauTypeList 784 Integer32, 785 ifMauDefaultType 786 OBJECT IDENTIFIER, 787 ifMauAutoNegSupported 788 TruthValue 789 } 791 , 793 ifMauIfIndex OBJECT-TYPE 794 SYNTAX Integer32 795 MAX-ACCESS read-only 796 STATUS current 797 DESCRIPTION 798 "This variable uniquely identifies the interface 799 to which the MAU described by this entry is 800 connected." 801 REFERENCE 802 "RFC 1213, ifIndex" 803 ::= { ifMauEntry 1 } 805 ifMauIndex OBJECT-TYPE 806 SYNTAX Integer32 (1..2147483647) 807 MAX-ACCESS read-only 808 STATUS current 809 DESCRIPTION 810 "This variable uniquely identifies the MAU 811 described by this entry from among other MAUs 812 connected to the same interface (ifMauIfIndex)." 813 REFERENCE 814 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 815 ::= { ifMauEntry 2 } 817 ifMauType OBJECT-TYPE 818 SYNTAX OBJECT IDENTIFIER 819 MAX-ACCESS read-only 820 STATUS current 821 DESCRIPTION 822 "This object identifies the 10 or 100 Mb/s 823 baseband MAU type. An initial set of MAU types 824 are defined above. The assignment of OBJECT 825 IDENTIFIERs to new types of MAUs is managed by the 826 IANA. If the MAU type is unknown, the object 827 identifier 829 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 831 is returned. Note that unknownMauType is a 832 syntactically valid object identifier, and any 833 conformant implementation of ASN.1 and the BER 834 must be able to generate and recognize this value. 836 This object represents the operational type of the 837 MAU, as determined by either (1) the result of the 839 , 840 auto-negotiation function or (2) if auto- 841 negotiation is not enabled or is not implemented 842 for this MAU, by the value of the object 843 ifMauDefaultType. In case (2), a set to the 844 object ifMauDefaultType will force the MAU into 845 the new operating mode." 846 REFERENCE 847 "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." 848 ::= { ifMauEntry 3 } 850 ifMauStatus OBJECT-TYPE 851 SYNTAX INTEGER { 852 other(1), 853 unknown(2), 854 operational(3), 855 standby(4), 856 shutdown(5), 857 reset(6) 858 } 859 MAX-ACCESS read-write 860 STATUS current 861 DESCRIPTION 862 "The current state of the MAU. This object may be 863 implemented as a read-only object by those agents 864 and MAUs that do not implement software control of 865 the MAU state. Some agents may not support 866 setting the value of this object to some of the 867 enumerated values. 869 The value other(1) is returned if the MAU is in a 870 state other than one of the states 2 through 6. 872 The value unknown(2) is returned when the MAU's 873 true state is unknown; for example, when it is 874 being initialized. 876 A MAU in the operational(3) state is fully 877 functional, operates, and passes signals to its 878 attached DTE or repeater port in accordance to its 879 specification. 881 A MAU in standby(4) state forces DI and CI to idle 882 and the media transmitter to idle or fault, if 883 supported. Standby(4) mode only applies to link 884 type MAUs. The state of ifMauMediaAvail is 886 , 887 unaffected. 889 A MAU in shutdown(5) state assumes the same 890 condition on DI, CI, and the media transmitter as 891 though it were powered down or not connected. The 892 MAU may return other(1) value for the 893 ifMauJabberState and ifMauMediaAvail objects when 894 it is in this state. For an AUI, this state will 895 remove power from the AUI. 897 Setting this variable to the value reset(6) resets 898 the MAU in the same manner as a power-off, power- 899 on cycle of at least one-half second would. The 900 agent is not required to return the value reset 901 (6). 903 Setting this variable to the value operational(3), 904 standby(4), or shutdown(5) causes the MAU to 905 assume the respective state except that setting a 906 mixing-type MAU or an AUI to standby(4) will cause 907 the MAU to enter the shutdown state." 908 REFERENCE 909 "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 910 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 911 acRESETMAU." 912 ::= { ifMauEntry 4 } 914 ifMauMediaAvail OBJECT-TYPE 915 SYNTAX INTEGER { 916 other(1), 917 unknown(2), 918 available(3), 919 notAvailable(4), 920 remoteFault(5), 921 invalidSignal(6), 922 remoteJabber(7), 923 remoteLinkLoss(8), 924 remoteTest(9) 925 } 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION 929 "If the MAU is a link or fiber type (FOIRL, 930 10BASE-T, 10BASE-F) then this is equivalent to the 931 link test fail state/low light function. For an 933 , 934 AUI or a coax (including broadband) MAU this 935 indicates whether or not loopback is detected on 936 the DI circuit. The value of this attribute 937 persists between packets for MAU types AUI, 938 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 940 The value other(1) is returned if the mediaAvail 941 state is not one of 2 through 6. 943 The value unknown(2) is returned when the MAU's 944 true state is unknown; for example, when it is 945 being initialized. At power-up or following a 946 reset, the value of this attribute will be unknown 947 for AUI, coax, and 10BASE-FP MAUs. For these MAUs 948 loopback will be tested on each transmission 949 during which no collision is detected. If DI is 950 receiving input when DO returns to IDL after a 951 transmission and there has been no collision 952 during the transmission then loopback will be 953 detected. The value of this attribute will only 954 change during non-collided transmissions for AUI, 955 coax, and 10BASE-FP MAUs. 957 For 100BASE-T4, 100BASE-TX and 100BASE-FX the 958 enumerations match the states within the 959 respective link integrity state diagrams, fig 23- 960 12 and 24-15 of sections 23 and 24 of [2]. Any 961 MAU which implements management of auto- 962 negotiation will map remote fault indication to 963 remote fault. 965 The value available(3) indicates that the link, 966 light, or loopback is normal. The value 967 notAvailable(4) indicates link loss, low light, or 968 no loopback. 970 The value remoteFault(5) indicates that a fault 971 has been detected at the remote end of the link. 972 This value applies to 10BASE-FB, 100BASE-T4 Far 973 End Fault Indication and non-specified remote 974 faults from a system running auto-negotiation. 975 The values remoteJabber(7), remoteLinkLoss(8), and 976 remoteTest(9) should be used instead of 977 remoteFault(5) where the reason for remote fault 978 is identified in the remote signaling protocol. 980 , 981 The value invalidSignal(6) indicates that an 982 invalid signal has been received from the other 983 end of the link. InvalidSignal(6) applies only to 984 MAUs of type 10BASE-FB. 986 Where an IEEE Std 802.3u-1995 clause 22 MII is 987 present, a logic one in the remote fault bit 988 (reference section 22.2.4.2.8 of that document) 989 maps to the value remoteFault(5), and a logic zero 990 in the link status bit (reference section 991 22.2.4.2.10 of that document) maps to the value 992 notAvailable(4). The value notAvailable(4) takes 993 precedence over the value remoteFault(5)." 994 REFERENCE 995 "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." 996 ::= { ifMauEntry 5 } 998 ifMauMediaAvailStateExits OBJECT-TYPE 999 SYNTAX Counter32 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION 1003 "A count of the number of times that 1004 ifMauMediaAvail for this MAU instance leaves the 1005 state available(3)." 1006 REFERENCE 1007 "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." 1008 ::= { ifMauEntry 6 } 1010 ifMauJabberState OBJECT-TYPE 1011 SYNTAX INTEGER { 1012 other(1), 1013 unknown(2), 1014 noJabber(3), 1015 jabbering(4) 1016 } 1017 MAX-ACCESS read-only 1018 STATUS current 1019 DESCRIPTION 1020 "The value other(1) is returned if the jabber 1021 state is not 2, 3, or 4. The agent must always 1022 return other(1) for MAU type dot3MauTypeAUI. 1024 The value unknown(2) is returned when the MAU's 1025 true state is unknown; for example, when it is 1027 , 1028 being initialized. 1030 If the MAU is not jabbering the agent returns 1031 noJabber(3). This is the 'normal' state. 1033 If the MAU is in jabber state the agent returns 1034 the jabbering(4) value." 1035 REFERENCE 1036 "[IEEE 802.3 Mgt], 30.5.1.1.6, 1037 aJabber.jabberFlag." 1038 ::= { ifMauEntry 7 } 1040 ifMauJabberingStateEnters OBJECT-TYPE 1041 SYNTAX Counter32 1042 MAX-ACCESS read-only 1043 STATUS current 1044 DESCRIPTION 1045 "A count of the number of times that 1046 mauJabberState for this MAU instance enters the 1047 state jabbering(4). For MAUs of type 1048 dot3MauTypeAUI, dot3MauType100BaseT4, 1049 dot3MauType100BaseTX, and dot3MauType100BaseFX, 1050 this counter will always indicate zero." 1051 REFERENCE 1052 "[IEEE 802.3 Mgt], 30.5.1.1.6, 1053 aJabber.jabberCounter." 1054 ::= { ifMauEntry 8 } 1056 ifMauFalseCarriers OBJECT-TYPE 1057 SYNTAX Counter32 1058 MAX-ACCESS read-only 1059 STATUS current 1060 DESCRIPTION 1061 "A count of the number of false carrier events 1062 during IDLE in 100BASE-X links. This counter does 1063 not increment at the symbol rate. It can 1064 increment after a valid carrier completion at a 1065 maximum rate of once per 100 ms until the next 1066 carrier event. 1068 This counter increments only for MAUs of type 1069 dot3MauType100BaseT4, dot3MauType100BaseTX, and 1070 dot3MauType100BaseFX. For all other MAU types, 1071 this counter will always indicate zero. 1073 , 1074 The approximate minimum time for rollover of this 1075 counter is 7.4 hours." 1076 REFERENCE 1077 "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." 1078 ::= { ifMauEntry 9 } 1080 ifMauTypeList OBJECT-TYPE 1081 SYNTAX Integer32 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "A value that uniquely identifies the set of 1086 possible IEEE 802.3 types that the MAU could be. 1087 The value is a sum which initially takes the value 1088 zero. Then, for each type capability of this MAU, 1089 2 raised to the power noted below is added to the 1090 sum. For example, a MAU which has the capability 1091 to be only 10BASE-T would have a value of 512 1092 (2**9). In contrast, a MAU which supports both 1093 10Base-T (full duplex) and 100BASE-TX (full 1094 duplex) would have a value of ((2**11) + (2**16)) 1095 or 67584. 1097 The powers of 2 assigned to the capabilities are 1098 these: 1100 Power Capability 1101 0 other or unknown 1102 1 AUI 1103 2 10BASE-5 1104 3 FOIRL 1105 4 10BASE-2 1106 5 10BASE-T duplex mode unknown 1107 6 10BASE-FP 1108 7 10BASE-FB 1109 8 10BASE-FL duplex mode unknown 1110 9 10BROAD36 1111 10 10BASE-T half duplex mode 1112 11 10BASE-T full duplex mode 1113 12 10BASE-FL half duplex mode 1114 13 10BASE-FL full duplex mode 1115 14 100BASE-T4 1116 15 100BASE-TX half duplex mode 1117 16 100BASE-TX full duplex mode 1118 17 100BASE-FX half duplex mode 1120 , 1121 18 100BASE-FX full duplex mode 1122 19 100BASE-T2 1124 If auto-negotiation is present on this MAU, this 1125 object will map to ifMauAutoNegCapability." 1126 ::= { ifMauEntry 10 } 1128 ifMauDefaultType OBJECT-TYPE 1129 SYNTAX OBJECT IDENTIFIER 1130 MAX-ACCESS read-write 1131 STATUS current 1132 DESCRIPTION 1133 "This object identifies the default administrative 1134 10 or 100 Mb/s baseband MAU type, to be used in 1135 conjunction with the operational MAU type denoted 1136 by ifMauType. 1138 The set of possible values for this object is the 1139 same as the set defined for the ifMauType object. 1141 This object represents the administratively- 1142 configured type of the MAU. If auto-negotiation 1143 is not enabled or is not implemented for this MAU, 1144 the value of this object determines the 1145 operational type of the MAU. In this case, a set 1146 to this object will force the MAU into the 1147 specified operating mode. 1149 If auto-negotiation is implemented and enabled for 1150 this MAU, the operational type of the MAU is 1151 determined by auto-negotiation, and the value of 1152 this object denotes the type to which the MAU will 1153 automatically revert if/when auto-negotiation is 1154 later disabled. 1156 NOTE TO IMPLEMENTORS: It may be necessary to 1157 provide for underlying hardware implementations 1158 which do not follow the exact behavior specified 1159 above. In particular, when 1160 ifMauAutoNegAdminStatus transitions from enabled 1161 to disabled, the agent implementation must ensure 1162 that the operational type of the MAU (as reported 1163 by ifMauType) correctly transitions to the value 1164 specified by this object, rather than continuing 1165 to operate at the value earlier determined by the 1167 , 1168 auto-negotiation function." 1169 REFERENCE 1170 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID, and [IEEE 1171 802.3 Std], 22.2.4.1.4." 1172 ::= { ifMauEntry 11 } 1174 ifMauAutoNegSupported OBJECT-TYPE 1175 SYNTAX TruthValue 1176 MAX-ACCESS read-only 1177 STATUS current 1178 DESCRIPTION 1179 "This object indicates whether or not auto- 1180 negotiation is supported on this MAU." 1181 ::= { ifMauEntry 12 } 1183 -- The ifJackTable applies to MAUs attached to interfaces 1184 -- which have one or more external jacks (connectors). 1186 ifJackTable OBJECT-TYPE 1187 SYNTAX SEQUENCE OF IfJackEntry 1188 MAX-ACCESS not-accessible 1189 STATUS current 1190 DESCRIPTION 1191 "Information about the external jacks attached to 1192 MAUs attached to an interface." 1193 ::= { dot3IfMauBasicGroup 2 } 1195 ifJackEntry OBJECT-TYPE 1196 SYNTAX IfJackEntry 1197 MAX-ACCESS not-accessible 1198 STATUS current 1199 DESCRIPTION 1200 "An entry in the table, containing information 1201 about a particular jack." 1202 INDEX { ifMauIfIndex, 1203 ifMauIndex, 1204 ifJackIndex } 1205 ::= { ifJackTable 1 } 1207 IfJackEntry ::= 1208 SEQUENCE { 1209 ifJackIndex 1210 Integer32, 1212 , 1214 ifJackType 1215 INTEGER 1216 } 1218 ifJackIndex OBJECT-TYPE 1219 SYNTAX Integer32 (1..2147483647) 1220 MAX-ACCESS not-accessible 1221 STATUS current 1222 DESCRIPTION 1223 "This variable uniquely identifies the jack 1224 described by this entry from among other jacks 1225 attached to the same MAU." 1226 ::= { ifJackEntry 1 } 1228 ifJackType OBJECT-TYPE 1229 SYNTAX INTEGER { 1230 other(1), 1231 rj45(2), 1232 rj45S(3), -- rj45 shielded 1233 db9(4), 1234 bnc(5), 1235 fAUI(6), -- female aui 1236 mAUI(7), -- male aui 1237 fiberSC(8), 1238 fiberMIC(9), 1239 fiberST(10), 1240 telco(11) 1241 } 1242 MAX-ACCESS read-only 1243 STATUS current 1244 DESCRIPTION 1245 "The jack connector type, as it appears on the 1246 outside of the system." 1247 ::= { ifJackEntry 2 } 1249 -- The ifMauAutoNegTable applies to systems in which 1250 -- auto-negotiation is supported on one or more MAUs 1251 -- attached to interfaces. Note that if auto-negotiation 1252 -- is present and enabled, the ifMauType object reflects 1253 -- the result of the auto-negotiation function. 1255 ifMauAutoNegTable OBJECT-TYPE 1256 SYNTAX SEQUENCE OF IfMauAutoNegEntry 1258 , 1259 MAX-ACCESS not-accessible 1260 STATUS current 1261 DESCRIPTION 1262 "Configuration and status objects for the auto- 1263 negotiation function of MAUs attached to 1264 interfaces." 1265 ::= { dot3IfMauAutoNegGroup 1 } 1267 ifMauAutoNegEntry OBJECT-TYPE 1268 SYNTAX IfMauAutoNegEntry 1269 MAX-ACCESS not-accessible 1270 STATUS current 1271 DESCRIPTION 1272 "An entry in the table, containing configuration 1273 and status information for the auto-negotiation 1274 function of a particular MAU." 1275 INDEX { ifMauIfIndex, ifMauIndex } 1276 ::= { ifMauAutoNegTable 1 } 1278 IfMauAutoNegEntry ::= 1279 SEQUENCE { 1280 ifMauAutoNegAdminStatus 1281 INTEGER, 1282 ifMauAutoNegRemoteSignaling 1283 INTEGER, 1284 ifMauAutoNegConfig 1285 INTEGER, 1286 ifMauAutoNegCapability 1287 Integer32, 1288 ifMauAutoNegCapAdvertised 1289 Integer32, 1290 ifMauAutoNegCapReceived 1291 Integer32, 1292 ifMauAutoNegRestart 1293 INTEGER 1295 } 1297 ifMauAutoNegAdminStatus OBJECT-TYPE 1298 SYNTAX INTEGER { 1299 enabled(1), 1300 disabled(2) 1301 } 1302 MAX-ACCESS read-write 1304 , 1305 STATUS current 1306 DESCRIPTION 1307 "Setting this object to enabled(1) will cause the 1308 interface which has the auto-negotiation signaling 1309 ability to be enabled. 1311 If the value of this object is disabled(2) then 1312 the interface will act as it would if it had no 1313 auto-negotiation signaling. Under these 1314 conditions, an IEEE 802.3 MAU will immediately be 1315 forced to the state indicated by the value of the 1316 object ifMauDefaultType. 1318 NOTE TO IMPLEMENTORS: When 1319 ifMauAutoNegAdminStatus transitions from enabled 1320 to disabled, the agent implementation must ensure 1321 that the operational type of the MAU (as reported 1322 by ifMauType) correctly transitions to the value 1323 specified by the ifMauDefaultType object, rather 1324 than continuing to operate at the value earlier 1325 determined by the auto-negotiation function." 1326 REFERENCE 1327 "[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState 1328 and 30.6.1.2.2, acAutoNegAdminControl." 1329 ::= { ifMauAutoNegEntry 1 } 1331 ifMauAutoNegRemoteSignaling OBJECT-TYPE 1332 SYNTAX INTEGER { 1333 detected(1), 1334 notdetected(2) 1335 } 1336 MAX-ACCESS read-only 1337 STATUS current 1338 DESCRIPTION 1339 "A value indicating whether the remote end of the 1340 link is using auto-negotiation signaling. It takes 1341 the value detected(1) if and only if, during the 1342 previous link negotiation, FLP Bursts were 1343 received." 1344 REFERENCE 1345 "[IEEE 802.3 Mgt], 30.6.1.1.3, 1346 aAutoNegRemoteSignaling." 1347 ::= { ifMauAutoNegEntry 2 } 1349 ifMauAutoNegConfig OBJECT-TYPE 1351 , 1352 SYNTAX INTEGER { 1353 other(1), 1354 configuring(2), 1355 complete(3), 1356 disabled(4), 1357 parallelDetectFail(5) 1358 } 1359 MAX-ACCESS read-only 1360 STATUS current 1361 DESCRIPTION 1362 "A value indicating the current status of the 1363 auto-negotiation process. The enumeration 1364 parallelDetectFail(5) maps to a failure in 1365 parallel detection as defined in 28.2.3.1 of [IEEE 1366 802.3 Std]." 1367 REFERENCE 1368 "[IEEE 802.3 Mgt], 30.6.1.1.4, 1369 aAutoNegAutoConfig." 1370 ::= { ifMauAutoNegEntry 4 } 1372 ifMauAutoNegCapability OBJECT-TYPE 1373 SYNTAX Integer32 1374 MAX-ACCESS read-only 1375 STATUS current 1376 DESCRIPTION 1377 "A value that uniquely identifies the set of 1378 capabilities of the local auto-negotiation entity. 1379 The value is a sum which initially takes the value 1380 zero. Then, for each capability of this 1381 interface, 2 raised to the power noted below is 1382 added to the sum. For example, an interface which 1383 has the capability to support only 100Base-TX half 1384 duplex would have a value of 32768 (2**15). In 1385 contrast, an interface which supports both 1386 100Base-TX half duplex and and 100Base-TX full 1387 duplex would have a value of 98304 ((2**15) + 1388 (2**16)). 1390 The powers of 2 assigned to the capabilities are 1391 these: 1393 Power Capability 1394 0 other or unknown 1395 (1-9) (reserved) 1396 10 10BASE-T half duplex mode 1398 , 1399 11 10BASE-T full duplex mode 1400 12 (reserved) 1401 13 (reserved) 1402 14 100BASE-T4 1403 15 100BASE-TX half duplex mode 1404 16 100BASE-TX full duplex mode 1406 Note that interfaces that support this MIB may 1407 have capabilities that extend beyond the scope of 1408 this MIB." 1409 REFERENCE 1410 "[IEEE 802.3 Mgt], 30.6.1.1.5, 1411 aAutoNegLocalTechnologyAbility." 1412 ::= { ifMauAutoNegEntry 5 } 1414 ifMauAutoNegCapAdvertised OBJECT-TYPE 1415 SYNTAX Integer32 1416 MAX-ACCESS read-write 1417 STATUS current 1418 DESCRIPTION 1419 "A value that uniquely identifies the set of 1420 capabilities advertised by the local auto- 1421 negotiation entity. Refer to 1422 ifMauAutoNegCapability for a description of the 1423 possible values of this object. 1425 Capabilities in this object that are not available 1426 in ifMauAutoNegCapability cannot be enabled." 1427 REFERENCE 1428 "[IEEE 802.3 Mgt], 30.6.1.1.6, 1429 aAutoNegAdvertisedTechnologyAbility." 1430 ::= { ifMauAutoNegEntry 6 } 1432 ifMauAutoNegCapReceived OBJECT-TYPE 1433 SYNTAX Integer32 1434 MAX-ACCESS read-only 1435 STATUS current 1436 DESCRIPTION 1437 "A value that uniquely identifies the set of 1438 capabilities received from the remote auto- 1439 negotiation entity. Refer to 1440 ifMauAutoNegCapability for a description of the 1441 possible values of this object. 1443 Note that interfaces that support this MIB may be 1445 , 1446 attached to remote auto-negotiation entities which 1447 have capabilities beyond the scope of this MIB." 1448 REFERENCE 1449 "[IEEE 802.3 Mgt], 30.6.1.1.7, 1450 aAutoNegReceivedTechnologyAbility." 1451 ::= { ifMauAutoNegEntry 7 } 1453 ifMauAutoNegRestart OBJECT-TYPE 1454 SYNTAX INTEGER { 1455 restart(1), 1456 norestart(2) 1457 } 1458 MAX-ACCESS read-write 1459 STATUS current 1460 DESCRIPTION 1461 "If the value of this object is set to restart(1) 1462 then this will force auto-negotiation to begin 1463 link renegotiation. If auto-negotiation signaling 1464 is disabled, a write to this object has no effect. 1466 Setting the value of this object to norestart(2) 1467 has no effect." 1468 REFERENCE 1469 "[IEEE 802.3 Mgt], 30.6.1.2.1, 1470 acAutoNegRestartAutoConfig." 1471 ::= { ifMauAutoNegEntry 8 } 1473 broadMauBasicTable OBJECT-TYPE 1474 SYNTAX SEQUENCE OF BroadMauBasicEntry 1475 MAX-ACCESS not-accessible 1476 STATUS current 1477 DESCRIPTION 1478 "Table of descriptive and status information about 1479 the broadband MAUs connected to interfaces." 1480 ::= { dot3BroadMauBasicGroup 1 } 1482 broadMauBasicEntry OBJECT-TYPE 1483 SYNTAX BroadMauBasicEntry 1484 MAX-ACCESS not-accessible 1485 STATUS current 1486 DESCRIPTION 1487 "An entry in the table, containing information 1488 about a single broadband MAU." 1489 INDEX { broadMauIfIndex, broadMauIndex } 1491 , 1492 ::= { broadMauBasicTable 1 } 1494 BroadMauBasicEntry ::= 1495 SEQUENCE { 1496 broadMauIfIndex 1497 Integer32, 1498 broadMauIndex 1499 Integer32, 1500 broadMauXmtRcvSplitType 1501 INTEGER, 1502 broadMauXmtCarrierFreq 1503 Integer32, 1504 broadMauTranslationFreq 1505 Integer32 1506 } 1508 broadMauIfIndex OBJECT-TYPE 1509 SYNTAX Integer32 1510 MAX-ACCESS read-only 1511 STATUS current 1512 DESCRIPTION 1513 "This variable uniquely identifies the interface 1514 to which the MAU described by this entry is 1515 connected." 1516 REFERENCE 1517 "Reference RFC 1213, ifIndex." 1518 ::= { broadMauBasicEntry 1 } 1520 broadMauIndex OBJECT-TYPE 1521 SYNTAX Integer32 (1..2147483647) 1522 MAX-ACCESS read-only 1523 STATUS current 1524 DESCRIPTION 1525 "This variable uniquely identifies the MAU 1526 connected to interface broadMauIfIndex that is 1527 described by this entry." 1528 REFERENCE 1529 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID." 1530 ::= { broadMauBasicEntry 2 } 1532 broadMauXmtRcvSplitType OBJECT-TYPE 1533 SYNTAX INTEGER { 1534 other(1), 1535 single(2), 1536 dual(3) 1538 , 1540 } 1541 MAX-ACCESS read-only 1542 STATUS current 1543 DESCRIPTION 1544 "This object indicates the type of frequency 1545 multiplexing/cabling system used to separate the 1546 transmit and receive paths for the 10BROAD36 MAU. 1548 The value other(1) is returned if the split type 1549 is not either single or dual. 1551 The value single(2) indicates a single cable 1552 system. The value dual(3) indicates a dual cable 1553 system, offset normally zero." 1554 REFERENCE 1555 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1556 aBbMAUXmitRcvSplitType." 1557 ::= { broadMauBasicEntry 3 } 1559 broadMauXmtCarrierFreq OBJECT-TYPE 1560 SYNTAX Integer32 1561 MAX-ACCESS read-only 1562 STATUS current 1563 DESCRIPTION 1564 "This variable indicates the transmit carrier 1565 frequency of the 10BROAD36 MAU in MHz/4; that is, 1566 in units of 250 kHz." 1567 REFERENCE 1568 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1569 aBroadbandFrequencies.xmitCarrierFrequency." 1570 ::= { broadMauBasicEntry 4 } 1572 broadMauTranslationFreq OBJECT-TYPE 1573 SYNTAX Integer32 1574 MAX-ACCESS read-only 1575 STATUS current 1576 DESCRIPTION 1577 "This variable indicates the translation offset 1578 frequency of the 10BROAD36 MAU in MHz/4; that is, 1579 in units of 250 kHz." 1580 REFERENCE 1581 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1582 aBroadbandFrequencies.translationFrequency." 1583 ::= { broadMauBasicEntry 5 } 1585 , 1587 -- Notifications for use by 802.3 MAUs 1589 rpMauJabberTrap NOTIFICATION-TYPE 1590 OBJECTS { rpMauJabberState } 1591 STATUS current 1592 DESCRIPTION 1593 "This trap is sent whenever a managed repeater MAU 1594 enters the jabber state. 1596 The agent must throttle the generation of 1597 consecutive rpMauJabberTraps so that there is at 1598 least a five-second gap between them." 1599 REFERENCE 1600 "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1601 notification." 1602 ::= { snmpDot3MauMgt 0 1 } 1604 ifMauJabberTrap NOTIFICATION-TYPE 1605 OBJECTS { ifMauJabberState } 1606 STATUS current 1607 DESCRIPTION 1608 "This trap is sent whenever a managed interface 1609 MAU enters the jabber state. 1611 The agent must throttle the generation of 1612 consecutive ifMauJabberTraps so that there is at 1613 least a five-second gap between them." 1614 REFERENCE 1615 "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1616 notification." 1617 ::= { snmpDot3MauMgt 0 2 } 1619 -- Conformance information 1621 mauModConf 1622 OBJECT IDENTIFIER ::= { mauMod 1 } 1623 mauModCompls 1624 OBJECT IDENTIFIER ::= { mauModConf 1 } 1625 mauModObjGrps 1626 OBJECT IDENTIFIER ::= { mauModConf 2 } 1627 mauModNotGrps 1628 OBJECT IDENTIFIER ::= { mauModConf 3 } 1630 , 1632 -- Object groups 1634 mauRpGrpBasic OBJECT-GROUP 1635 OBJECTS { rpMauGroupIndex, 1636 rpMauPortIndex, 1637 rpMauIndex, 1638 rpMauType, 1639 rpMauStatus, 1640 rpMauMediaAvail, 1641 rpMauMediaAvailStateExits, 1642 rpMauJabberState, 1643 rpMauJabberingStateEnters } 1644 STATUS current 1645 DESCRIPTION 1646 "Basic conformance group for MAUs attached to 1647 repeater ports. This group is also the 1648 conformance specification for RFC 1515 1649 implementations." 1650 ::= { mauModObjGrps 1 } 1652 mauRpGrp100Mbs OBJECT-GROUP 1653 OBJECTS { rpMauFalseCarriers } 1654 STATUS current 1655 DESCRIPTION 1656 "Conformance group for MAUs attached to 1657 repeater ports with 100 Mb/s capability." 1658 ::= { mauModObjGrps 2 } 1660 mauRpGrpJack OBJECT-GROUP 1661 OBJECTS { rpJackType } 1662 STATUS current 1663 DESCRIPTION 1664 "Conformance group for MAUs attached to 1665 repeater ports with managed jacks." 1666 ::= { mauModObjGrps 3 } 1668 mauIfGrpBasic OBJECT-GROUP 1669 OBJECTS { ifMauIfIndex, 1670 ifMauIndex, 1671 ifMauType, 1672 ifMauStatus, 1673 ifMauMediaAvail, 1674 ifMauMediaAvailStateExits, 1675 ifMauJabberState, 1676 ifMauJabberingStateEnters } 1678 , 1680 STATUS current 1681 DESCRIPTION 1682 "Basic conformance group for MAUs attached to 1683 interfaces. This group also provides a 1684 conformance specification for RFC 1515 1685 implementations." 1686 ::= { mauModObjGrps 4 } 1688 mauIfGrp100Mbs OBJECT-GROUP 1689 OBJECTS { ifMauFalseCarriers, 1690 ifMauTypeList, 1691 ifMauDefaultType, 1692 ifMauAutoNegSupported } 1693 STATUS current 1694 DESCRIPTION 1695 "Conformance group for MAUs attached 1696 to interfaces with 100 Mb/s capability." 1697 ::= { mauModObjGrps 5 } 1699 mauIfGrpJack OBJECT-GROUP 1700 OBJECTS { ifJackType } 1701 STATUS current 1702 DESCRIPTION 1703 "Conformance group for MAUs attached 1704 to interfaces with managed jacks." 1705 ::= { mauModObjGrps 6 } 1707 mauIfGrpAutoNeg OBJECT-GROUP 1708 OBJECTS { ifMauAutoNegAdminStatus, 1709 ifMauAutoNegRemoteSignaling, 1710 ifMauAutoNegConfig, 1711 ifMauAutoNegCapability, 1712 ifMauAutoNegCapAdvertised, 1713 ifMauAutoNegCapReceived, 1714 ifMauAutoNegRestart } 1715 STATUS current 1716 DESCRIPTION 1717 "Conformance group for MAUs attached to 1718 interfaces with managed auto-negotiation." 1719 ::= { mauModObjGrps 7 } 1721 mauBroadBasic OBJECT-GROUP 1722 OBJECTS { broadMauIfIndex, 1723 broadMauIndex, 1724 broadMauXmtRcvSplitType, 1726 , 1727 broadMauXmtCarrierFreq, 1728 broadMauTranslationFreq } 1729 STATUS current 1730 DESCRIPTION 1731 "Conformance group for broadband MAUs 1732 attached to interfaces. This group 1733 provides a conformance specification 1734 for RFC 1515 implementations." 1735 ::= { mauModObjGrps 8 } 1737 -- Compliances 1739 mauModRpCompl MODULE-COMPLIANCE 1740 STATUS current 1741 DESCRIPTION 1742 "Compliance for MAUs attached to repeater ports." 1744 MODULE -- this module 1745 MANDATORY-GROUPS { mauRpGrpBasic } 1747 GROUP mauRpGrp100Mbs 1748 DESCRIPTION 1749 "Implementation of this optional group is 1750 recommended for MAUs which have 100Mb/s 1751 capability." 1753 GROUP mauRpGrpJack 1754 DESCRIPTION 1755 "Implementation of this optional group is 1756 recommended for MAUs which have one or more 1757 external jacks." 1759 ::= { mauModCompls 1 } 1761 mauModIfCompl MODULE-COMPLIANCE 1762 STATUS current 1763 DESCRIPTION 1764 "Compliance for MAUs attached to interfaces." 1766 MODULE -- this module 1767 MANDATORY-GROUPS { mauIfGrpBasic } 1769 GROUP mauIfGrp100Mbs 1771 , 1772 DESCRIPTION 1773 "Implementation of this optional group is 1774 recommended for MAUs which have 100Mb/s 1775 capability." 1777 GROUP mauIfGrpJack 1778 DESCRIPTION 1779 "Implementation of this optional group is 1780 recommended for MAUs which have one or more 1781 external jacks." 1783 GROUP mauIfGrpAutoNeg 1784 DESCRIPTION 1785 "Implementation of this group is 1786 mandatory for MAUs which support 1787 managed auto-negotiation." 1789 GROUP mauBroadBasic 1790 DESCRIPTION 1791 "Implementation of this group is 1792 mandatory for broadband MAUs." 1794 ::= { mauModCompls 2 } 1796 END 1798 , 1799 4. Acknowledgements 1801 This document was produced by the IETF Hub MIB Working Group, 1802 whose efforts were greatly advanced by the contributions of 1803 the following people: 1805 Chuck Black 1806 John Flick 1807 Jeff Johnson 1808 Leon Leong 1809 Mike Lui 1810 Dave Perkins 1811 Geoff Thompson 1812 Maurice Turcotte 1813 Paul Woodruff 1815 , 1817 5. References 1819 [1] IEEE 802.3/ISO 8802-3 Information processing systems - 1820 Local area networks - Part 3: Carrier sense multiple 1821 access with collision detection (CSMA/CD) access method 1822 and physical layer specifications, 1993. 1824 [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium 1825 Attachment Units and Repeater for 100 Mb/s Operation, 1826 Type 100BASE-T," Sections 21 through 29, Supplement to 1827 IEEE Std 802.3, October 26, 1995. 1829 [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, 1830 Supplement to IEEE Std 802.3, October 26, 1995. 1832 [4] Romascanu, D., and K. de Graaf, "Definitions of Managed 1833 Objects for IEEE 802.3 Repeater Devices", May 1996. 1835 [5] McCloghrie, K., and M. Rose, Editors, "Management 1836 Information Base for Network Management of TCP/IP-based 1837 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 1838 Performance Systems International, March 1991. 1840 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1841 and S. Waldbusser, "Structure of Management Information 1842 for version 2 of the Simple Network Management Protocol 1843 (SNMPv2)", RFC 1902, January 1996. 1845 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1846 and S. Waldbusser, "Textual Conventions for version 2 of 1847 the Simple Network Management Protocol (SNMPv2)", RFC 1848 1903, January 1996. 1850 [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1851 and S. Waldbusser, "Conformance Statements for version 2 1852 of the Simple Network Management Protocol (SNMPv2)", RFC 1853 1904, January 1996. 1855 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1856 and S. Waldbusser, "Protocol Operations for version 2 of 1857 the Simple Network Management Protocol (SNMPv2)", RFC 1858 1905, January 1996. 1860 [10] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple 1861 Network Management Protocol", RFC 1157, SNMP Research, 1863 , 1864 Performance Systems International, MIT Laboratory for 1865 Computer Science, May 1990. 1867 [11] McMaster, D., K. McCloghrie, S. Roberts, "Definitions of 1868 Managed Objects for IEEE 802.3 Medium Attachment Units 1869 (MAUs)", RFC 1515, September 1993. 1871 , 1873 6. Security Considerations 1875 Security issues are not discussed in this memo. 1877 7. Authors' Addresses 1879 Donna McMaster 1880 Livingston Enterprises 1881 Tel: (916) 676-1147 1882 E-Mail: donna@livingston.com 1884 Keith McCloghrie 1885 Cisco Systems Inc. 1886 170 West Tasman Drive 1887 San Jose, CA 95134 1888 Tel: (408) 526-5260 1889 E-Mail: kzm@cisco.com 1891 Sam Roberts 1892 Farallon Computing, Inc. 1893 2470 Mariner Square Loop 1894 Alameda, CA 94501-1010 1895 Tel: (510) 814-5215 1896 E-Mail: sroberts@farallon.com 1898 Dan Romascanu 1899 Madge Networks (Israel) Ltd. 1900 Atidim Technology Park, Bldg. 3 1901 Tel Aviv 61131, Israel 1902 Tel: 972-3-6458414, 6458458 1903 Fax: 972-3-6487146 1904 E-mail: dromasca@madge.com 1906 Kathryn de Graaf 1907 3Com Corporation 1908 118 Turnpike Rd. 1909 Southborough, MA 01772 USA 1910 Tel: (508)229-1627 1911 Fax: (508)490-5882 1912 E-mail: kdegraaf@isd.3com.com 1914 , 1916 Table of Contents 1918 1 The SNMPv2 Network Management Framework ............... 2 1919 1.1 Object Definitions .................................. 3 1920 2 Overview .............................................. 4 1921 2.1 Relationship to RFC 1515 ............................ 4 1922 2.2 MAU Management ...................................... 4 1923 2.3 Relationship to Other MIBs .......................... 4 1924 2.3.1 Relationship to the MIB-II 'interfaces' group ..... 5 1925 2.3.2 Relationship to the 802.3 Repeater MIB ............ 5 1926 2.4 Management of Internal MAUs ......................... 5 1927 3 Definitions ........................................... 7 1928 4 Acknowledgements ...................................... 42 1929 5 References ............................................ 43 1930 6 Security Considerations ............................... 45 1931 7 Authors' Addresses .................................... 45