TELDAT-TRAP-ME-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsTELDAT-TRAP-ME-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router ME (management entity) 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-ME-MIB?

The TELDAT-TRAP-ME-MIB is a vendor-specific SNMP notification module for the 'ME' (management entity) subsystem on Teldat routers, defining traps tied to management/modem-style interactions including AT command exchanges. It exposes objects such as byte counts, an issued AT command string, interface identifiers, connection state, and error cause/bad-address information. Its monitoring value lies in the software status of the management/modem interface — confirming which AT command was sent and the resulting connection state, or flagging a bad address/cause code — useful when a Teldat router uses a modem-style or auxiliary management channel. It appears self-contained within Teldat's enterprise tree with no evident external MIB dependency. It would be deployed wherever a Teldat router's management entity/modem interface (e.g. out-of-band or dial-backup management) needs event-level visibility. Engineers can download the TELDAT-TRAP-ME-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-ME-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 router (management entity / modem interface)

Monitoring Examples

A trap containing me2-atCommand alongside me2-state and me2-interface shows exactly which AT command was issued on a given interface and what connection state resulted, useful for diagnosing a failed modem handshake. me4-cause together with me4-state and me4-interface reveals why a management-entity connection dropped or failed on that interface, and me3-bad-addr flags an invalid address encountered during the same subsystem's operation.

What Can Be Monitored

  • AT command issued
  • connection/interface state
  • bytes transferred
  • failure cause code
  • bad address indication
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

Teldat ME event subsystem MIB for serial terminal and AT command notifications.

Start monitoring Teldat router, management entity/modem interface (AT command/connection-state 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-ME-MIB