Ignite UX using network recovery

[Trevor McKenzie_1]

Q1.
Using ServerA as an ignite server, it has two Lan cards 10/100 (primary) and Gb card just added. New servers added to network with Gb cards as primary. Problem is that the new servers are unable to be added as Ignite clients to serverA. Original version of Ignite "swremoved" from new servers to avoid differing versions.
Q2.
From the make_network_recovery image on serverA from another server, can this be copied to a tape on serverA to be used as a local boot tape on the server it came from, in the event the network is down (DR senario), if so what steps, changes are required?

[Steven E. Protter]

Q1. Remember that you can only boot an Ignite client off the internal NIC card. The GB card is fine for image transfer not booting. instl_adm -d to see it.

I have had this problem in the past and was forced do delete the configuration files for servers based on mac address in /var/opt/ignite/clients and then add them in. As I recall I had to do it at the Ignite server in gui with X. Don't know why, after deleting the client files, left over from a failed add, everything was fine.

Q2.

I would have an Ignite image of the DR server including all of the Ignite images off site. You then obtain hardware or install the ignite tape onto that hardware.

All other server as they come in are booted off the Ignite server and configured in the DR center. We're writing a project plan for just such a scenario now.

Need elaboration? let me know.

SEP