Diagnostics and troubleshooting

This chapter describes diagnostic and troubleshooting information.

You can use the scomu.cmd utility to perform different diagnostic tasks, as described in the following sections:

For troubleshooting info, refer to Troubleshooting.

Testing the connection to the SCOM management server
You can check whether the Microsoft SCOM agent can successfully connect to the SCOM management server using the scomu.cmd --sc-check command.
Testing the connectivity to storage systems
When required, you can check whether the Microsoft SCOM server can successfully connect to the storage system using the scomu.cmd --test command.
Setting the logging level
You can set the logging level for each management pack, so that the logging is performed only for events with severity level equivalent or lower than the severity level that you set.
Collecting diagnostic information
Use the scomu.cmd --diag command to collect diagnostic information and include the generated tar file when reporting the issue.
Checking the running environment
Use the scomu.cmd --precheck command to check whether the running environment of the management packs is correctly set, and whether the installed libraries are corrupted.
Troubleshooting
The following table lists some typical problems that you might encounter, along with the possible solution for each problem.

Parent topic: Version 2.2.0