vPar to boot from external EVA disk.

[Anubhav Dhingra]

Hi
Please help on the following query.

configuration : rx8640 2 nPars both with HP-Ux 11.31 virtual Server Environment. Each nPar has 6 Fc Ports and 7
ethernet ports and 2 * 146 GB ScSI Disks Each nPar has one cell with 4 * 1.6 Ghz Dual core Montavale processors and
32 GB RAM.

We also have a EvA 8100 2C6D with some 56 Fc 300 GB Disks.

I want to configure 2-3 vPars on each nPar

nPar is booting from /dev/rdsk/c6tod0 or /dev/disk/disk3 which is not mirrored.

Now,

i have created a test vPar with 2 cpus and 6 GB RAm with 2 Fc/Lan ports which is using the same /dev/disk/disk3 to boot.

However, what i want to do is to boot the vPar from different disk from EvA. I have tested the zoning
and i can see the LUNS from EvA.

what i understand is /dev/disk/disk3 should be used for bringing the vpmon and then vpar should boot with the disk from EvA
.

For this i think of two options.
A.

1. Present disk from EvA to nPar and then mirror it with the Internal disk.
2. Use this External Disk as boot option while creating the vpar.

B.

1. Present disk from Eva to nPar and use this while creating the vPar.
2. vPar will not boot and will stuck on vPMoN> install the OS from one of the Golden Image residing on the Ignite server.


I am sure if i can achieve this. Please assist.

[Torsten.]

Option A is a bit dangerous for several reasons, better to copy the install media (DVD) to the ignite server and install via ignite from there. You can also create a golden imgae from the first to install the second vPar.

[Zinky]

This is EZ as pie.

While your nPar is booted as an nPar, present EVA LUNS sized ~same or a bit bigger than your internal disks your nPar is booted on - that will serve as vpar2, vpar3 boot disks.

Ascertain the primary HW Paths to these disks. (use ioscan, evainfo and use the 1st entry)

vpar2=h/w/p/a.t.h.2
vpar3=h/w/p/a.t.h.3

Carve your vPars (vParcreate -- allocating each vPar's IO paths, cpu, memory, NICs, etc)

DD copy your nPar's (or whatwill become your primary or monarch or 1st vPar's) bootdisk to vPar2 and vPar3's boot disks:

dd if=/dev/rdisk/disk3 of=/dev/rdisk/diskNN bs=1024k

Shutdown nPar.
Boot vPMON
Start vPar1 (MON> vparboot vpar1)

From vPar1 -- resettle each vPar's Boot Disk by booting in LVM Maintenance Mode amd fixing VG00 as follows:

root@vpar1 # vparboot -p vpar2 -B h/w/p/a.t.h.2 -o "-lm"

CTRL-A over to vPar2's Console
vgexport vg00
create vg00
vgcreate vg00 using map file from vpar1 and correct /dev/dsk/cXtYdZ
vgchange
lvlnboot gyrations
etc...
(the above gyrations is basically "fixing vg00")

fix network ,etc

reboot

Do the same for vPar3

[Anubhav Dhingra]

Hi,

This is the configuration for the nPar.

ioscan -funC disk ---------> legacy address mode

Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 1/0/0/2/0.6.0 sdisk CLAIMED DEVICE HP 146 GHUS153014VL3800
/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0
/dev/dsk/c0t6d0s1 /dev/rdsk/c0t6d0s1
/dev/dsk/c0t6d0s2 /dev/rdsk/c0t6d0s2
/dev/dsk/c0t6d0s3 /dev/rdsk/c0t6d0s3
disk 1 1/0/0/2/1.2.0 sdisk CLAIMED DEVICE Optiarc DVD RW AD-5200A
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
disk 2 1/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 146 GHUS153014VL3800
/dev/dsk/c2t6d0 /dev/rdsk/c2t6d0
disk 6 1/0/4/1/0/4/0.1.0.0.0.0.1 sdisk CLAIMED DEVICE HP HSV210
/dev/dsk/c9t0d1 /dev/rdsk/c9t0d1
disk 7 1/0/4/1/0/4/0.1.4.0.0.0.1 sdisk CLAIMED DEVICE HP HSV210
/dev/dsk/c11t0d1 /dev/rdsk/c11t0d1

