lanboot select or lanboot with a profile fails

[N Ward]

Trying to restore a VM with a newly created ignite server. The lanboot fails with PXE-E16 Valid PXE offer not received.

I have bootptab entry for the client on the server, they are both on the same subnet.

[Torsten.]

The client gets no response from the server, so I would double check the config first.

[N Ward]

Herein lies the problem, the bootptab entry to me looks correct. It has the correct client ipaddress, gateway and subnet mask. inetd has the tftp and bootps entries allowed. Anything else I am missing? Both servers are Itanium.

[Torsten.]

If you are using a profile the bootptab isn't used. So I would check the VM config for correct LAN settings first.

[N Ward]

Thanks for your reply, I'm not sure what I should be checking. The VM can see the ignite server and when the VM is up I can ping it. What else should I check?

[Stanimir]

Hello!

If you are using IVM, please find that
"avio-lan" -driver is not compatible with Ignite. Try change it to "lan".
It was real reason not to boot for me
some weeks ago.

BR, Stan

[N Ward]

Hi apologies for my ignorance, what is IVM? Itanium VM? for these boxes should I be initiating a restore in a different way? I am using either lanboot select or lanboot select -dn igniteserver.

[N Ward]

I have ran the bootpquery from the client I wish to restore and it works ok, reporting information back from my ignite server. If I run the bootpquery on the ignite server it just comes back with

bootpquery: Bootp servers not responding!

I discovered also that the hardware address needed to drop the leading 0x

[sujit kumar singh]

hi

yes in /etc/bootptab file when you enter the clients MAC Address for ha: there is no leading 0x required.

apart from that once more you said that the server is responding for "bootpquery".

thats true.

cab you also try if the tftp is running.

make tftp to the Ignite server and try getting the file that is /opt/ignite/boot/nbp.efi and also for /opt/ignite/boot/Rel_B.11.31/IINSTALL and /opt/ignite/boot/Rel_B.11.23/IINSTALLFS --- note well --If i remember the paths correctly.

bascially on the ignite server in /etc/inted.conf make sure

tftp
bootps
instl_boots are uncommented.

make sure that you run #inted -c after you make any changes to /etc/inetd.conf



in /etc/services on the ignite server, make sure that you are having ports open for

tftp 69
instl_boots 1067
instl_bootc 1068
bootps 67
bootpc 68

are free and reachable.


also please note that


/opt/ignite/boot/nbp.efi is intact on the server and also /etc/bootptab can show you that this entry is there as

bf=/opt/ignite/boot/nbp.efi:\


Also make sure that there is no other competing DHCP server racing with the Ignite server on the network.


regards
sujit

[sujit kumar singh]

Hi also for the lanboot select create a profile specifying exactly the boot file like this:


SHELL>dbprofile -dn test -sip -cip -gip -m -b /opt/ignite/boot/nbp.efi

SHELL>dbprofile -- this lists the boot profiles.


SHELL>lanboot -dn test


regards
sujit