Populating AUTO in LIF header of mirrored boot device in VPar

[Ralph Grothe]

Hi,

I cold installed this VPar from a Golden Image from an Ignite server on another VPar (i.e. cloning).
Since I haven't yet written a post install script for the Ignite server that would automatically build LVM RAID1 of vg00 with alt boot disk, I semi-manually followed the usual procedure (pvcreate -B, vgextend, mkboot, lvextend).
Because this one is running as a VPar I am not quite sure how to set the AUTO string correctly for a VPar.

From the boot devs I see that they differ and most likely need to be fixed.
Also somehow the alt boot dev already had a special AUTO where a vpmon kernel seems first to get loaded (I guess this is the virtualizer)

# vgdisplay -v vg00|awk '/PV Name/{print$NF}'|xargs -n1 -IPV lifcp PV:AUTO -
hpux
hpux /stand/vpmon -a

Assuming that the intermediate loading of /stand/vpmon is correct I still would like to intertwine the quorum deactivation switch.
On a non-vpared box I would simply issue this

# mkboot -a "hpux -lq /stand/vpmon -a" /dev/rdsk/c0t6d0

# vgdisplay -v vg00|awk '/PV Name/{print$NF}'|xargs -n1 -IPV lifcp PV:AUTO -
hpux -lq /stand/vpmon -a
hpux /stand/vpmon -a


But with those prevelant VPars I'm in doubt if one can do it that simple, or some tinkering with vpmon or vpmodify commands is necessary.

Thx
Ralph

[Luk Vandenbussche]

Hi Ralph,

Check this

Swlist â l fileset | grep â i mir

pvcreate â B /dev/rdsk/c7t6d0

vgextend /dev/vg00 /dev/dsk/c7t6d0

mkboot â l /dev/rdsk/c7t6d0
mkboot â a â hpux (;0)/stand/vpmon â aâ /dev/rdsk/c7t6d0

pvdisplay â v /dev/dsk/c7t6d0

lvextend â m 1 /dev/vg00/lvol1 /dev/dsk/c7t6d0
lvextend â m 1 /dev/vg00/lvol2 /dev/dsk/c7t6d0
lvextend â m 1 /dev/vg00/lvol3 /dev/dsk/c7t6d0
lvextend â m 1 /dev/vg00/lvol4 /dev/dsk/c7t6d0
lvextend â m 1 /dev/vg00/lvol5 /dev/dsk/c7t6d0
lvextend â m 1 /dev/vg00/lvol6 /dev/dsk/c7t6d0
lvextend â m 1 /dev/vg00/lvol7 /dev/dsk/c7t6d0
lvextend â m 1 /dev/vg00/lvol8 /dev/dsk/c7t6d0

lvlnboot â r /dev/vg00/lvol3 /dev/vg00
lvlnboot â b /dev/vg00/lvol1 /dev/vg00
lvlnboot â s /dev/vg00/lvol2 /dev/vg00
lvlnboot â d /dev/vg00/lvol2 /dev/vg00

lvlnboot â R

mkboot â b /usr/sbin/diag/lif/updatediaglif2 â p ISL â p AUTO â p HPUX â p PAD â p LABEL /dev/rdsk/c7t6d0

There are 3 possibilities to set the bootpath:
1) setboot
set primary bootpath : setboot â p 1/0/0/3/0.6.0
set alternate bootpath : setboot â a 1/0/1/0/0/1/1.6.0

2) vparcreate
When we create the vpar.
vparcreate â p varx ..... â a io:1.0.0.3.0.6.0/BOOT â a io:1.0.1.0.0.1.1.6.0:ALTBOOT


3) vparmodify
When the partition exist yet vparmodify:
vparmodify â p vparx .... â a io:1.0.0.3.0.6.0:BOOT â a io:1.0.1.0.0.1.1.6.0:ALTBOOT


How to boot ?

from a shell :
vparboot â p vparx â B pri
vparboot â p vparx â B alt

from virtual partition monitor (MON):
Vparload â p vparx (for primary path)
Vparload â p vparx â B 1.0.1.0.0.1.1.6.0 (for alternate path)

[Ralph Grothe]

Hi Luk,

looks like your "-" char maps oddly
(or maybe me browser has some inferior rendering char set?).
I can only see garbled signs where a minus sign ought to appear.
Anyway, all of what you outlined was already set up by me.
The only thing that left me puzzled was the significance (and correctness) of the LIF AUTO string on the boot disks.

[Sameer_Nirmal]

Hi,

I really doubt if Vpar uses LIFs. I am not sure how the AUTO LIF was created. Depending on the versions of Vapr and IG-UX , I would cross check the support for LIFs is added or not. Assuming the support is added , I feel there should one entry for vpmon with required attributes as we do for non-Vpar disks

AS per my understanding, the way kernel boots up under vpar is little different than the usual way without vpar.

In case of vpar , first of all ,"hpux" is primarily used for loading the "vpmon" only.Then with the a specific vpar , various boot option could be passed on through vparload.
So we have :
hpux /stand/vpmon vparload -p vpar1 -b -o "lq" -B

In case of problem with one vpar , you can use vparmodify command from another vpar to change above options.
If you don't have other vpar , then you have to do it manually at the ISL prompt.