From Wiki-UX.info

How to update vPar from 11.23 to 11.31?
Jump to: navigation, search

How to update vPar from 11.23 to 11.31?

Note: Editing to be continued.

Before the update it is a good idea to set a depot server, which will be holding the HPUX 11.31 DVD images.

Follow the instructions to create a network depot from the following link: [1]

Prior to updating your system, you must install a supported version of the update-ux command from the Operating Environment DVDs.

Mount the DVD onto the new directory as a file system. For example:

mount /dev/dsk/c1t2d0 /dvdrom

Using swinstall, install the latest version of the Update-UX bundle on the target system.

NOTE: Make sure you use the correct case to install the Update-UX bundle (in title case). This bundle contains the update-ux command (lowercase).

swinstall -s /dvdrom Update-UX
swinstall -s depot_server:/var/11iv3/update-depot Update-UX

Once you have install the latest Update-UX on all vpars, follow these steps to update your vpars from 11.23 to 11.31.

This section describes how to update an existing A.04.xx vPars on 11iv2 (11.23) environment to a vPars A.05.xx vPars environment on 11iv3 (11.31).

The Update Process: Goal


In the example below, we begin with three virtual partitions, all running vPars A.04.01:

the first partition keira1 running vPars A.04.01 (on 11.23)

the second partition keira2 running vPars A.04.01 (on 11.23)

the third partition keira3 running vPars A.04.01 (on 11.23)

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.

We wish to update to the following:

keira1 running A.05.01 (on 11.31)

keira2 running A.05.01 (on 11.31)

keira3 running A.05.01 (on 11.31)

The Update Process


To update vPars from A.04.xx to A.05.xx, follow the process below. 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. The update process sets autoboot to manual, so you will need to restore 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


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/1131/HPUX11i-OE-Ent.DVD Update-UX keira2 # swinstall -s depot1:/release/1131/HPUX11i-OE-Ent.DVD Update-UX keira3 # swinstall -s depot1:/release/1131/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.

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/1131/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335CC keira3 # update-ux -s depot1:/release/1131/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335CC



NOTE: Be sure that both the OE and vPars bundles are specified on the update-ux command line.

When using Update-UX to update vPars, you must update in this manner, in which case you are updating both the OS and vPars version with the same 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.

Use the update-ux command.

Example:


keira1 # update-ux -s depot1:/release/1131/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335CC


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. 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, if you wish to have the alternate boot disk up dated, 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/1131/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335CC




Reboot the nPartition to ISL> or EFI.

Use the reboot command from the vPars Monitor.

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. 

 

If needed (depending upon how your nPartition’s autoboot configuration is set up), interrupt the nPartition boot process and load the vPars Monitor.

The command sequences for loading the vPars Monitor differ on the BCH (on PA-RISC) and EFI Shell (on HP Integrity) interfaces.

Example for PA-RISC:


BCH> bo pri interact with IPL: y ISL> hpux /stand/vpmon


Example for Integrity: Shell> fs0: fs0:\> hpux HPUX> boot vpmon


Boot the virtual partitions.

Use the vparload -all vPars Monitor command.

Example:


MON> vparload -all


When the virtual partitions are booted, they will continue and complete their update processes (the virtual partitions can be booed in any order). 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.

Use the vparmodify command.

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 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.31 Up




NOTE: 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. To convert the base memory to float memory, see “Memory: Converting Base Memory to Float Memory”.

Authors

This page was last modified on 5 May 2009, at 01:23. This page has been accessed 1,921 times.