topic Re: ERROR 329 333 270 Firmware commnunication error in ProLiant Servers (ML,DL,SL)

ERROR 329 333 270 Firmware commnunication error

absicamara — Mon, 30 Nov 2020 10:24:44 GMT

Hello Dears,

I need your input on the following issue we're facing.

After a restart of a DL360 GEN9, we had the following errors

329-Power Management Controller FW Error – Unable to communicate with the FW. Action: Reset iLO FW. If issue persists reset the Power Management Controller FW (remove AC). If issue persists attempt to update the FW.

LO FW Communication Issue – Unable to communicate with iLO FW. Certain management functionality is not available".

333-HPE RESTful API Error - Unable to communicate with iLO FW.BIOS configuration resources may not be up-to-date. Action:
Reset iLO FW and reboot the server. If issue persists, AC power cycle theserver

We couldn't boot into the OS (2012 r2) so we tried to revert to the backup ROM. Now we're facing an error : REDUNDANTFOM ERROR

System utilities are not even available for us to change to the primary rom

Here are some additionnal steps we've done so far :

- tried to access the ILO GUI but no response

- We AC powered off the servers but in vain

- I should also note that this server had its ILO upgraded a while ago.

I appreciate your time

Re: ERROR 329 333 270 Firmware commnunication error

vijay9 — Tue, 01 Dec 2020 16:30:44 GMT

Hello,

Redundant ROM Error: The Primary System ROM is invalid. The system is operating on the Backup System ROM.

Action: Flash the System ROM to the desired revision to restore System ROM Redundancy.

Power down and remove all power from the server.
Flash the latest bios and check the status,
update the ILO management controller and interface driver and PMC firmware and check the status.

Regards,

Vijay

Re: ERROR 329 333 270 Firmware commnunication error

absicamara — Tue, 01 Dec 2020 22:24:07 GMT

I really thank you for your time.

One more question before i proceed.

After flashing the components you mentioned, will i still be able to recover the OS the server had before ?

Thanks once more.

Re: ERROR 329 333 270 Firmware commnunication error

LesRMed — Wed, 02 Dec 2020 16:31:35 GMT

None of the things mentioned should have any affect on the installed OS, but as always, I hope you have a backup just in case.

Re: ERROR 329 333 270 Firmware commnunication error

absicamara — Thu, 03 Dec 2020 22:15:51 GMT

I see. Thank you.
I downloaded the latest SPP and made a bootable usb using the usbkey tool from the iso file.
I when i boot the server on the pendrive, i run into the following error

Code Bad RIP number
Kernel Panic - not syncing : Fatal exception in interrupt
ERST [Firmware warn] : Firmware does not respond in time.

I have been trying all day and i'm running out of options.

I'll truly appreciate your input on this

Re: ERROR 329 333 270 Firmware commnunication error

absicamara — Thu, 10 Dec 2020 18:47:54 GMT

Hello,

Has anyone an idea ?

I reinstalled the server with Redhad linux Enternprise 7 since i couldn't do so with Windows (It gets stuck at hpe logo with the loading circle running on and on).

i ran launch_sum:sh, accessed the GUI and started the update process: that worked for my NIC drivers but the firmware failed : the software will not be installed... required hardware is not present or firmware doesn't apply to this system.

i used SPP 2020 version

i tried to update the ILO firmware but i kept receiving : hpilo ... open could not dequeue a packet

can anyone suggest me a fix ?

Thank you for your time

Re: ERROR 329 333 270 Firmware commnunication error

medaxc — Tue, 14 Feb 2023 10:24:49 GMT

I have all these errors at once: 329, 270, 312, 333

and it was problem with loop in network?! Belive or not!