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

• In HP-UX 11iv2 environment, except for vPars A.04.07 no other vPar versions support the
mixed minor version feature.
• In a mixed minor environment running HP-UX 11iv2 with vPar A.04.07, the booted monitor
must always be a 11i v3 vPar monitor. This is because a 11i v2 vPar monitor is not enabled
to provide all the functionality required by a HP-UX 11iv3 vPar environment.
Updating from vPars A.03.xx to A.05.xx
At the time of this publication, updating directly from vPars A.03.xx to A.05.xx is not supported
because the Update-UX tool does not support updating directly from 11i v1 (11.11) to 11i v3
(11.31). However, as a general workaround, you can attempt the following process. However,
there are many differences not only between vPars A.03.xx and A.05.xx, but also between 11.11
and 11.31. Be sure to read the applicable release notes for your given hardware (server, cards,
and expansion units), operating system, and vPars software. If you need help, contact your HP
Support Representative.
Note that there is no update software process to move from PA to Integrity servers.
General Process for A.03.xx to A.05.xx Workaround (PA only)
The general process for updating from A.03.xx to A.05.xx is to perform the update in two steps:
1. Update your virtual partitions from A.03.xx to A.04.02 or later.
“Updating from vPars A.03.xx to A.04.xx” (page 105)
2. Update your virtual partitions from A.04.02 or later to A.05.01
“Updating from vPars A.04.xx to A.05.xx” (page 78)
“Updating from vPars A.04.xx to Mixed HP-UX 11i v2/v3 vPars (A.04.xx and A.05.xx)
Environment” (page 96)
Updating from vPars A.03.xx to A.04.xx
This section describes how to update an existing A.03.xx PA-RISC vPars environment to the latest
A.04.xx PA-RISC vPars environment. The advantages of using this process are 1) you can update
both OE and vPars versions simultaneously, so there are fewer reboots, and 2) although you must
still reboot the nPartition, you can perform these steps within a vPars environment; you do not need
to boot the system into standalone mode. However, if you are not familiar with Update-UX, you
can continue to use the swinstall methods (see the links in the next paragraph).
Note that this process works only using Update-UX and a corresponding Ignite-UX depot; it does
not work by directly using the OE and vPars media. If you wish to install directly from media, you
should use the instructions from “Installing vPars with Ignite-UX on PA-RISC” (page 116) or “Installing
vPars with Software Distributor ” (page 120).
Updating from vPars A.03.xx to A.05.xx 105