- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- ERROR 329 333 270 Firmware commnunication error
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-30-2020 02:24 AM
11-30-2020 02:24 AM
ERROR 329 333 270 Firmware commnunication error
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2020 08:30 AM
12-01-2020 08:30 AM
Re: ERROR 329 333 270 Firmware commnunication error
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
I am an HPE employee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2020 02:24 PM
12-01-2020 02:24 PM
Re: ERROR 329 333 270 Firmware commnunication error
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2020 08:30 AM - edited 12-02-2020 08:31 AM
12-02-2020 08:30 AM - edited 12-02-2020 08:31 AM
Re: ERROR 329 333 270 Firmware commnunication error
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2020 02:37 PM - edited 12-03-2020 02:15 PM
12-02-2020 02:37 PM - edited 12-03-2020 02:15 PM
Re: ERROR 329 333 270 Firmware commnunication error
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-10-2020 10:47 AM
12-10-2020 10:47 AM
Re: ERROR 329 333 270 Firmware commnunication error
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2023 02:24 AM
02-14-2023 02:24 AM
Re: ERROR 329 333 270 Firmware commnunication error
I have all these errors at once: 329, 270, 312, 333
and it was problem with loop in network?! Belive or not!