05-16-2019 09:38 AM
We still have some B230 M2s in our domain which we recently upgraded to 3.2.3k. These B230 M2s have VIC 1280 which is supported on this FW version according to the HCL. I associated the Host Firmware Policy with the service profile and this blade gets stuck halfway through at 48% on step# 42.
It just says status fail:
Associate Pnu OS (This is what the step is named)
Identify pre-boot environment agent (This is the description)
Anyone ever had to deal with this for a B series blade? My other blades have upgraded without any issues. I have seen this before during discovery sometimes when I first connect a C-series server. I think they basically say to decommision the server and then reconnect to force discovery.
Right now it is just cycling through the steps over and over again. Any suggestions on how to resolve this?
05-16-2019 10:27 AM
05-16-2019 10:52 AM
BIOS is still the older version actually. Should I just roll it back in the service profile and then have it go through again?
05-16-2019 11:49 AM
05-16-2019 02:23 PM
I ended up opening a TAC case and they determined the BIOS was corrupted and need to RMA the blade.
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