B200M4 blade firmware issue

[mike_tharp]

I have three chassis with B200M3 blades and am in the process of installing the first B200M4 blade for an upgrade.

When I assign it to a service profile that has the normal firmware policy I use for all my blades it gets BIOS version B200M4.2.2.6c.0.111720151647 but it will not boot. I get an error that says "BIOS failed power-on self test" and looking at the console it is stopped at "Configuring and testing memory.."

If I disassociate the service profile and change to BIOS B200M4.3.1.3f.0.110320162243 it boots fine. Unfortunately my firmware policy doesn't allow me to individually change that one BIOS value because it is set to basic. I also am unsure how to set it to automatic without causing damage.

Has this been seen before? I couldn't find mention of it.

If there is no resolution I will just create a new firmware policy and set it there for the new blades so it isn't the end of the world.

[Wes Austin]

Your B200-M4 likely have v4 processors:

Cisco UCS B200 M4 Server Upgrade Guide for E5-2600 v4 Series CPUs

This document lists the minimum supported firmware. You will need to create a new Host Firmware Package to upgrade all components to the new minimum firmware.

[mike_tharp]

I would like to integrate the new blade without touching my infrastructure versions but it doesn't look like that is going to be an option.

Currently running UCS manager 2.2(6f) so it looks like that works per the document linked as it is above 2.2(4) but it also looks like I will need to upgrade the CIMC, BIOS, and Capability Catalog to 2.2(7) for it to work.

Will review the linked document more and find the proper method.

[Walter Dey]

Take any release notes, e.g.

https://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/release/notes/CiscoUCSManager-RN-3-1.html

Table 6 Mixed Cisco UCS Releases Supported on Cisco UCS 6200 and 6300 Fabric Interconnects

The Cisco UCS Manager A bundle software (Cisco UCS Manager, Cisco NX-OS, IOM and FEX firmware) can be mixed with previous B or C bundle releases on the servers (host firmware [FW], BIOS, Cisco IMC, adapter FW and drivers). ==> this implies that BIOS, CIMC,adaptor FW,... have to be same version !

¹ Beginning with Cisco UCS Manager Release 2.2(4), and for M4 servers, a lower version of the infrastructure A bundle will be compatible with the previous version and higher version of B and C server bundles. For example, the Cisco UCS Manager Release 2.2(4)A bundle will be supported with any of the following B bundles for B200-M4 servers: 2.1(1)B, 2.1(2)B, 2.1(3)B, 2.2(1)B, 2.2(2)B, 2.2(3)B, 2.2(4)B, 2.2(5)B, 2.2(6)B, 2.2(7)B.

[mike_tharp]

Walter, to clarify what Wesley said will apply and I can create a new service profile with the correct settings for the V4 blades and stay with the FI and manager versions of 2.2(6f).

Correct?

[Wes Austin · Accepted solution]

Mike,

You need to create a new Host Firmware Package that utilizes the 2.2.7b or later B Bundle. You then assign that Host Firmware Package to the service profiles or service profile template that is assigned to the B200-M4 blades. This will upgrade all the components on your blades to the correct version and it will allow them to boot.

With Server Packs, you can leave the blade firmware at a higher revision than the UCSM/FI/IOM so this is supported.

[mike_tharp]

Excellent, thank you for clarifying.

[Wes Austin]

Mike,

If your Infra is on 2.2.6, you can just upgrade the blades CIMC/BIOS/Adapter etc to the minimum firmware release per the previous documentation. There is no need to upgrade the FI and the UCSM unless desired.

[Walter Dey]

Can please clarify what you would like to achieve ?

- upgrade the UCS systen ? and if yes

- only infrastructure and let the blade where they are

- infrasturcture plus blades ?

- what is reason you are using a host firmware package ?