All MIBs › TPLINK-ETHERNETOAMEVENTLOG-MIB
Category: Link Layer and Ethernet Protocols
Description: Tracks TP-Link switch Ethernet OAM link event log entries and error statistics.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is TPLINK-ETHERNETOAMEVENTLOG-MIB?
This is a TP-Link private MIB for logging Ethernet OAM (802.3ah) event history on TP-Link managed switches, recording link-level OAM events such as link faults and errored-symbol/errored-frame notifications over time. No module description or sample objects were available in this batch, but based on its short description it would expose an event-log table of OAM error events with timestamps and error counters. It supports monitoring of hardware/link fault history, letting an admin review past link-level errors (rather than just current state) to identify intermittent physical-layer problems on a port. It builds on the IEEE 802.3ah Ethernet OAM standard's event-notification model, similar in spirit to the base Ethernet OAM MIB, though the exact dependency isn't visible from the available data. It is typically deployed on TP-Link managed switches for after-the-fact diagnosis of intermittent link problems reported by users, and a TPLINK-ETHERNETOAMEVENTLOG-MIB download is usually the first step toward loading it into a MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TPLINK-ETHERNETOAMEVENTLOG-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- TP-Link managed Ethernet switches
Monitoring Examples
No specific object names were available in the sampled data, so a concrete OID-level example cannot be honestly constructed; based on the module's stated purpose, an admin would generally expect to poll an OAM event-log table to review historical link-fault and error-frame events per port. Direct inspection of the raw MIB source would be needed to identify the actual table and object names for a precise monitoring scenario.
What Can Be Monitored
- historical Ethernet OAM error/event log entries (exact objects not confirmed)
Imported Objects
From RFC1155-SMI
| Counter |
From RFC1213-MIB
| ifIndex |
From SNMPv2-SMI
| Counter64 | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString |
| ethernetOamEventLog | OBJECT-IDENTITY |
How to Use in IPNetwork Monitor
Example using ethernetOamEventLogStatLocalSymbolPeriod OID:
OIDs
RFC description
Tracks Ethernet OAM (Operations, Administration, and Maintenance) event statistics per port on TP-Link switches. Logs symbol period, frame, and dying gasp events.
Start monitoring TP-Link managed Ethernet switches (OAM link-fault event-log history status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.