HP-UX 11i Installation and Update Guide

HP-UX 11i Installation and Update GuideHP 9000 ComputersImportant: Review the Read Before Installing or Updating to HP-UX 11i booklet accompanying HP-UX 11i OE CDs before installing or updating to 11i. .

Manufacturing Part Number: 5971-2215 Edition 2, June 2001 Printed in U.S.A.

Legal NoticesThe information in this document is subject to change without notice. Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and tness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental or consequential damages in connection with the furnishing, performance, or use of this material. Warranty. A copy of the specic warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Ofce. Restricted Rights Legend. Use, duplication or disclosure by the U.S. Government is subject to restrictions as set forth in sub-paragraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013. Rights for non-DOD U.S. Government Departments and Agencies are as set forth in FAR 52.227-19(c)(1,2). Hewlett-Packard Company 3000 Hanover Street Palo Alto, CA 94304 U.S.A. Copyright Notices. Copyright 1983-2001 Hewlett-Packard Company, all rights reserved. Reproduction, adaptation, or translation of this document without prior written permission is prohibited, except as allowed under the copyright laws. Copyright 1979, 1980, 1983, 1985-93 Regents of the University of California This software is based in part on the Fourth Berkeley Software Distribution under license from the Regents of the University of California. Copyright 1980, 1984, 1986 Novell, Inc. Copyright 1986-1992 Sun Microsystems, Inc. Copyright 1985, 1986, 1988 Massachusetts Institute of Technology Copyright 1989-1993, The Open Software Foundation, Inc. Copyright 1986 Digital Equipment Corp. Copyright 1990 Motorola, Inc. Copyright 1990, 1991, 1992 Cornell University Copyright 1989-1991 The University of Maryland Copyright 1988 Carnegie Mellon University Copyright 1991-2000 Mentat Inc. Copyright 1996 Morning Star Technologies, Inc. Copyright 1996 Progressive Systems, Inc. Copyright 1991-2000 Isogon Corporation, All Rights Reserved

2

Trademark Notices. UNIX is a registered trademark in the United States and other countries, licensed exclusively through The Open Group. X Window System is a trademark of the Massachusetts Institute of Technology. MS-DOS and Microsoft are U.S. registered trademarks of Microsoft Corporation. OSF/Motif is a trademark of the Open Software Foundation, Inc. in the U.S. and other countries. Revision History: December 2000, Edition 1 Initial version for HP-UX 11i. June 2001 Edition 2. This guides printing date and part number indicate its current edition. The printing date changes when a new edition is printed. (Minor corrections and updates which are incorporated at reprint do not cause the date to change.) The part number changes when extensive technical changes are incorporated. New editions of this manual will incorporate all material updated since the previous edition. For the latest version, see the HP-UX 11i documentation section on the Web: docs.hp.com/hpux/os/11i/ Please direct comments regarding this guide to: Hewlett-Packard Company HP-UX Learning Products, MS 11 3404 East Harmony Road Fort Collins, Colorado 80528-9599 Or, use this Web form to send us feedback directly: docs.hp.com/assistance/feedback.html

3

About this GuideThis guide describes installing HP-UX 11i on HP 9000 systems and assumes that you are the systems administrator familiar with installing, updating and maintaining software on the system. If you need to set up your system in different languages, please refer also to Conguring HP-UX For Different Languages, available on the Instant Information CD and on the Web: docs.hp.com A localized version of that manual is available with localized media kits. Latest versions are available at: docs.hp.com (select: localized documentation). This guide uses these typographic conventions: Boldface Computer User input Words dened for the rst time appear in boldface. Computer font indicates literal items displayed by the computer. For example: file not found Bold, computer text indicates literal items that you type. For example, to change to your accounts home directory, enter: cd Italics Manual titles, variable in commands and emphasized words appear in italics. For example, you would substitute an actual directory name for directory_name in this command: cd directory_name [ ] and | Brackets [] enclose optional items in command syntax. The vertical bar | separates syntax items in a list of choices. For example, you can enter any of these three items in this syntax: ls [-a | -i | -x]Enter

Text in this bold, sans-serif font denotes keyboard keys and on-screen menu items. A notation like Ctrl-Q indicates that you should hold the Ctrl key down and press Q.

4

Contents

1. Preparing for Software Migration Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Identifying Model, OS and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 Migrating from Previous HP-UX Releases. . . . . . . . . . . . . . . . . . . . . . . .17 Firmware Upgrades. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Updating Your Ignite-UX Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24 Installing Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 Needing More Disk Space? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26 Selecting the Path to HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Collect Key Install Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Back Up Your System!. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33 Save Conguration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35 Locate Source Media for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36 2. Migrating to HP-UX 11i Cold-installing HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40 Installing HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41 After Cold-installing HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45 Retrieving Information After Cold-installing . . . . . . . . . . . . . . . . . . . .46 Updating HP-UX 10.20/11.0 to 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48 Updating Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Procedure A: Install update-ux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 Procedure B: Create a Network Depot (optional) . . . . . . . . . . . . . . . . .54 Procedure C: Update to HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . .56

5

Contents

Updating an Existing 11i System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Updating to . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64-bit OS63 Changing Individual OE Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Changing Operating Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Updating Netscape Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Installing ServiceGuard Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 3. Verifying System Migration Verifying HP-UX Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Verifying Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 4. Updating Applications HP-UX Patching Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Updating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Adding and Removing Individual Patches . . . . . . . . . . . . . . . . . . . . . . . 81 Using Software Distributor Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Updating LicensePower/iFOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 Maintaining Your HP-UX 11i System . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 A. Booting HP 9000 Systems Halting the Autoboot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Booting Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 Booting HP 9000 Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 Booting V-Class Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Searching for Other Bootable Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . 97

6

Contents

B. In Case of Trouble Cold-install Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100 Common Update Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101 Analyzing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108 Problems Conguring HP-UX 11i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Intermittent Sendmail Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .117 Adjusting File System Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .118 Problems with Large Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122 Un-installing HP-UX 11i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .123 Re-installing SD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124 Recovering a Corrupt System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .125 Verifying and Adding Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .126 Problems Affecting non-C Locales . . . . . . . . . . . . . . . . . . . . . . . . . . . . .127 Web Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .129 C. Conguring Built-In PCI Networking Compatibility and Installation Requirements . . . . . . . . . . . . . . . . . . . .132 Conguring Network Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133 Manual Speed and Duplex Mode Conguration . . . . . . . . . . . . . . . . . .136 Setting Speed and Duplex Mode at Boot Time (workstation only) . .138 Autonegotiation and Auto-sensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .139 RJ-45 and AUI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .140 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .141 What Happens During Card Initialization Sequence? . . . . . . . . . . . . .143

7

Contents

V-Class PCI 10/100Base-TX Card Specications . . . . . . . . . . . . . . . . . 144 Hardware Regulatory Statements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 FCC Statement (For U.S.A.) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Canada. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

8

Preparing for Software Migration

1

Preparing for Software MigrationThis chapter will help you assess the current state of your system (hardware, OS, disk space, etc.) prior to migrating to HP-UX 11i. Topics covered here include: Introducing HP-UX 11i Media kit contents, new features, operating environments and overview of the migration process. System requirements HP 9000 systems supported by HP-UX 11i. Firmware upgrades Some systems require a rmware upgrade to support 11i releases. Installing diagnostics Be sure to install the support tools. Disk space, memory and diagnostic requirements Situations that may apply to your system. Selecting the path to 11i Look at your system state to decide whether to cold-install or update to HP-UX 11i. Collect key install information Youll need this information when cold-installing HP-UX 11i. Back up your system! Save conguration les so you can restore them after cold-installing. Prepare source media for migration.

Chapter 1

9

Preparing for Software Migration Introduction

IntroductionThis guide describes migrating HP 9000 systems to HP-UX 11i. This new version of HP-UX delivers hardware enablement, software functionality, and bundles of important HP-UX applications in Operating Environments. HP-UX 11i Operating Environments (OEs) are introduced in the Read Before Installing or Updating to HP-UX 11i booklet supplied with the HP-UX 11i OE CDs. HP-UX 11i is the recommended next-level enterprise release for all HP-UX systems currently running HP-UX 10.x and 11.0. This manual deals only with the software steps required to update your HP-UX operating system. For hardware upgrades, either see the documentation included with your hardware or consult your HP Support Engineer.

IMPORTANT

Be sure to review this entire guide before proceeding to install or update your system. If you plan to update to HP-UX 11i rather than cold-install it, carefully review Appendix B for situations that may apply to your system. If you have just received a system that was ordered with Instant Ignition, the HP-UX 11i Operating Environment has already been installed. You do not need to re-install it.

Migration overview

Heres an overview of this guide and migration process shown on the next page: Chapter 1 Prepare for migration to HP-UX 11i. Assess your system and select the migration path, either cold-installation or update. Back up your current system and, if needed, create an install depot or archive. Order and install any additional hardware and software. Chapter 2 Migrate to HP-UX 11i using either cold-installation or update. Chapter 3 Verify the migration. Chapter 4 Update other applications, as needed.

10

Chapter 1

Preparing for Software Migration Introduction

