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

PXE-E18: Timeout. Server did not respond

Carme Torca — Thu, 17 Jun 2010 09:14:41 GMT

Hi,

I have problems with one restore of one ignite.
The cable its connected but the Server doesn't respond.

Could anyone help me?
Thanks a lot of!
Carmen.

Shell> lanboot select -dn ignite_rec
01 Acpi(HWP0002,PNP0A03,101)/Pci(1|0)/Pci(6|0)/Mac(002481D969D6)
02 Acpi(HWP0002,PNP0A03,101)/Pci(1|0)/Pci(6|1)/Mac(002481D969D7)
03 Acpi(HWP0002,PNP0A03,102)/Pci(1|0)/Mac(002481773BF4)
04 Acpi(HWP0002,PNP0A03,102)/Pci(1|1)/Mac(002481773BF5)
Select Desired LAN: 04

Client MAC Address: 00 24 81 77 3B F5

LAN Configuration:
Client MAC Address : 00 24 81 77 3B F5
Client IP Address : 14.10.27.240
Subnet Mask : 255.255.255.0
Boot Server IP Address : 14.10.27.25
DHCP Server IP Address : 0.0.0.0

Retrieving File Size

Boot file name: /opt/ignite/boot/nbp.efi
Boot file size: 0 bytes

PXE-E18: Timeout. Server did not respond.

Usage:
LANBOOT [select] [-od "optional_data"]
LANBOOT [select] [-dn name]
LANBOOT [select] [-sip server_ip] [-cip client_ip] [-gip gateway_ip]
[-m subnet_mask] [-b "boot_file"] [-od "optional_data"]

Execute 'help lanboot' for more help.
Shell>

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

Torsten. — Thu, 17 Jun 2010 10:42:05 GMT

First check this:

Boot file name: /opt/ignite/boot/nbp.efi
Boot file size: 0 bytes

Does this file exist?

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

Carme Torca — Thu, 17 Jun 2010 11:12:04 GMT

Yes,

The nbp.efi exist

ls -l /opt/ignite/boot/nbp.efi
-r--r--r-- 1 bin bin 24576 Feb 15 2007 /opt/ignite/boot/nbp.efi

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

Torsten. — Thu, 17 Jun 2010 11:18:43 GMT

Do you need by chance a gateway?

Gateway IP address (-gip)
in dbprofile

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

Carme Torca — Thu, 17 Jun 2010 11:23:48 GMT

Here you are the configuration:

Shell> dbprofile
Profile List

Profile Name: ignite_rec
Network Type: IPv4
Server IP address: 14.10.27.25
Client IP address: 14.10.27.240
Gateway IP address: 14.10.27.1
Subnet Mask: 255.255.255.0
Boot File: /opt/ignite/boot/nbp.efi
Optional Data:

Shell>

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

Torsten. — Thu, 17 Jun 2010 11:34:39 GMT

Sure you can contact the server via this NIC?

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

Scot Bean — Thu, 17 Jun 2010 14:27:41 GMT

On the 14.10.27.25 server, check /etc/inetd.conf to make sure bootp is enabled.

You can also use '-d 9' on bootp to turn on debugging and watch the syslog when attempting boot.

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

Fabio Ettore — Thu, 17 Jun 2010 14:42:02 GMT

Hi Carme,

I've already experienced this problem, I'd guess it's something about tftp service on Ignite-UX Server. Check that it's enabled (not commented out) and well-configured into /etc/inetd.conf.

A quick test on Ignite-UX server to show if it works:

cp /etc/services /tmp
cd tmp
tftp localhost
tftp>get services

If you see something like

Received 11327 bytes in 0.0 seconds

then the service is enabled, otherwise it's not.

HTH.

Best regards,
Fabio

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

Steven E. Protter — Thu, 17 Jun 2010 14:51:29 GMT

Shalom,

Based on what I see, I would check the inetd.conf configuration on the Ignite server.

I would see that bootp and tftp and instl_boots are not commented and restart inetd. This would be on the Ignite server as well.

I would check for other PXE servers and see if you chose the right NIC card to talk to the Ignite server.

SEP

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

Carme Torca — Fri, 18 Jun 2010 05:39:27 GMT

Hi,
I have all ok configured on the server, I have reset de inetd but it doesn't works ok.
???

>more /etc/services |grep -i boot
bootps 67/udp # Bootstrap Protocol Server
bootpc 68/udp # Bootstrap Protocol Client
instl_boots 1067/udp # installation bootstrap protocol server
instl_bootc 1068/udp # installation bootstrap protocol client

>more /etc/services |grep -i tftp
tftp 69/udp # Trivial File Transfer Protocol

>cp /etc/services /tmp/
>cd /tmp

tmp>ls -l servic*
-rw-r--r-- 1 root sys 12137 Jun 18 08:40 services

>tftp localhost
tftp> get services
Error code 2: Access violation
tftp>

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

Fabio Ettore — Tue, 27 Jul 2010 09:50:13 GMT

Hi Carme,

sorry for the delay.

>tftp localhost
tftp> get services
Error code 2: Access violation
tftp>

it means tftp is now working.
Check inetd.conf which should contain /opt/ignite and /var/opt/ignite.

Follow the Ignite-UX FAQ:

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c02023840/c02023840.pdf

Look for tftp, I think you'll find all you need about the correct configuration of tftp in inetd.conf.

Until you don't solve it the Ignite-UX server cannot work as expected.HTH.

Best regards,
Fabio

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

Fabio Ettore — Tue, 27 Jul 2010 09:56:43 GMT

Typo:

"it means tftp is now working. "

I meant, "it means tftp is not working"