vpar's multiple root disks problem

[uk1]

Currently I am trying to create a bootable vpar using 3 different luns connected by fibre channel. With the following command:

vparcreate -p $host -a cpu::6 -a cpu:::6:6 -a mem::48000 -a io:1/0/8 -a io:1/0/10 -a io:1/0/12 -a io:0/0/14 -a io:0.0.8.1.1.173.0.2.0.3.3:BOOT

When vpmon comes up and tries to boot that vpar it pulls:

[MON] Booting
Kernel file is not relocatable
File address is 0x0000000000020000 and memory address is 0x0000000004000000
Error reading program segments
Failed to load (0/0/8/1/1.173.0.2.0.3.3;)/stand/vmunix

Can vpars boot using multiple fc boot devices in vg00? Or am I specifing the vparcreate command incorrectly, by chance?

Thanks,

-David

[uk1]

Let me include that 0/0/8/1/1/1.73.0.2.0.3.3 is the pri boot disk. However there are two other disks that are included in vg00

[Luk Vandenbussche]

David,

Did you create an extra Vpar or did you modify the bootpath of a vpar.

Did you install an os if you created an additional vpar?

[RAC_1]

What does lifls -l on boot disk say?? Should be authenticate LIF volume.

[Richard Pope]

Haven't done this myself for a few months, but should the vparcreate command include "-a io:0/0/8" as well as "-a io:0.0.8.1.1.173.0.2.0.3.3:BOOT"

[baiju_3]

You need to have an OS installed under 0/0/8/1/1.173.0.2.0.3.3.


Please verify.


Thanks,
BL.

[uk1]

Yea I am not sure what I was copying there but 0.0.8 was included in the vparcreate command. Also the disk is bootable from bch just not vpmon. I have a call to hp right now asking if vpars is supported over cisco switches connected to an xp1024.

[Luk Vandenbussche · Accepted solution]

Your vparcreate command is ok this is a valid i used

vparcreate -p vpar1 -a cpu::2 -a cpu:::2:2 -a cpu:0.10 -a cpu:0.11 -a mem::4096 -a io:1.0.0 -a io:1.0.1 -a io:0.0.8 -a io:0.0.10 -a io:0.0.2 -a io:1.0.0.3.0.6.0:boot

Then you have to execute the following to load the os

1) Create a depot
make_depots â r B.11.11 â s /dev/cdrom


2) Add vpar soft to depot (with vpar cdrom)
make_depots â r B.11.11 â a 800 â s /dev/cdrom

3) make igniteux file
make_config â r B.11.11

4) update ignite index for applications
manage_index â a â f /var/opt/ignite/data/Rel_B.11.11/apps_800_cfg

5) start ignite
/opt/ignite/bin/ignite

6) modify config as following

Options -> Server Configuration -> Server Options tab:
Default configuration: HP-UX B.11.11 Default
Client Timeouts: 40
Run clients installation UI on: server
Options -> Server Configurations -> Session Options tab:
Select options:
Confirm new clients
Show the welcome screen for the install server
unselect :
Halt the client after installation

7) boot the vpar from ignite server :
vparboot -p vparx -I IP ignite server,/opt/ignite/boot/WINSTALL

[Torsten.]

Hi David,

this looks to me like you're trying to boot an OS without having the vPars software installed on this OS instance. You need to have vPars software installed on *all* vPar instances.

[Richard Pope]

Can you confirm that the appropriate version of the vPar software is loaded on the vPar that you are trying to boot?

[Richard Pope]

D'oh, Torsten beat me to it!

[uk1]

The internal disk was shipped with vpar software we did not receive any third party software. Reading this I could kick myself! You guys are 100% right, I need to somehow get the software on the new boot paths.

[Torsten.]

Normally the software cd should be included, I guess.

If you have the necessary licences (to be legal) you may clone your first partition using ignite.
1. option:

backup the running vPar to a ignite server and restore the backup to the new vPar

2. option:
backup the OS without running vPar (/stand/vmunix booted instead of /stand/vpmon) to a tape and restore the backup to the new disk. After this start the first vPar, configure and start the second.

Remember, every vPar have to use its own FC HBA.