topic Mixed vPars Environments in Operating System - HP-UX

Mixed vPars Environments

System Unix — Mon, 19 Oct 2009 11:26:38 GMT

Hi,

I have installed mixed vPars v5.05 on HPUX 11.31 together with vPars 4.03 on HPUX 11.23. everything works fine.
after issuing the command mkboot -a "hpux /stand/vpmon -a" /dev/rdsk/cXtYdZ is there way the see how the vpar will be booted?
like what disk? is it vmunix/vpmon ?

thanks
Reuven

Re: Mixed vPars Environments

Torsten. — Mon, 19 Oct 2009 11:50:42 GMT

After a power on of a server the system will be boot vpmon, each vPar will then boot the vmunix kernel. You can see the boot process while toggling the console.

Re: Mixed vPars Environments

System Unix — Mon, 19 Oct 2009 13:16:32 GMT

Hi Torsten,
thanks for your reply.

my question was to find the boot params while vpars are up, like if you create a vg with disks a,b,c the command vgdisplay -v will show all the disks that the vg was created from.

can I do the same to see the boot details of each vpar ? ( a command that will show me hpux /stand/vpmon and the disk cXtYdZ )

rgards,

Reuven

Re: Mixed vPars Environments

Torsten. — Mon, 19 Oct 2009 13:44:31 GMT

You need to make a difference here!

The startup file that points to /stand/vpmon is somewhere on the LIF/EFI (depends on machine) and is only used after a cold start or nPar start, the startup for each vPAR OS is in vpdb file (check with vparstatus).

Re: Mixed vPars Environments

System Unix — Mon, 19 Oct 2009 14:08:49 GMT

Hi Torsten,
I am looking for something similar to echo 'boot_strings/S'|adb /stand/vmunix /dev/kmem that is on PA-RISC but will be similar on Ia64 in vPars environment. or any EFI other commad or lifls etc...

thans,

Reuven

Re: Mixed vPars Environments

Torsten. — Mon, 19 Oct 2009 14:18:17 GMT

Each (vpar or not) system is loading /stand/vmunix, so there is no difference!

The difference is only during a cold start.

After the firmware is loaded, the system attempts to boot from the configured boot disk and reads the configured boot string.

AT this point ONLY the /stand/vpmon is used to load the vpmon.

From that point on each vPar instance is started just like a normal stand-alone system by /stand/vmunix (but the vpdb file is emulating the LIF/EFI area and delivers the boot string).

So if you ask a vPar instance, the answer is always it is booted with /stand/vmunix.

Re: Mixed vPars Environments

Torsten. — Mon, 19 Oct 2009 14:21:16 GMT

see

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02029116/c02029116.pdf (BSC link updated by admin)

Re: Mixed vPars Environments

Torsten. — Mon, 19 Oct 2009 14:31:59 GMT

and

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02029116/c02029116.pdf (BSC link updated by admin)

Re: Mixed vPars Environments

System Unix — Tue, 20 Oct 2009 05:38:05 GMT

Hi Torsten,

thanks you for your clarification.

rgds,

Reuven