Sunday, June 28, 2015

How to import and export Volume Group when the device file names have changed (11iv2) HP-UX


In HP-UX 11iv2 or older the device files of the disks can change when you change the slot of the FC card or also when by any reasons the CxTxDx number changes. 11iv2 unlike 11iv3 does not use the persistent DSF.

The persistent DSFs bind to the WWID of a LUN in 11iv3 which does not change even if the controller position or the instance changes.

I suggest that you have  the latest map files of the VGs which are supposed to get affected.



Create a map file for all the VGs, say vg01,vg02 etc


1)


vgexport -p -v -s -m /tmp/vg01.map /dev/vg01
vgexport -p -v -s -m /tmp/vg02/map /dev/vg02


also make a note of

2)


ll /dev/*/group


note this information.


now ftp these map files like vg01.map,vg02.map etc to your desktop.

3) With the OS instance booted vgexport the current definitions of the VGs for which the disk cxtydz numbers have changed.


vgexport /dev/vg01
vgexport /dev/vg02


Create the VG Directories


mkdir /dev/vg01 /dev/vg02


Create the Group special files.

mknod /dev/vg01/group c 64 0xNN0000
mknod /dev/vg02/group c 64 0xMM0000


for these do refer to the info in 2) for the minor number information for the group file and try to keep this consistent for the VG as in the earlier Config.

then ftp the map files that had been saved to the desktop doing FTP after step 1). to /tmp directory of the server.

then using these do vgimport to get the new VGs come in 

vgimport -v -s -m /tmp/vg01.map /dev/vg01
vgimport -v -s -m /tmp/vg02.map /dev/vg02


Activate the VGs.

vgchange -a y vg01
vgchange -a y vg02



Take a new configuration backup of the VGs which are imported.


vgcfgbackup /dev/vg01
vgcfgbackup /dev/vg02


Do the mount operations for the file systems.

How to migrate the LVM Configuration and VGs from 11iv2 to 11iv3 (HP-UX)

LVM config migration to 11i v3

While migrating VGs from 11iv2 to 11iv3, make sure that you have the latest LVM patches also and have a look at (only) few limitations of 11iv2 Vgs being migrated to 11iv3.




Refer to compatibilty notes on page 14 of 
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01919369/c01919369.pdf (BSC link updated by admin)

Please note that the above link may have changed refer to the latest if so.

Also it is to be understood that the New generation Mass storage stack on 11iv3 has inbuilt Dynamic multipathing in it. While the legacy device files are well supported on 11iv3, you can choose to have the persistent DSFs that is agile view reflecting in your VGs.
-
Create MAP files of the VGs on 11iv2 using the command as below.

on 11iv2: (please note -p is for preview mode which just creates the map file and does not export the VG physically as such)

vgexport -p -v -s -m <map_file_name> <vg_name>

Keep these map files handy.

Post that import the VGs using the map file on 11iv3 OS


mkdir /dev/vg01



mknod /dev/vg01/group c 64 0x0Y0000

make sure that 0x0y0000 is unique on the system.


vgimport -p -v -s -m <map_file_name> <vg_name>

When the preview is satisfactory and there are no errors. 

Import without the -p option as below

vgimport -v -s -m <map_file_name> 


So once you have imported those VGs from the 11iv2 system to the 11iv3 system, once again re-export and import that VG in the following way. (This is not mandatory though and is needed only if you want to have support of persistent DSF on the VGs)



After you have imported the vgs to the 11iv3 system, say vg01 then re-export

It is worth noting that in general before actual export of a VG the VG has to be deactivated (using vgchange -a n which can be done only if the LVs in the VG are not open that is unmounted).



vgexport -p -v -s -N -m /tmp/vg01.map /dev/vg01

vgexport /dev/vg01

mkdir /dev/vg01

mknod /dev/vg01/group c 64 0x0Y0000

make sure that 0x0y0000 is unique on the system.

vgimport -v -s -N -m /tmp/vg01.map /dev/vg01

Activate the VGs using vgchange -a y <VG_NAME>


Mount the File systems.


For more see man pages of the command vgimport and vgexport also the 11iv3 Next Generation Mass Storage Stack

More on the vgexport/vgimport command on HP-UX


Please note: -f and -s options are mutually exclusive for the commands vgimport and vgexport.



vgexport -p -v -s -N -m /tmp/vg01.map /dev/vg01

this shall create the map file with the VGID of the VG in this.

after this


vgimport -v -s -N -m /tmp/vg01.map /dev/vg01

this shall scan all the disks on the system to match the VGID as in the specified map file and shall import those disks in the specified VG.



-f option of vgexport creates a file that keeps the device files in an file file.out

when this file.out is used with a vgimport command this shall scan the disks and those matching the device files in file.out shall be imported in the VG.


note that the Device Files as in 11iv2 can be different to that while the OS is 11iv3, in that case -f option can be erroneous if that can not match the device files in the target OS.

so it is better to use the -s option.



How to set USER LIMITS (ulimit) on HP-UX | Make the ulimit settings permanent | kctune related to the User Limit settings

ulimit - 

Use the command ulimit.


See more on man ulimit


time(seconds) -- use -t option 


file(blocks) ---- use -f option 


data(kbytes) -- use -d option 


stack(kbytes) -- use -s option 


memory(kbytes) -- use -m option 


coredump(blocks) -- use -c option 


nofiles(descriptors)



To make these settings permanent make sure that you add these to /etc/profile or the .profile file in the HOME of the user.


In case you need to increase the maximum values of the ULIMIT parameters. you can well think of changing the kctune values like

maxdsiz

maxssiz

or also the 64 bit kernel tunable counterparts of the above.

How to check and fix the lanboot select or lanboot with a profile fails (HP-UX) | How to Troubleshoot Ignite-UX lanboot problems

 lanboot select or lanboot with a profile fails

1) In the /etc/bootptab file when you enter the clients MAC Address for ha: there is no leading 0x required.

Check the server response from a client in the same network with bootpquery command.


See more on man bootpquery.



2) If TFTP is running in the Ignite-UX sevrer, try to get a file using TFTP from a client in the same network 

make tftp to the Ignite server and try getting the file that is /opt/ignite/boot/nbp.efi and also for /opt/ignite/boot/Rel_B.11.31/IINSTALL and /opt/ignite/boot/Rel_B.11.23/IINSTALLFS --- note well --If i remember the paths correctly.

basically on the ignite server in /etc/inted.conf make sure

tftp 
bootps
instl_boots are uncommented.

make sure that you run #inted -c after you make any changes to /etc/inetd.conf



3) in /etc/services on the ignite server, make sure that you are having ports open for

tftp 69
instl_boots 1067
instl_bootc 1068
bootps 67
bootpc 68 

are free and reachable.


4) also please note that 


/opt/ignite/boot/nbp.efi is intact on the server and also /etc/bootptab can show you that this entry is there as 

bf=/opt/ignite/boot/nbp.efi:\


Also make sure that there is no other competing DHCP server racing with the Ignite server on the network.

Saturday, June 27, 2015

Why have more than one VPAR on the system

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs





Why is this suggested to have more than one VPAR in an NPAR?


Addition of few resources as I/O and Memory do require the VPAR to be in down state.

If we have only one VPAR configured, we will be able to execute the vparmodify command keeping that VPAR down that is we will need to reboot the system in nPars mode if this is an integrity system or in an standalone mode when it is a PA-RISC system.

How to revert the VPAR configurations to use the default /stand/vpdb for a VPAR environment PA-RISC and Integrity machines running HP-UX

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs




If we want to revert to the OLD VPDB, then we need to shutdown all the current VPARs and give a reboot at the MON prompt. Interrupt the boot in BCH/EFI and give the command to boot the VPMON with no arguments, which shall boot the default /stand/vpdb.

BCH:
ISL> boot /stand/vpmon –a

EFI SHELL:
SHELL>fs0:
Fs0:>boot /stand/vpmon –a

How to create an alternate VPAR database vpdb | How to use alternate vpdb for VPARs



Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs




How can we use an Alternate VPAR Partition Database file?

The main VPAR DB file is the /stand/vpdb. The Alternate VPDB file is addressed using the option –D /stand/vpdb.alt where the /stand/vpdb.alt is the alternate VPDB file.

The alternate VPDB file can be created easily with an entirely different configuration for the VPARs even when all the VPARs are up and running without disturbing the Live partition database in the VPMON memory.

On a running VPAR we can create the VPDB.ALT

Keira1#vparcreate –p new_vpar1 –D /stand/vpdb.alt –a cpu::4 –a cpu:::4 –a mem::1600 –a io:0.0 –a io:0.4 –a io:0.0.2.0.6.0:BOOT

Keira1#vparcreate –p new_vpar2 –D /stand/vpdb.alt –a cpu::4 –a cpu:::4 –a mem::1600 –a io:0.8 –a io:1.10 –a io:1.2 –a io:0.8.0.0.5.0:BOOT

Keira1# vparstatus;shutdown –hy 00

Keira2# vparstatus;shutdown –hy 00

Keira3# vparstatus;shutdown –hy 00

MON>reboot

BCH/COMMAND> Interrupt the Autoboot

ISL> boot /stand/vpmon –D /stand/vpdb.alt –a

This boots the VPMON and loads the same into the memory with the VPAR config information as present in the VPDB.ALT.

In case of Integrity Systems


EFI SHELL>fso:
Fs0:>boot vpmon –D /stand/vpdb.alt –a

Once this VPAR is booted and we need to change some config information as for the VPARs we need not mention the DB file as /stand/vpdb.alt as that only is now current in the Memory and all changes without specifying the DB file shall modify the configurations as mentioned in the /stand/vpdb.alt only.


NOTE:


On Integrity the DB file is actually /stand/boot.sys/stand/vpdb.alt and that is soft linked to the file /stand/vpdb.alt. The command vparcreate creates the link transparently for this file the first time when the first VPAR is created.



NOTE:


1) The –D option should be used with care as lesser checks are performed when creating an alternate VPDB.ALT, that the VPDB.ALT may be totally invalid.
2) The LVM rules always apply that we will have to vgexport and again vgimport the VGs so that we are able to use the VGs.
3) The VPDB and VPDB.ALT must be in the /stand that is HFS filesystem so that the VPMON reads only the HFS partition at boot.
4) What is the VPDB that the monitor has currently booted with can only be known using the VPDB time stamps as these VPDB are synchronized every 5 minutes with the copies in all the VPARs.

How to change the boot device hardware path for a VPAR (HP-UX)


Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


How can we change the hardware path of the boot disk in a VPAR?


vpar2 is the VPAR whose disk we are going to migrate to a new hardware path location.

1) Note the present boot configuration of the VPAR vpar1

vpar2#vparstatus –p vpar2 –v --- note boot path and Autoboot and autosearch settings.

vpar2#setboot

vpar2#lvlnboot –v

vpar2#vgexport –p –v –s –m /stand/vg00.map /dev/vg00

vpar2#vgexport –p –f /stand/vg00_pv_list /dev/vg00

2) Shutdown the VPAR and remove the disk.

vpar2#shutdown –hy 00

3) Make changes to the VPDB from the other VPAR.

vpar1#vparmodify –p vpar2 –a io:new_io_path: –a io:new_io_path:boot

vpar1#vparmodify –p vpar2 –d io:old_io_path

4) Boot the VPAR from the VPMON.

MON>vparload –p vpar2 –o “-lq” –B <new_io_path>

5) After the VPAR has booted access the prompt of that VPAR and do a VGIMPORT and lvlnboot and setboot and if reqd vparefiutil.

How to reboot a hung VPAR | How to reset a Hung VPAR | What to do when the VPARs are in HUNG state | Soft reset and Hard Reset of VPARs | TOC of a VPAR | Hard Reboot of a HUNG VPAR

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


How can we boot a hung VPAR?

If a VPAR hangs we can see that in the vparstatus –v O/p and act accordingly for that in the following way.

1) vpar1#vparmodify –p vpar2 –B manual

2) vpar1#vparreset –p vpar1 –t ---- for a TOC that s soft reset.

3) vpar1#vparreset –p vpar1 –h --- hard reset --- this stops the VPAR and sets the Autoboot mode off.

4) After the vpar2 has started properly we can set the mode back to auto.

vpar1#vparmodify –p vpar2 –B auto

How to boot VPARs in Single User mode or LVM Maintenance Mode or LVM Quorum override mode with Single User

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


How can we boot a VPAR in various modes?

We can boot a VPAR in a desired mode from the UNIX Prompt using vparboot or using the VPMON vparload command. But the VPAR needs to be down to be booted in a desired mode.


vpar1#vparboot –p vpar2 –o “-is”  : Single user boot

vpar1#vparboot –p vpar2 –o “-lm”   : LVM Maintenance boot

vpar1#vparboot –p vpar2 –o “-lq” –o “-is”   : Single User with the Quorum ignore

From VPMON if we need to do the same things


VPMON

MON>vparload –p vpar2 –o “-is”   : Single user boot

MON>vparload –p vpar2 –o “-lm”   : LVM Maintenance Boot

MON>vparload –p vpar2 –o “-lq” –o “-is” : Single user with Quorum Ignore

How to configure the NPAR and all the VPARs on the NPAR to autoboot

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


HOW CAN WE MAKE ALL THE VPARS AND THE NPAR TO AUTOBOOT?

1) Make the NPAR Autoboot and autosearch to on and define the Primary and the HAA and the Alternate path properly and set the Autoboot to on in the EFI NVRAM setting.

BCH configuration/EFI SHELL> pa pri 0/0/2/0.6.0
BCH configuration/EFI SHELL> pa alt 0/8/0/0.5.0
BCH configuration/EFI SHELL> auto on

2) For the first VPAR and the Second VPAR set the boot string to boot the VPMON and all the VPAR. Say vpar1 is the first VPAR has boot disk as 0/0/2/0.6.0 (/dev/rdsk/c2t6d0) and vpar2 is the VPAR that holds the alternate boot disk 0/8/0/0.5.0 (/dev/rdsk/c1t5d0).


PARISC

vpar1#mkboot –a “hpux /stand/vpmon –a” /dev/rdsk/c2t6d0”
vpar2#mkboot –a “hpux /stand/vpmon –a” /dev/rdsk/c1t5d0”


INTEGRITY

vpar1#mkboot –a “boot /stand/vpmon –a” /dev/rdsk/c2t6d0”
vpar2#mkboot –a “boot /satnd/vpmon –a” /dev/rdsk/c1t5d0”


3) For all the VPARs set the Autoboot and autosearch strings to on.

vpar1#vparmodify –p vpar1 –B auto
vpar1#vparmodify –p vpar1 –B search
vpar1#vparmodify –p vpar2 –B auto
vpar1#vparmodify –p vpar2 –B search
vpar1#vparmodify –p vpar3 –B auto
vpar1#vparmodify –p vpar3 –B search

How to change or update the AUTOFile information AUTOBOOT Strimng for a VPAR

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


HOW CAN WE CHANGE THE AUTOFILE INFORMATION FOR A VPAR?

vpar1# vparmodify –p vpar2 –o “-is”
vpar1#vparmodify –p vpar1 –b “/stand/vmunix.other”

How to Boot VPAR from an alternate boot path | How to boot vpars from an alternate boot disk

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


How can we boot a VPAR using the Primary or Alternate Boot Paths?

vpar1#vparboot –p vpar2 –B pri
vpar1#vparboot –p vpar2

These two commands boot the VPAR vpar2 from the Primary that is default boot path.

vpar1#vparboot –p vpar2 –B alt

This boots the VPAR vpar2 from the alternate boot path as stated in the VPDB.

However if we want to boot the vpar2 using the VPMON command prompt, following are the commands:

MON> vparload –p vpar2 -- to boot from the Primary boot path.
MON> vparload –p vpar2 –B 0.8.0.0.2.0

This boots the VPAR vpar2 from the alternate boot path.HOW CAN WE MODIFY THE ATTRIBUTES OF A VPAR?

How to rename a VPAR | Change boot mode of a VPAR | Change the boot kernel of a VPAR

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


HOW CAN WE MODIFY THE ATTRIBUTES OF A VPAR?

#vparmodify –p vpar1 –P vpar1

This renames the VPAR vpar1 to vpar1.

Change the boot modes of a VPAR

#vparmodify –p vpar1 –B manual
#vparmodify –p vpar1 –B noserach


#vparmodify –p vpar1 –S static

This makes the attribute of the VPAR vpar1 as static that is the configuration of the resources on the VPAR vpar1 cannot be changed.


#vparmodify –p vpar1 –b /stand/vmunix.new

This configures the VPAR vpar1 to boot from the other kernel /stand/vmunix.new
The Alternate kernels to boot the VPARs are kept at the location /stand/alternate_config/.

HOW CAN WE REMOVE A VPAR?




Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs



The removal of a VPAR requires the VPAR to be in a shut state. So we have to shut down the VPAR before removing the same using the vparremove command.


vpar2#shutdown –hy 00
vpar1#vparremove –p vpar2

However this only removes the VPAR from the VPDB and the VPAR cannot boot.


The same VPAR if created with the same configuration can be made up and running as vparremove does not disturb any data on the VPAR’s disks.

What are the various states in which VPARs can exist (HP-UX) PA-RISC and Integrity

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


The Various States that a VPAR can be in are as follows:



The VPARs states that a VPAR can be at anytime are as follows.

1) load – the monitor VPMON is loading the kernel.

2) Boot – VPMON has loaded the kernel and the kernel is now booting the VPAR.

3) Up – the VPAR is up and running.

4) Shut – the VPAR is executing a graceful shutdown.

5) Down – the VPAR is down.

6) Crash – the VPAR is crashing due to HPMC, TOC etc , when the crash is complete, the VPAR goes to a down state.

7) Hung – the VPAR is not responding.

VPARs booting the VPMON and VPMON Commands (HP-UX) PA-RISC and Integrity servers

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


How can we boot the VPMON?

PARISC:


BCH> ISL
ISL> hpux /stand/vpmon


INTEGRITY:

SHELL> fs0:
Fso:>hpux
HPUX> boot vpmon

Options with the VPMON command:


-a read the VPDB and load all the VPARs that have the Autoboot attribute set.
-D /stand/vpdb – use the VPDB file /stand/vpdb


VPMON Commands: (Commands that can be given at the MON Prompt)


MON> readdb /stand/vpdb

NOTE:

On Integrity the /stand/vpdb is actually linked to /stand/boot.sys/stand/vpdb.backup.
So while performing the backup of the VPDB using the UNIX cp command we also have to create the link /stand/vpdb to the /stand/boot.sys/stand/vpdb.backup so that using the VPDB the VPARs can be booted.

MON>vparload –all  ---- boots all the VPARs irrespective AUTOBOOT/AUTOSEARCH is set or not.

MON> vparload –auto -- This will boot all the VPARs that have the AUTOBOOT set.

MON> vparload –p vpar1 –o “-is”

This boots the VPARs in the single user mode

MON>vparload –p vpar1 –b /stand/vmunix.other

This boots the VPAR from an alternate VPAR Kernel

MON>vparload –p vpar1 –B 0/0/0/3/0.6.0

Boot the VPAR from an alternate boot path

The alternate kernels for the VPARs are kept in the directory /stand/alternate_config/.

To see the bootpath

MON>bootpath

Reboot in nPars environment

MON>reboot nPars

Reboot in vPars environment

MON>reboot vPars

Reboot the MON (hence the system)

MON>reboot

Read a Text file in /stand

MON>cat /stand/stuents.txt

MON>cbuf vpar1 -- shows the console buffer of the partition.

MON>clear pending -- clears a pending RFR. If an RFR is pending the VPAR can not be booted so in some cases we need to clear the pending RFR.


Seeing the contents of LIF Area

MON>lifls

Get the contents of the AUTO file

MON>getauto

List the files in /stand

MON>ls

NOTE:
The following commands do not work when one or more of the VPARs are up and running, getauto, lifls and readdb.

The following commands are disabled when the VPAR is up that owns the bootdisk, ls and cat.

Important Operations for VPARs booting in vPars and nPars environments (HP-UX)

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


Commands for the VPARs:

Switching between the vPars and nPars mode: INTEGRITY ONLY:

1) HP-UX > vparenv :

If the system is booted in the NPARs MODE

#vparenv –m vPars
#shutdown –ry 00

In the EFI SHELL, SHELL> fs0:

Fso:> boot /stand/vpmon vparload –all

If the system is having all the VPARs up and running and we need to reboot the same in the NPAR mode.

#vparenv –m nPars

Shutdown all the VPARs one by one.

#shutdown –hy 00
On the Monitor prompt VPMON

MON> reboot

EFI SHELL> fs0:

Fs0:>boot /stand/vmunix

VPMON
MON>reboot nPars
MON>reboot vPars

EFI
Fso:>vparconfig reboot vPars
Fs0:>vparconfig reboot nPars



Vparconfig is not a Built-in EFI Shell command. This is installed in the EFI Shell of the disk at the time of installing the VPARs Bundle on to the system. This has to be executed from within the EFI shell of the disk.


Vparconfig is not a Built-in EFI Shell command. This is installed in the EFI Shell of the disk at the time of installing the VPARs Bundle on to the system. This has to be executed from within the EFI shell of the disk.


parconfig:

EFI Shell>

SHELL> fs0:

Fs0:>parconfig nPars –n

Fs0:>parconfig reset

It is recommended to perform the mode changing and the reboot using the vparconfig command instead of the parconfig whenever possible.

However in the cases when the VPARs product is not installed or using the other disks for the booting purposes we can use this as this command is present on an NPAR system Disk EFI even if the VPARs Bundle is not installed.
Parconfig can not be used to set the mode of the system to the VPARs mode.


NOTE:
1) If vparconfig reboot vPars is used and before that the mode is not set to vpars using the UNIX command vparenv –m vPars it is not possible to boot the VPARs.

2) It is always recommended to set the modes using the vparenv rather than vparconfig of the Disk EFI.

3) Setting the mode to vPars for the first time we must use the command as vparenv.

4) If the desired mode is not set, it will not be possible to boot in that mode.

vparefiutil:

The vparefiutil is a UNIX command that is used to update the EFI mappings in the VPDB /stand/vpdb or in the alternate VPAR Database.

The setboot or the vparmodify command only updates the entry in the VPDB, but does not update the EFI boot paths mappings of the VPDB.

During the boot of a VPAR, the VPMON reads the VPDB and transparently provides the boot path EFI settings so that the VPAR can boot.

Whenever the boot path of a disk changes or an additional boot disk is added including the addition of a boot mirror disk, the EFI mappings within the VPDB has to be updated otherwise it shall not be possible to boot that VPAR.

So vparefiutil has to be executed in the form on all the VPARs as

#vparefiutil –u –D /stand/vpdb

How to uninstall or remove the VPARs Product from the VPARs and from the entire NPAR (HP-UX)

Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


How do we remove the VPAR Product from the VPARs and from the entire NPAR?

1) Remove the VPAR at the product level from the VPAR not at the BUNDLE level.

2) Log on to the target VPAR and do a swremove on the product as such.


vpar3#swremove –x autoreboot=true VirtualPartition.

This will shutdown the associated VPAR.

3) The system then cannot be booted in the VPAR mode, however can be booted in the standalone mode.


4) This makes changes to the AUTO string converting them from /stand/vpmon to the /stand/vmunix for all the entries present in the /stand/bootconf file.


5) After the product is removed from the last VPAR, the system shall come to the MON> prompt , from there reboot the system.

HOW to install the VPARs using the IGNITE server on the INTEGRITY systems (HP-UX)

HOW to install the VPARs using the IGNITE server on the INTEGRITY systems


Note: These apply to VPARs versions 4.x/5.x . For the latest in case of any differences refer to the latest documents on the VPARs


NOTE: During the Ignite install on a VPAR in the Integrity server the LAN card of the target VPAR is used to boot the VPAR from the IGNITE server.


1) in the EFI shell configure the NPAR for the acpiconfig defaults


SHELL> acpiconfig default
SHELL> reset

To reboot the NPAR with the acpiconfig default setting as such reset has to be given.
Also make a note of the first boot path for the server.


2) Install the OS on the NPAR from an IGNITE server.


SHELL>lanboot select --- select the LAN card to boot over network from the IGNITE server and install the OS on the same. Make sure that VPARs Products also gets installed along with the OS on the system.


Also make a note of the first boot path for the server.


2) Install the OS on the NPAR from an IGNITE server.


SHELL>lanboot select --- select the LAN card to boot over network from the IGNITE server and install the OS on the same. Make sure that VPARs Products also gets installed along with the OS on the system.


3) Now create the VPARs on the server.


Create the FIRST VPAR first, say this one is vpar1.


#vparcreate –p vpar1 –a cpu::2 –a cpu:::2 –a mem::1024 –a io:0.0.1 –a io:1.0.0 –a io:1/0/0/3/0.6.0:BOOT

#vparcreate –p vpar2 –a cpu::1 –a cell:1::1 – mem::1024 –a io:1.0.1 –a io:1.0.4 –a io:1/0/4/1/0/4/0.1.0.0.0.0.1:BOOT

#vparcreate –p vpar3 –a cpu::1 –a mem::1024 –a io:0.0.2 –a io:0.0.1 –a io:0/0/0/3/0.6.0:BOOT

4) Set the system to be booted into the VPARs mode.

#vparenv –m vPars
#shutdown –ry 00


5) As the system comes in the EFI shell, we need to boot the same in the VPARs mode.


SHELL> fs0:
Fs0:>boot /stand/vpmon –p vpar1



vpar1 boots as a VPAR.



6) Install the Other VPARs from the Ignite server.

vpar1#vparboot –p vpar2 –I


This will lead to modify the EFI shell settings for vpar2 and shall execute the lanboot select for the same.

Go to the console of the vpar2 using CTRL-A.

The vparboot command uses the LAN card of the target VPAR vpar2 to contact the ignite server and boot the same from the IGNITE server.

IINSTALL and IINSTALLFS are tftp downloaded from the IGNITE server by the target VPAR LAN card only. 

The booting VPAR connects the IGNITE server using the same LAN card as specified and rest of the installation takes place from there.



Repeat the same steps for the other VPARs also.

pip3 install ovirt-engine-sdk-python 4.4.1 - import ovirtsdk4 errors with pycurl link-time SSL backend was nss and not openssl

In [2]: import ovirtsdk4 --------------------------------------------------------------------------- ImportError                         ...