11-17-2014 07:00 AM - edited 03-01-2019 11:55 AM
Very strange effect:
Firmware server autoinstall from 2.0.4b to 2.1.3f
I created a host firmware package, and then I found, that the board controller asks for a further reset ?? see screen shots
I thought that HFP does Bios, CIMC,.... all in one step.
Before the upgrade, the board controller seems to be compliant (see screenshot 33), after the upgrade with HFP, it say compliant after next reset.
11-17-2014 03:46 PM
Walter,
So you created the HFP and applied it to the Service Profile (SP) and even though you are applying the same version the system is asking you for a reboot?
-Kenny
11-17-2014 09:32 PM
Hi Kenny
No, I did the server firmware upgrade, with a HFP (set to 2.1.3f), which I hoped would do BIOS, CIMC, Board Controller and I/O adaptor with one reboot. However, this is not the case; I'm asked to do a reset for the Board controller to be in synch. The infra is at 2.2.3c.
Cheers Walter.
11-18-2014 12:54 AM
11-18-2014 02:09 AM
Reset as indicated doesn't resolve the issue ! this is definitely a bug !
11-18-2014 05:10 AM
Walter,
can you please run these commands:
# scope server x/y (x=chassis y=blade )
# scope boardcontroller
# show image (this will list all of the firmware versions) Check if there is anything listed there
then try :
# activate firmware version.0 force (select the appropriate value from the show image command)
# commit-buffer
Let me know if it still shows like it is not activated. If the manual process does not help I can look up if thereare bugs related.
Blessings,
-Kenny
11-18-2014 06:13 AM
Hi Kenny
here is the information
US-CUCSFISF00-01-A# scope server 1/3
US-CUCSFISF00-01-A /chassis/server # scope boardcontroller
US-CUCSFISF00-01-A /chassis/server/boardcontroller # show image
Name Type Version
--------------------------------------------- -------------------- -------
ucs-b200-m3-brdprog.11.0.bin Board Controller 11.0
ucs-b200-m3-brdprog.13.0.bin Board Controller 13.0
ucs-b200-m4-brdprog.5.0.bin Board Controller 5.0
ucs-b22-m3-brdprog.14.0.bin Board Controller 14.0
ucs-b22-m3-brdprog.8.0.bin Board Controller 8.0
ucs-b230-m1-pld.B230100C.bin Board Controller B230100C
ucs-b230-m1-pld.B230100D.bin Board Controller B230100D
ucs-b230-m2-pld.B230100C.bin Board Controller B230100C
ucs-b230-m2-pld.B230100D.bin Board Controller B230100D
ucs-b250-m1-pld.111026-111026.bin Board Controller 111026-111026
ucs-b420-m3-brdprog.10.0.bin Board Controller 10.0
ucs-b420-m3-brdprog.8.0.bin Board Controller 8.0
ucs-b440-m1-pld.B440100C-B4402006.bin Board Controller B440100C-B4402006
ucs-b440-m2-pld.B440100C-B4402008.bin Board Controller B440100C-B4402008
ucs-EXM4-1-brdprog.4.0.bin Board Controller 4.0
I don't see B250-M2; however, the HFP has such an entry see screenshot (55).
When I do a activate, it is complaining that there is a HFP, and will refuse to do it (most likely the force would override that).
US-CUCSFISF00-01-A /chassis/server/boardcontroller # show firmware
BoardController:
Running-Vers: N/A
Package-Vers:
Activate-Status: Ready
US-CUCSFISF00-01-A /chassis/server/boardcontroller # show version
BoardController:
Running-Vers: N/A
Package-Vers:
Activate-Status: Ready
This looks very strange ! should we prepared to experience a disaster ?
Before the upgrade, the situation looked llike this (meaning also no B250-M2)
US-CUCSFISF00-01-A /chassis/server # scope boardcontroller
US-CUCSFISF00-01-A /chassis/server/boardcontroller # show image
Name Type Version
--------------------------------------------- -------------------- -------
ucs-b200-m3-brdprog.11.0.bin Board Controller 11.0
ucs-b200-m3-brdprog.13.0.bin Board Controller 13.0
ucs-b200-m4-brdprog.5.0.bin Board Controller 5.0
ucs-b22-m3-brdprog.14.0.bin Board Controller 14.0
ucs-b22-m3-brdprog.8.0.bin Board Controller 8.0
ucs-b230-m1-pld.B230100C.bin Board Controller B230100C
ucs-b230-m1-pld.B230100D.bin Board Controller B230100D
ucs-b230-m2-pld.B230100C.bin Board Controller B230100C
ucs-b230-m2-pld.B230100D.bin Board Controller B230100D
ucs-b250-m1-pld.111026-111026.bin Board Controller 111026-111026
ucs-b420-m3-brdprog.10.0.bin Board Controller 10.0
ucs-b420-m3-brdprog.8.0.bin Board Controller 8.0
ucs-b440-m1-pld.B440100C-B4402006.bin Board Controller B440100C-B4402006
ucs-b440-m2-pld.B440100C-B4402008.bin Board Controller B440100C-B4402008
ucs-EXM4-1-brdprog.4.0.bin Board Controller 4.0
Thanks Walter.
11-18-2014 06:13 AM
Walter,
If it is not listed there I don't think the force option will do the trick. I just checked a few versions I have in my lab and I don't see a board controller option for the B250 either. One can actually go to Equipment>Equipment>Firmware Management>Packages and expand the bundles to look for the different firmware versions included with each package, the B250-M2 board controller is not listed; HOWEVER, I happened to have a B250 in my lab and I checked the board controller version and it is the same as the B250-M1, can you try the steps I gave you with the board controller version of the B250-M1?
-Kenny
11-18-2014 06:29 AM
Kenny
I could not try your command ! it's a highly business critical environment !
Anyway, would you use then the file for B250-M1 for a B250-M2 blade ?
The following screenshots show the situation of the board controller before and after the firmware upgrade.
Do you agree, that the server update with HFP should properly also include Board Controller ?
11-18-2014 06:32 AM
1-yes (as long as you use the board controller version that matches the new firmware)
2-Yes, I have set in that way in my lab
-Kenny
11-18-2014 06:43 AM
Thanks Kenny
I have to convince the customer ! This CLI fix is definitely not a nice solution ! He would like to have a UCS manager GUI solution.
11-18-2014 07:07 AM
If the CLI works we can look for a bug (if any, or create it) to see the reason for that.
-Kenny
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide