OA failed during f/w update, trying to restore f/w

[sknickhp]

Tried to update a chassis with dual OA to v4.85

One OA updated fine, other one hung up during the update.  After a long while, I reseated it.  I can use the reset button to get the Health LED to go from RED to GREEN, and I can interact with recovery mode over a serial connection.

I press F to load firmware, get a DHCP IP address, and then give it the TFTP server IP & filename 'hpoa485.bin'.  It says "Downloading ROM..." and never does anything after that.  If I give it a bad filename, it will come back with an error.

Anyone done this successfully before & have any tips?  Thanks!

[Torsten.]

Maybe a problem with your local firewall (windows defender, etc)?

[sknickhp]

TFTP server is on the same subnet as the OA when it grabs the DHCP IP address

[Torsten.]

A local firewall on the system where TFTP server is running?

[Torsten.]

I have done this successfully several times.

HP Onboard Administrator booting...

Lost Password or Flash Recovery requested
Press L for Lost Password Recovery
Press F for Flash Recovery
Press any other key to reset

Flash Recovery Mode

Obtaining DHCP Address...ENET Speed is 10 Mbps - HALF duplex connection
BOOTP broadcast 1
DHCP client bound to address 10.10.38.240
Done

Please enter the IP address of the tftp server at the next prompt.
Please enter 'serverip':10.10.38.241


Please enter the filename of the ROM image at the next prompt.
Please enter 'bootfile':hpoa480.bin


Downloading the ROM...Done!

Verifying ROM image....Done!

Flashing your Onboard Administrator.  This will take several minutes.
Do not power off or reset until the process completes
Flashing...
..
..
..Done!

Flash procedure succeeded.
Restarting the Onboard Administrator.

[sknickhp]

Actually you were right in a sense, thanks!

2 things

I had an IP subnet restriction on my TFTP server that was blocking that subnet.  Turned it off & the transfer worked.

Still failed the f/w verification process on 4.85.  So I went back to the bin file of the f/w version it was running before the upgrade, and that allowed it to reflash & work again.