Ignite Server DHCP Issues

[Rafael Casero]

I setup Ignite server on 11.23 Itanium server.

I was able to make a make_net_recovery successfully.

The problem I'm having, is that I have another DHCP server on the network and when I try to boot from the LAN it responce first.

I was reading that I can modify DHCP class-id in the IINSTALLFS file located /opt/ignite/boot/Rel_B.11.23/IINSTALLFS, I cannot open this file with vi.

Any suggestions on how to edit or any other options I can take for this ?

Thanks, All in advance.

[Steven E. Protter · Accepted solution]

Shalom Rafael,

Ignite has an application for doing this.

Its in /opt/ignite and its name may be ignite if I'm not mistaken.

Use that tool to reconfigure the DHCP database and make sure if you use your public corporate network you get ip addresses allocated to you by your network department.

I used to like to have a private network for Ignite boots, made life much simpler and I didn't have to beg for IP addresses and build boot helpers to deal with VLAN issues.

SEP

[Rafael Casero]

I'm running the latest version of Ignite on OS 11.23 on Itanium.


I was able to boot to the ignite server, I get no menu or the option to choose the image i would like.

When it boots up, under image=UNKNOWN.


HELP>>>>

[John Waller]

Unfortunatly I can't remember how I initially setup the ignite server, but I have a seperate DHCP server to the ignite server and don't have any problems. One thing I found was a file on my ignite server called instl_boottab within the /etc/opt/ignite directory. This file talks about reserving IP addresses for clients for PA-RISC machines and also mentions that the /etc/bootptab should be used for IPF clients.
I also have the following line in my inetd.conf file:
instl_boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd

[Bob Ingersoll]

Hi Rafael,

instl_adm is the command used to modify INSTALLFS, the install kernel for PA_RISC clients. If you want to modify the install kernel for Itanium clients you will update IINSTALLFS using instl_adm.

Check the instl_adm man page.

The way you configure your IUX server depends on whether your clients are PA_RISC, Itanium or both.

instl_bootd defaults to using ports 1067/1068 rather than the standard bootp ports 67/68. This is for use with the boot INSTALL option available on PA-RISC. This wont work with Itanium clients; they always use the standard bootp ports 67/68. So you need to modify the default instl_bootp ports (see the man page) or use the standard HP-UX bootp daemon.