HP Integrity Virtual Server Manager 6.0 User Guide

does not trust the certificate from the virtual partition, then the certificate is not in the keystore,
has expired, did not match the virtual partition name, or is otherwise invalid. For information
about trusted certificates, see “Trusted certificates” (page 15).
If the WBEM provider is unresponsive, you might need to restart it.
• No Data indicates one of the following:
Data is being collected, but it can take up to 10 minutes to display utilization data.◦
◦ The virtual partition is not started, not booted, or cannot be contacted by the system on
which Virtual Server Manager is running.
◦ The VSP has no WBEM credentials for collecting the data from the virtual partition.
Normally, this is only seen for invalid or missing WBEM credentials for a Windows VM
guest. See the discussion of the No Perm label.For more information about WBEM
credentials, see “Setting security credentials” (page 12).
For more information about problems displaying data (data is out of date, incomplete, or
missing), see “Troubleshooting virtual partition problems” (page 128).
• No Perm. indicates that the VSP lacks or has invalid WBEM credentials for collecting the
data from the virtual partition.
• Timed Out indicates that Virtual Server Manager attempted to retrieve utilization data but
received no response from the WBEM provider on the virtual partition because of one of the
following situations:
◦ The WBEM provider for the data is not running, is not installed, or is disabled on the
virtual partition.
◦ Network problems are preventing a timely response.
For more information about collecting and viewing utilization data, see Chapter 8 (page 113).
Troubleshooting virtual partition problems
This section discusses problems that might occur when using Virtual Server Manager to create,
start, or modify a virtual partition or to display virtual partition data. Also included are ways for
resolving these problems.
• Utilization data for OpenVMS guests is not displayed
The utilization data for OpenVMS guests may not be visible after the first installation of the
OpenVMS operating system or after rebooting the OpenVMS guests. This is because, by
default, the TCP/IP and WBEM Provider services do not start automatically after rebooting
the OpenVMS guest machine.
The TCP/IP, the WBEM Services, and the Utilization Provider products are not installed by
default on an OpenVMS guest. Ensure that the TCP/IP, the WBEM services, and the Utilization
Provider products are installed, configured, and started on the guest. After rebooting the guest,
verify if the TCP/IP and WBEM services have been started. If not, restart TCP/IP and/or WBEM
services manually or add the command in the startup script so that they start automatically
when the OpenVMS guest reboots. For more information, see the OpenVMS documentation
on setting up TCP/IP and WBEM Provider services.
• Failure creating a virtual partition
When using the Create Virtual Partitions wizard, a number of warning or error conditions can
prevent the virtual partition from being created. However, if the Create VM even if resources
are insufficient, missing or unavailable check box is selected on the Create Virtual Partitions
wizard Summary page, you can still have Virtual Server Manager create the virtual partition.
You will have to correct the conditions prior to starting the virtual partition.
128 Error messages, status indicators, and troubleshooting