cannot see ignite server

[Dave Chamberlin]

I am trying to use ignite server for the first time. I have configured the ignite server (I think), but when on the client I do:search lan install, I see nothing. What could the reason be? On the ignite server, bootpd is running.
Thanks

[jackie baron_1]

Are they on the same segment?
Have you added the client's IP address and MAC address into the server's /etc/bootptab file?
If this info is not in the /etc/bootptab file the server is not going to respond to the client's bootp request.

[Steven E. Protter]

Shalom,

Ignite won't boot on add in NIC cards (older versions 5.x for sure),nor will it boot across subnets without the presence of a boot helper.

http://docs.hp.com/en/5992-3336/apds01.html

Across gateways:
http://docs.hp.com/en/B2355-90153/apcs07.html

[likid0]

Here is a nice doc to take a look, with lanboot probs (tftp/bootpd) related:

http://docs.hp.com/en/5991-6548/ch03s05.html

[Dave Chamberlin]

I am somewhat confused about the ip/mac address. Is the IP the address the "temporary" address the server is expecting? How do I determine the mac address? What should bf be pointing to? Is it somewhere in the created depot on the ignite server?
BTW - The client is on the same subnet as the ignite server.
Thanks

[Dave Chamberlin]

I have my mac address and have edited instl_boottab - but the program instl_bootd does not start. Looking at syslog file shows: instl_bootd[17275]: "getsockname: Socket operation on non-socket"
What could be causing this?

Thanks

[likid0]

Hy,

The mac address you can get it with:

on the os:

#lanscan

on the efi:

#lanaddress

I prefer to use bootpd,coment your actual bootps in inetd.conf, and add to your /etc/inetd.conf ignite server this line:

bootps dgram udp wait root /usr/lbin/bootpd bootpd

and then #inetd -c


then you wan't to add to your /etc/bootptab
I line similar to this:


PUB:\
ht=ethernet:\
hn:\
bf=/opt/ignite/boot/nbp.efi:\
bs=48:\
sm=255.255.255.0:\
gw=10.7.7.1:\
ba

clientname:tc=PUB:ip=client-tmp-ip:ha=client-mac
SERVER1:tc=PUB:ip=10.7.7.146:ha=001A4B0AB13D



then from your client, query the bootp server:

bootpquery client_link_address -s servername


and see if you get response.


you can get bootpd more verbose with, this in inetd.conf:

bootps dgram udp wait root /usr/lbin/bootpd bootpd -d 3

[Patrice Le Guyader]

Hello,

For avoiding to spend time between looking for network issues or ignite ones, I've installed on the Ignite server "tcpdump".

With this you'll be able to see if your bootp request are arriving to the ignite server or if you have a network issue.(bad vlan,cable troubles,wrong port used,etc....)

http://gatekeep.cs.utah.edu/hppd/cgi-bin/search?package=on&description=on&term=tcpdump&Search=Search

Once you've installed it try this on your ignite server :

tcpdump -i lanX -vv -n ether host xx:xx:xx:x:xx:xx

with lanX the interface used by your client to contact the server.
and xx:xx:xx:x:xx:xx the MAC adress of the lan card used by your client to contact the server.

I've been able to solve many ignite issue with this little tool.

hope this helps.
kenavo
Pat

[Dave Chamberlin]

Thanks for the ideas. I did download tcpdump (though the hpux software archive for the US - the one in your link - doesnt work past the splash page). This program showed no activity. I tried configuring/restarting bootpd as per suggestion. I don't see bootp running on the system and there is still no difference on the client. I am giving up for now on ignite and may pursue it in the future. thanks