Copying a boot disk of an up and running vPar to another vpar in HPUX Itanium [11i v3]

[willsfrazer]

Hi,

This might sound strange but is there something like this :

Copying a boot disk of an up and running vPar to another vpar in HPUX Itanium [11i v3].

Whole idea is to see if we can add a raw disk to a vpar, let's say vPar1, which has an OS image and it's configured properly with all n/w, system and file system configuration. Now copy the image in such a format to this newly added raw disk that when we remove this disk from the vPar1 and add as BOOT disk to another vpar, assume vPar2, and say "vparload -p vPar2" it should load[come up with] the same image and configuration which we had on the vPar1. Then we could configure it as we want by logging in to it from MP console using same credentials of vPar1 and change the n/w configuration and other configurations if we want.

Now writing to a raw disk should be handled through adding it as new logical volume on vPar1 as image should be written only in new disk so that could be used for vPar2. Though not sure if we can specify using logical volumes that write to this particular disk only .

Is anything of such sort possible. I do not want ignite capturing as deploying image from ignite will require me to do n/w, system and file configuration at booting time, which I do not want. What I want is let me bring up the server with some default configuration so that I can install Ignite base[client] package on it and then I could use this setup for deploying the image through Ignite without doing any configuration manually.

Hopefully I conveyed what I am trying to do...

[Steven E. Protter]

Shalom,

While I suppose you can use dd to copy a boot disk to a network destination, the supported way to do this is Ignite.

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1189957

I think that thread explains it best.

SEP

[willsfrazer]

is that link still alive, it's not opening...

[Dennis Handly]

>is that link still alive, it's not opening.

I have no problems with it. You might try without the "11":
http://forums.itrc.hp.com/service/forums/questionanswer.do?threadId=1189957

[Torsten.]

I never did this so far, because I only used ignite golden images or cold installations.

But I think you can "clone" the disk (think about DRD - dynamic root disk), assign the disk to another vPar, boot this vPar into single user mode and adjust hostname, IP, etc...

In case you "clone" with "dd", boot into single user mode first and use vgexport/import to adjust vg00 to the new H/W path.

[willsfrazer]

Thanks for the help. Cloning works for me withh dd as I could bring another vPar up, but when I boot the vPar with cloned disk it gets lan card of source vPar with it and hence new cloned server has two lan cards, which I do not want as I want one card still to be with source vpar. When I bring the server which hosts both source and cloned vpar to nPar mode all the hardware resources seem to be in place, so VPDB does not have problem, the cloned disk is to be configured to release first vPars lan card, Any suggestions how can I do it.

-Thanks.

[Torsten.]

Please post

# vparstatus -v

[willsfrazer]

Hi

Here is the vparstatus after I booted vPar3 with cloned disk of vpar1.

*****************************
vparstatus -v -p vpar1
[Virtual Partition Details]
Name: vpar1
State: Down
Attributes: Dynamic,Autoboot,Nosearch
Kernel Path: /stand/vmunix
Boot Opts:

[CPU Details]
Min/Max: 1/4
User assigned [Path]: 1.120
Boot processor [Path]:
Monitor assigned [Path]:

Non-cell-specific:
User assigned [Count]: 1
Monitor assigned [Count]: 0
Cell-specific [Count]: Cell ID/Count


[IO Details]
1.0.0.3.0.6.0 BOOT

[Memory Details]
ILM, user-assigned [Base /Range]:
(bytes) (MB)
ILM, monitor-assigned [Base /Range]:
(bytes) (MB)
ILM Total (MB): 8192 (Floating 0)

ILM Granularity (MB): 128

CLM, user-assigned [CellID Base /Range]:
(bytes) (MB)
CLM, monitor-assigned [CellID Base /Range]:
(bytes) (MB)
CLM (CellID MB):

CLM Granularity (MB): 128

[OL* Details]
Sequence ID: N/A

Operation: N/A

Status: N/A

**************

vparstatus -v -p vPar3
[Virtual Partition Details]
Name: vPar3
State: Up
Attributes: Dynamic,Autoboot,Nosearch
Kernel Path: /stand/vmunix
Boot Opts:

[CPU Details]
Min/Max: 1/4
User assigned [Path]:
Boot processor [Path]: 1.122
Monitor assigned [Path]:

Non-cell-specific:
User assigned [Count]: 1
Monitor assigned [Count]: 0
Cell-specific [Count]: Cell ID/Count


[IO Details]
1.0.10.1.0
1.0.6.1.0.1.208.0.0.2.2
1.0.1.1.0.1.1.6.0.0.0.0.0 BOOT

[Memory Details]
ILM, user-assigned [Base /Range]:
(bytes) (MB)
ILM, monitor-assigned [Base /Range]: 0x20000000/1408
(bytes) (MB) 0x100000000/6784
ILM Total (MB): 8192 (Floating 0)

ILM Granularity (MB): 128

