All MIBs › TELDAT-TRAP-STUN-MIB
Organization: Teldat, S.A.
Last Updated: 2014-01-20
Category: Remote Access and Serial WAN, Teldat Router Management, Teldat Trap Notifications
Description: Defines Teldat router STUN (Simple Traversal of UDP through NAT) 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-STUN-MIB?
TELDAT-TRAP-STUN-MIB is a vendor-specific MIB from Teldat, a manufacturer of enterprise routers, defining SNMP trap notifications for the STUN (Simple Traversal of UDP through NAT) subsystem. Rather than exposing polled runtime counters, it primarily models a sequence of trap/notification objects describing state transitions and connection details of up to three tracked STUN sessions or peers. Its principal monitoring value is fault and status detection: it lets an NMS learn, via trap, that a STUN session has changed state along with the peer's IP address, port, and session ID, which is useful for diagnosing NAT-traversal or VPN connectivity issues on Teldat routers. It does not define general hardware health objects like temperature or CPU load; it is narrowly scoped to STUN event notification and relies on standard SNMPv2 notification conventions. It is typically deployed alongside a Teldat router's core MIBs in an NMS configured to receive Teldat-specific traps for network connectivity troubleshooting. Engineers can download the TELDAT-TRAP-STUN-MIB file directly to load it into their MIB browser.
IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-STUN-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
- Teldat VPN/NAT-traversal gateway
Monitoring Examples
An admin would configure a trap receiver to catch stunNotifications, carrying varbinds like stun1-state, stun2-ip, stun2-port, stun2-id, and stun3-type/stun3-ip/stun3-port for up to three tracked STUN peers. A trap showing stun1-state transitioning to a failure value alongside an unexpected stun2-ip would indicate a NAT-traversal session dropped or reassigned, useful for diagnosing VoIP or VPN flapping. Since the module is trap-oriented, diagnostic value comes mainly from correlating notification payload fields across the stunEventsGroup rather than continuous polling.
What Can Be Monitored
- STUN session state
- STUN peer IP address
- STUN peer port
- STUN session/connection ID
- STUN event type
Imported Objects
From SNMPv2-SMI
| Integer32 | |
| IpAddress | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DisplayString |
From TELDAT-MIB
| telEventTraps | OBJECT-IDENTITY |
OIDs
RFC description
Teldat vendor-private MIB defining SNMP trap definitions for STUN (Serial Tunneling) protocol management on Teldat routers.
Start monitoring Teldat VPN/NAT-traversal gateway (STUN session 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.