Bootp issue from Itanium to PA

[Terry Handel]

Hi

Was wondering if someone could help.

I am trying to get an Itanium to BOOTP off a PA system.

I have configured the bootptab on the PA to resemble the following:

ausyss01:\
hn:\
vm=rfc1048:\
ht=ether:\
ha=00110A3167B4:\
ip=172.16.8.57:\
sm=255.255.248.0:\
bf=/opt/ignite/boot/boot_lif

I try and EFI the new system using the GIG network to BOOTP off the systems lan and the error message I get is the following:

Loading.: Langig
Running LoadFile()

CLIENT MAC ADDR: 00 11 0A 31 67 B4
.....
PXE-E16: Valid PXE offer not received.
Load of Langig failed: Not Found

Using the DHCP on the PA is not an option unfortunately....

I have made sure that the bootp and tftp is running on the PA , and have looked at the /var/adm/inetd.sec and the /var/adm/syslog/syslog.log and nothing outstanding is showing up.

Any advice?

Only thing is that the ITanium and PA are separated by 2 layer 3 and one layer two switch. Could this be causing the lack of BOOTP responses from the PA machine?

Any advice appreaciated.

Thanks

Terry

[Mel Burslan]

The answer is : It depends. My experience with network booting so far, bootp prtocol does not like hopping through the subnets and vlans in order to boot. I am not sure how your switches are configured but if the client who is booting and the bootp server are on the same subnet, this should not be an issue. But if they are on different subnets, you may want to consider setting up a boot helper (see ignite UX manuals to set up one, pretty easy process) on the same subnet as the client.

Hope this helps

[Terry Handel]

Thanks for the reply - they are on the same subnet and vlan....

Yes - will look into the helper.

Thanks

Terry

[Torsten.]

Hi Terry,

I'm not experienced in booting an itanium box from net, but are you sure you're using the correct bootfile? I would expecting something like *.efi. Did you use
Shell> lanboot select
Just wondering about PXE message.

[Torsten.]

Found in documentation:

The changes to instl_bootd require that the bootpd daemon is not running on the given Ignite-UX server. Ignite-UX uses the instl_bootd daemon to respond to all boot requests from clients. The instl_bootd daemon normally runs on a set of unique network ports, 1067/1068, which are used only for booting Itanium-based clients. However, in this implementation, the instl_bootd runs on the standard bootpd ports, 67/68.

==================
have a look:
http://docs.hp.com/en/B2355-90875/ch02s03.html#d0e2845

[Steven E. Protter]

From Ignite class.

You can only boot off the built in NIC? Not any add in cards. Now the newservers have built in GB NIC so its not a speed loss.

After boot, you can transmit Ignite images any way or NIC you wish.

SEP

[Bill Hassell]

It is very common for network admins to block UDP broadcast requests at the router so whether bootp or DHCP, none of the requests are getting through. You can verify this by issuing the linkloop command from the Itanium box to the PA box. It issues a NIC-to-NIC query that is normally never routed so if it fails, the machines are not on the same network. The concept of a helper machine is to provide a mini-kernel on the same network so a box can bootup with enough code to understand subnets and routing tables.

[Michael Roberts_3]

I have a B2000 running B.11.11 that serves PA and IA cliens via net boot. My /etc/inetd.conf has:
$grep boot /etc/inetd.conf
bootps dgram udp wait root /usr/lbin/bootpd bootpd
instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd

my /etc/bootptab has:
(substitute valid IP address for '')
(substitute valid MAC for '' )

IADEF:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48:\
sm=255.255.248.0:\
gw=:\
ds=:\
dn=corp.com:\
vm=rfc1048:

myIAclient:tc=IADEF:ip=:ha=:

[Terry Handel]

Hi

My server are HP4400 - with only built in nics.

They are having hassles locating any BOOTP server - ie - with its mac address and IP configured on the Server - the client is not seeing any machine to service its BOOTP request. I am unsure if the issue is the bootptab conf, or should it be done in the ingite bootp conf. I will look into this today.

I need to try and find out if its an issue of switches blocking the bootprequest - or if its the server not configured correctly to pic up the requests.

Thanks all for the responses.

Terry

[Bill Hassell]

Your server will see bootp requests if they occur on the same LAN. Switches typically don't have packet filtering, but routers will always default to block all bootp requests between subnets. You can easily verify this by connecting a machine on the same network and see if it finds the bootp server.