stumbling blocks in upgrading Cisco UCS (Part 1of2)

stumbling blocks in upgrading Cisco UCS (Part 1of2)

In theory a upgrade of an UCS is not complicated, but there are many stumbling blocks.

I show you my procedure, bugs, some hints and Cisco TAC Support stuff 😉


  • See how i lost the Fibrechannel link permanently as a result of this “little” upgrade
  • See some hints to upgrade successfully

First of all, read carefully the release notes and check the compatibility lists!

As an example, we have an 4 year old Blade B230M2 with an Adapter M81KR (N20-AC0002) that is deprecated and not supported in the latest 3.1 Release! 3.1 Relase Notes

For that reason i show you the upgrade from version 2.2(3d) to 2.2(7c)


My procedure is the following:

  1. Read Release Notes carefully
  2. Check compatibility issues for Hardware or Firmware Versions
  3. Check space on the Fabric Interconnect
  4. Check filling level of the temp directory on the Fabric Interconnect (not more that 10%)
  5. Check reboot issue in Firmware 2.2(3d) BUG63966
  6. Check scheduled Backup or create it
  7. Upload the Bundles
  8. Check Cluster State
  9. Disable Home Call
  10. Check Datapaths & Note for later comparsion
  11. Activate UCS Manager
  12. Update IO Modules (Subordinate)
  13. Activate IO Modules (Subordinate)
  14. Activate FI (Subordinate)
  15. Check Datapaths if all are up again
  16. Halftime, take a Coffe or one Beer 😉
  17. Failover FI on CLI
  18. Check Datapaths
  19. Update IO Modules (Now Subordinate)
  20. Activate IO Modules (Now Subordinate)
  21. Activate FI (Now Subordinate)
  22. Check Datapaths
  23. Upgrade Servers/Blades
  24. Take some more Beer 😉

Let’s start …

Check space on the Fabric Interconnect


Check filling level of the temp directory on the Fabric Interconnect

You need this only if the last reboot of your FI is long ago (>1 Year,)

In my case /var/tmp is 10% filled up -> too much for upgrade!

Attention, i recommend that TAC Support do that for you! You also need that debug-plugin from Cisco to do this.


Check reboot issue in Firmware 2.2(3d) BUG63966

Another Bug we ran into some months ago 🙁

The problem is, a config save during shutdown or reboot maybe can’t happen because the system stops before the save is complete. -> Cisco’s resolution is to append a sleeptimer 😉

Here is how Cisco TAC Support fixed that:

Sure, you need to do this on both fabrics!


Check Backup


Upload the Bundles

Upload all your Bundles you downloaded from Cisco


Check Cluster Status

or GUI


Disable Home Call


Check out Part 2

Leave a Reply

Your email address will not be published. Required fields are marked *