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 11i Version 1 Installation and Update Guide: HP Servers and Workstations > Chapter 2 Choosing a Migration Path: Cold Install or Update

Deciding Which Method to Use
» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

spacerspacerspacer
spacer
spacer
  		 
 

Now that you have evaluated your system and ordered any additional needed hardware, you need to decide whether to cold-install HP-UX 11i v1 on your system or update it.

Cold-install means installing system software on a new (un-installed) or existing system disks by completely rebuilding the volume group (see “Back up Your System!”), erasing the existing operating system and data on that volume and installing the new operating system and specified software and data. An advantage of cold-install is that supported software can be installed without regard for the software currently on the system, or concern for cleaning up old software.

Update means using the update-ux command and Software Distributor (SD) tools to selectively overwrite the operating system and application software from a media or network source depot. An advantage of performing an update is that it leaves user data, configuration, and applications in place. Updating to HP-UX 11i v1 requires that the system be running at 10.20 or 11.0, with or without extension or Additional Core Enhancement (ACE) packs installed.

CAUTION: If the Distributed File System (DFS) is installed and in use on your HP-UX 10.20 system to manage large numbers of files, update-ux will remove it and associated data during the update to HP-UX 11i v1. If you need to continue using DFS, do not update to HP-UX 11.x or HP-UX 11i v1.

Depending on your system’s current configuration, here are some general guidelines to help you choose the best migration path to HP-UX 11i v1.

Cold Install When...

We recommend using Ignite-UX to cold-install HP-UX 11i v1 in the following situations:

  • You are managing several systems with similar OS configurations.

  • You need fast, predictable deployment.

  • Your disk space needs to be reconfigured. See “Planning Your Disk Space Needs”.

  • Your systems are organized with clean separation of the OS from user, application and data files.

You can cold-install from any supported HP-UX OS. (See Table 3-1 “Supported Systems”.)

The cold-install process using Ignite-UX is described in Chapter 5 “Cold Installing HP-UX 11i v1”. “Preparing to Cold-Install Your System” for more information.

Update When...

You can update rather than cold-install HP-UX 11i v1 when you are updating from HP-UX 10.20 or 11.0 as well as the following:

  • You are only updating a few (1-3) systems to HP-UX 11i v1.

  • You are concerned about recovering unique applications and data on your root volume, and do not want to write over non-OS files when installing HP-UX 11i v1.

  • Each system has a unique configuration.

  • Current disk space is sufficient for HP-UX 11i v1 (see “Planning Your Disk Space Needs”).

    IMPORTANT: If /stand is not of sufficient size, the partition can be resized, requiring the root disk to be reformatted. In this case, you must cold-install rather than update your system. To determine if /stand is large enough to support this release of HP-UX 11i v1, see “Disk Space and Memory Requirements”.
NOTE: update-ux removes all HP-UX 10.x patches from the system prior to updating to HP-UX 11i v1. Any 10.x applications left on the system after the update may not be supportable if they required those patches. After migrating your system, consult the documentation for those remaining applications for HP-UX 11i v1 requirements.

If your system meets these requirements, follow the update procedure in Chapter 6 “Updating to HP-UX 11i v1”. “Preparing to Update Your Existing System” for more information about preparing to update your system.

Considerations for Cold-install and Update

Firmware Patches Should Not Be Included In Cold-Install or Update Session

If you are migrating from either HP-UX 10.20 or HP-UX 11.0, HP strongly recommends you do not include firmware patches while running a cold-install or update session.

How Do You Know If This Affects You?

The following systems are affected:

  • A-Class

  • L-Class

  • N-Class

Many of the HP-UX 11i v1 firmware patches rely on HP-UX 11i v1 tools and system calls. The cold-install or update process uses a subset of existing commands and system calls. The firmware installation fails because of system call differences between the HP-UX 11i v1 operating system and the install session version.

What To Do:

HP strongly recommends that you install any firmware patches after you have completed the cold-install or update process and your system is running HP-UX 11i v1. Specific HP-UX 11i v1 firmware patches are available at the following website:

http://itresourcecenter.hp.com

Updating Network Drivers

Installing or updating to HP-UX 11i v1 will install a minimum set of default networking drivers that apply to the system (see “HP-UX 11i v1 Always-Installed Network Drivers”). You may need to select or specify other available networking drivers to enable other cards on your system (see “HP-UX 11i v1 Selectable Network Drivers”). This can easily be done during install or update by following the instructions for your selected migration path.

Installing or Updating HP-UX Web Server Suite

