TELDAT-TRAP-UDP-MIB

All MIBs › TELDAT-TRAP-UDP-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

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

This Teldat-proprietary MIB defines SNMP trap notifications for anomalous UDP-layer events observed by Teldat routers, such as checksum mismatches and other transport-level conditions. It exposes event data including source and destination IP addresses, port numbers, packet length, the incoming interface, and both calculated and received checksum values for a flagged datagram. It functions as a software-level network-health monitor rather than a hardware monitor, letting administrators catch corrupted or malformed UDP traffic, unexpected port activity, or datagram length anomalies as they occur. It has no formal dependency beyond the standard UDP protocol (RFC 768), whose fields it mirrors in trap form. It is deployed on Teldat routers wherever detailed transport-layer diagnostics are needed, such as troubleshooting flaky WAN links or detecting malformed traffic from misbehaving hosts. Engineers can download the TELDAT-TRAP-UDP-MIB file directly to load it into their MIB browser.

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

An operator would correlate udp1-source-ip-address, udp1-destination-ip-address, and udp1-port-number to identify which flow triggered a UDP event, while udp4-calculated-checksum versus udp4-received-checksum exposes a checksum mismatch indicating packet corruption in transit. udp3-source-ip-address and udp3-length would be checked together to catch datagrams with abnormal lengths, and udp5-incoming-interface pinpoints which router interface received the offending traffic. These traps are especially useful for isolating intermittent WAN-link corruption that standard interface counters wouldn't distinguish from packet loss.

What Can Be Monitored

