1 of 1 people found this helpful
Integrated BMC Force Update Procedure
1. Power down and remove the AC power cord.
2. Open the server chassis. For instructions, see your server chassis documentation.
3. Move jumper (J1E2), from the default operating position (covering pins 1 and 2) to the enabled
position (covering pins 2 and 3).
4. Close the server chassis.
5. Reconnect the AC cord and power up the server.
6. Perform the Integrated BMC firmware update procedure in EFI.
After successful completion of the firmware update process, the firmware
update utility may generate an error stating that the Integrated BMC is still in update
1) Verify that the following files are present in the directory:
upd_BMC.NSH; FWPIAUPD.EFI; BMC_0119.ima; IPMI.EFI
2) At the EFI command prompt type upd_BMC.nsh and hit enter
The update should take approximately 3-5 minutes to complete
7. Power down and remove the AC power cord.
8. Open the server chassis.
9. Move jumper from the enabled position (covering pins 2 and 3) to the disabled position
(covering pins 1 and 2).
10. Close the server chassis.
11. Reconnect the AC cord and power up the server.
12 update FRUSDR
I've already tried this different times (always with AC disconnect for min. 10secs, etc.).
BMC updates successfully with jumper set, but does not respond after step 11 to anything (as like before).
This is what works with jumper set to "(2-3) Force BMC Update":
- Updating BMC with upd_BMC.nsh
- Updating BIOS
This is what works with jumper set to "(1-2) default":
- Updating BIOS
So FRUSDR.efi isn't able to talk to BMC in any circumstances.
Any other ideas/suggestions?
Are there some special EFI Programs that don't rely on IPMI.efi or communication to FRUSDR via BMC?
Yes, the one you just ran
When you do a force BMC update (jumper J1A2 back corner of mother board), it flashes the FW for the BMC operational code in KVM mode, clears the BMC NVram and loads the default SDR values.
When you replace the jumper to the operational position and power cycle, the BMC reads the OP code and boots the BMC which can then process the IPMI traffic.
It is sounding like you have a hard failure in the BMC, or BMC boot block corrupted or something hanging the BMC i2C Bus.
- You may want to disconnect any devices connected to the i2c bus (RMM, backplane, front panel) and see if the BMC comes back.
- You could also try reflashing the boot block by adding the -b to the flash command string in the upd_BMC.nsh
(fwpiaupd -b-u -bin -o -ni -pia BMC_0119.ima) (I have never tried this on a GP board and it is usually the option of next to last resort)
- Last resort is replace the board