topic Re: Ignite PXE-E18 Timeout Server did not respond. in Operating System - HP-UX

Ignite PXE-E18 Timeout Server did not respond.

shashi kanth — Wed, 20 Jan 2010 06:11:17 GMT

I have Ignite server on 11iv3 0309.

Trying to install the OS on BL860c.

The client and Ignite server both are in same subnet.

Created a dbprofile on client, and issued the lanboot command, which ended with error bellow.

Retrieving File Size
PXE-E18: Timeout. Server did not respond.
Exit status code: Invalid Parameter

The NFS, inetd, and other processes are running on the server side, i can able to install the OS on other RX/RP boxes.

How can i solve this issue. Thanks.

Re: Ignite PXE-E18 Timeout Server did not respond.

shashi kanth — Wed, 20 Jan 2010 06:19:45 GMT

The client is having following firmware versions.

System Firmware: 4.21 [4907]
BMC Version: 5.36
MP Version: T.03.12

Re: Ignite PXE-E18 Timeout Server did not respond.

AVV — Wed, 20 Jan 2010 07:56:18 GMT

Hmmm.......

BL860c and igniting has become a problem to many including me.

Just a question before going deeper into,

are you using a cable which is connected back from Ignite Server and straight to the client ? If yes, what kind of cable you used ? straight or cross.

It seems your configurations OK and contacting servers also and comes into an error.

Re: Ignite PXE-E18 Timeout Server did not respond.

Scot Bean — Thu, 21 Jan 2010 18:43:15 GMT

Could be lots of reasons network may not work or be setup for this PXE/bootp protocol.

If other boxes are working, I would suspect the setup on the Bl860c in question:
1. double-check the 'dbprofile' settings you made, compare them to a machine that is working.

2. double-check the LAN card you used for the lanboot. The right one? Is Virtual Connect or other blade settings preventing?

3. This white paper has some 'lanboot' troubleshooting help: http://www.docs.hp.com/en/5992-5274/5992-5274.pdf

(Note: subnet should not matter with 'dbprofile', it can span subnets)