1. Prepare Your System Enough disk space? (4GB root vol min) . HP-UX 11i supported on your system? See page 13. System requires rmware upgrade? See page 19. Installing a new operating environment with HP-UX 11i? Your applications certied to run on HP-UX 11i? Decide: Migrate by either cold-installing or updating. Backup Your System: - Collect Key Install Information. - Backup existing system. - Save conguration le to tape, CD or another system. Prepare source media for migration.References: Chapter 1, Appendix B. Read Before Installing or Updating to HP-UX 11i

(read Chapter 1 to determine path) 2. Cold-install HP-UX 11i 2. Update to HP-UX 11i Verify system requirements. Insert HP-UX CD1. Boot from CD. Install HP-UX 11i. Restore cong & personal les. Backup your system.Reference: Chapter 2.

Verfy system requirements. Insert HP-UX CD1. Install update-ux. Create an optional update depot. Update to HP-UX 11i. Backup your system.Reference: Chapter 2.

3. Verify the Migration 2. Cold-install HP-UX 11i Verify HP-UX installation using swlist and swverify.Reference: Chapter 3.

4. Update Other Applications Update non-OS applications with swinstall. Install critical patches and remove unneeded patches.References: Chapter 4 and HP-UX 11i Release Notes.

HP-UX 11i Migration Overview

Chapter 1

11

Preparing for Software Migration Introduction Installing or updating to HP-UX 11i ? Review the remainder of this chapter to help decide which path to take to migrate your system to HP-UX 11i. You basically have two choices: Cold-install using Ignite-UX This method overwrites everything on the target disk. Use cold-install for new systems and on existing systems when overwriting the root (/) volume will not cause loss of applications or data. The process described in this guide cold-installs a single system from local media. If you plan to install many systems simultaneously, you should plan on using an Ignite-UX server. Ignite-UX is a free product available on the HP-UX 11i CD1. Additional information on Ignite-UX and newer versions are available on the Web: software.hp.com/products/IUX/ Update using update-ux Use the update-ux command when you do not want to erase data or application les on your root disk. As explained in Chapter 2, update-ux adds or replaces functionality based on what you choose when running the command. Verify existing applications HP-UX 11i Operating Environments (OEs) provide a convenient way to install many needed applications in a single step. Contents of HP-UX 11i OEs are listed in the Read Before Installing or Updating to HP-UX 11i booklet supplied with the 11i CDs. If you plan to install an OE, you should verify that your existing installed applications that are not included in the OE are certied to run on the new HP-UX 11i release:

Step 1. Go to this Web page: software.hp.com/HPUX-RDMP/ Step 2. Select: HP-UX 11i Application Release -> New/Updated Software Product List Step 3. Review the listing of supported applications to ensure that they are still supported. If needed, plan on updating applications not provided in an OE after you install or update to 11i.

12

Chapter 1

Preparing for Software Migration System Requirements

System RequirementsSupported systems HP-UX 11i is supported on the HP 9000 systems listed below (newly supported system are shown in bold). For the latest list of supported systems, see: devresource.hp.com/STK/hpux_faq.html Model Workstations: Series 700: 712, 715/64/80/100/100XC, 725/100 B132L, B132L+, B160L, B180L B1000, B2000 C100, C110, C160L C160, C180, C180-XP, C200, C240, C360 C3000, C3600 J200, J210, J210XC J280, J282, J2240 J5000, J5600, J6000, J7000 Servers: A180, A180C A400, A500 Dx10, Dx20, Dx30, Dx50, Dx60 Dx70, Dx80, Dx90 Kx00, Kx10, Kx20 Kx50, Kx60, Kx70, Kx80 L1000, L2000, L3000 N4000-36, N4000-44 R380, R390 T500, T520 T600 V22xx, V2500, V2600 HP Superdome: SD16000, SD32000, SD64000 32-bit X X X X X X X X X X X 64-bit

X X X X X X X X X X X X X X

X X X

Chapter 1

13

Preparing for Software Migration System Requirements Unsupported hardware These workstations and graphics adapters are no longer supported: Workstations: 705, 710, 715/33, 715/50, 715/75, 720, 725/50, 725/75, 730, 735, 750, 755. Graphics adapters: GRX, CRX, CRX-24, CRX-48Z. HP J3525A and J3526A PCI cards on these workstations: B1000, B2000, C3X00. J5000, J7000. Storage requirements HP-UX 11i memory and storage requirements are: 64 MB memory, minimum. Exceptions: All servers: 128 MB minimum. A-Class servers with HP A5838A LAN-SCSI Combo Card: 256 MB minimum. 128 MB swap space for updating or cold-installing. 4GB root disk, minimum, wheither installing or updating to HP-UX 11i, with or without an OE. This can be a single disk drive or combination of physical disks congured as one root volume. Additional updating requirements are listed in Chapter 2.

IMPORTANT

Any last-minute install/update issues are in Read Before Installing or Updating to HP-UX 11i booklet supplied with the 11i CDs Be sure to review that booklet before continuing.

14

Chapter 1

Preparing for Software Migration System Requirements You May Only Need to Install Patch Bundles... If your system is already running HP-UX 11i, you may only need to install one or more patch bundles to bring your system up-to-date or to enable new hardware. Rather than doing a complete migration to the current 11i OS or OE, consider using swinstall to install the latest patch bundles to meet your system needs: Patch BundleHWEnable11i

Description Enables new hardware and delivers critical patches for HP-UX 11i systems. Defect xes for HP-UX 11i OS and network drivers included in OEs. Defect xes for 11i OE applications.

Available via:HP-UX CD1 SupportPlus1

X

X

GOLDBASE11i

X2 X2

GOLDAPPS11i

Notes: 1 Support Plus bundles are available quarterly via CD and the Web. For more details and to download recent bundles, see this Web page: software.hp.com/SUPPORT_PLUS/2 These bundles contains patches with the highest ratings from tests in HPs Enterprise

Patch Test Center.

For instructions on installing patch bundles on an existing 11i system, see Updating and Existing 11i System in Chapter 2.

Chapter 1

15

Preparing for Software Migration Identifying Model, OS and Software

Identifying Model, OS and SoftwareBefore you can decide on the method to migrate to HP-UX 11i, you need to verify that HP-UX 11i is supported on your system and what software versions are currently on your system. Identify model To determine the model number of your system, enter: model Verify that 11i is supported on your system (see the previous table). Identify OS To identify the OS version that your system is currently running, enter: uname -r To update to HP-UX 11i, your system must be currently running either B.10.20 or B.11.00. After cold-installing or updating to HP-UX 11i, youll notice that uname identies the initial 11i release as: B.11.11 Identify installed software To identify the software products on a system or media, use swlist. For example, to list all products and their revisions on a CD mounted at /cdrom , enter: /usr/sbin/swlist -s /cdrom To get table of contents and product details, enter: /usr/sbin/swlist -dvl product -a readme @ /cdrom swlist has many options to expand or narrow the listing to specic attributes; see the swinstall(1M) manpage or the Software Distributor Administrator Guide, available on the HP-UX 11i Instant Information CD and on the Web: docs.hp.com/hpux/os/11i/ After identifying all software products, compare the list with products that will be installed with the HP-UX 11i Operating Environment. See the Read Before Installing or Updating to HP-UX 11i booklet. The update process will replace existing OS products and, optionally, an Operating Environment with new versions; other applications will not be touched unless specied in the update process. The cold-install process, however, will erase all software on the root volume before installing 11i and an optional Operating Environment. If you wish to retain any existing software, be sure to back up that software before migrating.

16

Chapter 1

Preparing for Software Migration Migrating from Previous HP-UX Releases

Migrating from Previous HP-UX ReleasesYou can cold-install HP-UX 11i and its accompanying Operating Environment on any supported system listed on page 13, running any HP-UX OS. If you choose to update an existing HP-UX OS to 11i, however, the system must be running either HP-UX 10.20 or 11.0. Updating from any other release directly to 11i is not a supported migration path. From: To HP-UX 11i with or without an operating environment3: Cold-install 11i or update to 10.20 before updating to 11i2. Cold-install 11i or update2. Cold-install 11i or update to 11.0 before updating to 11i2. Cold-install 11i or update2. Cold-install 1.

HP-UX 9.x -10.10 HP-UX 10.20 HP-UX 10.30 HP-UX 11.0 HP-UX 11.10 Notes:1

Cold-install 11i using Ignite-UX. Can also change from 32-bit to 64-bit OS and install patches and other applications using an install archive. 2 Update using update-ux command. Can also change from 32-bit to 64-bit OS. The update-ux command updates the base OS plus any specied software bundle(s) including products in a specied Operating Environment. By default, update-ux does not match target on installed software.3

Contents of HP-UX 11i Operating Environments are listed in the Read Before Installing or Updating to HP-UX 11i booklet supplied with the 11i CDs.

For help updating from HP-UX 10.20 or 10.30, use the Software Transition Kit available at: devresource.hp.com/STK/

Chapter 1

17

Preparing for Software Migration Firmware Upgrades

