A regional hospital updated the host firmware package on a service profile. The maintenance policy waits for an administrator to acknowledge a reboot, and the blade still runs the old firmware. Why has the new firmware not started?
Select an answer to reveal the explanation.
Short Explanation
The maintenance policy is a work order that sits on the bench until someone signs it. You updated the host firmware package, and the blade keeps running the old code until an administrator acknowledges the reboot. The package selected the new firmware, and the policy decides when the server may restart onto it.
Full Explanation
A host firmware package selects the server firmware, such as BIOS, adapter, and controller code, that a service profile should run. Applying a new package is disruptive and needs a reboot before the blade actually runs it. When the maintenance policy is set to wait for user acknowledgment, UCS holds that reboot until an administrator acknowledges it, so the hospital blade stays on the old firmware. The chassis IOM is not the installer for host firmware, and it does not reboot a blade just because a host package changed. Fabric interconnect firmware is the infrastructure image for the domain. Updating a host package does not require both interconnects to reload before the blade can use a new BIOS. A logical configuration export is an XML backup of profiles, pools, and policies. It does not transfer firmware into a running server. Caveat: once the reboot is acknowledged, the blade does go down, so the acknowledgment belongs in a maintenance window even though the package change itself was quiet. Operational check: confirm the profile shows a pending reboot, acknowledge it for one test blade, and verify the host firmware versions after it comes back.