You can upgrade the compute firmware (BMC and BIOS) to the latest versions. You can also upgrade the I/O card firmware for compute nodes running an ESXi hypervisor and onboarded to the inventory using ESXi credentials. However, CPLD upgrade is not supported.
By default, the compute node powers off, which initiates operating system shutdown before the system powers off.
- The HA800 G3 series server models are running firmware SPV 7.3, which is the latest version available.
- CPLD upgrade support is removed from server firmware upgrade workflow.
- For both the local site and remote site, verify that the IP addresses of the UCP Advisor VMs are reachable to the compute BMC IP address.
- Verify that the device user credentials are assigned administrator role: Administrator.
- Upload the firmware bundle to UCP Advisor. This might require you to additionally upload a bundle from an earlier release of UCP Advisor. See Supported compute BMC firmware upgrade paths.
- For firmware upgrade on HA800 G2 series servers, HTTPS port 18843 must be open, when the firewall is enabled.
- Place the ESXi hosts in maintenance mode.
- Enable the SOL settings on the compute nodes. See Enabling SOL settings for BIOS on DS120/DS220/DS225/DS240 and DS120 G2/DS220 G2 servers.
- For I/O card upgrades:
- Verify the currently supported I/O cards. See Supported I/O cards: DS120/DS220/DS225/DS240 and DS120/DS220 G2 server models.
- Add the ESXi host to the vCenter where the UCP system is registered so that the I/O cards can be discovered.
- Onboard the server to UCP Advisor and then verify that the BMC and ESXi details are available.
- Verify that the onboard status of the compute device is Normal.
During a sequential upgrade or a parallel upgrade, an individual task is created for each device on the Tasks console. The Initiate Upgrade server firmware task displays the details of all the servers selected for the upgrade.
For a sequential upgrade, if the cause of the failure is specific to the server where the task terminated, reinitiate the task for the remaining servers. You can manually update the firmware on the failed server using the server's BMC UI.