Firmware UpgradesSome systems may need a rmware upgrade prior to updating to 11i: Servers: A-Class L-Class N-Class Workstations: B-Class: B1000, B2000 C-Class: C3000, C3600 J-Class: J5000, J5600, J6000, J7000 Minimum rmware If you are about to install or upgrade one of the systems listed above, versions for 11i verify that it has the minimum required rmware version. If needed, install the patch(es) for your system listed here: Firmware and Patch for 11i Support ModelMinimum Firmware Available Patches Version HP-UX 10.20 HP-UX 11.0/11i

Firmware and Patch for OL* SupportMinimum Firmware Version Available Patches HP-UX 11.0 HP-UX 11i

A-Class B-Class C-Class J-Class L-Class N-Class1OL*

40.50 2.9 2.9 2.9 40.48 41.02

n/a

PHSS_23155 / PHSS_23156 PHSS_23185 / PHSS_23186

(not supported)

PHSS_23184

(Also, OL* not available on workstations.1)

n/a n/a

PHSS_23447 / PHSS_23446 PHSS_22657 / PHSS_22658

40.28 41.02

PHSS_22655 PHSS_22657

PHSS_22656 PHSS_22658

= OnLine add, delete and replace. These patches check the rmware and only update the bootROM to be compatible with HP-UX 11i or OL*. 18 Chapter 1

Preparing for Software Migration Firmware Upgrades If the needed rmware version or later is already on your system, you can skip the rest of this section. If not, or if you dont know what rmware version is on your system, please read on. Check workstation Follow these steps to check workstation rmware version prior to rmware revision migrating to 11i: Step 1. As root, shut down the system: 1. Enter: shutdown -h 2. Switch the system OFF. Step 2. Switch the system ON and watch console messages. Press any key when prompted to cancel the automatic boot feature. Step 3. Check the rmware version displayed at the beginning of the boot process. If the rmware revision for your B-, C- or J-Class workstation is less than 2.3, it needs upgrading. Continue with Downloading rmware patches on page 22.

NOTE

Even if your workstations rmware is 2.3 or later, HP recommends (but does not require) that you update to the most current rmware revision (version 4.8/9 at print-time). HP continues to revise the rmware for all the systems listed above, adding support for more types of plug-in PCI cards and memory modules and improving the ability to debug dump output for OC/HPMC/panic. Updating to the latest rmware ensures that your workstation takes advantage of these improvements.

Checking server rmware revision

There are two methods to check rmware version on HP 9000 servers: OnlineDiagnostics or the boot display. Use OnlineDiagnostics if you do not want to reboot your system. Using OnlineDiagnostics: If the OnlineDiagnostics are not already on your system, you can nd them on the 11.0 Support Plus CD.

Step 4. As root, run the Support Tools Manager (STM) utility: /usr/sbin/cstm

Chapter 1

19

Preparing for Software Migration Firmware Upgrades Step 5. Use the map command to nd the device number (Dev Num) for the processors on your system; search for items with the product description CPU:cstm>map systemA.hp.com Dev Num === 1 34 35 Path ==================== system ... 160 166 Product ========================= system () CPU (5c4) CPU (5c4)

Select any one of the processors (CPU) to use in the next step. Step 6. Use the CPU device number as input to the sel dev command to request information on that processor. For example:cstm>sel dev 34; info -- Updating Map -Updating Map...

Step 7. Use the information log (il) command to nd the rmware revision number:cstm>il -- Converting a (5060) byte raw log file to text. -... (output lines are omitted) -- Information Tool Log for CPU on path 160 -Log creation time: Wed May 10 10:21:53 2000 Hardware path: 160 ...(output lines are omitted) Firmware Revision: 40.14

Step 8. Enter q to leave this screen. Then press Enter at the next prompt, and enter exit to exit the utility. Using the Boot Display (this requires a reboot): Step 1. As your system is booting up, interrupt the auto-boot sequence by pressing any key when prompted. For example:... Primary boot path: 0/0/2/0.2 Alternate boot path: 0/0/2/0.2

20

Chapter 1

Preparing for Software Migration Firmware UpgradesConsole path: 0/0/4/0.0 Keyboard path: 0/0/4/0.0 Processor is booting from first available device. To discontinue, press any key with 10 seconds.

Step 2. Youll see the boot Main Menu:---Main Menu-------------------------------------------------Command Description ------------------------BOot [PRI|ALT|] Boot from specified path PAth [PRI|ALT] [] Display or modify a path SEArch [DIsplay|IPL] [] Search for boot devices COnfiguration menu Displays or sets boot values INformation menu Displays hardware information ... HElp [|] Display help for menu or command RESET Restart the system Main Menu: Enter command or menu>

Enter: IN

(for INformation)

Step 3. Youll see the information menu:---Information Menu------------------------------------------Command Description ------------------------ALL Display all system information BootINfo Display boot-related information Cache Display cache information ChipRevisions Display revisions of major VLSI FRU Display FRU information FwrVersion Display firmware information ... Main Return to Main Menu Information Menu: Enter command>

Enter: FV (for Firmware Version) Youll see something like:FIRMWARE INFORMATION Firmware Version: 40.14

Step 4. Continue with the boot (example commands are in bold): Chapter 1 21

Preparing for Software Migration Firmware UpgradesInformation Menu: Enter command > BO PRI Interact with IPL (Y, N, or Cancel)?> N Booting...

Downloading rmware patches

To get a rmware patch over the Web:

Step 1. Go to: itrc.hp.com From the home page, select: individual patches Step 2. If you are already registered, log in with your user ID and password. If not registered, following the instructions on the screen. Remember to save your user ID and password. Step 3. From the patch database main page, select hp-ux. Step 4. Select Series 700 for workstations or Series 800 for servers. Select the OS your system is running, either 10.20 or 11.00. Step 5. Choose Search By Keyword, enter the patch name for your system listed on page 18 and click search. The patch you entered or its successor should be listed. Select that patch (click select all, then add to selected patch list, then download). Ignore any comments that the rmware patch is Not yet HP recommended. Step 6. After downloading the patch, proceed to Applying Firmware Patches next.

To get a rmware patch free of charge via ftp: For the Americas and Asia-Pacic: ftp://us-ffs.external.hp.com For Europe: ftp://europe-ffs.external.hp.com

22

Chapter 1

Preparing for Software Migration Firmware Upgrades Applying rmware Follow these steps to install each patch youve downloaded on each patches system prior to updating it to 11i: Step 1. Back up your system! Step 2. Log in as root. Step 3. Copy the patch(es) to the /tmp directory. Step 4. Change your working directory to /tmp and unshar each patch. For example, to unshar patch PHSS_23184: cd /tmp sh PHSS_23184 Step 5. Run swinstall to install each patch. For example: /usr/sbin/swinstall -x autoreboot=true -x \ patch_match_target=true -s /tmp/PHSS_23184.depot

CAUTION

Do not interrupt the update process. Do not power down the system or perform any other similar action during the update. The process requires multiple reboots. Once the system has rebooted HP-UX completely, its safe to perform any other normal operation.

Chapter 1

23

Preparing for Software Migration Updating Your Ignite-UX Server

Updating Your Ignite-UX ServerThe HP-UX 11i OE CD1 contains the complete Ignite-UX product. When you cold-install 11i from the media, a subset of Ignite-UX is used to perform the installation on a single system. If you plan to update an existing Ignite-UX server to install 11i on more than one system in your network, you should update your Ignite-UX server rst. Follow the instructions for Updating to HP-UX 11i in Chapter 2. Updating your Ignite-UX server and using it to update other systems will ensure that you have the new make_tape_recovery(1M) command to backup and recovery your systems. You will also be assured of keeping consistent kernel conguration with specic drivers, daemons, and kernel tunables on all systems. The latest Ignite-UX software and documentation can also be downloaded from HP via the Web: software.hp.com/products/IUX/

24

Chapter 1

Preparing for Software Migration Installing Diagnostics

Installing DiagnosticsHP-UX 11i automatically installs support tools on all systems to provide required hardware support. These tools, contained in the OnlineDiag bundle, give you a complete solution to verify, troubleshoot, and monitor HP 9000 system hardware, including CPUs, memory, interface cards, mass storage and other devices.

CAUTION

De-installing the OnlineDiag bundle prevents products with dependencies on the support tools from functioning correctly. This currently includes Predictive Support and iCOD client software. Not installing the OnlineDiag bundle also removes protections against hardware failures that the support tools provide. Without these tools, you will nd it much harder to troubleshoot and x the problem if a hardware failure occurs. To ensure the reliability of your computer system, we highly recommend installing the OnlineDiag bundle with HP-UX 11i.

The tools in OnlineDiag: Protect you against some hardware failures (for example, some memory problems). Notify you hardware events that may indicate impending failure. Maintain logs that can give you critical help in determining the cause of failures. Let you troubleshoot system problems with the system online or ofine. For most computer systems, no special conguration of the support tools is necessary. For complete information, see the diagnostics Web site: docs.hp.com/hpux/diag/

Chapter 1

25

Preparing for Software Migration Needing More Disk Space?

