TELDAT-TRAP-LDAP-MIB
File:
TELDAT-TRAP-LDAP-MIB.mib (27271 bytes)
Imported modules
Imported symbols
Defined Values
| 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. |
| MODULE-IDENTITY |
|
|
|
| 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. |
| Status: current |
Access: read-write |
| OBJECT-IDENTITY |
|
|
|
| ldap1-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.1.1 |
| Parameter 'ldap-sequence' in event LDAP.1 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap1-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.1.2 |
| Parameter 'ip-source' in event LDAP.1 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap1-ip-destination |
1.3.6.1.4.1.2007.1.4.146.1.1.3 |
| Parameter 'ip-destination' in event LDAP.1 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap2-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.2.1 |
| Parameter 'ldap-sequence' in event LDAP.2 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap2-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.2.2 |
| Parameter 'ip-source' in event LDAP.2 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap2-ip-destination |
1.3.6.1.4.1.2007.1.4.146.1.2.3 |
| Parameter 'ip-destination' in event LDAP.2 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap3-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.3.1 |
| Parameter 'ldap-sequence' in event LDAP.3 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap3-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.3.2 |
| Parameter 'ip-source' in event LDAP.3 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap3-ip-destination |
1.3.6.1.4.1.2007.1.4.146.1.3.3 |
| Parameter 'ip-destination' in event LDAP.3 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap4-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.4.1 |
| Parameter 'ldap-sequence' in event LDAP.4 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap4-operation |
1.3.6.1.4.1.2007.1.4.146.1.4.2 |
| Parameter 'operation' in event LDAP.4 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap4-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.4.3 |
| Parameter 'ip-source' in event LDAP.4 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap4-ip-destination |
1.3.6.1.4.1.2007.1.4.146.1.4.4 |
| Parameter 'ip-destination' in event LDAP.4 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap5-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.5.1 |
| Parameter 'ldap-sequence' in event LDAP.5 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap5-operation |
1.3.6.1.4.1.2007.1.4.146.1.5.2 |
| Parameter 'operation' in event LDAP.5 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap5-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.5.3 |
| Parameter 'ip-source' in event LDAP.5 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap5-ip-destination |
1.3.6.1.4.1.2007.1.4.146.1.5.4 |
| Parameter 'ip-destination' in event LDAP.5 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap5-result-desc |
1.3.6.1.4.1.2007.1.4.146.1.5.5 |
| Parameter 'result-desc' in event LDAP.5 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap5-result-code |
1.3.6.1.4.1.2007.1.4.146.1.5.6 |
| Parameter 'result-code' in event LDAP.5 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap5-dn-affected |
1.3.6.1.4.1.2007.1.4.146.1.5.7 |
| Parameter 'dn-affected' in event LDAP.5 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap5-error-message |
1.3.6.1.4.1.2007.1.4.146.1.5.8 |
| Parameter 'error-message' in event LDAP.5 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap6-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.6.1 |
| Parameter 'ldap-sequence' in event LDAP.6 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap6-actual-state |
1.3.6.1.4.1.2007.1.4.146.1.6.2 |
| Parameter 'actual-state' in event LDAP.6 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap6-expected-state |
1.3.6.1.4.1.2007.1.4.146.1.6.3 |
| Parameter 'expected-state' in event LDAP.6 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap7-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.7.1 |
| Parameter 'ldap-sequence' in event LDAP.7 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap7-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.7.2 |
| Parameter 'ip-source' in event LDAP.7 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap7-ip-destination |
1.3.6.1.4.1.2007.1.4.146.1.7.3 |
| Parameter 'ip-destination' in event LDAP.7 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap8-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.8.1 |
| Parameter 'ldap-sequence' in event LDAP.8 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap8-command |
1.3.6.1.4.1.2007.1.4.146.1.8.2 |
| Parameter 'command' in event LDAP.8 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap9-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.9.1 |
| Parameter 'ldap-sequence' in event LDAP.9 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap9-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.9.2 |
| Parameter 'ip-source' in event LDAP.9 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap9-ip-destination |
1.3.6.1.4.1.2007.1.4.146.1.9.3 |
| Parameter 'ip-destination' in event LDAP.9 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap10-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.10.1 |
| Parameter 'ldap-sequence' in event LDAP.10 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap10-operation |
1.3.6.1.4.1.2007.1.4.146.1.10.2 |
| Parameter 'operation' in event LDAP.10 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap10-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.10.3 |
| Parameter 'ip-source' in event LDAP.10 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap10-frame-data |
1.3.6.1.4.1.2007.1.4.146.1.10.5 |
| Parameter 'frame-data' in event LDAP.10 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap11-origin |
1.3.6.1.4.1.2007.1.4.146.1.11.1 |
| Parameter 'origin' in event LDAP.11 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap11-destination |
1.3.6.1.4.1.2007.1.4.146.1.11.2 |
| Parameter 'destination' in event LDAP.11 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldapEventObjects12 |
1.3.6.1.4.1.2007.1.4.146.1.12 |
| Event LDAP.12
Shows the bytes sent to LDAP Server. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap12-bytes |
1.3.6.1.4.1.2007.1.4.146.1.12.1 |
| Parameter 'bytes' in event LDAP.12 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldapEventObjects13 |
1.3.6.1.4.1.2007.1.4.146.1.13 |
| Event LDAP.13
Shows the bytes received from LDAP Server. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap13-bytes |
1.3.6.1.4.1.2007.1.4.146.1.13.1 |
| Parameter 'bytes' in event LDAP.13 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap14-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.14.1 |
| Parameter 'ldap-sequence' in event LDAP.14 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap14-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.14.2 |
| Parameter 'ip-source' in event LDAP.14 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap15-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.15.1 |
| Parameter 'ldap-sequence' in event LDAP.15 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap15-ip-source |
1.3.6.1.4.1.2007.1.4.146.1.15.2 |
| Parameter 'ip-source' in event LDAP.15 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| ldap15-window-size |
1.3.6.1.4.1.2007.1.4.146.1.15.4 |
| Parameter 'window-size' in event LDAP.15 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap15-window-needed |
1.3.6.1.4.1.2007.1.4.146.1.15.5 |
| Parameter 'window-needed' in event LDAP.15 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| OBJECT-IDENTITY |
|
|
|
| ldap16-ldap-sequence |
1.3.6.1.4.1.2007.1.4.146.1.16.1 |
| Parameter 'ldap-sequence' in event LDAP.16 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
Integer32 |
|
|
| ldap16-reason |
1.3.6.1.4.1.2007.1.4.146.1.16.2 |
| Parameter 'reason' in event LDAP.16 |
| Status: current |
Access: accessible-for-notify |
| OBJECT-TYPE |
|
|
|
| |
DisplayString |
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|
| 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. |
| Status: current |
Access: accessible-for-notify |
| NOTIFICATION-TYPE |
|
|
|