Skip to main content

Known limitations and workarounds

This chapter provides information about limitations, problems, and workarounds that apply to Lenovo XClarity Integrator, v4.7.

  • In some scenarios, the hard disk position displayed in the topology view might be not consistent with the actual situation.

    The windows PowerShell command Get-PhysicalDisk retrieves the slot number of the disk, which might cause the error in some scenarios.

    Workaround: N/A

  • Users might fail to report problem to Lenovo if the angle bracket < or > is included in the problem fields.

    When users report a problem to Lenovo, it might be failed if the problem fields (title, description, reproduction steps or what changes happened) contain the angle bracket < or >.

    Workaround: Remove the angle bracket or replace it with other characters.

  • Native OS management initialization is failed with time-out error when the gateway of WAC 2110.2 or earlier versions is running on Windows 10/11.

    It's a WAC known issue. If WAC gateway is running on Windows 10/11, and the Windows logon account does not have permission to access the file system on the target Windows server, the error message Failed to initialize the native OS management. Timeout has occurred will be displayed. In browser development tool, the corresponding error code is 500, and the request URL is *****/features/fileTransfer/files/*****.

    Workaround: Install WAC gateway on the Windows server, or log in to Windows 10/11 using account with permission to access the file system on the target Windows server. This issue has been fixed in WAC 2211.

  • Users might fail to switch to the correct Web page in the Lenovo XClarity Integrator solution by clicking the back or forward button of the browser.

    This problem does not exist in the Server Manager solution, the Failover Cluster Manager solution, and the Hyper-Converged Cluster Manager solution.

    Workaround: Do not click the back or forward button of the browser. Instead, click the link of the Web page in the Lenovo XClarity Integrator solution to switch to the correct Web page.

  • When using Microsoft Edge, the information might exceed the border of the data table or might not align with the column name in some panes .

    When customizing columns or resizing the column width of the data table in some panes, for example, in the Alerts pane of the Lenovo Server page, the information might exceed the border of the data table or might not align with the column name. This problem only exists in Microsoft Edge.

    Workaround:

    • Use Chrome instead of Microsoft Edge.

    • Do not customize columns.

  • The “XX selected” message might cover the action button in the action bar.

    When the browser window is in a special width, and one item is selected from the data table in some panes, for example, in the Service Data pane of the Lenovo Server page, the 1 selected message might cover Export Logs in the action bar.

    Workaround: Resize the browser window until the action button is displayed.

  • The number of selected items is not correct or cannot be displayed on the All Connections page of Lenovo XClarity Integrator.

    On the All Connections page of Lenovo XClarity Integrator, when users click the blank space of a row in the data table to select a server or a Lenovo XClarity Administrator, the number of selected items XX selected might be incorrect or not displayed in the action bar. Actually the items are selected.

    Workaround: Ignore this problem, click the Clear Selection icon , and select these items by clicking their check boxes instead of the blank space.

  • Users might fail to enter the Cluster Dashboard page, with a message indicating that the target node is offline while the node is actually online.

    The problem will occur when users who have managed their cluster nodes by using a Lenovo XClarity Administrator A attempt to use another Lenovo XClarity Administrator B to manage some of their nodes without terminating the node management of A. In this case, both Lenovo XClarity Administrators are in connected state in Lenovo XClarity Integrator. This problem might exist in both the Failover Cluster Manager and the Hyper-Converged Cluster Manager solutions.

    Workaround: In the Lenovo XClarity Integrator solution, click the Remove button in the action bar to terminate the node management of Lenovo XClarity Administrator A.

  • Users might fail to obtain data when connecting to multiple Lenovo XClarity Administrators across different versions.

    When users connect to multiple Lenovo XClarity Administrators across different versions, some of the connections might be lost occasionally. As a result, user operations will fail, especially those requiring data reload on the corresponding servers.

    Workaround: On the Lenovo XClarity Integrator solution extension home page, reconnect to any disconnected Lenovo XClarity Administrator.

  • Users might fail to enter the update method selection page after selecting the Lenovo XClarity Administrator management method in the CAU tool in Cluster Manager.

    After logging in to the Lenovo hardware updates page by using the CAU tool, users then need to select a management method. If Lenovo XClarity Administrator is selected with an LXCA successfully added or connected, the management method selection page might persist and the CAU tool might not proceed to the expected system update wizard.

    In this case, make sure that all the cluster nodes are managed by the same LXCA and the LXCA user has required system update privileges.

    Workaround: In the CAU tool, click Back and then enter the Hardware updates page again.

  • Users might fail to submit hardware updates if "Specify a predefined share folder" is selected for storing the updates in the CAU tool in Cluster Manager.

    In the CAU tool in Cluster Manager, if users select Specify a predefined share folder and Use another Windows account on the update storage page and then proceed to submit the selected hardware updates, the following error message might be displayed:

    Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

    Workaround (either of the following):

    • Use the IP address of the remote server when trying to connect to the network share.

    • Create a different Domain Name System (DNS) alias for the remote server, and then use this alias to connect to the network share.

    After using either of the methods, users are able to connect to the network share with different user credentials. In this situation, the computer behaves as if it is connecting to a different server. Users can then resubmit the selected hardware updates.

    For more information, visit https://docs.microsoft.com/en-US/troubleshoot/windows-server/networking/cannot-connect-to-network-share.

  • Users might fail to submit hardware updates if "Create a share folder automatically" is selected for storing the updates in the CAU tool in Cluster Manager.

    In the CAU tool in Cluster Manager, if users select Create a share folder automatically on the update storage page and then proceed to submit the selected hardware updates, either of the following situations might occur:

    • Failed to execute the PowerShell script. Connection to remote server localhost failed with the following error message: WinRM cannot complete the operation.

      In this case, verify that the specified computer name is valid, the computer is accessible over the network, and that a firewall exception for the WinRM service is enabled and allows access from this computer. By default, the WinRM firewall exception for public profiles limits access to remote computers within the same local subnet. For more information, see About Remote Troubleshooting.

    • Starting a command on the remote server failed with the following error message: Access is denied.

      For more information, see About Remote Troubleshooting.

    Workaround:

    On the gateway server, start PowerShell with the Run as administrator option, and run the Enable-PSRemoting command. Users can then resubmit the selected hardware updates.