Ignite-UX

Integrity Virtual Machines booting from a Ignite/UX DART server.

 
SOLVED
Go to solution
Sander_4
Advisor

Integrity Virtual Machines booting from a Ignite/UX DART server.

I just installed Integrity Virtual Machines on a RX2600 for testing. I tried to do a lan boot so that I can use an ignite server vor installation. The boot goes fine but the TFTP failes. When it tries to download the fpswa.efi file is says "TFTP session failed. (reason:Buffer Too Small) No EFI FPSWA handle found.

Then it still goes on to downloading the IINSTALL file but it failes with the same error. How do I increase the buffer, or what else am I doing wrong, or where do I have to look?
If it works perfectly, it must be broke.
3 REPLIES 3
John P. Kole
Frequent Advisor
Solution

Re: Integrity Virtual Machines booting from a Ignite/UX DART server.

What version of HP-UX is your Ignite-UX server running?
[If it's B.11.23, be sure you are not using the "-r tsize"
option on the tftpd service in your /etc/inetd.conf file]

Also, I've just learned the site specific B.11.11 patch is
available upon request from HP customer support.

Here's my understanding of the whole issue:

The VM IPF clients, using PXE, will attempt to do tftp "option
negotiation" with their server. This is done to determine if
the tftp server supports the "tsize" option. This option will
enable a tftp server to tell the client how big a file is
*before* it is transfered.

If the tftp server supports this "tsize" option, it will tell
the tftp client how big the requested file is, the tftp client
will then allocate a buffer big enough to hold the entire file,
and then the tftp client will request the file from the server.

If the tftp server does not support this "tsize" option, the
tftp client must first transfer the entire file (and basically
write it to /dev/null) just so it can determine the file size.
Once this transfer is over, the client then knows the file size
and the client will allocate a buffer large enough to hold the
file, and then re-pull the file from the server.

The bug comes in when the server is running HP-UX B.11.00
or B.11.11 (with no "tsize" option) and the tftp client gets the
buffer size calculation wrong. The buffer size computed (and
thus allocated) is too small to hold the entire file... leaving
us with the error message "Buffer Too Small".

Once these B.11.00 and B.11.11 servers are patched
appropriately, they will no longer fail with this error,
and they will no longer transfer each file twice because
the patch will enable the "tsize" option on the server.

Thanks to Shane for all the good information here (and above).
What could possibly go wrong?
Sander_4
Advisor

Re: Integrity Virtual Machines booting from a Ignite/UX DART server.

I run my Ignite server on 11.11. I didn't have any other option as this is an DART version of Ignite. I run a training center where HP educations are given. (HP does not do this them selves in the Netherlands). But Dart or not a Dart. I don't think that matters as this is a TFTPD problem.

How site specific is that patch? (weird that it is not freely available)
If it works perfectly, it must be broke.
Oleg Sukharev
Valued Contributor

Re: Integrity Virtual Machines booting from a Ignite/UX DART server.

Maybe this patch helps: PHNE_32825