Collecting data for IBM Power Virtualization Center problems
Sometimes you cannot solve a problem by troubleshooting the symptoms. In such cases, you must collect diagnostic data.
- Do the symptoms match any known problems? If so, has a fix or workaround been published?
- Can the problem be identified and resolved without a code fix?
- When does the problem occur?
The diagnostic data that you collect, and the sources from which you collect that data, are dependent on the type of problem that you are investigating. A base set of information is typically required for diagnosing and resolving a product-level or component-level problem. For specific symptoms, you must collect more problem-specific data.
When you submit a problem to IBM® Support, you must provide a base set of information, such as debug logs, screenshots, and a timestamp. The PowerVC diagnostic data collection tool, also called the powervc-diag tool, can be used to collect information. The tool is in the /usr/bin directory of your PowerVC installation, though you do not need to specify the path when invoking the tool. However, you must have root access to run it.
/usr/bin/powervc-log compute debug --enable. The debug logs are large, so after recreating the issue and collecting the logs, turn off debug logging.
--restartoption for changes to take effect.
- OpenStack service log files
- Contacting IBM Support
- Exchanging information with IBM Support