Needing More Disk Space?This section provides hints and information to help you determine your disk needs for HP-UX 11i. If you need more disk space (HP-UX 11i generally requires a 4GB root volume), be sure to order the equipment and plan on installing it after backing up your current system as explained later in this chapter. Planning hints Record the hardware path to the CD drive. Develop a clear conguration plan, including: File system sizes. Swap space size. Dump device. Disk and le-system parameters. Mirroring information. If installing application programs other than those supplied within an HP-UX 11i Operating Environment (OE), consider the vendors size recommendations. When planning disk space, refer to these books: Managing Systems and Workgroups: A Guide for System Administrators or Managing HP Superdome Complexes Both manuals are available on the HP-UX 11i Instant Information CD and at:docs.hp.com/hpux/onlinedocs/B2355-90701/B2355-90701.html

Disk and File Management Tasks on HP-UX Prentice-Hall Hewlett-Packard Professional Books, 1997. Update requirements To update your HP 9000 server or workstation to HP-UX 11i, it must have the following: Existing OS: HP-UX 10.20 or 11.0. If your system is running another HP-UX release, you must rst update it to HP-UX 10.20 or 11.0 before following these steps to update to 11i. See Migrating from Previous HP-UX Releases on page 17 for more information.

26

Chapter 1

Preparing for Software Migration Needing More Disk Space? Disk space and memory: update-ux checks for required swap space but does not check for minimum memory: 64 MB memory, minimum. 128 MB free swap space, minimum. Total swap should be 1GB. LVM partitions: / (root): 30 MB free space. /usr: 80-654 MB free space (see the next table). /stand: 30 MB free space (to expand /stand, see Appendix B). /var: 50 MB free space. /opt: 30-580 MB free space (see the next table). 4GB root volume, minimum. Disk-space requirements for the /usr and /opt partitions depend upon the update task. Typical requirements for various updates are listed next. Extra space needed with Technical Computing OE Cold-installing the HP-UX 11i Technical Computing OE installs all CDE languages, rather than just a selected language. To remove unneeded CDE language bundles after installing the TCOE, list them using swlist and remove unneeded bundles using swremove. See Chapter 4 for example uses of swlist and swremove.

Chapter 1

27

Preparing for Software Migration Needing More Disk Space?

Table 1-1

Update Free Disk-space Requirements for /usr and /opt HP-UX 11i Update Task 10.20 -> 11i default update: HPUXBase, HPUXBaseAux, network drivers, CDE and OnlineDiag 10.20 -> 11i OE 10.20 -> 11i Enterprise OE 10.20 -> 11i Mission Critical OE 10.20 -> 11i Technical Computing OE 10.20 -> 11i Minimal Technical OE 11.0 -> 11i default update: HPUXBase, HPUXBaseAux, HWEnable11i, BUNDLE11i, network drivers, CDE and OnlineDiag. 11.0 -> 11i OE 11.0 -> 11i Enterprise OE 11.0 -> 11i Mission Critical OE 11.0 -> 11i Technical Computing OE 11.0 -> 11i Minimal Technical OE 11i (no OE) -> 11i OE 11i (no OE) -> 11i Enterprise OE 11i (no OE) -> 11i Mission Critical OE 11i (no OE) -> 11i Technical Computing OE 11i (no OE) -> 11i Minimal Technical OE 11i OE -> 11i Enterprise OE 11i OE -> 11i Mission Critical OE /usr 554 MB 564 MB 614 MB 614 MB 654 MB 564 MB 404 MB /opt 80 MB 420 MB 580 MB 515 MB 580 MB 420 MB 80 MB

414 MB 474 MB 499 MB 474 MB 414 MB 225 MB 225 MB 225 MB 225 MB 225 MB 80 MB 80 MB

330 MB 530 MB 530 MB 500 MB 330 MB 310 MB 540 MB 540 MB 470 MB 310 MB 230 MB 230 MB

28

Chapter 1

Preparing for Software Migration Selecting the Path to HP-UX 11i

Selecting the Path to HP-UX 11iNow that you have evaluated your system and ordered any additional needed hardware, you need to decide whether to cold-install HP-UX 11i on your system (overwrite everything on the root disk) or update it (replace the OS, patches and add an OE, while leaving other applications intact). Cold-install means installing system software on a new (un-installed) or existing system disk by completely rebuilding the root le system, erasing the existing operating system and data on that volume and installing the new operating system and specied 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, congurations and applications in place. Updating to HP-UX 11i requires that the system be running at 10.20 or 11.0, with or without extension or Additional Core Enhancement (ACE) packs installed. Here are some general guidelines: Cold-install when... We recommend using Ignite-UX to cold-install HP-UX 11i when: You are managing several systems with similar OS congurations. You need fast, predictable deployment. Disk space needs reconguration. See Needing More Disk Space? on page 26. Systems are organized with clean separation of the OS from user, application and data les. You can cold-install from any supported HP-UX OS. See the table on page 17. The cold-install process using Ignite-UX is described in Chapter 2.

Chapter 1

29

Preparing for Software Migration Selecting the Path to HP-UX 11i Update when... You should update rather than cold-install HP-UX 11i when you are updating from HP-UX 10.20 or 11.0 and: You are only updating a few (1-3) systems to 11i. You are concerned about recovering unique applications and data on your root volume, such as custom desktops or applications, that are hard to restore. The update-ux command will not write over non-OS les when installing 11i. Each system has a unique conguration. Current disk space is sufcient for 11i (see page 20). If your system meets these requirements, follow the update procedure in Chapter 2.

NOTE

update-ux removes all 10.x patches from the system prior to updating to 11i. Any 10.x applications left on the system after the update may not be supportable if they required those patches. After migrating your system, see instructions for each remaining application to update it to 11i.

Updating network drivers

Installing or updating to HP-UX 11i will install a minimum set of default networking drivers that apply to the system (see the top part of the table at the end of Chapter 2). You may need to select or specify other available networking drivers to enable other cards on your system. This can easily be done during the install or update by following the instructions in Chapter 2. If you plan to update Netscape Directory Server (NDS) along with HP-UX 11i, see Chapter 2 for details. The update-ux command does not replace NDS with a new version by default. If the Distributed File System (DFS) is installed and in use on your HP-UX 10.20 system to manage large numbers of les, update-ux will remove it and associated data during the update to 11i. If you need to continue using DFS, do not update to HP-UX 11.x or 11i. If you system already is running any version of the Apache Web Server, installing or updating to an HP-UX 11i Operating Environment will not install the version of Apache included with the 11i OE. If you wish to install the version of Apache provided with HP-UX 11i, you should

Updating NDS

update-ux removes DFS

Installing or updating Apache

30

Chapter 1

Preparing for Software Migration Selecting the Path to HP-UX 11i swinstall it after migrating your system to 11i. See Chapter 4 for example uses of the swinstall command.

After deciding which migration path to follow, review the Readme Before Installing or Updating to HP-UX 11i booklet for situations that may apply to your system. Then proceed to collect key system information and back up your current system as explained next.

Chapter 1

31

Preparing for Software Migration Collect Key Install Information

Collect Key Install InformationDuring the cold-install process, you will be prompted for your systems identity and network addresses. Record the following data on paper or on another computer for access during the migration: Hostname (for example, elvis) To get your systems hostname, enter: hostname Host IP address (for example, 15.0.68.12). To get the above systems IP address, enter: nslookup elvis Distributed Network Server (DNS) name (for example, memphis) and IP address. For this example, enter: nslookup memphis Software depot name (for example, vegas) and IP address. For this example, enter: nslookup vegas

32

Chapter 1

Preparing for Software Migration Back Up Your System!

Back Up Your System!In addition to your normal, periodic system backup procedures, you should create a backup tape or a network backup of your root volume group. Do this rst before performing a cold-install or update, and again after the cold-install or update. If a problem occurs, its a very simple procedure to restore the system to its original state. This section offers three alternatives for performing system backups: fbackup, make_recovery and make_net_recovery. Using fbackup Many administrators use the basic fbackup command to back up the entire system to tape. You do not need to unmount any imported le systems; fbackup does not cross NFS boundaries unless specied. Using the normal tape location to do a full backup, mount a new tape and enter: fbackup -f/dev/rmt/0m -i -v Later, if you wish to return the system to its previous state, use the frecover command. See the fbackup(1M) manpage for examples. Ignite-UX recovery A better alternative to using fbackup/frecover is to use the recovery commands commands available with an Ignite-UX server. Ignite-UX recovery commands offer more exibility than fbackup/frecover, including the ability to recover non-bootable systems. The Ignite-UX server software for HP-UX 11i is provided on the HP-UX 11i OE CD1, and can be either cold-installed along with 11i to create a new server or specied in the update-ux command to update an existing Ignite-UX server to 11i. See Chapter 2 for details.Using The Ignite-UX servers make_tape_recovery command creates a bootable make_tape_recovery recovery tape for an LVM or whole disk le system while it is up and

running. When a system has a logical volume layout, the recovery tape will only include data from the root volume group, plus data from any non-root volume group containing the /usr directory. To create the bootable recovery tape, enter: /opt/ignite/bin/make_tape_recovery -ACv where: v is for verbose mode and A species the entire root disk or

Chapter 1

33

