Sending secure communication logs to Veritas Technical Support
If you encounter a issue that is due to certificate deployment or secure communication, you can send a problem report and the relevant logs to Veritas Technical Support for assistance. Table: Logs to gather for secure communication issues provides a list of logs and the recommended logging levels that Veritas Technical Support may need to diagnose certain secure communication issues.
Table: Logs to gather for secure communication issues
Type of issue | Logs to gather |
|---|---|
Java console login failure | From the primary server:
From the entity on which the console was started:
|
Starting or unexpected termination of nbwmc on the primary server | All of the logs are located on the primary:
|
Certificate deployment during installation | From the server on which the certificates cannot be deployed:
From the primary server:
|
Backup failures due to failure to establish a secure connection | From the problem client or media server:
From the primary or media server rejecting the connection:
From the primary:
Note: Ensure that cURL logging is enabled. |
Disaster recovery (DR) package creation during catalog backup | From the primary server:
|
Web server tunnel (media) or web server router (client) | From the media server acting as the tunnel:
From the client/router:
From the primary server:
Note: Ensure that cURL logging is enabled. |