TELDAT-TRAP-LDAP-MIB

All MIBs › TELDAT-TRAP-LDAP-MIB

Organization: Teldat, S.A.

Last Updated: 2014-01-20

Category: Teldat Router Management, Teldat Trap Notifications

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

TELDAT-TRAP-LDAP-MIB is a vendor MIB from Teldat, a Spanish/European router manufacturer, dedicated entirely to defining SNMP trap notifications generated by the router's LDAP event subsystem. Rather than exposing a polled data table, it defines a set of parallel notification groups (ldap1 through ldap4 and beyond) each carrying objects like sequence number, source/destination IP address, and operation type for a specific LDAP-related event stream. Its monitoring value is squarely in software-level event/fault monitoring: it lets an NMS detect and log LDAP protocol events (e.g., authentication or directory lookup activity/failures) as they occur on the router, rather than reporting on hardware health like temperature or power. It is a self-contained trap-definition MIB that depends on the router's underlying LDAP client/event subsystem for the data it reports, without apparent reliance on other standard MIBs beyond SNMPv2 notification conventions. It is typically deployed on Teldat routers in enterprise or carrier networks where LDAP-based authentication or directory integration needs event-level SNMP alerting. Engineers can download the TELDAT-TRAP-LDAP-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in TELDAT-TRAP-LDAP-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 NMS receiving a Teldat LDAP trap would read companion varbinds like ldap1-ldap-sequence to correlate the event with a sequence number, and ldap1-ip-source/ldap1-ip-destination to identify which LDAP server and client were involved in the event. The presence of ldap4-operation alongside ldap4-ip-source/ldap4-ip-destination suggests some trap variants also report which LDAP operation (e.g., bind, search) triggered the notification, useful for diagnosing repeated authentication failures against a directory server. The repeated ldap1..ldap4 naming pattern indicates multiple concurrent LDAP session/event slots are tracked independently.

What Can Be Monitored

LDAP event sequence number
LDAP source IP address
LDAP destination IP address
LDAP operation 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

