Mixed HP-UX 11i v1/v2/v3 vPars Environments in vPars A.05.03

Beginning with vPars A.05.03, you can have a mixed HP-UX 11i v1/v2/v3 vPars environment on PA-RISC systems only. A mixed HP-UX 11i v1/v2/v3 vPars environment allows you to have a vPars A.05.03 monitor and database that supports:

virtual partitions running vPars A.05.03 on HP-UX 11i v3 (11.31)
virtual partitions running vPars A.04.02 or later on HP-UX 11i v2 (11.23), and
virtual partitions running vPars A.03.05 on HP-UX 11i v1 (11.11)

An example mixed HP-UX 11i v1/v2/v3 vPars environment looks like the following:

Table 3-6 Mixed HP-UX 11i v1/v2/v3 vPars Environment

HP-UX 11i v3 (11.31) running vPars A.05.03	HP-UX 11i v2 (11.23) running vPars A.04.02	HP-UX 11i v1 (11.11) running vPars A.03.05	HP-UX 11i v3 (11.31) running vPars A.05.03	HP-UX 11i v2 (11.23) running vPars A.04.05
vPars A.05.03 Monitor

Mixed HP-UX 11i v1/v2/v3 vPars does not refer to mixing hardware (PA-RISC and Integrity) platforms. Additionally, virtual partitions running vPars A.05.02 or earlier on HP-UX 11iv3 (11.31), vPars A.04.01 or earlier on HP-UX 11i v2 (11.23), or vPars A.03.04 or earlier on HP-UX 11i v1 (11.11) are not supported in a mixed HP-UX 11i v1/v2/v3 vPars environment.

Features of Mixed HP-UX 11i v1/v2/v3 vPars Environments

The following are notable features of mixed HP-UX 11i v1/v2/v3 vPars environments:

The vPars A.05.03 Monitor or later is required for a mixed HP-UX 11i v1/v2/v3 vPars environment.
The vPars A.05.03 Monitor supports virtual partitions running vPars A.05.03 on HP-UX 11i v3 (11.31), virtual partitions running vPars A.04.02 or later on HP-UX 11i v2 (11.23), and virtual partitions running vPars A.03.05 on HP-UX 11i v1 (11.11).
The vPars A.03.05 Monitor does not support booting the HP-UX 11i v2 or 11i v3 environments.
The vPars A.04.xx Monitor does not support booting the HP-UX 11i v3 environment.
HP-UX 11i v3 virtual partitions (running vPars A.05.03) have no vPars command restrictions as compared with a pure HP-UX 11i v3 vPars environment.
An HP-UX 11i v1 virtual partition (running vPars A.03.05) can use vparmodify on itself only, and cannot use the vparcreate and vparremove commands. Thus, in a mixed HP-UX 11i v1/v2/v3 vPars environment, an HP-UX 11i v1 virtual partition cannot remove virtual partitions, cannot create new virtual partitions, and can modify only itself.
An HP-UX 11i v2 virtual partition (running vPars A.04.02 or later) can use vparmodify on itself only, and cannot use the vparcreate and vparremove commands. Thus, in a mixed HP-UX 11i v1/v2/v3 vPars environment, an HP-UX 11i v2 virtual partition cannot remove virtual partitions, cannot create new virtual partitions, and can modify only itself.
When the vPars Flexible Administrative Capability feature is enabled, a vPars A.05.03 virtual partition should be the designated-admin virtual partition. Because of HP-UX 11i v1 and 11i v2 virtual partition command restrictions in mixed HP-UX 11i v1/v2/v3 vPars environments, if only HP-UX 11i v1 or HP-UX 11i v2 virtual partitions are configured to be designated-admin, then no virtual partitions will be able to perform vparmodify, vparremove, or vparcreate operations on other virtual partitions.
The status details reported by the vparstatus command are determined by the target virtual partition version and the vPars software version of the virtual partition issuing the command.
- Cell Local Memory (CLM) and Cell Local Processor (CLP) details are displayed only when listing details from an HP-UX 11i v2 or 11i v3 virtual partition.
- Bound and floater CPU information is displayed only when listing details from an HP-UX 11i v1 virtual partition. This information is presented in legacy (HP-UX 11i v1) format.
- HP-UX 11i v1 bound processors are shown only when the HP-UX 11i v1 virtual partition is in an “up” state.
- When the vparstatus command is run from an HP-UX 11i v2 or v3 virtual partition to display information about an HP-UX 11i v1 virtual partition:
  The output is displayed in HP-UX 11i v2/v3 format.
  The bound CPUs in an HP-UX 11i v1 virtual partition are reported as “Min CPUs”.
