Root Mirroring in Vpar's

[suvy12]

Hi All,

We have a Npar having 2 Vpar's. All of the 2 Vpar's having 11iv3 so if we have to make root mirroring the disk then what will be the entry in the auto file residing in the EFI partition.
I am asking this because when i entered the string "boot vmunix -lq" in the auto file(which i normally entered in Rx servers) then after rebooting the whole Npar it stucks as vpmon is not available to boot.in this case every time i have to give the path of /stand/vpmon only after that it comes to >mon prompt from where i can load the vpar's.

If i entred "boot /stand/vpmon" in auto file and then reset the Npar then it rebooted fine and comes to the >mon prompt.

Please suggest me what should i have to enter in the auto file.

[Torsten.]

The AUTO file should contain

"boot vpmon -a"



This boots vpmon and starts all vPars.





Everything is different if you have a Superdome 2!

[suvy12]

Thanks Torsten for quick reply.
If i have a single Npar then what would be the entry in the auto file vpmon or vmunix -lq

[suvy12]

And what do you mean by that superdome 2
We have SD64B superdome is the string whihc you mention is for SD64B

[melvyn burnard · Accepted solution]

SuperDome2 is the new Superdome based on Blade-Cell technology. It was released last year, and is differnet from your SuperDome.
As for the Auto file,the nPar primary boot disk should have "boot vpmon -a"
This tells the server to boot to the VPMON, and then boot ALL vPars that have their autoboot set to yes (as seen in a vparstatus output.)
The Alternate Path for the nPar should be a DIFFERENT vPar's boot disk, and that shoul dhave the same AUTO file entry.
Any mirrors you create should also have the same boot string.
The definition of booting thre vPar to /stand/vmunix, with or without -lq, is held in the vPar database (/stand/vpdb)

[Torsten.]

A normal nPar (without vPars) should always boot "vmunix", a vPar always "vpmon".

In a Superdome 2 the instance is always starting "vmunix", regardless if it is a nPar or vPar.

[Torsten.]

BTW, the quroum mode is configured in the vpdb for each vPar.

Set it by running

# vparmodify -p winona2 -o "-lq"

[suvy12]

@melvyn

I i run
mkboot -a "hpux /stand/vpmon" /dev/rdsk/c0t8d0
where c0t8d0 is the primary boot disk for the npar while creating the vpar then what should be the entry in the auto file "boot vpmon -a" or "boot vmunix -lq"

[melvyn burnard]

>mkboot -a "hpux /stand/vpmon" /dev/rdsk/c0t8d0
Well that is incorrect if it is an Integrity server, but in your case for vPars it should read:
"boot vpmon -a"

[Torsten.]

You should set the AUTO file to "vpmon" on each disk, because you can boot up the system from each disk.



If the system runs 11.31, you can use mkboot to set the AUTO file:

# mkboot -a "boot vpmon -a" /dev/rdisk/disk2

[Torsten.]

... even on Integrity servers.

[INH]

Install autoexecute file on new disk
$ mkboot -a "hpux /stand/vpmon " /dev/rdsk/cxtxdx


npartition boots with "vmunix" & a vPar boots with "vpmon".

Rest all the steps for root disk mirrroring remains the same

Rgds,
INH

[suvy12]

Thnx all for support