TELDAT-TRAP-DHCL-MIB

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › TELDAT-TRAP-DHCL-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

Description: Defines Teldat router DHCL (DHCP client) 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-DHCL-MIB?

This is a Teldat-proprietary notification MIB defining SNMP trap events generated by the DHCP client (DHCL) subsystem on Teldat routers. It exposes fault/event data rather than polled counters - the trap objects carry details such as the affected interface, port, message type, and failure reason whenever a DHCP client event occurs. It is used purely for software-status monitoring of the DHCP client process: administrators use these traps to detect lease failures, interface-specific DHCP problems, or unexpected client state transitions as they happen, rather than by periodic polling. It has no explicit dependency on external IETF DHCP MIBs, being a Teldat-internal event-notification scheme layered on the standard SNMP notification framework. It is deployed on Teldat routers acting as DHCP clients on WAN or LAN interfaces, typically in branch-office deployments relying on dynamic addressing from an ISP or upstream DHCP server, where TELDAT-TRAP-DHCL-MIB SNMP monitoring provides the trap-driven visibility needed to catch lease failures as they happen.

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

A NOC would subscribe to dhclNotifications and inspect varbinds such as dhcl4-interface and dhcl5-message-type to identify which router interface failed to obtain or renew a DHCP lease and what kind of message was involved. The dhcl6-reason and dhcl7-reason objects supply a coded or textual reason for a failure, letting an admin distinguish a timeout from a NAK response. Because these are traps rather than polled counters, monitoring relies on a trap receiver correlating dhcl1-generic-info through dhcl8-message-type objects across successive DHCP client events on a given interface.

What Can Be Monitored

  • DHCP client lease events
  • affected interface/port
  • DHCP message type
  • failure/close reason codes
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 DHCP trap/notification management; defines DHCP-related alarms and event notifications on Teldat routing equipment.

Start monitoring Teldat routers 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-DHCL-MIB