LVM/VxVM and vPars sx2000 Upgrade

3
INTRODUCTION
This document describes the necessary HP-UX operating system configuration changes required during the upgrade from the HP Integrity
Superdome/sx1000 to the HP Integrity Superdome/sx2000. This document covers the upgrade products listed below:
 HP Integrity Superdome/sx1000 to the HP Integrity Superdome/sx2000.
This hardware upgrade will change existing hardware paths due to the PCI-X 2.0 chassis upgrade included with these servers. The
hardware path changes are detailed in Table 1 on the next page.
CAUTIONS
 Read and understand this document in its entirety before performing any of these upgrades. Failure to understand and follow
these instructions can result in an unbootable system after the upgrade hardware has been installed.
 The server model string will change after the hardware has been upgraded. Therefore, if Veritas software is running on the
server, a new license must be obtained from Veritas before performing the hardware upgrade.
 During this upgrade, all the cells in the HP Integrity Superdome complex must be upgraded at the same time.
 The I/O cards must be moved to the exact same slot number in the PCI-X 2.0 chassis
 The Core I/O used in the HP Integrity Superdome/sx1000 is not supported in the HP Integrity Superdome/sx2000 so must not
be moved into the upgraded PCI-X 2.0 chassis.
 The X.25 adapter J3526A is not supported on HP IntegritySuperdome/sx2000 Superdome, so you must remove those cards
before proceeding with your HP Integrity Superdome/sx1000 upgrade.
NOTES
 The upgrade to PCI-X 2.0 is mandatory for the sx2000 Integrity Superdome. The previous PCI and PCI-X chassis are
incompatible with the HP Integrity Superdome/sx2000.
 This document does not cover the procedure for nPartitions running non-HP-UX operating systems.
 For vPars to run on the sx2000 chipset, you must update all virtual partitions to vPars A.04.02 or later before performing the
upgrade. For information on how to upgrade to the latest version of vPars, see Chapter 4 of the manual Installing and
Managing HP-UX Virtual Partitions.
GENERAL UPGRADE INFORMATION
Because of the hardware paths changes, you must follow the steps described below to ensure that the multiple OS instances running on
the HP Integrity Superdome complex can be rebooted. If these steps are not followed, one or more operating systems may not reboot and
recovery of HP-UX could be difficult or even impossible. If HP-UX cannot be recovered, it will be necessary to reload from a customer
backup or HP-UX install media.
If the customer agrees, an alternative to the following steps is to reload HP-UX for all the OS instances running on the complex after the
upgrade hardware is installed. The HP-UX reload process will create all new kernel hardware paths and device files and will generally
take longer to perform than the recommended steps. In addition, the reload will resolve the root volume group path changes, but any
other volume group(s) will still have to be recovered (via vgimport).
If the procedure described below is chosen, the customer should still be fully prepared to reload HP-UX in case problems occur during this
process. Therefore, a full system backup must be done before the hardware upgrade is performed.
TERMS AND DEFINITIONS
The first virtual partition is defined as the virtual partition from which the vPars Monitor boots.