Known limitations, problems, and workarounds

In the ESXi stand-alone host, the firmware compliance details are missing in the vSphere Lifecycle Manager image compliance report.

When performing the compliance scan for a stand-alone host, the compliance details might be missing even the compliance check is successful. It is caused by the automatic page refresh or the back-end bug in vCenter vLCM. For more information about the bug, refer to https://kb.vmware.com/s/article/92226.

Workaround: Perform the image compliance scan for the stand-alone host installed with vSphere Lifecycle Manager frequently until the compliance scan is completed successfully. In this process, ensure not to navigate away or refresh the web page.

The Unknown message information is displayed when vLCM fails to remediate firmware of a host.

When vLCM fails to remediate the non-compliant firmware of a host, the Unknown message information is displayed on the remediation result page. It is a known limitation in vSphere 7.0 and will be addressed in the later versions of vSphere and vCenter.

Workaround: Click Check compliance of the cluster, and then check Firmware compliance table of the host to view the list of firmware not remediated successfully.

If you are using Lenovo XClarity Integrator for VMware vCenter version 6.2.0, the backup data of version 6.1.0 or earlier will fail to be restored.

If you are using Lenovo XClarity Integrator for VMware vCenter version 6.2.0 and trying to restore the backup data of version 6.1.0 or earlier, an error message stating “Failed to import data” will be displayed.

Workaround: Deploy Lenovo XClarity Integrator for VMware vCenter version 6.1.0, restore the backup data, and then upgrade the software to version 6.2.0.

After Lenovo XClarity Integrator for VMware vCenter is upgraded to version 5.4.0 or later, all existed rolling update tasks will be lost.

If you are using Lenovo XClarity Integrator for VMware vCenter version 5.3.1 or earlier version, after you upgrade Lenovo XClarity Integrator for VMware vCenter to version 5.4.0 or later, all existed rolling update tasks will be lost.

Workaround: If your Lenovo XClairty Integrator for VMware vCenter has scheduled update tasks that have not been started, after upgrading Lenovo XClairty Integrator for VMware vCenter to version 5.4.0 or later, you should recreate those update tasks.

Pre-authenticated BMC might lose connection after it is managed by Lenovo XClarity Administrator

For a BMC to which you have requested access using a local BMC account before in Lenovo XClarity Integrator, Lenovo XClarity Integrator loses access to the BMC after you manage the BMC with Lenovo XClarity Administrator.

Lenovo XClarity Administrator disables all local BMC accounts after it manages the BMC, so Lenovo XClarity Integrator cannot access the BMC using the local BMC account that you provided before.

Workaround: Use the account that you configured in Lenovo XClarity Administrator to request BMC access again in Lenovo XClarity Integrator.

Failed to get and set BMC SNMP settings

You might fail to get and set BMC SNMP settings in Configuration View.

If you do not have an SNMP account or your account does not have the authority, you cannot get and set BMC SNMP settings.

Workaround: Log in to BMC and change your account authority level to supervisor.

Lenovo XClarity Integrator for VMware vCenter might not work correctly if your ESXi is started from a USB device which is installed on another server

ESXi can be started from a USB device; however, if your USB device is moved to another system, and you start your server from this USB device, the server may not work correctly with Lenovo XClarity Integrator.

This issue occurs when the ESXi recorded information is not consistent with its Integrate Management Module.

Workaround: Reset your System Configuration or reinstall ESXi on your server.

Lenovo XClarity Integrator for VMware vCenter does not display the fan speed and thermal information for blade servers.

If you are working with a blade server and try to view the power metric, the fan speed and thermal information entries are blank.

A blade server does not have a fan or thermal sensor, therefore the fan speed and thermal information entries are blank.

Lenovo XClarity Integrator for VMware vCenter cannot be accessed by blind and visually impaired computer users.

Buttons on the Lenovo XClarity Integrator for VMware vCenter graphical user interface cannot be read correctly by the screen reading program used by blind and visually impaired computer users.

This issue is a limitation of DOJO that used to develop the Lenovo XClarity Integrator for VMware vCenter user interface. The DOJO button cannot be read correctly by the screen reading program.

Lenovo XClarity Integrator for VMware vCenter may download a greater number of update packages from the IBM Web site than you initiated.

When you download updates from an IBM Web site, the number of update packages that are downloaded may be greater than the number you specified.

Each update package may have prerequisite packages, and Lenovo XClarity Integrator for VMware vCenter downloads the packages as well. The package number that is downloading is displayed on the download page and might display more than the number of updates that you initiated.

The error message The host is not managed by Lenovo XClarity Integrator is displayed after Lenovo XClarity Administrator (LXCA) is upgraded to version 3.3.0.

When you acces to LXCI pages (for example, the System overview page and the Inventory page) after LXCA is upgraded to version 3.3.0, the error message The host is not managed by Lenovo XClarity Integrator might be displayed.

The firmware and drivers addon list is empty when creating a dedicated vcenter service account for LXCI V7.2.0.

When creating a dedicated vCenter service account for LXCI V7.2.0, if you select Grant the needed privileges automatically for registering LXCI to vCenter, and define cluster image in vSphere Lifecycle Manager, the firmware and drivers addon list will be empty.

Workaround: Manulally grant the privilege Sessions.ValidateSession to the dedicated vCenter service account for LXCI within vSphere client.

The Session ID is missing message pops up when using Chrome to access LXCI.

When using Chrome 80 or later version to access LXCI, and register LXCA or use rolling update function on LXCI page, the Session ID is missing message will popup.

Workaround: Input chrome://flags in Chrome address bar, then disable the SameSite by default cookies setting.

The firmware version displayed on LXCI is not up-to-date.

On the server managed by LXCI, if you update the server firmware through other tools (for example, BMC web interface, LXCA) without restarting the server, the displayed firmware version of LXCI might not be up-to-date.

Workaround: On the Managed servers page of LXCI, select the server and click REFRESH INVENTORY.

Failed to display the hint information of a component on the chassis map view page when the mouse pointer is hovered onto the component.

When you frequently move the mouse pointer over different components on the chassis map view page, hint information of some components may not be displayed.

Workaround: Click the refresh icon on the upper right corner of the chassis map view page and hover the mouse pointer over the component again.

Get dynamic settings failed. error is displayed on the Configuration page

If there are no IPMI and SNMP user accounts in the baseboard management controller, the Get dynamic settings failed. error is displayed when you open the Configuration page under the Lenovo XClarity Integrator tab in vSphere Web Client.

Workaround: Log in to the management controller Web interface, open the IPMI and SNMP User Accounts page, and add the user account that you specified when you requested management-controller access in Lenovo XClarity Integrator. If it is a Flex compute node, and you choose to use centralized user management by the CMM, you cannot create the account in the management controller. In this case, select the Provision IPMI and SNMPv3 Account checkbox on the Node Account Mgmt page of the CMM Web interface to provision the IPMI user account to the management controller.

Failed to import a Lenovo XClarity Administrator certificate when using Internet Explorer 10

When you manually import a Lenovo XClarity Administrator certificate (PEM) file into Lenovo XClarity Integrator, the import may fail with the following message: Fail to upload certificate file. It is a known problem with Internet Explorer 10.

Failed to register Lenovo XClarity Administrator configured with IPv6 address

When you register a Lenovo XClarity Administrator instance that is configured with IPv6 addresses, the page shows the Loading, Please wait … message and does not return.

Workaround: Manually download certificate from Lenovo XClarity Administrator, and add it to Lenovo XClarity Integrator by clicking Manage trusted certificates > Add. For more information, see the Lenovo XClarity Integrator for VMware vCenter Installation and User Guide.