If your system already is running any version of the HP Apache-based Web Server, installing or updating to an HP-UX 11i v1 Operating Environment will install the version of HP-UX Web Server Suite included with the HP-UX 11i v1 OE. See the HP-UX 11i v1 Release Notes for more information about the HP-UX Web Server Suite: HP-UX Apache-based web server, HP-UX Tomcat-based Servlet Engine, HP-UX Webmin-based Admin, HP-UX XML Web Server Tools.

Installing or Updating Netscape Directory Server

Although the Netscape Directory Server (NDS) Version 6.02 is included in HP-UX 11i v1 OEs, you must explicitly select NDS during the install or update process. If you do not select NDS, it will not be installed with HP-UX 11i v1. For more on this, see “Updating Netscape Directory Server”.

CAUTION: If you have NDS version B.02.00.05 and are updating to HP-UX 11i v1, be sure to either select the new version of NDS during the update or remove the old version from your system. If you run NDS version B.02.00.05 with HP-UX 11i v1, the server will cease to work and all client systems may lose the ability to have anyone log in.
NOTE: Currently, Netscape Directory Server Version 6.02 is not included with the HP-UX 11i v1 Operating Environments. If you wish to have the iPlanet 5.0 product, order the AR1202 CD or DVD for this product separately.

After NDS is installed or updated with HP-UX 11i v1, additional configuration steps are required to initiate NDS. See the NDS release notes available on the HP-UX 11i v1 Instant Information CD for instructions.

HP 3D Graphics No Longer Supported Pre-PA-RISC 2.0 Systems

As of the September 2002 HP-UX 11i v1 release, HP 3D Graphics are no longer supported on PA-RISC systems older than version 2.0. If you have an older PA-RISC workstation and need 3D Graphics, HP recommends that you do not install or update to this release of the Technical Computing (TCOE) or Minimal Computing Operating Environments (MCOE).

Previous releases of HP-UX 11i v1 still support PA-RISC 2.0 and older systems. If you have any questions about your particular situation, please contact your local HP Country Response Center.

How to Determine Your PA-RISC Version. With the System Administration Manager (SAM), select: Performance Monitors > System Properties. Your PA-RISC version will appear next to the CPU Version line.

Small Memory Systems (<1GB/CPU) May Need to Configure VxFS 3.5 Tunables after Install/Update

If you have a system with less than 1GB/CPU of RAM, and you plan to use VxFS 3.5, you may need to modify some of the default VxFS tunables for optimal performance after you install or update your system to HP-UX 11i v1. For more information, see Appendix E “Controlling Memory Utilization of VxFS 3.5 on HP-UX 11i v1”.

Update Considerations

The following sections provide additional information to assist you in your decision to update to HP-UX 11i v1:

Update May Fail if Latest Version of Update-UX is Not Installed

If your updating from the June 2003 HP-UX 11i v1 release or earlier, you must install the latest version of Update-UX™ prior to updating your system if your system has one of the following DCE Client IPv6 patches installed:

  • PHSS_24261

  • PHSS_25473

  • PHSS_25710

  • PHSS_26394

  • PHSS_27258

To determine if any of these patches are installed on your system, enter the following command:

/usr/sbin/swlist -l patch | grep <patch_name>

If any of these patches appear in standard output, you have the patch installed and need to install the latest version of Update-UX before starting the update process.

See “Step 1: Install the update-ux Command (Required Task!)” describes the steps required to install the latest version of Update-UX.

VxVM Rootability Not Enabled with update-ux

With the September 2002 release of HP-UX 11i v1, you can not enable VxVM rootability through the update process using update-ux. If you wish to manage your root volume with VxVM, you can choose to either enable rootability by:

  • cold-installing HP-UX 11i v1, see “Using VxVM Rootability”

  • using the VxVM conversion tools provided in the Base-VXVM and FEATURE11-11 bundles that are installed with HP-UX 11i v1 (for more information about HP-UX 11i v1 software bundles, see “What is Installed with HP-UX 11i v1?”). For more information, see the VERITAS Volume Manager 3.5 Release Notes and VERITAS Volume Manager 3.5 Administrator’s Guide on the Instant Information CD

Updating to 64-bit OS

update-ux defaults to the OS word-width that your system is currently running. For example, if the target system is running 32-bit OS, this will be the default for the new OS to be installed.

NOTE: Changing an existing 64-bit OS to 32-bit is not supported. To return a 64-bit OS to 32-bit, use the Ignite-UX make_tape_recovery or make_net_recovery command to restore the 32-bit OS.

