TELDAT-TRAP-XN-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TELDAT-TRAP-XN-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router XN protocol 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-XN-MIB?

TELDAT-TRAP-XN-MIB is a Teldat enterprise SNMP module defining trap notifications for the XN protocol subsystem, an internal or legacy network-layer protocol handled by Teldat routers (the object names suggest a Novell IPX/XNS-style addressing scheme with network/node identifiers). The module carries protocol, source-network, source-node, and packet-length/checksum fields as notification bindings rather than a polling schema, making it purely event-driven. Operationally it gives visibility into XN protocol anomalies as they occur — malformed packets, checksum issues, or unexpected source addressing — serving as a fault-detection aid for this legacy protocol path rather than a source of general hardware/software health data. It is built on the shared Teldat enterprise MIB tree and standard SNMPv2 NOTIFICATION-TYPE conventions. Deployment is limited to Teldat routers that still bridge or route the XN protocol, with an NMS trap receiver subscribed to catch subsystem faults, typically after a TELDAT-TRAP-XN-MIB download from Teldat is loaded into the trap receiver's MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-XN-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 WAN router
  • Teldat router bridging/routing the legacy XN protocol

Monitoring Examples

A monitoring station receiving a trap with xn2-source-net, xn2-source-node, and xn2-TC populated can pinpoint exactly which node on which XN network segment triggered the event and what traffic class was involved. Similarly, xn3-cksum in a notification would flag a checksum-related anomaly on XN packet traffic through interface path 3. Because this MIB has no gettable runtime table, the only monitoring mechanism is subscribing to xnNotifications and inspecting the trap-bound variables.

What Can Be Monitored

  • XN protocol identifier per event
  • XN source network number
  • XN source node address
  • XN packet length
  • XN traffic class / checksum anomalies
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 MIB for managing SNMP traps and event notifications in the XN router platform.

Start monitoring Teldat router bridging/routing the legacy XN protocol (packet anomaly/checksum 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-XN-MIB