Preparing for Software Migration Back Up Your System! volume group. If a tape drive other than the default (/dev/rmt/0m) will be used, modify the command to point to the device you want to use, for example a tape drive at /dev/rmt/3mn: /opt/ignite/bin/make_tape_recovery -ACv -d/dev/rmt/3mn To recover a failed system disk or volume group after a recovery tape has been made, simply load the recovery tape, boot the system, interrupting the boot sequence to redirect to the tape drive. Allow the install process to complete. Do not intervene. The system will reboot and, because map les for all associated volume groups have been saved on the tape, any other existing volume groups are imported and mounted automatically. Data which is not in the root volume group must be backed up and recovered using normal backup utilities. For more information on using make_recovery, see the make_tape_recovery(1m) manpage on an Ignite-UX server or Chapter 11 of the Ignite-UX Administration Guide. The guide is available on the HP-UX 11i Instant Information CD and on the Web: docs.hp.com/hpux/onlinedocs/B2355-90738/B2355-90738.htmlUsing make_net_recovery

The Ignite-UX server also has the make_net_recovery command to create a system recovery archive on another system on the network. The archive created by make_net_recovery is specic to the system it was created for and its identity includes hostname, IP_address, networking information, and so on. In the event of a root disk failure, you use the Ignite-UX server to restore the system by installing the recovery archive. The contents of the system recovery archive always includes all les and directories which are essential to bringing up a functional system. This "essential" list is pre-dened by make_net_recovery. You can run make_net_recovery in its interactive mode to review the directories and les which make up the "essential list, and also add or remove other data from the archive on a disk/volume group, le, or directory basis. For more information on using make_net_recovery, see the make_net_recovery(4) manpage or Chapter 11 of the Ignite-UX Administration Guide.

34

Chapter 1

Preparing for Software Migration Save Conguration Files

