vPars on an nPar.

[Narayanaswami]

Hi,
If I've set up n vPars on an nPar and ,after shutting down all the n vPars,
I reboot the nPar in nPar mode (vparenv -m nPars) with the specific intention of bringing up only one machine on the nPar in the nPar mode,
will I lose the information stored in the vPar database ?
Has anyone tried this before?
Thanks in advance..

[Pat Obrien_1]

I am not familiar with your vparenv -m npars command, but yes, in fact there are situations where you need to boot stand vmunix to make npar changes, and then reboot into vpmon. Done this many times.

[Narayanaswami]

Well,this command is Integrity specific only.

To ask the question clearly,
If vpars are first setup,used for some purpose,then if vmunix is booted,the nPar is used for some purpose(like testing a build etc) and then again vpmon is booted and
the vPars are brought up, will the original vpar configurations with hardware resource allocations stay the same ?

Thanks!

[Kevin Wright · Accepted solution]

Yes, vpdb will not change by booting into the npar.

[Navin Jain]

vpdb will not change.
Just make sure during the boot process after loading hpux you enter the command:

boot vmunix

to boot in npar mode.

When you want to boot again in vPar mode, change back NVRAM to vpar mode by entering the commnad: vparenv -m vPars

Reboot the server and at the boot time after hpux load enter the command

boot vpmon -a

this will boot all vPars defined.

Navin Jain

[Zinky]

You will not loose your vPar configuration at all.

That's the beauty of vPar environments.. each vPar can actually be booted off as an nPar/regular server BUT note that an nPar boot of a vPar will mean that environment will SEE all the I/O paths BUT will only mount the filesystems as defined. In fact this is the only supported way to upgrade your vPar software - you need to boot each vPar in non-vPar mode and upgrade the vPar software.


Note that you can also boot vpmon from any of the vPar's boot disk if you want to revert to vPar mode..

Hope this helps.

Peace & Clean Earth!

[Senthil Kumar .A_1]

Hi,

The intial setup, itself answers your question. If you remember right, the first vpar is created when you were booted through /stand/vmunix. You could create as many vpars as the valid config would allow. This simply states that you can still boot through /stand/vmunix in future without any vpar config changes. This is true unless you don't run vpar related config commands to change the configuration that changes the VPAR DB....

Again, Please remember even if you change any software, install or remove while booted from /stand/vmunix directly, will only affect the system config, whereas, VPAR is just letting the same /stand/vmunix be loaded by vpmon, with less H/W assigned to it..

Regards,
Senthil Kumar .A

[Narayanaswami]

Hi All,
Many thanks for your responses.
My vPar knowledge is
restricted to what HP officially provides.
All your responses gave me a "practical"
idea.
I think vPars are fantastic as far as potential goes!!
Closing this thread.

[Narayanaswami]

closing thread..