TELDAT-TRAP-IKE-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TELDAT-TRAP-IKE-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: IP Security and VPN, Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router IKE (Internet Key Exchange) 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-IKE-MIB?

TELDAT-TRAP-IKE-MIB is another Teldat vendor-specific SNMP notification module, this one dedicated to trap payloads generated by the router's IKE (Internet Key Exchange) event subsystem used in IPsec VPN negotiation. It defines a series of numbered notification variable sets (ike1 through ike9 in this excerpt) that carry the remote peer address and, for some events, an associated connection or template identifier. Like its AFS counterpart, it is used purely for event/fault monitoring of the VPN negotiation process — flagging failed or notable IKE exchanges with specific peers — rather than for tracking hardware health metrics such as CPU, memory, or temperature. It depends on the standard SNMPv2 notification framework (NOTIFICATION-TYPE, SNMPv2-CONF) for its structure and is complementary to a Teldat IPsec/IKE configuration MIB that would define policy objects, though that module is not shown here. It is deployed on Teldat routers terminating IPsec VPN tunnels, where operators watch these traps to detect peer-side negotiation failures or renegotiation storms. Engineers can download the TELDAT-TRAP-IKE-MIB file directly to load it into their MIB browser.

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

Monitoring Examples

An operator would watch for ikeNotifications carrying ike1-remote-addr (or ike2-remote-addr, ike6-remote-addr, etc.) to identify which VPN peer triggered the event, and for slots like ike1-template-number or ike2-connection/ike6-connection to correlate the event with a specific IKE policy template or active tunnel. Repeated traps citing the same ike-remote-addr value would suggest a peer failing to complete key negotiation, useful for diagnosing a flapping site-to-site VPN. As with the AFS module, this is trap-only — there is no walkable status table, only notifications rooted under ikeNotificationsPrefix within ikeEventsGroup.

What Can Be Monitored

  • IKE peer remote address
  • IKE template/policy number associated with event
  • IKE connection identifier
  • frequency of IKE trap notifications
  • which numbered IKE event slot fired
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 vendor-private MIB for IKE (Internet Key Exchange) protocol traps and event notifications.

Start monitoring Teldat router terminating IPsec VPN tunnels (IKE negotiation 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-IKE-MIB