DOT3-OAM-MIB :: dot3OamEventLogType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsDOT3-OAM-MIBdot3OamEventLogType

dot3OamEventLogType

Module: DOT3-OAM-MIB

OID (symbolic): DOT3-OAM-MIB::dot3OamEventLogType

OID (numeric): 1.3.6.1.2.1.158.1.6.1.4

Node type: OBJECT-TYPE

Type: Unsigned32

Access: read-only

Description: The type of event that generated this entry in the event log. When the OUI is the IEEE 802.3 OUI of 0x0180C2, the following event types are defined: erroredSymbolEvent(1), erroredFramePeriodEvent(2), erroredFrameEvent(3), erroredFrameSecondsEvent(4), linkFault(256), dyingGaspEvent(257), criticalLinkEvent(258) The first four are considered threshold crossing events, as they are generated when a metric exceeds a given value within a specified window. The other three are not threshold crossing events.

When the OUI is not 71874 (0x0180C2 in hex), then some other organization has defined the event space. If event subtyping is known to the implementation, it may be reflected here. Otherwise, this value should return all F's (2^32 - 1).

What is dot3OamEventLogType?

This read-only value identifies which kind of OAM event was logged, e.g. erroredSymbolEvent(1), erroredFramePeriodEvent(2), erroredFrameEvent(3), erroredFrameSecondsEvent(4), linkFault(256), dyingGaspEvent(257), or criticalLinkEvent(258) under the standard IEEE OUI; the first four are threshold-crossing events, the rest are one-shot faults. An admin reads this to know what specifically triggered the log entry, e.g. distinguishing a dying-gasp power event from a routine symbol-error threshold crossing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.158.1.6.1.4
snmpwalk -v2c -c public <target> DOT3-OAM-MIB::dot3OamEventLogType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.158.1.6.1.4.1
snmpget -v2c -c public <target> DOT3-OAM-MIB::dot3OamEventLogType.1

Start monitoring Ethernet switch/access device supporting IEEE 802.3ah OAM (vendor-neutral IETF standard) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the DOT3-OAM-MIB::dot3OamEventLogType OID value, configure state conditions and alerts, and monitor any Ethernet switch/access device supporting IEEE 802.3ah OAM (vendor-neutral IETF standard) 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.158dot3OamMIBDOT3-OAM-MIB
1.3.6.1.2.1.158.1dot3OamObjectsDOT3-OAM-MIB
1.3.6.1.2.1.158.1.6dot3OamEventLogTableDOT3-OAM-MIB
1.3.6.1.2.1.158.1.6.1dot3OamEventLogEntryDOT3-OAM-MIB
1.3.6.1.2.1.158.1.6.1.4dot3OamEventLogTypeDOT3-OAM-MIB