DOT3-MAU-MIB :: rpMauStatus

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsDOT3-MAU-MIBrpMauStatus

rpMauStatus

Module: DOT3-MAU-MIB

OID (symbolic): DOT3-MAU-MIB::rpMauStatus

OID (numeric): 1.3.6.1.2.1.26.1.1.1.5

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-write

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 rpMauMediaAvailable 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 rpMauJabberState and rpMauMediaAvailable 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.

What is rpMauStatus?

Controls or reports the MAU's operating state: operational(3) means it's fully functional, standby(4) idles the transmitter, shutdown(5) behaves as if powered off, and writing reset(6) power-cycles the MAU -- admins use this to remotely force-reset a misbehaving transceiver without physically touching the hardware.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.26.1.1.1.5
snmpwalk -v2c -c public <target> DOT3-MAU-MIB::rpMauStatus

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.26.1.1.1.5.1
snmpget -v2c -c public <target> DOT3-MAU-MIB::rpMauStatus.1

Set instance 1 (SNMPv2c):

snmpset -v2c -c private <target> 1.3.6.1.2.1.26.1.1.1.5.1 i <value>

Start monitoring Network equipment with IEEE 802.3 MAU transceivers (vendor-neutral IETF standard RFC 4836) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DOT3-MAU-MIB::rpMauStatus OID value, configure state conditions and alerts, and monitor any Network equipment with IEEE 802.3 MAU transceivers (vendor-neutral IETF standard RFC 4836) from a single console.

OID Breakdown

Upper-level ancestors (6 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.2mgmtAXON-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.26snmpDot3MauMgtDOT3-MAU-MIB
1.3.6.1.2.1.26.1dot3RpMauBasicGroupDOT3-MAU-MIB
1.3.6.1.2.1.26.1.1rpMauTableDOT3-MAU-MIB
1.3.6.1.2.1.26.1.1.1rpMauEntryDOT3-MAU-MIB
1.3.6.1.2.1.26.1.1.1.5rpMauStatusDOT3-MAU-MIB