ioscan -fuNC disk ----------> persistent address mode

Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 3 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP 146 GHUS153014VL3800
/dev/disk/disk3 /dev/rdisk/disk3
/dev/disk/disk3_p1 /dev/rdisk/disk3_p1
/dev/disk/disk3_p2 /dev/rdisk/disk3_p2
/dev/disk/disk3_p3 /dev/rdisk/disk3_p3
disk 4 64000/0xfa00/0x1 esdisk CLAIMED DEVICE Optiarc DVD RW AD-5200A
/dev/disk/disk4 /dev/rdisk/disk4
disk 5 64000/0xfa00/0x2 esdisk CLAIMED DEVICE HP 146 GHUS153014VL3800
/dev/disk/disk5 /dev/rdisk/disk5
disk 8 64000/0xfa00/0x7 esdisk CLAIMED DEVICE HP HSV210
/dev/disk/disk8 /dev/rdisk/disk8

ioscan -funC lan
Class I H/W Path Driver S/W State H/W Type Description
=========================================================================
lan 0 1/0/0/1/0 igelan CLAIMED INTERFACE HP PCI-X 1000Base-T Built-in
lan 1 1/0/4/1/0/6/0 iether CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X 1000Base-T 2-port 4Gb FC/2-port 1000B-T Combo Adapter
lan 2 1/0/4/1/0/6/1 iether CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X 1000Base-T 2-port 4Gb FC/2-port 1000B-T Combo Adapter
lan 3 1/0/6/1/0/6/0 iether CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X 1000Base-T 2-port 4Gb FC/2-port 1000B-T Combo Adapter
lan 4 1/0/6/1/0/6/1 iether CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X 1000Base-T 2-port 4Gb FC/2-port 1000B-T Combo Adapter
lan 5 1/0/14/1/0/6/0 iether CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X 1000Base-T 2-port 4Gb FC/2-port 1000B-T Combo Adapter
lan 6 1/0/14/1/0/6/1 iether CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X 1000Base-T 2-port 4Gb FC/2-port 1000B-T Combo Adapter

lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
1/0/0/1/0 0x00226410E0D7 0 UP lan0 snap0 1 ETHER Yes 119
1/0/4/1/0/6/0 0x0024813328D8 1 UP lan1 snap1 2 ETHER Yes 119
1/0/4/1/0/6/1 0x0024813328D9 2 UP lan2 snap2 3 ETHER Yes 119
1/0/6/1/0/6/0 0x002481332840 3 UP lan3 snap3 4 ETHER Yes 119
1/0/6/1/0/6/1 0x002481332841 4 UP lan4 snap4 5 ETHER Yes 119
1/0/14/1/0/6/0 0x0024813328DA 5 UP lan5 snap5 6 ETHER Yes 119
1/0/14/1/0/6/1 0x0024813328DB 6 UP lan6 snap6 7 ETHER Yes 119
LinkAgg0 0x000000000000 900 DOWN lan900 snap900 9 ETHER Yes 119
LinkAgg1 0x000000000000 901 DOWN lan901 snap901 10 ETHER Yes 119
LinkAgg2 0x000000000000 902 DOWN lan902 snap902 11 ETHER Yes 119
LinkAgg3 0x000000000000 903 DOWN lan903 snap903 12 ETHER Yes 119
LinkAgg4 0x000000000000 904 DOWN lan904 snap904 13 ETHER Yes 119


