Igniting a new server

[Michelle Barton]

I've recently built a server which I want to build another server just like it with the exception of the name and ip. I know I could use the tape recovery and boot off of tape, however, this new server does not have a tape drive. I'm looking for direction on how to do this with the net_recovery, maybe using the ignite server. I'm reading docs, but thought someone here might be able to point me in the right direction, as I really need to get this server up today.

Thanks,
Michelle

[G. Vrijhoeven]

Hi Michelle,

Here is a link that helps you with setting up an ignite server.

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90772/B2355-90772_top.html&con=/hpux/onlinedocs/B2355-90772/00/00/11-con.html&toc=/hpux/onlinedocs/B2355-90772/00/00/11-toc.html&searchterms=server%7csetup%7cignite&queryid=20040419-092307

What you could do if you have a server that has a simular hardware config as your new server is.
1. Create an ignite server.
2. Start a make_netrecovery on the server that is allready installed and has simular hardware config.
3. Path the new server with lan0 in the same network. ( Not nessesary but this avoids configuring boothelpers)
4. bo net
5. access interactive install and make changes (ipconfig settings e.g.)

HTH,

Gideon

[Michelle Barton]

The new server IS on a different network, so it looks like boot helpers are necessary. Thanks!

Michelle

[Victor Fridyev]

Hi,

If you have a free disk slot in the first computer, just put into it system disk from the second server and after
ioscan -fn and
insf -e -C disk
run the following:
dd if=/dev/rdsk/System_Source of=/dev/rdsk/Target bs=32768k
The target disk should be inserted into the same slot on the second machine. This trick works if you don't intend to put both servers into the same SG cluster.

HTH

[Jasti Kalyan Babu]

If you have the OS mirrored on Server1 you can split mirror and swap the disk with Server2. With a little bit of additional work you can make Server2 ready with its own name.
Make sure you have Server2 off the network.