I am planning on running an Infra firmware upgrade on my current UCS domain. It's currently 3.2(1b) and we are planning the upgrade to 4.0(4e) so we can make use of some new M5 blades. The M5 blades are going to replace the existing M3 and M4 blades in the chassis in our environment.
As soon as the system is on 4.0(4e) we will be replacing the old blades, so I guess my question is whether or not I can leave the blades on the old firmware during the upgrade? I don't want to have to do firmware on all the blades just so I can pull them out, immediately after doing it. It's just wasted effort.
Can I leave the blades on 3.2(1b) while I upgrade the Infra packages to 4.0(4e)? Even if it's only for a very short time?
Solved! Go to Solution.
Apologies the blades are 3.1(2b).
I know that's not on the list, but will the system continue to operate at that revision? It's literally for a day or two before we will be replacing the blades anyway... so we don't want to update the firmware if we can avoid it.
Ive read this thread twice, and got the same from it each time. So here's the upgrade procedure you need (unless I should've read it 3x):
You need to upgrade UCS Infrastructure first, before the blades. This means that your blades will have older firmware after you upgrade the FIs. B200M5s can run 3.2. They should be the same version as the FIs, but you obviously cant do everything at the same time.
Upgrade your FIs to 4.x. Then put in your M5s. Upgrade the M5s to match the 4.x. Your existing blades can be upgraded during a maintenance window. Note: every blade should be at least 3.1(3) prior to the FI going to 4.x.