We have discovered that sometimes UCS Server firmware doesn't always install properly. When you look at the server firmware, it displays sometimes like this;
Now we have track some of this down to human error. When the operations team migrates service profiles within UCS Central to newer UCS Domains with Newer Firmware, they sometimes forget to update the firmware policy until after the profile has been migrated. In the example above, A service Profile that had firmware policy for 3.1(2f) was migrated to a server with 3.2(3j). This forced a downgrade of the server which did not downgrade completely. After updating the service profile the upgrade runs but doesn't upgrade completely.
The way to fix this is to upgrade the local components manually. from UCSM.
We have discovered the only role that is allowed to update server firmware locally is admin. We do not want to give the operations staff full admin rights so I was wondering if anyone else has seen this and what they have done to fix it.
Just seeing two values does not necessarily mean the firmware did not install correctly. You just have versions running on the server that are included on two different B series firmware bundles.
If you look at the installed firmware tab on the server hardware, do you see all components running the correct package version? If so, then the server firmware upgrade was successful.
Thanks Bob. Please open a TAC case and we can investigate to ensure we are not missing anything and find an acceptable solution.