VM manager statuses
After you add a connection to the VM manager, see the explanation of its status to ensure that the VM manager works properly.
VM manager statuses
The statuses apply to VM managers that are managed by all VM Manager Tool deployment types.- Connection failed
-
Connection to the VM manager failed and the data was not retrieved.
Action:-
To determine the cause of the problem, open the VM Manager Tool log file, and look for the following exception.
VM Manager is not able to communicate with ESX 4.x due to: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificates does not conform to algorithm constraints
For more information, see: RQMCopyUtility error: SSL_TLS SSLContext not available. Certificate does not conform to algorithm constraints.Note: ESX 4 is no longer supported by VMware. For more information, see: End of Availability and End of Support Life for ESX 4.x and VMware Management Assistant. - In order to debug the log in process, modify the vmman.sh or
vmman.bat file. By default, the file is stored in the following location.
- For local VM Manager Tool
- opt/ibm/LMT/VMMAN/vmman.sh
- C:\Program Files\ibm\LMT\VMMAN\vmman.bat
- For central and distributed VM Manager Tool
- /var/opt/BES/LMT/VMMAN/vmman.sh
- C:\Program Files (x86)\BigFix Enterprise\BES Client\LMT\VMMAN\vmman.bat
- For disconnected VM Manager Tool
- VM Manager Tool install dir/VMMAN/vmman.sh
- VM Manager Tool install dir\VMMAN\vmman.bat
In the Properties Definitions section, add the debug dump option to the VMM_PROPERTIES_DEFS parameter. Insert the following line before the####### CLASS PATH DEFINITONS #######
line:-
VMM_PROPERTIES_DEFS="${VMM_PROPERTIES_DEFS} -Dcom.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.dump=true -Dhttps.protocols=TLSv1.2,TLSv1.1,TLSv1 -Dcom.ibm.jsse2.disableSSLv3=false -Dcom.ibm.tools.attach.enable=no"
-
SET VMM_PROPERTIES_DEFS=%VMM_PROPERTIES_DEFS% -Dcom.sun.xml.internal.ws.transport.http.client.HttpTransportPipe.dump=true
Then, run the following VM Manager Tool command.-
vmman.sh -testconnection > vmman.out 2>&1
-
vmman.bat -testconnection > vmman.out 2>&1
Verify the command output by checking credentials and VM manager response. If no VM manager connection is defined, the command output is empty.
- For local VM Manager Tool
-
- Data partially collected
-
Data was collected only from some of the hosts.
Action:- If the problem occurs on Hyper-V, it indicates that some of the host in the cluster have
connectivity issues. To identify the problematic hosts, open the VM Manager Tool log file , and look for the following
entries.
Processing of the host: <HOST_UUID> ip: <HOST_IP_ADDRESS> from hyper-v cluster was skipped because of invalid connection status (<STATUS>). A communication error occurred when processing one of the Hyper-V hosts in the cluster. Host name: <HOSTNAME>. Skip and continue.
Fix connectivity issues for the identified hosts. If the problem persists, contact IBM Support.
- If the problem occurs on Citrix Hypervisor (formerly XenServer), it indicates that XenTools are
not installed on some of the virtual machines. To identify the problematic virtual machines, open
the VM Manager Tool log file
, and look for the following
entries.
It was not possible to retrieve the number of cores assigned to XEN VM with UUID: <VM_UUID>. Most likely the XenServer Tools are not installed on this particular VM. Skipping VM and continue.
Install XenTools on the identified virtual machines.
- If the problem occurs on Hyper-V, it indicates that some of the host in the cluster have
connectivity issues. To identify the problematic hosts, open the VM Manager Tool log file , and look for the following
entries.
- Duplicated address
-
The address of the VM manager is duplicated. The first VM manager with this address remains active and the status is displayed for the remaining ones.
Action: Delete duplicated VM managers to ensure that data is gathered only once. The duplicated addresses might occur only within a particular VM manager type.
- Hard timeout - suspended
-
Connection to the VM manager failed and no further attempts are made. The status indicates that connection to a VM manager failed due to high network latency or some other problems with the network.
Action:- Check the connection between VM managers and the VM Manager Tool.
- Try increasing the time after which the connection with a VM manager is ended
by changing the value of the following parameter.
- For local and central VM Manager Tool, change the value of the vmman_connection_time_out parameter on the Advanced Server Settings panel. For more information, see: Advanced server settings.
- For distributed and disconnected VM Manager Tool, change the value of the vmm_connection_timeout parameter in the vmmmainconf.properties file. For more information, see: VM Manager Tool configuration parameters.
- Ensure that the
vmm_communication_locked
property is set tofalse
in the corresponding vmmconf_*.properties file.
- Inactive
-
Data from the VM manager was not retrieved for a period longer than the maximum VM manager inactivity. The status indicates that either the provided URL or configuration is incorrect.
Action: Correct the URL and the credentials, and save the changes.
- Invalid credentials - attempting
-
Connection to the VM manager failed because the credentials are incorrect or the password expired. More attempts are made until the limit of failed login attempts is exceeded. Then, the status changes to Invalid credentials - suspended to prevent the account from locking.
Action: Edit the VM manager and correct the credentials.
- Invalid credentials - suspended
-
Connection to the VM manager is suspended because the number of failed login attempts was exceeded. The status is used to prevent the account from locking if invalid credentials were provided.
Action:- Ensure that the VM manager credentials are correct. Then, click Resume.
- Go to vmmconf_*.properties file and make sure that the
vmm_communication_locked
parameter is set tofalse
. - Check the connection between the VM Manager Tool and the VM manager. Make sure that the firewall, proxy and NAT settings are correct.
- No data
-
No data was collected from the VM manager. The most common reason is that there is no data or that the user that is defined for this VM manager does not have sufficient rights.
Action:- If you collected data directly from the virtualization host, ensure that the virtualization hosts from which you want to collect capacity data have at least one virtual machine that is correctly defined and running.
- Ensure that the user has read access to virtual machines that are managed by this VM manager and their host.
- If you enabled UUID-based virtual machine filtering, all VM data might be filtered out. Include more UUIDs on the list. For more information, see: UUID-based virtual machine filtering.
- Insufficient permissions
-
No data was collected from Red Hat OpenShift.
Action:- Ensure the ServiceAccount created for the License Metric Tool server has the required permissions to collect data from Red Hat OpenShift.
- OK
-
Data is collected from the VM manager and processed according to the schedule. No issues were detected.
- OK - duplicated UUIDs discarded
-
Each virtual machine must have a unique UUID. When a UUID identifies more than one VM, both VMs are discarded from the results.
The problem occurs most frequently on VMware and is usually caused by one of the following reasons:- Virtual machines were deployed from catalog templates in vCloud Director. By default, such machines are assigned the same BIOS UUID. For more information, see: VM BIOS UUIDs are not unique when virtual machines are deployed from vApp templates.
- Virtual machines were cloned without changing their UUIDs. For more information, see: Changing or keeping a UUID for a moved virtual machine.
Action: Open the VM Manager Tool log file, and identify discarded virtual machines. Then, refer to the documentation for your virtualization type to learn how to assign unique UUIDs to each virtual machine. For information about VMware, see: Override the Generated UUID for a Virtual Machine.
After the duplicates are corrected, the VM manager status changes to OK.
- Pending
-
The status is applicable only to VM managers that are managed by the local and central VM Manager Tool. It is displayed after a VM manager is created or after its definition is modified. It indicates that changes are still being propagated to the VM Manager Tool. The status changes to OK when the following steps are completed:
- VM Manager Tool gathers data from VM managers.
- The data is uploaded to the BigFix® server.
- The data is transferred to License Metric Tool with a data import.
If a problem occurs during any of these steps, the status changes to indicate the problem.
Action: Wait until the VM Manager Tool completes the steps that are required to upload the data. For more information about each step, see: Flow of capacity data - central VM Manager Tool.
If the status of the VM manager remains Pending for a longer period of time for the central VM Manager Tool, it might indicate that the Schedule VM Manager Tool Scan Results Upload task was not scheduled or was stopped. To check whether it is the case, perform the following steps.- Log in to the BigFix console, and go to Actions.
- Look for the Schedule VM Manager Tool Scan Results Upload action and check its status.
- If the action does not exist, or its status is Stopped or Expired, start the action.
- Go to .
- In the upper right pane, select Schedule VM Manager Tool Scan Results Upload, and click Take Action.
- Select the computer on which the BigFix server is installed, and click OK.
- Unknown problem
- The problem does not fall into any other category. Check the VM Manager Tool
log to determine the cause.
Action: If you are not able to determine the cause of the problem from the VM Manager Tool log, contact IBM Support.
Connection test statuses
The following statuses are displayed in the Connection Test Status column
after you select a VM manager, and click Test Connection. The statuses are
applicable only to VM managers that are managed by local or central VM Manager Tool. If the VM manager is managed in the distributed or
disconnected VM Manager Tool, the connection test status is
Not Applicable
.
- Not Tested
- The connection test was never started. Select a VM manager, and click Test Connection.
- Testing
- The connection is being tested. It might take a few minutes until the status changes. Refresh the panel.
- Successful
- The connection to a VM manager was established. The VM manager is configured correctly.
- Failed or Failed - <reason of failure>
- The connection to a VM manager could not be established due to the provided reason (if applicable). Check the VM Manager Tool log to determine the cause.