Booting a vpar

[Joan Blais]

Hi Gurus,
I've loaded HPUX 11.i, latest patches and Vpar software and firmware. I captured an ignite image of the system on tape, then created the vpars. Vpar1 came up fine. How can I boot vpar2 off the ignite tape to load the OS? The vpar does see the tape drive, but fails to load(0/0/8/0/0/1/0.5.0.0.0;)/stand/vmunix The command issued is vparboot -p vpar2 -B 0/0/8/0/0/1/0.5.0.0.0. I've also tried the -I option with no luck.

[Pete Randall]

Joan,

VPARs and Ignite tapes do not play well together. That is why the VPAR install docs suggest setting up an Ignite server rather than using tape.

In my opinion, this is one of the big drawbacks of VPARS. You can't use make_tape_recovery for DR purposes.


Pete

[Joan Blais]

This is a HUGE drawback. I'm in the process of igniting to an ignite server.
Thank you.
Joan

[Jeff Schussele]

Hi Joan,

I agree that this is a major pain.
So if you intend to use vPars then you need to set up an Ignite server for make_net_recovery anyway to back them up.
Might as well just go ahead & set it up to provide a "standard" image for loading new vPars.
It's really the only way to do it.

Rgds,
Jeff

[Joan Blais]

The ignite ran successfully. Vpar2 booted up to the ignite installation. I customized file system and network info. The execution failed ERROR: There is no software fitting the Core-OS requirements.
On the "Basic" tab the "Configurations:" bar shows (HP-UX B.11.11 Default), the "Environments:" bar is empty. When I enter here it notes "The currently selected configuration does not contain any environments. You may want to select another configuration. Any suggestions?

[Jeff Schussele · Accepted solution]

Hi Joan,

Well the way we do it is a 2-part load.
First part is Ignite-UX which gets a kernel loaded then you point it to a depot which contains the image(s) - in our case it's the same server (But it doesn't need to be) and the path is like:

/depot/os/hp-ux/11.11/2004Dec/OS_image

It's created by just using swcopy to move the contents off a CD & onto our depot server.

It sounds like you don't have any images loaded on the Ignite server. If you had one or more they show up in the Environments field.

You could also run a make_net_recovery on vpar1 to the Ignite server & link the new hostname to the vpar1 image in the /recovery/clients directory. Then let Ignite load that recovery image.
You also may need to update the
/opt/ignite/boot/WINSTALL with the vPars WINSTALL file - it's different from the "standard" Ignite WINSTALL

Rgds,
Jeff

[Joan Blais]

I'm all set now. I'm in too much of a rush. My ignite server was not totally set up. I needed to designate a depot. The installation is running now without issues.
Thanks for the help.
-Joan

[Joan Blais]

The fix = Ignite server with a functional depot instead of igniting from tape. Cloning from tape would be a beautiful solution when they get it to work!