Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
obsoleted by
- rfc-3636 — Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)
Extracted elements (22)
If a MAU type is unknown, the special OBJECT IDENTIFIER unknownMauType ::= { 0 0 } is returned for rpMauType and ifMauType. This value is syntactically valid ASN.1/BER so any conformant implementation must be able to generate and recognize it, avoiding the need for a separate error path.
Internal MAUs (those whose functionality is implemented entirely within a device) may or may not be managed. If they are managed, their objects should appear in the appropriate MIB group (dot3RpMauBasicGroup or dot3IfMauBasicGroup), rather than in a separate group, maintaining a uniform management model.
An agent implementing interface MAU objects must also implement the 'interfaces' group of MIB-II; the ifMauIfIndex value must equal the ifIndex value for the connected interface. The agent is also expected to implement the Ethernet-like Interfaces MIB (RFC 1398).
An agent implementing repeater MAU objects must also implement the 802.3 Repeater MIB (RFC 1368). The rpMauGroupIndex and rpMauPortIndex values must match the rptrPortGroupIndex and rptrPortIndex values for the connected port.
Implementation of the dot3BroadMauBasicGroup is mandatory for 10BROAD36 MAUs, and is not appropriate for other types of MAUs.
Implementation of the dot3IfMauBasicGroup is mandatory for MAUs attached to interfaces (DTEs).
Implementation of the dot3RpMauBasicGroup is mandatory for MAUs attached to repeaters.
The agent must throttle consecutive rpMauJabberTrap (and ifMauJabberTrap) generations so that there is at least a five-second gap between them.
broadMauBasicTable provides broadband-specific attributes for 10BROAD36 MAUs attached to interfaces, indexed by broadMauIfIndex and broadMauIndex. Fields include broadMauXmtRcvSplitType, broadMauXmtCarrierFreq, and broadMauTranslationFreq.
broadMauXmtCarrierFreq and broadMauTranslationFreq report the transmit carrier frequency and translation offset frequency of the 10BROAD36 MAU respectively, both expressed as INTEGER in units of MHz/4 (250 kHz).
broadMauXmtRcvSplitType indicates the frequency multiplexing/cabling system used for the 10BROAD36 MAU transmit/receive path separation: other(1), single(2) for single-cable, or dual(3) for dual-cable with normally-zero offset.
ifMauTable mirrors rpMauTable for interface MAUs, indexed by ifMauIfIndex (INTEGER, matching MIB-II ifIndex) and ifMauIndex (INTEGER 1..9). Contains the same set of type, status, media availability, jabber state, and counter objects.
rpMauJabberingStateEnters is a Counter that counts entries into the jabbering(4) state for a repeater MAU; for dot3MauTypeAUI this counter always indicates zero.
rpMauJabberState reports jabber detection status with values: other(1), unknown(2), noJabber(3), jabbering(4). The agent must always return other(1) for MAU type dot3MauTypeAUI, which does not support jabber detection.
rpMauJabberTrap (TRAP-TYPE ::= 1) is sent whenever a managed repeater MAU enters the jabbering state, carrying the variable rpMauJabberState. ifMauJabberTrap (TRAP-TYPE ::= 2) is the equivalent for interface MAUs, carrying ifMauJabberState.
rpMauMediaAvailable reports link/loopback status with values: other(1), unknown(2), available(3), notAvailable(4), remoteFault(5), invalidSignal(6). For link/fiber MAUs it reflects link test state; for AUI/coax it reflects loopback on the DI circuit. remoteFault and invalidSignal apply only to 10BASE-FB MAUs.
rpMauMediaAvailableStateExits is a Counter that counts the number of times rpMauMediaAvailable leaves the available(3) state, corresponding to IEEE 802.3 MAU Mgt attribute lostMediaCount.
rpMauTable is a table of descriptive and status information about MAUs attached to repeater ports, indexed by rpMauGroupIndex, rpMauPortIndex, and rpMauIndex (INTEGER 1..9). Each entry contains type, status, media availability, media availability state exit count, jabber state, and jabber state enter count.
The MIB is organized into three groups: dot3RpMauBasicGroup (OID snmpDot3MauMgt 1) for repeater MAUs, dot3IfMauBasicGroup (OID snmpDot3MauMgt 2) for interface MAUs, and dot3BroadMauBasicGroup (OID snmpDot3MauMgt 3) for broadband MAUs. The root OID snmpDot3MauMgt is assigned under mib-2 26.
IANA manages the assignment of OBJECT IDENTIFIERs for new MAU types under dot3MauType (snmpDot3MauMgt 4). Initial set includes dot3MauTypeAUI, dot3MauType10Base5, dot3MauTypeFoirl, dot3MauType10Base2, dot3MauType10BaseT, dot3MauType10BaseFP, dot3MauType10BaseFB, dot3MauType10BaseFL, and dot3MauType10Broad36.
The RFC explicitly states that security issues are not discussed in this memo.
rpMauStatus (and ifMauStatus) defines MAU administrative states: other(1), unknown(2), operational(3), standby(4), shutdown(5), reset(6). Writing reset(6) triggers a power-cycle equivalent; writing standby(4) to a mixing-type MAU or AUI instead causes the shutdown state. The agent is not required to return the value reset(6).