EFM-COMMON-MIB :: dot3OamEventLogType

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › EFM-COMMON-MIB › dot3OamEventLogType

dot3OamEventLogType

Module: EFM-COMMON-MIB

OID (symbolic): EFM-COMMON-MIB::dot3OamEventLogType

OID (numeric): 1.3.6.1.2.1.9908.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 0x0180C2, 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 Fs (0xFFFFFFFF).

What is dot3OamEventLogType?

The specific event type recorded in this log entry; under the standard IEEE OUI (0x0180C2) this is one of erroredSymbolEvent(1), erroredFramePeriodEvent(2), erroredFrameEvent(3), erroredFrameSecondsEvent(4), linkFault(256), dyingGaspEvent(257), or criticalLinkEvent(258) — the first four are threshold-crossing events, the last three are not.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.2.1.9908.1.6.1.4
snmpwalk -v2c -c public <target> EFM-COMMON-MIB::dot3OamEventLogType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.2.1.9908.1.6.1.4.1
snmpget -v2c -c public <target> EFM-COMMON-MIB::dot3OamEventLogType.1

Start monitoring Ethernet access/carrier equipment supporting 802.3ah EFM OAM (vendor-neutral IETF standard) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the EFM-COMMON-MIB::dot3OamEventLogType OID value, configure state conditions and alerts, and monitor any Ethernet access/carrier equipment supporting 802.3ah EFM 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.2mgmtAPERTUS-NPG-MIB
1.3.6.1.2.1mib_2AXON-MIB
Numeric OIDNameModule
1.3.6.1.2.1.9908efmOamMIBEFM-COMMON-MIB
1.3.6.1.2.1.9908.1dot3OamMIBEFM-COMMON-MIB
1.3.6.1.2.1.9908.1.6dot3OamEventLogTableEFM-COMMON-MIB
1.3.6.1.2.1.9908.1.6.1dot3OamEventLogEntryEFM-COMMON-MIB
1.3.6.1.2.1.9908.1.6.1.4dot3OamEventLogTypeEFM-COMMON-MIB