The trace command displays details of service requests, confirmations, or errors. You need to specify the level of tracing you want to use.
trace full | none | trace-event-list ;
Traces everything. Full tracing degrades performance, so you should use it only during testing.
Turns off all tracing
A comma-separated list of one or more of the following trace options:
Displays authentication errors.
Displays certificate operations.
Traces local DXserver operations that were refused.
Similar to the x500 trace, but also includes tracing of the module flow inside the DSA.
Displays error messages of high severity. Compare with trace warn.
These events that may impact on the ability of DXserver to perform a requested operation. This is the default trace level.
We recommend that the error trace option is included in the set trace command during normal operation.
Traces detailed LDAP operations. The output can become quite large when searches return a large number of entries.
Traces any violation of size or time limits.
Displays a one-line summary containing the server request and result.
Displays detailed protocol tracing. The output can become quite large.
Displays statistical information for each minute the DSA is not idle.
Displays a one-line summary containing the service request and result.
Displays the time taken for successful operations.
To send this output to a separate file, use the set time-log command.
Displays update operations-add, delete, modify, and rename.
Displays error messages of moderate severity. Compare with trace error.
Warn messages usually represent a user error, rather than a problem with DXserver.
Displays the full details of the service request, confirmation, or error. This traces DAP, DSP, and LDAP operations. The output can become quite large when searches return a large number of entries.
Copyright © 2013 CA.
All rights reserved.