14 — Troubleshooting with the client activity log
14-4 Alcatel-Lucent 5620 Service Aware Manager, Release
Troubleshooting Guide 3HE 05723 TQZZA Edition 01
Table 14-2 Log file information
Note
(1)
The 5620 SAM also raises an alarm for log entries that are related to security.
14.2 Using the 5620 SAM Usage and Activity Records forms
The following procedures describe how to use the 5620 SAM Usage and Activity
Records form to correlate user requests and deployment activity.
Action Log file entries
Receive client request • date and time the log entry was created
• user who initiated the request
• request ID (supplied by the client)
• package-qualified class of the target object
• fully distinguished name of the target object
• name of the target object (if different from the fully
distinguished name
• name of the operation requested
• source of the request (GUI or XML OSS interface)
Completion of database update • date and time the log entry was created
• user who initiated the request
• request ID (supplied by the client)
• type of operation performed (insert, delete, or modify)
• fully distinguished name of the target object
• result of the update (success or failure)
Completion of deployment
operation
• date and time the log entry was created
• user who initiated the request
• request ID (supplied by the client)
• deployer ID
• deployment stage
• package-qualified class of the target object
• fully distinguished name of the target object
• result of the deployment (success or failure)
Failed authentication attempt,
either through native 5620 SAM
authentication or through an
external authentication
mechanism
(1)
• date and time the log entry was created
• name of the operator the event relates to
• type of event, for example, failed login or disabled
account
Disabling of a user account because
of too many failed authentication
attempts
(1)
Violation of user permissions
through the XML OSS interface
(1)
To Next Page
Loading...
