Update deployment considerations

• For the best performance, ensure that Lenovo XClarity Administrator resource managers are running v3.2.1 or later
• Ensure that the updates repository contains the update packages that you intend to apply. If not, refresh the product catalog, and download the appropriate updates (see Downloading and importing updates).
• Ensure that no jobs are currently running on the target resource. If jobs are running, the update job is queued until all other jobs have completed.
• If the resource has an assigned update-compliance policy that results in compliance violations, you must correct the violations either by adjusting the compliance policy or assigning an alternate policy.
• If you choose to install an update package that contains updates for multiple components, all components to which the update package applies are updated.

Resource considerations​

• The updates function supports updating only servers and resource managers.

  For ThinkSystem SR635 and SR655, only BMC and UEFI firmware-updates are supported.

  For ThinkSystem and ThinkAgile devices, firmware updates are not supported for baseboard managed controller and UEFI backup banks. Instead, update the primary bank and then enable auto promotion.

• Before updating managed devices, ensure that you read important update considerations (see Firmware-update considerations in the XClarity Administrator online documentation).
• Before updating XClarity Administrator resource managers, ensure that you read the update considerations for XClarity Administrator (see Updating the XClarity Administrator management server in the XClarity Administrator online documentation).
• Before updating XClarity Administrator resource managers, back up the virtual appliance by creating a clone (see Backing up XClarity Administrator in the XClarity Administrator online documentation).
• Ensure that the resources that you want to update have an assigned update-compliance policy.
• XClarity Orchestrator transfers the applicable updates to the resource manager during the update process. Ensure that there is enough disk space in the management server to contain the updates.
• For ThinkEdge Client devices, only BIOS updates on servers running Windows 10 version 1809 or later 64-bit operating system is supported. Special editions (such as 10 S or 10x) are not currently supported.
• You cannot download firmware updates for the following servers from the web interface. Instead, manually download updates from ibm.com and then import the updates.
  • IBM System x iDataPlex dx360 M4
  • IBM System series M4
  • IBM System x3100 M5 and x3250 M
  • IBM System x3850 X5 and x3950 X5
  • IBM System x3850 X6 and x3950 X6
  • IBM Flex System

Repository considerations​

• Ensure that the updates repository contains the update packages that you intend to apply. If not, refresh the product catalog, and download the appropriate updates (see Downloading and importing updates).

  You can choose to install prerequisite updates in addition to the target update. All prerequisite updates must be downloaded to the repository before they can be applied.

  In some cases, multiple versions might be needed to apply an update, and all versions need to be downloaded to the repository.

Update-process considerations​

• If you choose to install an update package that contains updates for multiple components, all components to which the update package applies are updated.
• When a request is made to apply updates to a resource manager and one or more devices that are managed by that resource manager, updates are applied to the resource manager first.
• While an update is in progress, the target resource is locked. You cannot initiate other management tasks on the target resource until the update process is complete.
• After an update is applied to a resource, one or more restarts might be required to fully activate the update. You can choose whether to restart the resource immediately or delay the activation, or prioritize activation. If you choose to restart immediately, XClarity Orchestrator minimizes the number of restarts that are required. If you choose to delay activation, the updates are activated the next time the resource is restarted. If you choose prioritized activation, the updates are immediately activated on the baseboard management controller, and all other updates are activated the next time the device is restarted.
• If you choose to restart the resource during the update process (immediate activation), ensure that any running workloads have either been stopped or, if you are working in a virtualized environment, moved to a different resource.
• Some firmware updates require a monitor to be connected to the target device. The update process might fail if a monitor is not connected.