idnits 2.17.1 draft-ietf-hubmib-mau-mib-02.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-19) 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 == It seems as if not all pages are separated by form feeds - found 0 form feeds but 44 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: ' 5. 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 43 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 (31 May 1996) is 10185 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 1745 looks like a reference -- Missing reference section? '5' on line 1740 looks like a reference -- Missing reference section? '10' on line 1765 looks like a reference -- Missing reference section? '9' on line 1760 looks like a reference -- Missing reference section? '7' on line 1750 looks like a reference -- Missing reference section? '8' on line 1755 looks like a reference -- Missing reference section? '11' on line 1772 looks like a reference -- Missing reference section? '1' on line 1724 looks like a reference -- Missing reference section? '2' on line 1729 looks like a reference -- Missing reference section? '4' on line 1737 looks like a reference -- Missing reference section? '3' on line 1734 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 2 warnings (==), 13 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft 802.3 MAU MIB 31 May 1996 4 Definitions of Managed Objects 5 for IEEE 802.3 Medium Attachment Units (MAUs) 7 31 May 1996 9 11 Dan Romascanu 12 Madge Networks (Israel) Ltd. 13 dromasca@madge.com 15 Kathryn de Graaf 16 3Com Corporation 17 kdegraaf@isd.3com.com 19 Status of this Memo 21 This document is an Internet-Draft. Internet-Drafts are 22 working documents of the Internet Engineering Task Force 23 (IETF), its areas, and its working groups. Note that other 24 groups may also distribute working documents as Internet- 25 Drafts. 27 Internet-Drafts are draft documents valid for a maximum of six 28 months and may be updated, replaced, or obsoleted by other 29 documents at any time. It is not appropriate to use Internet- 30 Drafts as reference material or to cite them other than as a 31 "work in progress". 33 To learn the current status of any Internet-Draft, please 34 check the "1id-abstracts.txt" listing contained in the 35 Internet-Drafts Shadow Directories on ds.internic.net (US East 36 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 38 , 39 or munnari.oz.au (Pacific Rim). 41 Abstract 43 This memo defines an experimental portion of the Management 44 Information Base (MIB) for use with network management 45 protocols in the Internet community. In particular, it 46 defines objects for managing 10 and 100 Mb/second Medium 47 Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, 48 "10 & 100 Mb/s Management," October 26, 1995. 50 This memo does not specify a standard for the Internet 51 community. 53 1. The SNMPv2 Network Management Framework 55 The SNMPv2 Network Management Framework presently consists of 56 three major components. They are: 58 o the SMI, described in RFC 1902 [6] - the mechanisms used 59 for describing and naming objects for the purpose of 60 management. 62 o the MIB-II, STD 17, RFC 1213 [5] - the core set of 63 managed objects for the Internet suite of protocols. 65 o the protocol, RFC 1157 [10] and/or RFC 1905 [9] - the 66 protocol used for accessing managed information. 68 Textual conventions are defined in RFC 1903 [7], and 69 conformance statements are defined in RFC 1904 [8]. 71 The Framework permits new objects to be defined for the 72 purpose of experimentation and evaluation. 74 1.1. Object Definitions 76 Managed objects are accessed via a virtual information store, 77 termed the Management Information Base or MIB. Objects in the 78 MIB are defined using the subset of Abstract Syntax Notation 79 One (ASN.1) defined in the SMI. In particular, each object 81 , 82 type is named by an OBJECT IDENTIFIER, an administratively 83 assigned name. The object type together with an object 84 instance serves to uniquely identify a specific instantiation 85 of the object. For human convenience, we often use a textual 86 string, termed the descriptor, to refer to the object type. 88 , 89 2. Overview 91 2.1. Relationship to RFC 1515 93 This MIB is intended to be a superset of that defined by RFC 94 1515 [11], which will go to historic status. This MIB 95 includes all of the objects contained in that MIB, plus 96 several new ones which provide additional capabilities. 97 Implementors are encouraged to support all applicable 98 conformance groups in order to make the best use of the new 99 functionality provided by this MIB. The new objects provide 100 management support for: 102 o management of 100 Mb/s devices 104 o auto-negotiation 106 o jack management 108 2.2. MAU Management 110 Instances of these object types represent attributes of an 111 IEEE 802.3 MAU. Several types of MAUs are defined in the IEEE 112 802.3 CSMA/CD standard [1] and [2]. These MAUs may be 113 connected to IEEE 802.3 repeaters or to 802.3 (Ethernet-like) 114 interfaces. For convenience this document refers to these 115 devices as "repeater MAUs" and "interface MAUs." 117 The definitions presented here are based on Section 30.5, 118 "Layer Management for 10 & 100 Mb/s Medium Attachment Units 119 (MAUs)", and Annex 30A, "GDMO Specifications for 802.3 managed 120 objects" of IEEE Std 802.3u-1995. That specification includes 121 definitions for both 10Mb/s and 100Mb/s devices, and is 122 essentially a superset of the 10Mb/s definitions given by IEEE 123 802.3 Section 20. This specification is intended to serve the 124 same purpose: to provide for management of both 10Mb/s and 125 100Mb/s MAUs. 127 2.3. Relationship to Other MIBs 129 It is assumed that an agent implementing this MIB will also 130 implement (at least) the 'system' group defined in MIB-II [5]. 131 The following sections identify other MIBs that such an agent 133 , 134 should implement. 136 2.3.1. Relationship to the MIB-II 'interfaces' group 138 The sections of this document that define interface MAU- 139 related objects specify an extension to the 'interfaces' group 140 of MIB-II. An agent implementing these interface-MAU related 141 objects must also implement the 'interfaces' group of MIB-II. 142 The value of the object ifMauIfIndex is the same as the value 143 of 'ifIndex' used to instantiate the interface to which the 144 given MAU is connected. 146 It is expected that an agent implementing the interface-MAU 147 related objects in this MIB will also implement the Ethernet- 148 like Interfaces MIB, RFC 1650. 150 (Note that repeater ports are not represented as interfaces in 151 the sense of MIB-II's 'interfaces' group.) 153 2.3.2. Relationship to the 802.3 Repeater MIB 155 The section of this document that defines repeater MAU-related 156 objects specifies an extension to the 802.3 Repeater MIB 157 defined in [4]. An agent implementing these repeater-MAU 158 related objects must also implement the 802.3 Repeater MIB. 160 The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to 161 instantiate a repeater MAU variable shall be the same as the 162 values of 'rptrPortGroupIndex' and 'rptrPortIndex' used to 163 instantiate the port to which the given MAU is connected. 165 2.4. Management of Internal MAUs 167 In some situations, a MAU can be "internal" -- i.e., its 168 functionality is implemented entirely within a device. For 169 example, a managed repeater may contain an internal repeater- 170 MAU and/or an internal interface-MAU through which management 171 communications originating on one of the repeater's external 172 ports pass in order to reach the management agent associated 173 with the repeater. Such internal MAUs may or may not be 174 managed. If they are managed, objects describing their 175 attributes should appear in the appropriate MIB subtree: 177 , 178 dot3RpMauBasicGroup for internal repeater-MAUs and 179 dot3IfMauBasicGroup for internal interface-MAUs. 181 , 182 3. Definitions 184 MAU-MIB DEFINITIONS ::= BEGIN 186 IMPORTS 187 Counter32, Integer32, 188 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE, mib-2 189 FROM SNMPv2-SMI 190 OBJECT-GROUP, MODULE-COMPLIANCE 191 FROM SNMPv2-CONF; 193 mauMod MODULE-IDENTITY 194 LAST-UPDATED "9605310000Z" 195 ORGANIZATION "IETF HUB MIB Working Group" 196 CONTACT-INFO 197 "WG E-mail: hubmib@hprnd.rose.hp.com 199 Chair: Dan Romascanu 200 Postal: Madge Networks (Israel) Ltd. 201 Atidim Technology Park, Bldg. 3 202 Tel Aviv 61131, Israel 203 Tel: 972-3-6458414, 6458458 204 Fax: 972-3-6487146 205 E-mail: dromasca@madge.com 207 Editor: Kathryn de Graaf 208 Postal: 3Com Corporation 209 118 Turnpike Rd. 210 Southborough, MA 01772 211 USA 212 Tel: (508)229-1627 213 Fax: (508)490-5882 214 E-mail: kdegraaf@isd.3com.com" 215 DESCRIPTION 216 "Management information for 802.3 MAUs. 218 The following references are used throughout this 219 MIB module: 221 [IEEE 802.3 Std] 222 refers to IEEE 802.3/ISO 8802-3 Information 223 processing systems - Local area networks - 224 Part 3: Carrier sense multiple access with 225 collision detection (CSMA/CD) access method 227 , 228 and physical layer specifications (1993), 229 and to IEEE Std 802.3u-1995, Supplement to 230 IEEE Std 802.3, clauses 22 through 29. 232 [IEEE 802.3 Mgt] 233 refers to IEEE 802.3u-1995, - 10 Mb/s & 234 100 Mb/s Management, Section 30 - 235 Supplement to IEEE Std 802.3." 236 ::= { snmpDot3MauMgt 6 } 238 snmpDot3MauMgt OBJECT IDENTIFIER ::= { mib-2 26 } 240 dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } 241 dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } 242 dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } 244 dot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } 246 -- object identifiers for MAU types 247 -- (see rpMauType and ifMauType for usage) 249 dot3MauType 250 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } 251 dot3MauTypeAUI -- no internal MAU, view from AUI 252 OBJECT IDENTIFIER ::= { dot3MauType 1 } 253 dot3MauType10Base5 -- thick coax MAU (per 802.3 section 8) 254 OBJECT IDENTIFIER ::= { dot3MauType 2 } 255 dot3MauTypeFoirl -- FOIRL MAU (per 802.3 section 9.9) 256 OBJECT IDENTIFIER ::= { dot3MauType 3 } 257 dot3MauType10Base2 -- thin coax MAU (per 802.3 section 10) 258 OBJECT IDENTIFIER ::= { dot3MauType 4 } 259 dot3MauType10BaseT -- UTP MAU (per 802.3 section 14) 260 OBJECT IDENTIFIER ::= { dot3MauType 5 } 261 dot3MauType10BaseFP -- passive fiber MAU (per 802.3 section 16) 262 OBJECT IDENTIFIER ::= { dot3MauType 6 } 263 dot3MauType10BaseFB -- sync fiber MAU (per 802.3 section 17) 264 OBJECT IDENTIFIER ::= { dot3MauType 7 } 265 dot3MauType10BaseFL -- async fiber MAU (per 802.3 section 18) 266 OBJECT IDENTIFIER ::= { dot3MauType 8 } 267 dot3MauType10Broad36 -- broadband DTE MAU (per 802.3 section 11) 268 -- note that 10BROAD36 MAUs can be attached to interfaces but 270 , 271 -- not to repeaters 272 OBJECT IDENTIFIER ::= { dot3MauType 9 } 274 ------ new since RFC 1515: 276 dot3MauType10BaseTHD -- UTP MAU (per 802.3 section 14) 277 -- half duplex mode 278 OBJECT IDENTIFIER ::= { dot3MauType 10 } 280 dot3MauType10BaseTFD -- UTP MAU (per 802.3 section 14) 281 -- full duplex mode 282 OBJECT IDENTIFIER ::= { dot3MauType 11 } 284 dot3MauType10BaseFLHD -- async fiber MAU (per 802.3 section 18) 285 -- half duplex mode 286 OBJECT IDENTIFIER ::= { dot3MauType 12 } 288 dot3MauType10BaseFLFD -- async fiber MAU (per 802.3 section 18) 289 -- full duplex mode 290 OBJECT IDENTIFIER ::= { dot3MauType 13 } 292 dot3MauType100BaseT4 -- 4 pair categ. 3 UTP (per 802.3 section 23) 293 OBJECT IDENTIFIER ::= { dot3MauType 14 } 295 dot3MauType100BaseTXHD -- 2 pair categ. 5 UTP (per 802.3 section 25), 296 -- half duplex mode 297 OBJECT IDENTIFIER ::= { dot3MauType 15 } 299 dot3MauType100BaseTXFD -- 2 pair categ. 5 UTP (per 802.3 section 25), 300 -- full duplex mode 301 OBJECT IDENTIFIER ::= { dot3MauType 16 } 303 dot3MauType100BaseFXHD -- X fiber over PMT (per 802.3 section 26) 304 -- half duplex mode 305 OBJECT IDENTIFIER ::= { dot3MauType 17 } 307 dot3MauType100BaseFXFD -- X fiber over PMT (per 802.3 section 26) 308 -- full duplex mode 309 OBJECT IDENTIFIER ::= { dot3MauType 18 } 311 dot3MauType100BaseT2 312 OBJECT IDENTIFIER ::= { dot3MauType 19 } 314 -- 316 , 317 -- The Basic Repeater MAU Table 318 -- 320 rpMauTable OBJECT-TYPE 321 SYNTAX SEQUENCE OF RpMauEntry 322 MAX-ACCESS not-accessible 323 STATUS current 324 DESCRIPTION 325 "Table of descriptive and status information about 326 the MAU(s) attached to the ports of a repeater." 327 ::= { dot3RpMauBasicGroup 1 } 329 rpMauEntry OBJECT-TYPE 330 SYNTAX RpMauEntry 331 MAX-ACCESS not-accessible 332 STATUS current 333 DESCRIPTION 334 "An entry in the table, containing information 335 about a single MAU." 336 INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex } 337 ::= { rpMauTable 1 } 339 RpMauEntry ::= 340 SEQUENCE { 341 rpMauGroupIndex 342 Integer32, 343 rpMauPortIndex 344 Integer32, 345 rpMauIndex 346 Integer32, 347 rpMauType 348 OBJECT IDENTIFIER, 349 rpMauStatus 350 INTEGER, 351 rpMauMediaAvail 352 INTEGER, 353 rpMauMediaAvailStateExits 354 Counter32, 355 rpMauJabberState 356 INTEGER, 357 rpMauJabberingStateEnters 358 Counter32, 359 rpMauFalseCarriers 360 Counter32 361 } 363 , 365 rpMauGroupIndex OBJECT-TYPE 366 SYNTAX Integer32 (1..2147483647) 367 MAX-ACCESS read-only 368 STATUS current 369 DESCRIPTION 370 "This variable uniquely identifies the group 371 containing the port to which the MAU described by 372 this entry is connected. 374 Note: In practice, a group will generally be a 375 field-replaceable unit (i.e., module, card, or 376 board) that can fit in the physical system 377 enclosure, and the group number will correspond to 378 a number marked on the physical enclosure. 380 The group denoted by a particular value of this 381 object is the same as the group denoted by the 382 same value of rptrGroupIndex." 383 ::= { rpMauEntry 1 } 385 rpMauPortIndex OBJECT-TYPE 386 SYNTAX Integer32 (1..2147483647) 387 MAX-ACCESS read-only 388 STATUS current 389 DESCRIPTION 390 "This variable uniquely identifies the repeater 391 port within group rpMauGroupIndex to which the MAU 392 described by this entry is connected." 393 REFERENCE 394 "" 395 ::= { rpMauEntry 2 } 397 rpMauIndex OBJECT-TYPE 398 SYNTAX Integer32 (1..2147483647) 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION 402 "This variable uniquely identifies the MAU 403 described by this entry from among other MAUs 404 connected to the same port (rpMauPortIndex)." 405 REFERENCE 406 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 407 ::= { rpMauEntry 3 } 409 rpMauType OBJECT-TYPE 411 , 412 SYNTAX OBJECT IDENTIFIER 413 MAX-ACCESS read-only 414 STATUS current 415 DESCRIPTION 416 "This object identifies the 10 or 100 Mb/s 417 baseband MAU type. An initial set of MAU types 418 are defined above. The assignment of OBJECT 419 IDENTIFIERs to new types of MAUs is managed by the 420 IANA. If the MAU type is unknown, the object 421 identifier 423 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 425 is returned. Note that unknownMauType is a 426 syntactically valid object identifier, and any 427 conformant implementation of ASN.1 and the BER 428 must be able to generate and recognize this 429 value." 430 REFERENCE 431 "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." 432 ::= { rpMauEntry 4 } 434 rpMauStatus OBJECT-TYPE 435 SYNTAX INTEGER { 436 other(1), 437 unknown(2), 438 operational(3), 439 standby(4), 440 shutdown(5), 441 reset(6) 442 } 443 MAX-ACCESS read-write 444 STATUS current 445 DESCRIPTION 446 "The current state of the MAU. This object may be 447 implemented as a read-only object by those agents 448 and MAUs that do not implement software control of 449 the MAU state. Some agents may not support 450 setting the value of this object to some of the 451 enumerated values. 453 The value other(1) is returned if the MAU is in a 454 state other than one of the states 2 through 6. 456 The value unknown(2) is returned when the MAU's 458 , 459 true state is unknown; for example, when it is 460 being initialized. 462 A MAU in the operational(3) state is fully 463 functional, operates, and passes signals to its 464 attached DTE or repeater port in accordance to its 465 specification. 467 A MAU in standby(4) state forces DI and CI to idle 468 and the media transmitter to idle or fault, if 469 supported. Standby(4) mode only applies to link 470 type MAUs. The state of rpMauMediaAvail is 471 unaffected. 473 A MAU in shutdown(5) state assumes the same 474 condition on DI, CI, and the media transmitter as 475 though it were powered down or not connected. The 476 MAU may return other(1) value for the 477 rpMauJabberState and rpMauMediaAvail objects when 478 it is in this state. For an AUI, this state will 479 remove power from the AUI. 481 Setting this variable to the value reset(6) resets 482 the MAU in the same manner as a power-off, power- 483 on cycle of at least one-half second would. The 484 agent is not required to return the value reset 485 (6). 487 Setting this variable to the value operational(3), 488 standby(4), or shutdown(5) causes the MAU to 489 assume the respective state except that setting a 490 mixing-type MAU or an AUI to standby(4) will cause 491 the MAU to enter the shutdown state." 492 REFERENCE 493 "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 494 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 495 acRESETMAU." 496 ::= { rpMauEntry 5 } 498 rpMauMediaAvail OBJECT-TYPE 499 SYNTAX INTEGER { 500 other(1), 501 unknown(2), 502 available(3), 503 notAvailable(4), 505 , 506 remoteFault(5), 507 invalidSignal(6), 508 remoteJabber(7), 509 remoteLinkLoss(8), 510 remoteTest(9) 511 } 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "If the MAU is a link or fiber type (FOIRL, 516 10BASE-T, 10BASE-F) then this is equivalent to the 517 link test fail state/low light function. For an 518 AUI or a coax (including broadband) MAU this 519 indicates whether or not loopback is detected on 520 the DI circuit. The value of this attribute 521 persists between packets for MAU types AUI, 522 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 524 The value other(1) is returned if the mediaAvail 525 state is not one of 2 through 6. 527 The value unknown(2) is returned when the MAU's 528 true state is unknown; for example, when it is 529 being initialized. At power-up or following a 530 reset, the value of this attribute will be unknown 531 for AUI, coax, and 10BASE-FP MAUs. For these MAUs 532 loopback will be tested on each transmission 533 during which no collision is detected. If DI is 534 receiving input when DO returns to IDL after a 535 transmission and there has been no collision 536 during the transmission then loopback will be 537 detected. The value of this attribute will only 538 change during non-collided transmissions for AUI, 539 coax, and 10BASE-FP MAUs. 541 For 100BASE-T4, 100BASE-TX and 100BASE-FX the 542 enumerations match the states within the 543 respective link integrity state diagrams, fig 23- 544 12 and 24-15 of sections 23 and 24 of [2]. Any 545 MAU which implements management of auto- 546 negotiation will map remote fault indication to 547 remote fault. 549 The value available(3) indicates that the link, 550 light, or loopback is normal. The value 552 , 553 notAvailable(4) indicates link loss, low light, or 554 no loopback. 556 The value remoteFault(5) indicates that a fault 557 has been detected at the remote end of the link. 558 This value applies to 10BASE-FB, 100BASE-T4 Far 559 End Fault Indication and non-specified remote 560 faults from a system running auto-negotiation. 561 The values remoteJabber(7), remoteLinkLoss(8), and 562 remoteTest(9) should be used instead of 563 remoteFault(5) where the reason for remote fault 564 is identified in the remote signaling protocol. 566 The value invalidSignal(6) indicates that an 567 invalid signal has been received from the other 568 end of the link. InvalidSignal(6) applies only to 569 MAUs of type 10BASE-FB. 571 Where an IEEE Std 802.3u-1995 clause 22 MII is 572 present, a logic one in the remote fault bit 573 (reference section 22.2.4.2.8 of that document) 574 maps to the value remoteFault(5), and a logic zero 575 in the link status bit (reference section 576 22.2.4.2.10 of that document) maps to the value 577 notAvailable(4). The value notAvailable(4) takes 578 precedence over the value remoteFault(5)." 579 REFERENCE 580 "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." 581 ::= { rpMauEntry 6 } 583 rpMauMediaAvailStateExits OBJECT-TYPE 584 SYNTAX Counter32 585 MAX-ACCESS read-only 586 STATUS current 587 DESCRIPTION 588 "A count of the number of times that 589 rpMauMediaAvail for this MAU instance leaves the 590 state available(3)." 591 REFERENCE 592 "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." 593 ::= { rpMauEntry 7 } 595 rpMauJabberState OBJECT-TYPE 596 SYNTAX INTEGER { 597 other(1), 599 , 600 unknown(2), 601 noJabber(3), 602 jabbering(4) 603 } 604 MAX-ACCESS read-only 605 STATUS current 606 DESCRIPTION 607 "The value other(1) is returned if the jabber 608 state is not 2, 3, or 4. The agent must always 609 return other(1) for MAU type dot3MauTypeAUI. 611 The value unknown(2) is returned when the MAU's 612 true state is unknown; for example, when it is 613 being initialized. 615 If the MAU is not jabbering the agent returns 616 noJabber(3). This is the 'normal' state. 618 If the MAU is in jabber state the agent returns 619 the jabbering(4) value." 620 REFERENCE 621 "[IEEE 802.3 Mgt], 30.5.1.1.6, 622 aJabber.jabberFlag." 623 ::= { rpMauEntry 8 } 625 rpMauJabberingStateEnters OBJECT-TYPE 626 SYNTAX Counter32 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "A count of the number of times that 631 mauJabberState for this MAU instance enters the 632 state jabbering(4). For MAUs of type 633 dot3MauTypeAUI, dot3MauType100BaseT4, 634 dot3MauType100BaseTX, and dot3MauType100BaseFX, 635 this counter will always indicate zero." 636 REFERENCE 637 "[IEEE 802.3 Mgt], 30.5.1.1.6, 638 aJabber.jabberCounter." 639 ::= { rpMauEntry 9 } 641 rpMauFalseCarriers OBJECT-TYPE 642 SYNTAX Counter32 643 MAX-ACCESS read-only 644 STATUS current 646 , 647 DESCRIPTION 648 "A count of the number of false carrier events 649 during IDLE in 100BASE-X links. This counter does 650 not increment at the symbol rate. It can 651 increment after a valid carrier completion at a 652 maximum rate of once per 100 ms until the next 653 carrier event. 655 This counter increments only for MAUs of type 656 dot3MauType100BaseT4, dot3MauType100BaseTX, and 657 dot3MauType100BaseFX. For all other MAU types, 658 this counter will always indicate zero. 660 The approximate minimum time for rollover of this 661 counter is 7.4 hours." 662 REFERENCE 663 "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." 664 ::= { rpMauEntry 10 } 666 -- The rpJackTable applies to MAUs attached to repeaters 667 -- which have one or more external jacks (connectors). 669 rpJackTable OBJECT-TYPE 670 SYNTAX SEQUENCE OF RpJackEntry 671 MAX-ACCESS not-accessible 672 STATUS current 673 DESCRIPTION 674 "Information about the external jacks attached to 675 MAUs attached to the ports of a repeater." 676 ::= { dot3RpMauBasicGroup 2 } 678 rpJackEntry OBJECT-TYPE 679 SYNTAX RpJackEntry 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "An entry in the table, containing information 684 about a particular jack." 685 INDEX { rpMauGroupIndex, 686 rpMauPortIndex, 687 rpMauIndex, 688 rpJackIndex } 689 ::= { rpJackTable 1 } 691 , 693 RpJackEntry ::= 694 SEQUENCE { 695 rpJackIndex 696 Integer32, 697 rpJackType 698 INTEGER 699 } 701 rpJackIndex OBJECT-TYPE 702 SYNTAX Integer32 (1..2147483647) 703 MAX-ACCESS not-accessible 704 STATUS current 705 DESCRIPTION 706 "This variable uniquely identifies the jack 707 described by this entry from among other jacks 708 attached to the same MAU (rpMauIndex)." 709 ::= { rpJackEntry 1 } 711 rpJackType OBJECT-TYPE 712 SYNTAX INTEGER { 713 other(1), 714 rj45(2), 715 rj45S(3), -- rj45 shielded 716 db9(4), 717 bnc(5), 718 fAUI(6), -- female aui 719 mAUI(7), -- male aui 720 fiberSC(8), 721 fiberMIC(9), 722 fiberST(10), 723 telco(11) 724 } 725 MAX-ACCESS read-only 726 STATUS current 727 DESCRIPTION 728 "The jack connector type, as it appears on the 729 outside of the system." 730 ::= { rpJackEntry 2 } 732 -- 733 -- The Basic Interface MAU Table 734 -- 736 ifMauTable OBJECT-TYPE 738 , 739 SYNTAX SEQUENCE OF IfMauEntry 740 MAX-ACCESS not-accessible 741 STATUS current 742 DESCRIPTION 743 "Table of descriptive and status information about 744 MAU(s) attached to an interface." 745 ::= { dot3IfMauBasicGroup 1 } 747 ifMauEntry OBJECT-TYPE 748 SYNTAX IfMauEntry 749 MAX-ACCESS not-accessible 750 STATUS current 751 DESCRIPTION 752 "An entry in the table, containing information 753 about a single MAU." 754 INDEX { ifMauIfIndex, ifMauIndex } 755 ::= { ifMauTable 1 } 757 IfMauEntry ::= 758 SEQUENCE { 759 ifMauIfIndex 760 Integer32, 761 ifMauIndex 762 Integer32, 763 ifMauType 764 OBJECT IDENTIFIER, 765 ifMauStatus 766 INTEGER, 767 ifMauMediaAvail 768 INTEGER, 769 ifMauMediaAvailStateExits 770 Counter32, 771 ifMauJabberState 772 INTEGER, 773 ifMauJabberingStateEnters 774 Counter32, 775 ifMauFalseCarriers 776 Counter32, 777 ifMauTypeList 778 Integer32 779 } 781 ifMauIfIndex OBJECT-TYPE 782 SYNTAX Integer32 783 MAX-ACCESS read-only 785 , 786 STATUS current 787 DESCRIPTION 788 "This variable uniquely identifies the interface 789 to which the MAU described by this entry is 790 connected." 791 REFERENCE 792 "RFC 1213, ifIndex" 793 ::= { ifMauEntry 1 } 795 ifMauIndex OBJECT-TYPE 796 SYNTAX Integer32 (1..2147483647) 797 MAX-ACCESS read-only 798 STATUS current 799 DESCRIPTION 800 "This variable uniquely identifies the MAU 801 described by this entry from among other MAUs 802 connected to the same interface (ifMauIfIndex)." 803 REFERENCE 804 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 805 ::= { ifMauEntry 2 } 807 ifMauType OBJECT-TYPE 808 SYNTAX OBJECT IDENTIFIER 809 MAX-ACCESS read-write 810 STATUS current 811 DESCRIPTION 812 "This object identifies the 10 or 100 Mb/s 813 baseband MAU type. An initial set of MAU types 814 are defined above. The assignment of OBJECT 815 IDENTIFIERs to new types of MAUs is managed by the 816 IANA. If the MAU type is unknown, the object 817 identifier 819 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 821 is returned. Note that unknownMauType is a 822 syntactically valid object identifier, and any 823 conformant implementation of ASN.1 and the BER 824 must be able to generate and recognize this value. 826 If auto-negotiation is not enabled or is not 827 implemented for this MAU, a set to this object 828 will force the MAU into the new operating mode. 829 If auto-negotiation is present and enabled on this 830 MAU, a set to this object has no effect, and the 832 , 833 value of this object reflects the result of the 834 auto-negotiation function." 835 REFERENCE 836 "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." 837 ::= { ifMauEntry 3 } 839 ifMauStatus OBJECT-TYPE 840 SYNTAX INTEGER { 841 other(1), 842 unknown(2), 843 operational(3), 844 standby(4), 845 shutdown(5), 846 reset(6) 847 } 848 MAX-ACCESS read-write 849 STATUS current 850 DESCRIPTION 851 "The current state of the MAU. This object may be 852 implemented as a read-only object by those agents 853 and MAUs that do not implement software control of 854 the MAU state. Some agents may not support 855 setting the value of this object to some of the 856 enumerated values. 858 The value other(1) is returned if the MAU is in a 859 state other than one of the states 2 through 6. 861 The value unknown(2) is returned when the MAU's 862 true state is unknown; for example, when it is 863 being initialized. 865 A MAU in the operational(3) state is fully 866 functional, operates, and passes signals to its 867 attached DTE or repeater port in accordance to its 868 specification. 870 A MAU in standby(4) state forces DI and CI to idle 871 and the media transmitter to idle or fault, if 872 supported. Standby(4) mode only applies to link 873 type MAUs. The state of ifMauMediaAvail is 874 unaffected. 876 A MAU in shutdown(5) state assumes the same 877 condition on DI, CI, and the media transmitter as 879 , 880 though it were powered down or not connected. The 881 MAU may return other(1) value for the 882 ifMauJabberState and ifMauMediaAvail objects when 883 it is in this state. For an AUI, this state will 884 remove power from the AUI. 886 Setting this variable to the value reset(6) resets 887 the MAU in the same manner as a power-off, power- 888 on cycle of at least one-half second would. The 889 agent is not required to return the value reset 890 (6). 892 Setting this variable to the value operational(3), 893 standby(4), or shutdown(5) causes the MAU to 894 assume the respective state except that setting a 895 mixing-type MAU or an AUI to standby(4) will cause 896 the MAU to enter the shutdown state." 897 REFERENCE 898 "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 899 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 900 acRESETMAU." 901 ::= { ifMauEntry 4 } 903 ifMauMediaAvail OBJECT-TYPE 904 SYNTAX INTEGER { 905 other(1), 906 unknown(2), 907 available(3), 908 notAvailable(4), 909 remoteFault(5), 910 invalidSignal(6), 911 remoteJabber(7), 912 remoteLinkLoss(8), 913 remoteTest(9) 914 } 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "If the MAU is a link or fiber type (FOIRL, 919 10BASE-T, 10BASE-F) then this is equivalent to the 920 link test fail state/low light function. For an 921 AUI or a coax (including broadband) MAU this 922 indicates whether or not loopback is detected on 923 the DI circuit. The value of this attribute 924 persists between packets for MAU types AUI, 926 , 927 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 929 The value other(1) is returned if the mediaAvail 930 state is not one of 2 through 6. 932 The value unknown(2) is returned when the MAU's 933 true state is unknown; for example, when it is 934 being initialized. At power-up or following a 935 reset, the value of this attribute will be unknown 936 for AUI, coax, and 10BASE-FP MAUs. For these MAUs 937 loopback will be tested on each transmission 938 during which no collision is detected. If DI is 939 receiving input when DO returns to IDL after a 940 transmission and there has been no collision 941 during the transmission then loopback will be 942 detected. The value of this attribute will only 943 change during non-collided transmissions for AUI, 944 coax, and 10BASE-FP MAUs. 946 For 100BASE-T4, 100BASE-TX and 100BASE-FX the 947 enumerations match the states within the 948 respective link integrity state diagrams, fig 23- 949 12 and 24-15 of sections 23 and 24 of [2]. Any 950 MAU which implements management of auto- 951 negotiation will map remote fault indication to 952 remote fault. 954 The value available(3) indicates that the link, 955 light, or loopback is normal. The value 956 notAvailable(4) indicates link loss, low light, or 957 no loopback. 959 The value remoteFault(5) indicates that a fault 960 has been detected at the remote end of the link. 961 This value applies to 10BASE-FB, 100BASE-T4 Far 962 End Fault Indication and non-specified remote 963 faults from a system running auto-negotiation. 964 The values remoteJabber(7), remoteLinkLoss(8), and 965 remoteTest(9) should be used instead of 966 remoteFault(5) where the reason for remote fault 967 is identified in the remote signaling protocol. 969 The value invalidSignal(6) indicates that an 970 invalid signal has been received from the other 971 end of the link. InvalidSignal(6) applies only to 973 , 974 MAUs of type 10BASE-FB. 976 Where an IEEE Std 802.3u-1995 clause 22 MII is 977 present, a logic one in the remote fault bit 978 (reference section 22.2.4.2.8 of that document) 979 maps to the value remoteFault(5), and a logic zero 980 in the link status bit (reference section 981 22.2.4.2.10 of that document) maps to the value 982 notAvailable(4). The value notAvailable(4) takes 983 precedence over the value remoteFault(5)." 984 REFERENCE 985 "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." 986 ::= { ifMauEntry 5 } 988 ifMauMediaAvailStateExits OBJECT-TYPE 989 SYNTAX Counter32 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "A count of the number of times that 994 ifMauMediaAvail for this MAU instance leaves the 995 state available(3)." 996 REFERENCE 997 "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." 998 ::= { ifMauEntry 6 } 1000 ifMauJabberState OBJECT-TYPE 1001 SYNTAX INTEGER { 1002 other(1), 1003 unknown(2), 1004 noJabber(3), 1005 jabbering(4) 1006 } 1007 MAX-ACCESS read-only 1008 STATUS current 1009 DESCRIPTION 1010 "The value other(1) is returned if the jabber 1011 state is not 2, 3, or 4. The agent must always 1012 return other(1) for MAU type dot3MauTypeAUI. 1014 The value unknown(2) is returned when the MAU's 1015 true state is unknown; for example, when it is 1016 being initialized. 1018 If the MAU is not jabbering the agent returns 1020 , 1021 noJabber(3). This is the 'normal' state. 1023 If the MAU is in jabber state the agent returns 1024 the jabbering(4) value." 1025 REFERENCE 1026 "[IEEE 802.3 Mgt], 30.5.1.1.6, 1027 aJabber.jabberFlag." 1028 ::= { ifMauEntry 7 } 1030 ifMauJabberingStateEnters OBJECT-TYPE 1031 SYNTAX Counter32 1032 MAX-ACCESS read-only 1033 STATUS current 1034 DESCRIPTION 1035 "A count of the number of times that 1036 mauJabberState for this MAU instance enters the 1037 state jabbering(4). For MAUs of type 1038 dot3MauTypeAUI, dot3MauType100BaseT4, 1039 dot3MauType100BaseTX, and dot3MauType100BaseFX, 1040 this counter will always indicate zero." 1041 REFERENCE 1042 "[IEEE 802.3 Mgt], 30.5.1.1.6, 1043 aJabber.jabberCounter." 1044 ::= { ifMauEntry 8 } 1046 ifMauFalseCarriers OBJECT-TYPE 1047 SYNTAX Counter32 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "A count of the number of false carrier events 1052 during IDLE in 100BASE-X links. This counter does 1053 not increment at the symbol rate. It can 1054 increment after a valid carrier completion at a 1055 maximum rate of once per 100 ms until the next 1056 carrier event. 1058 This counter increments only for MAUs of type 1059 dot3MauType100BaseT4, dot3MauType100BaseTX, and 1060 dot3MauType100BaseFX. For all other MAU types, 1061 this counter will always indicate zero. 1063 The approximate minimum time for rollover of this 1064 counter is 7.4 hours." 1065 REFERENCE 1067 , 1068 "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." 1069 ::= { ifMauEntry 9 } 1071 ifMauTypeList OBJECT-TYPE 1072 SYNTAX Integer32 1073 MAX-ACCESS read-only 1074 STATUS current 1075 DESCRIPTION 1076 "A value that uniquely identifies the set of 1077 possible IEEE 802.3 types that the MAU could be. 1078 The value is a sum which initially takes the value 1079 zero. Then, for each type capability of this MAU, 1080 2 raised to the power noted below is added to the 1081 sum. For example, a MAU which has the capability 1082 to be only 10BASE-T would have a value of 512 1083 (2**9). In contrast, a MAU which supports both 1084 10Base-T (full duplex) and 100BASE-TX (full 1085 duplex) would have a value of ((2**11) + (2**16)) 1086 or 67584. 1088 The powers of 2 assigned to the capabilities are 1089 these: 1091 Power Capability 1092 0 other or unknown 1093 1 AUI 1094 2 10BASE-5 1095 3 FOIRL 1096 4 10BASE-2 1097 5 10BASE-T duplex mode unknown 1098 6 10BASE-FP 1099 7 10BASE-FB 1100 8 10BASE-FL duplex mode unknown 1101 9 10BROAD36 1102 10 10BASE-T half duplex mode 1103 11 10BASE-T full duplex mode 1104 12 10BASE-FL half duplex mode 1105 13 10BASE-FL full duplex mode 1106 14 100BASE-T4 1107 15 100BASE-TX half duplex mode 1108 16 100BASE-TX full duplex mode 1109 17 100BASE-FX half duplex mode 1110 18 100BASE-FX full duplex mode 1111 19 100BASE-T2 1113 , 1115 If auto-negotiation is present on this MAU, this 1116 object will map to ifMauAutoNegCapability." 1117 ::= { ifMauEntry 10 } 1119 -- The ifJackTable applies to MAUs attached to interfaces 1120 -- which have one or more external jacks (connectors). 1122 ifJackTable OBJECT-TYPE 1123 SYNTAX SEQUENCE OF IfJackEntry 1124 MAX-ACCESS not-accessible 1125 STATUS current 1126 DESCRIPTION 1127 "Information about the external jacks attached to 1128 MAUs attached to an interface." 1129 ::= { dot3IfMauBasicGroup 2 } 1131 ifJackEntry OBJECT-TYPE 1132 SYNTAX IfJackEntry 1133 MAX-ACCESS not-accessible 1134 STATUS current 1135 DESCRIPTION 1136 "An entry in the table, containing information 1137 about a particular jack." 1138 INDEX { ifMauIfIndex, 1139 ifMauIndex, 1140 ifJackIndex } 1141 ::= { ifJackTable 1 } 1143 IfJackEntry ::= 1144 SEQUENCE { 1145 ifJackIndex 1146 Integer32, 1147 ifJackType 1148 INTEGER 1149 } 1151 ifJackIndex OBJECT-TYPE 1152 SYNTAX Integer32 (1..2147483647) 1153 MAX-ACCESS not-accessible 1154 STATUS current 1155 DESCRIPTION 1156 "This variable uniquely identifies the jack 1157 described by this entry from among other jacks 1159 , 1160 attached to the same MAU." 1161 ::= { ifJackEntry 1 } 1163 ifJackType OBJECT-TYPE 1164 SYNTAX INTEGER { 1165 other(1), 1166 rj45(2), 1167 rj45S(3), -- rj45 shielded 1168 db9(4), 1169 bnc(5), 1170 fAUI(6), -- female aui 1171 mAUI(7), -- male aui 1172 fiberSC(8), 1173 fiberMIC(9), 1174 fiberST(10), 1175 telco(11) 1176 } 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "The jack connector type, as it appears on the 1181 outside of the system." 1182 ::= { ifJackEntry 2 } 1184 -- The ifMauAutoNegTable applies to systems in which 1185 -- auto-negotiation is supported on one or more MAUs 1186 -- attached to interfaces. Note that if auto-negotiation 1187 -- is present and enabled, the ifMauType object reflects 1188 -- the result of the auto-negotiation function. 1190 ifMauAutoNegTable OBJECT-TYPE 1191 SYNTAX SEQUENCE OF IfMauAutoNegEntry 1192 MAX-ACCESS not-accessible 1193 STATUS current 1194 DESCRIPTION 1195 "Configuration and status objects for the auto- 1196 negotiation function of MAUs attached to 1197 interfaces." 1198 ::= { dot3IfMauAutoNegGroup 1 } 1200 ifMauAutoNegEntry OBJECT-TYPE 1201 SYNTAX IfMauAutoNegEntry 1202 MAX-ACCESS not-accessible 1203 STATUS current 1205 , 1206 DESCRIPTION 1207 "An entry in the table, containing configuration 1208 and status information for the auto-negotiation 1209 function of a particular MAU." 1210 INDEX { ifMauIfIndex, ifMauIndex } 1211 ::= { ifMauAutoNegTable 1 } 1213 IfMauAutoNegEntry ::= 1214 SEQUENCE { 1215 ifMauAutoNegAdminStatus 1216 INTEGER, 1217 ifMauAutoNegRemoteSignaling 1218 INTEGER, 1219 ifMauAutoNegConfig 1220 INTEGER, 1221 ifMauAutoNegCapability 1222 Integer32, 1223 ifMauAutoNegCapAdvertised 1224 Integer32, 1225 ifMauAutoNegCapReceived 1226 Integer32, 1227 ifMauAutoNegRestart 1228 INTEGER 1230 } 1232 ifMauAutoNegAdminStatus OBJECT-TYPE 1233 SYNTAX INTEGER { 1234 enabled(1), 1235 disabled(2) 1236 } 1237 MAX-ACCESS read-write 1238 STATUS current 1239 DESCRIPTION 1240 "Setting this object to enabled(1) will cause the 1241 interface which has the auto-negotiation signaling 1242 ability to be enabled. 1244 If the value of this object is disabled(2) then 1245 the interface will act as it would if it had no 1246 auto-negotiation signaling. Under these 1247 conditions, an IEEE 802.3 MAU will immediately be 1248 forced to the state indicated by a write to the 1249 object ifMauType." 1251 , 1253 REFERENCE 1254 "[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState 1255 and 30.6.1.2.2, acAutoNegAdminControl." 1256 ::= { ifMauAutoNegEntry 1 } 1258 ifMauAutoNegRemoteSignaling OBJECT-TYPE 1259 SYNTAX INTEGER { 1260 detected(1), 1261 notdetected(2) 1262 } 1263 MAX-ACCESS read-only 1264 STATUS current 1265 DESCRIPTION 1266 "A value indicating whether the remote end of the 1267 link is using auto-negotiation signaling. It takes 1268 the value detected(1) if and only if, during the 1269 previous link negotiation, FLP Bursts were 1270 received." 1271 REFERENCE 1272 "[IEEE 802.3 Mgt], 30.6.1.1.3, 1273 aAutoNegRemoteSignaling." 1274 ::= { ifMauAutoNegEntry 2 } 1276 ifMauAutoNegConfig OBJECT-TYPE 1277 SYNTAX INTEGER { 1278 other(1), 1279 configuring(2), 1280 complete(3), 1281 disabled(4), 1282 parallelDetectFail(5) 1283 } 1284 MAX-ACCESS read-only 1285 STATUS current 1286 DESCRIPTION 1287 "A value indicating the current status of the 1288 auto-negotiation process. The enumeration 1289 parallelDetectFail(5) maps to a failure in 1290 parallel detection as defined in 28.2.3.1 of [IEEE 1291 802.3 Std]." 1292 REFERENCE 1293 "[IEEE 802.3 Mgt], 30.6.1.1.4, 1294 aAutoNegAutoConfig." 1295 ::= { ifMauAutoNegEntry 4 } 1297 ifMauAutoNegCapability OBJECT-TYPE 1299 , 1300 SYNTAX Integer32 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "A value that uniquely identifies the set of 1305 capabilities of the local auto-negotiation entity. 1306 The value is a sum which initially takes the value 1307 zero. Then, for each capability of this 1308 interface, 2 raised to the power noted below is 1309 added to the sum. For example, an interface which 1310 has the capability to support only 100Base-TX half 1311 duplex would have a value of 32768 (2**15). In 1312 contrast, an interface which supports both 1313 100Base-TX half duplex and and 100Base-TX full 1314 duplex would have a value of 98304 ((2**15) + 1315 (2**16)). 1317 The powers of 2 assigned to the capabilities are 1318 these: 1320 Power Capability 1321 0 other or unknown 1322 (1-9) (reserved) 1323 10 10BASE-T half duplex mode 1324 11 10BASE-T full duplex mode 1325 12 (reserved) 1326 13 (reserved) 1327 14 100BASE-T4 1328 15 100BASE-TX half duplex mode 1329 16 100BASE-TX full duplex mode 1331 Note that interfaces that support this MIB may 1332 have capabilities that extend beyond the scope of 1333 this MIB." 1334 REFERENCE 1335 "[IEEE 802.3 Mgt], 30.6.1.1.5, 1336 aAutoNegLocalTechnologyAbility." 1337 ::= { ifMauAutoNegEntry 5 } 1339 ifMauAutoNegCapAdvertised OBJECT-TYPE 1340 SYNTAX Integer32 1341 MAX-ACCESS read-write 1342 STATUS current 1343 DESCRIPTION 1344 "A value that uniquely identifies the set of 1346 , 1347 capabilities advertised by the local auto- 1348 negotiation entity. Refer to 1349 ifMauAutoNegCapability for a description of the 1350 possible values of this object. 1352 Capabilities in this object that are not available 1353 in ifMauAutoNegCapability cannot be enabled." 1354 REFERENCE 1355 "[IEEE 802.3 Mgt], 30.6.1.1.6, 1356 aAutoNegAdvertisedTechnologyAbility." 1357 ::= { ifMauAutoNegEntry 6 } 1359 ifMauAutoNegCapReceived OBJECT-TYPE 1360 SYNTAX Integer32 1361 MAX-ACCESS read-only 1362 STATUS current 1363 DESCRIPTION 1364 "A value that uniquely identifies the set of 1365 capabilities received from the remote auto- 1366 negotiation entity. Refer to 1367 ifMauAutoNegCapability for a description of the 1368 possible values of this object. 1370 Note that interfaces that support this MIB may be 1371 attached to remote auto-negotiation entities which 1372 have capabilities beyond the scope of this MIB." 1373 REFERENCE 1374 "[IEEE 802.3 Mgt], 30.6.1.1.7, 1375 aAutoNegReceivedTechnologyAbility." 1376 ::= { ifMauAutoNegEntry 7 } 1378 ifMauAutoNegRestart OBJECT-TYPE 1379 SYNTAX INTEGER { 1380 restart(1), 1381 norestart(2) 1382 } 1383 MAX-ACCESS read-write 1384 STATUS current 1385 DESCRIPTION 1386 "If the value of this object is set to restart(1) 1387 then this will force auto-negotiation to begin 1388 link renegotiation. If auto-negotiation signaling 1389 is disabled, a write to this object has no effect. 1391 Setting the value of this object to norestart(2) 1393 , 1394 has no effect." 1395 REFERENCE 1396 "[IEEE 802.3 Mgt], 30.6.1.2.1, 1397 acAutoNegRestartAutoConfig." 1398 ::= { ifMauAutoNegEntry 8 } 1400 broadMauBasicTable OBJECT-TYPE 1401 SYNTAX SEQUENCE OF BroadMauBasicEntry 1402 MAX-ACCESS not-accessible 1403 STATUS current 1404 DESCRIPTION 1405 "Table of descriptive and status information about 1406 the broadband MAUs connected to interfaces." 1407 ::= { dot3BroadMauBasicGroup 1 } 1409 broadMauBasicEntry OBJECT-TYPE 1410 SYNTAX BroadMauBasicEntry 1411 MAX-ACCESS not-accessible 1412 STATUS current 1413 DESCRIPTION 1414 "An entry in the table, containing information 1415 about a single broadband MAU." 1416 INDEX { broadMauIfIndex, broadMauIndex } 1417 ::= { broadMauBasicTable 1 } 1419 BroadMauBasicEntry ::= 1420 SEQUENCE { 1421 broadMauIfIndex 1422 Integer32, 1423 broadMauIndex 1424 Integer32, 1425 broadMauXmtRcvSplitType 1426 INTEGER, 1427 broadMauXmtCarrierFreq 1428 Integer32, 1429 broadMauTranslationFreq 1430 Integer32 1431 } 1433 broadMauIfIndex OBJECT-TYPE 1434 SYNTAX Integer32 1435 MAX-ACCESS read-only 1436 STATUS current 1437 DESCRIPTION 1439 , 1440 "This variable uniquely identifies the interface 1441 to which the MAU described by this entry is 1442 connected." 1443 REFERENCE 1444 "Reference RFC 1213, ifIndex." 1445 ::= { broadMauBasicEntry 1 } 1447 broadMauIndex OBJECT-TYPE 1448 SYNTAX Integer32 (1..2147483647) 1449 MAX-ACCESS read-only 1450 STATUS current 1451 DESCRIPTION 1452 "This variable uniquely identifies the MAU 1453 connected to interface broadMauIfIndex that is 1454 described by this entry." 1455 REFERENCE 1456 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID." 1457 ::= { broadMauBasicEntry 2 } 1459 broadMauXmtRcvSplitType OBJECT-TYPE 1460 SYNTAX INTEGER { 1461 other(1), 1462 single(2), 1463 dual(3) 1464 } 1465 MAX-ACCESS read-only 1466 STATUS current 1467 DESCRIPTION 1468 "This object indicates the type of frequency 1469 multiplexing/cabling system used to separate the 1470 transmit and receive paths for the 10BROAD36 MAU. 1472 The value other(1) is returned if the split type 1473 is not either single or dual. 1475 The value single(2) indicates a single cable 1476 system. The value dual(3) indicates a dual cable 1477 system, offset normally zero." 1478 REFERENCE 1479 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1480 aBbMAUXmitRcvSplitType." 1481 ::= { broadMauBasicEntry 3 } 1483 broadMauXmtCarrierFreq OBJECT-TYPE 1484 SYNTAX Integer32 1486 , 1487 MAX-ACCESS read-only 1488 STATUS current 1489 DESCRIPTION 1490 "This variable indicates the transmit carrier 1491 frequency of the 10BROAD36 MAU in MHz/4; that is, 1492 in units of 250 kHz." 1493 REFERENCE 1494 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1495 aBroadbandFrequencies.xmitCarrierFrequency." 1496 ::= { broadMauBasicEntry 4 } 1498 broadMauTranslationFreq OBJECT-TYPE 1499 SYNTAX Integer32 1500 MAX-ACCESS read-only 1501 STATUS current 1502 DESCRIPTION 1503 "This variable indicates the translation offset 1504 frequency of the 10BROAD36 MAU in MHz/4; that is, 1505 in units of 250 kHz." 1506 REFERENCE 1507 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1508 aBroadbandFrequencies.translationFrequency." 1509 ::= { broadMauBasicEntry 5 } 1511 -- Notifications for use by 802.3 MAUs 1513 rpMauJabberTrap NOTIFICATION-TYPE 1514 OBJECTS { rpMauJabberState } 1515 STATUS current 1516 DESCRIPTION 1517 "This trap is sent whenever a managed repeater MAU 1518 enters the jabber state. 1520 The agent must throttle the generation of 1521 consecutive rpMauJabberTraps so that there is at 1522 least a five-second gap between them." 1523 REFERENCE 1524 "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1525 notification." 1526 ::= { snmpDot3MauMgt 0 1 } 1528 ifMauJabberTrap NOTIFICATION-TYPE 1529 OBJECTS { ifMauJabberState } 1531 , 1532 STATUS current 1533 DESCRIPTION 1534 "This trap is sent whenever a managed interface 1535 MAU enters the jabber state. 1537 The agent must throttle the generation of 1538 consecutive ifMauJabberTraps so that there is at 1539 least a five-second gap between them." 1540 REFERENCE 1541 "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1542 notification." 1543 ::= { snmpDot3MauMgt 0 2 } 1545 -- Conformance information 1547 mauModConf 1548 OBJECT IDENTIFIER ::= { mauMod 1 } 1549 mauModCompls 1550 OBJECT IDENTIFIER ::= { mauModConf 1 } 1551 mauModObjGrps 1552 OBJECT IDENTIFIER ::= { mauModConf 2 } 1553 mauModNotGrps 1554 OBJECT IDENTIFIER ::= { mauModConf 3 } 1556 -- Object groups 1558 mauRpGrpBasic OBJECT-GROUP 1559 OBJECTS { rpMauGroupIndex, 1560 rpMauPortIndex, 1561 rpMauIndex, 1562 rpMauType, 1563 rpMauStatus, 1564 rpMauMediaAvail, 1565 rpMauMediaAvailStateExits, 1566 rpMauJabberState, 1567 rpMauJabberingStateEnters } 1568 STATUS current 1569 DESCRIPTION 1570 "Basic conformance group for MAUs attached to 1571 repeater ports. This group is also the 1572 conformance specification for RFC 1515 1573 implementations." 1574 ::= { mauModObjGrps 1 } 1576 , 1578 mauRpGrp100Mbs OBJECT-GROUP 1579 OBJECTS { rpMauFalseCarriers } 1580 STATUS current 1581 DESCRIPTION 1582 "Conformance group for MAUs attached to 1583 repeater ports with 100 Mb/s capability." 1584 ::= { mauModObjGrps 2 } 1586 mauRpGrpJack OBJECT-GROUP 1587 OBJECTS { rpJackType } 1588 STATUS current 1589 DESCRIPTION 1590 "Conformance group for MAUs attached to 1591 repeater ports with managed jacks." 1592 ::= { mauModObjGrps 3 } 1594 mauIfGrpBasic OBJECT-GROUP 1595 OBJECTS { ifMauIfIndex, 1596 ifMauIndex, 1597 ifMauType, 1598 ifMauStatus, 1599 ifMauMediaAvail, 1600 ifMauMediaAvailStateExits, 1601 ifMauJabberState, 1602 ifMauJabberingStateEnters } 1603 STATUS current 1604 DESCRIPTION 1605 "Basic conformance group for MAUs attached to 1606 interfaces. This group also provides a 1607 conformance specification for RFC 1515 1608 implementations." 1609 ::= { mauModObjGrps 4 } 1611 mauIfGrp100Mbs OBJECT-GROUP 1612 OBJECTS { ifMauFalseCarriers, 1613 ifMauTypeList } 1614 STATUS current 1615 DESCRIPTION 1616 "Conformance group for MAUs attached 1617 to interfaces with 100 Mb/s capability." 1618 ::= { mauModObjGrps 5 } 1620 mauIfGrpJack OBJECT-GROUP 1621 OBJECTS { ifJackType } 1622 STATUS current 1624 , 1625 DESCRIPTION 1626 "Conformance group for MAUs attached 1627 to interfaces with managed jacks." 1628 ::= { mauModObjGrps 6 } 1630 mauIfGrpAutoNeg OBJECT-GROUP 1631 OBJECTS { ifMauAutoNegAdminStatus, 1632 ifMauAutoNegRemoteSignaling, 1633 ifMauAutoNegConfig, 1634 ifMauAutoNegCapability, 1635 ifMauAutoNegCapAdvertised, 1636 ifMauAutoNegCapReceived, 1637 ifMauAutoNegRestart } 1638 STATUS current 1639 DESCRIPTION 1640 "Conformance group for MAUs attached to 1641 interfaces with managed auto-negotiation." 1642 ::= { mauModObjGrps 7 } 1644 mauBroadBasic OBJECT-GROUP 1645 OBJECTS { broadMauIfIndex, 1646 broadMauIndex, 1647 broadMauXmtRcvSplitType, 1648 broadMauXmtCarrierFreq, 1649 broadMauTranslationFreq } 1650 STATUS current 1651 DESCRIPTION 1652 "Conformance group for broadband MAUs 1653 attached to interfaces. This group 1654 provides a conformance specification 1655 for RFC 1515 implementations." 1656 ::= { mauModObjGrps 8 } 1658 -- Compliances 1660 mauModRpCompl MODULE-COMPLIANCE 1661 STATUS current 1662 DESCRIPTION 1663 "Compliance for MAUs attached to repeater ports." 1665 MODULE -- this module 1666 MANDATORY-GROUPS { mauRpGrpBasic } 1668 GROUP mauRpGrp100Mbs 1670 , 1671 DESCRIPTION 1672 "Implementation of this optional group is 1673 recommended for MAUs which have 100Mb/s 1674 capability." 1676 GROUP mauRpGrpJack 1677 DESCRIPTION 1678 "Implementation of this optional group is 1679 recommended for MAUs which have one or more 1680 external jacks." 1682 ::= { mauModCompls 1 } 1684 mauModIfCompl MODULE-COMPLIANCE 1685 STATUS current 1686 DESCRIPTION 1687 "Compliance for MAUs attached to interfaces." 1689 MODULE -- this module 1690 MANDATORY-GROUPS { mauIfGrpBasic } 1692 GROUP mauIfGrp100Mbs 1693 DESCRIPTION 1694 "Implementation of this optional group is 1695 recommended for MAUs which have 100Mb/s 1696 capability." 1698 GROUP mauIfGrpJack 1699 DESCRIPTION 1700 "Implementation of this optional group is 1701 recommended for MAUs which have one or more 1702 external jacks." 1704 GROUP mauIfGrpAutoNeg 1705 DESCRIPTION 1706 "Implementation of this group is 1707 mandatory for MAUs which support 1708 managed auto-negotiation." 1710 GROUP mauBroadBasic 1711 DESCRIPTION 1712 "Implementation of this group is 1713 mandatory for broadband MAUs." 1715 , 1717 ::= { mauModCompls 2 } 1719 END 1721 , 1722 4. References 1724 [1] IEEE 802.3/ISO 8802-3 Information processing systems - 1725 Local area networks - Part 3: Carrier sense multiple 1726 access with collision detection (CSMA/CD) access method 1727 and physical layer specifications, 1993. 1729 [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium 1730 Attachment Units and Repeater for 100 Mb/s Operation, 1731 Type 100BASE-T," Sections 21 through 29, Supplement to 1732 IEEE Std 802.3, October 26, 1995. 1734 [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, 1735 Supplement to IEEE Std 802.3, October 26, 1995. 1737 [4] Romascanu, D., and K. de Graaf, "Definitions of Managed 1738 Objects for IEEE 802.3 Repeater Devices", May 1996. 1740 [5] McCloghrie, K., and M. Rose, Editors, "Management 1741 Information Base for Network Management of TCP/IP-based 1742 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 1743 Performance Systems International, March 1991. 1745 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1746 and S. Waldbusser, "Structure of Management Information 1747 for version 2 of the Simple Network Management Protocol 1748 (SNMPv2)", RFC 1902, January 1996. 1750 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1751 and S. Waldbusser, "Textual Conventions for version 2 of 1752 the Simple Network Management Protocol (SNMPv2)", RFC 1753 1903, January 1996. 1755 [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1756 and S. Waldbusser, "Conformance Statements for version 2 1757 of the Simple Network Management Protocol (SNMPv2)", RFC 1758 1904, January 1996. 1760 [9] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., 1761 and S. Waldbusser, "Protocol Operations for version 2 of 1762 the Simple Network Management Protocol (SNMPv2)", RFC 1763 1905, January 1996. 1765 [10] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple 1766 Network Management Protocol", RFC 1157, SNMP Research, 1768 , 1769 Performance Systems International, MIT Laboratory for 1770 Computer Science, May 1990. 1772 [11] McMaster, D., K. McCloghrie, S. Roberts, "Definitions of 1773 Managed Objects for IEEE 802.3 Medium Attachment Units 1774 (MAUs)", RFC 1515, September 1993. 1776 , 1778 5. Security Considerations 1780 Security issues are not discussed in this memo. 1782 6. Authors' Addresses 1784 Dan Romascanu 1785 Madge Networks (Israel) Ltd. 1786 Atidim Technology Park, Bldg. 3 1787 Tel Aviv 61131, Israel 1788 Tel: 972-3-6458414, 6458458 1789 Fax: 972-3-6487146 1790 E-mail: dromasca@madge.com 1792 Kathryn de Graaf 1793 3Com Corporation 1794 118 Turnpike Rd. 1795 Southborough, MA 01772 USA 1796 Tel: (508)229-1627 1797 Fax: (508)490-5882 1798 E-mail: kdegraaf@isd.3com.com 1800 , 1802 Table of Contents 1804 1 The SNMPv2 Network Management Framework ............... 2 1805 1.1 Object Definitions .................................. 2 1806 2 Overview .............................................. 4 1807 2.1 Relationship to RFC 1515 ............................ 4 1808 2.2 MAU Management ...................................... 4 1809 2.3 Relationship to Other MIBs .......................... 4 1810 2.3.1 Relationship to the MIB-II 'interfaces' group ..... 5 1811 2.3.2 Relationship to the 802.3 Repeater MIB ............ 5 1812 2.4 Management of Internal MAUs ......................... 5 1813 3 Definitions ........................................... 7 1814 4 References ............................................ 41 1815 5 Security Considerations ............................... 43 1816 6 Authors' Addresses .................................... 43