HPN-ICF-EFM-COMMON-MIB :: hpnicfDot3OamEventLogType

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsHPN-ICF-EFM-COMMON-MIBhpnicfDot3OamEventLogType

hpnicfDot3OamEventLogType

Module: HPN-ICF-EFM-COMMON-MIB

OID (symbolic): HPN-ICF-EFM-COMMON-MIB::hpnicfDot3OamEventLogType

OID (numeric): 1.3.6.1.4.1.11.2.14.11.15.2.42.3.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 hpnicfDot3OamEventLogType?

This is the specific event type for this log entry. Under the standard IEEE 802.3 OUI, values include the four threshold-crossing events erroredSymbolEvent(1), erroredFramePeriodEvent(2), erroredFrameEvent(3), erroredFrameSecondsEvent(4), plus the non-threshold events linkFault(256), dyingGaspEvent(257), and criticalLinkEvent(258); under a non-802.3 OUI it may reflect a vendor-defined type or read all-Fs (0xFFFFFFFF) if unknown. Admins use this to identify exactly what kind of link problem an event-log row represents, notably distinguishing a dying-gasp (power-loss) event from an ordinary threshold crossing.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.6.1.4
snmpwalk -v2c -c public <target> HPN-ICF-EFM-COMMON-MIB::hpnicfDot3OamEventLogType

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.6.1.4.1
snmpget -v2c -c public <target> HPN-ICF-EFM-COMMON-MIB::hpnicfDot3OamEventLogType.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> hpnicfDot3OamEventLogType.1

Start monitoring HP/H3C Comware switch or router (802.3ah Ethernet OAM, first-mile link) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the HPN-ICF-EFM-COMMON-MIB::hpnicfDot3OamEventLogType OID value, configure state conditions and alerts, and monitor any HP/H3C Comware switch or router (802.3ah Ethernet OAM, first-mile link) from a single console.

OID Breakdown

Upper-level ancestors (13 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.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.11hpCLJ8500-MIB
1.3.6.1.4.1.11.2nmCLJ8500-MIB
1.3.6.1.4.1.11.2.14icfCONFIG-MIB
1.3.6.1.4.1.11.2.14.11hpicfObjectsCONFIG-MIB
1.3.6.1.4.1.11.2.14.11.15hpnicfHPN-ICF-OID-MIB
1.3.6.1.4.1.11.2.14.11.15.2hpnicfCommonHPN-ICF-OID-MIB
1.3.6.1.4.1.11.2.14.11.15.2.42hpnicfEponHPN-ICF-OID-MIB
Numeric OIDNameModule
1.3.6.1.4.1.11.2.14.11.15.2.42.3hpnicfEfmOamMIBHPN-ICF-EFM-COMMON-MIB
1.3.6.1.4.1.11.2.14.11.15.2.42.3.1hpnicfDot3OamMIBHPN-ICF-EFM-COMMON-MIB
1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.6hpnicfDot3OamEventLogTableHPN-ICF-EFM-COMMON-MIB
1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.6.1hpnicfDot3OamEventLogEntryHPN-ICF-EFM-COMMON-MIB
1.3.6.1.4.1.11.2.14.11.15.2.42.3.1.6.1.4hpnicfDot3OamEventLogTypeHPN-ICF-EFM-COMMON-MIB