Save Conguration FilesIf you are planning to cold-install HP-UX 11i rather than update an existing system, be sure to save the les that you will want to re-install. These include a number of conguration les in /etc, the contents of /usr/local, any local home directories (that is, those you do not import from another system), and any /opt directories that contain installed software. If multiple users are preparing for the cold-install, you might consider creating a directory (such as /backup) on another system. Do not create this directory on your root disk. Mount it with sam. Then create a subdirectory for each system or user (for example, /backup/your_sys). As root, copy the les. For example: Step 1. Copy all cong les from /etc on a system named moe to system curly. On curly, enter: mkdir /backup/moe/etc rcp -p your_name@moe:/etc/* /backup/moe/etc/. Step 2. Copy your local home directory to the backup system. On curly: mkdir /backup/moe/home rcp -pr your_name@moe:/home/ /backup/moe/home/ and so on... Colors and fonts If you want to preserve your colors and fonts in VUE or CDE, execute: xrdb -q > xrdb.save Then save the xrdb.save le in your backup directory. Be aware that VUE is not supported beyond HP-UX 10.20.

Chapter 1

35

Preparing for Software Migration Locate Source Media for Migration

Locate Source Media for MigrationNow that you have backed up your system and important data les, and you have decided how to migrate to HP-UX 11i (cold-install or update), you need to locate the source media needed for the migration: If you are migrating one system at a time Migrate directly from the CDs in the HP-UX 11i media box: HP-UX 11i OE CDs Boot and install a new system or update an existing HP-UX 10.20 system. Support Plus CD Install current HP-UX 11i patch bundles to x defects in the OS and OE applications. HP-UX Application CDs Install applications not installed with the OE or install a newer version of an OE application. Some applications installed with an 11i OE may be older versions than those available on the HP-UX Applications CDs supplied in the media box. Products available on Application CDs are listed in the CD_TABLE_OF_CONTENTS le on each CD. If you plan to migrate many systems in your enterprise We recommend using an Ignite-UX server to create a golden image from which to migrate. This install image can contain the 11i OS, and OE, other applications and any needed patches. Once the archive is in place, either on the Ignite-UX server or on another system, migration on each client system is a single-pass operation; you will only need to reboot each client once. For details on installing an Ignite-UX server with HP-UX 11.0, see the Ignite-UX Administration Guide, supplied on the HP-UX Instant Information CD and on the Web: docs.hp.com/hpux/os/11i/ This completes preparing the system. Now migrate your system to HP-UX 11i as explained in Chapter 2.

36

Chapter 1

Migrating to HP-UX 11i

2

Migrating to HP-UX 11iThis chapter describes migrating your system to HP-UX 11i using the HP-UX 11i Operating Environment (OE) CDs: Cold-installing HP-UX 11i, page 38. Updating HP-UX 10.20 or 11.0 to 11i, page 48. Updating HP-UX 11i to this June 2001 release, page 61. For help in deciding which migration path to follow for your system, please read Chapter 1. Contents of each OE are listed in the Read Before Installing or Updating to HP-UX 11i booklet supplied with 11i CDs. More details on each application are in Chapter 4 of the HP-UX 11i Release Notes. Devices supported by network drivers are listed in the release notes. Other software bundles such as Ignite-UX are available for selection during cold-installation and update. The procedures in this chapter describe booting newer HP 9000 servers. The process differs for older servers, HP 9000 workstations, V-Class and partitioned systems such as HP Superdome. For help with V-Class servers, see Appendix A. Booting partitioned systems, such as HP Superdome and HP S-Class, are explained in the Managing HP Superdome Complexes manual, available on the Instant Information CD and on HPs user-documentation Web site: docs.hp.com/hpux/onlinedocs/B2355-90701/B2355-90701.html

Chapter 2

37

Migrating to HP-UX 11i Cold-installing HP-UX 11i

Cold-installing HP-UX 11iThis section describes cold-installing from the HP-UX 11i CDs, including the operating system, a selected Operating Environment (OE) bundle, network drivers, CDE language bundle, diagnostics and required patches from the Support Plus CD. The overall process is shown on the next page, along with alternate methods of cold-installing 11i: Alternate install methods Installing from software depot(s) Use Software Distributor commands to create depots containing OS, OE, and other software bundles, then install from the depots. For help with this method, see the swinstall(1M) manpage and the Software Distributor Administration Guide available on the Instant Information CD. 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 available on the Instant Information CD. 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. If youre new HP 9000 system was factory installed (we call this factory integrated), the cold-installation process described here has already been performed. Skip this chapter and proceed to install application software. Cold-installing HP-UX on partitioned systems HP-UX must be installed on the boot disk assigned to each partition after the partition has been congured. Conguring the boot disk is explained in the Managing Superdome Complexes manual, available on the HP-UX 11i Instant Information CD and on HPs user-documentation Web listed above. Once each partition has been congured for installation, follow the cold-installation instruction on the following pages to install HP-UX on each partitions boot disk. Installing or updating NDS Although the Netscape Directory Server (NDS) is included in HP-UX 11i OEs, you must explicitly select NDS during the install or update process described next to install it. If you do not select NDS, it will not be installed with 11i. For more on this, see Updating Netscape Directory Server on page 67. 38 Chapter 2


Determine installapproach

if factory integrated from CDsInstall 11i OS/OE using Ignite-UX(see page 43)

use depots *

use golden image **Create Install golden image using Ignite-UX Server**

Create 2 installdepots: OE depot: OS/OE, QPK. AR depot: Applications, QPK.(see Notes below)

Install non-OE applications using swinstall(see Chapter 4)

Install patches from Support Plus CD using swinstall(see Chapter 4)

Install from depot(s) using Ignite-UX

Install image using Ignite-UX Server

Install non-OE applications using swinstall(see Chapter 4)

Identify and install non-OE patches using Custom Patch Manager (CPM)

Install 3rd-party and internal software

Create archive/recovery image Done

Notes: QPK - Quality Pack from Support Plus CD contains patch bundles for OS/OE and applications. See Step 24 on page 47. * For help creating depots, see the Software Distributor Administration Guide. **Golden image can contain OS/OE, patches, and application bundles. For help creating golden images, see the Ignite-UX Administration Guide.

Cold-installing HP-UX 11i

Chapter 2

39


IMPORTANT

If you have NDS version B.02.00.05 and are updating to HP-UX 11i, 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 11i, the server will cease to work and all client systems may lose the ability to have anyone log in.

After NDS is installed or updated with HP-UX 11i, additional conguration steps are required to initiate NDS. See the NDS release notes available on the HP-UX 11i Instant Information CD for instructions. Installing MC/ServiceGuard If you are planning to install the HP-UX 11i Mission Critical OE, MC/ServiceGuard will be automatically installed, removing any previous version of MC/ServiceGuard on the system. If you will require the ServiceGuard OPS Edition on the system rather than MC/ServiceGuard, review Installing ServiceGuard Products at the back of this chapter before continuing. After installing the 11i MC OE, follow the instructions in that section to replace MC/ServiceGuard with the ServiceGuard OPS Edition. If your system is on HP Mission Critical Support, discuss the proper method of installing and patching the Mission Critical OE with your HP Customer Engineer.

On Mission Critical support?

System RequirementsTo cold-install HP-UX 11i, you must have the following: A supported HP 9000 server or workstation. Supported systems are listed in Chapter 1. The HP-UX 11i media (2-CD set). 64 MB memory, minimum. 128 MB swap space, minimum. 4GB root volume, minimum, required when installing HP-UX 11i with or without an operating environment (OE).

40

Chapter 2


Installing HP-UX 11iRequired media Have these CDs ready from the HP-UX 11i media box: HP-UX 11i OE CDs 1 and 2, June 2001 or later. Support Plus CD, June 2001 or later (for general release patch bundle, quality patch bundles and diagnostics. Typical install time Cold-installing HP-UX 11i typically takes from 2-3 hours, depending upon the system and whether you are installing only the OS or also installing an OE. To do a cold installation: Step 1. Insert the HP-UX 11i CD1 into the drive. Make sure any external devices connected to the target system are turned ON and operational. Then turn the system ON or cycle power. Step 2. Stop the autoboot: On workstations, press and hold down the Esc key. On servers, press any key. You will see the boot console menu. Boot procedures vary somewhat between computers. If you need help, enter: HELP Step 3. Ensure that Fast Boot is enabled (the full memory check run when Fast Boot is OFF may take several hours on a large system): 1. Select the Conguration Menu: CO 2. If the Fast Boot selection is available, switch Fast Boot ON: FB ON 3. Return to the Main Menu: MA Step 4. Search for bootable devices, using the choices displayed (for example, enter search or sea). Youll see a table similar to this:Path# ----P0 Device Path ----------SESCSI.2.0 Device Type ----------TOSHIBA CD-ROM

Chapter 2

41

Migrating to HP-UX 11i Cold-installing HP-UX 11iP1 P2 LAN.1.2.3.4 .5.6 FWSCSI.6.0 1.2.3.4 IBM DDRS-34560WS

Of the media listed, a fast/wide SCSI device (FWSCSI) is usually a disk, whereas a single-ended SCSI device (SESCSI) can be a disk or CD drive. CDs usually default to a device path ending in 2. Step 5. Boot from the CD drive using the listed path number. For the example shown above, enter: BO P0 Step 6. After a few minutes, youll be asked Interact with IPL? Press: n The install kernel will load (takes 3-5 minutes), after which a screen might ask you to enter the keyboard language of your console. Enter the number and press Return/Enter... and again to conrm. Step 7. When the initial Ignite-UX screen appears, take a moment to read how to navigate and select choices using this terminal interface:

Use the Tab key to navigate between elds and the arrow keys to navigate within elds. Press Return/Enter to select an item. Pressing Return/Enter or the space-bar opens a menu list. To navigate more quickly, enter the underlined letter of an item (such as I for Install HP-UX). Step 8. Select: Install HP-UX

42

Chapter 2

Migrating to HP-UX 11i Cold-installing HP-UX 11i From the User Interface and Media Options screen, choose: Source Location Options: Media-only installation User Interface Options: Guided Installation provides an install wizard with limited choices. Select if you are not familiar with Ignite-UX. Alternately, select Advanced Installation to see tabbed screens, enabling you to customize your system. Use this mode to change LVM settings and set system parameters, network services, le-system characteristics, and other conguration details. Minimum le-system requirement are listed on page 40. You can exit Guided Installation and restart the conguration using Advanced Installation at any time by either selecting the Cancel button or pressing C. Make your choices and select OK. Step 9. Whether using Guided Installation or Advanced Installation, proceed through each screen to congure your system: Congurations: Lists the OS version (initially B.11.11). Environments: Specify desired OE from those available on the CD. If your system is 32/64-bit capable, select the bundle for the OS word-width you wish to install, 32 or 64 (see the table at the back of this chapter). Languages: Click the Languages... button to view CDE-languages bundles to be loaded. Global is set by default when installing on workstations, resulting in all available CDE-language bundles being installed. Global (Non-CDE) is set when installing on servers to indicate that a generic, CDE-language bundle will be installed. Additional Software: Ensure that the needed networking driver(s) and other applications are selected for your system (see the table at the back of this chapter).

IMPORTANT

Do not de-select the HPUXBaseAux, HWEnable11i, OnlineDiag and/or BUNDLE11i bundles (BUNDLE11i is not needed with the Technical Computing or Minimal Technical OEs). If in doubt, leave the selections as default. Other software products may be selectable, however, we recommend that you do not de-select any products at this time. For more about OnlineDiag, see Verifying and Adding Diagnostics

Chapter 2

43

Migrating to HP-UX 11i Cold-installing HP-UX 11i in Appendix B.

TIP

If youre installing an Ignite-UX server, be sure to select the entire Ignite-UX server product, B5725AA, thus installing the new make_tape_recovery(1M) command on your Ignite-UX server.

At the end of the Guided Installation session, a screen allows you to review any messages that Ignite-UX encountered. If there are any errors, resolve them before continuing with the installation.

NOTE

Ignore any message stating that /var needs to be larger than available to hold a dump le. /var typically only needs to be set to 50-100% as large as the current memory to handle dump les.

Step 10. When nished conguring your installation: With Guided Installation, select: Finish With Advanced Installation, select GO! (at the bottom of any tab). A conrmation screen lists the disks that will be written to during installation and a log of any warnings or errors encountered. You have the chance to Cancel at this time. If you cancel, you return to the previous conguration screen. After you selecting Finish or GO!, the system congures the hard disk(s) and loads a minimum set of commands and libraries. SD then downloads all the products and patches from the rst CD. Step 11. When prompted, replace HP-UX 11i CD1 with the requested CD from the media box. Software will be automatically loaded from each CD. If you see the message:Unable to verify CD-ROM media content ...

You may have pressed Enter before changing the CD. If so, select the displayed Recovery Action 1: Retry software Load... and press Enter again. Step 12. The system automatically reboots after all software has been loaded.

44

Chapter 2

Migrating to HP-UX 11i Cold-installing HP-UX 11i Eject the last CD. Be sure to store all CDs in a safe place. You may need them later to install drivers or install/change the OE. Step 13. If you specied Ask at rst boot during the installation screens, the set_parms command runs now so you can set the root password, date, time, time zone, IP address, and other network parameters. You may need to customize NFS mount gateways, le systems, and so forth after you log in. Changes to the kernel, such as adding devices, will require a reboot to enable them. Step 14. Before installing or updating applications, insert the HP-UX Support Plus CD and install the Quality Pack patch bundles to update the OS and OE applications on your system. For example: /usr/sbin/swinstall -s /cdrom QPK11.11.depot \ x patch_match_target=true -x autoreboot=true The Quality Pack delivers two 11i patch bundles: GOLDBASE11i patches for the 11i OS and OE network drivers. GOLDAPPS11i patches for 11i OE applications. For more about this package, see the Quality Pack page available on the Support Plus Web: software.hp.com/SUPPORT_PLUS/qpk.html Problems? If you encounter a problem during the cold-install process, rst review Appendix B for possible solutions. Help may also be available on the Web: forums.itrc.hp.com/cm/FamilyHome/1,1148,117,00.htm

After Cold-installing HP-UX 11i Your task is nearly complete. If you cold-installed to enable a hardware upgrade, proceed with the hardware phase of the upgrade. Ask your HP Customer Engineer for more information. To potentially improve performance, run sam as root and remove any unneeded network drivers. The drivers listed at the top of the table at the back of this chapter are installed by default. For help using sam, see its Help screens or the Managing Systems and Workgroups manual.

Chapter 2

45


Retrieving Information After Cold-installingAfter completing the cold-install, you can retrieve the information you had previously saved onto another system. Here are some tips: Create a new root directory Consider creating a root home directory that is not /. This keeps the user root dot les out of the / directory. Make sure it is on the root volume by calling it something like /homeroot. This is especially important if you are using LVM and /home is a separate volume.

Step 1. From the CDE login screen, select Options -> Command Line Login and login as root. Step 2. Edit /etc/passwd to change the home directory from root to /homeroot and save it. Step 3. Create the /homeroot directory: mkdir /homeroot Step 4. Move roots personal les (les beginning with . ) to /homeroot: mv /.[a-zA-Z]* /homeroot Step 5. Exit and log in again as root. Recover les Recover all the customized and personal les that you saved previously by merging them manually. For example, do not overwrite /etc/passwd with your old version. Instead, either paste in entries from your old les or merge the old information into the new les. If you had a local home directory, you can restore it as follows: If you copied it to, say, /backup/moe/home, enter these commands: cd /backup/moe/home find -depth -print | cpio -pdm /moe/home If you backed it up to tape with fbackup, enter: frecover -x -i /moe/home -v Restore other les Carefully use the same techniques to restore other les and directories, such as /usr, /local and /opt. For help in importing entire volume groups, see either the Managing Filesystems and Workgroups manual or the Managing HP Superdome Complexes manual.

Restore /home

46

Chapter 2

Migrating to HP-UX 11i Cold-installing HP-UX 11i The commands above will not write over newer les, so your new operating system and any les you update are well protected.

This completes the cold-install process. Now verify the installation as explained in Chapter 3 and back up your new system using the same process you used before installation. Then install other required patches and software; see hints in Chapter 4.

Chapter 2

47

Migrating to HP-UX 11i Updating HP-UX 10.20/11.0 to 11i

Updating HP-UX 10.20/11.0 to 11iThis section describes updating an existing HP-UX 10.20 or 11.0 system to HP-UX 11i using the new update-ux command. To help you decide whether you should update or cold-install, see Chapter 1. Beginning with the 11i release, the update-ux command replaces swgettools to perform these OS update tasks: Update the HP-UX OS from 10.20 or 11.0 to 11i, including adding a new Operating Environment (OE). Update and existing 11i system to a later release. Change the OS word-width from 32-bit to 64-bit on appropriate systems. Change from one OE to another. About update-ux The update-ux command improves the usability and robustness of the update process by eliminating many of the manual steps required by swgettools in previous HP-UX updates. In addition to ensuring a safe environment on the target system for the OS update, update-ux performs these update preparation steps before initiating the update: Before updating from HP-UX 10.20, update-ux performs these operations for you: Veries that FibreChannel Storage is not on the system. If present, it must be manually removed. Ensures that you are not updating a diskless server. Youll have to cold-install 11i on a diskless server, making it a stand-alone system. Checks for minimal disk space in /, /stand, /opt, /usr and /var on a system using LVM. Removes the no-longer-needed SW-DIST.RUPDATE leset. Removes any 10.x patch information and 10.20 OS bundle wrappers. Upgrades to JFS version 3 if needed. Before updating from HP-UX 11.0 or an earlier version of 11i,

48

Chapter 2

Migrating to HP-UX 11i Updating HP-UX 10.20/11.0 to 11i update-ux performs these operations: Checks for minimal disk space in /, /stand, /opt, /usr and /var on a system using LVM. Removes HP-UX 11.0 OS bundle wrappers. If any requirements are not met, update-ux will display an appropriate message and exit. update-ux installs a new version of HP-UX Software Distributor (SD), plus any patches to it, from the source depot before initiating an OS update. Updating NDS If you plan to update Netscape Directory Server (NDS) along with HP-UX 11i, see Updating Netscape Directory Server on page 67. The update-ux command does not replace NDS with a new version by default. If the Distributed File System (DFS) is installed and in use on your HP-UX 10.20 system to manage large numbers of les, update-ux will remove it and associated data during the update to 11i. If you need to continue using DFS, STOP! Do not update to HP-UX 11.x or 11i. If you are planning to install the HP-UX 11i Mission Critical OE, MC/ServiceGuard will be automatically installed, removing any previous version of MC/ServiceGuard on the system. If you currently have or will require the ServiceGuard OPS Edition on the system rather than MC/ServiceGuard, review Installing ServiceGuard Products at the back of this chapter before continuing. If you are updating a system containing MirrorDisk/UX and wish to continue using that product, and you are updating to either of the HP-UX 11i Technical OEs, you will need to re-install patch PHKL_23333 after the update. Although this patch is installed with the 11i update, youll need to re-install it after the update to 11i to re-enable the product. See Chapter 4 for help installing patches.

update-ux removes DFS

Installing MC/ServiceGuard

Updating MirrorDisk/UX

Chapter 2

49


Create archive/recovery image

use depot(s) Determine update-ux Determineupdate approach source

Create depot(s)(see page 54)

cold-install Cold-install from CDs, depots or golden image(see page 41)

CDs Update OS/OE from 11i OE CDs using update-ux(start at page 54)

Update to 11i OE from depot containing OS/OE and Support Plus bundles using update-ux(see page 60)

Update non-OEapplications from Application CDs using swinstall Install patches from Support Plus CD using swinstall

Update non-OEapplications using swinstall(see Chapter 4)

Identify and install non-OE patches Identify and install non-OE patches (use Custom Patch using Custom Patch Manager)

Install 3rd-party and internal software

Updating HP-UX 10.20/11.0 to 11i

Create archive/recovery image

Done

50

Chapter 2

Migrating to HP-UX 11i Updating HP-UX 10.20/11.0 to 11i The update-ux command updates your system in this order: 1. Performs preparation steps including checking the root volume (see About update-ux on page 48). 2. Calls swinstall to install software bundles from CD1. swinstall does its Selection and Analysis processes on the software loaded from the CD, then replaces the existing OS with 11i OS bundles and default network drivers. 3. Prompts you after about an hour to replace CD1 with other CDs from the media box. After mounting each CD, update-ux calls swinstall again to load software and any additional software bundle(s) you specied in the update-ux command. 4. Reboots the system after all software has been loaded. These OS and network driver bundles are loaded by default:HPUXBase32 or HPUXBase64 HPUXBaseAux HWEnable11i BUNDLE11i FibrChanl-00 (64-bit OS only) GigEther-00 RAID-00 (64-bit OS only) FDDI-00 (32-bit OS only) (other networked drivers if needed) OnlineDiag CDE-English (or appropriate language bundle(s))

Typical update times

The entire update process typically takes from 2 to 6 hours, depending upon the system being updated, whether you are updating only the OS or also adding an OE, the amount of existing user data on the system, etc. If you are only updating the OS (not including an OE) on a newer system, the update time will typically be 2-3 hours. If you encounter a problem during the update process, review Appendix B in this guide for possible solutions.

Monitoring the update process

IMPORTANT

Before proceeding, please back up your system; see Chapter 1.

Chapter 2

51


Updating TipsRecord software versions before updating To identify what software still needs updating after the OS update, print an swlist listing of all products and bundles beforehand. For example, enter: /usr/sbin/swlist | lp Then compare it with a similar swlist done after the update. Rebuild kernel Your update could fail if the HP-UX kernel fails in the starting before you update environment. To ensure that you have a reliable starting point, rebuild the kernel before you update: Step 1. As root, enter: /usr/sbin/mk_kernel Step 2. Fix any problems listed in the mk_kernel output. Step 3. Reboot your system to ensure that your new kernel boots. Disable CDE screen lock To prevent the CDE screen lock function from locking the keyboard during an update, disable the function now: Click the style manager icon on the front panel. Click the Screen icon. Select: Screen Lock: Off Also, do not lock the system using the front panel lock icon. Clean out your log To make it easier to check for problems encountered during an update, les rename the log les before starting an update: Step 1. cd /var/adm/sw Step 2. As root, rename each log le. For example: mv swagent.log swagent_old.log Monitor the update If you wish to view the update process in detail, open another term process window (drag it aside so you can also watch for any messages on the window running update-ux) and use the tail command to view swinstall messages being logged: tail -t /var/adm/sw/swagent.log 52 Chapter 2

Migrating to HP-UX 11i Updating HP-UX 10.20/11.0 to 11i You may also wish to log all messages directed to the console by using the script command. For example, to log all messages into a le named: /tmp/updateOS, enter: script -a /tmp/updateOS To halt the script log process, enter: exit Running other commands You can run other commands during an update, such as viewing les, tail, etc. However, do not run other Software Distributor commands during an update; doing so may cause the commands to function improperly. If you encounter a problem during the update process, review Appendix B in this guide for possible solutions. After updating to an HP-UX 11i operating environment (OE), some OE products will need post-installation conguration to make them functional. This may be indicated by a message logged in /var/adm/sw/swagent.log. Refer to each products installation instructions for details. Location of OE product documentation is listed in the tables at the back of the Read Before Installing or Updating to HP-UX 11i booklet and in the HP-UX 11i Release Notes. Release notes are in /usr/share/doc/ and on the Web: docs.hp.com/hpux/os/11i/ All software doesnt get updated The update-ux command updates the HP-UX OS and any software specied in additional software bundle(s) available on the source media. When an OE is specied, some products in the OE such as Apache Web Server, will not automatically get updated if a version of the product not previously installed with an OE already exists on the system. Youll have to update or re-install those products after updating 11i. To verify the software versions after updating, list the products using the swlist command. To verify that all software products are compatible with the new OS, run swverify. These operations are explained in Chapters 3 and 4. After you update, please back up your system. We recommend using the Ignite-UX make_tape_recovery or make_net_recovery command to create a recovery archive immediately after updating to HP-UX 11i. By backing up your system, you will have a reliable system image to return to if subsequent system changes or a system failure corrupts your Chapter 2 53

Updating problems? Conguring OE applications

Verify the update

Back up your system!

Migrating to HP-UX 11i Updating HP-UX 10.20/11.0 to 11i system. To use these recovery commands, you need to rst install the Ignite-UX bundle as shown later in the update examples. Use the same process you used to back up your system before migrating to HP-UX 11i. See Back Up Your System! in Chapter 1.

Procedure A: Install update-uxYou need the update-ux command installed to update from HP-UX 10.20 or 11.0 to 11i. Follow these steps to install update-ux: Step 1. Insert the HP-UX 11i CD 1 and wait for the CD drives busy light to stop blinking. Step 2. Log on as root and nd the CD-ROM device le name: ioscan -fnC disk A typical CD-ROM device name is: /dev/dsk/c1t2d0 Step 3. Create the directory /cdrom under root(/): mkdir /cdrom Step 4. Mount the CD onto the /cdrom directory as a le system. For example: mount /dev/dsk/c1t2d0 /cdrom Step 5. Install update-ux onto the target system: swinstall -r -s /cdrom SW-DIST.SD-UPDATE \ \@ /var/adm/sw/update-ux.root 2> /dev/null The -r option causes SD to write the log les to the alternate root. The 11i SD contains many new keywords that 10.20 and 11.00 SD do not recognize, so the install generates many warnings that can be ignored. Use of the alternate root facilitates ignoring the warnings.

Procedure B: Create a Network Depot (optional)HP-UX 11i is delivered on two CDs, requiring you to swap CDs during the update process. If you want to update without having to swap CDs, you need to create a remote depot on an existing 11i system that contains all the necessary software, then update from that single source. As root, follow this procedure to create a network depot from the HP-UX 11i CDs onto a depot server or other system running HP-UX 11i in your 54 Chapter 2

Migrating to HP-UX 11i Updating HP-UX 10.20/11.0 to 11i network: Step 1. Verify that you have at least 1,230 MB of free space to create the network depot on another system in your network. If this space is not available, use sam to either create a new volume group or extend an existing volume group. For help, see either SAM help or the Managing Systems and Workgroups manual. Step 2. Login as root and mount the logical volume on a new directory named /update. This directory will hold your network depot. Step 3. Insert the HP-UX 11i CD1 and wait for the CD drives busy light to stop blinking. Step 4. Find the CD-ROM device le name: ioscan -fn | more A typical CD-ROM device name is: /dev/dsk/c1t2d0 Step 5. Create the directory /cdrom under root(/): mkdir /cdrom Step 6. Mount the CD onto the /cdrom directory as a le system. For example: mount /dev/dsk/c1t2d0 /cdrom Step 7. Merge all products on the mounted CD to the target depot, for example /update/update-depot: swcopy -s /cdrom \* @ /update/update-depot Step 8. Unmount the CD from directory /cdrom: umount /cdrom Step 9. Insert the HP-UX 11i CD2. Wait for the drives busy light to stop blinking. Step 10. Repeat Steps 6 through 8 using CD2 and the Support Plus CD. The network depot is now ready to update your HP-UX 10.20 or 11.0 system to HP-UX 11i.

Chapter 2

55


Procedure C: Update to HP-UX 11iBy now you should have successfully installed update-ux onto the target system and, optionally, created an update depot containing all software bundles to be installed. Now you can proceed to update your target system as follows. update-ux syntax update-ux -s source_location [-?] [-a 32|64] [-n|-y] [-i] [-x option=value] [sw_spec] where: -ssource_location Species the source containing the new software depot. Possible locations are a local directory, a mounted CD containing a depot, or a remote system-and-depot combination. All paths used in the source_location must be absolute paths. If source_location is a remote system/depot combination, the remote system should be specied rst, followed by the absolute path to the remote depot, separated by a colon with no spaces; for example: swperf:/var/spool/sw -? -a 32|64 Prints the usage statement. Species the OS architecture (word width), 32 bit or 64 bit. Omitting this defaults to the systems currently set OS word-width. update-ux will halt if directed to install an unsupported word-width (only 64-bit OS is supported on B-, C- and J-class systems). Changing an existing system from 64-bit OS to 32-bit OS is not supported. update-ux issues a message and waits for your response to continue whenever something unexpected is attempted. Specify -n at rst (or omit this option) to have update-ux not continue when an error is issued. When you have reviewed/resolved all errors, use -y instead of -n to have update-ux ignore all messages which would otherwise cause update-ux to wait for a user response. Species the swinstall interactive user interface to select software products from a depot or bundle during the update. For more information, see the

-n | -y

-i

56

Chapter 2


swinstall(1M) manpage. -x option=value Species swinstall options to be applied during the update. For a typical update, no swinstall options are required. swinstall -p (preview) is not supported. For information on swinstall options, see the swinstall(1m) manpage or the Software Distributor Administration Guide. sw_spec Species one or more optional software bundles to be updated, such as an operating environment (OE) bundle name, a network-driver bundle or Ignite-UX.

For more about update-ux, see the update-ux(1M) manpage. Examples Recommended update! Each of the following examples updates and reboots the system. Update to HP-UX 11i and an OE: To update to HP-UX 11i and include an 11i Operating Environment, you need to specify the Operating Environment bundle name in the update-ux command. The OE bundles names are:HPUX11i-OE HPUX11i-OE-Ent HPUX11i-OE-MC HPUX11i-TCOE HPUX11i-MTOE

For example, to update to 11i and install the default 11i OE, insert an HP-UX 11i CD1 in the local drive mounted at /cdrom. As root, enter: /usr/sbin/update-ux -s /cdrom HPUX11i-OE Or, to update to 11i and install the 11i Mission Critical OE, insert HP-UX 11i Mission Critical OE CD1 in the local drive mounted at /cdrom and enter: /usr/sbin/update-ux -s /cdrom HPUX11i-OE-MC Each example updates the OS, installing all OS products listed on page 51, plus the OE bundle. Application software products included in the OE are represented by the bundle name. Any replaced product bundles and unneeded patch information are removed. Applications installed with each OE are listed at the back of the Read Before Installing or Updating to HP-UX 11i booklet supplied with the CDs.

Chapter 2

57


Update to HP-UX 11i OS (no OE): To update to HP-UX 11i, insert HP-UX 11i CD1 in the local drive mounted at /cdrom and enter: /usr/sbin/update-ux -s /cdrom This example updates the HP-UX OS to 11i. All OS, networking, diagnostic and CDE bundles listed on page 41 are installed.

Updating from a network depot: To update from an optional network depot on a remote system named homer, include the path to the depot in the update-ux command: /usr/sbin/update-ux -s homer:/update/updatedepot This example does a default HP-UX 11i OS update, running swinstall only once since a depot is used instead of HP-UX 11i CDs.

Update using match_target To update to HP-UX 11i OE using match_target, enter: /usr/sbin/update-ux -s /cdrom -x match_target=true HPUX11i-OE This command adds all OS, networking, CDE and diagnostic bundles described in the previous example, plus the HP-UX 11i OE and any software selected by match_target. Software that is selected by match_target may not t be contained in a bundle. We do not recommend using match_target because: match_target only installs lesets matching those already on your system. Filesets containing any new HP-UX 11i functionality introduced will not be selected. Software that is installed may not include bundle wrappers, making identication of software on the system more difcult. To help avoid potential problems, update-ux always installs a minimum set of OS bundles and the match_target option selects additional software beyond the minimum set.

58

Chapter 2


NOTE

Do not use patch_match_target with update-ux when updating applications. Instead, use update-ux -i to invoke swinstalls interactive mode, where you can specify match_target or patch_match_target to update existing applications and/or patches.

Update using interactive software selection: To interactively select software for an update, use the -i option. For example: /usr/sbin/update-ux -s /cdrom -i For each CD, update-ux displays swinstalls interactive user interface with software already selected to match the default update. Now you can change software selections, for example, selecting as non-default network driver or a Web browser, before performing the update. Since update-ux selects OS, networking, language and diagnostic bundles by default, the interactive user interface provides a way to de-select the default software and use a pure match_target instead. Due to the problems explained above, using a pure match_target is not recommended.

NOTE

Do not combine -i and -x options in the same update-ux command.

When the -i option is specied, swinstalls interactive user interface is active only when swinstall is running to load software from each source location. When installing from HP-UX 11i CDs, you will have to select non-default software twice; once for each CD. If you do set swinstall options like match_target, be sure to re-select those options in the second swinstall session. For help using swinstalls interactive mode, see the swinstall(1M) manpage or the Software Distributor Administration Guide.

Update with selectable software such as an Ignite-UX server: To update to HP-UX 11i and include additional software such as Ignite-UX, enter: /usr/sbin/update-ux -s /cdrom B5725AA Chapter 2 59

Migrating to HP-UX 11i Updating HP-UX 10.20/11.0 to 11i Products installed include the default HP-UX 11i OS bundles listed on page 51, plus the Ignite-UX server bundle, B5725AA. Now you can use Ignite-UX to install and recover other HP-UX 10.20, 11.0 and 11i systems in your network. After installing selectable software, complete any post-install conguration explained in the HP-UX 11i Release Notes available in /usr/share/doc/. To complete the Ignite-UX server installation, see Chapter 2 in the Ignite-UX Administration Guide, available on the HP-UX 11i Instant Information CD. In case of trouble The update-ux command returns an error value when it is not successful: 1 Error during execution; update aborted. 2 Update aborted via user action (-n or keyboard press). Messages are recorded in /var/adm/sw/swagent.log and /var/adm/sw/swinstall.log When updating Ignite-UX, also look at its log in /var/adm/sw/ Typical update-ux error messages and recovery actions are listed in Appendix B. Verify the update To verify the success of your update, review the update messages logged in /var/adm/sw/swagent.log. Also see the verication tips in Chapter 4.

This completes the update process. Now verify the update as explained in Chapter 3 and back up your new system as you did prior to this update. Then install required patches and other software as explained in Chapter 4.

60

Chapter 2

Migrating to HP-UX 11i Updating an Existing 11i System

Updating an Existing 11i SystemTo update an existing HP-UX 11i system to the latest release, use the update-ux command (see the previous section) to install all new software from the newest HP-UX 11i CDs. For example, if your system includes the default HP-UX 11i OE, this command will update the OS and 11i OE appli

HP-UX 11i Installation and Update Guide

Documents