LAN boot from Ignite server for a make_net_recovery restore

[Chris Compton]

We use several K260 running HPUX 11.0 64-bit as SAP app servers. In the event the Central Instance goes down, I want to use a make_net_recovery archive to restore it to a different machine. Each box has 2 GSC 100BT NICs with different IP addresses. The built-in internal NIC is not used or connected to the network.

There is no problem creating the recovery archives.

I am aware of the need to change the directory name in /var/opt/ignite/clients from the MAC of the source box to the MAC of the target box.

I interrupt the boot of the target machine and attempt:
BOOT LAN.111.222.333.444 INSTALL.

I cannot get it to find the Ignite server (btw it IS on the same subnet).

Is my problem that I am not using the internal NIC?

Any pointers would be appreciated.
Thanks.

[Steven E. Protter]

You have to use the internal built in NIC to boot.

After that you can run the Ignite Transfer through the fast card.

instl_adm -d (not sure on the command name, its late)

Displays the parameters of the transfer after boot on the ignite server.

you can change it as follows:

instl_adm -d > file

change the file

instl_adm -f file

I am sure on that command now.

SEP

[Steven E. Protter]

You can monitor the connection for other issues as follows:

tail -f /var/adm/syslog/syslog.log

and/or

ps -ef | grep boot

You should see things happen interactively as they happen and will quickly know if you have everything straigthtened out.

I also recommend staying ucrrent on Ignite.

SEP

[Larry Basford]

I've experienced the same problem. The K series dosn't know about the GSC until it loads the driver.

I'm having the same luck though with an N400
I can boot from tape and go to the ignite server OK but not searching the lan.

[Chris Compton]

Thanks for the feedback. I have found that if the target box is up and running, I can initiate an install of the source systems from the Ignite server without too much trouble.