A regional hospital points a service profile at a newer host firmware package. The blade still runs the old BIOS, and the maintenance policy is set to wait for an administrator. Why is the new firmware not active yet?
Select an answer to reveal the explanation.
Short Explanation
The new firmware is packed, and the maintenance policy is the permit to reboot. You acknowledge that policy's pending action before the blade reloads onto the host firmware you selected. Exporting a backup does not install the package.
Full Explanation
A host firmware package selects the server firmware, and the maintenance policy decides when a disruptive change is allowed to reboot the blade. When the policy waits for an administrator, UCS keeps the pending reboot until someone acknowledges it, so the hospital blade continues to run the old BIOS. Acknowledging the pending action is what lets the reboot apply the package. A vNIC template change updates adapter networking. It does not apply a host firmware package and it does not skip the maintenance policy. Exporting a logical backup writes an XML file of profiles, pools, and policies. The export does not install firmware. Grid is a chassis power policy. It does not gate whether a host firmware package can activate. Caveat: acknowledging the activity reboots that server, so the host operating system drops when the reboot starts. Other servers with their own pending activities are not rebooted by this one acknowledgment. Operational check: confirm the profile shows a pending maintenance action, acknowledge it in the window, and verify the BIOS version after the blade returns.