Ignite install with multi-homed hosts

[Tim Nelson]

I am wondering if anyone has run into this before.

HPUX 11i, ignite 6.9.150

I am working on building a new server using an ignite image from an ignite server. Both servers are multi-homed.

When lan booting the new server using 172.20.10.x and selecting the proper LAN interface in the new server, ignite starts out fine, configuration changes are made, the mini-system is loaded but when the attempt is made to NFS mount the archive ignite switches over to 172.20.11.x for the mount ( this is the other NIC ). Consequetially the NFS mounts fail as well as the install.

I did finally configure the new host to lan boot over the 172.20.11.x and configured the new host to use that interface instead.

I was looking for some way to control which LAN is used when booting and installing from an ignite server.

Any ideas ?

[Geoff Wild]

From what I know (okay - might not be much - walked into that one) best way to do this is to configure lan0 to be on the same subnet for all servers.

That's what we did - so instead of using the "primary" host name - eg svr0800 we use svr0800-ig

Basically, we created an ignite lan.

Rgds...Geoff

[Tim Nelson]

Thanks for the idea Geoff.

In this case on this server ( vPar ). The 172.20.10.x net was on lan0. The ignite server switched over to lan1 when trying to mount the archive.

Another interesting note was that the initial nfs mount of the /var/opt/ignite/clients directory succeeded using lan0.

[Tim Nelson]

I found the solution. In the book again :)

http://docs.hp.com/en/B2355-90997/ch05s05.html

instl_adm can be used to modify the defaults for the Ignite server boot image.

extract the defaults to a file.
edit and add
( lan[].driver == "btlan" ){ _hp_lanadmin_args="-X 100FD"}

then import the config file

[Tim Nelson]

One more note.

The info provided was to solve a 100HD issue on a 100FD connection ( ignite recovery took six hours because of lan config.

The additional defaults when using instl_adm -d to view includes the default IP addresses, netmask, etc..

This solves the multihomed issue by defining what default IP/LAN to use.