Cannot network-boot rx2600 after firmware update!

[Kent C. Brodie]

Hi folks. We have a cluster of 16 rx2600 servers- identical to oneanother. Identical (this is important). For quite some time, I have been using "systemimager", a network-boot cloning tool (think: OSCAR) for these systems. HP actually supplied an older systemimager distribution on the CD's that came with the system.

Before I start- I need to stress that all 16 servers boot off of the network just fine, via the gig port(s). Systemimager basically sees a dhcp request, hands off the boot loader to tftp, elilo.efi is obtained, and you're on your way to system booting. It's kind of like PXE, but isn't. A bit simpler actually. Works very slick. Again- this has worked flawlessly for 2 years.

ANYWAY-- I have a totally bizarre situation that I'm hoping someone can help resolve.

The other day I finally decided it was time to update the firmware with these servers-- so, I grabbed the latest available, blasted it to a CD, and booted the first of the 16 servers. The BMC/EFI/MP firmware updates went smoothly (although, took quite a long time! Whoa...).

Here's the problem: The one server I updated can no longer boot from the network. The server sends out the DHCP boot request-- and the DHCP server out there RESPONDS with the information-- multiple times in fact-- but the client never gets the address, and eventually times out with the error

"PXE-E16 Valid PXE offer not received.".

Um, I'm not USING pxe, and it seems that the firmware update has somehow forced the network boot environment to "ONLY" use pxe.

OK.... highly annoyed, I decided to downrev the firmware back to where I started. I have confirmed that the client in question is now the exact same firmware rev as all my other nodes - back to where I started. (via "showrev" commands and such).

But--- same problem! On this ONE server, I can't boot from the network. I can however successfully boot the other 15 nodes without issue.

Note, the DHCP server DOES see the network boot requests, and serves up the address-- but to no avail. (see log below).

SO.... the firmware update I did has now changed the network boot to "PXE ONLY" (for lack of a better term), and I am stumped as to how to UN-DO the damage caused by the firmware update. DOWNREVving the firmware back to the same as the other hosts has made no difference.

HELP? Is there some hidden network-boot setting I can tweak or examine via the EFI shell or whatever - something that got changed by the firmare update, yet didn't get UN-done when I went back to the earlier version?

I fear trying to call HP support on this, because the person on the other end will very likely be clueless. That call could take me days. I'm hoping the experts here have an idea!

Feb 20 08:47:40 brock dhcpd: DHCPDISCOVER from 00:30:6e:f3:4b:50 via eth0
Feb 20 08:47:40 brock dhcpd: DHCPOFFER on 192.168.96.102 to 00:30:6e:f3:4b:50 via eth0
Feb 20 08:48:44 brock dhcpd: DHCPREQUEST for 192.168.96.102 (192.168.96.10) from 00:30:6e:f3:4b:50 via eth0
Feb 20 08:48:44 brock dhcpd: DHCPACK on 192.168.96.102 to 00:30:6e:f3:4b:50 via eth0
Feb 20 08:48:44 brock dhcpd: DHCPDISCOVER from 00:30:6e:f3:4b:50 via eth0
Feb 20 08:48:44 brock dhcpd: DHCPOFFER on 192.168.96.102 to 00:30:6e:f3:4b:50 via eth0
Feb 20 08:50:53 brock dhcpd: DHCPREQUEST for 192.168.96.102 (192.168.96.10) from 00:30:6e:f3:4b:50 via eth0

(Editor note: I accidently posted this earlier to "ignite" under HP-UX.. sorry for the dup).

[Prashanth.D.S]

Hi Kent,

Check if the below url helps you out.

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1049782&admit=-682735245+1172020295797+28353475

Best Regards,
Prashanth