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

11. Turn autoboot and autosearch settings back to their original settings that you recorded earlier
above.
Example:
keira1 # vparmodify -p keira1 -B auto
keira1 # vparmodify -p keira1 -B nosearch
keira1 # vparmodify -p keira2 -B manual
keira1 # vparmodify -p keira2 -B nosearch
keira1 # vparmodify -p keira3 -B auto
keira1 # vparmodify -p keira3 -B nosearch
12. Verify the Virtual Partitions.
The virtual partitions should now be running the latest vPars version. To verify this, you can
login to each virtual partition and use the vparstatus command with the -P option:
Example:
keira1# vparstatus -P
Current Virtual Partition Version: A.05.01
Monitor Version: A.05.01
[Virtual Partition OS Version]
Virtual Partition Name OS Version State
============================ ========== =====
keira1 B.11.31 Up
keira2 B.11.23 Up
keira2# vparstatus -P
Commands product information: A.04.03
Monitor product information: A.05.01
13. Verification the vPars Monitor.
If you changed the nPartition’s PRI boot path, you can also verify that the vPars Monitor has
been booted from the correct boot disk:
keira3# vparstatus -m
Console path: No path as console is virtual
Monitor boot disk path: 0.0.6.0.0.5.0
Monitor boot filename: /stand/vpmon
Database filename: /stand/vpdb
...
The boot disk path shown is from a vPars A.05.01 virtual partition.
14. Convert base memory to float memory.
vPars A.04.xx uses only base memory; therefore, when updating to vPars A.05.xx from
A.04.xx, all memory will be converted as base memory. There is no method to convert the
memory to float during the update process. For information base and float memory, see
“Definitions for Dynamically Migrating ILM or CLM Memory ” (page 177).
To convert the base memory to float memory, see “Memory: Converting Base Memory to Float
Memory” (page 184).
Mixing Minor Versions – vPar A.04.xx and A.05.xx
Virtual Partitions can be used at different Operating Environment (OE) levels. This section describes
the supported configurations and guidelines for operating mixed HP-UX versions environment.
Virtual partitions support mixing different minor release of vPars. The mixed minor versions feature
increases the flexibility of using vPar software for the following reasons:
• It is not necessary to upgrade all vPars simultaneously. This makes it easier to perform OE
upgrades.
• It might not be necessary to reboot the vPar Monitor after an upgrade. There are conditions
where a lower version Monitor is able to support a higher version vPar.
Mixing Minor Versions – vPar A.04.xx and A.05.xx 103