ioscan -funC fc
Class I H/W Path Driver S/W State H/W Type Description
======================================================================
fc 0 1/0/4/1/0/4/0 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 1)
/dev/fcd0
fc 1 1/0/4/1/0/4/1 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
/dev/fcd1
fc 2 1/0/6/1/0/4/0 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 1)
/dev/fcd2
fc 3 1/0/6/1/0/4/1 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
/dev/fcd3
fc 4 1/0/14/1/0/4/0 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 1)
/dev/fcd4
fc 5 1/0/14/1/0/4/1 fcd CLAIMED INTERFACE HP AD194-60001 PCI/PCI-X Fibre Channel 2-port 4Gb FC/2-port 1000B-T Combo Adapter (FC Port 2)
/dev/fcd5
# olrad -q
Driver(s)
Capable
Slot Path Bus Max Spd Pwr Occu Susp OLAR OLD Max Mode
Num Spd Mode
0-0-1-1 1/0/8/1 396 133 133 Off No N/A N/A N/A PCI-X PCI-X
0-0-1-2 1/0/10/1 425 133 133 Off No N/A N/A N/A PCI-X PCI-X
0-0-1-3 1/0/12/1 454 266 266 Off No N/A N/A N/A PCI-X PCI-X
0-0-1-4 1/0/14/1 483 266 133 On Yes No Yes Yes PCI-X PCI-X
0-0-1-5 1/0/6/1 368 266 133 On Yes No Yes Yes PCI-X PCI-X
0-0-1-6 1/0/4/1 340 266 133 On Yes No Yes Yes PCI-X PCI-X
0-0-1-7 1/0/2/1 312 133 133 Off No N/A N/A N/A PCI-X PCI-X
0-0-1-8 1/0/1/1 284 133 133 Off No N/A N/A N/A PCI-X PCI-X

setboot
Primary bootpath : 1/0/0/2/0.0x6.0x0 (/dev/rdisk/disk3)
HA Alternate bootpath :
Alternate bootpath : 1/0/0/2/0.0x6.0x0 (/dev/rdisk/disk3)

Autoboot is ON (enabled)
Hyperthreading : ON
: ON (next boot)

I have presented /dev/dsk/c9t0d1 from the EVA which has only one alternate path. This LUN is presented through the fcd0
which is on 1/0/4/1 IO card.

i want to create 1st vPar that should boot from /dev/dsk/c9t0d1 or /dev/disk/disk8 or 1/0/4/1/0/4/0.1.0.0.0.0.1

So that VPMON should boot from /dev/disk/disk3 and then load vPar from this external disk

so i have created the vPar

vparcreate -p vp_svu_hq1 -a io:1.0.4 -a io:0.1.0.0.0.0.1:BOOT -a cpu::2
-a cpu:::2:4 -a mem::2048:base -a mem::4096:float -g ilm:256:y -g clm:256:y


mkboot -a "boot vpmon -a" /dev/rdisk/disk3 --> which is the internal disk

vparenv -m vPars

vparefiutil -u

vparefiutil

Hardware path - EFI path mapping
================================

Hardware path : 1.0.0.2.0.6.0
: 1.0.0.2.0.6.0
EFI path : Acpi(HWP0002,PNP0A03,100)/Pci(2|0)/Scsi(Pun6,Lun0)/HD(Part1,SigDC150302-F2FF-11DD-8000-D6217B60E588)/\EFI\HPUX\HPUX.EFI


1/0/0/2/0.6.0


From the VP MON> I want to ignite the Vpar from Golden Image stored on the Network.

Then create another vPars using other IO/CPU/Memory.

I am sorry, i need some more help as i am creating a vPar for the first time.

What i understand from your reply is that
I need to create atleast one vPar which will boot from the internal disk and then make subsequent vPar which will boot from EVA.

[Zinky]

yes from nPar Boot, create all your vPars.

vPar1 -- which includes your npar's boot disk, IO - FC Paths and NIC(s)
vpar2 -- which includes your 2nd vPars IO Path - FC and NIC...
vParN. -- ....

Then boot the nPar in vPar mode, which should boot your vPar1 using your nPar's boot disk.

And from there -- since youre using Ignite from Golden Image, invoke vparboot to initiate the ignite.

If however your vPar2 or 3 will be based on the same OS as your nPar/1st vPar -- The above method is faster

[Anubhav Dhingra]

Hi alzhy,

Thanx for your help, it was really a pie.

its not giving option to submit points for your help or else it would have been 10.