TELDAT-TRAP-NAPT-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TELDAT-TRAP-NAPT-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router NAPT (Network Address Port Translation) 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-NAPT-MIB?

TELDAT-TRAP-NAPT-MIB is a vendor-specific SNMP module from Teldat, a Spanish networking equipment manufacturer, that defines trap notifications generated by the NAPT (Network Address and Port Translation) subsystem on Teldat routers. It exposes objects describing the internal and external IP addresses and ports (or identifiers) involved in address/port translation events across up to three NAPT instances, plus grouping objects for the notification set itself. This MIB is a software/networking-status MIB rather than a hardware one: it is used to monitor the correct operation of NAT translation on the router, alerting administrators when translation mappings are created or behave unexpectedly, which can reveal connectivity or address-pool exhaustion problems. It depends on Teldat's own enterprise MIB tree and trap-notification conventions rather than a shared IETF NAT MIB. It is typically deployed on Teldat routers performing NAPT/NAT for branch-office or SMB WAN connections where visibility into address translation events is needed for troubleshooting. Engineers can download the TELDAT-TRAP-NAPT-MIB file directly to load it into their MIB browser.

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

Monitoring Examples

An administrator would subscribe to naptNotifications carrying napt1-internal-ip, napt1-internal-port, napt1-external-ip, and napt1-external-port to see exactly which internal host and port were mapped to which external address/port at the moment of a NAPT event. Comparable objects for a second and third NAPT context, such as napt2-external-ip/napt2-internal-port and napt3-internal-ident/napt3-external-ident, allow the same visibility across multiple translation instances on a multi-context router. A flood of naptNotifications referencing the same napt1-internal-ip in a short window could indicate a misbehaving client exhausting the port-translation pool.

What Can Be Monitored

  • NAPT internal-to-external IP/port mappings
  • per-NAPT-instance translation events
  • NAT session identifiers
  • notification/trap volume for NAT events
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

SNMP notification definitions for NAPT (Network Address Port Translation) events on Teldat devices.

Start monitoring Teldat routers performing NAPT/NAT (address/port translation 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-NAPT-MIB