HP-UX Virtual Partitions Administrator Guide (includes A.05.08) (5900-1312, March 2011)

A.04.05 Monitor and database that supports both virtual partitions running vPars A.04.05 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 vPars environment looks like the following:
Table 7 Mixed HP-UX 11i v1/v2 vPars Environment
HP-UX 11i v1 (11.11)
running vPars A.03.05
HP-UX 11i v2 (11.23)
running vPars A.04.05
HP-UX 11i v1 (11.11)
running vPars
A.03.05
HP-UX 11i v1 (11.11)
running vPars
A.03.05
HP-UX 11i v2
(11.23) running
vPars A.04.05
vPars A.04.05 Monitor
Mixed HP-UX 11i v1/v2 vPars does not refer to mixing hardware (PA and Integrity) platforms.
Additionally, virtual partitions running vPars A.05.xx on HP-UX 11i v3 (11.31), vPars A.04.04
and earlier on HP-UX 11i v2 (11.23), or vPars A.03.04 and earlier on HP-UX 11i v1 (11.11) are
not supported in a mixed HP-UX 11i v1/v2 vPars environment.
Features of Mixed HP-UX 11i v1/v2 vPars Environments
The following are notable features of mixed HP-UX 11i v1/v2 vPars environments:
• The vPars A.04.05 Monitor or later is required for a mixed HP-UX 11i v1/v2 vPars environment.
The vPars A.04.05 Monitor supports both virtual partitions running vPars A.04.05 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 supports booting only the HP-UX 11i v1 vPars A.03.05 environment.
The vPars A.03.05 Monitor does not support booting HP-UX 11i v2 environments and does
not support Ignite-UX installation of HP-UX 11i v2 vPars using the vparboot -I command.
• HP-UX 11i v1 virtual partitions (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 vPars environment, an HP-UX 11i v1 virtual partition cannot remove virtual partitions,
cannot create new virtual partitions, and can modify only itself.
• HP-UX 11i v2 virtual partitions (running vPars A.04.05) have no vPars command restrictions
as compared with a pure HP-UX 11i v2 vPars environment.
• The status details reported by vparstatus are determined by the target virtual partition
version and the vPars software version of the virtual partition issuing the command:
◦ When vparstatus is run from an HP-UX 11i v2 virtual partition targeting an HP-UX 11i
v1 virtual partition, the result is shown in HP-UX 11i v2 (vPars A.04.05) format.
◦ The vparstatus command run from an HP-UX 11i v1 virtual partition does not report
cell local memory (CLM) and cell local processor (CLP) details for HP-UX 11i v2 virtual
partitions, even if they have CLM or CLP configured.
Likewise, the vparstatus -A command run from an HP-UX 11i v1 virtual partition does
not display CLP information.
◦ HP-UX 11i v1 bound processors are shown only when the HP-UX 11i v1 virtual partition
is in an “up” state.
◦ The vparstatus command run from an HP-UX 11i v1 virtual partition reports an HP-UX
11i v1 virtual partition's bound and float CPUs in legacy format.
The vparstatus command run from an HP-UX 11i v1 virtual partition reports that an
HP-UX 11i v2 virtual partition's monarch CPU is “bound” and all other CPUs are shown
as unbound (floater).
• 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 vPars environment.
Mixed HP-UX 11i v1/v2 vPars Environments in vPars A.04.05 57