TELDAT-TRAP-DHCP-MIB

All MIBs › TELDAT-TRAP-DHCP-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

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

TELDAT-TRAP-DHCP-MIB is a Teldat proprietary, notification-only SNMP MIB that defines the trap varbinds emitted by the router's DHCP event subsystem, covering both DHCP relay and server functions. It groups numbered event definitions (dhcp3 through dhcp8, under dhcpEventsGroup/dhcpNotifications) carrying source and destination IP addresses, DHCP message type (Discover/Offer/Request/Ack-style values), and a generic parameter field (dhcp8-param). Operationally it is a fault/event monitor for the DHCP software service: it lets a management station learn asynchronously about specific DHCP transactions and message-type events, which is useful for diagnosing lease-assignment failures, DHCP relay misbehavior, or unexpected message types indicating a rogue or misconfigured DHCP server on the LAN. As with Teldat's other TRAP-* modules it depends on the standard SNMPv2-SMI/SNMPv2-TC notification conventions and Teldat's private enterprise OID tree. It is deployed on Teldat routers acting as DHCP relay agents or servers for branch-office LANs, where address-assignment problems need prompt visibility. Engineers can download the TELDAT-TRAP-DHCP-MIB file directly to load it into their MIB browser.

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

This module defines only notification objects and their varbinds rather than a polled lease table, so there is no GET-based monitoring scenario; it is trap-only. An SNMP trap receiver would examine dhcp5-message-type or dhcp6-message-type alongside dhcp5-source-ip-address/dhcp6-source-ip-address to see which DHCP message type passed between which client and server, and dhcp8-param for additional detail flagged by that specific event.

What Can Be Monitored

DHCP message-type events (Discover/Offer/Request/Ack)
DHCP transaction source/destination IP addresses

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

