topic Re: create a new vPAR in Operating System - HP-UX

create a new vPAR

marvik — Fri, 01 Aug 2008 10:28:27 GMT

Hi Guys,
Here is the configuration and I wanna create a 2nd vPAR on this nPAR.I wanna know the paths of i/o , cpu, bootable disk , Can u pls suggest how to proceed.
1st vPAR is already created.

Its a 2cell server,nPAR0 consists of both the cells.
i have to create 2 vPAR each consisting one cell.

model:
ia64 hp server rx7640

root@partition1:/root# parstatus -Vp 0
[Partition]
Partition Number : 0
Partition Name : partition1
Status : Active
IP Address :
Primary Boot Path : 0/0/0/3/0.0x6.0x0
Alternate Boot Path :
HA Alternate Boot Path :
PDC Revision : 9.22
IODCH Version : N/A
Cell Architecture : Itanium(R)-based
CPU Compatibility : CDH-640
CPU Speed : 1598 MHz
Core Cell : cab0,cell1
Core Cell Choice [0] : cab0,cell1
Total Good Memory Size : 32.0 GB
Total Interleave Memory: 32.0 GB
Total Requested CLM : 0.0 GB
Total Allocated CLM : 0.0 GB
GSM Sharing : Disabled complex-wide
Hyperthreading Enabled : yes

[Cell]
CPU Memory Use
OK/ (GB) Core On
Hardware Actual Deconf/ OK/ Cell Next Par
Location Usage Max Deconf Connected To Capable Boot Num
========== ============ ======= ========= =================== ======= ==== ===
cab0,cell0 Active Base 4/0/8 16.0/0.0 cab0,bay0,chassis0 yes yes 0
cab0,cell1 Active Core 4/0/8 16.0/0.0 cab0,bay0,chassis1 yes yes 0

Notes: * = Cell has no interleaved memory.

[Chassis]
Core Connected Par
Hardware Location Usage IO To Num
=================== ============ ==== ========== ===
cab0,bay0,chassis0 Active yes cab0,cell0 0

[Chassis]
Core Connected Par
Hardware Location Usage IO To Num
=================== ============ ==== ========== ===
cab0,bay0,chassis1 Active yes cab0,cell1 0

Here is th config of the 1st vPAR

root@parstatus1:/root# vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============================== ===== ============ ======================= =====
partition1 Up Dyn,Auto,Nsr /stand/vmunix

[Virtual Partition Resource Summary]
CPU Num Num Memory Granularity
Virtual Partition Name Min/Max CPUs IO ILM CLM
============================== ======= ==== ==== ========== ==========
partition1 1/ 4 4 2 512 512

Memory (MB)
ILM CLM
# User # User
Virtual Partition Name Ranges/MB Total MB Ranges/MB Total MB
============================== ====================== ======================
partition1 0/ 0 15360 0/ 0 0

Re: create a new vPAR

Torsten. — Fri, 01 Aug 2008 10:34:52 GMT

>>"I wanna know the paths of i/o , cpu, bootable disk"

For exactly this reason you should keep an "ioscan -fn" made in non-vapr configuration.

Now you can reboot to non-vpar environment and get it or have a look at the hardware and calculate the pathes...

An

# vparstatus -A

may help.

Re: create a new vPAR

marvik — Fri, 01 Aug 2008 11:01:35 GMT

Thanks Torsten,
here's vparstatus -A output but when i reboot it comes back in vpar mode.Do u mean i should change vparenv -m npars and then reboot the server ?

[CPUs (path)]: 1.120
1.121
1.122
1.123
[CLP (CellID Count)]: 0 0
1 4
[Available CPUs]: 4

[Available I/O devices (path)]: 1.0
1.0.0
1.0.1
1.0.2
1.0.4
1.0.6
1.0.8
1.0.10
1.0.12
1.0.14

[Available ILM (Base /Range)]: 0x20000000/511
(bytes) (MB) 0x4c0000000/12800
0x7e0000000/384
0x4040000000/2560
0x40e0000000/508
[Available ILM (MB)]: 16763

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

Re: create a new vPAR

Torsten. — Fri, 01 Aug 2008 11:06:47 GMT

Now you know all available slots.

Take a look what slots you want to assign.

The install process will tell you the path to the boot disk, use this information to set the boot path in vPar config.

Normally, all this information you currently have should be enough to setup your new vPar.

Re: create a new vPAR

marvik — Fri, 01 Aug 2008 11:21:43 GMT

i have t use the entire I/O what i can't make out of this is which should be the Pri Boot path.I have to install OS using Ignite/UX which i will do once my vPar is created.