OID symbolic	OID numeric	Type	Access	Description
ldapTrapsMIB	1.3.6.1.4.1.2007.1.4.146			This Module Information Base file is defined for managing received SNMP notifications generated by the LDAP event subsystem.
ldapEventsGroup	1.3.6.1.4.1.2007.1.4.146.1
ldapEventObjects1	1.3.6.1.4.1.2007.1.4.146.1.1			Event LDAP.1 Succesfull Bind Operation. A requested bind operation finished with a correct connection establishment.
I32 ldap1_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.1.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.1
STR ldap1_ip_source	1.3.6.1.4.1.2007.1.4.146.1.1.2	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.1
STR ldap1_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.1.3	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.1
ldapEventObjects2	1.3.6.1.4.1.2007.1.4.146.1.2			Event LDAP.2 Unsuccesfull bind operation between a source an a destination returned no room available. Bind was right but when trying to send connection information the router tell us there is no space left to send it.
I32 ldap2_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.2.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.2
STR ldap2_ip_source	1.3.6.1.4.1.2007.1.4.146.1.2.2	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.2
STR ldap2_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.2.3	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.2
ldapEventObjects3	1.3.6.1.4.1.2007.1.4.146.1.3			Event LDAP.3 Unsuccesfull bind operation between a source an a destination returned timeout.
I32 ldap3_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.3.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.3
STR ldap3_ip_source	1.3.6.1.4.1.2007.1.4.146.1.3.2	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.3
STR ldap3_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.3.3	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.3
ldapEventObjects4	1.3.6.1.4.1.2007.1.4.146.1.4			Event LDAP.4 An operation was requested by an LDAP client and LDAP Server returned OK.
I32 ldap4_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.4.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.4
STR ldap4_operation	1.3.6.1.4.1.2007.1.4.146.1.4.2	DisplayString	accessible-for-notify	Parameter 'operation' in event LDAP.4
STR ldap4_ip_source	1.3.6.1.4.1.2007.1.4.146.1.4.3	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.4
STR ldap4_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.4.4	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.4
ldapEventObjects5	1.3.6.1.4.1.2007.1.4.146.1.5			Event LDAP.5 An operation was requested by an LDAP client and LDAP Server returned any value meaning error.
I32 ldap5_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.5.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.5
STR ldap5_operation	1.3.6.1.4.1.2007.1.4.146.1.5.2	DisplayString	accessible-for-notify	Parameter 'operation' in event LDAP.5
STR ldap5_ip_source	1.3.6.1.4.1.2007.1.4.146.1.5.3	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.5
STR ldap5_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.5.4	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.5
STR ldap5_result_desc	1.3.6.1.4.1.2007.1.4.146.1.5.5	DisplayString	accessible-for-notify	Parameter 'result-desc' in event LDAP.5
I32 ldap5_result_code	1.3.6.1.4.1.2007.1.4.146.1.5.6	Integer32	accessible-for-notify	Parameter 'result-code' in event LDAP.5
STR ldap5_dn_affected	1.3.6.1.4.1.2007.1.4.146.1.5.7	DisplayString	accessible-for-notify	Parameter 'dn-affected' in event LDAP.5
STR ldap5_error_message	1.3.6.1.4.1.2007.1.4.146.1.5.8	DisplayString	accessible-for-notify	Parameter 'error-message' in event LDAP.5
ldapEventObjects6	1.3.6.1.4.1.2007.1.4.146.1.6			Event LDAP.6 All operations are composed by a set of sub-operations. The flow of this sub-operations is followed through a state machine. In this case a sub-operation appears when other was expected.
I32 ldap6_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.6.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.6
STR ldap6_actual_state	1.3.6.1.4.1.2007.1.4.146.1.6.2	DisplayString	accessible-for-notify	Parameter 'actual-state' in event LDAP.6
STR ldap6_expected_state	1.3.6.1.4.1.2007.1.4.146.1.6.3	DisplayString	accessible-for-notify	Parameter 'expected-state' in event LDAP.6
ldapEventObjects7	1.3.6.1.4.1.2007.1.4.146.1.7			Event LDAP.7 Unsuccesfull unbind operation between a source an a destination returned timeout.
I32 ldap7_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.7.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.7
STR ldap7_ip_source	1.3.6.1.4.1.2007.1.4.146.1.7.2	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.7
STR ldap7_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.7.3	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.7
ldapEventObjects8	1.3.6.1.4.1.2007.1.4.146.1.8			Event LDAP.8 An error occurred when allocating memory for a command buffer.
I32 ldap8_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.8.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.8
STR ldap8_command	1.3.6.1.4.1.2007.1.4.146.1.8.2	DisplayString	accessible-for-notify	Parameter 'command' in event LDAP.8
ldapEventObjects9	1.3.6.1.4.1.2007.1.4.146.1.9			Event LDAP.9 An LDAP Timeout occurred while performing request operation between client and server.
I32 ldap9_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.9.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.9
STR ldap9_ip_source	1.3.6.1.4.1.2007.1.4.146.1.9.2	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.9
STR ldap9_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.9.3	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.9
ldapEventObjects10	1.3.6.1.4.1.2007.1.4.146.1.10			Event LDAP.10 After a request operation an unexpected frame is received.
I32 ldap10_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.10.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.10
STR ldap10_operation	1.3.6.1.4.1.2007.1.4.146.1.10.2	DisplayString	accessible-for-notify	Parameter 'operation' in event LDAP.10
STR ldap10_ip_source	1.3.6.1.4.1.2007.1.4.146.1.10.3	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.10
STR ldap10_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.10.4	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.10
STR ldap10_frame_data	1.3.6.1.4.1.2007.1.4.146.1.10.5	DisplayString	accessible-for-notify	Parameter 'frame-data' in event LDAP.10
ldapEventObjects11	1.3.6.1.4.1.2007.1.4.146.1.11			Event LDAP.11 Shows the evolution on the LDAP TCP STATE MACHINE.
I32 ldap11_origin	1.3.6.1.4.1.2007.1.4.146.1.11.1	Integer32	accessible-for-notify	Parameter 'origin' in event LDAP.11
I32 ldap11_destination	1.3.6.1.4.1.2007.1.4.146.1.11.2	Integer32	accessible-for-notify	Parameter 'destination' in event LDAP.11
ldapEventObjects12	1.3.6.1.4.1.2007.1.4.146.1.12			Event LDAP.12 Shows the bytes sent to LDAP Server.
STR ldap12_bytes	1.3.6.1.4.1.2007.1.4.146.1.12.1	DisplayString	accessible-for-notify	Parameter 'bytes' in event LDAP.12
ldapEventObjects13	1.3.6.1.4.1.2007.1.4.146.1.13			Event LDAP.13 Shows the bytes received from LDAP Server.
STR ldap13_bytes	1.3.6.1.4.1.2007.1.4.146.1.13.1	DisplayString	accessible-for-notify	Parameter 'bytes' in event LDAP.13
ldapEventObjects14	1.3.6.1.4.1.2007.1.4.146.1.14			Event LDAP.14 When a search operation is requested, LDAP Server sends results to the client. This results are stored into buffers. Users can establish how many buffers are to be filled. When they are reached operation is finished OK.
I32 ldap14_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.14.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.14
STR ldap14_ip_source	1.3.6.1.4.1.2007.1.4.146.1.14.2	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.14
STR ldap14_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.14.3	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.14
ldapEventObjects15	1.3.6.1.4.1.2007.1.4.146.1.15			Event LDAP.15 When a search operation is requested, LDAP Server sends results to the client. This results are stored into buffers. The size of the reception buffer is determined by the window size. If Server sends data and client is no able to store it then this error occurs.
I32 ldap15_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.15.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.15
STR ldap15_ip_source	1.3.6.1.4.1.2007.1.4.146.1.15.2	DisplayString	accessible-for-notify	Parameter 'ip-source' in event LDAP.15
STR ldap15_ip_destination	1.3.6.1.4.1.2007.1.4.146.1.15.3	DisplayString	accessible-for-notify	Parameter 'ip-destination' in event LDAP.15
I32 ldap15_window_size	1.3.6.1.4.1.2007.1.4.146.1.15.4	Integer32	accessible-for-notify	Parameter 'window-size' in event LDAP.15
I32 ldap15_window_needed	1.3.6.1.4.1.2007.1.4.146.1.15.5	Integer32	accessible-for-notify	Parameter 'window-needed' in event LDAP.15
ldapEventObjects16	1.3.6.1.4.1.2007.1.4.146.1.16			Event LDAP.16 For any reason the client sends an Abandon Request to the LDAP Server.
I32 ldap16_ldap_sequence	1.3.6.1.4.1.2007.1.4.146.1.16.1	Integer32	accessible-for-notify	Parameter 'ldap-sequence' in event LDAP.16
STR ldap16_reason	1.3.6.1.4.1.2007.1.4.146.1.16.2	DisplayString	accessible-for-notify	Parameter 'reason' in event LDAP.16
ldapNotifications	1.3.6.1.4.1.2007.1.4.146.2
ldapNotificationsPrefix	1.3.6.1.4.1.2007.1.4.146.2.0
NTF ldapNotification1	1.3.6.1.4.1.2007.1.4.146.2.0.1			Notification of Event LDAP.1 Message: '($1) Connection established between $2 $3. Bind Operation completed successfully.' Parameters list: $1: ldap1-ldap-sequence $2: ldap1-ip-source $3: ldap1-ip-destination Succesfull Bind Operation. A requested bind operation finished with a correct connection establishment.
NTF ldapNotification2	1.3.6.1.4.1.2007.1.4.146.2.0.2			Notification of Event LDAP.2 Message: '($1) There is no room in the router to send data between $2 $3. Operation aborted.' Parameters list: $1: ldap2-ldap-sequence $2: ldap2-ip-source $3: ldap2-ip-destination Unsuccesfull bind operation between a source an a destination returned no room available. Bind was right but when trying to send connection information the router tell us there is no space left to send it.
NTF ldapNotification3	1.3.6.1.4.1.2007.1.4.146.2.0.3			Notification of Event LDAP.3 Message: '($1) Timeout expired for a bind operation between $2 as source IP and $3 as destiny IP' Parameters list: $1: ldap3-ldap-sequence $2: ldap3-ip-source $3: ldap3-ip-destination Unsuccesfull bind operation between a source an a destination returned timeout.
NTF ldapNotification4	1.3.6.1.4.1.2007.1.4.146.2.0.4			Notification of Event LDAP.4 Message: '($1) Data negotiation successfull. $2 sent $3 operation request $4 answered LDAPResult with OK message.' Parameters list: $1: ldap4-ldap-sequence $2: ldap4-operation $3: ldap4-ip-source $4: ldap4-ip-destination An operation was requested by an LDAP client and LDAP Server returned OK.
NTF ldapNotification5	1.3.6.1.4.1.2007.1.4.146.2.0.5			Notification of Event LDAP.5 Message: '($1) Requested $2 operation was unsuccessfull. $3 requests operation to $4.LDAPResult: $5 ($6).DN : $7.Message : $8' Parameters list: $1: ldap5-ldap-sequence $2: ldap5-operation $3: ldap5-ip-source $4: ldap5-ip-destination $5: ldap5-result-desc $6: ldap5-result-code $7: ldap5-dn-affected $8: ldap5-error-message An operation was requested by an LDAP client and LDAP Server returned any value meaning error.
NTF ldapNotification6	1.3.6.1.4.1.2007.1.4.146.2.0.6			Notification of Event LDAP.6 Message: '($1) Requested operation finished at this state ($2) when other ($3) was expected. State machine corrupted.' Parameters list: $1: ldap6-ldap-sequence $2: ldap6-actual-state $3: ldap6-expected-state All operations are composed by a set of sub-operations. The flow of this sub-operations is followed through a state machine. In this case a sub-operation appears when other was expected.
NTF ldapNotification7	1.3.6.1.4.1.2007.1.4.146.2.0.7			Notification of Event LDAP.7 Message: '($1) Disconnection for a bind operation between $2 as source IP and $3 as destiny IP' Parameters list: $1: ldap7-ldap-sequence $2: ldap7-ip-source $3: ldap7-ip-destination Unsuccesfull unbind operation between a source an a destination returned timeout.
NTF ldapNotification8	1.3.6.1.4.1.2007.1.4.146.2.0.8			Notification of Event LDAP.8 Message: '($1) Error allocating memory for the $2 operation in LDAP ObtenerComando' Parameters list: $1: ldap8-ldap-sequence $2: ldap8-command An error occurred when allocating memory for a command buffer.
NTF ldapNotification9	1.3.6.1.4.1.2007.1.4.146.2.0.9			Notification of Event LDAP.9 Message: '($1) LDAP Timeout occurred while performing request operation between $2 as client and $3 as server.' Parameters list: $1: ldap9-ldap-sequence $2: ldap9-ip-source $3: ldap9-ip-destination An LDAP Timeout occurred while performing request operation between client and server.
NTF ldapNotification10	1.3.6.1.4.1.2007.1.4.146.2.0.10			Notification of Event LDAP.10 Message: '($1) LDAP Error. Unexpected Frame from LDAP Server at operation $2 between $3 as client and $4 as server.Following data was received from LDAP Server:$5' Parameters list: $1: ldap10-ldap-sequence $2: ldap10-operation $3: ldap10-ip-source $4: ldap10-ip-destination $5: ldap10-frame-data After a request operation an unexpected frame is received.
NTF ldapNotification11	1.3.6.1.4.1.2007.1.4.146.2.0.11			Notification of Event LDAP.11 Message: 'FROM STATE $1 ---------> TO STATE $2' Parameters list: $1: ldap11-origin $2: ldap11-destination Shows the evolution on the LDAP TCP STATE MACHINE.
NTF ldapNotification12	1.3.6.1.4.1.2007.1.4.146.2.0.12			Notification of Event LDAP.12 Message: 'LDAP CLIENT:$1' Parameters list: $1: ldap12-bytes Shows the bytes sent to LDAP Server.
NTF ldapNotification13	1.3.6.1.4.1.2007.1.4.146.2.0.13			Notification of Event LDAP.13 Message: 'LDAP SERVER:$1' Parameters list: $1: ldap13-bytes Shows the bytes received from LDAP Server.
NTF ldapNotification14	1.3.6.1.4.1.2007.1.4.146.2.0.14			Notification of Event LDAP.14 Message: '($1) Search operation successfull. The operation between $2 and $3 finished OK afer the fullfillment of max results buffer.' Parameters list: $1: ldap14-ldap-sequence $2: ldap14-ip-source $3: ldap14-ip-destination When a search operation is requested, LDAP Server sends results to the client. This results are stored into buffers. Users can establish how many buffers are to be filled. When they are reached operation is finished OK.
NTF ldapNotification15	1.3.6.1.4.1.2007.1.4.146.2.0.15			Notification of Event LDAP.15 Message: '($1) Search operation unsuccessfull. The operation between $2 and $3 finished with error because window size is set as $4 bytes and $5 bytes is required.' Parameters list: $1: ldap15-ldap-sequence $2: ldap15-ip-source $3: ldap15-ip-destination $4: ldap15-window-size $5: ldap15-window-needed When a search operation is requested, LDAP Server sends results to the client. This results are stored into buffers. The size of the reception buffer is determined by the window size. If Server sends data and client is no able to store it then this error occurs.
NTF ldapNotification16	1.3.6.1.4.1.2007.1.4.146.2.0.16			Notification of Event LDAP.16 Message: '($1) LDAP Client sends an Abandon Request to LDAP Server. Reason is $2' Parameters list: $1: ldap16-ldap-sequence $2: ldap16-reason For any reason the client sends an Abandon Request to the LDAP Server.

RFC description

Provides SNMP traps for LDAP event subsystem on Teldat routing equipment. Monitors LDAP bind operations and connection events.

Start monitoring Teldat router (LDAP authentication/directory-lookup 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-LDAP-MIB

What Is TELDAT-TRAP-LDAP-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description