HP Matrix Operating Environment Software - Manual (Page 132)

•
No Comm. indicates that Integrity Virtual Server Manager is unable to communicate with the
WBEM provider running on a VM or vPar. Hover the cursor over the meter to display an
exception error message identifying the problem.
A common reason for the No Comm. label to be displayed is a problem with trusted certificates.
For example, if trusted certificates are required (the Require trusted certificates check box was
selected on the Set WBEM Credentials for VM or vPar page) but the keystore on the VSP does
not trust the certificate from the VM or vPar, then the certificate is not in the keystore, has
expired, did not match the VM or vPar name, or is otherwise invalid. For information about
trusted certificates, see
“Trusted certificates” (page 18) .
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 VM or vPar is not started, not booted, or cannot be contacted by the system on which
Integrity Virtual Server Manager is running.
◦
The VSP has no WBEM credentials for collecting the data from the VM or vPar. 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 15) .
For more information about problems displaying data (data is out of date, incomplete, or
missing), see
“Troubleshooting VM or vPar problems” (page 132) .
•
No Perm. indicates that the VSP lacks or has invalid WBEM credentials for collecting the
data from the VM or vPar.
•
Timed Out indicates that Integrity Virtual Server Manager attempted to retrieve utilization
data but received no response from the WBEM provider on the VM or vPar because of one
of the following situations:
◦ The WBEM provider for the data is not running, is not installed, or is disabled on the VM
or vPar.
◦ Network problems are preventing a timely response.
For more information about collecting and viewing utilization data, see Chapter 7 (page 117) .
Troubleshooting VM or vPar problems
This section discusses problems that might occur when using Integrity Virtual Server Manager to
create, start, or modify a VM or a vPar or to display VM or vPar 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 VM
When using the Create Virtual Machines wizard, a number of warning or error conditions
can prevent the VM or vPar from being created. However, if the Create VM even if resources
132 Error messages, status indicators, and troubleshooting