- When the vparstatus command is run from an HP-UX 11i v1 virtual partition to display information about an HP-UX 11i v2 or v3 virtual partition:
  An HP-UX 11i v2 or 11i v3 virtual partition's monarch CPU is reported as “bound”.
  If an HP-UX 11i v2 or 11i v3 virtual partition has Cell Local Processors, some CPUs are reported as “user bound”. The vparstatus -A option does not list CLP details when issued from HP-UX 11i v1.
  All other HP-UX 11i v2 or 11i v3 CPUs are shown as unbound (floater).
  Any Cell Local Memory assigned to an HP-UX 11i v2 or 11i v3 virtual partition is listed as part of the total memory. (That is, the “total memory” reported for the virtual partition is a sum of the interleaved memory and CLM.)
The vparstatus -P command option is provided to display the HP-UX version running on virtual partitions in a mixed HP-UX 11i v1/v2/v3 vPars environment.
HP Global Workload Manager (gWLM) is supported in mixed HP-UX 11i v1/v2 vPars environments with the following restrictions:
- Do not nest processor sets (Psets) under vPars A.03.05.
- Do not assign CLPs to any of the virtual partitions.
For details about these restrictions for using gWLM in a mixed vPars environment see the HP-UX Virtual Partitions Release Notes (A.03.05).
The Virtual Partition Manager (vparmgr) GUI is supported only on HP-UX 11i v1 virtual partitions in a mixed HP-UX 11i v1/v2/v3 vPars environment.
In a mixed HP-UX 11i v1/v2/v3 vPars environment, dynamic memory migration is only supported on the vPars versions that support dynamic memory migration. In other words, both the source and target virtual partitions must be running vPars A.05.03.
Hyperthreading is not supported in mixed HP-UX 11i v1/v2/v3 vPars environments.
Enabling hyperthreading (HT ON) is supported only on Integrity systems with hyperthreading-capable processors. However, only HP-UX 11i v3 supports hyperthreading. HP-UX 11i v2 cannot boot on an Integrity system that has hyperthreading enabled, and HP-UX 11i v1 only is supported on PA-RISC systems.
HP-UX 11i v1 virtual partitions (vPars A.03.05) does not support CLM or CLP resources.
It is possible—but not supported—to add CLM or CLP resources to an HP-UX 11i v1 virtual partition when it is in a “down” state. However, booting an HP-UX 11i v1 virtual partition will be halted if it has CLM or CLP resources assigned to it.
The system firmware must match the vPars A.05.03 firmware requirements.

Features Summary

The following table highlights the rules for having a mixed HP-UX 11i v1/v2/v3 vPars environment.

Table 3-7 Mixed HP-UX 11i v1/v2/v3 vPars Environment Feature Summary

Feature	vPars A.05.xx instances	vPars A.04.xx instances	vPars A.03.05 instances
Minimum vPars Version	A.05.03	A.04.02 or later	A.03.05
vPars Monitor Supports Mixed HP-UX 11i v1/v2/v3 vPars Environment	Yes	No	No
Dynamic CPU Migration	Supported	Supported	Not Supported
Dynamic Memory Migration	Supported	Not Supported	Not Supported
HT OFF	Supported (Integrity only)	Supported (Integrity only)	Not Applicable (vPars A.03.05 not supported on Integrity)
HT ON	Supported (Integrity only)	Not Supported	Not Applicable (vPars A.03.05 not supported on Integrity)
Cell Local Processor (CLP)	Supported	Supported	Not Supported
Cell Local Memory (CLM)	Supported	Supported	Not Supported
vparcreate, vparremove	Supported	Not Supported	Not Supported
vparmodify on other virtual partitions	Supported	Not Supported	Not Supported

Mixed HP-UX 11i v1/v2/v3 vPars Environments in vPars A.05.03

Technical documentation

» Table of Contents

» Glossary

» Index

Features of Mixed HP-UX 11i v1/v2/v3 vPars Environments

Features Summary