The B200 M4 blades shipped with 7.0 board controller firmware and the UCS Mini shipped with the latest 3.0(2c) code. Once a Service Profile is associated, the activation of the 7.0 board controller firmware fails. The 3.0(2c) blade firmware package ships with 6.0 board controller firmware. I uploaded the 2.2(5a) blade server firmware package in order for the UCS to "see" the 7.0 firmware. I then modified a 3.0(2c) host firmware package to include the 7.0 board controller firmware for the B200 M4 but activation still fails after acknowledging the reboots. Reacknowledging the blades doesn't change the outcome. Any ideas?
You have done the right thing by adding 2.2.5a firmware package.
Did you perform the activate from CLI?
#scope server X/Y (chassis X blade Y)
# scope boardcontroller
# show image (this will list all of the firmware versions)
# activate firmware version.0 force (Select a lower version than the one already running)
If the above is successful then reset CIMC
You may try --->
In the host firmware policy do not check board controller for this B200M4 leave it blank. Then manually activate it from installed firmware tab in server.