Updating from vPars A.03.xx to Mixed HP-UX 11i v1/v2 vPars (A.03.05 and A.04.05) Environment

This section describes how to update an existing vPars A.03.xx environment to a mixed HP-UX 11i v1/v2 vPars environment. A mixed HP-UX 11i v1/v2 vPars environment contains both vPars A.03.05/11.11 and A.04.05/11.23 virtual partitions in the same nPartition.

If you wish to upgrade to a mixed HP-UX 11i v1/v2/v3 vPars environment (vPars A.03.xx, vPars A.04.xx, and vPars A.05.xx in the same nPartition), see “Migrating from vPars A.03.xx to Mixed HP-UX 11i v1/v2/v3 vPars (A.03.05, A.04.02 or later, A.05.03)”.




	CAUTION: Designated-Admin Feature and Mixed HP-UX 11i v1/v2 vPars Environments In a mixed HP-UX 11i v1/v2 environment, configure only virtual partitions containing vPars A.04.05 as designated-admin virtual partitions. Within a mixed HP-UX 11i v1/v2 vPars environment, only the virtual partitions containing vPars A.04.05 can modify other virtual partitions via the vparmodify command, and only virtual partitions containing vPars A.04.05 can use vparcreate and vparremove to create and remove other virtual partitions. If you use the designated-admin feature and configure only virtual partitions containing vPars A.03.05 as designated-admin virtual partitions, no virtual partition will be able to modify other virtual partitions.




	NOTE: In a mixed HP-UX 11i v1/v2 vPars environment, all HP-UX 11i v1 virtual partitions must be updated to vPars A.03.05, and all HP-UX 11i v2 vPars must be updated to vPars A.04.05.

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

For information on vPars and HP-UX versions, see the HP-UX Virtual Partitions Ordering and Configuration Guide.

For information on using a mixed HP-UX 11i v1/v2 vPars environment, see “Mixed HP-UX 11i v1/v2 vPars Environments in vPars A.04.05”.

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 sections:

Overview of the Mixed HP-UX 11i v1/v2 vPars Environment Update Process

This section provides a high-level overview of the process for updating from a vPars A.03.xx environment to a mixed HP-UX 11i v1/v2 vPars environment. For details and examples of the update process see “The Update Process for Mixed HP-UX 11i v1/v2 vPars Environments: Step by Step Details”.

Figure 4-1 shows an overview of the update process for migrating an HP-UX 11i v1 vPars environment to a mixed HP-UX 11i v1/v2 vPars environment. For details see High-Level Description of the Mixed HP-UX 11i v1/v2 vPars Environment Update Process and “The Update Process for Mixed HP-UX 11i v1/v2 vPars Environments: Step by Step Details”.

Figure 4-1 Overview of Update Process for Mixed HP-UX 11i v1/v2 vPars Environment

High-Level Description of the Mixed HP-UX 11i v1/v2 vPars Environment Update Process The following list gives a high-level description of the process shown in Figure 4-1. After backing up all virtual partitions and establishing a depot with the required HP-UX OE and vPars versions, the steps are as follows. For details and examples see “The Update Process for Mixed HP-UX 11i v1/v2 vPars Environments: Step by Step Details”.

