HP-UX Update Requirements

Update and Upgrade Paths

You can use the SD-UX tools to update your OS to a later version of HP-UX, from 10.01, 10.10, 10.20, or 10.30. For upgrades to 10.x from 9.0x, see the manual Upgrading from HP-UX 9.x to 10.01. You can also use SD-UX to install or update applications.

Required Kernels

The 32-bit kernel can execute on any Server or Workstation supported on 11.0, except the V2200 Server.
The 64-bit kernel executes only on certain Servers. The V2200 requires the use of the 64-bit kernel.
Not all PA8x00 CPU-equipped systems are supported for 64-bit operation, even though all PA8x00 CPUs are 64-bit capable.

Supported Workstations:

At release 11.0, the following 32-bit systems are supported (for 64-bit server information, see “Updating to HP-UX 11.0”, in this chapter):

Series 700: 712, 715/64, 715/80, 715/100, 715/100XC, 743, 744, 725/100

B-Class: B132L, B160L

C-Class: C100, C110, C160, C160L, C180

J-Class: All J-Class systems

Unsupported Workstations

Workstations not supported are the following:

705, 710, 715/33, 715/50, 715/75, 720, 725/50, 725/75, 730,735, 755

Workstations not supported due to required 100BaseT driver are the following:B132L+, B180L C200, C240

Supported Servers

The following summarizes the HP 9000 Server implementations:

32-Bit Only: D, E, G, H, and I-class, K-class (PA7x00), T500, and T520.
32/64-Bit: K-class (PA8x00), and T600,
64-Bit Only:V2200

NFS Diskless

Updating a cluster server to HP-UX 10.30 or later is not supported. NFS Diskless functionality is not supported in HP-UX 10.30 or later. Do not update your server to HP-UX 11.0 if you intend for that server to operate as an NFS Diskless server.

For the latest information on system support, consult your HP sales engineer.

Fiber Link and HPIB

HP-UX 11.0 does not support HPIB, or Fiber Link disks or controller cards. If you are using this hardware, you should first copy the data from the device(s), and then disconnect it from your system before updating to 11.0. Failure to do this will not cause a data loss, panic, or other catastrophic problem, but will result in not being able to access the data on those devices. Updating before copying the data will render the data inaccessible, except by reinstalling the earlier release.

Memory and Disk Space Requirements

RAM: HP-UX 10.x, including NFS, LAN/9000, and CDE, requires 32 MB of RAM. For HP-UX 11.0, a minimum of 32 MB of RAM is required, and 64 MB is recommended.
Before you begin the update, you should be sure your target disk has the space needed to accommodate the new OS as well as your data files and all needed backups on disk. You should plan on a minimum disk size of one GB for a general workstation. Disk usage numbers will vary by a factor of 20%, depending on the installation.
- File System Increments: Compared to HP-UX 10.20, updating HP-UX to 11.0 (including NFS, LAN/9000, CDE, and the X Window System), requires the following additional file system size for a 32-bit update:
  /usr: 120 MB additional.
  /var: 5 MB additional.
  /opt: 55 MB additional.
  Since some of these increases may cause the default file system size and freespace to be exceeded, see“Adjusting File System Size ”, in Chapter 7 “Troubleshooting ” for the procedure for making adjustments.




	NOTE: In general, the Disk Space Analysis phase of `swinstall` will warn you if disk space is insufficient. However, Disk Space Analysis does not currently check `/var/adm/sw`, where the database is kept, for temporary space usage. If you are running your system as LVM and `/var` comprises a single volume, be sure you have configured adequate space in the `/var` volume to accommodate the update files. An update requires a minimum amount of free disk space of at least 20 MB to allow for the generation of the installed software database, among other things. The disk space analysis will help you determine the needed volume sizes.

Preparing the Disks

Determine your free disk space in /var by running bdf /var and bdf /var/tmp. The default temporary directory is /var/tmp.
Delete any files in this volume that you don't need.
If necessary, set the environment variable TMPDIR to point to a directory that has sufficient space. For example (for a directory dir):
export TMPDIR=/dir
After setting and exporting this variable, kill and restart the swagentd process.
/usr/sbin/swagentd -r
Ensure that your system has at least 30 MB of swap enabled before starting the update process. You can use swapinfo -mt and check the total free MB of swap space. Or you can use SAM to see how much swap you currently have. If you do not have enough swap, you can enable file system swap for the duration of the update (until system reboot) by using the following command:
/usr/sbin/swapon /var/tmp
The directory /var/tmp can be used if there is sufficient free space. If /var/tmp is full, then specify a different volume that has enough free space to satisfy the swap space requirement.
Alternatively, you can shut down unneeded programs to make more memory and swap space available. This also improves performance.
Before updating, you may wish to use /usr/sbin/swremove to remove unneeded filesets from your system.

For More Information on Space Requirements

Refer to the current System Administration Tasks manual and the Release Notes for HP-UX 10.x for additional information on peripherals and disk space.

Source Media

The general names applied to the HP-UX source media are as follows:

CD-ROMs Used

CORE
Applications.
Support.
HP-UX Extension Software (Includes essential patches).




	NOTE: If you are updating any networking products, such as FDDI or Token-Ring, which are not on the HP-UX Runtime CORE CD, please see “Networking Products on Additional Media”, in this chapter.

Mounting the Source Media

Note that your multi-user license is typically supplied on separate media.
Ensure that you have made a backup tape of your present system.
Ensure that your system is booted and running HP-UX 10.x. You should have a term window opened.
Turn on the CD-ROM drive, if it is external to your HP-UX 10.x system.
Insert the CD-ROM into its drive.
Wait for the busy lights to stop blinking.
If necessary, identify the drive device, using the following command:
/etc/ioscan -fn
If you are using a single local CD-ROM, note that swinstall will automatically mount the disk in the drive. Otherwise, you may have to first mount the disc, using SAM or the mount(1M) command. If you do not use SAM, you can do the following to mount the disc:
1. Put the CD into the CD-ROM drive. CD-ROM "busy light" should blink.
2. Open a term window and, at the shell prompt, type the following:
  mkdir /SD_CDROM Enter mount /dev/dsk/c1t2d0 /SD_CDROM Enter
  The device name "c1t2d0" should be replaced with whatever device name you found using ioscan in item 7 above.