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