Newbie question regarding networked archives

[Terry Kummell]

I read about using make_net_recovery to create an archive of recovery images. What I did not 'get', even after readying the man pages, was the procedure to actually recover a failed system.

What would be the operational steps to recover from a catastrophic root volume failure? In the man pages, they talk about a network boot or bootsys command. It that command entered from the recovery_archive server or from the failed system?

Thanks

Terry Kummell
CCI-Triad

[John Bolene]

After the failed disk is replaced, you interrupt the boot sequence and do
bo lan.xxx.xxx.xxx.xxx install

the above x's are the IP of the network machine

check the ignite manual at
http://www.docs.hp.com/hpux/onlinedocs/B2355-90704/B2355-90704.html

[Bill Hassell]

Note in the Ignite/UX man pages the reference to a helper machine. The boot over LAN feature does not work between subnets. You'll need a helper machine to provide a memory-based kernel which can then reach any machine on the network.

[Michael Roberts_3]

When the Ignite server is on a different subnet than the
machine to be recovered, you can use a boot helper
as Bill H. mentioned. Also if the machine to be recovered
has a tape drive (or an external one can be attached)
you can use the make_boot_tape command on the
Ignite server to create a bootstrap tape. You would take
this tape to the machine to be recovered, boot from the
tape (boot sescsi.3.0 for example), and the machine will load the kernel from the tape and then contact the Ignite server to complete the recovery over the network.

[John Paine]

The boot lan install does not work with all flavours of HP machines....I did an N class last week and had to use the bootsys command.
On your ignite server type bootsys -vw .The client will reboot and get to the stage where you can do a "new client install" on your ignite server.

[Michael Roberts_3 · Accepted solution]

Regarding HP machines that do network boot (boot lan install).

All new HP hardware does network boot with the exception of V-class. There is a requirement that the core lan card be live and on the same network as the bootp/instl_bootd server. Meaning that if you have 10 active lan cards in the machine but the core lan card is not connected then you can't network boot.

Current machines that network boot:
N-class
L-class
A-class
SuperDome
C-class
B-class
J-class

An some legacy platforms network boot also:
K-class
D-class
all S700's (though some use RMP and not bootp)

Legacy platforms that don't network boot:
E,F,G,H,I,T-class

Don't know about s300 or s400's.