In addition to the monitoring tools in SPP, you can use the SPP to One Identity Safeguard for Privileged Sessions (SPS) join issues during the join process. Several SPS tools are described below.
If the join process fails for any reason, consult the system logs.
To view the Safeguard for Privileged Sessions logs, navigate to Basic Settings | Troubleshooting | View log files.
To show only the logs for the join process:
Use the buttons at the bottom of the dialog to perform the following tasks:
To increase the level of detail in the log, enable debug level logging at Basic Settings | Management | Debug logging | Enable debug logs.
When SPP and SPS report a successful join, but the connections don't work, view the SPS connection logs.
In Safeguard for Privileged Sessions, navigate to Basic Settings | Troubleshooting | View log files.
To show only the logs for the join process:
To change the verbosity level of SPS, complete the following steps in Safeguard for Privileged Sessions:
Select the desired log level from the Verbosity level field. The verbosity level ranges from 1 (no logging) to 10 (extremely detailed), with level 4 being the default normal level.
|
CAUTION: High verbosity levels generate a very large amount of log messages and might result in a very high load on the machine. Log levels set around 9 to 10, may result in logs with highly sensitive data, for example, passwords in plain text format. |
You can use the Diagnostics tools of SPP and SPS to test network issues. The following commands are available:
To execute one of the above commands on SPS, see Network troubleshooting.
To execute one of the above commands on SPP, see Diagnostics tools of SPP.
If you have an issue which needs Support assistance, you may be asked to provide an SPS Support Bundle. To collect system-state information (also known as a debug bundle) in One Identity Safeguard for Privileged Sessions, see Collecting logs and system information for error reporting.
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center