LAN boot rx2660

[Dusty Mjoen]

Hi,

I am an ignite rookie and need to be able to boot an rx2660 over the LAN to our ignite server for recovery purposes. I have successfully run the make_net_recovery. My ignite server is 172.25.X.X, and my client is 172.23.X.X. I have also created an entry in the bootptab on the server. I thought my best plan of attack was to create a dbprofile, but due to the fact my two servers are on different subnets, will that preclude this from working without a boot helper?

Thanks

[Steven E. Protter]

Shalom,

Boot helper is required to make this boot work.

You don't mention what version of Ignite you are using.

Unless something has changed recently a boot helper is required for this situation.

SEP

[Dusty Mjoen]

Thanks Steven. I am running ignite version 7.6.100. The server is 11iv1 and client is 11iv2. The whole boot helper concept confuses me a bit. Would the boot helper system run on the 172.23.X.X subnet? What would the requirements of that server be?

Thanks!

[Tim Nelson]

dbprofile works for cross net ignite boots.

[Dusty Mjoen]

Excellent news Tim. So after creating the dbprofile, can the lanboot command be added as an option when I create a new boot option in the EFI menu?

[Tim Nelson]

Not sure about the boot option with lanboot, might have to read the EFI guide. I always just executed from the shell.


Here is a dpprofile example, note the different subnets.
Shell> dbprofile -dn IUX â cip 172.20.103.100 -sip 172.26.0.19 -gip 172.26.103.25 -m 255.255.255.192 -b "/opt/ignite/boot/nbp.efiâ

Then
Shell>lanboot select -dn IUX


I typically ctrl-c the DHCP during the Ignite boot and type in my own IP and other config items.

[Dusty Mjoen]

Thanks for the replys, I think I'm making progress. However, I am getting these PXE errors, they pop up almost instantly. Any ideas?

Shell> lanboot select -dn igniteprof
01 Acpi(HWP0002,PNP0A03,200)/Pci(2|0)/Mac(0017A499AD63)
02 Acpi(HWP0002,PNP0A03,200)/Pci(2|1)/Mac(0017A499AD62)
Select Desired LAN: 01
Selected Acpi(HWP0002,PNP0A03,200)/Pci(2|0)/Mac(0017A499AD63)


Client MAC Address: 00 17 A4 99 AD 63
Client IP Address: 172.23.70.220
Subnet Mask: 255.255.255.0
BOOTP Server IP Address: 172.25.202.6
Gateway IP Address: 172.23.70.1
DHCP Server IP Address: 0.0.0.0
Boot file name: /opt/ignite/boot/nbp.efi

Retrieving File Size..
PXE-E23: Client received TFTP error from server.
PXE-E98: Code: 1h File not found
Exit status code: Invalid Parameter

Shell>

[Tim Nelson]

Couple questions:

1) post your dbprofile output.

2) What version of ignite are you using

3) What version OS is the ignite server on ?

4) Does your ignite server have the 11.23 tools ? Post swlist|grep -i ignite

[Dusty Mjoen]

Here ya go:

Shell> dbprofile
Profile List

Profile Name: igniteprof
Network Type: IPv4
Client IP address: 172.23.70.220
Gateway IP address: 172.23.70.1
Subnet Mask: 255.255.255.0
Server IP address: 172.25.202.6
Boot File: /opt/ignite/boot/nbp.efi
Optional Data:

I am running ignite version 7.6.100.

The Ignite server is version 11.11.

# swlist | grep -i ignite
IGNITE C.7.6.100 HP-UX Installation Utilities (Ignite-UX)
Ignite-UX-11-11 C.7.6.100 HP-UX Installation Utilities for Installing 11.11 Systems
#

[Dusty Mjoen]

I don't know if this is meaningful or not, but I also get these tftp messages intermittently since installing ignite.

Aug 12 14:57:55 dns2 tftpd[13543]: Timeout (no requests in 10 minutes)

[Tim Nelson]

The timeout messages are cool.. I get them all the time during loads.

I am not sure if this is still an issue in the current version. But..

I had to move my ignite server to an Itanium host due to some tftp payload/transfer size issue on PA-RISC.

I do know for sure that once I moved to IA I have no issues Igniting my mixed environment.
11.11, 11.23 (PA-IA), and 11.31

[Dusty Mjoen]

I wish I had another Itanium server to check the theory. Oh well, back to the drawing board. I certainly appreciate the help you all have given!

[Tim Nelson]

Might be worth a call to HP. They were very helpful when I ran into this.

If not then you are back to the Ignite Admin Guide with the chapter labled "boot helpers"

Either a CD or another system that is on both nets.

[Tim Nelson]

I found a reference similar to this issue. Talks about a current tftp patch for the PA-RISC. PHNE_32825 .. If you do not have this or newer it may fix your problem.

This also assumes you have all the other stuff configured correctly.

http://www.docs.hp.com/en/IUX/faq.html#1-16

section 1-17

1-17 Why is the network boot of my Itanium-based system slow?
A: To reduce the amount of time it takes to perform a network boot, you should use an Ignite-UX server that is running a tftp daemon (tftpd) that supports the "tsize" option.

When the firmware on an Itanium-based system is downloading a file (i.e. booting), it first attempts to determine the size (in bytes) of the file. If the tftp daemon (tftpd) on the server does not support the "tsize" option, the client downloads the file using the following steps:
Download the entire file (not storing the data), counting the bytes
Allocate a buffer which is the exact size of the file
Download the entire file (again) into the allocated buffer.
The B.11.11 patch that enables the "tsize" feature is PHNE_32825, which was posted on 20-Mar-2006.

NOTE: HPVM requires this patch if you are installing a virtual machine from an Ignite-UX server running B.11.11. Not having this patch installed on the server will cause the network boot to fail because of a firmware defect. No tftpd patch is required for B.11.23 onwards as the tftpd daemon supports the "tsize" option from first release.

Top

[Steven E. Protter]

Shalom,

PXE and Itanium have been known to interfere with each other.

I've been forced to do Ignite work on networks without PXE servers on them.

You may need to shut down or isolate PXE servers to get the Ignite stuff to work right.

SEP

[cobra_1]

During Ignite installing of 11iv3/rx2620, I had same error message as:

Retrieving File Size..
PXE-E23: Client received TFTP error from server.
PXE-E98: Code: 1h File not found
Exit status code: Invalid Parameter

And I solved this problem by checking the tftp entry in
/etc/inetd.conf and /etc/passwd files.
The tftpd should know /opt/ignite path.

/etc/inetd.conf:
tftp dgram udp wait root /usr/lbin/tftpd tftpd\
-l\
/opt/ignite\
/var/opt/ignite

/etc/passwd:
tftp:*:106:105:Trivial FTP user:/home/tftp:/usr/bin/false

Hopefully it be helpful.

[Dusty Mjoen]

Thanks for everyones help. My problem was that the /opt/ignite/boot/nbp.efi file did not exist. A reinstall of Ignite fixed that problem.

[Dusty Mjoen]

See above post.