Updating firmware/drivers for Azure Stack HCI cluster nodes

When creating an Azure Stack HCI cluster in Windows Admin Center, users can update firmware and drivers for the cluster nodes using Best Recipes (Recommended), Compliance Policies, or Latest Updates.

Procedure

1. Log in to the Solution updates page. Refer to Logging in to the Install hardware updates page.
2. Ensure that all the cluster nodes are managed. Refer to Managing Azure Stack HCI cluster nodes with Lenovo XClarity Administrator or Managing Azure Stack HCI cluster nodes without Lenovo XClarity Administrator.
   The system update wizard is displayed.

   Note

   In the system update wizard, users can sync the inventory by clicking in the upper right corner to sync the inventory. This function is the same as Syncing the inventory of a server.
3. Select any 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.

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 Summary tab, check the information about the update job, including the components to be updated, job name, schedule, and assigned policy if any.
9. Click Submit.