Make sure that all the virtual partitions are up.
Record the current autoboot and autosearch settings of all the virtual partitions.
Change the autoboot setting to manual for all virtual partitions.
This step is critical, to avoid automatically rebooting into the wrong vPars Monitor.
Disable (undeploy) gWLM if it is in use.
Determine if it will be necessary to change the PRI boot path for the nPartition and record the path details.
1. Find the nPartition partition number and the PRI boot path for the current nPartition.
2. Find the boot path of the boot disk of a future vPars A.04.05 virtual partition.
If it is necessary to change the PRI boot path for the nPartition, do so now using the parmodify command from HP-UX running on any of the virtual partitions.
Because the vPars Monitor is loaded from the first virtual partition (whose disk is specified by the PRI path), the PRI disk must be installed with vPars A.04.05.
Install the latest and OS-applicable Update-UX bundle onto each virtual partition that will be updating the HP-UX Operating Environment—including all virtual partitions updating to HP-UX 11i v2 and vPars A.04.05.
For each virtual partition that is updating to HP-UX 11i v2 and vPars A.04.05, use Update-UX to install the latest OE and vPars bundle.
The updated virtual partitions must not be rebooted at this point—keep the systems halted while other virtual partitions are being updated. Rebooting to the new vPars Monitor occurs later, after all virtual partitions have completed the software loading phase and have halted.
Install iCAP v8.03 on all HP-UX 11i v1 virtual partitions updating to vPars A.03.05.
iCAP v8.03 is required before installing vPars A.03.05.
Determine whether to update the remaining virtual partitions in parallel (concurrently with the HP-UX 11i v2 and vPars A.04.05 updates) or stagger the remaining updates (wait for the HP-UX 11i v2 and vPars A.04.05 updates to complete).
Update the remaining virtual partitions to vPars A.03.05.
The update steps will depend on whether you do a parallel update or a staggered update.
- If updating all virtual partitions in parallel, then perform the following steps.
  On all remaining virtual partitions:
  If the OE must also be updated, use Update-UX to install the latest OE and the vPars A.03.05 bundle to the virtual partition.
  If only the vPars bundle needs to be updated, use swinstall to install vPars A.03.05.
  Wait for the vPars A.03.05 updates to complete.
  Monitor the installation logs (such as the /var/adm/sw/swagent.log file or swinstall.log file) until the virtual partitions halt.
- If updating in a staggered manner, then perform the following steps
  Wait for the HP-UX 11i v2 and vPars A.04.05 updates to complete.
  After the vPars A.04.05 updates complete, update all but one of the remaining virtual partitions to vPars A.03.05.
  Wait for the vPars A.03.05 update to complete on all but the last virtual partition.
  Monitor the installation logs (such as the /var/adm/sw/swagent.log file or swinstall.log file) until the virtual partitions halt.
  On the last virtual partition, update the HP-UX Operating Environment, if needed, and update the vPars bundle.
Make sure that all virtual partition updates have successfully completed to the point of halting, then reboot the nPartition (reboot from the vPars Monitor).
Interrupt the nPartition boot process as needed and load the vPars A.04.05 Monitor.
Boot all virtual partitions (vparload -all from the vPars Monitor).
Turn autoboot and autosearch settings back to their original settings that you recorded previously.
Verify the virtual partition configurations.
Verify the correct vPars Monitor has been booted.
Restart gWLM if needed.

