idnits 2.17.1 draft-ietf-hubmib-mau-mib-01.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-25) 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. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an 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. ** 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 11 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** The abstract seems to contain references ([2], [3], [4], [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 (14 February 1996) is 10298 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? '1' on line 1678 looks like a reference -- Missing reference section? '2' on line 1683 looks like a reference -- Missing reference section? '4' on line 1691 looks like a reference -- Missing reference section? '3' on line 1688 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 1 warning (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft 802.3 MAU MIB 14 February 1996 4 Definitions of Managed Objects 5 for IEEE 802.3 Medium Attachment Units (MAUs) 7 14 February 1996 9 11 Dan Romascanu 12 Madge Networks (Israel) Ltd. 13 dan@lannet.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), 37 or munnari.oz.au (Pacific Rim). 39 Abstract 41 This memo defines an experimental portion of the Management 42 Information Base (MIB) for use with network management 43 protocols in the Internet community. In particular, it 44 defines objects for managing 10 and 100 Mb/second Medium 45 Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, 46 "10 & 100 Mb/s Management," October 26, 1995. 48 This memo does not specify a standard for the Internet 49 community. 51 1. The SNMPv2 Network Management Framework 53 The SNMPv2 Network Management Framework consists of several 54 major components. They include: 56 o RFC 1902 which defines the SMI, the mechanisms used for 57 describing and naming objects for the purpose of 58 management. 60 o STD 17, RFC 1213 defines MIB-II, the core set of managed 61 objects for the Internet suite of protocols. 63 o RFC 1905 which defines the protocol used for network 64 access to managed objects. 66 The Framework permits new objects to be defined for the 67 purpose of experimentation and evaluation. 69 1.1. Object Definitions 71 Managed objects are accessed via a virtual information store, 72 termed the Management Information Base or MIB. Objects in the 73 MIB are defined using the subset of Abstract Syntax Notation 74 One (ASN.1) defined in the SMI. In particular, each object 75 type is named by an OBJECT IDENTIFIER, an administratively 76 assigned name. The object type together with an object 77 instance serves to uniquely identify a specific instantiation 78 of the object. For human convenience, we often use a textual 79 string, termed the descriptor, to refer to the object type. 81 2. Overview 83 Instances of these object types represent attributes of an 84 IEEE 802.3 MAU. Several types of MAUs are defined in the IEEE 85 802.3 CSMA/CD standard [1] and [2]. These MAUs may be 86 connected to IEEE 802.3 repeaters or to 802.3 (Ethernet-like) 87 interfaces. For convenience this document refers to these 88 devices as "repeater MAUs" and "interface MAUs." 90 The definitions presented here are based on Section 30.5, 91 "Layer Management for 10 & 100 Mb/s Medium Attachment Units 92 (MAUs)", and Annex 30A, "GDMO Specifications for 802.3 managed 93 objects" of IEEE Std 802.3u-1995. That specification includes 94 definitions for both 10Mb/s and 100Mb/s devices, and is 95 essentially a superset of the 10Mb/s definitions given by IEEE 96 802.3 Section 20. This specification is intended to serve the 97 same purpose: to provide for management of both 10Mb/s and 98 100Mb/s MAUs. 100 2.1. Relationship to Other MIBs 102 It is assumed that an agent implementing this MIB will also 103 implement (at least) the 'system' group defined in MIB-II. 104 The following sections identify other MIBs that such an agent 105 should implement. 107 2.1.1. Relationship to the 'interfaces' group 109 The sections of this document that define interface MAU- 110 related objects specify an extension to the 'interfaces' group 111 of MIB-II. An agent implementing these interface-MAU related 112 objects must also implement the 'interfaces' group of MIB-II. 113 The value of the ifMauIfIndex object is the same as the value 114 of 'ifIndex' used to instantiate the interface to which the 115 given MAU is connected. 117 It is expected that an agent implementing the interface-MAU 118 related objects in this MIB will also implement the Ethernet- 119 like Interfaces MIB, RFC 1650. 121 (Note that repeater ports are not represented as interfaces in 122 the sense of MIB-II's 'interfaces' group.) 123 2.1.2. Relationship to the 802.3 Repeater MIB 125 The section of this document that defines repeater MAU-related 126 objects specifies an extension to the 802.3 Repeater MIB 127 defined in [4]. An agent implementing these repeater-MAU 128 related objects must also implement the 802.3 Repeater MIB. 130 The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to 131 instantiate a repeater MAU variable shall be the same as the 132 values of 'rptrPortGroupIndex' and 'rptrPortIndex' used to 133 instantiate the port to which the given MAU is connected. 135 2.2. Management of Internal MAUs 137 In some situations, a MAU can be "internal" -- i.e., its 138 functionality is implemented entirely within a device. For 139 example, a managed repeater may contain an internal repeater- 140 MAU and/or an internal interface-MAU through which management 141 communications originating on one of the repeater's external 142 ports pass in order to reach the management agent associated 143 with the repeater. Such internal MAUs may or may not be 144 managed. If they are managed, objects describing their 145 attributes should appear in the appropriate MIB group -- 146 dot3RpMauBasicGroup for internal repeater-MAUs and 147 dot3IfMauBasicGroup for internal interface-MAUs. 149 3. Definitions 151 MAU-MIB DEFINITIONS ::= BEGIN 153 IMPORTS 154 experimental, 155 Counter32, Integer32, 156 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE 157 FROM SNMPv2-SMI 158 OBJECT-GROUP, MODULE-COMPLIANCE 159 FROM SNMPv2-CONF 160 mib-2 161 FROM RFC1213-MIB; 163 mauMod MODULE-IDENTITY 164 LAST-UPDATED "9602140000Z" 165 ORGANIZATION "IETF HUB MIB Working Group" 166 CONTACT-INFO 167 "WG E-mail: hubmib@hprnd.rose.hp.com 169 Chair: Dan Romascanu 170 Postal: Madge Networks (Israel) Ltd. 171 Atidim Technology Park, Bldg. 3 172 Tel Aviv 61131, Israel 173 Tel: 972-3-6458414, 6458458 174 Fax: 972-3-6487146 175 E-mail: dan@lannet.com 177 Editor: Kathryn de Graaf 178 Postal: 3Com Corporation 179 118 Turnpike Rd. 180 Southborough, MA 01772 181 USA 182 Tel: (508)229-1627 183 Fax: (508)490-5882 184 E-mail: kdegraaf@isd.3com.com" 185 DESCRIPTION 186 "Management information for 802.3 MAUs. 188 The following references are used throughout this 189 MIB module: 191 [IEEE 802.3 Std] 192 refers to IEEE 802.3/ISO 8802-3 Information 193 processing systems - Local area networks - 194 Part 3: Carrier sense multiple access with 195 collision detection (CSMA/CD) access method 196 and physical layer specifications (1993), 197 and to IEEE Std 802.3u-1995, Supplement to 198 IEEE Std 802.3, clauses 22 through 29. 200 [IEEE 802.3 Mgt] 201 refers to IEEE 802.3u-1995, - 10 Mb/s & 202 100 Mb/s Management, Section 30 - 203 Supplement to IEEE Std 802.3." 204 ::= { snmpDot3MauMgt 6 } 206 snmpDot3MauMgt OBJECT IDENTIFIER ::= { experimental x } 208 dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } 209 dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } 210 dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } 212 dot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } 214 -- object identifiers for MAU types 215 -- (see rpMauType and ifMauType for usage) 217 dot3MauType 218 OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } 219 dot3MauTypeAUI -- no internal MAU, view from AUI 220 OBJECT IDENTIFIER ::= { dot3MauType 1 } 221 dot3MauType10Base5 -- thick coax MAU (per 802.3 section 8) 222 OBJECT IDENTIFIER ::= { dot3MauType 2 } 223 dot3MauTypeFoirl -- FOIRL MAU (per 802.3 section 9.9) 224 OBJECT IDENTIFIER ::= { dot3MauType 3 } 225 dot3MauType10Base2 -- thin coax MAU (per 802.3 section 10) 226 OBJECT IDENTIFIER ::= { dot3MauType 4 } 227 dot3MauType10BaseT -- UTP MAU (per 802.3 section 14) 228 OBJECT IDENTIFIER ::= { dot3MauType 5 } 229 dot3MauType10BaseFP -- passive fiber MAU (per 802.3 section 16) 230 OBJECT IDENTIFIER ::= { dot3MauType 6 } 231 dot3MauType10BaseFB -- sync fiber MAU (per 802.3 section 17) 232 OBJECT IDENTIFIER ::= { dot3MauType 7 } 233 dot3MauType10BaseFL -- async fiber MAU (per 802.3 section 18) 234 OBJECT IDENTIFIER ::= { dot3MauType 8 } 235 dot3MauType10Broad36 -- broadband DTE MAU (per 802.3 section 11) 236 -- note that 10BROAD36 MAUs can be attached to interfaces but 237 -- not to repeaters 238 OBJECT IDENTIFIER ::= { dot3MauType 9 } 240 -- new for 100 MB/s: 242 dot3MauType100BaseT4 -- 4 pair categ. 3 UTP (per 802.3 section 23) 243 OBJECT IDENTIFIER ::= { dot3MauType 10 } 244 dot3MauType100BaseTX -- 2 pair categ. 5 UTP (per 802.3 section 25) 245 OBJECT IDENTIFIER ::= { dot3MauType 11 } 246 dot3MauType100BaseFX -- X fiber over PMT (per 802.3 section 26) 247 OBJECT IDENTIFIER ::= { dot3MauType 12 } 249 -- 250 -- The Basic Repeater MAU Table 251 -- 253 rpMauTable OBJECT-TYPE 254 SYNTAX SEQUENCE OF RpMauEntry 255 MAX-ACCESS not-accessible 256 STATUS current 257 DESCRIPTION 258 "Table of descriptive and status information about 259 the MAU(s) attached to the ports of a repeater." 260 ::= { dot3RpMauBasicGroup 1 } 262 rpMauEntry OBJECT-TYPE 263 SYNTAX RpMauEntry 264 MAX-ACCESS not-accessible 265 STATUS current 266 DESCRIPTION 267 "An entry in the table, containing information 268 about a single MAU." 269 INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex } 270 ::= { rpMauTable 1 } 272 RpMauEntry ::= 273 SEQUENCE { 274 rpMauGroupIndex 275 Integer32, 276 rpMauPortIndex 277 Integer32, 279 rpMauIndex 280 Integer32, 281 rpMauType 282 OBJECT IDENTIFIER, 283 rpMauStatus 284 INTEGER, 285 rpMauMediaAvail 286 INTEGER, 287 rpMauMediaAvailStateExits 288 Counter32, 289 rpMauJabberState 290 INTEGER, 291 rpMauJabberingStateEnters 292 Counter32, 293 rpMauFalseCarriers 294 Counter32 295 } 297 rpMauGroupIndex OBJECT-TYPE 298 SYNTAX Integer32 (1..2147483647) 299 MAX-ACCESS read-only 300 STATUS current 301 DESCRIPTION 302 "This variable uniquely identifies the group 303 containing the port to which the MAU described by 304 this entry is connected. 306 Note: In practice, a group will generally be a 307 field-replaceable unit (i.e., module, card, or 308 board) that can fit in the physical system 309 enclosure, and the group number will correspond to 310 a number marked on the physical enclosure. 312 The group denoted by a particular value of this 313 object is the same as the group denoted by the 314 same value of rptrGroupIndex." 315 ::= { rpMauEntry 1 } 317 rpMauPortIndex OBJECT-TYPE 318 SYNTAX Integer32 (1..2147483647) 319 MAX-ACCESS read-only 320 STATUS current 321 DESCRIPTION 322 "This variable uniquely identifies the repeater 323 port within group rpMauGroupIndex to which the MAU 324 described by this entry is connected." 325 REFERENCE 326 "" 327 ::= { rpMauEntry 2 } 329 rpMauIndex OBJECT-TYPE 330 SYNTAX Integer32 (1..2147483647) 331 MAX-ACCESS read-only 332 STATUS current 333 DESCRIPTION 334 "This variable uniquely identifies the MAU 335 connected to port rpMauPortIndex within group 336 rpMauGroupIndex that is described by this entry." 337 REFERENCE 338 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 339 ::= { rpMauEntry 3 } 341 rpMauType OBJECT-TYPE 342 SYNTAX OBJECT IDENTIFIER 343 MAX-ACCESS read-only 344 STATUS current 345 DESCRIPTION 346 "This object identifies the 10 or 100 Mb/s 347 baseband MAU type. An initial set of MAU types 348 are defined above. The assignment of OBJECT 349 IDENTIFIERs to new types of MAUs is managed by the 350 IANA. If the MAU type is unknown, the object 351 identifier 353 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 355 is returned. Note that unknownMauType is a 356 syntactically valid object identifier, and any 357 conformant implementation of ASN.1 and the BER 358 must be able to generate and recognize this 359 value." 360 REFERENCE 361 "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." 362 ::= { rpMauEntry 4 } 364 rpMauStatus OBJECT-TYPE 365 SYNTAX INTEGER { 366 other(1), 367 unknown(2), 368 operational(3), 369 standby(4), 370 shutdown(5), 371 reset(6) 372 } 373 MAX-ACCESS read-write 374 STATUS current 375 DESCRIPTION 376 "The current state of the MAU. This object may be 377 implemented as a read-only object by those agents 378 and MAUs that do not implement software control of 379 the MAU state. Some agents may not support 380 setting the value of this object to some of the 381 enumerated values. 383 The value other(1) is returned if the MAU is in a 384 state other than one of the states 2 through 6. 386 The value unknown(2) is returned when the MAU's 387 true state is unknown; for example, when it is 388 being initialized. 390 A MAU in the operational(3) state is fully 391 functional, operates, and passes signals to its 392 attached DTE or repeater port in accordance to its 393 specification. 395 A MAU in standby(4) state forces DI and CI to idle 396 and the media transmitter to idle or fault, if 397 supported. Standby(4) mode only applies to link 398 type MAUs. The state of rpMauMediaAvail is 399 unaffected. 401 A MAU in shutdown(5) state assumes the same 402 condition on DI, CI, and the media transmitter as 403 though it were powered down or not connected. The 404 MAU may return other(1) value for the 405 rpMauJabberState and rpMauMediaAvail objects when 406 it is in this state. For an AUI, this state will 407 remove power from the AUI. 409 Setting this variable to the value reset(6) resets 410 the MAU in the same manner as a power-off, power- 411 on cycle of at least one-half second would. The 412 agent is not required to return the value reset 413 (6). 415 Setting this variable to the value operational(3), 416 standby(4), or shutdown(5) causes the MAU to 417 assume the respective state except that setting a 418 mixing-type MAU or an AUI to standby(4) will cause 419 the MAU to enter the shutdown state." 420 REFERENCE 421 "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 422 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 423 acRESETMAU." 424 ::= { rpMauEntry 5 } 426 rpMauMediaAvail OBJECT-TYPE 427 SYNTAX INTEGER { 428 other(1), 429 unknown(2), 430 available(3), 431 notAvailable(4), 432 remoteFault(5), 433 invalidSignal(6), 434 remoteJabber(7), 435 remoteLinkLoss(8), 436 remoteTest(9) 437 } 438 MAX-ACCESS read-only 439 STATUS current 440 DESCRIPTION 441 "If the MAU is a link or fiber type (FOIRL, 442 10BASE-T, 10BASE-F) then this is equivalent to the 443 link test fail state/low light function. For an 444 AUI or a coax (including broadband) MAU this 445 indicates whether or not loopback is detected on 446 the DI circuit. The value of this attribute 447 persists between packets for MAU types AUI, 448 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 450 The value other(1) is returned if the mediaAvail 451 state is not one of 2 through 6. 453 The value unknown(2) is returned when the MAU's 454 true state is unknown; for example, when it is 455 being initialized. At power-up or following a 456 reset, the value of this attribute will be unknown 457 for AUI, coax, and 10BASE-FP MAUs. For these MAUs 458 loopback will be tested on each transmission 459 during which no collision is detected. If DI is 460 receiving input when DO returns to IDL after a 461 transmission and there has been no collision 462 during the transmission then loopback will be 463 detected. The value of this attribute will only 464 change during non-collided transmissions for AUI, 465 coax, and 10BASE-FP MAUs. 467 For 100BASE-T4, 100BASE-TX and 100BASE-FX the 468 enumerations match the states within the 469 respective link integrity state diagrams, fig 23- 470 12 and 24-15 of sections 23 and 24 of [2]. Any 471 MAU which implements management of Auto- 472 Negotiation will map remote fault indication to 473 remote fault. 475 The value available(3) indicates that the link, 476 light, or loopback is normal. The value 477 notAvailable(4) indicates link loss, low light, or 478 no loopback. 480 The value remoteFault(5) indicates that a fault 481 has been detected at the remote end of the link. 482 This value applies to 10BASE-FB, 100BASE-T4 Far 483 End Fault Indication and non-specified remote 484 faults from a system running Auto-Negotiation. 485 The values remoteJabber(7), remoteLinkLoss(8), and 486 remoteTest(9) should be used instead of 487 remoteFault(5) where the reason for remote fault 488 is identified in the remote signaling protocol. 490 The value invalidSignal(6) indicates that an 491 invalid signal has been received from the other 492 end of the link. InvalidSignal(6) applies only to 493 MAUs of type 10BASE-FB. 495 Where an IEEE Std 802.3u-1995 clause 22 MII is 496 present, a logic one in the remote fault bit 497 (reference section 22.2.4.2.8 of that document) 498 maps to the value remoteFault(5), and a logic zero 499 in the link status bit (reference section 500 22.2.4.2.10 of that document) maps to the value 501 notAvailable(4). The value notAvailable(4) takes 502 precedence over the value remoteFault(5)." 503 REFERENCE 504 "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." 506 ::= { rpMauEntry 6 } 508 rpMauMediaAvailStateExits OBJECT-TYPE 509 SYNTAX Counter32 510 MAX-ACCESS read-only 511 STATUS current 512 DESCRIPTION 513 "A count of the number of times that 514 rpMauMediaAvail for this MAU instance leaves the 515 state available(3)." 516 REFERENCE 517 "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." 518 ::= { rpMauEntry 7 } 520 rpMauJabberState OBJECT-TYPE 521 SYNTAX INTEGER { 522 other(1), 523 unknown(2), 524 noJabber(3), 525 jabbering(4) 526 } 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "The value other(1) is returned if the jabber 531 state is not 2, 3, or 4. The agent must always 532 return other(1) for MAU type dot3MauTypeAUI. 534 The value unknown(2) is returned when the MAU's 535 true state is unknown; for example, when it is 536 being initialized. 538 If the MAU is not jabbering the agent returns 539 noJabber(3). This is the 'normal' state. 541 If the MAU is in jabber state the agent returns 542 the jabbering(4) value." 543 REFERENCE 544 "[IEEE 802.3 Mgt], 30.5.1.1.6, 545 aJabber.jabberFlag." 546 ::= { rpMauEntry 8 } 548 rpMauJabberingStateEnters OBJECT-TYPE 549 SYNTAX Counter32 550 MAX-ACCESS read-only 551 STATUS current 552 DESCRIPTION 553 "A count of the number of times that 554 mauJabberState for this MAU instance enters the 555 state jabbering(4). For MAUs of type 556 dot3MauTypeAUI, dot3MauType100BaseT4, 557 dot3MauType100BaseTX, and dot3MauType100BaseFX, 558 this counter will always indicate zero." 559 REFERENCE 560 "[IEEE 802.3 Mgt], 30.5.1.1.6, 561 aJabber.jabberCounter." 562 ::= { rpMauEntry 9 } 564 rpMauFalseCarriers OBJECT-TYPE 565 SYNTAX Counter32 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "A count of the number of false carrier events 570 during IDLE in 100BASE-X links. This counter does 571 not increment at the symbol rate. It can 572 increment after a valid carrier completion at a 573 maximum rate of once per 100 ms until the next 574 carrier event. 576 This counter increments only for MAUs of type 577 dot3MauType100BaseT4, dot3MauType100BaseTX, and 578 dot3MauType100BaseFX. For all other MAU types, 579 this counter will always indicate zero. 581 The approximate minimum time for rollover of this 582 counter is 7.4 hours." 583 REFERENCE 584 "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." 585 ::= { rpMauEntry 10 } 587 -- The rpJackTable applies to MAUs attached to repeaters 588 -- which have one or more external jacks (connectors). 590 rpJackTable OBJECT-TYPE 591 SYNTAX SEQUENCE OF RpJackEntry 592 MAX-ACCESS not-accessible 593 STATUS current 594 DESCRIPTION 595 "Information about the external jacks attached to 596 MAUs attached to the ports of a repeater." 597 ::= { dot3RpMauBasicGroup 2 } 599 rpJackEntry OBJECT-TYPE 600 SYNTAX RpJackEntry 601 MAX-ACCESS not-accessible 602 STATUS current 603 DESCRIPTION 604 "An entry in the table, containing information 605 about a particular jack." 606 INDEX { rpJackGroupIndex, 607 rpJackPortIndex, 608 rpJackMauIndex, 609 rpJackIndex } 610 ::= { rpJackTable 1 } 612 RpJackEntry ::= 613 SEQUENCE { 614 rpJackGroupIndex 615 Integer32, 616 rpJackPortIndex 617 Integer32, 618 rpJackMauIndex 619 Integer32, 620 rpJackIndex 621 Integer32, 622 rpJackType 623 INTEGER 624 } 626 rpJackGroupIndex OBJECT-TYPE 627 SYNTAX Integer32 (1..2147483647) 628 MAX-ACCESS read-only 629 STATUS current 630 DESCRIPTION 631 "This variable uniquely identifies the group 632 within containing the port attached to the MAU to 633 which the jack described by this entry is 634 connected. 636 Note: In practice, a group will generally be a 637 field-replaceable unit (i.e., module, card, or 638 board) that can fit in the physical system 639 enclosure, and the group number will correspond to 640 a number marked on the physical enclosure. 642 The group denoted by a particular value of this 643 object is the same as the group denoted by the 644 same value of rpMauGroupIndex." 645 ::= { rpJackEntry 1 } 647 rpJackPortIndex OBJECT-TYPE 648 SYNTAX Integer32 (1..2147483647) 649 MAX-ACCESS read-only 650 STATUS current 651 DESCRIPTION 652 "This variable uniquely identifies the repeater 653 port within group rpJackGroupIndex attached to the 654 MAU to which the jack described by this entry is 655 connected." 656 REFERENCE 657 "" 658 ::= { rpJackEntry 2 } 660 rpJackMauIndex OBJECT-TYPE 661 SYNTAX Integer32 (1..2147483647) 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "This variable uniquely identifies the MAU 666 connected to port rpJackPortIndex within group 667 rpJackGroupIndex to which the jack that is 668 described by this entry is connected." 669 REFERENCE 670 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 671 ::= { rpJackEntry 3 } 673 rpJackIndex OBJECT-TYPE 674 SYNTAX Integer32 (1..2147483647) 675 MAX-ACCESS read-only 676 STATUS current 677 DESCRIPTION 678 "This variable uniquely identifies the jack 679 described by this entry among within other jacks 680 attached to the MAU denoted by rpJackMauIndex." 681 ::= { rpJackEntry 4 } 683 rpJackType OBJECT-TYPE 684 SYNTAX INTEGER { 685 other(1), 686 rj45(2) 687 } 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "The jack connector type, as it appears on the 692 outside of the system." 693 ::= { rpJackEntry 5 } 695 -- 696 -- The Basic Interface MAU Table 697 -- 699 ifMauTable OBJECT-TYPE 700 SYNTAX SEQUENCE OF IfMauEntry 701 MAX-ACCESS not-accessible 702 STATUS current 703 DESCRIPTION 704 "Table of descriptive and status information about 705 MAU(s) attached to an interface." 706 ::= { dot3IfMauBasicGroup 1 } 708 ifMauEntry OBJECT-TYPE 709 SYNTAX IfMauEntry 710 MAX-ACCESS not-accessible 711 STATUS current 712 DESCRIPTION 713 "An entry in the table, containing information 714 about a single MAU." 715 INDEX { ifMauIfIndex, ifMauIndex } 716 ::= { ifMauTable 1 } 718 IfMauEntry ::= 719 SEQUENCE { 720 ifMauIfIndex 721 Integer32, 722 ifMauIndex 723 Integer32, 724 ifMauType 725 OBJECT IDENTIFIER, 726 ifMauStatus 727 INTEGER, 729 ifMauMediaAvail 730 INTEGER, 731 ifMauMediaAvailStateExits 732 Counter32, 733 ifMauJabberState 734 INTEGER, 735 ifMauJabberingStateEnters 736 Counter32, 737 ifMauFalseCarriers 738 Counter32, 739 ifMauTypeList 740 Integer32 741 } 743 ifMauIfIndex OBJECT-TYPE 744 SYNTAX Integer32 745 MAX-ACCESS read-only 746 STATUS current 747 DESCRIPTION 748 "This variable uniquely identifies the interface 749 to which the MAU described by this entry is 750 connected." 751 REFERENCE 752 "RFC 1213, ifIndex" 753 ::= { ifMauEntry 1 } 755 ifMauIndex OBJECT-TYPE 756 SYNTAX Integer32 (1..2147483647) 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "This variable uniquely identifies the MAU 761 connected to interface ifMauIfIndex that is 762 described by this entry." 763 REFERENCE 764 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 765 ::= { ifMauEntry 2 } 767 ifMauType OBJECT-TYPE 768 SYNTAX OBJECT IDENTIFIER 769 MAX-ACCESS read-only 770 STATUS current 771 DESCRIPTION 772 "This object identifies the 10 or 100 Mb/s 773 baseband MAU type. An initial set of MAU types 774 are defined above. The assignment of OBJECT 775 IDENTIFIERs to new types of MAUs is managed by the 776 IANA. If the MAU type is unknown, the object 777 identifier 779 unknownMauType OBJECT IDENTIFIER ::= { 0 0 } 781 is returned. Note that unknownMauType is a 782 syntactically valid object identifier, and any 783 conformant implementation of ASN.1 and the BER 784 must be able to generate and recognize this 785 value." 786 REFERENCE 787 "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." 788 ::= { ifMauEntry 3 } 790 ifMauStatus OBJECT-TYPE 791 SYNTAX INTEGER { 792 other(1), 793 unknown(2), 794 operational(3), 795 standby(4), 796 shutdown(5), 797 reset(6) 798 } 799 MAX-ACCESS read-write 800 STATUS current 801 DESCRIPTION 802 "The current state of the MAU. This object may be 803 implemented as a read-only object by those agents 804 and MAUs that do not implement software control of 805 the MAU state. Some agents may not support 806 setting the value of this object to some of the 807 enumerated values. 809 The value other(1) is returned if the MAU is in a 810 state other than one of the states 2 through 6. 812 The value unknown(2) is returned when the MAU's 813 true state is unknown; for example, when it is 814 being initialized. 816 A MAU in the operational(3) state is fully 817 functional, operates, and passes signals to its 818 attached DTE or repeater port in accordance to its 819 specification. 821 A MAU in standby(4) state forces DI and CI to idle 822 and the media transmitter to idle or fault, if 823 supported. Standby(4) mode only applies to link 824 type MAUs. The state of ifMauMediaAvail is 825 unaffected. 827 A MAU in shutdown(5) state assumes the same 828 condition on DI, CI, and the media transmitter as 829 though it were powered down or not connected. The 830 MAU may return other(1) value for the 831 ifMauJabberState and ifMauMediaAvail objects when 832 it is in this state. For an AUI, this state will 833 remove power from the AUI. 835 Setting this variable to the value reset(6) resets 836 the MAU in the same manner as a power-off, power- 837 on cycle of at least one-half second would. The 838 agent is not required to return the value reset 839 (6). 841 Setting this variable to the value operational(3), 842 standby(4), or shutdown(5) causes the MAU to 843 assume the respective state except that setting a 844 mixing-type MAU or an AUI to standby(4) will cause 845 the MAU to enter the shutdown state." 846 REFERENCE 847 "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 848 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, 849 acRESETMAU." 850 ::= { ifMauEntry 4 } 852 ifMauMediaAvail OBJECT-TYPE 853 SYNTAX INTEGER { 854 other(1), 855 unknown(2), 856 available(3), 857 notAvailable(4), 858 remoteFault(5), 859 invalidSignal(6), 860 remoteJabber(7), 861 remoteLinkLoss(8), 862 remoteTest(9) 863 } 865 MAX-ACCESS read-only 866 STATUS current 867 DESCRIPTION 868 "If the MAU is a link or fiber type (FOIRL, 869 10BASE-T, 10BASE-F) then this is equivalent to the 870 link test fail state/low light function. For an 871 AUI or a coax (including broadband) MAU this 872 indicates whether or not loopback is detected on 873 the DI circuit. The value of this attribute 874 persists between packets for MAU types AUI, 875 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. 877 The value other(1) is returned if the mediaAvail 878 state is not one of 2 through 6. 880 The value unknown(2) is returned when the MAU's 881 true state is unknown; for example, when it is 882 being initialized. At power-up or following a 883 reset, the value of this attribute will be unknown 884 for AUI, coax, and 10BASE-FP MAUs. For these MAUs 885 loopback will be tested on each transmission 886 during which no collision is detected. If DI is 887 receiving input when DO returns to IDL after a 888 transmission and there has been no collision 889 during the transmission then loopback will be 890 detected. The value of this attribute will only 891 change during non-collided transmissions for AUI, 892 coax, and 10BASE-FP MAUs. 894 For 100BASE-T4, 100BASE-TX and 100BASE-FX the 895 enumerations match the states within the 896 respective link integrity state diagrams, fig 23- 897 12 and 24-15 of sections 23 and 24 of [2]. Any 898 MAU which implements management of Auto- 899 Negotiation will map remote fault indication to 900 remote fault. 902 The value available(3) indicates that the link, 903 light, or loopback is normal. The value 904 notAvailable(4) indicates link loss, low light, or 905 no loopback. 907 The value remoteFault(5) indicates that a fault 908 has been detected at the remote end of the link. 909 This value applies to 10BASE-FB, 100BASE-T4 Far 910 End Fault Indication and non-specified remote 911 faults from a system running Auto-Negotiation. 912 The values remoteJabber(7), remoteLinkLoss(8), and 913 remoteTest(9) should be used instead of 914 remoteFault(5) where the reason for remote fault 915 is identified in the remote signaling protocol. 917 The value invalidSignal(6) indicates that an 918 invalid signal has been received from the other 919 end of the link. InvalidSignal(6) applies only to 920 MAUs of type 10BASE-FB. 922 Where an IEEE Std 802.3u-1995 clause 22 MII is 923 present, a logic one in the remote fault bit 924 (reference section 22.2.4.2.8 of that document) 925 maps to the value remoteFault(5), and a logic zero 926 in the link status bit (reference section 927 22.2.4.2.10 of that document) maps to the value 928 notAvailable(4). The value notAvailable(4) takes 929 precedence over the value remoteFault(5)." 930 REFERENCE 931 "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." 932 ::= { ifMauEntry 5 } 934 ifMauMediaAvailStateExits OBJECT-TYPE 935 SYNTAX Counter32 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "A count of the number of times that 940 ifMauMediaAvail for this MAU instance leaves the 941 state available(3)." 942 REFERENCE 943 "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." 944 ::= { ifMauEntry 6 } 946 ifMauJabberState OBJECT-TYPE 947 SYNTAX INTEGER { 948 other(1), 949 unknown(2), 950 noJabber(3), 951 jabbering(4) 952 } 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "The value other(1) is returned if the jabber 957 state is not 2, 3, or 4. The agent must always 958 return other(1) for MAU type dot3MauTypeAUI. 960 The value unknown(2) is returned when the MAU's 961 true state is unknown; for example, when it is 962 being initialized. 964 If the MAU is not jabbering the agent returns 965 noJabber(3). This is the 'normal' state. 967 If the MAU is in jabber state the agent returns 968 the jabbering(4) value." 969 REFERENCE 970 "[IEEE 802.3 Mgt], 30.5.1.1.6, 971 aJabber.jabberFlag." 972 ::= { ifMauEntry 7 } 974 ifMauJabberingStateEnters OBJECT-TYPE 975 SYNTAX Counter32 976 MAX-ACCESS read-only 977 STATUS current 978 DESCRIPTION 979 "A count of the number of times that 980 mauJabberState for this MAU instance enters the 981 state jabbering(4). For MAUs of type 982 dot3MauTypeAUI, dot3MauType100BaseT4, 983 dot3MauType100BaseTX, and dot3MauType100BaseFX, 984 this counter will always indicate zero." 985 REFERENCE 986 "[IEEE 802.3 Mgt], 30.5.1.1.6, 987 aJabber.jabberCounter." 988 ::= { ifMauEntry 8 } 990 ifMauFalseCarriers OBJECT-TYPE 991 SYNTAX Counter32 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "A count of the number of false carrier events 996 during IDLE in 100BASE-X links. This counter does 997 not increment at the symbol rate. It can 998 increment after a valid carrier completion at a 999 maximum rate of once per 100 ms until the next 1000 carrier event. 1002 This counter increments only for MAUs of type 1003 dot3MauType100BaseT4, dot3MauType100BaseTX, and 1004 dot3MauType100BaseFX. For all other MAU types, 1005 this counter will always indicate zero. 1007 The approximate minimum time for rollover of this 1008 counter is 7.4 hours." 1009 REFERENCE 1010 "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." 1011 ::= { ifMauEntry 9 } 1013 ifMauTypeList OBJECT-TYPE 1014 SYNTAX Integer32 1015 MAX-ACCESS read-only 1016 STATUS current 1017 DESCRIPTION 1018 "A value that uniquely identifies the set of 1019 possible IEEE 802.3 types that the MAU could be. 1020 The value is a sum which initially takes the value 1021 zero. Then, for each type capability of this MAU, 1022 2 raised to the power noted below is added to the 1023 sum. For example, a MAU which has the capability 1024 to be only 10BASE-T would have a value of 512 1025 (2**9). In contrast, a MAU which supports both 1026 10Base-T and 100BASE-TX would have a value of 1536 1027 ((2**9) + (2**10)). 1029 The powers of 2 assigned to the capabilities are 1030 these: 1032 Power Capability 1033 1 AUI 1034 2 10BASE-5 1035 3 FOIRL 1036 4 10BASE-2 1037 5 10BASE-T 1038 6 10BASE-FP 1039 7 10BASE-FB 1040 8 10BASE-FL 1041 9 10BROAD36 1042 10 100BASE-T4 1043 11 100BASE-TX 1044 12 100BASE-FX 1046 If auto-negotiation is present on the jack to 1047 which this MAU is attached, this attribute will 1048 map to the ifMauAutoNegCapability." 1049 ::= { ifMauEntry 10 } 1051 -- The ifJackTable applies to MAUs attached to interfaces 1052 -- which have one or more external jacks (connectors). 1054 ifJackTable OBJECT-TYPE 1055 SYNTAX SEQUENCE OF IfJackEntry 1056 MAX-ACCESS not-accessible 1057 STATUS current 1058 DESCRIPTION 1059 "Information about the external jacks attached to 1060 MAUs attached to an interface." 1061 ::= { dot3IfMauBasicGroup 2 } 1063 ifJackEntry OBJECT-TYPE 1064 SYNTAX IfJackEntry 1065 MAX-ACCESS not-accessible 1066 STATUS current 1067 DESCRIPTION 1068 "An entry in the table, containing information 1069 about a particular jack." 1070 INDEX { ifJackIfIndex, 1071 ifJackMauIndex, 1072 ifJackIndex } 1073 ::= { ifJackTable 1 } 1075 IfJackEntry ::= 1076 SEQUENCE { 1077 ifJackIfIndex 1078 Integer32, 1079 ifJackMauIndex 1080 Integer32, 1081 ifJackIndex 1082 Integer32, 1083 ifJackType 1084 INTEGER 1085 } 1087 ifJackIfIndex OBJECT-TYPE 1088 SYNTAX Integer32 1089 MAX-ACCESS read-only 1090 STATUS current 1091 DESCRIPTION 1092 "This variable uniquely identifies the interface 1093 attached to the MAU to which the jack described by 1094 this entry is connected. 1096 The interface denoted by a particular value of 1097 this object is the same as the group denoted by 1098 the same value of ifMauIfIndex." 1099 ::= { ifJackEntry 1 } 1101 ifJackMauIndex OBJECT-TYPE 1102 SYNTAX Integer32 (1..2147483647) 1103 MAX-ACCESS read-only 1104 STATUS current 1105 DESCRIPTION 1106 "This variable uniquely identifies the MAU 1107 connected to port ifJackIfIndex to which the jack 1108 that is described by this entry is connected." 1109 REFERENCE 1110 "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." 1111 ::= { ifJackEntry 2 } 1113 ifJackIndex OBJECT-TYPE 1114 SYNTAX Integer32 (1..2147483647) 1115 MAX-ACCESS read-only 1116 STATUS current 1117 DESCRIPTION 1118 "This variable uniquely identifies the jack 1119 described by this entry among within other jacks 1120 attached to the MAU denoted by ifJackMauIndex." 1121 ::= { ifJackEntry 3 } 1123 ifJackType OBJECT-TYPE 1124 SYNTAX INTEGER { 1125 other(1), 1126 rj45(2) 1127 } 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "The jack connector type, as it appears on the 1132 outside of the system." 1133 ::= { ifJackEntry 4 } 1135 -- The ifMauAutoNegTable applies to systems in which 1136 -- auto-negotiation is supported on one or more MAUs 1137 -- attached to interfaces. 1139 ifMauAutoNegTable OBJECT-TYPE 1140 SYNTAX SEQUENCE OF IfMauAutoNegEntry 1141 MAX-ACCESS not-accessible 1142 STATUS current 1143 DESCRIPTION 1144 "Configuration and status objects for the auto- 1145 negotiation function of MAUs attached to 1146 interfaces." 1147 ::= { dot3IfMauAutoNegGroup 1 } 1149 ifMauAutoNegEntry OBJECT-TYPE 1150 SYNTAX IfMauAutoNegEntry 1151 MAX-ACCESS not-accessible 1152 STATUS current 1153 DESCRIPTION 1154 "An entry in the table, containing configuration 1155 and status information for the auto-negotiation 1156 function of a particular MAU." 1157 AUGMENTS { ifMauEntry } 1158 ::= { ifMauAutoNegTable 1 } 1160 IfMauAutoNegEntry ::= 1161 SEQUENCE { 1162 ifMauAutoNegAdminStatus 1163 INTEGER, 1164 ifMauAutoNegRemoteSignaling 1165 INTEGER, 1166 ifMauAutoNegConfig 1167 INTEGER, 1168 ifMauAutoNegCapability 1169 Integer32, 1170 ifMauAutoNegCapAdvertised 1171 Integer32, 1172 ifMauAutoNegCapReceived 1173 Integer32, 1174 ifMauAutoNegTechnologyInUse 1175 INTEGER, 1176 ifMauAutoNegRestart 1177 INTEGER 1179 } 1181 ifMauAutoNegAdminStatus OBJECT-TYPE 1182 SYNTAX INTEGER { 1183 enabled(1), 1184 disabled(2) 1185 } 1186 MAX-ACCESS read-write 1187 STATUS current 1188 DESCRIPTION 1189 "Setting this object to enabled(1) will cause the 1190 interface which has the auto-negotiation signaling 1191 ability to be enabled. If disabled then the 1192 interface will act as it would if it had no auto- 1193 negotiation signaling. 1195 Under these conditions, an IEEE 802.3 MAU will 1196 immediately be forced to the states indicated by a 1197 write to the object rpMauType or ifMauType. 1198 [Ed.--This doesn't allow for half vs. full 1199 duplex.]" 1200 REFERENCE 1201 "[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState 1202 and 30.6.1.2.2, acAutoNegAdminControl." 1203 ::= { ifMauAutoNegEntry 1 } 1205 ifMauAutoNegRemoteSignaling OBJECT-TYPE 1206 SYNTAX INTEGER { 1207 detected(1), 1208 notdetected(2) 1209 } 1210 MAX-ACCESS read-only 1211 STATUS current 1212 DESCRIPTION 1213 "A value indicating whether the remote end of the 1214 link is using auto-negotiation signaling. It takes 1215 the value detected(1) if and only if, during the 1216 previous link negotiation, FLP Bursts were 1217 received." 1218 REFERENCE 1219 "[IEEE 802.3 Mgt], 30.6.1.1.3, 1220 aAutoNegRemoteSignaling." 1221 ::= { ifMauAutoNegEntry 2 } 1223 ifMauAutoNegConfig OBJECT-TYPE 1224 SYNTAX INTEGER { 1225 other(1), 1226 configuring(2), 1227 complete(3), 1228 disabled(4), 1229 parallelDetectFail(5) 1230 } 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "A value indicating the current status of the 1235 auto-negotiation process. The enumeration 1236 parallelDetectFail(5) maps to a failure in 1237 parallel detection as defined in 28.2.3.1 of [IEEE 1238 802.3 Std]." 1239 REFERENCE 1240 "[IEEE 802.3 Mgt], 30.6.1.1.4, 1241 aAutoNegAutoConfig." 1242 ::= { ifMauAutoNegEntry 4 } 1244 ifMauAutoNegCapability OBJECT-TYPE 1245 SYNTAX Integer32 1246 MAX-ACCESS read-only 1247 STATUS current 1248 DESCRIPTION 1249 "A value that uniquely identifies the set of 1250 capabilities of the local auto-negotiation entity. 1251 The value is a sum which initially takes the value 1252 zero. Then, for each capability of this 1253 interface, 2 raised to the power noted below is 1254 added to the sum. For example, an interface which 1255 has the capability to support only 100Base-TX 1256 would have a value of 512 (2**9). In contrast, an 1257 interface which supports both 100Base-TX and 1258 100Base-TX Full Duplex would have a value of 1536 1259 ((2**9) + (2**10)). 1261 The powers of 2 assigned to the capabilities are 1262 these: 1264 Power Capability 1265 1 other 1266 2 reserved 1267 3 10BASE-T 1268 4 10BASE-T Full Duplex 1269 5 10BASE-FL 1270 6 10BASE-FL Full Duplex 1271 7 10BASE-FB 1272 8 10BASE-FB Full Duplex 1273 9 100BASE-TX 1274 10 100BASE-TX Full Duplex 1275 11 100BASE-FX 1276 12 100BASE-FX Full Duplex 1277 13 100BASE-T4 1279 For IEEE 802.3 MAUs, the half- and full-duplex 1280 value pairs each map to a single MAU type. For 1281 example, 10BASE-T and 10BASE-T Full Duplex each 1282 use a MAU type of dot3MauType10BaseT. 1284 Note that interfaces that support this MIB may 1285 have capabilities that extend beyond the scope of 1286 this MIB." 1287 REFERENCE 1288 "[IEEE 802.3 Mgt], 30.6.1.1.5, 1289 aAutoNegLocalTechnologyAbility." 1290 ::= { ifMauAutoNegEntry 5 } 1292 ifMauAutoNegCapAdvertised OBJECT-TYPE 1293 SYNTAX Integer32 1294 MAX-ACCESS read-write 1295 STATUS current 1296 DESCRIPTION 1297 "A value that uniquely identifies the set of 1298 capabilities advertised by the local auto- 1299 negotiation entity. Refer to 1300 ifMauAutoNegCapability for a description of the 1301 possible values of this object. 1303 Capabilities in this object that are not available 1304 in ifMauAutoNegCapability cannot be enabled." 1305 REFERENCE 1306 "[IEEE 802.3 Mgt], 30.6.1.1.6, 1307 aAutoNegAdvertisedTechnologyAbility." 1308 ::= { ifMauAutoNegEntry 6 } 1310 ifMauAutoNegCapReceived OBJECT-TYPE 1311 SYNTAX Integer32 1312 MAX-ACCESS read-only 1313 STATUS current 1314 DESCRIPTION 1315 "A value that uniquely identifies the set of 1316 capabilities received from the remote auto- 1317 negotiation entity. Refer to 1318 ifMauAutoNegCapability for a description of the 1319 possible values of this object. 1321 Note that interfaces that support this MIB may be 1322 attached to remote auto-negotiation entities which 1323 have capabilities beyond the scope of this MIB." 1324 REFERENCE 1325 "[IEEE 802.3 Mgt], 30.6.1.1.7, 1326 aAutoNegReceivedTechnologyAbility." 1327 ::= { ifMauAutoNegEntry 7 } 1329 ifMauAutoNegTechnologyInUse OBJECT-TYPE 1330 SYNTAX INTEGER { 1331 other(1), 1332 reserved(2), 1333 t10BASET(3), 1334 t10BASETFD(4), 1335 t10BASEFL(5), 1336 t10BASEFLFD(6), 1337 t10BASEFB(7), 1338 t10BASEFBFD(8), 1339 t100BASETX(9), 1340 t100BASETXFD(10), 1341 t100BASEFX(11), 1342 t100BASEFXFD(12), 1343 t100BASET4(13) 1344 } 1345 MAX-ACCESS read-only 1346 STATUS current 1347 DESCRIPTION 1348 "The value of this object identifies the 1349 technology currently in use on the link to which 1350 this MAU is attached. This value may be a result 1351 of auto- negotiation on the link. If auto- 1352 negotiation is disabled and the MAU is an IEEE 1353 802.3 MAU, this object will change to reflect the 1354 result of a write to the object rpMauType or 1355 ifMauType." 1356 ::= { ifMauAutoNegEntry 8 } 1358 ifMauAutoNegRestart OBJECT-TYPE 1359 SYNTAX INTEGER { 1360 restart(1), 1361 norestart(2) 1362 } 1363 MAX-ACCESS read-write 1364 STATUS current 1365 DESCRIPTION 1366 "If the value of this object is set to restart(1) 1367 then this will force auto-negotiation to begin 1368 link renegotiation. If auto-negotiation signaling 1369 is disabled, a write to this object has no effect. 1371 Setting the value of this object to norestart(2) 1372 has no effect." 1373 REFERENCE 1374 "[IEEE 802.3 Mgt], 30.6.1.2.1, 1375 acAutoNegRestartAutoConfig." 1376 ::= { ifMauAutoNegEntry 9 } 1378 broadMauBasicTable OBJECT-TYPE 1379 SYNTAX SEQUENCE OF BroadMauBasicEntry 1380 MAX-ACCESS not-accessible 1381 STATUS current 1382 DESCRIPTION 1383 "Table of descriptive and status information about 1384 the broadband MAUs connected to interfaces." 1385 ::= { dot3BroadMauBasicGroup 1 } 1387 broadMauBasicEntry OBJECT-TYPE 1388 SYNTAX BroadMauBasicEntry 1389 MAX-ACCESS not-accessible 1390 STATUS current 1391 DESCRIPTION 1392 "An entry in the table, containing information 1393 about a single broadband MAU." 1394 INDEX { broadMauIfIndex, broadMauIndex } 1395 ::= { broadMauBasicTable 1 } 1397 BroadMauBasicEntry ::= 1398 SEQUENCE { 1399 broadMauIfIndex 1400 Integer32, 1401 broadMauIndex 1402 Integer32, 1403 broadMauXmtRcvSplitType 1404 INTEGER, 1405 broadMauXmtCarrierFreq 1406 Integer32, 1407 broadMauTranslationFreq 1408 Integer32 1409 } 1411 broadMauIfIndex OBJECT-TYPE 1412 SYNTAX Integer32 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "This variable uniquely identifies the interface 1417 to which the MAU described by this entry is 1418 connected." 1419 REFERENCE 1420 "Reference RFC 1213, ifIndex." 1421 ::= { broadMauBasicEntry 1 } 1423 broadMauIndex OBJECT-TYPE 1424 SYNTAX Integer32 (1..2147483647) 1425 MAX-ACCESS read-only 1426 STATUS current 1427 DESCRIPTION 1428 "This variable uniquely identifies the MAU 1429 connected to interface broadMauIfIndex that is 1430 described by this entry." 1431 REFERENCE 1432 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID." 1433 ::= { broadMauBasicEntry 2 } 1435 broadMauXmtRcvSplitType OBJECT-TYPE 1436 SYNTAX INTEGER { 1437 other(1), 1438 single(2), 1439 dual(3) 1440 } 1441 MAX-ACCESS read-only 1442 STATUS current 1443 DESCRIPTION 1444 "This object indicates the type of frequency 1445 multiplexing/cabling system used to separate the 1446 transmit and receive paths for the 10BROAD36 MAU. 1448 The value other(1) is returned if the split type 1449 is not either single or dual. 1451 The value single(2) indicates a single cable 1452 system. The value dual(3) indicates a dual cable 1453 system, offset normally zero." 1454 REFERENCE 1455 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1456 aBbMAUXmitRcvSplitType." 1457 ::= { broadMauBasicEntry 3 } 1459 broadMauXmtCarrierFreq OBJECT-TYPE 1460 SYNTAX Integer32 1461 MAX-ACCESS read-only 1462 STATUS current 1463 DESCRIPTION 1464 "This variable indicates the transmit carrier 1465 frequency of the 10BROAD36 MAU in MHz/4; that is, 1466 in units of 250 kHz." 1467 REFERENCE 1468 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1469 aBroadbandFrequencies.xmitCarrierFrequency." 1470 ::= { broadMauBasicEntry 4 } 1472 broadMauTranslationFreq OBJECT-TYPE 1473 SYNTAX Integer32 1474 MAX-ACCESS read-only 1475 STATUS current 1476 DESCRIPTION 1477 "This variable indicates the translation offset 1478 frequency of the 10BROAD36 MAU in MHz/4; that is, 1479 in units of 250 kHz." 1480 REFERENCE 1481 "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, 1482 aBroadbandFrequencies.translationFrequency." 1483 ::= { broadMauBasicEntry 5 } 1485 -- Notifications for use by 802.3 MAUs 1487 rpMauJabberTrap NOTIFICATION-TYPE 1488 OBJECTS { rpMauJabberState } 1489 STATUS current 1490 DESCRIPTION 1491 "This trap is sent whenever a managed repeater MAU 1492 enters the jabber state. 1494 The agent must throttle the generation of 1495 consecutive rpMauJabberTraps so that there is at 1496 least a five-second gap between them." 1497 REFERENCE 1498 "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1499 notification." 1500 ::= { snmpDot3MauMgt 0 1 } 1502 ifMauJabberTrap NOTIFICATION-TYPE 1503 OBJECTS { ifMauJabberState } 1504 STATUS current 1505 DESCRIPTION 1506 "This trap is sent whenever a managed interface 1507 MAU enters the jabber state. 1509 The agent must throttle the generation of 1510 consecutive ifMauJabberTraps so that there is at 1511 least a five-second gap between them." 1512 REFERENCE 1513 "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber 1514 notification." 1515 ::= { snmpDot3MauMgt 0 2 } 1517 -- Conformance information 1519 mauModConf 1520 OBJECT IDENTIFIER ::= { mauMod 1 } 1521 mauModCompls 1522 OBJECT IDENTIFIER ::= { mauModConf 1 } 1523 mauModObjGrps 1524 OBJECT IDENTIFIER ::= { mauModConf 2 } 1525 mauModNotGrps 1526 OBJECT IDENTIFIER ::= { mauModConf 3 } 1528 -- Object groups 1530 mauRpGrpBasic OBJECT-GROUP 1531 OBJECTS { rpMauGroupIndex, 1532 rpMauPortIndex, 1533 rpMauIndex, 1534 rpMauType, 1535 rpMauStatus, 1536 rpMauMediaAvail, 1537 rpMauMediaAvailStateExits, 1538 rpMauJabberState, 1539 rpMauJabberingStateEnters } 1540 STATUS current 1541 DESCRIPTION 1542 "Basic conformance group for MAUs attached to 1543 repeater ports. This group is also the 1544 conformance specification for RFC 1515 1545 implementations." 1546 ::= { mauModObjGrps 1 } 1548 mauRpGrpExtended OBJECT-GROUP 1549 OBJECTS { rpMauFalseCarriers, 1551 rpJackGroupIndex, 1552 rpJackPortIndex, 1553 rpJackMauIndex, 1554 rpJackIndex, 1555 rpJackType } 1556 STATUS current 1557 DESCRIPTION 1558 "Conformance group for MAUs attached to 1559 repeater ports with extended management 1560 (including 100 Mb/s and jack management)." 1561 ::= { mauModObjGrps 2 } 1563 mauIfGrpBasic OBJECT-GROUP 1564 OBJECTS { ifMauIfIndex, 1565 ifMauIndex, 1566 ifMauType, 1567 ifMauStatus, 1568 ifMauMediaAvail, 1569 ifMauMediaAvailStateExits, 1570 ifMauJabberState, 1571 ifMauJabberingStateEnters } 1572 STATUS current 1573 DESCRIPTION 1574 "Basic conformance group for MAUs attached to 1575 interfaces. This group also provides a 1576 conformance specification for RFC 1515 1577 implementations." 1578 ::= { mauModObjGrps 3 } 1580 mauIfGrpExtended OBJECT-GROUP 1581 OBJECTS { ifMauFalseCarriers, 1582 ifMauTypeList, 1584 ifJackIfIndex, 1585 ifJackMauIndex, 1586 ifJackIndex, 1587 ifJackType } 1588 STATUS current 1589 DESCRIPTION 1590 "Conformance group for MAUs attached 1591 to interfaces with extended management 1592 (including 100 Mb/s and jack management)." 1593 ::= { mauModObjGrps 4 } 1595 mauIfGrpAutoNeg OBJECT-GROUP 1596 OBJECTS { ifMauAutoNegAdminStatus, 1597 ifMauAutoNegRemoteSignaling, 1598 ifMauAutoNegConfig, 1599 ifMauAutoNegCapability, 1600 ifMauAutoNegCapAdvertised, 1601 ifMauAutoNegCapReceived, 1602 ifMauAutoNegTechnologyInUse, 1603 ifMauAutoNegRestart } 1604 STATUS current 1605 DESCRIPTION 1606 "Conformance group for MAUs attached to 1607 interfaces with managed auto-negotiation." 1608 ::= { mauModObjGrps 5 } 1610 mauBroadBasic OBJECT-GROUP 1611 OBJECTS { broadMauIfIndex, 1612 broadMauIndex, 1613 broadMauXmtRcvSplitType, 1614 broadMauXmtCarrierFreq, 1615 broadMauTranslationFreq } 1616 STATUS current 1617 DESCRIPTION 1618 "Conformance group for broadband MAUs 1619 attached to interfaces. This group 1620 provides a conformance specification 1621 for RFC 1515 implementations." 1622 ::= { mauModObjGrps 6 } 1624 -- Notification groups 1626 -- ?? later 1628 -- Compliances 1630 mauModRpCompl MODULE-COMPLIANCE 1631 STATUS current 1632 DESCRIPTION 1633 "Compliance for MAUs attached to repeater ports." 1635 MODULE -- this module 1636 MANDATORY-GROUPS { mauRpGrpBasic } 1638 GROUP mauRpGrpExtended 1639 DESCRIPTION 1640 "Implementation of this optional group is 1641 recommended for MAUs which have 100Mb/s 1642 capability and/or more than one attached 1643 external jack." 1645 ::= { mauModCompls 1 } 1647 mauModIfCompl MODULE-COMPLIANCE 1648 STATUS current 1649 DESCRIPTION 1650 "Compliance for MAUs attached to interfaces." 1652 MODULE -- this module 1653 MANDATORY-GROUPS { mauIfGrpBasic } 1655 GROUP mauIfGrpExtended 1656 DESCRIPTION 1657 "Implementation of this optional group is 1658 recommended for MAUs which have 100Mb/s 1659 capability and/or more than one attached 1660 external jack." 1662 GROUP mauIfGrpAutoNeg 1663 DESCRIPTION 1664 "Implementation of this optional group 1665 is recommended for MAUs which support 1666 managed auto-negotiation." 1668 GROUP mauBroadBasic 1669 DESCRIPTION 1670 "Implementation of this group is 1671 mandatory for broadband MAUs." 1673 ::= { mauModCompls 2 } 1675 END 1676 4. References 1678 [1] IEEE 802.3/ISO 8802-3 Information processing systems - 1679 Local area networks - Part 3: Carrier sense multiple 1680 access with collision detection (CSMA/CD) access method 1681 and physical layer specifications, 1993. 1683 [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium 1684 Attachment Units and Repeater for 100 Mb/s Operation, 1685 Type 100BASE-T," Sections 21 through 29, Supplement to 1686 IEEE Std 802.3, October 26, 1995. 1688 [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, 1689 Supplement to IEEE Std 802.3, October 26, 1995. 1691 [4] Romascanu, D., and K. de Graaf, "Definitions of Managed 1692 Objects for IEEE 802.3 Repeater Devices", February 1996.