Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Virtual Partitions Administrator’s Guide > Chapter 4 Installing, Updating, or Removing vPars and Upgrading Servers with vPars

Updating from vPars (A.02.xx or A.03.xx) to A.03.xx

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

To update from an earlier vPars A.02.xx or A.03.xx version to the latest vPars A.03.xx version, perform the following steps.

NOTE: If updating to the vPars A.03.05 release, use the “Updating vPars A.03.xx to vPars A.03.05” procedure.
  1. Save a copy of the vPars database in case you need to revert back to the earlier version of vPars or you need to restore the database.

  2. Shut down all the virtual partitions.

  3. Reboot the server into standalone mode. This consists of the following:

    1. At the MON> prompt, type reboot

    2. If needed, interrupt the boot sequence at the BCH> prompt and boot /stand/vmunix instead of /stand/vpmon. For example:

      BCH> bo pri interact with IPL? y . . . ISL> hpux /stand/vmunix
  4. Install the new vPars bundle using swinstall. For the appropriate bundle name, see “Bundle Names”.

  5. Reboot the system:

    # shutdown -r

  6. Boot the vPars Monitor and the virtual partitions from the disk where you installed the vPars bundle. For example, if we had installed the bundle to the disk at the primary path:

    BCH> bo pri interact with IPL? y . . . ISL> hpux /stand/vpmon -a

    If you have configured your AUTO file in the LIF area to boot the vPars Monitor and virtual partitions automatically, then this step will be performed automatically. For more information, see “Autoboot”.

  7. On each virtual partition, repeat Step 4 to install the new vPars bundle on each boot disk of each virtual partition (you do not need to reboot the hard partition). Because the boot disk used to boot in standalone mode in Step 3 already has the new vPars bundle (this was installed during Step 4), you can exclude this step for the boot disk at the primary path.

    You must install the new vPars bundle on each virtual partition before putting the virtual partitions back into production. Running a mix of older and newer vPars versions within a group of virtual partitions is not supported.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2008 Hewlett-Packard Development Company, L.P.