vPar on 7620

[trytosolve]

Hi All,
We are trying to install vPar on 7620 which is a 2 cell system with 4GB memory, FYI... i am new vPar world

Now this is what is the current setup:
nPar's
cell0 -windows
cell1 - HP-UX 11.23

without disturbing the setup we need vPar on cell1
so we installed vPar and created a vPar using the below

vparcreate -p myvpar -a cpu::2 -a cpu:::1:2 -a cpu:120 -a cpu:121 -a mem::1024 -a io:1.0.0 -a io:1.0.1 -a io::boot

it created successfully
vparenv -m vPars and reboot the system and on the reboot from Shell:> changed to fs0: and changed to hpux> and boot /stand/vpmon vparload -all and here the output is fs0:> and does nothing

I am not sure if the command was executed correct command and created the vPar.

Thanks for your help

[Tim Nelson]

Type help at the vpar MON> prompt. There should be an option for vparstatus listing "myvar" and it's properties.

[Tim Nelson]

Boot to the vpar MON> prompt and type help at the MON> prompt. There should be an option for vparstatus listing "myvar" and it's properties.

vparboot -l myvpar after reviewing.

If not, reboot the npar straight to HPUX and start over.

[trytosolve]

should i execute the vparboot from shell or in nPar of HP-UX, if it is HP-UX npar i get vPar monitor is not running

[trytosolve]

# vparboot -p mrovpar
vparboot: Error: Virtual partition monitor not running.

[trytosolve]

Hi Tim,
i am not getting the vPar MON> prompt as its not getting loaded when i execute manual boot from HPUX> prompt vpar boot /stand/vpmon does nothing.
thanks,
Kumar

[Tim Nelson · Accepted solution]

Here is my steps from a new server perspective.

1) configure nPar to your likeing, in this case nPar1 is your UNIX partition.

2) boot your install cd from nPar1 and install your unix instance.

3) Once unix is up, configure the vPar as you have mentioned.

4) shutdown your UNIX partition and boot the disk where UNIX is installed but use /stand/vpmon instead of /stand/vmunix

5) you should now be at the MON> prompt. from there you can review the config and vparboot your first vPar. once booted you will have unix running in the first vpar

6) from here on it becomes a preference.

a) create ignite image on ignite server to be used for installing second vPar
b) cold install second vPar.

1a) configure your second vPar using the vparcreate or gui. from the first vPar execute vparboot -p myvpar2 ( using the ignite server as the source, you will have to look at the syntax for this )

1b) a little more research is needed here as I do not remember the exact process when two nPars are deployed.
Summary: shutdown vPar1 and boot the install cd, then install unix onto the vPar2 assigned disk. Once unix is installed shutdown and boot to vpmon again. You should be able to see both vPars. boot one, the other, or both.

The above assumes you have assigned all the CPU, IO, and Mem correctly to both vpars.

There are some good white papers under the virtual environment section of docs.hp.com

Hope this helps and does not confuse.

[trytosolve]

Thanks Tim, i shall try this, mean while i have couple more question before i start

I have one Lan card, do i need a seperate NIC card, for vPar and a unused HDD

Thanks,
Kumar

[melvyn burnard]

yes.
Each Vpar requires a disk device to have the OS loaded onto and boot from, and a LAN card to be able to connect to the network

[Torsten.]

Hi,

your first vPar will use the same disk as your non-vPar nPar.
I assume the npar is using the internal disks

1/0/1/1/0/1/1.6.0
and
1/0/0/3/0.6.0

For HP-UX 11.23 it is enough to specify the number of CPUs only, like you did:

-a cpu::2 -a cpu:::1:2

(no need to give
-a cpu:120 -a cpu:121 )

1GB of memory looks like a little less:

-a mem::1024

after creating the vPar and setting the mode you should set the AUTO file (bootstring in the EFI area) like this:

# echo "hpux vpmon -a" >/tmp/AUTO
# efi_cp -d /dev/rdsk/c3t2d0s1 /tmp/AUTO /EFI/HPUX/AUTO

Adjust "c3t2d0s1" to your value!

Now you can reboot and the vPar will start up ...

[Tim Nelson]

Each vPar required it's own physical IO assignments.

i.e. 1 SCSI for each disk, 1 NIC for each LAN, 1 FC for each fibre attach, etc...
In the vpar world they must be assigned per LBA ( i.e. physical interface card )

