Ignite-UX make_net_recovery

[Charles Holland]

Working with HPUX 11i trying to set up an Ignite server that I can back my vPARs up to incase of disaster. Client is systemA ignite server is systemB. Attached is the recover.log and an image of the screen from Ignite that give the impression that things are not totally perfect. Any suggestions as to how I can get the yellow to turn green? (without increasing the amount of blue on my screen.)

Another question: This is a "push" process from the client to the server on a gigabit "backplane" (not the public network ip address). Does anyone know if I should have any problems restoring this if I have to? My server is a rp5450 and the client I'm working with is a rp7410 with two core cards and each core card has 2 vPARa on it. Each vPAR has its own public (100MB) and private (1000 MB)card.

[Steven E. Protter]

Second part:

You can push through a gigabit network card. The only restriction I know is you can't boot off any other card than the built in lan card.

Some warnings are not necessarily a problem. When doing a lot of image pushing and pulling I ended up with one warning on /etc/passwd. Sometimes that the best you can do.

I see nothing in the log that is earth shattering.

Testing the recovery may be the next stage.

SEP

[Charles Holland]

SEP,
Previously (9 months ago) when I tried to set up a server I had heard this simular comment. In my situation a rp7410 has one built in core card per core i/o. If I take that core i/o and then put vPar on it, only one vpar will have access to the built in lan card. Therefore if I need to rebuild the other OS I'm SOL. I figured that I could sit on the Ignite server and "push" to the vpar that does not have the access to the built in lan card. Though the 1000MB lan card. Are there any limitations that I might have to use the 100MB card?

Comments.

[Bill Rothanburg]

There are two parts to booting a vPar for Ignite install/recovery.

You will need to run a script from the vPars cdrom to update the WINSTALL image on your ignite server. This will allow the Ignite server to 'boot' a Virtual Partition.

Once that is done, you should be able to use the vparboot/vparload commands to boot the vpar from the Ignite server.