VM manager statuses

After you add a 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 both in central and distributed mode.

Outdated VM Manager Data or No VM Manager Data

If the scan result file was imported without errors, but some computers still have the Outdated VM Manager Data or No VM Manager Data status, perform the following steps.

Action

To determine the cause of the problem, check whether the VM Manager tool collects valid and complete results. For more information, see: Troubleshooting Outdated VM Manager Data.

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 files that are in the BES Client\LMT\VMMAN\logs directory, 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 log in process modify the following file.
- BES Client/LMT/VMMAN/vmman.sh
- BES Client\LMT\VMMAN\vmman.bat
Update the Properties Definitions section by adding the debug dump option to VMM_PROPERTIES_DEFS parameter. Insert the following line:
- 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
Run the following VMMAN 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.

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 files that are in the BES Client\LMT\VMMAN\logs directory and search 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 HCL 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 files that are in the BES Client\LMT\VMMAN\logs directory and search 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.

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 either the provided URL or configuration is incorrect, or that there are problems with the network.

Action: Check the connection between VM managers and the VM Manager tool. Also, correct the URL and the credentials, and save the changes. Ensure that thevmm_communication_locked property is set to false 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 of the below reasons:

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 to false.
- By default, VM Manager tool is installed on the same computer as the BigFix server. Check the connection between VM Manager tool and VM manager. Make sure that the firewall, proxy and NAT settings are correct.
Windows™ Remote Management (WinRM) not configured properly with BigFix Inventory to gather data about installed machines.
Action: The user must have administrative access to the WinRM framework to get data from Hyper-V managed hosts. For more information, refer to Configuring WinRM on Hyper-V hosts.

No data (previously Insufficient rights)

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 run the Run Capacity Scan on Virtualization Hosts fixlet, 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.

Make sure that the user has read access to these virtual machines that are managed by this VM manager and their host.

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, the duplicate VMs are discarded from the results. The problem is most often caused by one of the following reasons:

For VMware:
- Virtual machines were deployed from catalog templates in vCloud Director. By default, such machines are assigned the same BIOS UUID. For more information, see: BIOS UUIDs in vCloud Director are not unique when virtual machines are deployed from catalog templates.
- Virtual machines were cloned without changing their UUIDs. For more information, see: Changing or keeping a UUID for a moved virtual machine.
For Hyper-V:
- Virtual machines were deployed by importing an exported Hyper-V guest that already exists, without changing the BIOS UUID.
- Virtual machines were deployed using a template.

Action: Open the VM Manager tool log files that are in the BES Client\LMT\VMMAN\logs directory 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: Editing a virtual machine with a duplicate UUID.bios.

After the duplicates are corrected, the VM manager status changes to OK.

Pending

The status is applicable only to VM managers that are managed in the central mode. 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 BigFix Inventory 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: Capacity data flow.

If the status of the VM manager remains Pending for a longer period of time, 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.
1. Go to Sites > External Sites > BigFix Inventory > Fixlets and Tasks.
2. In the upper right pane, select Schedule VM Manager Tool Scan Results Upload, and click Take Action.
3. Select the computer on which the BigFix server is installed, and click OK.

After you schedule the action, wait for the collected data to be uploaded to the BigFix server and then imported to BigFix Inventory. The status of the VM manager should change to OK after the import.

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 HCL 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 in central mode. If the VM manager is managed in the distributed mode, 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: The connection to a VM manager could not be established. Check the VM Manager tool log files that are in the BES Client\LMT\VMMAN\logs to determine the cause.