TELDAT-TRAP-EOAM-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TELDAT-TRAP-EOAM-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router EOAM (Ethernet OAM) event trap notifications.

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 TELDAT-TRAP-EOAM-MIB?

TELDAT-TRAP-EOAM-MIB is a Teldat (Spanish networking vendor) private enterprise MIB dedicated entirely to SNMP notifications generated by the Ethernet OAM (802.3ah/802.1ag-style) subsystem on Teldat routers. Rather than defining pollable counters, it defines trap/notification objects that report per-interface EOAM finite-state-machine (FSM) transitions and events across multiple EOAM instances (eoam1 through eoam5) on the device. This makes it a fault/event MIB used specifically to monitor the software-level health of the Ethernet OAM link-monitoring process — alerting operators in real time when an EOAM session's state machine changes or detects a fault, rather than reporting hardware sensors like temperature or power. It depends conceptually on the underlying Ethernet OAM protocol standards (IEEE 802.3ah/ITU-T Y.1731) that the FSM notifications describe. It is typically deployed on Teldat WAN/Ethernet access routers where Ethernet OAM monitors link continuity and fault detection between carrier-grade Ethernet endpoints. Engineers can download the TELDAT-TRAP-EOAM-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-EOAM-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

  • Teldat routers
  • Ethernet WAN access devices with 802.3ah/802.1ag OAM support

Monitoring Examples

An NMS receiving an SNMP trap referencing eoam1-interface, eoam1-fsm, and eoam1-event would use those varbinds to identify which Ethernet OAM session and finite-state-machine changed state, and what event triggered it (e.g. loss of OAM PDUs). Correlating eoam2-state or eoam3-event across the numbered EOAM instances lets an admin tell whether a single link or multiple monitored sessions are affected simultaneously. The eoamNotifications/eoamEventsGroup structures group these traps for selective trap-receiver filtering.

What Can Be Monitored

  • EOAM session interface identity
  • EOAM finite-state-machine state
  • EOAM fault/event type
  • per-session EOAM state across multiple instances
Imported Objects

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString

From TELDAT-MIB

telEventTrapsOBJECT-IDENTITY
OIDs

RFC description

Defines SNMP trap notifications for Ethernet OAM (Operations, Administration, Maintenance) events on Teldat devices.

Start monitoring Teldat routers, Ethernet WAN access devices with 802.3ah/802.1ag OAM (EOAM FSM state-change event traps) 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.

Download TELDAT-TRAP-EOAM-MIB