OID symbolic	OID numeric	Type	Access	Description
dhcpTrapsMIB	1.3.6.1.4.1.2007.1.4.133			This Module Information Base file is defined for managing received SNMP notifications generated by the DHCP event subsystem.
dhcpEventsGroup	1.3.6.1.4.1.2007.1.4.133.1
dhcpEventObjects3	1.3.6.1.4.1.2007.1.4.133.1.3			Event DHCP.3 Message generated when the router relays packets received from DHCP clients and addressed to DHCP servers.
IP dhcp3_source_ip_address	1.3.6.1.4.1.2007.1.4.133.1.3.1	IpAddress	accessible-for-notify	Parameter 'source-ip-address' in event DHCP.3
IP dhcp3_destination_ip_address	1.3.6.1.4.1.2007.1.4.133.1.3.2	IpAddress	accessible-for-notify	Parameter 'destination-ip-address' in event DHCP.3
dhcpEventObjects4	1.3.6.1.4.1.2007.1.4.133.1.4			Event DHCP.4 Message generated when the router relays packets received from DHCP servers and addressed to DHCP clients.
IP dhcp4_source_ip_address	1.3.6.1.4.1.2007.1.4.133.1.4.1	IpAddress	accessible-for-notify	Parameter 'source-ip-address' in event DHCP.4
IP dhcp4_destination_ip_address	1.3.6.1.4.1.2007.1.4.133.1.4.2	IpAddress	accessible-for-notify	Parameter 'destination-ip-address' in event DHCP.4
dhcpEventObjects5	1.3.6.1.4.1.2007.1.4.133.1.5			Event DHCP.5 DHCP message received in server from relay on an IP address.
STR dhcp5_message_type	1.3.6.1.4.1.2007.1.4.133.1.5.1	DisplayString	accessible-for-notify	Parameter 'message-type' in event DHCP.5
IP dhcp5_source_ip_address	1.3.6.1.4.1.2007.1.4.133.1.5.2	IpAddress	accessible-for-notify	Parameter 'source-ip-address' in event DHCP.5
dhcpEventObjects6	1.3.6.1.4.1.2007.1.4.133.1.6			Event DHCP.6 DHCP message received in server from host on an known IP address.
STR dhcp6_message_type	1.3.6.1.4.1.2007.1.4.133.1.6.1	DisplayString	accessible-for-notify	Parameter 'message-type' in event DHCP.6
IP dhcp6_source_ip_address	1.3.6.1.4.1.2007.1.4.133.1.6.2	IpAddress	accessible-for-notify	Parameter 'source-ip-address' in event DHCP.6
dhcpEventObjects7	1.3.6.1.4.1.2007.1.4.133.1.7			Event DHCP.7 DHCP message received in server any host on local subnet.
STR dhcp7_message_type	1.3.6.1.4.1.2007.1.4.133.1.7.1	DisplayString	accessible-for-notify	Parameter 'message-type' in event DHCP.7
dhcpEventObjects8	1.3.6.1.4.1.2007.1.4.133.1.8			Event DHCP.8 Message generated when server offer or send an acknowledge allocating an IP address.
STR dhcp8_message_type	1.3.6.1.4.1.2007.1.4.133.1.8.1	DisplayString	accessible-for-notify	Parameter 'message-type' in event DHCP.8
STR dhcp8_param	1.3.6.1.4.1.2007.1.4.133.1.8.2	DisplayString	accessible-for-notify	Parameter 'param' in event DHCP.8
IP dhcp8_destination_ip_address	1.3.6.1.4.1.2007.1.4.133.1.8.3	IpAddress	accessible-for-notify	Parameter 'destination-ip-address' in event DHCP.8
dhcpEventObjects11	1.3.6.1.4.1.2007.1.4.133.1.11			Event DHCP.11 Found HOST definition with unknown hardware type (neither ethernet nor token ring).
I32 dhcp11_HW_type	1.3.6.1.4.1.2007.1.4.133.1.11.1	Integer32	accessible-for-notify	Parameter 'HW-type' in event DHCP.11
dhcpEventObjects12	1.3.6.1.4.1.2007.1.4.133.1.12			Event DHCP.12 Error in the DHCP module.
STR dhcp12_message	1.3.6.1.4.1.2007.1.4.133.1.12.1	DisplayString	accessible-for-notify	Parameter 'message' in event DHCP.12
dhcpEventObjects13	1.3.6.1.4.1.2007.1.4.133.1.13			Event DHCP.13 Warnings in the DHCP module.
STR dhcp13_message	1.3.6.1.4.1.2007.1.4.133.1.13.1	DisplayString	accessible-for-notify	Parameter 'message' in event DHCP.13
dhcpEventObjects14	1.3.6.1.4.1.2007.1.4.133.1.14			Event DHCP.14 Common information on the standard operation of the DHCP server.
STR dhcp14_message	1.3.6.1.4.1.2007.1.4.133.1.14.1	DisplayString	accessible-for-notify	Parameter 'message' in event DHCP.14
dhcpEventObjects15	1.3.6.1.4.1.2007.1.4.133.1.15			Event DHCP.15 State change of a shared network which is controlled by a NSLA advisor.
I32 dhcp15_shared_id	1.3.6.1.4.1.2007.1.4.133.1.15.1	Integer32	accessible-for-notify	Parameter 'shared-id' in event DHCP.15
I32 dhcp15_nsla_advisor_id	1.3.6.1.4.1.2007.1.4.133.1.15.2	Integer32	accessible-for-notify	Parameter 'nsla-advisor-id' in event DHCP.15
STR dhcp15_state	1.3.6.1.4.1.2007.1.4.133.1.15.3	DisplayString	accessible-for-notify	Parameter 'state' in event DHCP.15
dhcpEventObjects16	1.3.6.1.4.1.2007.1.4.133.1.16			Event DHCP.16 State change of a DHCP relay agent because all its servers are not accesibles.
STR dhcp16_state	1.3.6.1.4.1.2007.1.4.133.1.16.1	DisplayString	accessible-for-notify	Parameter 'state' in event DHCP.16
I32 dhcp16_indicator	1.3.6.1.4.1.2007.1.4.133.1.16.2	Integer32	accessible-for-notify	Parameter 'indicator' in event DHCP.16
dhcpNotifications	1.3.6.1.4.1.2007.1.4.133.2
dhcpNotificationsPrefix	1.3.6.1.4.1.2007.1.4.133.2.0
NTF dhcpNotification1	1.3.6.1.4.1.2007.1.4.133.2.0.1			Notification of Event DHCP.1 Message: 'BOOTREQUEST packet received' The router has received a packet from a DHCP client requesting a response to a DHCP server.
NTF dhcpNotification2	1.3.6.1.4.1.2007.1.4.133.2.0.2			Notification of Event DHCP.2 Message: 'BOOTREPLY packet received' The router has received a packet from a DHCP server in response to a BOOTREQUEST.
NTF dhcpNotification3	1.3.6.1.4.1.2007.1.4.133.2.0.3			Notification of Event DHCP.3 Message: 'Relay BOOTREQUEST from $1 to DHCP server $2' Parameters list: $1: dhcp3-source-ip-address $2: dhcp3-destination-ip-address Message generated when the router relays packets received from DHCP clients and addressed to DHCP servers.
NTF dhcpNotification4	1.3.6.1.4.1.2007.1.4.133.2.0.4			Notification of Event DHCP.4 Message: 'Relay BOOTREPLAY from DHCP server $1 to DHCP client $2' Parameters list: $1: dhcp4-source-ip-address $2: dhcp4-destination-ip-address Message generated when the router relays packets received from DHCP servers and addressed to DHCP clients.
NTF dhcpNotification5	1.3.6.1.4.1.2007.1.4.133.2.0.5			Notification of Event DHCP.5 Message: 'DHCP $1 packet received from relay on $2' Parameters list: $1: dhcp5-message-type $2: dhcp5-source-ip-address DHCP message received in server from relay on an IP address.
NTF dhcpNotification6	1.3.6.1.4.1.2007.1.4.133.2.0.6			Notification of Event DHCP.6 Message: 'DHCP $1 packet received from host on $2' Parameters list: $1: dhcp6-message-type $2: dhcp6-source-ip-address DHCP message received in server from host on an known IP address.
NTF dhcpNotification7	1.3.6.1.4.1.2007.1.4.133.2.0.7			Notification of Event DHCP.7 Message: 'DHCP $1 packet received from any host on local subnet' Parameters list: $1: dhcp7-message-type DHCP message received in server any host on local subnet.
NTF dhcpNotification8	1.3.6.1.4.1.2007.1.4.133.2.0.8			Notification of Event DHCP.8 Message: 'DHCP $1 packet sent to a $2 host on $3' Parameters list: $1: dhcp8-message-type $2: dhcp8-param $3: dhcp8-destination-ip-address Message generated when server offer or send an acknowledge allocating an IP address.
NTF dhcpNotification9	1.3.6.1.4.1.2007.1.4.133.2.0.9			Notification of Event DHCP.9 Message: 'Packet BOOTREQUEST' Message generated when server receives a BOOTREQUEST.
NTF dhcpNotification10	1.3.6.1.4.1.2007.1.4.133.2.0.10			Notification of Event DHCP.10 Message: 'Sent Packet BOOTREPLY' Message generated when server sends a BOOTREPLY.
NTF dhcpNotification11	1.3.6.1.4.1.2007.1.4.133.2.0.11			Notification of Event DHCP.11 Message: 'Unknown Hardware type: $1' Parameters list: $1: dhcp11-HW-type Found HOST definition with unknown hardware type (neither ethernet nor token ring).
NTF dhcpNotification12	1.3.6.1.4.1.2007.1.4.133.2.0.12			Notification of Event DHCP.12 Message: 'error: $1' Parameters list: $1: dhcp12-message Error in the DHCP module.
NTF dhcpNotification13	1.3.6.1.4.1.2007.1.4.133.2.0.13			Notification of Event DHCP.13 Message: '$1' Parameters list: $1: dhcp13-message Warnings in the DHCP module.
NTF dhcpNotification14	1.3.6.1.4.1.2007.1.4.133.2.0.14			Notification of Event DHCP.14 Message: '$1' Parameters list: $1: dhcp14-message Common information on the standard operation of the DHCP server.
NTF dhcpNotification15	1.3.6.1.4.1.2007.1.4.133.2.0.15			Notification of Event DHCP.15 Message: 'Shared network $1 controlled by NLSA advisor $2 changes to $3' Parameters list: $1: dhcp15-shared-id $2: dhcp15-nsla-advisor-id $3: dhcp15-state State change of a shared network which is controlled by a NSLA advisor.
NTF dhcpNotification16	1.3.6.1.4.1.2007.1.4.133.2.0.16			Notification of Event DHCP.16 Message: 'DHCP relay goes $1 updating the level indicator $2' Parameters list: $1: dhcp16-state $2: dhcp16-indicator State change of a DHCP relay agent because all its servers are not accesibles.

RFC description

SNMP notifications for DHCP relay events on Teldat routers, tracking DHCP client and server message exchanges.

Start monitoring Teldat router (DHCP relay/server transaction 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-DHCP-MIB

What Is TELDAT-TRAP-DHCP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description