Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)<draft-ietf-hubmib-mau-mib-00.txt> 27 November 199514 February 1996 <draft-ietf-hubmib-mau-mib-01.txt> Dan RomascanuLANNET Data Communications,Madge Networks (Israel) Ltd. dan@lannet.com Kathryn de Graaf 3Com Corporationkdegraaf@chipcom.comkdegraaf@isd.3com.com Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet- Drafts as reference material or to cite them other than as a "work in progress". To learn the current status of any Internet-Draft, please check the "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). Abstract This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in theInternetsInternet community. In particular, it defines objects for managing 10 and 100 Mb/second Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, "10 & 100 Mb/s Management," October 26, 1995. This memo does not specify a standard for the Internet community. 1. The SNMPv2 Network Management Framework The SNMPv2 Network Management Framework consists offourseveral major components. Theyare:include: o RFC14421902 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. o STD 17, RFC 1213 defines MIB-II, the core set of managed objects for the Internet suite of protocols. o RFC1445 which defines the administrative and other architectural aspects of the framework. o RFC 14481905 which defines the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. 1.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. 2. Overview Instances of these object types represent attributes of an IEEE 802.3 MAU. Several types of MAUs are defined in the IEEE 802.3 CSMA/CD standard [1] and [2]. These MAUs may be connected to IEEE 802.3 repeaters or to 802.3 (Ethernet-like) interfaces. For convenience this document refers to these devices as "repeater MAUs" and "interface MAUs." The definitions presented here are based on Section 30.5, "Layer Management for 10 & 100 Mb/s Medium Attachment Units (MAUs)", and Annex 30A, "GDMO Specifications for 802.3 managed objects" of IEEE Std 802.3u-1995. That specification includes definitions for both 10Mb/s and 100Mb/s devices, and is essentially a superset of the 10Mb/s definitions given by IEEE 802.3 Section 20. This specification is intended to serve the same purpose: to provide for management of both 10Mb/s and 100Mb/s MAUs.MAUs are components2.1. Relationship to Other MIBs It is assumed thatare often located inside a larger system, and are not always externally visiblean agent implementing this MIB will also implement (at least) the 'system' group defined in MIB-II. The following sections identify other MIBs that such an agent should implement. 2.1.1. Relationship toa network administrator.the 'interfaces' group Theexternal connectionsections ofa MAU is generally a jackthis document that define interface MAU- related objects specify an extension towhich a network cable can be attached.the 'interfaces' group of MIB-II. An agent implementing these interface-MAU related objects must also implement the 'interfaces' group of MIB-II. Theinternal connectionvalue ofa MAU can be,the ifMauIfIndex object is the same asexplained above, a repeater port or an interface. In some systems, this internal connectivity may be configurable. Additionally,theintroductionvalue ofauto-negotiation functionality in'ifIndex' used to instantiate theIEEE 802.3 specification allows for a connection which can,interface toa certain degree, configure or reconfigure itself during operation. This MIB includeswhich the given MAU is connected. It is expected that an agent implementing the interface-MAU related objectsfor jack configuration and statusin this MIB will also implement the Ethernet- like Interfaces MIB, RFC 1650. (Note that repeater ports areintendednot represented as interfaces in the sense of MIB-II's 'interfaces' group.) 2.1.2. Relationship toallowthenetwork management software802.3 Repeater MIB The section of this document that defines repeater MAU-related objects specifies an extension tomodel and reporttheconnectivity between802.3 Repeater MIB defined in [4]. An agent implementing these repeater-MAU related objects must also implement theexternal jacks,802.3 Repeater MIB. The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to instantiate a repeater MAU variable shall be theMAUs,same as the values of 'rptrPortGroupIndex' and 'rptrPortIndex' used to instantiate theother components (repeater ports or interfaces)port to which the given MAU is connected. 2.2. Management of Internal MAUs In some situations, a MAU can be "internal" -- i.e., its functionality is implemented entirely withinsuchasystem, including both administrative configuration and auto- negotiation. This model assumesdevice. For example, aone-to-one relationship between jacksmanaged repeater may contain an internal repeater- MAU and/or an internal interface-MAU through which management communications originating on one of the repeater's external ports pass in order to reach the management agent associated with the repeater. Such internal MAUs may or may not be managed. If they are managed, objects describing their attributes should appear in the appropriate MIB group -- dot3RpMauBasicGroup for internal repeater-MAUs andMAUs.dot3IfMauBasicGroup for internal interface-MAUs. 3. Definitions MAU-MIB DEFINITIONS ::= BEGIN IMPORTS experimental, Counter32, Integer32,Gauge32, Counter64,OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE FROM SNMPv2-SMITimeStamp, DisplayString, MacAddress, TEXTUAL-CONVENTION, RowStatus FROM SNMPv2-TCOBJECT-GROUP,MODULE-COMPLIANCE, NOTIFICATION-GROUP,MODULE-COMPLIANCE FROM SNMPv2-CONF mib-2 FROM RFC1213-MIB; mauMod MODULE-IDENTITY LAST-UPDATED"9511270000Z""9602140000Z" ORGANIZATION "IETF HUB MIB Working Group" CONTACT-INFO "WG E-mail:hubmib@baynetworks.comhubmib@hprnd.rose.hp.com Chair: Dan Romascanu Postal:LANNET Data Communications,Madge Networks (Israel) Ltd. Atidim Technology Park, Bldg. 3 Tel Aviv 61131, Israel Tel: 972-3-6458414, 6458458 Fax: 972-3-6487146 E-mail: dan@lannet.com Editor: Kathryn de Graaf Postal: 3Com Corporation 118 Turnpike Rd. Southborough, MA 01772 USA Tel: (508)229-1627 Fax: (508)490-5882 E-mail:kdegraaf@chipcom.com"kdegraaf@isd.3com.com" DESCRIPTION "Management information for 802.3 MAUs. The following references are used throughout this MIB module: [IEEE 802.3 Std] refers to IEEE 802.3/ISO 8802-3 Information processing systems - Local area networks - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications (1993), and to IEEE Std 802.3u-1995, Supplement to IEEE Std 802.3, clauses 22 through 29. [IEEE 802.3 Mgt] refers to IEEE 802.3u-1995, - 10 Mb/s & 100 Mb/s Management, Section 30 - Supplement to IEEE Std 802.3." ::= { snmpDot3MauMgt 6 } snmpDot3MauMgt OBJECT IDENTIFIER ::= { experimental x }-- the following subtrees are deprecateddot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 }dot3MauBasicGroupdot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt75 } -- object identifiers for MAU types -- (see rpMauType and ifMauType for usage) dot3MauType OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } dot3MauTypeAUI -- no internal MAU, view from AUI OBJECT IDENTIFIER ::= { dot3MauType 1 } dot3MauType10Base5 -- thick coax MAU (per 802.3 section 8) OBJECT IDENTIFIER ::= { dot3MauType 2 } dot3MauTypeFoirl -- FOIRL MAU (per 802.3 section 9.9) OBJECT IDENTIFIER ::= { dot3MauType 3 } dot3MauType10Base2 -- thin coax MAU (per 802.3 section 10) OBJECT IDENTIFIER ::= { dot3MauType 4 } dot3MauType10BaseT -- UTP MAU (per 802.3 section 14) OBJECT IDENTIFIER ::= { dot3MauType 5 } dot3MauType10BaseFP -- passive fiber MAU (per 802.3 section 16) OBJECT IDENTIFIER ::= { dot3MauType 6 } dot3MauType10BaseFB -- sync fiber MAU (per 802.3 section 17) OBJECT IDENTIFIER ::= { dot3MauType 7 } dot3MauType10BaseFL -- async fiber MAU (per 802.3 section 18) OBJECT IDENTIFIER ::= { dot3MauType 8 } dot3MauType10Broad36 -- broadband DTE MAU (per 802.3 section 11) -- note that 10BROAD36 MAUs can be attached to interfaces but -- not to repeaters OBJECT IDENTIFIER ::= { dot3MauType 9 } -- new for 100 MB/s: dot3MauType100BaseT4 -- 4 pair categ. 3 UTP (per 802.3 section 23) OBJECT IDENTIFIER ::= { dot3MauType 10 } dot3MauType100BaseTX -- 2 pair categ. 5 UTP (per 802.3 section 25) OBJECT IDENTIFIER ::= { dot3MauType 11 } dot3MauType100BaseFX -- X fiber over PMT (per 802.3 section 26) OBJECT IDENTIFIER ::= { dot3MauType 12 } -- -- The Basic Repeater MAU Table --mauTablerpMauTable OBJECT-TYPE SYNTAX SEQUENCE OFMauEntryRpMauEntry MAX-ACCESS not-accessible STATUSmandatorycurrent DESCRIPTION "Table of descriptive and status information about themanagedMAU(s)in this system."attached to the ports of a repeater." ::= {mauBasicGroupdot3RpMauBasicGroup 1 }mauEntryrpMauEntry OBJECT-TYPE SYNTAXMauEntryRpMauEntry MAX-ACCESS not-accessible STATUSmandatorycurrent DESCRIPTION "An entry in the table, containing information about a single MAU." INDEX {mauGroupIndex, mauIndexrpMauGroupIndex, rpMauPortIndex, rpMauIndex } ::= {mauTablerpMauTable 1 }MauEntryRpMauEntry ::= SEQUENCE {mauGroupIndexrpMauGroupIndex Integer32, rpMauPortIndex Integer32,mauIndexrpMauIndex Integer32,mauTyperpMauType OBJECT IDENTIFIER,mauTypeList Integer32, mauStatusrpMauStatus INTEGER,mauMediaAvailrpMauMediaAvail INTEGER,mauMediaAvailStateExitsrpMauMediaAvailStateExits Counter32,mauJabberStaterpMauJabberState INTEGER,mauJabberingStateEntersrpMauJabberingStateEnters Counter32,mauFalseCarriersrpMauFalseCarriers Counter32 }mauGroupIndexrpMauGroupIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "This variable uniquely identifies the group containing the port to which the MAU described by thisentry.entry is connected. Note: In practice, a group will generally be a field-replaceable unit (i.e., module, card, or board) that can fit in the physical system enclosure, and the group number will correspond to a number marked on the physical enclosure.For MAUs attached to repeaters, theThe group denoted by a particular value of this object is the same as the group denoted by the same value of rptrGroupIndex." ::= {mauEntryrpMauEntry 1 }mauIndexrpMauPortIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "This variable uniquely identifies the repeater port within group rpMauGroupIndex to which the MAU described by this entry is connected." REFERENCE "" ::= { rpMauEntry 2 } rpMauIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the MAU connected to port rpMauPortIndex within groupmauGroupIndexrpMauGroupIndex that is described by this entry." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." ::= {mauEntry 2rpMauEntry 3 }mauTyperpMauType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "This object identifies the 10 or 100 Mb/s baseband MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." ::= {mauEntry 3rpMauEntry 4 }mauTypeListrpMauStatus OBJECT-TYPE SYNTAXInteger32INTEGER { other(1), unknown(2), operational(3), standby(4), shutdown(5), reset(6) } MAX-ACCESSread-onlyread-write STATUSmandatorycurrent DESCRIPTION"A value that uniquely identifies the set"The current state ofpossible IEEE 802.3 typesthe MAU. This object may be implemented as a read-only object by those agents and MAUs that do not implement software control of the MAUcould be. The value is a sum which initially takesstate. Some agents may not support setting the valuezero. Then, for each type capabilityof thisMAU, 2 raisedobject to some of thepower noted belowenumerated values. The value other(1) isadded toreturned if thesum. For example, aMAUwhich has the capability to be only 10BASE-T would have a value of 512 (2**9). In contrast, a MAU which supports both 10Base-T and 100BASE-TX would have a value of 1536 ((2**9) + (2**10)). The powers of 2 assigned to the capabilities are these: Power Capability 1 AUI 2 10BASE-5 3 FOIRL 4 10BASE-2 5 10BASE-T 6 10BASE-FP 7 10BASE-FB 8 10BASE-FL 9 10BROAD36 10 100BASE-T4 11 100BASE-TX 12 100BASE-FX If auto-negotiation is present on the jack to which this MAU is attached, this attribute will map to the jackAutoNegCapability." ::= { mauEntry 4 } mauStatus OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), operational(3), standby(4), shutdown(5), reset(6) } MAX-ACCESS read-write STATUS mandatory DESCRIPTION "The current state of the MAU. This object may be implemented as a read-only object by those agents and MAUs that do not implement software control of the MAU state. Some agents may not support setting the value of this object to some of the enumerated values. The value other(1) is returned if the MAU is inis in a state other than one of the states 2 through 6. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. A MAU in the operational(3) state is fully functional, operates, and passes signals to its attached DTE or repeater port in accordance to its specification. A MAU in standby(4) state forces DI and CI to idle and the media transmitter to idle or fault, if supported. Standby(4) mode only applies to link type MAUs. The state ofmauMediaAvailrpMauMediaAvail is unaffected. A MAU in shutdown(5) state assumes the same condition on DI, CI, and the media transmitter as though it were powered down or not connected. The MAU may return other(1) value for themauJabberStaterpMauJabberState andmauMediaAvailrpMauMediaAvail objects when it is in this state. For an AUI, this state will remove power from the AUI. Setting this variable to the value reset(6) resets the MAU in the same manner as a power-off, power- on cycle of at least one-half second would. The agent is not required to return the value reset (6). Setting this variable to the value operational(3), standby(4), or shutdown(5) causes the MAU to assume the respective state except that setting a mixing-type MAU or an AUI to standby(4) will cause the MAU to enter the shutdown state." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, acRESETMAU." ::= {mauEntryrpMauEntry 5 }mauMediaAvailrpMauMediaAvail OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), available(3), notAvailable(4), remoteFault(5), invalidSignal(6), remoteJabber(7), remoteLinkLoss(8), remoteTest(9) } MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 10BASE-T, 10BASE-F) then this is equivalent to the link test fail state/low light function. For an AUI or a coax (including broadband) MAU this indicates whether or not loopback is detected on the DI circuit. The value of this attribute persists between packets for MAU types AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. The value other(1) is returned if the mediaAvail state is not one of 2 through 6. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. At power-up or following a reset, the value of this attribute will be unknown for AUI, coax, and 10BASE-FP MAUs. For these MAUs loopback will be tested on each transmission during which no collision is detected. If DI is receiving input when DO returns to IDL after a transmission and there has been no collision during the transmission then loopback will be detected. The value of this attribute will only change during non-collided transmissions for AUI, coax, and 10BASE-FP MAUs. For 100BASE-T4, 100BASE-TX and 100BASE-FX the enumerations match the states within the respective link integrity state diagrams, fig 23- 12 and 24-15 of sections 23 and 24 of [2]. Any MAU which implements management of Auto- Negotiation will map remote fault indication to remote fault. The value available(3) indicates that the link, light, or loopback is normal. The value notAvailable(4) indicates link loss, low light, or no loopback. The value remoteFault(5) indicates that a fault has been detected at the remote end of the link. This value applies to 10BASE-FB, 100BASE-T4 Far End Fault Indication and non-specified remote faults from a system running Auto-Negotiation. The values remoteJabber(7), remoteLinkLoss(8), and remoteTest(9) should be used instead of remoteFault(5) where the reason for remote fault is identified in the remote signaling protocol. The value invalidSignal(6) indicates that an invalid signal has been received from the other end of the link.Both remoteFault(5) and invalidSignal(6) applyInvalidSignal(6) applies only to MAUs of type 10BASE-FB. Where an IEEEDraftStd802.3u/D4802.3u-1995 clause 22 MII is present, a logic one in the remote fault bit (reference section 22.2.4.2.8 of that document) maps to the value remoteFault(5), and a logic zero in the link status bit (reference section 22.2.4.2.10 of that document) maps to the value notAvailable(4). The value notAvailable(4) takes precedence over the value remoteFault(5)." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." ::= {mauEntryrpMauEntry 6 }mauMediaAvailStateExitsrpMauMediaAvailStateExits OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "A count of the number of times thatmauMediaAvailrpMauMediaAvail for this MAU instance leaves the state available(3)." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." ::= {mauEntryrpMauEntry 7 }mauJabberStaterpMauJabberState OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), noJabber(3), jabbering(4) } MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "The value other(1) is returned if the jabber state is not 2, 3, or 4. The agent must always return other(1) for MAU type dot3MauTypeAUI. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. If the MAU is not jabbering the agent returns noJabber(3). This is the 'normal' state. If the MAU is in jabber state the agent returns the jabbering(4) value." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, aJabber.jabberFlag." ::= {mauEntryrpMauEntry 8 }mauJabberingStateEntersrpMauJabberingStateEnters OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "A count of the number of times that mauJabberState for this MAU instance enters the state jabbering(4). For MAUs of type dot3MauTypeAUI, dot3MauType100BaseT4, dot3MauType100BaseTX, and dot3MauType100BaseFX, this counter will always indicate zero." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, aJabber.jabberCounter." ::= {mauEntryrpMauEntry 9 }mauFalseCarriersrpMauFalseCarriers OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "A count of the number of false carrier events during IDLE in 100BASE-X links. This counter does not increment at the symbol rate. It can increment after a valid carrier completion at a maximum rate of once per 100 ms until the next carrier event. This counter increments only for MAUs of type dot3MauType100BaseT4, dot3MauType100BaseTX, and dot3MauType100BaseFX. For all other MAU types, this counter will always indicate zero. The approximate minimum time for rollover of this counter is 7.4 hours." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." ::= {mauEntryrpMauEntry 10 } ---- Jack Tables -- --Thejack object types defined below are intendedrpJackTable applies toprovideMAUs attached to repeaters --management information forwhich have one or more external jackson a system. They -- describe(connectors). rpJackTable OBJECT-TYPE SYNTAX SEQUENCE OF RpJackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about thejack fromexternal jacks attached to MAUs attached to theoutside looking in, such that for --ports of aparticular connector atrepeater." ::= { dot3RpMauBasicGroup 2 } rpJackEntry OBJECT-TYPE SYNTAX RpJackEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the table, containing information about a particularlocation on the outside -- of the box, these objects can be used to determinejack." INDEX { rpJackGroupIndex, rpJackPortIndex, rpJackMauIndex, rpJackIndex } ::= { rpJackTable 1 } RpJackEntry ::= SEQUENCE { rpJackGroupIndex Integer32, rpJackPortIndex Integer32, rpJackMauIndex Integer32, rpJackIndex Integer32, rpJackType INTEGER } rpJackGroupIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the group within containing the port attached towhich -- internal entity it is mapped, andthe MAU to whichinternal entity it -- could potentially be mapped as a result of the operation ofthe-- auto-negotiation function definedjack described bythe IEEE 802.3 management -- standard. -- -- The IEEE 802.3 auto-negotiation functionthis entry isdefined such that -- it can be expanded to work for technologies other than those -- defined by 802.3.connected. Note: Inaddition, although the purpose of -- auto-negotiation is to negotiate the use ofpractice, aparticular -- (signalling?) technology acrossgroup will generally be aparticular link between -- network components, the outcome offield-replaceable unit (i.e., module, card, or board) thattechnology choice --canhave run-time implications for systems containing a mix -- of networking features. -- -- For instance, afit in the physical systemcontaining both 10enclosure, and100 -- Mb/s repeater capability on a particular link will, -- of necessity, requirethelink to potentially connectgroup number will correspond to-- two different repeaters: one 10 Mb/s repeater and one 100 -- Mb/s repeater (there being no such device asa10/100 -- repeater). Only one of these connections will be active -- at run time, dependingnumber marked on theoutcomephysical enclosure. The group denoted by a particular value of this object is theauto-negotiation -- on that link, and therefore the auto-negotiation itself can -- havesame as theeffect of determininggroup denoted by theactual connectivitysame value of--rpMauGroupIndex." ::= { rpJackEntry 1 } rpJackPortIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies thelink. -- -- These tables are intendedrepeater port within group rpJackGroupIndex attached toapply firstlythe MAU tojacks connectedwhich the jack described by this entry is connected." REFERENCE "" ::= { rpJackEntry 2 } rpJackMauIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the MAU connected to-- IEEE 802.3 repeaters, and additionallyport rpJackPortIndex within group rpJackGroupIndex toany other management -- domain forwhichthey may be useful. Certain object types here -- have been cross-referenced intothe802.3 repeater MIB (which -- draftjack that iscurrently under discussiondescribed by thisworking group) and -- to the interfaces table of MIB-II. For example, thereentry is-- some overlap between "jackInternalConnection" and "rptrInfoId" -- fromconnected." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." ::= { rpJackEntry 3 } rpJackIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies therepeater MIB draft. Please referjack described by this entry among within other jacks attached to theobjectMAU denoted by rpJackMauIndex." ::= { rpJackEntry 4 } rpJackType OBJECT-TYPE SYNTAX INTEGER { other(1), rj45(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The jack connector type, as it appears on the outside of the system." ::= { rpJackEntry 5 } --definitions below for specific details.-- ThejackTable applies to systems which have one orBasic Interface MAU Table --more external jacks (connectors). jackTableifMauTable OBJECT-TYPE SYNTAX SEQUENCE OFJackEntryIfMauEntry MAX-ACCESS not-accessible STATUSmandatorycurrent DESCRIPTION"Configuration objects for the external jacks on the system.""Table of descriptive and status information about MAU(s) attached to an interface." ::= {jackBasicGroupdot3IfMauBasicGroup 1 }jackEntryifMauEntry OBJECT-TYPE SYNTAXJackEntryIfMauEntry MAX-ACCESS not-accessible STATUSmandatorycurrent DESCRIPTION "An entry in the table, containingconfigurationinformationfor aabout aparticular jack."single MAU." INDEX {jackGroupIndex, jackjackIndexifMauIfIndex, ifMauIndex } ::= { ifMauTable 1 } IfMauEntry ::= SEQUENCE { ifMauIfIndex Integer32, ifMauIndex Integer32, ifMauType OBJECT IDENTIFIER, ifMauStatus INTEGER, ifMauMediaAvail INTEGER, ifMauMediaAvailStateExits Counter32, ifMauJabberState INTEGER, ifMauJabberingStateEnters Counter32, ifMauFalseCarriers Counter32, ifMauTypeList Integer32 } ifMauIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the interface to which the MAU described by this entry is connected." REFERENCE "RFC 1213, ifIndex" ::= {jackTableifMauEntry 1 }JackEntryifMauIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the MAU connected to interface ifMauIfIndex that is described by this entry." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." ::= { ifMauEntry 2 } ifMauType OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS current DESCRIPTION "This object identifies the 10 or 100 Mb/s baseband MAU type. An initial set of MAU types are defined above. The assignment of OBJECT IDENTIFIERs to new types of MAUs is managed by the IANA. If the MAU type is unknown, the object identifier unknownMauType OBJECT IDENTIFIER ::= { 0 0 } is returned. Note that unknownMauType is a syntactically valid object identifier, and any conformant implementation of ASN.1 and the BER must be able to generate and recognize this value." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." ::= { ifMauEntry 3 } ifMauStatus OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), operational(3), standby(4), shutdown(5), reset(6) } MAX-ACCESS read-write STATUS current DESCRIPTION "The current state of the MAU. This object may be implemented as a read-only object by those agents and MAUs that do not implement software control of the MAU state. Some agents may not support setting the value of this object to some of the enumerated values. The value other(1) is returned if the MAU is in a state other than one of the states 2 through 6. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. A MAU in the operational(3) state is fully functional, operates, and passes signals to its attached DTE or repeater port in accordance to its specification. A MAU in standby(4) state forces DI and CI to idle and the media transmitter to idle or fault, if supported. Standby(4) mode only applies to link type MAUs. The state of ifMauMediaAvail is unaffected. A MAU in shutdown(5) state assumes the same condition on DI, CI, and the media transmitter as though it were powered down or not connected. The MAU may return other(1) value for the ifMauJabberState and ifMauMediaAvail objects when it is in this state. For an AUI, this state will remove power from the AUI. Setting this variable to the value reset(6) resets the MAU in the same manner as a power-off, power- on cycle of at least one-half second would. The agent is not required to return the value reset (6). Setting this variable to the value operational(3), standby(4), or shutdown(5) causes the MAU to assume the respective state except that setting a mixing-type MAU or an AUI to standby(4) will cause the MAU to enter the shutdown state." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, acRESETMAU." ::= { ifMauEntry 4 } ifMauMediaAvail OBJECT-TYPE SYNTAX INTEGER { other(1), unknown(2), available(3), notAvailable(4), remoteFault(5), invalidSignal(6), remoteJabber(7), remoteLinkLoss(8), remoteTest(9) } MAX-ACCESS read-only STATUS current DESCRIPTION "If the MAU is a link or fiber type (FOIRL, 10BASE-T, 10BASE-F) then this is equivalent to the link test fail state/low light function. For an AUI or a coax (including broadband) MAU this indicates whether or not loopback is detected on the DI circuit. The value of this attribute persists between packets for MAU types AUI, 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. The value other(1) is returned if the mediaAvail state is not one of 2 through 6. The value unknown(2) is returned when the MAU's true state is unknown; for example, when it is being initialized. At power-up or following a reset, the value of this attribute will be unknown for AUI, coax, and 10BASE-FP MAUs. For these MAUs loopback will be tested on each transmission during which no collision is detected. If DI is receiving input when DO returns to IDL after a transmission and there has been no collision during the transmission then loopback will be detected. The value of this attribute will only change during non-collided transmissions for AUI, coax, and 10BASE-FP MAUs. For 100BASE-T4, 100BASE-TX and 100BASE-FX the enumerations match the states within the respective link integrity state diagrams, fig 23- 12 and 24-15 of sections 23 and 24 of [2]. Any MAU which implements management of Auto- Negotiation will map remote fault indication to remote fault. The value available(3) indicates that the link, light, or loopback is normal. The value notAvailable(4) indicates link loss, low light, or no loopback. The value remoteFault(5) indicates that a fault has been detected at the remote end of the link. This value applies to 10BASE-FB, 100BASE-T4 Far End Fault Indication and non-specified remote faults from a system running Auto-Negotiation. The values remoteJabber(7), remoteLinkLoss(8), and remoteTest(9) should be used instead of remoteFault(5) where the reason for remote fault is identified in the remote signaling protocol. The value invalidSignal(6) indicates that an invalid signal has been received from the other end of the link. InvalidSignal(6) applies only to MAUs of type 10BASE-FB. Where an IEEE Std 802.3u-1995 clause 22 MII is present, a logic one in the remote fault bit (reference section 22.2.4.2.8 of that document) maps to the value remoteFault(5), and a logic zero in the link status bit (reference section 22.2.4.2.10 of that document) maps to the value notAvailable(4). The value notAvailable(4) takes precedence over the value remoteFault(5)." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." ::=SEQUENCE{jackGroupIndex Integer32, jackIndex Integer32, jackType INTEGER, jackInternalConnection OBJECT IDENTIFIER, jackConnectionLastChange TimeStampifMauEntry 5 }jackGroupIndexifMauMediaAvailStateExits OBJECT-TYPE SYNTAXInteger32 (1..2147483647)Counter32 MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION"This variable uniquely identifies the group within the system containing the jack described by this entry. Note: In practice, a group will generally be a field-replaceable unit (i.e., module, card, or board) that can fit in the physical system enclosure, and"A count of thegroup number will correspond to anumbermarked on the physical enclosure. For jacks attached to repeaters, the group denoted by a particular valueof times that ifMauMediaAvail for thisobject is the same as the group denoted byMAU instance leaves thesame value of rptrGroupIndex."state available(3)." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." ::= {jackEntry 1ifMauEntry 6 }jackIndexifMauJabberState OBJECT-TYPE SYNTAXInteger32 (1..2147483647)INTEGER { other(1), unknown(2), noJabber(3), jabbering(4) } MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION"This variable uniquely identifies the jack described by this entry among within other jacks within the group denoted by jackGroupIndex. Note that"The value other(1) is returned if thejackjabber state isconnected to a repeater, thenot 2, 3, or 4. The agent must always return other(1) for MAU type dot3MauTypeAUI. The valueof this objectunknown(2) is returned when thesame as the value of rptrPortIndexMAU's true state is unknown; for example, when it is being initialized. If theassociated port in the same group (i.e. jackIndex == rptrPortIndex, and jackGroupIndex == rptrPortGroupIndex). Jacks may also be connected to other entities, including logical interfaces within the system, in which case the numbering of the entity mayMAU is notmatchjabbering thenumbering ofagent returns noJabber(3). This is thejack. In all cases,'normal' state. If thenext-level entity to which this jack is connectedMAU isspecified byin jabber state thejackInternalConnection object for this entry."agent returns the jabbering(4) value." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, aJabber.jabberFlag." ::= {jackEntry 2ifMauEntry 7 }jackTypeifMauJabberingStateEnters OBJECT-TYPE SYNTAXINTEGER { other(1), rj45(2) }Counter32 MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION"The jack connector type, as it appears on"A count of theoutsidenumber of times that mauJabberState for this MAU instance enters thesystem."state jabbering(4). For MAUs of type dot3MauTypeAUI, dot3MauType100BaseT4, dot3MauType100BaseTX, and dot3MauType100BaseFX, this counter will always indicate zero." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.6, aJabber.jabberCounter." ::= {jackEntry 3ifMauEntry 8 }jackInternalConnectionifMauFalseCarriers OBJECT-TYPE SYNTAXOBJECT IDENTIFIERCounter32 MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION"This variable identifies"A count of theinstancenumber ofan internal entity to whichfalse carrier events during IDLE in 100BASE-X links. This counter does not increment at thejack is connected. For a jack whichsymbol rate. It canbe administratively configured, orincrement after ajack on which auto-negotiation is supported, the value of this object may change between system resets. If the jack is connected tovalid carrier completion at arepeater,maximum rate of once per 100 ms until thevaluenext carrier event. This counter increments only for MAUs of type dot3MauType100BaseT4, dot3MauType100BaseTX, and dot3MauType100BaseFX. For all other MAU types, thisobjectcounter willbe rptrInfoId.r, where r equals the value of rptrPortRptrIdalways indicate zero. The approximate minimum time forthe port with whichrollover of thisjackcounter isassociated (see also7.4 hours." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." ::= { ifMauEntry 9 } ifMauTypeList OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "A value that uniquely identifies theabove descriptionset ofjackIndex). Ifpossible IEEE 802.3 types that thejackMAU could be. The value isconnected to an interface,a sum which initially takes the value zero. Then, for each type capability of thisobject will be ifIndex.i, where i isMAU, 2 raised to theinstance ofpower noted below is added to theinterface. For other types of internal entities,sum. For example, a MAU which has the capability to be only 10BASE-T would have a value ofthis object must be an instance identifier512 (2**9). In contrast, a MAU whichuniquely identifies the entity typesupports both 10Base-T andthe instance of that type within the managed system." ::= { jackEntry 4 } jackConnectionLastChange OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The100BASE-TX would have a value ofsysUpTime when any1536 ((2**9) + (2**10)). The powers of 2 assigned to thefollowing conditions occurred: 1)capabilities are these: Power Capability 1 AUI 2 10BASE-5 3 FOIRL 4 10BASE-2 5 10BASE-T 6 10BASE-FP 7 10BASE-FB 8 10BASE-FL 9 10BROAD36 10 100BASE-T4 11 100BASE-TX 12 100BASE-FX If auto-negotiation is present on theagent cold- or warm-started; 2) this instance ofjackwas created (such as when a device or module was addedtothe system); 3) a change occurred in the value of jackInternalConnection forwhich thisentry."MAU is attached, this attribute will map to the ifMauAutoNegCapability." ::= {jackEntry 5ifMauEntry 10 } -- ThejackAutoNegTableifJackTable applies tosystems in whichMAUs attached to interfaces --auto-negotiation is supported onwhich have one or morejacks. jackAutoNegTableexternal jacks (connectors). ifJackTable OBJECT-TYPE SYNTAX SEQUENCE OFJackAutoNegEntryIfJackEntry MAX-ACCESS not-accessible STATUSmandatorycurrent DESCRIPTION"Configuration and status objects for"Information about theauto- negotiation function ofexternal jackson the system."attached to MAUs attached to an interface." ::= {jackAutoNegGroup 1dot3IfMauBasicGroup 2 }jackAutoNegEntryifJackEntry OBJECT-TYPE SYNTAXJackAutoNegEntryIfJackEntry MAX-ACCESS not-accessible STATUSmandatorycurrent DESCRIPTION "An entry in the table, containingconfiguration and statusinformationfor the auto-negotiation function ofabout a particular jack."AUGMENTSINDEX {jackEntryifJackIfIndex, ifJackMauIndex, ifJackIndex } ::= {jackAutoNegTableifJackTable 1 }JackAutoNegEntryIfJackEntry ::= SEQUENCE {jackAutoNegAdminStatus INTEGER, jackAutoNegRemoteSignaling INTEGER, jackAutoNegPotentialConnectSetifJackIfIndex Integer32,jackAutoNegConfig INTEGER, jackAutoNegCapability Integer32, jackAutoNegCapAdvertisedifJackMauIndex Integer32,jackAutoNegCapReceivedifJackIndex Integer32,jackAutoNegTechnologyInUse INTEGER, jackAutoNegRestartifJackType INTEGER }jackAutoNegAdminStatusifJackIfIndex OBJECT-TYPE SYNTAXINTEGER { enabled(1), disabled(2) }Integer32 MAX-ACCESSread-writeread-only STATUSmandatorycurrent DESCRIPTION"Setting this object to enabled(1) will cause"This variable uniquely identifies the interfacewhich has the auto-negotiation signaling abilityattached tobe enabled. If disabled thentheinterface will act as it would if it had no auto- negotiation signaling. Under these conditions, a jack connected to an IEEE 802.3MAUwill immediately be forcedto which thestates indicatedjack described by this entry is connected. The interface denoted by awrite to theparticular value of this objectrpMauType or ifMauType. [Ed.--This doesn't allow for half vs. full duplex.]" REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState and 30.6.1.2.2, acAutoNegAdminControl."is the same as the group denoted by the same value of ifMauIfIndex." ::= {jackAutoNegEntryifJackEntry 1 }jackAutoNegRemoteSignalingifJackMauIndex OBJECT-TYPE SYNTAXINTEGER { detected(1), notdetected(2) }Integer32 (1..2147483647) MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION"A value indicating whether"This variable uniquely identifies theremote end ofMAU connected to port ifJackIfIndex to which thelinkjack that isusing auto-negotiation signaling. It takes the value detected(1) if and only if, during the previous link negotiation, FLP Bursts were received."described by this entry is connected." REFERENCE "[IEEE 802.3 Mgt],30.6.1.1.3, aAutoNegRemoteSignaling."30.5.1.1.1, aMAUID." ::= {jackAutoNegEntryifJackEntry 2 }jackAutoNegPotentialConnectSetifJackIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "This variable uniquely identifies theset of internal entities to which this jack can potentially connect using as a result of auto-negotiation. The set of potential connections can include, at most, one entity supporting each of the technologies for which thisjackhas auto- negotiation capability. For example, if the jackAutoNegCapability fordescribed by this entryincludes 10Base-T, then one and only one 10Base-T entity may be included in the jack's potential connection set. The members of the set are defined inamong within other jacks attached to thejackAutoNegConnectSetTable;MAU denoted by ifJackMauIndex." ::= { ifJackEntry 3 } ifJackType OBJECT-TYPE SYNTAX INTEGER { other(1), rj45(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The jack connector type, as it appears on thevalueoutside ofthis object isthefirst index (jackAutoNegConnectSetIndex) into that table. Each entrysystem." ::= { ifJackEntry 4 } -- The ifMauAutoNegTable applies to systems inthat table whose first index has the same value as this object is a member of the set of potential connections for this jack. Note that this objectwhich -- auto-negotiation isread-only,supported on one or more MAUs -- attached to interfaces. ifMauAutoNegTable OBJECT-TYPE SYNTAX SEQUENCE OF IfMauAutoNegEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Configuration andtherefore does not allowstatus objects foradministrative control ofthejack connection: the method of such control, if available, is implementation-specific. [?? allow read-write implementationsauto- negotiation function ofthis ??] (See also the definitions for the jackAutoNegConnectSetTable.)"MAUs attached to interfaces." ::= {jackAutoNegEntry 3dot3IfMauAutoNegGroup 1 }jackAutoNegConfigifMauAutoNegEntry OBJECT-TYPE SYNTAXINTEGER { other(1), configuring(2), complete(3), disabled(4), parallelDetectFail(5) }IfMauAutoNegEntry MAX-ACCESSread-onlynot-accessible STATUSmandatorycurrent DESCRIPTION"A value indicating"An entry in thecurrenttable, containing configuration and statusofinformation for the auto-negotiationprocess. The enumeration parallelDetectFail(5) maps to a failure in parallel detection as defined in 28.2.3.1function of[IEEE 802.3 Std]." REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.4, aAutoNegAutoConfig."a particular MAU." AUGMENTS { ifMauEntry } ::= {jackAutoNegEntry 4ifMauAutoNegTable 1 } IfMauAutoNegEntry ::= SEQUENCE { ifMauAutoNegAdminStatus INTEGER, ifMauAutoNegRemoteSignaling INTEGER, ifMauAutoNegConfig INTEGER, ifMauAutoNegCapability Integer32, ifMauAutoNegCapAdvertised Integer32, ifMauAutoNegCapReceived Integer32, ifMauAutoNegTechnologyInUse INTEGER, ifMauAutoNegRestart INTEGER }jackAutoNegCapabilityifMauAutoNegAdminStatus OBJECT-TYPE SYNTAXInteger32INTEGER { enabled(1), disabled(2) } MAX-ACCESSread-onlyread-write STATUSmandatorycurrent DESCRIPTION"A value that uniquely identifies the set of capabilities of the local auto-negotiation entity. The value is a sum which initially takes the value zero. Then, for each capability of"Setting thisinterface, 2 raised to the power noted below is addedobject to enabled(1) will cause thesum. For example, aninterface which has thecapability to support only 100Base-TX would have a value of 512 (2**9). In contrast, an interface which supports both 100Base-TX and 100Base-TX Full Duplex would have a value of 1536 ((2**9) + (2**10)). The powers of 2 assigned to the capabilities are these: Power Capability 1 other 2 reserved 3 10BASE-T 4 10BASE-T Full Duplex 5 10BASE-FL 6 10BASE-FL Full Duplex 7 10BASE-FB 8 10BASE-FB Full Duplex 9 100BASE-TX 10 100BASE-TX Full Duplex 11 100BASE-FX 12 100BASE-FX Full Duplex 13 100BASE-T4 For jacks connectedauto-negotiation signaling ability to be enabled. If disabled then the interface will act as it would if it had no auto- negotiation signaling. Under these conditions, an IEEE 802.3MAUs, the half- and full-duplex value pairs each map to a singleMAUtype. For example, 10BASE-T and 10BASE-T Full Duplex each usewill immediately be forced to the states indicated by aMAU type of dot3MauType10BaseT. Note that interfaces that support this MIB may have capabilities that extend beyondwrite to thescope of this MIB."object rpMauType or ifMauType. [Ed.--This doesn't allow for half vs. full duplex.]" REFERENCE "[IEEE 802.3 Mgt],30.6.1.1.5, aAutoNegLocalTechnologyAbility."30.6.1.1.2, aAutoNegAdminState and 30.6.1.2.2, acAutoNegAdminControl." ::= {jackAutoNegEntry 5ifMauAutoNegEntry 1 }jackAutoNegCapAdvertisedifMauAutoNegRemoteSignaling OBJECT-TYPE SYNTAXInteger32INTEGER { detected(1), notdetected(2) } MAX-ACCESSread-writeread-only STATUSmandatorycurrent DESCRIPTION "A valuethat uniquely identifiesindicating whether thesetremote end ofcapabilities advertised bythelocal auto- negotiation entity. Refer to jackAutoNegCapability for a description oflink is using auto-negotiation signaling. It takes thepossible values of this object. Capabilities in this object that are not available in jackAutoNegCapability cannot be enabled."value detected(1) if and only if, during the previous link negotiation, FLP Bursts were received." REFERENCE "[IEEE 802.3 Mgt],30.6.1.1.6, aAutoNegAdvertisedTechnologyAbility."30.6.1.1.3, aAutoNegRemoteSignaling." ::= {jackAutoNegEntry 6ifMauAutoNegEntry 2 }jackAutoNegCapReceivedifMauAutoNegConfig OBJECT-TYPE SYNTAXInteger32INTEGER { other(1), configuring(2), complete(3), disabled(4), parallelDetectFail(5) } MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "A valuethat uniquely identifiesindicating thesetcurrent status ofcapabilities received fromtheremote auto- negotiation entity. Referauto-negotiation process. The enumeration parallelDetectFail(5) maps tojackAutoNegCapability foradescription of the possible values of this object. Note that interfaces that support this MIB may be attached to remote auto-negotiation entities which have capabilities beyond the scopefailure in parallel detection as defined in 28.2.3.1 ofthis MIB."[IEEE 802.3 Std]." REFERENCE "[IEEE 802.3 Mgt],30.6.1.1.7, aAutoNegReceivedTechnologyAbility."30.6.1.1.4, aAutoNegAutoConfig." ::= {jackAutoNegEntry 7ifMauAutoNegEntry 4 }jackAutoNegTechnologyInUseifMauAutoNegCapability OBJECT-TYPE SYNTAXINTEGER { other(1), reserved(2), 10BASE-T(3), 10BASE-T-FD(4), 10BASE-FL(5), 10BASE-FL-FD(6), 10BASE-FB(7), 10BASE-FB-FD(8), 100BASE-TX(9), 100BASE-TX-FD(10), 100BASE-FX(11), 100BASE-FX-FD(12), 100BASE-T4(13) }Integer32 MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION"The"A valueof this objectthat uniquely identifies thetechnology currently in use onset of capabilities of thelink to which this jack is attached. Thislocal auto-negotiation entity. The valuemay beis aresult of auto- negotiation onsum which initially takes thelink. If auto- negotiation is disabled andvalue zero. Then, for each capability of this interface, 2 raised to thejackpower noted below isconnectedadded to the sum. For example, anIEEE 802.3 MAU, this object will change to reflectinterface which has theresultcapability to support only 100Base-TX would have a value of 512 (2**9). In contrast, an interface which supports both 100Base-TX and 100Base-TX Full Duplex would have awritevalue of 1536 ((2**9) + (2**10)). The powers of 2 assigned to theobject rpMauType or ifMauType." ::= { jackAutoNegEntrycapabilities are these: Power Capability 1 other 2 reserved 3 10BASE-T 4 10BASE-T Full Duplex 5 10BASE-FL 6 10BASE-FL Full Duplex 7 10BASE-FB 8} jackAutoNegRestart OBJECT-TYPE SYNTAX INTEGER { restart(1), norestart(2) } MAX-ACCESS read-write STATUS mandatory DESCRIPTION "If10BASE-FB Full Duplex 9 100BASE-TX 10 100BASE-TX Full Duplex 11 100BASE-FX 12 100BASE-FX Full Duplex 13 100BASE-T4 For IEEE 802.3 MAUs, the half- and full-duplex valueof this object is set to restart(1) then this will force auto-negotiationpairs each map tobegin link renegotiation. If auto-negotiation signaling is disabled,awrite tosingle MAU type. For example, 10BASE-T and 10BASE-T Full Duplex each use a MAU type of dot3MauType10BaseT. Note that interfaces that support thisobject has no effect. SettingMIB may have capabilities that extend beyond thevaluescope ofthis object to norestart(2) has no effect."this MIB." REFERENCE "[IEEE 802.3 Mgt],30.6.1.2.1, acAutoNegRestartAutoConfig."30.6.1.1.5, aAutoNegLocalTechnologyAbility." ::= {jackAutoNegEntry 9ifMauAutoNegEntry 5 }-- The jackAutoNegConnectSetTable applies to systems in which -- auto-negotiation is supported on one or more jacks. jackAutoNegConnectSetTableifMauAutoNegCapAdvertised OBJECT-TYPE SYNTAXSEQUENCE OF JackAutoNegConnectSetEntryInteger32 MAX-ACCESSnot-accessibleread-write STATUSmandatorycurrent DESCRIPTION "Atable describing sets of entities within the system. Each jack in the system, for which auto- negotiation is supported, is associated with one of these sets. Each such jack may connect to any ONE of the entities belonging tovalue that uniquely identifies the setdenoted by its instanceofjackAutoNegPotentialConnectSet, the choice to be determinedcapabilities advertised by thejack'slocal auto- negotiationfunction (if enabled). Any single set may contain no more than one entity representing a particular technologyentity. Refer towhich the jack can auto-negotiate. For example, a set may include one and only one 10BASE-T entity (e.g.ifMauAutoNegCapability for arepeater), and one and only one 100BASE-TX full duplex entity (e.g. an interface). The listdescription ofpotential technologies is denoted bythecapabilities enumeratedpossible values of this object. Capabilities inthe jackAutoNegCapabilitythis object that are not available in ifMauAutoNegCapability cannot be enabled." REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.6, aAutoNegAdvertisedTechnologyAbility." ::= { ifMauAutoNegEntry 6 } ifMauAutoNegCapReceived OBJECT-TYPEdescription; it followsSYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "A value that uniquely identifies themaximum number of entities in anysetisof capabilities received from thesame asremote auto- negotiation entity. Refer to ifMauAutoNegCapability for a description of thenumberpossible values ofdifferent capabilities listed inthis object. Note thatdescription. It is expectedinterfaces thatin a systemsupport this MIB may be attached to remote auto-negotiation entities whichsupports administrative configuration of connections, the administrator will configurehave capabilities beyond theconnection set for a jack so that allscope of this MIB." REFERENCE "[IEEE 802.3 Mgt], 30.6.1.1.7, aAutoNegReceivedTechnologyAbility." ::= { ifMauAutoNegEntry 7 } ifMauAutoNegTechnologyInUse OBJECT-TYPE SYNTAX INTEGER { other(1), reserved(2), t10BASET(3), t10BASETFD(4), t10BASEFL(5), t10BASEFLFD(6), t10BASEFB(7), t10BASEFBFD(8), t100BASETX(9), t100BASETXFD(10), t100BASEFX(11), t100BASEFXFD(12), t100BASET4(13) } MAX-ACCESS read-only STATUS current DESCRIPTION "The value of this object identifies the technology currently in use on theentity members are part oflink to which this MAU is attached. This value may be asingle network, in order thatresult of auto- negotiation on the link. If auto- negotiationfunction will not be able to disconnectis disabled andreconnect a link between various networks supported withinthesystem. That is, the jackAutoNegPotentialConnectSetMAU isusedan IEEE 802.3 MAU, this object will change todeterminereflect thenetwork connection (similarlyresult of a write to theway a repeater port's repeater id can be used), but WITHIN that set,object rpMauType or ifMauType." ::= { ifMauAutoNegEntry 8 } ifMauAutoNegRestart OBJECT-TYPE SYNTAX INTEGER { restart(1), norestart(2) } MAX-ACCESS read-write STATUS current DESCRIPTION "If theparticular entity chosenvalue of this object isdetermined viaset to restart(1) then this will force auto-negotiationduring operation."to begin link renegotiation. If auto-negotiation signaling is disabled, a write to this object has no effect. Setting the value of this object to norestart(2) has no effect." REFERENCE "[IEEE 802.3 Mgt], 30.6.1.2.1, acAutoNegRestartAutoConfig." ::= {jackAutoNegGroup 2ifMauAutoNegEntry 9 }jackAutoNegConnectSetEntrybroadMauBasicTable OBJECT-TYPE SYNTAXJackAutoNegConnectSetEntrySEQUENCE OF BroadMauBasicEntry MAX-ACCESS not-accessible STATUSmandatorycurrent DESCRIPTION"An entry defining one entity of a set"Table ofentities to which a system jack may potentially connect,descriptive and status information about thedeterminationbroadband MAUs connected tobe made byinterfaces." ::= { dot3BroadMauBasicGroup 1 } broadMauBasicEntry OBJECT-TYPE SYNTAX BroadMauBasicEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in thejack's auto- negotiation function."table, containing information about a single broadband MAU." INDEX {jackAutoNegConnectSet, jackAutoNegConnectEntityTypebroadMauIfIndex, broadMauIndex } ::= {jackAutoNegConnectSetTablebroadMauBasicTable 1 }JackAutoNegConnectSetEntryBroadMauBasicEntry ::= SEQUENCE {jackAutoNegConnectSetbroadMauIfIndex Integer32, broadMauIndex Integer32,jackAutoNegConnectEntityTypebroadMauXmtRcvSplitType INTEGER,jackAutoNegConnectEntity OBJECT IDENTIFIERbroadMauXmtCarrierFreq Integer32, broadMauTranslationFreq Integer32 } broadMauIfIndex OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the interface to which the MAU described by this entry is connected." REFERENCE "Reference RFC 1213, ifIndex." ::= { broadMauBasicEntry 1 } broadMauIndex OBJECT-TYPE SYNTAX Integer32 (1..2147483647) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable uniquely identifies the MAU connected to interface broadMauIfIndex that is described by this entry." REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID." ::= { broadMauBasicEntry 2 }jackAutoNegConnectSetbroadMauXmtRcvSplitType OBJECT-TYPE SYNTAXInteger32 (1..2147483647)INTEGER { other(1), single(2), dual(3) } MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "Thisvariable uniquely identifies a setobject indicates the type ofentity instances amongfrequency multiplexing/cabling system used to separate theother sets represented within this table."transmit and receive paths for the 10BROAD36 MAU. The value other(1) is returned if the split type is not either single or dual. The value single(2) indicates a single cable system. The value dual(3) indicates a dual cable system, offset normally zero." REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aBbMAUXmitRcvSplitType." ::= {jackAutoNegConnectSetEntry 1broadMauBasicEntry 3 }jackAutoNegConnectEntityTypebroadMauXmtCarrierFreq OBJECT-TYPE SYNTAXINTEGER { other(1), reserved(2), 10BASE-T(3), 10BASE-T-FD(4), 10BASE-FL(5), 10BASE-FL-FD(6), 10BASE-FB(7), 10BASE-FB-FD(8), 100BASE-TX(9), 100BASE-TX-FD(10), 100BASE-FX(11), 100BASE-FX-FD(12), 100BASE-T4(13) }Integer32 MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "This variableidentifiesindicates thetype of internal entity about which this entry contains information. Each settransmit carrier frequency ofpotential connections may contain no more than one entrythe 10BROAD36 MAU in MHz/4; that is, in units ofany particular technology type."250 kHz." REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aBroadbandFrequencies.xmitCarrierFrequency." ::= {jackAutoNegConnectSetEntry 2broadMauBasicEntry 4 }jackAutoNegConnectEntitybroadMauTranslationFreq OBJECT-TYPE SYNTAXOBJECT IDENTIFIERInteger32 MAX-ACCESS read-only STATUSmandatorycurrent DESCRIPTION "This variableidentifies the instance of an internal entity to which a jack may potentially connect. 802.3 repeater and interfaces are examples of such entities. Note that if the jack is connected to a repeater, the value of this object is the same asindicates thevaluetranslation offset frequency ofrptrPortIndex fortheassociated port10BROAD36 MAU inthe same group (i.e. jackIndex == rptrPortIndex, and jackGroupIndex == rptrPortGroupIndex). Jacks may also be connected to other types of entities, including logical interfaces within the system,MHz/4; that is, inwhich case the numbering of the entity may not match the numberingunits ofthe jack. In all cases, the next-level entity to which this jack is connected is specified by the jackInternalConnection object for this entry."250 kHz." REFERENCE "Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aBroadbandFrequencies.translationFrequency." ::= {jackAutoNegConnectSetEntry 3broadMauBasicEntry 5 } -- Notifications for use by 802.3 MAUsmauJabberTraprpMauJabberTrap NOTIFICATION-TYPE OBJECTS {mauJabberStaterpMauJabberState } STATUS current DESCRIPTION "This trap is sent whenever a managed repeater MAU enters the jabber state. The agent must throttle the generation of consecutivemauJabberTrapsrpMauJabberTraps so that there is at least a five-second gap between them." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber notification." ::= { snmpDot3MauMgt 0 1 } ifMauJabberTrap NOTIFICATION-TYPE OBJECTS { ifMauJabberState } STATUS current DESCRIPTION "This trap is sent whenever a managed interface MAU enters the jabber state. The agent must throttle the generation of consecutive ifMauJabberTraps so that there is at least a five-second gap between them." REFERENCE "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber notification." ::= { snmpDot3MauMgt 0 2 } -- Conformance information mauModConf OBJECT IDENTIFIER ::= { mauMod 1 } mauModCompls OBJECT IDENTIFIER ::= { mauModConf 1 } mauModObjGrps OBJECT IDENTIFIER ::= { mauModConf 2 } mauModNotGrps OBJECT IDENTIFIER ::= { mauModConf 3 } -- Object groups mauRpGrpBasic OBJECT-GROUP OBJECTS { rpMauGroupIndex, rpMauPortIndex, rpMauIndex, rpMauType, rpMauStatus, rpMauMediaAvail, rpMauMediaAvailStateExits, rpMauJabberState, rpMauJabberingStateEnters } STATUS current DESCRIPTION "Basic conformance group for MAUs attached to repeater ports. This group is also the conformance specification for RFC 1515 implementations." ::= { mauModObjGrps 1 } mauRpGrpExtended OBJECT-GROUP OBJECTS { rpMauFalseCarriers, rpJackGroupIndex, rpJackPortIndex, rpJackMauIndex, rpJackIndex, rpJackType } STATUS current DESCRIPTION "Conformance group for MAUs attached to repeater ports with extended management (including 100 Mb/s and jack management)." ::= { mauModObjGrps 2 } mauIfGrpBasic OBJECT-GROUP OBJECTS { ifMauIfIndex, ifMauIndex, ifMauType, ifMauStatus, ifMauMediaAvail, ifMauMediaAvailStateExits, ifMauJabberState, ifMauJabberingStateEnters } STATUS current DESCRIPTION "Basic conformance group for MAUs attached to interfaces. This group also provides a conformance specification for RFC 1515 implementations." ::= { mauModObjGrps 3 } mauIfGrpExtended OBJECT-GROUP OBJECTS { ifMauFalseCarriers, ifMauTypeList, ifJackIfIndex, ifJackMauIndex, ifJackIndex, ifJackType } STATUS current DESCRIPTION "Conformance group for MAUs attached to interfaces with extended management (including 100 Mb/s and jack management)." ::= { mauModObjGrps 4 } mauIfGrpAutoNeg OBJECT-GROUP OBJECTS { ifMauAutoNegAdminStatus, ifMauAutoNegRemoteSignaling, ifMauAutoNegConfig, ifMauAutoNegCapability, ifMauAutoNegCapAdvertised, ifMauAutoNegCapReceived, ifMauAutoNegTechnologyInUse, ifMauAutoNegRestart } STATUS current DESCRIPTION "Conformance group for MAUs attached to interfaces with managed auto-negotiation." ::= { mauModObjGrps 5 } mauBroadBasic OBJECT-GROUP OBJECTS { broadMauIfIndex, broadMauIndex, broadMauXmtRcvSplitType, broadMauXmtCarrierFreq, broadMauTranslationFreq } STATUS current DESCRIPTION "Conformance group for broadband MAUs attached to interfaces. This group provides a conformance specification for RFC 1515 implementations." ::= { mauModObjGrps 6 } -- Notification groups -- ?? later -- Compliances mauModRpCompl MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance for MAUs attached to repeater ports." MODULE -- this module MANDATORY-GROUPS { mauRpGrpBasic } GROUP mauRpGrpExtended DESCRIPTION "Implementation of this optional group is recommended for MAUs which have 100Mb/s capability and/or more than one attached external jack." ::= { mauModCompls 1 } mauModIfCompl MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance for MAUs attached to interfaces." MODULE -- this module MANDATORY-GROUPS { mauIfGrpBasic } GROUP mauIfGrpExtended DESCRIPTION "Implementation of this optional group is recommended for MAUs which have 100Mb/s capability and/or more than one attached external jack." GROUP mauIfGrpAutoNeg DESCRIPTION "Implementation of this optional group is recommended for MAUs which support managed auto-negotiation." GROUP mauBroadBasic DESCRIPTION "Implementation of this group is mandatory for broadband MAUs." ::= { mauModCompls 2 } END 4. References [1] IEEE 802.3/ISO 8802-3 Information processing systems - Local area networks - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications, 1993. [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium Attachment Units and Repeater for 100 Mb/s Operation, Type 100BASE-T," Sections 21 through 29, Supplement to IEEE Std 802.3, October 26, 1995. [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, Supplement to IEEE Std 802.3, October 26, 1995. [4] Romascanu, D., and K. de Graaf, "Definitions of Managed Objects for IEEE 802.3 Repeater Devices",November 1995.February 1996.