Ignite lanboot problems...

[Eric Ladner]

I've read through dozens of posts with similar issues and tried to eliminate all the problems I could, but I'm still getting bizarre timeouts on the Ignite server.

Setup: Both machines on the same subnet, both machines are the same type (rx2660), Ignite (C.7.9.261) server is 11.31. dbprofile is set up on the client machine to point to the server directly.

Booting the client produces this:

Client MAC Address: 00 1C C4 FC 74 D5
Client IP Address: 10.0.59.232
Subnet Mask: 255.255.248.0
BOOTP Server IP Address: 10.0.59.250
DHCP Server IP Address: 0.0.0.0
Boot file name: /opt/ignite/boot/nbp.efi

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

On the server, it produces this in the logs (tfptd logging increased..)

Apr 16 09:08:22 ignite tftpd[11826]: receive: RRQ /opt/ignite/boot/nbp.efi octet blksize 512 tsize 0
Apr 16 09:08:22 ignite tftpd[11826]: send: OACK blksize 512 tsize 31232
[ previous two messages repeat several times ]
Apr 16 09:08:42 ignite tftpd[11759]: Transfer timed out
Apr 16 09:08:44 ignite tftpd[12000]: receive: RRQ /opt/ignite/boot/nbp.efi octet blksize 512 tsize 0
Apr 16 09:08:44 ignite tftpd[12000]: send: OACK blksize 512 tsize 31232
Apr 16 09:08:47 ignite tftpd[11826]: Transfer timed out
[ several more receive/send/timeout messages follow, about 12 sets total ]

/etc/opt/ignite/instl_boottab contains:

10.0.59.232:::
10.0.59.235:::
10.0.59.236:::

boot file exists:

# ls -ld /opt/ignite/boot/nbp.efi
-r--r--r-- 1 bin bin 31232 Jan 13 2009 /opt/ignite/boot/nbp.efi


Ideas?

[Eric Ladner]

Also, PHNE_39443 (bootpd(1M)/DHCP, tftp(1) and tftpd(1M) patch) is installed.

[Eric Ladner]

Relevant inetd.conf stuff:

bootps dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd

tftp dgram udp wait root /usr/lbin/tftpd tftpd -l \
/opt/ignite \
/var/opt/ignite

[Tim Nelson]

I seem to recall this as an old problem but either fixed with an OS patch or Ignite version. Your version is fairly new.

2 thoughts.

1) upgrade Ignite to the latest ( ignite always seems to have some problem with something )

2) use NFS instead of tftp ( this is new as of 7.9.254 ) i am planning on moving to NFS also, so this may just solve your issue permentently ?

I know that my 11.11 and 11.23 clients booting from 11.31 server have worked fine for a number of years now 7.5.142 ( i hesitate upgrading because my current version works )

There are more instl_adm settings that you can try, e.g. if you have 10/100 NICs force to 100MB ( check out the Ignite admin guide on how to )

[Eric Ladner]

My understanding is NFS is used only when creating a net recovery for existing clients, not for booting a new client from the Ignite server (does the EFI shell know about NFS?)

[Tim Nelson]

I saw this in the C.7.9.254 release notes..

Ignite-UX version C.7.9.254 contains the following new features:
- Ignite-UX now supports the use of NFS instead of TFTP for
transferring files from the server to the client during system
installation and recovery. To support this feature, the locations of
several files (/opt/ignite/Version, /var/opt/ignite/INDEX, and
/var/opt/ignite/config.local) have been changed. See the September
2009 (or later) version of the Ignite-UX Administration Guide and the
description of



read for yourself here...

http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01942662/c01942662.pdf

[Eric Ladner]

Ah. I think I found the issue. I THINK what was happening since I was using the inetl bootp server, it was responding to any bootp request, so I switch to the DHCP server restricted to Ignite requests (section 4.3.1.3) and things starting working magically.

Thanks for pointing me in the right direction