Ignite push installation

[Michael O'brien_1]

Hi,

Is it possible to recover a system using an network ignite archive without interacting with the client, ie. not using the BCH or bootsys to initiate the recovery process. Is possible just to drive the recovery from the ignite server GUI?

Thanks
Mike

[RAC_1]

Yes. Start ignite on ignite server and slecet the client and reboot, then thereon it is self explainatory.

[Michael O'brien_1]

Hi,

Just had a check on the ignite gui, I selected the client and looked in the actions menu and also right clicked client to see what options were available but I couldn't see any reboot option. We are using ignite 5.1.32 could you advise were the reboot option lives.

Thanks
Mike

[Mark Nieuwboer]

it's not reboot its boot client.
if you use this option your client is rebooting and over this you can install the ignite image.

grtz. mark

[Michael O'brien_1]

Hi,

The boot client calls the bootsys command which require the os to be running. I was interested if you could recovery a client, which isn't hasn;t got a working OS and unable to get to the console to use the BCH.

Thanks
Mike

[Scot Bean]

If your target machine is down (not on the network), the Ignite GUI will not be able to talk to it / control it.

You have to get to the target's console and get some networking going between the down machine and the Ignite server for the GUI stuff to work at all.

(Now it should be possible to automate the target console stuff via "expect" scripts or similar.)

[Michael O'brien_1]

Hi,

What I was interested in is if the machine had crashed, it's MAC address was still visable on the network. But the full tcp/ip stack isn't loaded, ie the OS isn't up and running.

I'd like to be able to drop the make_net_recovery archive on the crashed server.

Thanks
Mike

[Armin Kunaschik]

It's not possible without ANY interaction.
You could set the primary bootlist to the network,
resulting in an installation any time you boot your server... bad choice.
Putting the installation on the alternate boot path would not work because it's not likely that a crashed system always doesn't reach ISL.

So the one thing you have to do on the console is to select the network as the boot device,
e.g. bo lan install

I think the rest would work without interaction if you edit the configuration the "right" way.

On a current rp-series machine there is always a networkable GSP so it's no problem to interact with the boot process...

My 2 cents,
Armin

[Michael O'brien_1]

Thanks Armin,

I thought that was the answer but I just wanted to check if I was missing somthing and there was an option to recover the machine without interacting with the client.