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” or “Installing vPars with Software Distributor ”.

For information on the typical time needed to update the OS version, see the HP-UX 11i v2 Installation and Update Guide.




	CAUTION: Using Update-UX Update-UX allows for both the OE and vPars bundles to be updated in the same session. To simultaneously update both the OE and vPars bundles in the same session, they both must be in the same source depot. If you update from a depot which does not contain the vPars bundle, your disk will no longer boot in vPars mode. See the Ignite-UX Administration Guide and Using Golden Images with Virtual Partitions for information on how to setup your Ignite-UX server.




	NOTE: Before using the Update-UX command, make sure you have the latest Update-UX bundle installed for each virtual partition: `# swinstall -s source_depot Update-UX`

In the example below, the Update-UX command syntax is

# update-ux -s source_depot OE_bundle vPars_bundle

For example, the command line used in this section is

# update-ux -s depot1:/release/0505.1123/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335BC

where:

depot1:/release/0505.1123/HPUX11i-OE-Ent.DVD is the source depot
HPUX11i-OE-Ent is the OE bundle
T1335BC is the vPars bundle

For more information on using Update-UX, see the HP-UX 11.23 Installation and Update Guide.

The Steps

The following steps should be done from the console:

Make sure that all the virtual partitions are up. You can check this with vparstatus.

Example:

keira1# vparstatus
[Virtual Partition]
                                                                          Boot
Virtual Partition Name         State Attributes   Kernel Path             Opts
============================== ===== ============ ======================= =====
keira1                         Up    Dyn,Auto,Nsr /stand/vmunix
keira2                         Up    Dyn,Manl,Nsr /stand/vmunix
keira3                         Up    Dyn,Auto,Nsr /stand/vmunix

Record the current autoboot and autosearch settings of all the virtual partitions so that you can change back to these settings later. To find the current settings, use vparstatus.

Example:

keira1 # vparstatus
[Virtual Partition]
                                                                          Boot
Virtual Partition Name         State Attributes   Kernel Path             Opts
============================== ===== ============ ======================= =====
keira1                         Up    Dyn,Auto,Nsr /stand/vmunix
keira2                         Up    Dyn,Manl,Nsr /stand/vmunix
keira3                         Up    Dyn,Auto,Nsr /stand/vmunix

Turn autoboot and autosearch settings off using vparmodify for all the virtual partitions.

Example:

keira1 # vparmodify -p keira1  -B manual
keira1 # vparmodify -p keira1  -B nosearch
keira1 # vparmodify -p keira2  -B manual 
keira1 # vparmodify -p keira2  -B nosearch
keira1 # vparmodify -p keira3  -B manual 
keira1 # vparmodify -p keira3  -B nosearch

Note that the -B nosearch option is valid for only vPars A.03.02 and later. If you are using an earlier version of vPars, you can skip thevparmodify ... -B nosearch command.

Install the latest Update-UX bundle onto each virtual partition (use Ctrl-A to switch between consoles).

Note that this does not update the operating system, only the Update-UX bundle. Example:

keira1 # swinstall -s depot1:/release/0505.1123/HPUX11i-OE-Ent.DVD Update-UX
keira2 # swinstall -s depot1:/release/0505.1123/HPUX11i-OE-Ent.DVD Update-UX 
keira3 # swinstall -s depot1:/release/0505.1123/HPUX11i-OE-Ent.DVD Update-UX

For each virtual partition, except the first virtual partition, use Update-UX to install the latest OE and vPars bundle. These updates can occur in parallel, although this is not required.
The first virtual partition is defined as the virtual partition that owns the boot disk from which the vPars Monitor was booted; you can use the vparstatus -m and vparstatus -v commands to determine which virtual partition this is.
Although you can update all the virtual partitions, including the first virtual partition, in parallel, by leaving the first virtual partition up until all the updates for the other virtual partitions are complete, it allows you to use the first virtual partition to verify the processing and status of the other virtual partitions.
Example:
keira2 # update-ux -s depot1:/release/0505.1123/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335BC keira3 # update-ux -s depot1:/release/0505.1123/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335BC
Bundle Names
- For HP-UX 11i v2, the possible OE bundles are listed below.
  HPUX11i-OE
  Foundation OE
  HPUX11i-OE-Ent
  Enterprise OE
  HPUX11i-OE-MC
  Mission Critical OE
  You should chose the same OE that your current virtual partition is running. Use the swlist command to check which OE you are currently running:
  # swlist -l bundle | grep -i OE HPUX11i-OE-Ent B.11.23.0505 HP-UX Enterprise Operating Environment
- T1335BC is the vPars A.04.xx bundle.
NOTE: Be sure that both the OE and vPars bundles are specified on the update-ux command line.

After the all updates for the above virtual partitions have completed, use Update-UX to install the latest OE and vPars bundle to the first virtual partition.

Example:

keira1 # update-ux -s depot1:/release/0505.1123/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335BC

Although you can do all the updates in parallel, you need to make sure that all of the other virtual partition updates have successfully performed the updating to the point of halting for reboot. In the next step, the entire nPartition will be rebooted; if the other virtual partitions are still in progress of updating, the OS instances may be in an unknown state.

NOTE: If the BOOT and ALTBOOT disks are a mirrored pair, updating is not required on the ALTBOOT disk. Otherwise, after updating the OS on the primary boot path disk, boot the virtual partitions from the alternate path boot disk and repeat the update-ux procedure. For example, if keira2 has an alternate boot disk that is not a mirror of the primary boot disk, and you wish to update the OS on the alternate boot disk, boot keira2 from the alternate boot path using:

MON> vparload -p keira2 -B ALT

and repeat the update-ux procedure

keira2# update-ux -s depot1:/release/0505.1123/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335BC

Reboot the nPartition to the ISL> prompt.
Example:
MON> reboot
NOTE: At this point, you need to reboot the nPartition from the MON> prompt, not just the virtual partition. By rebooting the nPartition, you can load the new vPars Monitor in the next step.
From ISL> load the vPars Monitor.
Example:
ISL> hpux /stand/vpmon
Boot the virtual partitions.
Example:
MON> vparload -all
When the virtual partitions are booted, they will continue and complete their update processes. After this is completed, you should arrive at the login: prompt for each virtual partition. Login as root and continue to the next step.

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

The virtual partitions should now be running the latest OE and vPars version.

Updating from vPars A.03.xx to A.04.xx

Technical documentation

» Table of Contents

» Glossary

» Index

The Steps