12-22-2025 11:55 AM
i have a cisco UCS C240m5 server that connect UCSM, i want to upgrade this firmware ,do i upgrade from ucsm or server cimc
12-22-2025 12:48 PM
Typically for UCSM connected C-Series servers you would:
Most often UCS C-Series firmware is controlled by a UCS Host Firmware Package (HFP) Policy.
Change the HFP policy (make sure it is set to user-ack first) and then reboot the server which should trigger a firmware upgrade during the reboot (so the server will likely reboot a couple of times.)
Since I see label UCS Central, that can throw a wrench in the works as policy may need to be pushed from UCS Central.
I also see label Hyperflex, where those servers can NOT be managed by UCS Central and where Server firmware upgrades should be done via HX connect as HX will control the upgrade process (which does a proper rolling reboot waiting for the cluster to heal between reboots).
12-22-2025 02:01 PM - edited 12-22-2025 02:13 PM
hello steven
thanks for your reply ,
i want upgrade firmware of UCS C240m5 server that is connect to UCSM ,also there cluster of hyperflex server which will upgrade through HX connect , and i don't have UCS central
i need the method to upgrade the ucs c240 firmware which is connect with UCSM , can i upgrade it through its CIMC or UCSM , and please mention the document that explain that
12-23-2025 07:20 AM
UCSM lets you have varied levels of configuration/automation/policy so multiple sections in the docs apply depending on your existing/custom configuration. From most automatic to most manual steps:
12-23-2025 08:24 AM
UCSM and C240 M5 Upgrade Sequence
UCSM (FI) firmware must be equal to or higher than the server VIC firmware for compatibility. Always upgrade FI first.
Take a full UCSM configuration backup (Admin > All > Backup & Export) and verify current version compatibility with target bundles using the Cisco Interoperability Matrix Tool.
Navigate to UCSM GUI > Equipment > Firmware Management > Download Tasks to download/upload "A-bundle" (FI A.bin) and "C-bundle" (host C.bin).
Click Firmware Auto Install > Install Infrastructure Firmware, then upgrade FI-A (subordinate) first with "A-bundle" (20-25 minutes, monitor via FSM tab).
Upgrade FI-B (primary) next and confirm reconnection. If connection drops, log in via subordinate FI.
Go to Servers > Policies > Host Firmware Packages, modify existing policy or create new one selecting "C-bundle". Apply to Service Profile (check User Ack settings).
HXDP license registration is mandatory before upgrading to 5.0 or higher (failure without it).
Run Hypercheck tool (cluster health, DRS Fully Automated, storage capacity >20% free).
After FI "A-bundle" upgrade, access HX Connect > Upgrade > Pre-Upgrade Validation (upload ESXi/HXDP bundles and test).
Upon test success, perform sequential node upgrades (verify per-node health: vCenter connectivity, no Major Alarms).
Risk management: Avoid non-maintenance windows; monitor FSM during upgrades.
Compatibility: Check Cisco Software Download > UCS B/C-Series Firmware > Release Notes & Upgrade Path.
Rollback: Download prior A/C-bundles, verify network/cabling. Confirm HX node vSphere services.
Issues: Contact Cisco TAC (collect logs: UCSM Support > Faults/Alarms).
This sequence ensures stability. Let me know for version-specific details!
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide