Boot from LAN using ignite

[Coolmar]

Hi,

We have many servers and all on different subnets. When we get a new server in, or in the event of disaster recovery we boot the server from the lan and ignite it. The problem is that the servers are all on different subnets (110, 107, 108, etc). The ignite server is on the 110 network and when we want to ignite a server we have to pull this long cable - attached to the 110 network - and plug it into the back of the system. Obviously, this is not ideal. Is there a way to get ignite to listen on more than one network, so that if a system on the 107 network needs to be ignited, we can just boot from the lan and that system and it will ignite without having to move the system to the 110 network?

[Torsten.]

The answer is here:

http://docs.hp.com/en/IUX/faq.html#d0e2659

(Can I have the Ignite-UX server and client on different subnets?)

You should use a "boot helper" or an installation CD.

[Marvin Strong]

I have a similar problem in the environment I am currently working in.

Just boot from cd or dvd, and then choose ignite server installation its the easiest.

Once you get an HP on every subnet you can make them boothelpers for new newservers.

[Coolmar]

The problem is that alot don't have a cd/dvd drive in them. So I really need ignite to work.

[Torsten.]

The problem is, you need to load the installation utility on the client somehow before restoring the backup. This can be done by booting an installation CD and select the ignite server or using a boot helper. You can even use a tape for this, if you have or another HDD with an install kernel on it.

[Marvin Strong]

If you don't have a cd/dvd in alot of them then you will need to turn one of your other HP server on the same subnet as the server you want to build into a boothelper. Its a relatively easy process documented in the ignite admin guide.



http://docs.hp.com/en/B2355-90970/B2355-90970.pdf

[Marvin Strong]

Alternately if you can put these machines on the network. New HP's seem to normally come with some base OS build. You can just answer the questions on first boot, put the machine on your network, then bootsys from the ignite server.

If you don't have any OS then we are back to boothelpers.

For DR I would suggest you do make_tape_recovery for every system this makes the OS install at a DR site very easy.

[Coolmar]

Sorry, something that I didn't mention because I am still in the process of figuring this all out....is that the ignite server has 7 NICs - one on each subnet - but seems to only listen on the one (110)subnet. Is there a way to get the ignite server to listen on all the other subnets as well?

[Marvin Strong]

I personally have never had ignite server setup like that.

You could try to add the IP for the client you are going to install into /etc/opt/ignite/instl_boottab

then try to do boot lan.x.x.x.x (using the subnet the client on)

I doubt that will work. Might be worth a try if you haven't tried it.

[Coolmar]

I have decided to open another thread and try and explain the situation better.
Thanks for the help.