You can update a system from 32-bit OS to 64-bit OS while updating to HP-UX 11i v1, provided that you consider these hardware and firmware issues:

  • Is your system capable of running 64-bit operation? See Table 3-1 “Supported Systems” in Chapter 3 “Installing and Updating System Requirements”.

  • Is your system’s firmware recent enough to support 64-bit operation? See “Firmware Requirements” in Chapter 3 “Installing and Updating System Requirements”.

  • 64-bit binary data cannot be used by 32-bit applications. 64-bit is useful if you need large address space, such as for use with very large databases and large-scale modeling. 64-bit applications can be compiled and linked on 32-bit systems; however, these applications cannot be run on a 32-bit system.

  • If updating an existing HP-UX 11i v1 system from 32-bit to 64-bit OS, do not include the HP-UX 11i v1 Quality Pack (GOLDQPK11i) bundle in the update-ux command. Doing so may cause a mk_kernel failure. Instead, install the GOLDQPK11i bundle from the Support Plus CD using swinstall after updating to this release.

  • If updating an HP-UX 10.20 system with the CDE Spanish language keyboard enabled: After updating from HP-UX 10.20 to HP-UX 11i v1, changing from 32-bit to 64-bit OS and installing the HP-UX 11i v1 Quality Pack (GOLDQPK11i) bundle, you must install patch PHSS_23644 (or superseding patch PHSS_23818) from the GOLDBASE11i quality pack bundles on the latest Support Plus CD to re-enable the CDE Spanish language keyboard. Obtain this patch from the HP IT Resource Center (http://itrc.hp.com). This problem does not occur with other languages.

  • If updating an existing HP-UX 11i v1 system having any of the following EISA network drivers installed, you must remove all EISA drivers before updating from 32-bit to 64-bit OS:

    • 100BaseT-00 — EISA 100BaseT

    • FDDI-03 — EISA FDDI

    • TermIO-01 — EISA MUX

    • TokenRing-02 — EISA Token Ring

    (New drivers installed by default are listed in “HP-UX 11i v1 Always-Installed Network Drivers”. Other drivers can be specified in the update-ux command or installed later using swinstall.)

    To determine if any EISA drivers are installed on the system, use swlist. For example:

    /usr/sbin/swlist -l bundle 100BaseT-00 FDDI-03 \
    TermIO-01 TokenRing-02

    If any EISA drivers are on the system, remove them. For example, to remove the TermIO-01 EISA MUX driver, as root enter:

    /usr/sbin/swremove -x autoreboot=true TermIO-01

    The kernel will automatically regenerate and the system will reboot after you remove each driver. After removing all EISA drivers, proceed to update as explained below.

If you're updating from HP-UX version 11.0 or higher, update-ux will determine if your hardware and firmware are compatible with 64-bit operation. If you're updating from HP-UX version 10.20, however, refer to the Software Transition Kit available on the HP-UX Applications media. The STK contains tools and documents to assess applications or libraries that run on HP-UX 10.20 and 11.0 and help transition them to the HP-UX 11i v1 64-bit operation. The ITRC web site (http://www.itresourcecenter.hp.com/) also has release notes and a FAQ with details about supported systems and necessary firmware updates.

Cold-Install Considerations

The following sections provide additional information to assist you in your decision to cold-install HP-UX 11i v1:

Using VxVM Rootability

Ignite-UX now provides you the option to install and configure VxVM 3.5 on your root volume. If you plan to configure your root volume with VxVM 3.5, make sure you read the supporting VxVM 3.5 documentation included on the Instant Information CD. For additional information, see “VxVM Rootability”.

Cold-Installing on Partitioned Systems

HP-UX must be installed on the boot disk assigned to each partition after the partition has been configured. Configuring the boot disk is explained in the HP System Partitions Guide manual, available on the HP-UX 11i v1 Instant Information CD and on HP’s user documentation web site:

http://docs.hp.com

Once each partition has been configured for installation, follow the cold-installation instruction on the following pages to install HP-UX on each partition’s boot disk.

Instant Ignition

For customers ordering new systems with the “Instant Ignition” option (also known as “factory integrated”), the cold-installation process described here has already been performed. Skip this chapter and proceed to install application software.

Alternate Cold-Install Methods

In addition to the procedures described in this chapter, you can cold-install your system using the following methods:

Installing From Software Depots

Use Software Distributor commands to create depots containing OS, OE, and other software bundles, then install from the depot using Ignite-UX. For help with this method, see the swinstall(1M) manpage and Software Distributor Administration Guide and Ignite-UX Administration Guide.

Installing from Golden Images

If you need to install the same OS/OE and applications on many systems in your network, use an Ignite-UX server as explained in the Ignite-UX Administration Guide. With Ignite-UX, you can create a single install image (golden image) containing OS/OE bundles, application bundles and patch bundles, then install the image on multiple systems in your environment.



Migrating from Previous HP-UX Releases
  		 


If You Have an Existing HP-UX 11i v1 System  
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© Hewlett-Packard Development Company, L.P.