UDP source/destination IP and port
datagram length anomalies
checksum mismatches
incoming interface for flagged traffic

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
udpTrapsMIB	1.3.6.1.4.1.2007.1.4.13			This Module Information Base file is defined for managing received SNMP notifications generated by the UDP event subsystem.
udpEventsGroup	1.3.6.1.4.1.2007.1.4.13.1
udpEventObjects1	1.3.6.1.4.1.2007.1.4.13.1.1			Event UDP.1 This message is generated when a packet is discarded because UDP is not installed in the router. The packet was for the broadcast address.
IP udp1_source_ip_address	1.3.6.1.4.1.2007.1.4.13.1.1.1	IpAddress	accessible-for-notify	Parameter 'source-ip-address' in event UDP.1
IP udp1_destination_ip_address	1.3.6.1.4.1.2007.1.4.13.1.1.2	IpAddress	accessible-for-notify	Parameter 'destination-ip-address' in event UDP.1
I32 udp1_port_number	1.3.6.1.4.1.2007.1.4.13.1.1.3	Integer32	accessible-for-notify	Parameter 'port-number' in event UDP.1
udpEventObjects2	1.3.6.1.4.1.2007.1.4.13.1.2			Event UDP.2 This message is generated when a packet is discarded because UDP is not installed in the router. The packet was addressed to the router.
IP udp2_source_ip_address	1.3.6.1.4.1.2007.1.4.13.1.2.1	IpAddress	accessible-for-notify	Parameter 'source-ip-address' in event UDP.2
IP udp2_destination_ip_address	1.3.6.1.4.1.2007.1.4.13.1.2.2	IpAddress	accessible-for-notify	Parameter 'destination-ip-address' in event UDP.2
I32 udp2_port_number	1.3.6.1.4.1.2007.1.4.13.1.2.3	Integer32	accessible-for-notify	Parameter 'port-number' in event UDP.2
udpEventObjects3	1.3.6.1.4.1.2007.1.4.13.1.3			Event UDP.3 This message is generated when a packet is discarded because it had an UDP length greater than its IP length.
IP udp3_source_ip_address	1.3.6.1.4.1.2007.1.4.13.1.3.1	IpAddress	accessible-for-notify	Parameter 'source-ip-address' in event UDP.3
I32 udp3_length	1.3.6.1.4.1.2007.1.4.13.1.3.2	Integer32	accessible-for-notify	Parameter 'length' in event UDP.3
udpEventObjects4	1.3.6.1.4.1.2007.1.4.13.1.4			Event UDP.4 This message is generated when a packet is discarded because it had a bad checksum.
I32 udp4_calculated_checksum	1.3.6.1.4.1.2007.1.4.13.1.4.1	Integer32	accessible-for-notify	Parameter 'calculated-checksum' in event UDP.4
I32 udp4_received_checksum	1.3.6.1.4.1.2007.1.4.13.1.4.2	Integer32	accessible-for-notify	Parameter 'received-checksum' in event UDP.4
udpEventObjects5	1.3.6.1.4.1.2007.1.4.13.1.5			Event UDP.5 This message is generated when a broadcast UDP packet is received
STR udp5_incoming_interface	1.3.6.1.4.1.2007.1.4.13.1.5.1	DisplayString	accessible-for-notify	Parameter 'incoming-interface' in event UDP.5
IP udp5_source_ip_address	1.3.6.1.4.1.2007.1.4.13.1.5.2	IpAddress	accessible-for-notify	Parameter 'source-ip-address' in event UDP.5
I32 udp5_source_udp_port	1.3.6.1.4.1.2007.1.4.13.1.5.3	Integer32	accessible-for-notify	Parameter 'source-udp-port' in event UDP.5
IP udp5_destination_ip_address	1.3.6.1.4.1.2007.1.4.13.1.5.4	IpAddress	accessible-for-notify	Parameter 'destination-ip-address' in event UDP.5
I32 udp5_destination_udp_port	1.3.6.1.4.1.2007.1.4.13.1.5.5	Integer32	accessible-for-notify	Parameter 'destination-udp-port' in event UDP.5
udpEventObjects6	1.3.6.1.4.1.2007.1.4.13.1.6			Event UDP.6 This message is generated when a broadcast UDP packet is being forwarded to another destination address on the specified vrf.
IP udp6_next_hop	1.3.6.1.4.1.2007.1.4.13.1.6.1	IpAddress	accessible-for-notify	Parameter 'next-hop' in event UDP.6
STR udp6_vrf_next_hop	1.3.6.1.4.1.2007.1.4.13.1.6.2	DisplayString	accessible-for-notify	Parameter 'vrf-next-hop' in event UDP.6
udpEventObjects7	1.3.6.1.4.1.2007.1.4.13.1.7			Event UDP.7 This message is generated when a echo-responder service is waiting for data on a UDP port.
I32 udp7_udp_port	1.3.6.1.4.1.2007.1.4.13.1.7.1	Integer32	accessible-for-notify	Parameter 'udp-port' in event UDP.7
udpEventObjects9	1.3.6.1.4.1.2007.1.4.13.1.9			Event UDP.9 This message is generated when an echo-request UDP packet is received
IP udp9_client_address	1.3.6.1.4.1.2007.1.4.13.1.9.1	IpAddress	accessible-for-notify	Parameter 'client-address' in event UDP.9
I32 udp9_client_port	1.3.6.1.4.1.2007.1.4.13.1.9.2	Integer32	accessible-for-notify	Parameter 'client-port' in event UDP.9
I32 udp9_data_len	1.3.6.1.4.1.2007.1.4.13.1.9.3	Integer32	accessible-for-notify	Parameter 'data-len' in event UDP.9
udpNotifications	1.3.6.1.4.1.2007.1.4.13.2
udpNotificationsPrefix	1.3.6.1.4.1.2007.1.4.13.2.0
NTF udpNotification1	1.3.6.1.4.1.2007.1.4.13.2.0.1			Notification of Event UDP.1 Message: 'Packet from $1 for $2 port $3, no server' Parameters list: $1: udp1-source-ip-address $2: udp1-destination-ip-address $3: udp1-port-number This message is generated when a packet is discarded because UDP is not installed in the router. The packet was for the broadcast address.
NTF udpNotification2	1.3.6.1.4.1.2007.1.4.13.2.0.2			Notification of Event UDP.2 Message: 'Packet from $1 for $2 port $3, no server' Parameters list: $1: udp2-source-ip-address $2: udp2-destination-ip-address $3: udp2-port-number This message is generated when a packet is discarded because UDP is not installed in the router. The packet was addressed to the router.
NTF udpNotification3	1.3.6.1.4.1.2007.1.4.13.2.0.3			Notification of Event UDP.3 Message: 'Discarded packet from $1, bad length $2' Parameters list: $1: udp3-source-ip-address $2: udp3-length This message is generated when a packet is discarded because it had an UDP length greater than its IP length.
NTF udpNotification4	1.3.6.1.4.1.2007.1.4.13.2.0.4			Notification of Event UDP.4 Message: 'Bad checksum - calculated $1, received $2' Parameters list: $1: udp4-calculated-checksum $2: udp4-received-checksum This message is generated when a packet is discarded because it had a bad checksum.
NTF udpNotification5	1.3.6.1.4.1.2007.1.4.13.2.0.5			Notification of Event UDP.5 Message: 'Broadcast packet received on interface $1 from $2 port $3 for $4 port $5' Parameters list: $1: udp5-incoming-interface $2: udp5-source-ip-address $3: udp5-source-udp-port $4: udp5-destination-ip-address $5: udp5-destination-udp-port This message is generated when a broadcast UDP packet is received
NTF udpNotification6	1.3.6.1.4.1.2007.1.4.13.2.0.6			Notification of Event UDP.6 Message: 'Broadcast packet forwarded to $1 on vrf $2' Parameters list: $1: udp6-next-hop $2: udp6-vrf-next-hop This message is generated when a broadcast UDP packet is being forwarded to another destination address on the specified vrf.
NTF udpNotification7	1.3.6.1.4.1.2007.1.4.13.2.0.7			Notification of Event UDP.7 Message: 'Waiting for data on UPD PORT $1' Parameters list: $1: udp7-udp-port This message is generated when a echo-responder service is waiting for data on a UDP port.
NTF udpNotification8	1.3.6.1.4.1.2007.1.4.13.2.0.8			Notification of Event UDP.8 Message: 'Service echo-responder UDP stopped' The service echo-responder UDP was stopped due to an user request.
NTF udpNotification9	1.3.6.1.4.1.2007.1.4.13.2.0.9			Notification of Event UDP.9 Message: 'Received echo-request from $1 port $2, data len $3.' Parameters list: $1: udp9-client-address $2: udp9-client-port $3: udp9-data-len This message is generated when an echo-request UDP packet is received

RFC description

UDP event subsystem SNMP trap and notification management for Teldat routers.

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-UDP-MIB

What Is TELDAT-TRAP-UDP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description