CLM, user-assigned [CellID Base /Range]:
(bytes) (MB)
CLM, monitor-assigned [CellID Base /Range]:
(bytes) (MB)
CLM (CellID MB):

CLM Granularity (MB): 128

[OL* Details]
Sequence ID: N/A

Operation: N/A

Status: N/A


********************

Though vPar3 does not show two lan cards in vparstatus. lanscan shows two of them in vPar3.

# lanscan
Hardware Station Crd Hdw Net-Interface NM MAC HP-DLPI DLPI
Path Address In# State NamePPA ID Type Support Mjr#
1/0/1/1/0/4/0 0x0017084CB8CC 0 UP lan0 snap0 1 ETHER Yes 119
1/0/10/1/0 0x001321EA88C6 2 UP lan2 snap2 2 ETHER Yes 119


**********************

Here 1/0/1/1/0/4/0 is actually vpar1 's lan card but is seen in vpar3 once I boot vpar3 up with cloned disk from.

[Torsten.]

You have only this IO in vpar1:

IO Details]
1.0.0.3.0.6.0 BOOT

IMHO this includes all beneath 1.0.0, but seams to be a little less.

Please post

# vparstatus -A

now.

[Torsten.]

and please some more:

# ioscan -fn
(from vpar1)

# vparstatus -P

[willsfrazer]

Hi,

Sorry for the delay...

Here is the required information

# vparstatus -A [from vPar3]
[CPUs (path)]: 1.123
[CLP (CellID Count)]: 1 1
[Available CPUs]: 1

[Available I/O devices (path)]: 1.0.8
1.0.12
1.0.14

[Available ILM (Base /Range)]: 0x78000000/127
(bytes) (MB) 0x2a8000000/13977
0x611a00000/102
0x618000000/7680
0x7f8000000/64
0x4080000000/1920
0x40f8000000/124
[Available ILM (MB)]: 7610

[Available CLM (CellID Base /Range)]:
(bytes) (MB)
[Available CLM (CellID MB)]: 1 0

***********************

ioscan -f [from vpar1]

# ioscan -fn
Class I H/W Path Driver S/W State H/W Type Description
=============================================================================
root 0 root CLAIMED BUS_NEXUS
cell 0 1 cell CLAIMED BUS_NEXUS
ioa 0 1/0 sba CLAIMED BUS_NEXUS System Bus Adapter (127b)
ba 0 1/0/0 lba CLAIMED BUS_NEXUS Local PCI Bus Adapter (1054)
ext_bus 0 1/0/0/3/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6793-60001
/dev/c8xx0
target 0 1/0/0/3/0.6 tgt CLAIMED DEVICE
disk 3 1/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 146 GMAW3147NC
/dev/dsk/c0t6d0 /dev/dsk/c0t6d0s2 /dev/rdsk/c0t6d0 /dev/rdsk/c0t6d0s2
/dev/dsk/c0t6d0s1 /dev/dsk/c0t6d0s3 /dev/rdsk/c0t6d0s1 /dev/rdsk/c0t6d0s3
ext_bus 1 1/0/0/3/1 c8xx CLAIMED INTERFACE SCSI C1010 Ultra Wide Single-Ended A6793-60001
/dev/c8xx1
target 1 1/0/0/3/1.2 tgt CLAIMED DEVICE
disk 5 1/0/0/3/1.2.0 sdisk CLAIMED DEVICE _NEC DVD_RW ND-3550A
/dev/dsk/c1t2d0 /dev/rdsk/c1t2d0
processor 0 1/120 processor CLAIMED PROCESSOR Processor
ba 1 1/250 pdh CLAIMED BUS_NEXUS Core I/O Adapter
acpi_node 0 1/250/0 acpi_node CLAIMED INTERFACE Acpi Hardware
ipmi 0 1/250/1 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi


**********************

lanscan [from vpar1]
error: no PPAs available


**************************

# vparstatus -P [from vpar1]
Current Virtual Partition Version: A.05.01
Monitor Version: A.05.01

[Virtual Partition OS Version]

Virtual Partition Name OS Version State
============================== ========== =====
vPar3 B.11.31 Up
vpar1 B.11.31 Up
vpar2 Unknown Down

[Torsten.]

Your vpar1 has only 1 LBA: 1/0/0.

You have a dual scsi HBA - that's it. No configured lan device at all.

[willsfrazer]

Hi,

It's not that vpar1 did not or does not have any lan configured. Before I cloned the vPar3 with cloned disk, vpar1 was showing this :


vparstatus -v -p vpar1
vparstatus: Warning: Not accessing live monitor database, Requested resources shown.
[Virtual Partition Details]
Name: vpar1
State: N/A
Attributes: Dynamic,Autoboot,Nosearch
Kernel Path: /stand/vmunix
Boot Opts:

[CPU Details]
Min/Max: 1/4
User assigned [Path]: 1.120
Boot processor [Path]:
Monitor assigned [Path]:

Non-cell-specific:
User assigned [Count]: 1
Monitor assigned [Count]: 0
Cell-specific [Count]: Cell ID/Count


[IO Details]
1.0.1.1.0.4.0
1.0.0.3.0.6.0 BOOT

[Memory Details]
ILM, user-assigned [Base /Range]:
(bytes) (MB)
ILM, monitor-assigned [Base /Range]:
(bytes) (MB)
ILM Total (MB): 8192 (Floating 0)

ILM Granularity (MB): 128

CLM, user-assigned [CellID Base /Range]:
(bytes) (MB)
CLM, monitor-assigned [CellID Base /Range]:
(bytes) (MB)
CLM (CellID MB):

CLM Granularity (MB): 128

[OL* Details]
Sequence ID: N/A
Operation: N/A
Status: N/A

Even now if I boot server in nPar mode everything seems to be fine as vpar database has entries right.

It's when I booted vPar3 with cloned boot disk[source boot disk is vpar1's boot disk for cloning] vpar3 automatically took ownership of lan of vpar1 as well. Might be due to system configuration which cloned disk had same as of vpar1. And this is what I want to change after cloning so that resources of vpars remain as they were assigned initially even if I clone boot disk n number of times and boot different vpars with those disks.

Thanks.
Wills.

[Torsten.]

IMHO you have a general problem wit I/O assignments.

Somehow you did configure the same path to vpar1 and vpar3. (1.0.1)

You should *always* use the LBA in any assignment (except boot disks), for example:

-a io:1.0.1
-a io:1.0.0
-a io:1.0.0.3.0.6.0 BOOT




Your vpar3 has

1.0.1.1.0.1.1.6.0.0.0.0.0 BOOT

and your vpar1 has

1.0.1.1.0.4.0

This is NOT possible!

[willsfrazer]

Hi,

Initially boot disk for vPar3 was 1.0.6.1.0.1.208.0.0.2.2

then i changed it to 1.0.1.1.0.1.1.6.0.0.0.0.0 as this one is cloned disk and I was trying to boot vPar3 with this new boot disk.

So the conclusion is that I am doing a wrong configuration of resources.

How do we see what are all LBA's in nPar. And what is the correct assignment of these IO devices across the vPars depending upon these LBAs

Thanks.

[Torsten.]

Example taken in non-vpars mode:

# ioscan -fndlba
Class I H/W Path Driver S/W State H/W Type Description
============================================================
ba 0 0/0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 2 0/0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 3 0/0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 5 0/0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 7 0/0/5 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 9 0/0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 11 0/0/8 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 13 0/0/9 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 15 0/0/10 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 17 0/0/12 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 19 0/0/13 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 21 0/0/14 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 24 2/0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 25 2/0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 26 2/0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 28 2/0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 30 2/0/5 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 32 2/0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 34 2/0/8 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 36 2/0/9 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 38 2/0/10 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 40 2/0/12 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 42 2/0/13 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 44 2/0/14 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 23 3/0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 25 3/0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 26 3/0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 27 3/0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 29 3/0/5 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 31 3/0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 33 3/0/8 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 35 3/0/9 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 37 3/0/10 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 39 3/0/12 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 41 3/0/13 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
ba 43 3/0/14 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)


Assign resources like this:

-a io:1/0/1
-a io:1/0/0
-a io:1/0/0/3/0.6.0 BOOT

[Torsten.]

This may also help you to find the relation between a slot and the related hardware path:

# olrad -q
Driver(s)
Capable
Slot Path Bus Max Spd Pwr Occu Susp OLAR OLD Max Mode
Num Spd Mode
0-1-1-0 2/0/0/1 8192 133 133 Off No N/A N/A N/A PCI-X PCI-X
0-1-1-1 2/0/1/1 8448 133 133 Off No N/A N/A N/A PCI-X PCI-X
0-1-1-2 2/0/2/1 8704 133 133 On Yes No Yes N/A PCI-X PCI-X
0-1-1-3 2/0/4/1 8960 133 133 On Yes No Yes N/A PCI-X PCI-X
0-1-1-4 2/0/5/1 9216 133 133 On Yes No Yes N/A PCI-X PCI-X
0-1-1-5 2/0/6/1 9472 266 133 On Yes No Yes N/A PCI-X PCI-X
0-1-1-6 2/0/14/1 11008 266 133 On Yes No Yes N/A PCI-X PCI-X
0-1-1-7 2/0/13/1 10752 133 133 On Yes No Yes N/A PCI-X PCI-X
0-1-1-8 2/0/12/1 10496 133 133 On Yes No Yes N/A PCI-X PCI-X
0-1-1-9 2/0/10/1 10240 133 133 On Yes No Yes N/A PCI-X PCI-X
0-1-1-10 2/0/9/1 9984 133 133 On Yes No Yes N/A PCI-X PCI-X
0-1-1-11 2/0/8/1 9728 133 133 On Yes No Yes N/A PCI-X PCI-X