If you want to share IO cards you have to start looking at integrity virtual machines ( which is a little closer to HP's version of VMWare ).

2 vpars requires two of everything, 3 vpars requires 3 of everything. In an RP7420 already having 2 nPars you have already cut the number of usable slots in 1/2 and are going to run out of physical slots even before you start.

[trytosolve]

I have the dmesg and ioscan output, could you please help me in creating the vPar, "vparcreate" followed by the parameters using the below information

# dmesg

Jan 24 16:16
Found adjacent data tr. Growing size. 0x3467000 -> 0x7467000.
Pinned PDK malloc pool: base: 0xe000000100b99000 size=119196K
Loaded ACPI revision 2.0 tables.

MFS is defined: base= 0xe000000100b99000 size= 1864 KB


Unpinned PDK malloc pool: base: 0xe000000108000000 size=98304K
Multiple MCAs/INITs feature enabled via checksum invalidation method
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
NOTICE: mod_fs_reg: Cannot retrieve configured loading phase from KRS for module
: cifs. Setting to load at INIT

1 cell
1/0 sba
1/0/0 lba
1/0/0/0/0 asio0
1/0/0/0/1 asio0
c8xx BUS: 0 SCSI C1010 Ultra160 Wide LVD A6793-60001 assigned CPU: 1
1/0/0/3/0 c8xx
c8xx BUS: 1 SCSI C1010 Ultra Wide Single-Ended A6793-60001 assigned CPU: 0
1/0/0/3/1 c8xx
1/0/1 lba
1/0/1/1/0 PCItoPCI
c8xx BUS: 2 SCSI C1010 Ultra160 Wide LVD assigned CPU: 1
1/0/1/1/0/1/0 c8xx
c8xx BUS: 3 SCSI C1010 Ultra160 Wide LVD assigned CPU: 0
1/0/1/1/0/1/1 c8xx
1/0/1/1/0/4/0 igelan
1/0/2 lba
1/0/2/1/0 PCItoPCI
c8xx BUS: 4 SCSI C1010 Ultra160 Wide LVD assigned CPU: 1
1/0/2/1/0/1/0 c8xx
c8xx BUS: 5 SCSI C1010 Ultra160 Wide LVD assigned CPU: 0
1/0/2/1/0/1/1 c8xx
1/0/2/1/0/4/0 igelan
1/0/4 lba
1/0/6 lba
1/0/8 lba
1/0/10 lba
1/0/12 lba
1/0/14 lba
1/120 processor
1/121 processor
1/250 pdh
1/250/0 acpi_node
1/250/1 ipmi
1/0/0/3/1.2 tgt
1/0/0/3/1.2.0 sdisk
1/0/0/3/0.6 tgt
1/0/0/3/0.6.0 sdisk
1/0/0/3/0.7 tgt
1/0/0/3/0.7.0 sctl
1/0/0/3/1.7 tgt
1/0/0/3/1.7.0 sctl
1/0/1/1/0/1/1.6 tgt
1/0/1/1/0/1/1.6.0 sdisk
1/0/1/1/0/1/1.7 tgt
1/0/1/1/0/1/1.7.0 sctl
1/0/1/1/0/1/0.7 tgt
1/0/1/1/0/1/0.7.0 sctl
1/0/2/1/0/1/0.7 tgt
1/0/2/1/0/1/0.7.0 sctl
1/0/2/1/0/1/1.7 tgt
1/0/2/1/0/1/1.7.0 sctl
Boot device's HP-UX HW path is: 1/0/0/3/0.6.0

System Console is on the Built-In Serial Interface
igelan0: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 1/0/1/1/0/4
/0
igelan1: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 1/0/2/1/0/4
/0
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 8388608
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x6000; start = 1743732,
size = 4194300
Starting the STREAMS daemons-phase 1
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 4177168 Kbytes, lockable: 2968360 Kbytes, available: 3450696 Kbyte

ioscan output:
=============================================================
root
1 cell
1/0 ioa System Bus Adapter (127b)
1/0/0 ba Local PCI Bus Adapter (1054)
1/0/0/0/0 tty PCI SimpleComm (103c1290)
1/0/0/0/1 tty PCI Serial (103c1048)
1/0/0/3/0 ext_bus SCSI C1010 Ultra160 Wide LVD A
6793-60001
1/0/0/3/0.6 target
1/0/0/3/0.6.0 disk HP 36.4GMAU3036NC
1/0/0/3/0.7 target
1/0/0/3/0.7.0 ctl Initiator
1/0/0/3/1 ext_bus SCSI C1010 Ultra Wide Single-E
nded A6793-60001
1/0/0/3/1.2 target
1/0/0/3/1.2.0 disk _NEC DVD+RW ND-2100AD
1/0/0/3/1.7 target
1/0/0/3/1.7.0 ctl Initiator
1/0/1 ba Local PCI-X Bus Adapter (122e)
1/0/1/1/0 ba PCItoPCI Bridge
1/0/1/1/0/1/0 ext_bus SCSI C1010 Ultra160 Wide LVD
1/0/1/1/0/1/0.7 target
1/0/1/1/0/1/0.7.0 ctl Initiator
1/0/1/1/0/1/1 ext_bus SCSI C1010 Ultra160 Wide LVD
1/0/1/1/0/1/1.6 target
1/0/1/1/0/1/1.6.0 disk HP 36.4GMAU3036NC
1/0/1/1/0/1/1.7 target
1/0/1/1/0/1/1.7.0 ctl Initiator
1/0/1/1/0/4/0 lan HP A6794-60001 PCI 1000Base-T
1/0/2 ba Local PCI-X Bus Adapter (122e)
1/0/2/1/0 ba PCItoPCI Bridge
1/0/2/1/0/1/0 ext_bus SCSI C1010 Ultra160 Wide LVD
1/0/2/1/0/1/0.7 target
1/0/2/1/0/1/0.7.0 ctl Initiator
1/0/2/1/0/1/1 ext_bus SCSI C1010 Ultra160 Wide LVD
1/0/2/1/0/1/1.7 target
1/0/2/1/0/1/1.7.0 ctl Initiator
1/0/2/1/0/4/0 lan HP A6794-60001 PCI 1000Base-T
1/0/4 ba Local PCI-X Bus Adapter (122e)
1/0/6 ba Local PCI-X Bus Adapter (122e)
1/0/8 ba Local PCI-X Bus Adapter (122e)
1/0/10 ba Local PCI-X Bus Adapter (122e)
1/0/12 ba Local PCI-X Bus Adapter (122e)
1/0/14 ba Local PCI-X Bus Adapter (122e)
1/120 processor Processor
1/121 processor Processor
1/250 ba Core I/O Adapter
1/250/0 acpi_node Acpi Hardware
1/250/1 ipmi IPMI Controller

[Tim Nelson]

See the attached word doc ( double check for accuracy ). I have highlightend the vPar1 HW in red and the vPar2 HW in blue.

You do have two SCSI disk and two LAN NIC on separate LBA.

Give 1 proc to each vpar and the IO paths with some memory and you are ready to go. ( i.e. start over creating vpar and the rest of this thread ).

[Tim Nelson]

Every gosh dern time... Always forget the attach.

[Tim Nelson]

BTW..

Great docs under the virtual partition chapter here. http://docs.hp.com/en/oshpux11iv2.html

[trytosolve]

Hi Tim,
Thanks for the info it made me understand few concepts

but still not able to do it successful, i had installed Fresh HP-UX 11.23 on rx7620 on cell 1 and please find the below information:

vparcreate -p keiral -a cpu::2 -a cpu:::1:2 -a cpu:120 -a io:1.0.2 -a io:1.0.0.3.0.6.0:BOOT

vparcreate: Note: Database is created with the following information:
CLM granularity is 128 MBytes
ILM granularity is 128 MBytes
All the subsequent virtual partition's CLM or ILM memory specifications must be
an integral multiple of the corresponding granularity.

# vparstatus -p keiral
vparstatus: Warning: Not accessing live monitor database, Requested resources sh
own.
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
============================== ===== ============ ======================= =====
keiral N/A Dyn,Auto,Nsr /stand/vmunix

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

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

# vparenv -m vPars
#

Shell> fs0:x' to start hpux bootloader
fs0:\> hpux

(C) Copyright 1999-2006 Hewlett-Packard Development Company, L.P.
All rights reserved

HP-UX Boot Loader for IPF -- Revision 2.028

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

HPUX> boot /stand/vpmon

fs0:\>

now i executed hpux and the below is seen

HP-UX Boot Loader for IPF -- Revision 2.028

Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vmunix
Seconds left till autoboot - 0
AUTOBOOTING...Start of HP-UX Primary Boot: 1/0/0/3/0.6.0 failed: Unsupported
Paused - press any key to continue

i moved to blk1:/EFI/HPUX:> and changed back to HP-UX system and the system was reboot and back to HP-UX 11.23 the base OS on nPar

[Tim Nelson]

1 note: there is no memory assigned to the vpar. vparmodify -p vpar1 -a mem::1024 (or some value enough to run the OS and applicaiton.)

Looking through the docs for IPF boot syntax. I have the PARISC memorized but not the IPF.

Will get back to you.

[Tim Nelson]

From the doc.

-Integrity:
shell>fs0
fs0:\> hpux
HPUX> boot vpmon

remove the /stand/vpmon and just try vpmon.

[trytosolve]

Hi Tim, i still get the same prompt even after modifying the vpar with mem

fs0:>

[Torsten.]

Like suggested by Tim, you must not start vmunix after reboot.

You have to run this:

fs0:\> hpux
HPUX> boot vpmon

because your system is in vPars mode and cannot run vmunix.

If you want to run in non-vPars mode, you must set the nPar mode:

fs0:\> vparconfig reboot nPars

This is setting the system back to nPars mode.


Remember to set the AUTO file!!!

# echo "hpux vpmon -a" >/tmp/AUTO
# efi_cp -d /dev/rdsk/c3t2d0s1 /tmp/AUTO /EFI/HPUX/AUTO


Good luck and thanks for the points in advance ;-)

[trytosolve]

Hi,
thanks, but please see the below: i reboot the system now with nPar mode and set the values as you mentioned

root@bwink30> echo "hpux vpmon -a" > /tmp/AUTO

root@bwink30> efi_cp -d /dev/rdsk/c3t2d0s1 /tmp/AUTO /EFI/HPUX/AUTO
efi_cp: open device failed(errno = 2)

[Torsten.]

This was just to remind you.

READ MY POST!!!

"Adjust "c3t2d0s1" to your value!"

Don't cut and paste without think about it!

Read the doc and come back again:

http://docs.hp.com/en/T1335-90056/T1335-90056.pdf