Following the mixed HP-UX 11i v1/v2 vPars update, perform any application updates as needed.

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.




	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` If you are unfamiliar with the Update-UX product or would like information on using or debugging Update-UX, read the HP-UX 11.11 or 11.23 Installation and Update Guide. Also, see the applicable Software Distributor and Ignite-UX documents available at http://docs.hp.com.

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 other_bundles

For example, the command line used in this section is:

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

where:

depot1:/release/1123/HPUX11i-OE-Ent.DVD is the source depot
HPUX11i-OE-Ent is the OE bundle
T1335BC is the vPars A.04.xx bundle

Because 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.




	NOTE: Before performing the update, you should verify that all of the target virtual partitions meet the HP-UX 11.23 requirements as documented in the HP-UX 11.23 Read Before Installing or Updating document. One example of a possible issue is file system size. The update-ux command will ensure that there is sufficient space before allowing an update: `/usr`: 400000 kbytes free `/opt`: 1300000 kbytes free `/`: 200000 kbytes free `/stand`: 80000 kbytes total, and 49595 kbytes free `/var`: 900000 kbytes free For details see also the HP-UX 11i v2 Installation and Update Guide.

OE Bundle Names for Update-UX

For HP-UX 11i v2, 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 the virtual partition is running is currently running:

# swlist -l bundle | grep -i OE
HPUX11i-OE-MC         B.11.11.0612   HP-UX Mission Critical Operating Environment Component

This shows the virtual partition is running a Mission Critical OE.

vPars Bundle Names for Update-UX

For vPars, the possible vPars bundles are:

T1335AC: vPars A.03.xx bundle
T1335BC: vPars A.04.xx bundle

In a mixed HP-UX 11i v1/v2 vPars environment, the virtual partitions running A.03.xx must be running version A.03.05 or later. Therefore, the “Revision” field in the depot should be A.03.05 or greater. Using swlist, we can find the revision number for the vPars A.03.xx bundle on the depot.

# swlist -d @ depot1:/release/1111/HPUX11i-OE-Ent.DVD | grep T1335AC
T1335AC       A.03.05.02     HP-UX Virtual Partitions

Likewise, in a mixed HP-UX 11i v1/v2 vPars environment, the virtual partitions running A.04.xx must be running version A.04.05 or later. Therefore, the “Revision” field in the depot should be A.04.05 or greater. Use the swlist command to find the revision number for the vPars A.04.xx bundle on the depot.

Changing nPartition Boot Paths To Boot the vPars A.04.xx Monitor




	CAUTION: To boot a mixed HP-UX 11i v1/v2 vPars environment, you must boot a vPars A.04.05 or later vPars Monitor.




	NOTE: 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. You can use parmodify to change the nPartition boot path, or you can make the change at the Boot Console Handler (BCH) PA-RISC firmware interface. Using parmodify to change the nPartition PRI boot path to point to a vPars A.04.05 boot disk is the method used in “Overview of the Mixed HP-UX 11i v1/v2 vPars Environment Update Process” and “The Update Process for Mixed HP-UX 11i v1/v2 vPars Environments: Step by Step Details”.

You can configure boot options for an nPartition by using the /usr/sbin/parmodify command from the HP-UX command line in any virtual partition in the nPartition.

The format for changing nPartition boot paths using parmodify is as follows:

parmodify -p partitionNumber [-b priPath] [-t haaPath] [-s altPath]

where:

partitionNumber is the nPartition to be modified. You can use the parstatus -w command to list the local nPartition number.
priPath is the primary boot path (PRI on HP 9000 servers, or the first item in the boot options list on HP Integrity servers).
haaPath is the secondary boot path (the HAA boot path on HP 9000 servers, or the second item in the boot options list on HP Integrity servers).
altPath is the alternate boot path (ALT on HP 9000 servers, or the third item in the boot options list on HP Integrity servers).

The Update Process for Mixed HP-UX 11i v1/v2 vPars Environments: Step by Step Details

This section describes how to update a vPars A.03.xx environment to a mixed HP-UX 11i v1/v2 vPars environment running vPars A.03.05 and A.04.05.

The Update Process: Goal In the examples used in this section, we begin with three virtual partitions, all running vPars A.03.02:

The first partition, azure1, is running vPars A.03.02 (on 11.11).
The second partition, azure2, is running vPars A.03.02 (on 11.11).
The third partition, azure3, is running vPars A.03.02 (on 11.11).

We wish to update to the following:

azure1 running vPars A.04.05 (on 11.23).
azure2 running vPars A.03.05 (on 11.11).
azure3 running vPars A.04.05 (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. When upgrading to a mixed HP-UX 11i v1/v2 vPars environment, the first virtual partition must have vPars A.04.05 installed.

Procedure 4-2 Update Process for Mixed HP-UX 11i v1/v2 vPars Environments

The following steps should be done from the vPars console after backing up all virtual partitions and establishing a depot with the required HP-UX OE and vPars versions.

Make sure that all the virtual partitions are up.

You can check this with the vparstatus command.

azure1# vparstatus
[Virtual Partition]
                                                                          Boot
Virtual Partition Name         State Attributes   Kernel Path             Opts
============================== ===== ============ ======================= =====
azure1                         Up    Dyn,Auto,Nsr /stand/vmunix
azure2                         Up    Dyn,Manl,Nsr /stand/vmunix
azure3                         Up    Dyn,Auto,Nsr /stand/vmunix

Record the current autoboot and autosearch settings of all the virtual partitions.

You will need to restore these settings later. To find the current settings, use vparstatus.

azure1 # vparstatus
[Virtual Partition]
                                                                          Boot
Virtual Partition Name         State Attributes   Kernel Path             Opts
============================== ===== ============ ======================= =====
azure1                         Up    Dyn,Auto,Nsr /stand/vmunix
azure2                         Up    Dyn,Manl,Nsr /stand/vmunix
azure3                         Up    Dyn,Auto,Nsr /stand/vmunix

Auto indicates autoboot is set, Manl indicates manual boot is set, and Nsr indicates “no search”.




	TIP: In this example, we are updating all the virtual partitions. However, if you have virtual partitions that already meet the mixed HP-UX 11i v1/v2 vPars requirements (vPars A.03.05 or later) and are not updating those virtual partitions, you can skip the update steps for those virtual partitions.

Change the autoboot setting to manual for all virtual partitions.
Use the vparmodify -p vparname -B manual command, where vparname is the name of the virtual partition.
This step must be performed to avoid automatically rebooting into the wrong vPars Monitor.
If gWLM is in use, disable (undeploy) gWLM’s management of resources in all virtual partitions.
gWLM is supported with restrictions in mixed HP-UX 11i v1/v2 vPars environments, as of the first release of vPars A.03.05 and vPars A.04.05. For details on gWLM restrictions, see “Features of Mixed HP-UX 11i v1/v2 vPars Environments”.
For details on how to disable gWLM, see Getting Started with HP Integrity Essentials Global Workload Manager and reference the “Stop Managing an SRD” (shared resource domain) procedure.
Determine if you need to change the PRI boot path and record the necessary boot path details.
If the current nPartition’s PRI boot path currently points to a virtual partition that will be updated to only A.03.05 and not A.04.05, 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.04.05.
For more information, see “Changing nPartition Boot Paths To Boot the vPars A.04.xx Monitor”.
In this example, the first virtual partition azure1 is being updated to vPars A.04.05, so we would not need to change the nPartition PRI boot path and can proceed to the next step. However, if azure1 were being updated to only A.03.05, 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 vPars A.04.05.
To record the necessary boot path details, perform the following steps:
1. Find and record the nPartition number for the current nPartition.
  Use the parstatus -w command from any virtual partition.
  azure1# parstatus -w The local partition number is 0.
  In this example, the nPartition number is 0. Record this information.
2. Find the boot path of the boot disk of a future vPars A.04.05 virtual partition. This boot path will become the nPartition’s new PRI boot path.
  Use the vparstatus -v -p vparname command from any virtual partition.
  In the following example, we find the boot path of azure3, which is being updated to vPars A.04.05 and thus could serve as the first virtual partition (the one that owns the boot disk from which the vPars Monitor is booted).
  azure1# vparstatus -v -p azure3 ... [IO Details] 0.0.6 0.0.6.0.0.5.0 BOOT
  The BOOT attribute identifies the boot path for the virtual partition azure3 as 0.0.6.0.0.5.0. Record this information.
The next step changes the PRI boot path for the nPartition.
If you need to change the PRI boot path for the nPartition, follow the procedure below. Otherwise, proceed to the next step.
The nPartition’s PRI boot path must point to the boot disk of a vPars A.04.05 virtual partition.
Use the parmodify command from HP-UX running on any of the virtual partitions in the nPartition to change the nPartition PRI boot path.
parmodify -p partitionNumber -b priPath
where partitionNumber is the nPartition number recorded earlier, and priPath is the boot path, selected earlier, of a virtual partition that will have vPars A.04.05 installed.
TIP: The parmodify command requires major path components to be separated with a slash (/). For example, 0.0.6.0.0.5.0 would be specified as 0/0/6/0/0.5.0 when using parmodify.
Install the latest and OS-applicable Update-UX bundle onto each virtual partition that will be updating the HP-UX Operating Environment—including all virtual partitions updating to HP-UX 11i v2 and vPars A.04.05.
This does not update the operating system, only the Update-UX bundle.
Use Ctrl-A to switch between consoles.
To list the current Update-UX bundle, use the swlist command. For example:
azure2 # swlist -l product | grep Update
If necessary to update the Update-UX bundle, use the swinstall command.
Example where target OS will be HP-UX 11.23
azure1 # swinstall -s depot1:/release/1123/HPUX11i-OE-Ent.DVD Update-UX Ctrl-A azure3 # swinstall -s depot1:/release/1123/HPUX11i-OE-Ent.DVD Update-UX
Example where target OS will be HP-UX 11.11
azure2 # swinstall -s depot1:/release/1111/HPUX11i-OE-Ent.DVD Update-UX

Use Update-UX to install the latest OE and vPars bundle on each virtual partition that is updating to HP-UX 11i v2 and vPars A.04.05




	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.

In the following example the target OS will be HP-UX 11.23 (the HPUX11i-OE-Ent Enterprise OE bundle) and vPars will be updated to vPars A.04.05 (the T1335BC bundle).

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




	NOTE: The update virtual partitions must not be rebooted at this point. Once the update completes, keep the systems halted while other virtual partitions are being updated.

Install iCAP v8.03 on all HP-UX 11i v1 virtual partitions that are updating to vPars A.03.05.

iCAP v8.03 must be installed before vPars A.03.05 is installed. For details see the HP Instant Capacity User's Guide for Versions 8.x.




	NOTE: If you are updating to vPars A.03.05, or configuring a mixed 11i v1/v2 vPars environment, you must install iCAP version 8.03 (B.11.11.08.03.00) on each HP-UX 11i v1 virtual partition. This will also install the required versions of WBEM and NParProvider and necessary patches. Installing iCAP 8.03 onto an HP-UX 11i v1 system running versions of vPars prior to A.03.05 will exhibit an error message which can be ignored, and you can proceed with updating the vPars software. After the vPars installation (which includes halting every virtual partition and rebooting the nPartition to the new vPars A.04.05 Monitor), you must go to each HP-UX 11i v1 virtual partition and run the command swconfig -v B9073BA to complete the iCAP installation.

Decide whether to perform the remaining updates in parallel or to stagger the updates.
Updating in parallel involves updating concurrently with the HP-UX 11i v2 and vPars A.04.05 updates. A parallel update of the virtual partitions can reduce the total downtime resulting from the updates.
Staggering updates involves waiting for the HP-UX 11i v2 and vPars A.04.05 updates to complete before updating virtual partitions to vPars A.03.05. A staggered approach to updating enables you to better monitor the update process from the last virtual partition before it is updated.
Update the remaining virtual partitions to vPars A.03.05.
How you perform the remaining updates will depend on whether you are doing parallel or staggered updates.
1. If updating all virtual partitions in parallel then perform the following steps.
  1. On all remaining virtual partitions:
    - If the HP-UX Operating Environment must also be updated, use Update-UX to install the latest OE and the vPars A.03.05 bundle to the virtual partition.
      In the following example the target OS will be HP-UX 11.11 (the HPUX11i-OE-Ent Enterprise OE bundle) and vPars will be updated to vPars A.03.05 (the T1335AC bundle).
      azure2 # update-ux -s depot1:/release/1111/HPUX11i-OE-Ent.DVD HPUX11i-OE-Ent T1335AC
    - If only the vPars bundle needs to be updated, use the swinstall command to install vPars A.03.05.
      In the following example vPars will be updated to vPars A.03.05 (the T1335AC bundle).
      azure2 # swinstall -s depot1:/release/1111/VirtualPartitions T1335AC
  2. Wait for the vPars A.03.05 update process to complete.
    Monitor the installation logs until the virtual partitions halt.
    To monitor the log files, first login to the virtual partition being updated (for example, use telnet) and then use the tail -f command to view the current installation status being written to the /var/adm/sw/swagent.log file or swinstall.log file.
2. If updating virtual partitions in a staggered manner, then perform the following steps.
  1. Wait for the HP-UX 11i v2 and vPars A.04.05 updates to complete.
  2. After the vPars A.04.05 updates complete, update all but one of the remaining virtual partitions to vPars A.03.05.
    If possible, select a virtual partition that requires only vPars A.03.05 (and not also an OE update) to be the “last virtual partition”, which will be the last one to be updated and will be used to monitor progress of the other virtual partition updates.
    On all virtual partitions except the last virtual partition:
    - If the OE must also be updated, use Update-UX to install the latest OE and the vPars bundle to the virtual partition.
    - If only the vPars bundle needs to be updated, use swinstall to install vPars A.03.05.
  3. Wait for the vPars A.03.05 updates to complete on all but the last virtual partition.
    Monitor the installation logs until the virtual partitions halt.
    To monitor the log files, first login to the virtual partition being updated (for example, use telnet) and then use the tail -f command to view the current installation status being written to the /var/adm/sw/swagent.log file or swinstall.log file.
  4. On the last virtual partition, update the HP-UX Operating Environment, if needed, and update the vPars bundle.
    - If the OE must also be updated, use Update-UX to install the latest OE and the vPars bundle to the virtual partition.
    - If only the vPars bundle needs to be updated, use swinstall to install vPars A.03.05.
    - On the last virtual partition, wait for the vPars A.03.05 update to complete.
      Monitor the installation progress until the virtual partitions halt.
      To monitor the log files, first login to the virtual partition being updated (for example, use telnet) and then use the tail -f command to view the current installation status being written to the /var/adm/sw/swagent.log file or swinstall.log file.
Make sure that all virtual partition updates have successfully completed to the point of halting, then reboot the nPartition.
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.
Load the vPars Monitor.
The need to do this depends upon how your nPartition’s autoboot configuration is set up (that is, whether /stand/vmunix or /stand/vpmon is loaded by default).
BCH> bo pri interact with IPL: y ISL> hpux /stand/vpmon
Boot the virtual partitions.
MON> vparload -all
When the virtual partitions are booted, they will continue and complete their update processes (the virtual partitions can be booted 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 previously.

azure1 # vparmodify -p azure1  -B auto
azure1 # vparmodify -p azure1  -B nosearch
azure1 # vparmodify -p azure2  -B manual 
azure1 # vparmodify -p azure2  -B nosearch
azure1 # vparmodify -p azure3  -B auto 
azure1 # vparmodify -p azure3  -B nosearch

Verify the virtual partition configurations.

To confirm the state of the system you can use various commands (vparstatus, bdf, lvlnboot, swverify) and log files (/var/adm/sw/swagent.log or swinstall.log).

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.

azure1# vparstatus -P
Current Virtual Partition Version:  A.04.05
Monitor Version:  A.04.05

[Virtual Partition OS Version]
Virtual Partition Name       OS Version State
============================ ========== =====
azure1                         B.11.23    Up
azure2                         B.11.11    Up
azure3                         B.11.23    Up

azure2# vparstatus -P
Current Virtual Partition Version:  A.03.05
Monitor Version:  A.04.05

[Virtual Partition OS Version]
Virtual Partition Name       OS Version State
============================ ========== =====
azure1                         B.11.23    Up
azure2                         B.11.11    Up
azure3                         B.11.23    Up

azure3# vparstatus -P
Current Virtual Partition Version:  A.04.05
Monitor Version:  A.04.05

[Virtual Partition OS Version]
Virtual Partition Name       OS Version State
============================ ========== =====
azure1                         B.11.23    Up
azure2                         B.11.11    Up
azure3                         B.11.23    Up

Verify the correct vPars Monitor has been booted.
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:
azure3# 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.04.05 virtual partition.
Restart gWLM if needed.
If you disabled (undeployed) gWLM earlier in the update process, you can restart it now.
gWLM is supported with restrictions in mixed HP-UX 11i v1/v2 vPars environments. For details on these gWLM restrictions, see “Features of Mixed HP-UX 11i v1/v2 vPars Environments”.

Following the mixed HP-UX 11i v1/v2 vPars update process, update any applications as needed.




	IMPORTANT: If you have installed iCAP version 8.03 during the update process, on each HP-UX 11i v1 virtual partition you must run the command swconfig -v B9073BA to complete the iCAP installation.

Updating from vPars A.03.xx to Mixed HP-UX 11i v1/v2 vPars (A.03.05 and A.04.05) Environment

Technical documentation

» Table of Contents

» Glossary