Updating firmware/drivers for cluster nodes

For Windows Admin Center 1910, Hyper-Converged Cluster Manager and Failover Cluster Manager are combined into the Cluster Manager solution. This section describes how to perform a firmware/driver update job on cluster nodes in Cluster Manager, using Best Recipes (Recommended), Compliance Policies, or Latest Updates. The Updates pane displays the best recipes, latest updates, cluster consistency, and update logs of firmware and drivers.

Procedure

1. Connect to Lenovo XClarity Integrator in Cluster Manager. Refer to Connecting to Lenovo XClarity Integrator in Cluster Manager.
2. Do one of the following:

   • Ensure that the target server is managed. In the Menu pane of the Lenovo Server page, click Updates.

     Note

     • Users can refer to Managing cluster nodes with Lenovo XClarity Administrator and Managing cluster nodes without Lenovo XClarity Administrator.

     • The Compliance Policies feature is only supported when managing a server with Lenovo XClarity Administrator.

   • In the left navigation pane of the server page, click Lenovo XClarity Integrator — Compliance and Updates or .
3. In the Updates pane, select one of the following update methods:

   • To assign a best recipe for firmware/driver updates:

     1. Click Best Recipes (Recommended).

     2. Select the best recipe from the drop-down list, and do one of the following:

        • To view firmware/driver updates in the best recipe, click Show Best Recipe Definition.

        • To refresh the recipe, click Refresh Best Recipe.

        • To view the applicable firmware/driver updates, click in front of a device.

          Note

          • If Compliance is Compliant for a component, the installed version is already the same as or even higher than the target update version in the policy. Therefore, components with Compliance being Not Compliant are recommended to be updated.

          • The table only shows the components defined in the best recipe.

     3. Click Install Updates.

   • To assign a compliance policy for firmware updates:

     1. Click Compliance Policies.

     2. Select a policy from the drop-down list.

        Note

        • Users can click Show Compliance Policy Definition to view firmware updates in the policy.

        • Users can click in front of the device to view firmware updates applicable to it in the policy. If Compliance is Compliant for a component, the installed version is already the same as or even higher than the target update version in the policy. Therefore, components with Compliance being Not Compliant are recommended to be updated.

     3. Click Install Updates.

   • To select a target version for each component to be updated:

     1. Click Latest Updates.

     2. Do one of the following:

        • To view the latest firmware and driver updates, click Reload local repository.

        • To perform firmware and driver updates, select a target catalog or a target update package, and click Install Updates.

        • To manage local repository, click Manage local repository, and do one of the following:

          • To refresh catalog, select one or more target catalogs, and click Refresh Catalog.

          • To download the update packages, select one or more target catalogs or update packages, and click Download.

          • To delete the update packages, select one or more target machine types or update packages, and click Delete.

          • To filter out firmware updates or driver updates only, click Firmware & Driver, and select Firmware or Driver.

          • To filter out updates for Windows or Linux only, click Windows & Linux, and select Windows or Linux.

   • To check the consistency of firmware versions across cluster nodes, click Cluster Consistency, and select a base for BMC and UEFI to check the firmware version consistency.

   • To delete, cancel, or retry the update jobs of current cluster nodes or servers:

     1. Click Update Logs.

     2. Do one of the following:

        • To delete the update job, select one or more update jobs, and click Delete.

        • To cancel the update job, select one or more scheduled update jobs, and click Cancel.

        • To retry the update job, select an update job in Failed, Stopped, or Cancelled status, and click Retry.

4. On the Update Selection tab, select or deselect components to be updated.
   1. Select or deselect components to be updated in the Select Items pane.
      Note

      • Users can click at the upper right corner of the Select Items pane to expand the Preview pane, or click to remove a component.

      • Operations on the Select Items and Preview panes are synchronized in real time.

   2. (Optional) To update firmware/drivers on the selected components even if the installed version is already up to date or later than the target version for update, enable Forced update.
      Note

      • It's not allowed to apply firmware or drivers of earlier versions to device options, adapters, or disk drives.

      • Forced update is available only when Compliance Policy is used.

   3. Click Next.
5. On the Update Download tab, download or import update packages as required, and then click Next.
6. On the Clustered Roles Migration tab, click Next.
   Attention

   The cluster roles cannot be migrated when the cluster consists only one server node; otherwise, all running clustered roles, including clustered and non-clustered virtual machines, will be disrupted after the server node is restarted.

   Note

   Clustered roles migration is automatically enabled on all servers in the cluster.

   Clustered Roles Migration performs the following tasks:

   1. Puts one cluster node into maintenance mode, and moves the clustered roles off the node.

   2. Install system updates.

   3. Performs a restart.

   4. Brings the node out of maintenance mode, and restores the clustered roles on the node.

   5. Moves to the next cluster node.

7. On the OS Credential tab, click Credential Needed to input the account, user name, and password of a Windows administrator account, and then click Next.
   Note

   • For the cluster node, the account should be the Active Directory domain account included in the local Administrators group.

   • For the non-cluster server, the account should be the Active Directory domain account included in the local Administrators group or the built-in administrator account.

   • OS credentials are required if one or more of the following operations are required:

     • Firmware/driver update in native OS management mode

     • Clustered roles migration

8. On the Options tab, name and schedule the update job. Then, click Next.
9. On the Summary tab, check the information about the update job, including the components to be updated, job name, schedule, and assigned policy if any.
10. Click Submit.