 |
» |
|
|
|
This section describes how to update an existing
A.04.xx vPars environment to a mixed HP-UX 11i v2/v3 vPars environment;
a mixed HP-UX 11i v2/v3 vPars environment contains both vPars A.04.xx/11.23
and A.05.xx/11.31 virtual partitions in the same nPartition. For information
on using a mixed HP-UX 11i v2/v3 vPars environment, see “Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx”. For information
on the typical time needed to update the OS version, see the HP-UX 11i v3 Installation and Update Guide. For information on vPars and OS versions, see
the HP-UX Virtual Partitions Ordering and Configuration
Guide. 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 any of the following: Update-UX Primer | |
The advantages of using Update-UX 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. After the latest Update-UX bundle has been installed,
you can use the update-ux command, the 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/1131/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335CC |
where depot1:/release/1131/HPUX11i-OE-Ent.DVD is the source depot HPUX11i-OE-Ent is the OE
bundle T1335CC is the vPars A.05.xx
bundle
Since both the OE and vPars bundle are
the parameters for update-ux, both the OE (including the OS version)
and the vPars version are updated in this single step.
OE Bundle Names for Update-UXFor HP-UX 11i v3, the possible OE bundles are: - HPUX11i-OE
Foundation OE - HPUX11i-OE-Ent
Enterprise OE - HPUX11i-OE-MC
Mission Critical OE
When choosing the OE, you should select the same
OE that your 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.31 HP-UX Enterprise Operating Environment |
This shows that you are running an Enterprise OE. vPars Bundle Names for Update-UXFor vPars, the possible vPars bundles are: - T1335CC
vPars A.05.xx bundle - T1335BC
vPars A.04.xx bundle
Note that in a mixed HP-UX 11i v2/v3 vPars environment,
the vPars running A.04.xx must be running version A.04.02 or later.
Therefore, the “Revision” field in the depot should
be A.04.02 or greater. Using swlist, we can find
the revision number for the vPars A.04.xx bundle on the depot. # swlist -d @ depot1:/release/1123/HPUX11i-OE-Ent.DVD | grep T1335BC
T1335BC A.04.02.03 HP-UX Virtual Partitions for 11.23 |
Changing nPartition Boot Paths To Boot the vPars A.05.xx Monitor | |
To boot a mixed HP-UX 11i v2/v3 vPars environment,
you must boot a vPars A.05.xx Monitor. In our example below, entitled The Update Process, we are updating the first virtual
partition (the virtual partition from which the vPars Monitor is booted)
from vPars A.04.01 to A.05.01. However, if we had chosen to update
that partition to only vPars A.04.02, we must change the nPartition’s
PRI (primary) boot path so that it points to the boot disk of a vPars
A.05.01 virtual partition, which would contain a vPars A.05.xx Monitor. For example, if we originally had this configuration:
- nPartition’s PRI boot path is:
boot disk of thurman1 - thurman1
vPars A.04.01 with vPars A.04.01 Monitor - thurman2
vPars A.04.01 with vPars A.04.01 Monitor
but wanted to update to the following configuration: - thurman1
vPars A.04.02 with vPars A.04.02 Monitor - thurman2
vPars A.05.01 with vPars A.05.01 Monitor
we must change the nPartition’s PRI boot
path to point to the boot disk of a vPars A.05.01 boot disk, which
contains a vPars A.05.01 Monitor, such that - nPartition’s PRI boot path is:
boot disk of thurman2 - thurman1
vPars A.04.02 with vPars A.04.02 Monitor - thurman2
vPars A.05.01 with vPars A.05.01 Monitor
Note that to change the nPartition’s PRI
boot path, you cannot use setboot from within a virtual partition; using setboot within a virtual
partition changes only the virtual partition’s primary path
entry in the vPars database. Further, you cannot use parmodify from
within vPars on Integrity systems. However, if you are unfamiliar with the firmware
interfaces on PA or Integrity, you can boot the system into standalone/nPars
mode, use parmodify or setboot to change the nPar boot path, and then boot back into vPars mode.
This is included in the steps below. 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.04.02 (on
11.23) keira3 running A.05.01 (on
11.31)
The Update Process: Step by Step | |
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 |
| | | |  | TIP: In our example, we are updating all the virtual partitions.
However, if you have virtual partitions that already meet the mixed/OS
vPars requirements (vPars A.04.02 or later) and are not updating those
virtual partitions, you can skip the update steps for these partitions. | | | | |
Install the latest and OS-applicable 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 where target OS will be 11.31: keira1 # swinstall -s depot1:/release/1131/HPUX11i-OE-Ent.DVD Update-UX
keira3 # swinstall -s depot1:/release/1131/HPUX11i-OE-Ent.DVD Update-UX |
Example where target OS will be 11.23: keira2 # swinstall -s depot1:/release/1123/HPUX11i-OE-Ent.DVD Update-UX |
Determine if you need to change the PRI boot path
and perform accordingly. If the current nPartition’s
PRI boot path currently points to a virtual partition that will be
updated to only A.04.xx and not A.05.01, you will need to change the
nPartition’s PRI boot path such that it points to the boot
disk of a virtual partition that will be updated to A.05.01. For more
information, see “Changing nPartition Boot Paths To Boot the vPars A.05.xx Monitor”. Example: In our example, the first virtual partition keira1 is being
updated to vPars A.05.01, so we would not need to change the nPartition
PRI boot path and can proceed to the next step. However, if keira1 is being updated to only A.04.02, then we
would need to change the nPartition’s PRI boot path to the
boot disk of a virtual partition that is being updated to A.05.01.
To do this, perform the following: Find the nPartition partition number for the current
nPartition. keira1# parstatus -w
The local partition number is 0. |
The nPartition number is 0. Record
this information. Find the boot path of the boot disk of a future vPars
A.05.01 virtual partition. This boot path will become the nPartition’s
new PRI boot path. Since keira3 is being updated to A.05.01,
let’s chose to change the nPartition’s PRI path to the
boot disk of keira3. Since we have chosen keira3 as the future A.05.01 virtual partition,
we need to find the boot path of keira3: keira1# vparstatus -v -p keira3
...
[IO Details]
0.0.6
0.0.6.0.0.5.0 BOOT |
The BOOT attribute identifies the boot
path for the virtual partition keira3 as 0.0.6.0.0.5.0. Record this information. Set the mode for the next nPartition reboot. on Integrity, set the mode to nPars for the next reboot: # vparenv -m nPars on PA, no mode setting is required.
The remainder of the steps to change the PRI boot path will
be done later, while in nPars/standalone mode. 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. Example where target OS will be
11.31, which implies vPars A.05.xx: keira3 # update-ux -s depot1:/release/1131/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335CC |
Example where target OS will be 11.23, which implies vPars A.04.xx: keira2 # update-ux -s depot1:/release/1123/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335BC |
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/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 updated, 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/1123/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335BC |
| | | | |
Reboot the nPartition. Example: On Integrity, if you need to change the PRI boot path, reboot
in nPars mode: | | | | | 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. | | | | |
If you need to change the PRI boot path, follow the
procedure below. Otherwise, proceed to the next step. Interrupt the boot up process and enter into standalone
(PA) or nPars (Integrity) mode. Example for PA-RISC: BCH> bo pri
interact with IPL: y
ISL> hpux /stand/vmunix |
Example for Integrity: Shell> fs0:
fs0:\> hpux
HPUX> boot vmunix |
Change the nPartition’s PRI path to the boot
path of the future A.05.01 partition recorded earlier. Example: keira# parmodify -p0 -b 0.0.6.0.0.5.0 |
where the syntax of parmodify is Verify the new PRI path using parstatus. keira# parstatus -p0 -V
[Partition]
Partition Number : 0
Partition Name : npar0
Status : active
IP address : 0.0.0.0
PrimaryBoot Path : 0/0/6/0/0.5.0
... |
Once the PRI path has been successfully changed, set
the mode to back to vPars. On PA-RISC, no mode setting is required.
Reboot the nPartition.
If needed (depending upon how your nPartition’s
autoboot configuration is set up), interrupt the nPartition boot process
and load the vPars Monitor. 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. Example: 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. 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 |
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 |
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. 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 ”. To convert the base memory to float memory, see “Memory: Converting Base Memory to Float Memory”.
|
Printable version