JFYI,
I rebooted the box in nPARS mode but that made it stuck in MON prompt .so i had to reboot it from there in vPARS mode again

MON>reboot vPars

Re: create a new vPAR

Torsten. — Fri, 01 Aug 2008 11:28:52 GMT

Did you install to internal, external, SCSI or SAN disk?

You should see the used boot disk anywhere in the ignite installation or the console logs.

Re: create a new vPAR

marvik — Fri, 01 Aug 2008 11:32:23 GMT

But in the vparcreate command I have to give the -a io:*****:BOOT

so what H/W path should I give there.Without this the vparcreate command is incomplte

Re: create a new vPAR

marvik — Fri, 01 Aug 2008 11:33:25 GMT

From the vPar0 this is the output of ioscan disk

root@ddpsdb02:/root# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
=======================================================================
disk 0 0/0/0/3/0.6.0 sdisk CLAIMED DEVICE HP 146 GHUS153014VL3800
/dev/dsk/c0t6d0 /dev/dsk/c0t6d0s2 /dev/rdsk/c0t6d0 /dev/rdsk/c0t6d0s2
/dev/dsk/c0t6d0s1 /dev/dsk/c0t6d0s3 /dev/rdsk/c0t6d0s1 /dev/rdsk/c0t6d0s3
disk 1 0/0/1/1/0/4/1.5.0 sdisk CLAIMED DEVICE HP 146 GHUS153014VL3800
/dev/dsk/c3t5d0 /dev/rdsk/c3t5d0

Re: create a new vPAR

Torsten. — Fri, 01 Aug 2008 11:37:00 GMT

Another suggestion:

- switch to non-vPar mode and reboot
- let the system boot the default boot entry from EFI menu
- interrupt the OS loader!
- now you have the HPUX> prompt

- run

HPUX> boot vmunix

this will boot the kernel directly, the default setting is "boot vpmon" - this will boot the vPar monitor.

Once the (non-vPar) system is booted, you have access to all devices.

Run

# ioscan -fn

and look for all disks with special files like

cxtydzs2

(note the "s2"!)

These are boot disks - the disk that isn't in

# strings /etc/lvmtab

under vg00 is most likely the boot disk of your new vPar.

# vparstatus -v

will confirm this.

Re: create a new vPAR

Torsten. — Fri, 01 Aug 2008 11:38:31 GMT

My understanding is your second vPar is already installed via ignite, right?

Re: create a new vPAR

marvik — Fri, 01 Aug 2008 11:51:04 GMT

i'll try with the steps now nad get back

No my second vPAR is not yet created.I am looged into the MP and thru console logged into the vPAR0 shell prompt , from there I'm tryin to run the vparcreate to create the 2nd vPar.
Once my vPar1 is created and visible in vparstatus command i'll install OS on it thru ignite server ( vpar0 )

Thanks for all the insight

Re: create a new vPAR

Torsten. — Fri, 01 Aug 2008 11:58:20 GMT

Ok, now I see.

It's a lot more easy now ;-)

Define your vPar and let the -a io:...:BOOT away. Now install hp-ux. In the installer windows, you can select the boot disk (you will see the path here) - note it down!

While the vPar is installing hp-ux, you can go back to your first vPar and use

# vparmodify ...

to add the boot disk setting - that's it.

Re: create a new vPAR

marvik — Fri, 01 Aug 2008 12:10:40 GMT

I changed to nPars and the shutdown -ry 0

00:fs0:\> hpux
Usage:
(C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P.
All rights reserved

HP-UX Boot Loader for IPF -- Revision 2.035

Press Any Key to interrupt Autoboot
\efi\hpux\AUTO ==> boot vmunix
Seconds left till autoboot - 4
Type 'help' for help

HPUX> boot vmunix
> System Memory = 333 MB
loading section 0
.............................................................................. (complete)
loading section 1
............. (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
......
loading MFSFILES directory (bootfs) to MFS
........................
Launching /stand/vmunix
SIZE: Text:39822K + Data:6330K + BSS:19516K = Total:65669K
Console is on virtual console - via PCDP
Booting kernel...

This kernel cannot be launched directly when the system
is set to vPars mode. To launch a kernel please boot
the vPar monitor, vpmon, and then load any configured
vPars with the 'vparload' monitor command.

The system will now reset.

And its getting into a loop

Re: create a new vPAR

Torsten. — Fri, 01 Aug 2008 12:17:50 GMT

No need to do this.

Just boot back to vPars mode.

I thought you have already installed hp-ux on the new vPar and can't remember the boot disk path ...

Just do like I wrote a post earlier ... install and set the path later.