HP-UX 11.0 Installation and Update Guide
HP-UX 11.0 Installation and Update Guide
HP-UX 11.0 Installation and Update Guide
Manufacturing Part Number: 5990-6721 March 2004, Edition 1 Printed in the United States Copyright 1983-2004 Hewlett-Packard Development Company, L.P.
Legal Notices
The 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 fitness 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 specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Sales and Service Office. U.S. Government License Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Copyright Notice !Copyright 1983-2004 Hewlett-Packard Development Company, L.P. !Copyright 1979, 1980, 1983, 1985-1993 The Regents of the Univ. of California !Copyright 1980, 1984, 1986 Novell, Inc. !Copyright 1986-2000 Sun Microsystems, Inc. !Copyright 1985, 1986, 1988 Massachusetts Institute of Technology !Copyright 1989-1993 The Open Group !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-2003 Mentat Inc. !Copyright 1996 Morning Star Technologies, Inc. !Copyright 1996 Progressive Systems, Inc.
Trademark Notices Adobe" and Acrobat" are trademarks of Adobe Systems Incorporated. HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000 computers are Open Group UNIX 95 branded products. Intel" and Itanium" are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Java is a US trademark of Sun Microsystems, Inc. Microsoft" and Windows" are U.S. registered trademarks of Microsoft Corporation. Oracle" is a registered US trademark of Oracle Corporation, Redwood City, California. UNIX" is a registered trademark of The Open Group.
Publication History
The manual publication date and part number indicate its current edition. The publication date changes when a new edition is released. The manual part number changes when extensive changes are made. To ensure that you receive the latest edition, you should subscribe to the appropriate product support service. See your HP sales representative for details. HP-UX 11.0 Installation and Update Guide, Dec 2002, Edition 1, 5187-1843, Instant Information CD, and web: http://docs.hp.com HP-UX 11.0 Installation and Update Guide, June 2002, Edition 1, 5187-0151, Instant Information CD, and web: http://docs.hp.com HP-UX 11.0 Installation and Update Guide, March 2002, Edition 2, 5187-0103, Instant Information CD, and web: http://docs.hp.com HP-UX 11.0 Installation and Update Guide, March 2002, Edition 1, 5185-6583, Instant Information CD, and web: http://docs.hp.com HP-UX 11.0 Installation and Update Guide, March 2001, Edition 1, 5971-0642, Instant Information CD, and web: http://docs.hp.com Installing HP-UX 11.0 and Updating HP-UX 10.x to 11.0, March 2000, Edition 2, B2355-90679, Instant Information CD, and web: http://docs.hp.com Installing and Updating HP-UX 11.0 Additional Core Enhancements, Nov 1999, Edition 1, B3782-90785, Instant Information CD, and web: http://docs.hp.com Installing and Updating HP-UX 11.0 Extension Pack, November 1997, Edition 1, B2355-90153, Instant Information CD, and web: http://docs.hp.com
New editions of this manual incorporate all material updated since the previous edition. For the latest version, see the HP-UX 11.0 documentation on the web: http://docs.hp.com/hpux/os/11.0
Please direct comments regarding this guide to: Hewlett-Packard Company HP-UX Learning Products 3404 East Harmony Road Fort Collins, Colorado 80528-9599 Or, use this web form to send us feedback: http://docs.hp.com/assistance/feedback.html
Typographic Conventions
We use the following typographical conventions. audit (5) HP-UX manpage. audit is the name and 5 is the section in the HP-UX Reference. On the web and on the Instant Information DVD, it may be a hot link to the manpage itself. From the HP-UX command line, you can enter man audit or man 5 audit to view the manpage. See man (1). Title of a book. On the web and on the Instant Information DVD, it may be a hot link to the book itself. Command name or qualified command phrase. Text displayed by the computer. Text that is emphasized. Text that is strongly emphasized. Name of a keyboard key. Note that Return and Enter both refer to the same key. Defined use of an important word or phrase. Commands and other text that you type. Name of a variable that you may replace in a command or function or information in a display that represents several possible values. Contents are optional in formats and command descriptions. If the contents are a list separated by |, you must choose one of the items. Contents are required in formats and command descriptions. If the contents are a list separated by |, you must choose one of the items. Preceding element may be repeated an arbitrary number of times. Separates items in a list of choices.
Book Title
Term UserInput
Variable
[ ]
{ }
... |
Contents
1. Preparing for Software Migration
Using the Migration Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Introducing HP-UX 11.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reviewing the Media Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Is Your System Already Running HP-UX 11.0? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Choosing the Migration Path: Cold Install or Update . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keeping Up with Firmware Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying Model, OS, and Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying the Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying the OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying Installed Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Meeting System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsupported Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unsupported Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Supported Kernel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Storage Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Requirements for Cold Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Requirements for Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Needing More Disk Space? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Planning Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Verifying Existing Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backing Up the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Ignite-UX Recovery Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using make_tape_recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using make_net_recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using fbackup and frecover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Files to Consider Backing Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Using the Ignite-UX Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Should You Use Ignite-UX? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Should You Upgrade the Ignite-UX Server? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Possible Impact of Ignite-UX Default Parameter Changes . . . . . . . . . . . . . . . . . . . . Using Core Media for Expert Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Additional Pre-Cold Install Tasks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collecting Key Install Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Saving Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preserving Colors and Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 22 22 24 25 28 29 30 30 30 30 31 31 33 33 33 33 34 35 36 36 38 39 39 39 40 41 41 42 42 42 43 44 46 46 47 47
Contents
Additional Pre-Update Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removing Information about Prior Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating from a Custom Software Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locating Source Media & Codewords for Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . Locating Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Locating Codewords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The Next Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 48 49 50 50 51 52
Contents
Installing from the Core OS Options CD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 Backing Up the Core System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 The Next Step. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
B. Troubleshooting
Common Install and Update Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intermittent sendmail Problem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Adjusting File System Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Problems with Large Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Un-installing HP-UX 11.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Re-installing SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing Diagnostic Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 119 120 125 126 127 128 11
Contents
Installing and Updating Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Disk Space, Memory and Diagnostic Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . / Partition Must Have 100 MB Free Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . /stand on LVM Partition Must Have at Least 47 MB Available . . . . . . . . . . . . . . . /var Partition Must Have at Least 500 MB Free Space . . . . . . . . . . . . . . . . . . . . . . /usr on LVM Systems Must be Extended. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . eqmemsize Kernel Parameter May Need Increasing . . . . . . . . . . . . . . . . . . . . . . . . Security Situations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Applications on Trusted Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting up NIS+ with Trusted Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tightened Permissions on CUE to Prevent Security Breaches . . . . . . . . . . . . . . . . Hardware and Firmware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP D6804A USB Hub Not Supported on HP-UX 11.0 ACE 9911 . . . . . . . . . . . . . . Problems with Configuring LAN Cards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Remove VME Before Updating a Workstation from 10.20 to 11.0. . . . . . . . . . . . . . Graphics Driver Configuration May Be Needed . . . . . . . . . . . . . . . . . . . . . . . . . . . . PCI Card Problem on Some HP Visualize Workstations . . . . . . . . . . . . . . . . . . . . . GSP Reset Command Returns Wrong Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . Application and Compiler Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating When HP Domain/NetScape Suitespot Pro is Present . . . . . . . . . . . . . . Updating When HP Web Quality of Service is Present . . . . . . . . . . . . . . . . . . . . . . libc Changes May Require Applications to be Rebuilt . . . . . . . . . . . . . . . . . . . . . . . C Compiler Mode Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP Compilers May Need Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CDE Desktop's X11 Server May Not Start After Update to 11.0. . . . . . . . . . . . . . . EISA 100BT Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP VUE/CDE Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . HP-UX 10.20 Patch Causes Kernel Build Failure . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple LAN Cards Cause CDE Login Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . Patch May be Needed to Run SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Patch Needed Before Installing Fibre Channel Adaptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Patch Interaction Can Cause 3-D Graphics Software Install Errors. . . . . . . . . . . . Screen May Lock During Update. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Panic Caused by Streampipes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating between 32-bit and 64-bit OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 129 130 130 130 131 131 133 134 134 135 135 136 136 136 136 137 138 138 139 139 139 140 140 141 142 142 144 144 146 147 148 149 149 150 150 152
Contents
Installing 64-bit Minimal OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating to 64-bit Operation on New Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . Converting between 32-bit and 64-bit Operation for Kernel with Drivers . . . . . . . Convert between 32-bit and 64-bit OS without Additional Drivers. . . . . . . . . . . . . 64-bit OS Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . BIND 8.1.2 Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 152 155 157 159 160
13
Contents
14
Tables
Table 1-1. Patch Bundles Available from HP-UX Media . . . . . . . . . . . . . . . . . . . . . . .24 Table 1-2. Supported Workstation Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 Table 1-3. Supported Server Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32 Table 1-4. Disk Space Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Table 1-5. HP Licensing Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Table 2-1. Mass Storage and Network I/O Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . .61 Table A-1. HP-UX 11.0 Software Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110 Table A-2. Core OS Options Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111 Table A-3. Support Plus Software Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .115 Table B-1. Device Drivers Required for 32/64-bit Conversion . . . . . . . . . . . . . . . . . .154
15
Tables
16
Figures
Figure 2-1. Overview of Cold-install Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54 Figure 3-1. HP-UX 10.x -> HP-UX 11.0 Update Flowchart . . . . . . . . . . . . . . . . . . . . .71
17
Figures
18
To complete the steps in this chapter, we estimate you require 6-8 hours to choose the migration path, back up the system, and perform pre-migration tasks. Please note that your time may vary. Chapter 1 19
In this guide, the following terms apply: Migration refers to both the cold-install and update processes. HP-UX 11.0 Install/Update/Recovery CD and HP-UX 11.0 Core OS CD are used interchangeably.
IMPORTANT
Review the Read Before Installing or Updating to HP-UX 11.0 CD booklet. It describes last-minute cold-install and update information.
Please note that March 2004 is the final release of HP-UX 11.0. This is the final version of the user guide and the media. HP is discontinuing HP-UX 11.0 as of March 31, 2004 and obsoleting it on December 31, 2006. Please contact your local support representative for more information.
20
Chapter 1
Chapter 1
21
22
Preparing for Software Migration Introducing HP-UX 11.0 Application CDs Delivers the latest versions of application software supported on HP-UX 11.0. All products available on the Application CD set are listed in the CD_TABLE_OF_CONTENTS file on each CD. Some applications require codeword certificates to unlock the software. To obtain certificates, follow the ordering instructions after installing the software. Support Plus CD Provides diagnostics and current HP-UX 11.0 patch bundles to enable hardware and applications. For details, see the Support Plus User Guide on the CD and the Read Before Installing or Updating to Support Plus CD booklet. Also see Whats on the HP-UX 11.0 Support Plus CD? on page 115. The Support Plus CD contains a software product called HP Instant Support Enterprise Edition (ISEE) that replaces HP Predictive Support on HP-UX servers. ISEE enables HP remote support over the Internet. ISEE is a feature of select HP support contracts. HP-UX Instant Information CD (II CD) Contains current HP-UX 11.0 guides, release notes, and white papers. See the CD booklet for more information. Read Before Installing (RBI) or Updating to HP-UX 11.0 Provides last-minute cold-install and update information. The CD booklet is delivered with HP-UX 11.0 Install/Update/Recovery CD. HP-UX 11.0 Release Notes Describes features and functionality of HP-UX 11.0. After you migrate to HP-UX 11.0, the file is on the system in /usr/share/doc/. Release notes, HP-UX 11.0 guides, and many application software guides are available on the HP-UX Instant Information CD and on the web: http://docs.hp.com/hpux/os/11.0 NOTE For the latest information on HP-UX software releases, go to the web: http://software.hp.com/RELEASES-MEDIA For a list of all products in the HP-UX 1.0 release, HP provides an Availability Matrix Overview. Go to the web: http://software.hp.com/MATRIX
Chapter 1
23
Preparing for Software Migration Is Your System Already Running HP-UX 11.0?
QPK1100
Notes Support Plus bundles are available by CD and the web. For more details and to download recent bundles, go to the web: http://software.hp.com/SUPPORT_PLUS
24
Chapter 1
Preparing for Software Migration Choosing the Migration Path: Cold Install or Update
Cold install means installing system software on a new (un-installed) or existing system disk by completely rebuilding the root file system, erasing the existing operating system and data on that volume, and installing the new operating system and specified software and data. Here are some general considerations: Supported software can be installed without regard for the software currently on the system, or concern for cleaning up old software Easy to cold install Fast, time-effective way to migrate to the new OS Less prone to problems with integration Overwrites everything on the target disk Use on new systems and existing systems when overwriting the root (/) disk will not cause loss of applications or data. Use on an existing system that has the HP-UX 10.01, 10.10, or 10.20 operating system and meets system requirements. Updating from any other release is not supported. Use this guide to cold install a single system from local media.
Chapter 1
25
Preparing for Software Migration Choosing the Migration Path: Cold Install or Update Should You Update to HP-UX 11.0? Update means using Software Distributor (SD) tools to selectively overwrite the operating system and application software from media or network source depot. Here are some general considerations: Leaves user data, configurations, and applications on the target disk. Do not worry about recovering unique applications and data on your root volume such as custom desktops or applications that are hard to restore. Each system has a unique configuration. Use on an existing system when overwriting the root (/) disk does not cause problems. Use when current disk space is sufficient for HP-UX 11.0. Difficult to update, requiring more time and integration. More prone to problems with integration. Do not want to erase data and application files on the root disk, Do not want to rebuild a highly configured system, or reconfigure filesystems. Use on an existing system that has the HP-UX 10.01, 10.10, or 10.20 operating system, regardless of Extension Packs/Support Plus software and Additional Core Enhancements (ACE), and meets system requirements. Updating from any other release is not supported. Use this guide to update a single system from local media.
NOTE
For help in updating from HP-UX 10.30, see the Software Transition Kit on the web: http://devresource.hp.com/STK
26
Chapter 1
Preparing for Software Migration Choosing the Migration Path: Cold Install or Update Should You Migrate to HP-UX 11i? As of December 2000, you should consider migrating your HP-UX 10.20 or HP-UX 11.0 systems to HP-UX 11i, the recommended, next-level enterprise release. HP-UX 11i delivers new hardware enablement, software functionality, and bundles of important HP-UX applications in software bundles called Operating Environments. Migrating to HP-UX 11i is easier with the new update-ux command available on the HP-UX 11i media. You can update from HP-UX 10.20 or HP-UX 11.0 to HP-UX 11i using one command and requiring generally only one reboot. For more information about HP-UX 11i, go to the web: http://docs.hp.com/hpux/os/11i A summary of HP-UX 11.0 and HP-UX 11i features and benefits is also available on the HP Software Transition Kit web site: http://devresource.hp.com/STK/hpuxoverview.html NOTE If you just received a system that was ordered with "Instant Ignition," either HP-UX 11.0 or HP-UX 11i was installed. You do not need to re-install the operating system (OS). Go to Chapter 5, Installing Patches and Applications, on page 99 to check for the latest patches and latest non-OS applications.
Chapter 1
27
Pre-Migration Tasks
You must complete these pre-migration tasks and any additional pre-cold install and pre-update tasks in this chapter before migrating to HP-UX 11.0: Keeping Up with Firmware Recommendations on page 29 Identifying Model, OS, and Software on page 30 Meeting System Requirements on page 31 Needing More Disk Space? on page 36 Verifying Existing Applications on page 38 Backing Up the System on page 39 Using the Ignite-UX Server on page 42 Additional Pre-Cold Install Tasks on page 46 Collecting Key Install Information on page 46 Saving Configuration Files on page 47 Preserving Colors and Fonts on page 47 Additional Pre-Update Tasks on page 48 Removing Information about Prior Patches on page 48 Updating from a Custom Software Depot on page 49 Pre-Migration Tasks for Everyone Locating Source Media & Codewords for Migration on page 50
If you see this heading, it alerts you to tasks in the remainder of this chapter that everyone must perform for the migration.
28
Chapter 1
Chapter 1
29
Identifying the OS
To identify the OS version that your system is currently running, enter: uname -r
30
Chapter 1
Supported Systems
HP-UX 11.0 is supported on the following HP systems. For the latest list of supported systems, go to the web: http://www.hp.com Enter model to see the model of the system you are using. For example, $ model 9000/780/J282 NOTE The model command may return information that does not match the bezel on your system. You need the latest release of media to support the latest hardware on HP-UX 11.0. HP-UX 11.00 does not support systems with PA-8800 and later processors. Table 1-2 Supported Workstation Models 32-bit X X X X X X X 31 64-bit
Workstation Model Series 700: 712, 715/64/80/100/100XC, 725/100 B132L, B132L+, B160L, B180L B1000, B2000, B2600 C100, C110, C160L C160, C180, C180XP, C200, C240, C360 C3000, C3600, C3650, C3700, C3750 Chapter 1
Preparing for Software Migration Meeting System Requirements Table 1-2 Supported Workstation Models (Continued) 32-bit X X X X 64-bit
Workstation Model J200, J210, J210XC J280, J282, J2240 J5000, J5600, J6000, J6700, J7000, J6750 Table 1-3 Server Model A180, A180C A400, A500 Dx10, Dx20, Dx30, Dx50, Dx60 Dx70, Dx80, Dx90 E, F, G, H, I (all) Kx00, Kx10, Kx20 Kx50, Kx60, Kx70, Kx80 L1000, L2000, L1500, L3000 N4000 R380, R390 T500, T520 T6xx V22xx, V2500, V2600 Enterprise Parallel Servers: EPS22, EPS23, EPS40 Supported Server Models
32-bit X
64-bit
X X X X X X X X X X X X X X X X X X
32
Chapter 1
Unsupported Hardware
These workstations and graphics adapters are no longer supported on HP-UX 11.0: 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
Unsupported Cards
For unsupported cards, see Keeping Up with Firmware Recommendations on page 29.
Supported Kernel
You need the latest install kernel to use any of the newer I/O cards or mass storage devices that ship with the latest HP-UX 11.0 Install/Update/Recovery CD. New HP-UX 11.0 Kernel Tunables Use the latest SAM/ObAM patch to manage the new HP-UX 11.0 kernel tunables and drivers. See the release notes for the new HP-UX driver and kernel tunables managed by the latest SAM/ObAM patch.
Storage Requirements
HP-UX 11.0 requires a system to have the following: 64 MB memory, minimum. 128 MB swap space for updating or cold installing. 8 GB root disk, minimum, when installing or updating to HP-UX 11.0. This can be a single disk drive or combination of physical disks configured as one root volume group.
Chapter 1
33
34
Chapter 1
Chapter 1
35
Planning Hints
Record the hardware path to the CD drive. Develop a clear configuration plan: For example, for a cold install you should consider changing the following parameters: File system sizes Swap space size Dump device Disk and file-system parameters Mirroring information For example, for an update you may consider changing the following parameters: Swap space size Dump device Kernel parameters (retune) If you are installing application programs other than those supplied within an HP-UX 11.0 Applications CD, consider the vendor's size recommendations.
36
Chapter 1
When planning disk space, refer to these books: Managing Systems and Workgroups: A Guide for System Administrators available on the HP-UX 11.0 Instant Information CD and on the web: http://docs.hp.com/hpux/os/11.0 Disk and File Management Tasks on HP-UX Prentice-Hall Hewlett-Packard Professional Books, 1997.
Additional Memory Needed with A5838A LAN-SCSI Combo Card If you have or plan to install an HP A5838A LAN-SCSI Combo Card in A400/A500/A550 servers, you must also have at least 256 MB of memory. The A5838A card driver, btlan3, may cause the system to hang with less than 256 MB of system memory.
Chapter 1
37
3. Review the listing of applications to ensure that they are still supported. 4. If needed, plan on installing patches and applications after you migrate to HP-UX 11.0. See Installing Patches and Applications on page 99. NOTE HP provides an Availability Matrix Overview for HP-UX releases. Go to the web: http://software.hp.com/MATRIX
38
Chapter 1
Ignite-UX recovery commands offer more flexibility than fbackup/frecover, including the ability to recover non-bootable systems. The Ignite-UX software for HP-UX 11.0 is provided on an HP-UX Applications CD. Use swinstall to install Ignite-UX on a server after installing or updating to HP-UX 11.0. The Ignite-UX documentation for HP-UX 11.0 is available on the Instant Information CD and the web: http://docs.hp.com
Using make_tape_recovery
The Ignite-UX make_recovery or make_tape_recovery command (available beginning with Ignite-UX version 3.2) creates a bootable recovery tape for a Logical Volume Manager (LVM) or whole disk file
Chapter 1
39
Preparing for Software Migration Backing Up the System system while the system 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 -Av where v is for verbose mode and A specifies the entire root disk or volume group. If a tape drive other than the default (/dev/rmt/0m) is used, modify the command to point to the device you want to use. For example, if a tape drive is at /dev/rmt/3m, enter: /opt/ignite/bin/make_tape_recovery -Av -a/dev/rmt/3m 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 unless you need to make changes to volume groups. The system will reboot and, because map files 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 back-up utilities. For more information on using make_tape_recovery, see make_tape_recovery (1M) on the Ignite-UX server (version B.3.2 or later) or the Ignite-UX Administration Guide (March 2001 or later). It also includes more information on root volume groups. The guide is available on the HP Instant Information CD and on the web: http://docs.hp.com/hpux/os/11.0
Using 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 specific to the system for which it was created 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.
40
Chapter 1
Preparing for Software Migration Backing Up the System The contents of the system recovery archive always includes all files and directories which are essential to bringing up a functional system. This "essential" list is predefined by make_net_recovery. You can run make_net_recovery in its interactive mode to review the directories and files which make up the "essential list," and also add or remove other data from the archive on a disk/volume group, file, or directory basis. For more information on using make_net_recovery, see make_net_recovery (1M) on the Ignite-UX server (version B.3.2 or later) or the Ignite-UX Administration Guide (March 2001 or later). It also includes more information on root volume groups. The guide is available on the HP Instant Information CD and on the web: http://docs.hp.com/hpux/os/11.0
Chapter 1
41
42
Chapter 1
Preparing for Software Migration Using the Ignite-UX Server In some cases, a newer version of Ignite-UX cannot restore older backups. New images should be made with the newer version of Ignite-UX. For the latest Ignite-UX software and documentation, go to the HP-UX 11.0 Applications release media or the web: http://software.hp.com/products/IUX NOTE When using a network depot with your HP-UX 11.0 Install/Update/Recovery media, the depot must exactly match the depot software delivered on the media.
Chapter 1
43
The more you know about the system disk and its partitioning scheme, before you encounter major damage or corruption, the easier it will be for you to recover. The procedures which follow assume that both fsck and mount can be run successfully on the system disk; otherwise, the following procedures are not applicable.
44
Chapter 1
Preparing for Software Migration Using the Ignite-UX Server Automated Recovery Procedures There are four possible expert recovery situations, each of which has its associated recovery procedure: If, after a system problem, you cannot get the system to the ISL> prompt from the system disk, you will want to rebuild the bootlif on the system disk, and install all critical files required to boot on the root file system. If you can get the system to the ISL> prompt, but cannot boot vmunix, the system disk is corrupted; you will want to install only the critical files required to boot on the root file system. If you can't get to the ISL> prompt, but you know that the root file system is good, you will want to rebuild the bootlif on the system disk. If you believe your kernel is corrupted, you will want to replace only the kernel on the root file system.
Chapter 1
45
46
Chapter 1
TIP
HP-UX releases have manual pages (manpages) online. To see an explanation of commands and options, at a system prompt enter the following: man command_name
Chapter 1
47
Start Task
To remove information about prior patches: 1. Make a back-up copy of the IPD (in /var/adm/sw/products): find /var/adm/sw/products | cpio -pdumv /tmp/products.bak 2. Enter the command: /usr/sbin/swmodify -u PH\?\?\_\*.\* PH\?\?\_\* 3. Remove the patch directory: rm -rf /var/adm/sw/patch The swmodify command in Step 2 removes all fileset information and then product information for the patch products. The swmodify command does not allow you to remove traces of a product from the Installed Products Database (IPD) if any of its filesets exist in the IPD.
48
Chapter 1
Preparing for Software Migration Additional Pre-Update Tasks The backslashes inhibit the shell from expanding the wildcard characters, thus allowing swmodify to match all the software selections for patches. If information about prior patches is not removed before you update, it will still be there when you boot HP-UX 11.0, wasting a significant amount of disk space and comprising old software replaced by the patches.
Chapter 1
49
Preparing for Software Migration Locating Source Media & Codewords for Migration
Locating Media
If you are migrating one system at a time, migrate directly from the media or network: HP-UX 11.0 Install/Update/Recovery CD boot and install a new system or update an existing HP-UX 10.01, 10.10 or 10.20 system. Core OS Options CD install a new workstation or update an existing HP-UX 10.20 workstation system. Support Plus CD install diagnostics and current HP-UX 11.0 patch bundles to enable hardware and applications.
After the migration, you can install other applications from their media. TIP Applications CDs install or update HP-UX applications.
To install HP-UX from a network depot, go to the Ignite-UX Administration Guide on the web: http://docs.hp.com/hpux/os/11.0
NOTE
This guide supports the latest HP-UX 11.0 release, the steps do not support previously released media. If you have older media, check the following information. Make sure you have the correct core media for the hardware. Check these links to see that the system is referenced to verify that media supports the system: http://docs.hp.com/hpux/os/11.0
50
Chapter 1
Preparing for Software Migration Locating Source Media & Codewords for Migration
Locating Codewords
You can obtain a codeword for a purchased product by calling one of the following numbers. Table 1-5 HP Licensing Services Location Asia Telephone 0120.42.1231 (Inside Japan) 0426.48.9310 (Inside Japan) +81.426.48.9312 (Outside Japan) Europe North America +33 (0)4.76.14.15.29 (800)538-1733 codeword_europe@hp.com hplicensing.na@mayfield. hp.com Email sw_codeword@hp.com
NOTE
For more information on HP Licensing Services and codeword redemption, go to the web: http://licensing.hp.com The Codeword Request forms also list the telephone numbers and web site for codeword redemption.
Chapter 1
51
52
Chapter 1
To complete the steps in this chapter, we estimate you require 2-3 hours to cold install HP-UX 11.0, select drivers, and retrieve information. Please note that your time may vary. NOTE In this guide, the terms HP-UX 11.0 Install/Update/Recovery CD and HP-UX 11.0 Core OS CD are used interchangeably.
CAUTION
The cold-install process overwrites everything on the root (/) disk. Make sure you completed backups on tape or another system. See Backing Up the System on page 39.
Chapter 2
53
Review the Read Before Installing or Updating to HP-UX 11.0 (RBI) CD booklet.
The system automatically reboots after installing all selected software. Review the log files: /var/adm/sw/swagent.log /var/adm/sw/swinstall.log /var/adm/syslog/syslog.log
Boot from the HP-UX 11.0 Install/Update/ Recovery CD. Perform post-install tasks such as restoring files. Make software selections from the Ignite-UX menus. For example, select network and mass storage devices from which you want to boot.
IMPORTANT
Any last-minute install/update issues are provided in the Read Before Installing or Updating to HP-UX 11.0 CD booklet provided with the HP-UX 11.0 media. Be sure to review that document before continuing.
54
Chapter 2
Cold installing HP-UX 11.0 Reviewing the Cold-Install Process Is Your System Factory-ignited? If you received a new HP system, it may have HP-UX 11.0 (or HP-UX 11i) factory installed already; we call this "factory ignited". If so, the cold-install process has already been performed; you can skip this chapter and proceed to Chapter 5, Installing Patches and Applications, on page 99 to install any needed patches and application software. Be sure to review the other documents supplied with the HP-UX 11.0 media: HP-UX Release Notes Describes the HP-UX 11.0 release. This document is on your installed system in the /usr/share/doc/directory, on the HP Instant Information CD supplied with HP-UX, and on the web: http://docs.hp.com/hpux/os/11.0 Read Before Installing and Updating to HP-UX 11.0 Describes last-minute migration information that may apply to your system. It is the most recent information available for the current release. Ignite-UX Summary Provides the latest information on Ignite-UX; go to the Ignite-UX web site: http://software.hp.com/products/IUX Required Media Have the following CDs from the HP-UX 11.0 media box ready: HP-UX 11.0 Install/Update/Recovery CD For technical servers and workstations Core OS Options CD For technical servers and workstations Support Plus CD For Hardware Enablement, patch bundles, diagnostics, and iCOD, if needed
Chapter 2
55
56
Chapter 2
6. Ensure that Fast Boot is enabled. The full memory check run when Fast Boot is OFF may take several hours on a large system. a. Select the Configuration Menu: CO b. If the Fast Boot selection is available, switch Fast Boot ON: FB ON c. Return to the Main Menu: MA 7. Search for bootable devices, using the choices displayed (for example, enter search or sea). You may see a table similar to the following:
Path# ----P0 P1 P2 Device Path ----------SESCSI.2.0 LAN.1.2.3.4 .5.6 FWSCSI.6.0 Device Type ----------TOSHIBA CD-ROM 1.2.3.4 IBM DDRS-34560W
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. NOTE Depending on the firmware, you may see different output. 8. Boot from the CD drive using the listed path number. For the example shown previously, you would enter: BO P0 9. You'll be asked Interact with IPL? Enter: n The install kernel will load (takes 3-5 minutes). 10. A screen might ask you to enter the keyboard language of your console. Enter the number and press Return/Enter... and again to confirm. 11. 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 fields and the arrow keys to navigate within fields. Press Return/Enter to select an item. Pressing Return/Enter or the space-bar opens a menu list.
Chapter 2
57
Cold installing HP-UX 11.0 Cold installing HP-UX 11.0 To navigate more quickly, enter the underlined letter of an item (such as I for Install HP-UX).
12. If your plan to install HP-UX 11.0 on a disk connected via a PCI I20 RAID card, such as an HP A5856A, configure the card: a. Select: Advanced Options b. Select: Configure A5856A RAID 4Si cards c. Follow on-screen instructions to configure the RAID card. 13. From the installation/recovery Welcome screen, select: Install HP-UX From the User Interface and Media Options screen, verify that these choices are selected:
Source Location Options: Media-only installation installing from
wizard with limited choices. Select this 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, file-system characteristics, and other configuration details. You can exit Guided Installation and restart the configuration using Advanced Installation at any time by either selecting the Cancel button or pressing C. Make your choices and select OK. 14. Whether using Guided Installation or Advanced Installation, proceed through each screen to configure your system with one of the following: Default configuration Technical Computing configuration Commercial Servers configuration
Each configuration automatically selects the HWE1100 patch bundle required for all current and new hardware, including the latest HP servers and workstations supported on HP-UX 11.0. Technical Computing and the Commercial Servers configurations also match the HP Instant Ignition options with the current patch bundles and diagnostic products recommended for new HP systems. 58 Chapter 2
Cold installing HP-UX 11.0 Cold installing HP-UX 11.0 Install the HWE1100, QPK1100, and Diagnostics from the Support Plus media in the same install session to eliminate extra system reboots. The HP-UX 11.00 Default configuration includes the following: - HP-UX 11.0 core OS and Support Plus software - Required ACE 9911 patches in the XSWGR1100 bundle - Hardware enablement patches in the HWE1100 bundle The Technical Computing configuration includes the following: - HP-UX 11.0 core OS, Support Plus, and Core OS Options software - Required ACE 9911 patches in the XSWGR1100 bundle If you are prompted to use the Core OS Options CD, go to step 17. - Technical computing products in the TechSysConf bundle - Graphics software products in the B6268AA bundle - Hardware enablement patches in the HWE1100 bundle - Diagnostic products (with hardware monitors) - iCOD Product, B9073AA, for N-, L-, and V-Class servers The Commercial Servers configuration includes the following: - HP-UX 11.0 core OS and Support Plus software - Required ACE 9911 patches in the XSWGR1100 bundle - Hardware enablement patches in HWE1100 bundle - Diagnostic products with hardware monitors - iCOD Product, B9073AA for N-, L-, and V-Class servers
Software Selection: Select mass-storage and networking I/O driver
products; see Selecting Mass Storage and Network Drivers on page 61 in this chapter. If you install HP-UX 11.0 using add-on networking or mass storage devices, see Cold Installing over a Network on page 62.
Languages: Select 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.
15. If you are using Guided Installation, a screen allows you to review any messages that Ignite-UX encountered. If there are any errors, resolve them before continuing with the installation. 16. When finished configuring your installation: Chapter 2 59
Cold installing HP-UX 11.0 Cold installing HP-UX 11.0 With Guided Installation, select: Finish With Advanced Installation, select GO! (at the bottom of any tab). A confirmation 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 configuration screen.
After selecting Finish or GO!, the system configures the disk(s) and loads a minimum set of commands and libraries. Software Distributor then downloads all the products and patches from the CD. 17. If you are prompted for the Core OS Options CD, insert the CD and press Enter. 18. IF you are prompted to use the Support Plus CD, insert the CD and press Enter. 19. The system automatically reboots after all software has been loaded. Eject the CD. Be sure to store the CDs in a safe place. You may need them later to install other software. If prompted, replace the HP-UX 11.0 Install/Update/Recovery CD with the requested CD from the media box. Software will be automatically loaded from that 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. 20. If you specified Ask at first 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 mounts, file systems, and so forth after you log in. Changes to the kernel, such as adding devices, will require a reboot to enable them. Problems? If you encounter a problem during the cold-install process, first review Appendix B, Troubleshooting, on page 117 for possible solutions. Help is also available on the web: http://software.hp.com/products/IUX
60
Chapter 2
Cold installing HP-UX 11.0 Selecting Mass Storage and Network Drivers
Cold installing HP-UX 11.0 Selecting Mass Storage and Network Drivers Table 2-1 Mass Storage and Network I/O Drivers (Continued) Hardware/Software A5783A A5856A A6092A A6684A A6685A A6748A A6795A A6825A A6847A B5509BA J1642AA J2157B J2166B J3514A J3515A J3516A Description PCI Token Ring I2O RAID HyperFabric 9000/[78]00 HSC Fibre Channel HSC Fibre Channel PCI RS-232 MUX Software PCI Tachyon TL/TS/XL2 Fibre Channel 1000Base-T PCI Gigabit Ethernet Driver 1000Base-SX PCI Gigabit Ethernet Driver 100BT/9000 PCI HP PCI/HSC Gigabit Ethernet Driver Server FDDI/9000 Token Ring/9000 HPPB Series 800 100BT/9000 GSC for K and T Series 100BT/9000 GSC for B, C, D, and J Series 100BT/9000 GSC for B, C, D, and J Series
62
Chapter 2
Cold installing HP-UX 11.0 Selecting Mass Storage and Network Drivers necessary drivers will prevent your system from booting from the networking or mass storage device after completion of the HP-UX 11.0 cold install. Booting from a boot device connected via a Fibre Channel fabric switch is not supported. Connect the boot device directly to the system using one of the available Fibre Channel cards listed in Table 2-1, Mass Storage and Network I/O Drivers, on page 61.
Chapter 2
63
NOTE
The Support Plus bundles are available via CD and the web. For more details and to download recent bundles, go to the web: http://software.hp.com/SUPPORT_PLUS
64
Chapter 2
Recover Files
Recover all customized and personal files 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 files or merge the old information into the new files.
Restore /home
If you had a local home directory, you can restore it as follows: If you copied it to /backup/joe/home, enter these commands: cd /backup/joe/home find . -depth -print | cpio -pdum /joe/home
Chapter 2
65
Cold installing HP-UX 11.0 Retrieving Information after Cold installing If you backed it up to tape with fbackup: frecover -x -i /joe/home -v
66
Chapter 2
Chapter 2
67
68
Chapter 2
To complete the steps in this chapter, we estimate you require 10-15 hours to perform more pre-update tasks, update the system, update bundles and patches, and enable hardware. Please note that your time may vary.
NOTE
In this guide, the terms HP-UX 11.0 Install/Update/Recovery CD and HP-UX 11.0 Core OS CD are used interchangeably.
Chapter 3
69
Consider updating If you are running HP-UX 10.20, please consider updating to HP-UX 11i to HP-UX 11i rather than HP-UX 11.0. HP-UX 11i provides a single-command update from HP-UX 10.20 that allows you to install the OS, network drivers and other selected software bundles from the HP-UX 11i Operating Environment CDs, typically with a single reboot. For more information about HP-UX 11i, go to the web: http://docs.hp.com/hpux/os/11i http://devresource.hp.com/STK/hpuxoverview.html IMPORTANT Any last-minute install/update issues are provided in the Read Before Installing or Updating to HP-UX 11.0 CD booklet provided with the HP-UX 11.0 media. Be sure to review that document before continuing.
70
Chapter 3
If installing 64-bit OS, check for /etc/.supported_bits file. If not found, install file via patch PHCO_23169 (or superseded patch) and verify: grep $(/usr/bin/model) /etc/.supported_bits
If running 10.01 and plan on using swinstall GUI, verify the presence of PHSS_18011 (or superseded patch).
If running 10.20, check for and remove PHKL_16498 and/or PHKL_16499 (or superseded patches). If you removed patches, regenerate kernel with mk_kernel.
Verify that no 10.x patch information remains with swlist. If needed, remove patch information with clean-up utility.
Chapter 3
71
Pre-Update Tasks
Updating should typically only be used when adequate time can be devoted to the update (especially in the planning stages), when there are only a few systems to bring to HP-UX 11.0 or in cases like a desktop application, where application data resides in the root VG that cannot be easily restored. Prior to updating to HP-UX 11.0 from HP-UX 10.01, 10.10 or 10.20, first perform the procedures detailed in the following pages: If the system is already patched, remove information about prior patches. This does not involve the use of swremove. See Removing Information about Prior Patches on page 48. Mount the HP-UX 11.0 Install/Update/Recovery CD. Update the SD toolset, swgettools, from the new OS media. Do not attempt to use your present version of swinstall to update the system to a newer version. The update will fail. Export the PATH to SD-UX executables. If you are planning to use your system in 64-bit mode, test for presence and version of the /etc/.supported_bits file. See Updating to 64-bit Operation on New Systems on page 152.
Once these preparations have been completed, your update from HP-UX 10.x to HP-UX 11.0 in 32-bit or 64-bit mode should proceed smoothly.
72
Chapter 3
Chapter 3
73
Start Task
1. Run this command to prevent some system configurations from hanging later in the procedure: /usr/sbin/swremove SW-DIST.RUPDATE 2. If needed, mount the CD drive as explained above. Then extract the swgettools utility from the HP-UX 11.0 Install/Update/Recovery CD and load it into /var/tmp: cp /cdrom/catalog/SW-GETTOOLS/pfiles/swgettools /var/tmp 3. swgettools needs a temporary directory with at least 2 MB of free space or it will fail. To check the size of /var/tmp: bdf /var/tmp 4. To make swgettools executable, enter: chmod 775 /var/tmp/swgettools 5. Load SD 11.0 tools onto your system: /var/tmp/swgettools -s /cdrom Ignore any messages relating to software compatibility.
74
Chapter 3
Setting PATH
Before updating to HP-UX 11.0, enter: export PATH=/usr/lbin/sw/bin:$PATH This ensures that the SD-UX executables will be found. For more information, see the swgettools(1M) manpage or Managing HP-UX Software with SD-UX.
Chapter 3
75
76
Chapter 3
Updating to HP-UX 11.0 Updating from HP-UX 10.x to HP-UX 11.0 Update from HP-UX 10.01 or 10.10 Start Task Before updating from HP-UX 10.01 or 10.10, you need to remove the CDE fileset. After updating, you can remove the X11 products associated with HP-VUE. Follow these steps: 1. Remove most of the information about prior patches, as explained on Removing Information about Prior Patches on page 48. 2. Complete the removal of information about prior patches by executing this swmodify command: swmodify -u ExtSWDocs.XSW\* ExtSWDocs \ PatchText.\* PatchText 3. If you are running HP-UX 10.10, remove the CDE-LANG fileset: /usr/sbin/swremove [-p] CDE.CDE-LANGS You can use the -p option to preview the analysis phase. 4. Update to HP-UX 11.0 by following the appropriate next section, Updating Using the Command Line on page 79 or Updating Using SD-UX Interactively on page 80". Update from HP-UX 10.20 to HP-UX 11.00 Before updating to HP-UX 11.00, you must update the Software Distributor to the HP-UX 11.0 version using the following steps: 1. Mount the HP-UX 11.0 Install/Update/Recovery CD: cp /cdrom/SW-DIST/catalog/pfiles/swgettools /var/tmp /var/tmp/swgettools -s /cdrom 2. Use the correct swinstall syntax for the 32-bit version of HP-UX 11.0, enter: /usr/sbin/swinstall -x logdetail=true \ -x allow_incompatible=false \ -x autoreboot=true -x match_target=true \ -x reinstall=true -x reinstall_files=true \ -x os_name=HP-UX:32 -x os_release=B.11.00 \ -s /cdrom 3. Tab to the actions menu and select Match What Target Has. 4. Upon completion of the match operation tab to actions. 5. Select Install analysis. Chapter 3 77
Updating to HP-UX 11.0 Updating from HP-UX 10.x to HP-UX 11.0 6. Evaluate all errors and warnings from the analysis. 7. Proceed with install. NOTE To install a 64-bit operating system, replace os_name=HP-UX:32 with os_name=HP-UX:64 in the swinstall command. You can include the -p option in the swinstall command to preview what will be installed.
Before updating to HP-UX 11.0 from 10.20, remove patch PHKL_16498 on workstations and PHKL_16499 on servers. For details, see the HP-UX 10.20 Patch Causes Kernel Build Failure on page 146. 1. Determine if this patch is on your system, by executing the following command: /usr/sbin/swlist -l product PHKL_16499 2. If PHKL_16499 is installed, remove the patch: /usr/sbin/swremove -x autoreboot=true PHKL_16499 3. Regenerate the kernel with the mk_kernel command. Then update the system using either the command line or SD-UX user interface, as explained in following pages. Now proceed to update to HP-UX 11.0, using either the swinstall command-line interface (see Updating Using the Command Line on page 79) or SD-UX (Updating Using SD-UX Interactively on page 80).
78
Chapter 3
Chapter 3
79
80
Chapter 3
Updating to HP-UX 11.0 Updating from HP-UX 10.x to HP-UX 11.0 To install a 64-bit operating system, replace os_name=HP-UX:32 with os_name=HP-UX:64 in the swinstall command. You can include the -p option in the swinstall command to preview what will be installed. 2. Fill in the Source Screen: Specify the source depot type, which by default is shown as Local. If you are accessing the CD via the network, select the source depot type option button to display Network Directory /cdrom. If needed, enter the Source Host Name... To list the valid source depot paths on the source host name, select the left-hand box labeled Source Depot Path... and select from the list that appears. Select OK to view the Software Selection screen. 3. You must match the general filesets and functionality you already have on your system. Select Actions -> Match What Target Has. By default, SD automatically selects the proper set of patches for your new operating system. You may choose additional items by highlighting them for install via the Actions menu or by using the right mouse button. 4. Select: Options -> Change Options. In the window provided, select these two choices:
Reinstall filesets, even if same revision exists Reinstall files even if same one already there
These are the equivalent to the swinstall -x options reinstall=true and reinstall_files=true. Confirm the changes by selecting the OK buttons to return to the main install window. 5. Select: Actions -> Install (Analysis) Do not press the Logfile button in the terminal interface; closing that window in HP-UX 11.0 is only available in the graphical interface (GUI). SD-UX analyzes the build. Once the analysis completes, you can view the log file, which is a product summary describing the elements ready (or skipped) for installation, and disk space impact on all affected file systems. Chapter 3 81
Updating to HP-UX 11.0 Updating from HP-UX 10.x to HP-UX 11.0 When using the interactive mode, if the analysis reports that disk space for a system directory is too small, use SAM to extend its logical volume and file system. If the program reports errors, read the log file to resolve them before proceeding. You may then re-analyze the installation. When you are satisfied with the selection, press OK to begin the installation. 6. Approve the series of confirmations (including Done). 7. Log in to the system after the reboot. Once you log in, review the files: /var/adm/sw/swagent.log and /var/adm/sw/swinstall.log 8. If needed, remove information about HP-UX 10.x patches, as explained next.
82
Chapter 3
Start Task
1. To determine if you have any of these patches, enter: swlist -l product -a architecture PH\?\?\_\* >filename Every product listed in filename with a revision indicating HP-UX 10.x, is a HP-UX 10.x patch that has been applied. The obsolete software replaced by each patch is still on the system. You can reclaim the disk space taken up by the obsolete software by following the directions detailed in Removing Information about Prior Patches on page 48. Do not use swremove to remove HP-UX 10.x patches. 2. Use the cleanup utility to remove patch information. For example: /usr/sbin/cleanup -i The cleanup command on HP-UX 11.0 removes HP-UX 10.x patches from the IPD and removes superseded patches from the software depot. For more details see the cleanup(1M) manpage. The cleanup command is available as a patch via the web from HP's IT Resource Center: http://itrc.hp.com
NOTE
Chapter 3
83
1. Insert the Support Plus CD into the CD drive: a. Put the CD into the drive. b. Make sure the CD drive is mounted: /usr/sbin/mount /dev/dsk/device_file /cdrom 2. To install the latest patch bundles: /usr/sbin/swinstall \ -x patch_match_target=true \ -x autoreboot=true \ -s /cdrom This command installs all patches in the depot that apply to your system and then reboots. Be sure to specify patch_match_target, not match_target.
To use the swinstall terminal or graphical interface: 1. Mount the Support Plus CD into the CD drive. 2. Start swinstall: /usr/sbin/swinstall -i -s /cdrom 3. Fill in the Source Screen: a. Specify the source depot type, which is shown as Local CD by default. If you are accessing the CD via the network, select the right-hand box to display Network Directory /cdrom. b. If needed, enter the Source Host Name...
84
Chapter 3
Updating to HP-UX 11.0 Updating from HP-UX 10.x to HP-UX 11.0 c. To list the source depot paths on the source host name, select the left-hand box labeled Source Depot Path... and select from the list that appears. Select: Actions -> Manage Patch Selection -> Automatically Select Patches... Press OK. A confirmation message will appear indicating that SD-UX will automatically mark patches that correspond to the software already installed on the target system.
4. Select: Actions -> Install (Analysis) Do not press the Logfile button in the terminal interface; access to close that window on HP-UX 11.0 is only available in the graphical interface. SD-UX analyzes the build. Once the analysis completes, you can view the logfile, a product summary describing the elements ready (or skipped) for installation, and disk space impact on all affected file systems. When using the interactive mode, if the analysis reports that disk space for a system directory is too small, extend its logical volume and file system. If the program reports errors, read the logfile and resolve them before proceeding. You may then re-analyze the installation. When you are satisfied with the selection, press OK to begin the installation. 5. Approve series of confirmations (including Done). 6. Log in to the system after the reboot. Once you log in, review the files: /var/adm/sw/swagent.log and /var/adm/sw/swinstall.log
Chapter 3
85
86
Chapter 3
NOTE
The Support Plus bundles are available via CD and the web. For more details and to download recent bundles, go to the web: http://software.hp.com/SUPPORT_PLUS
Chapter 3
87
88
Chapter 3
Chapter 3
89
90
Chapter 3
To complete the steps in this chapter, we estimate you require 2-3 hours to verify the HP-UX installation, applications, and patches. Please note that your time may vary.
TIP
This chapter provides verification information for the HP-UX installation, applications, and patches. To check other software patches and applications, please refer to the appropriate vendor documentation.
Chapter 4
91
2. Run swverify to verify that each bundle is intact. Several examples follow: To verify that an installed English 32-bit HP-UX 11.0 OS is intact, enter the command: /usr/sbin/swverify HPUXEng32RT To verify all HP software on your system, enter the command: /usr/sbin/swverify \* The Selection process locates all required filesets for the product. After the list, the following message displays: * Selection succeeded. Then, the Analysis process verifies that each required file is loaded (existence and revision), all required dependencies are met, and runs any available verification scripts for the product. After the analysis, the following message displays: * Analysis succeeded. If you do not get the Selection and Analysis messages, then the software most likely needs to be installed or updated. Go to Updating HP-UX Applications on page 94.
92
Chapter 4
TIP
For help with these commands, see the swlist (1M) and swverify (1M) manpages, and the Managing HP-UX Software with SD-UX manual, which is available on the HP-UX Instant Information CD or the web: http://docs.hp.com/hpux/os/11.0
Chapter 4
93
94
Chapter 4
Chapter 4
95
Verifying System Migration Changing the State of HP-UX Installed Patches The superseded patch was installed from the November 1999 ACE Bundle, XSWGR1100 (B.11.00.47.08). The applied patch was installed from the HWE1100 bundle for the March 2002 release. NOTE Superseded patches left in an installed SD state do not cause any problems, but they require an extra swconfig step when they become the current applied patch. 2. In the previous example, removing PHCO_23876 results in PHCO_17792 with an installed SD state and an applied patch state, since PHCO_17792 was not previously configured. HP recommends that you configure a current applied patch in the installed SD state with the following command: /usr/sbin/swconfig <patch_number> For example, swconfig PHCO_17792 CAUTION This problem only exists when an active patch is removed and rolled back to a superseded patch left in an installed state. Executing swconfig on a patch in the superseded patch state is dangerous; do not do it. 3. Use the following options to list active products, patches, and states: swlist -l fileset -a state -a patch_state \ -x show_superseded_patches=false The previous swlist options will display all active (non-superseded) filesets with their SD software state" and "patch state" attributes. For example:
# Accounting Accounting.ACCOUNTNG Accounting.ACCT-ENG-A-MAN # AgentConfig AgentConfig.MX-CONFIG AgentConfig.SCR-CONFIG AgentConfig.SD-CONFIG ... # PHCO_12555 PHCO_12555.UX-CORE configured configured configured configured configured configured applied
96
Chapter 4
You can change swlist to not display superseded patches by adding the following line to the /var/adm/sw/defaults file: swlist.show_superseded_patches=false TIP For help with these commands, see the Managing HP-UX Software with SD-UX manual, which is available on the HP-UX Instant Information CD and on the web: http://docs.hp.com/hpux/os/11.0
Chapter 4
97
98
Chapter 4
To complete the steps in this chapter, we estimate you require 1-2 hours per patch and 1-2 hours per application. Please note that your time may vary.
TIP
This chapter provides installation information for HP-related patches and applications only. To install or upgrade other vendor patches and applications, please refer to the appropriate vendor documentation. There are patching resources available on the HP web site: http://docs.hp.com/hpux/os/11.0/ \ index.html#Patch%20Management
Chapter 5
99
100
Chapter 5
Installing Patches and Applications Installing Individual Application Patches Select the site (americas/asia pacific or european). Select the maintenance and support page, then select the appropriate patching tools. To receive HP Security Bulletins, select the maintenance and support page, then select support information digests.
Chapter 5
101
102
Chapter 5
4. To find out which patches are in a specific category tag, use swlist. For example, to list the patches (by product name) for all patches categorized as hardware enablement, enter the command: /usr/sbin/swlist -d -l product *,c=hardware_enablement \ @ host:depot NOTE If you are running HP-UX 10.x, you need to load the HP-UX 11.0 SD-UX tools before you can access the patches. See Updating the SD Toolset (swgettools) on page 74 to install the swgettools utility.
However, after you used the Support Plus media or swinstall command, other critical or required patches may have become available. You should check on a regular basis to see if Hewlett-Packard has released any new, critical patches. Start Task To check regularly to ensure that your system is up to date, look for additional critical patches on the HP IT Resource Center web site. 1. Go to the web: http://itrc.hp.com 2. Select the site (americas/asia pacific or european). Select the maintenance and support page, then select the appropriate patching tools. 3. To receive HP Security Bulletins, select the maintenance and support page, then select support information digests. Chapter 5 103
TIP
There are two ways you can easily keep your OS and HP-UX applications up to date: subscribe to HP-UX Support Plus Services and use the Patch Management Tools: HP-UX Support Plus Services periodically delivers critical patches and general release patches to you. Instructions for installing patch bundles are provided on the web. See the Support Plus web page: http://software.hp.com/SUPPORT_PLUS Patch Management Tools are available from the HP IT Resource Center web site: http://itrc.hp.com
104
Chapter 5
NOTE
HP provides an Availability Matrix Overview for HP-UX releases. Go to the web: http://software.hp.com/MATRIX
Using Ignite-UX
You can use the Ignite-UX utility to install HP-UX applications on systems using a local mount directory, or over a network using an Ignite-UX server. Ignite-UX is an HP-UX product that facilitates installing and configuring HP-UX systems.
Chapter 5
105
Installing Patches and Applications Tips for Updating HP Applications See the Ignite-UX Administration Guide for detailed instructions on how to install HP-UX applications. It is on the HP-UX Instant Information CD and on the web: http://docs.hp.com/hpux/os/11.0 Ignite-UX can address your need to perform system installations and deployment, often on a large scale. With Ignite-UX, you can do the following: Create and reuse standard system configurations. Archive a standard system configuration and use that archive to replicate systems in far less time than with other methods. Create customized processes to allow interactive and unattended installs. Recover OS and applications more easily after crashes and hardware failures.
For example, you can install the Ignite-UX utilities to install HP-UX and applications on other systems: 1. Mount the HP-UX Applications CD containing Ignite-UX (mount point is assumed here to be /cdrom) and enter the command: /usr/sbin/swinstall -s /cdrom B5725AA 2. After installing the software, see the Ignite-UX release notes and Ignite-UX Administration Guide to complete any post-install steps and configuration. After running an Ignite-UX install session, you have a working HP-UX client system.
106
Chapter 5
Chapter 5
107
108
Chapter 5
For the remaining CDs, you can find the contents by looking at the CD_TABLE_OF_CONTENTS file on the CD: HP Applications (5 CDs): HP-UX Application Software CDs Documentation (1 CD): HP-UX 11.0 Instant Information CD
For the latest information on the HP-UX software releases, go to the web: http://software.hp.com/RELEASES-MEDIA NOTE In HP documentation, the terms HP-UX 11.0 Install/Update/Recovery CD and the HP-UX 11.0 Core OS CD are used interchangeably.
Appendix A
109
Exploring the HP-UX 11.0 CDs Whats on the HP-UX 11.0 Install/Update/Recovery CD?
110
Appendix A
Exploring the HP-UX 11.0 CDs Whats on the Core OS Options CD?
GraphicsSBaseDK
GraphicsPHIGSRT GraphicsPHIGSDK
GraphicsPEX5RT GraphicsPEX5DK
Appendix A
111
Exploring the HP-UX 11.0 CDs Whats on the Core OS Options CD? Table A-2 Core OS Options Bundles (Continued) Bundle Name TechSysConf Description Technical System Configuration This bundle contains software to modify kernel parameters and other system and networking parameters to increase performance of HP technical workstations and servers and delivers useful open source tools. The TechSysConf bundle includes the following SD products: TC-SysSetup: Tunes system, networking, and system parameters. TC-OpenSource: Delivers standard open source tools useful in a technical environment
Exploring the HP-UX 11.0 CDs Whats on the Core OS Options CD? Ignite-UX Software tab. This will give you the most recent updates to the OS, and eliminate any error messages caused by trying to install the newer graphics bundle. If you have questions about your particular situation, please contact your local HP Country Response Center. Beginning with the September 2002 update to HP-UX 11.0, HP has created the Technical System Configuration (TechSysConf) bundle that contains two products, one which modifies kernel, system, and networking parameters to tune technical workstations and technical servers and one which provides a collection of open source tools. HP strongly recommends installation of the TechSysConf bundle (specifically the TC-SysSetup product) to improve performance of all technical workstations and servers. The TechSysConf bundle consists of two component products: TC-SysSetup Alters kernel configurable parameters by assigning values that are proven to increase performance in technical environments. Alters selected system configuration files to ease NFS, AutoFS, and NIS+ configuration. Makes other system changes to improve operability. TC-OpenSource Contains the following Open Source software tools: bash 2.04 The Bourne-Again Shell emacs 20.7 GNU Emacs gmake 3.79.1 GNU make less 358GNU less tcsh 6.10 tcsh (a superset of C-shell) vim 5.7 Vi IMproved xcdroast 0.98alpha9 X-CD-Roast
Appendix A
113
Exploring the HP-UX 11.0 CDs Whats on the Core OS Options CD?
114
Appendix A
Exploring the HP-UX 11.0 CDs Whats on the HP-UX 11.0 Support Plus CD?
Appendix A
115
Exploring the HP-UX 11.0 CDs Whats on the HP-UX 11.0 Support Plus CD?
116
Appendix A
Troubleshooting
Troubleshooting
This appendix describes the following topics: Common Install and Update Errors on page 118 Intermittent sendmail Problem on page 119 Adjusting File System Sizes on page 120 Problems with Large Systems on page 125 Un-installing HP-UX 11.0 on page 126 Re-installing SD on page 127 Installing Diagnostic Drivers on page 128 Installing and Updating Requirements on page 129 Disk Space, Memory and Diagnostic Requirements on page 130 Security Situations on page 134 Hardware and Firmware Requirements on page 136 Application and Compiler Requirements on page 139 General Requirements on page 142 Updating between 32-bit and 64-bit OS on page 152 BIND 8.1.2 Notice on page 160
When troubleshooting a problem with installing or updating to HP-UX 11.0, be sure to review the Read Before Installing or Updating to HP-UX 11.0 CD booklet. A copy of the latest version is also available on the web: http://docs.hp.com/hpux/os/11.0 Other helpful installation resources on the web: http://devresource.hp.com/STK/hpux_faq.html http://software.hp.com/products/IUX
Appendix B
117
If you see a message or experience unusual behavior, see the pages in this appendix for likely solutions.
118
Appendix B
An error message similar to the following is generated: 554 Switch map aliases: unknown member map aliases.nis
Start Task
1. Stop the sendmail daemon: /sbin/rc2.d/S540sendmail stop 2. Restart the sendmail daemon: /sbin/rc2.d/S540sendmail start Mail delivery should resume and the error should not occur again.
Appendix B
119
120
Appendix B
The Free PE indicates the number of 4 MB extents available, in this case 79 (equivalent to 316 MB). 2. Change to single user state: /sbin/shutdown This allows /var to be unmounted. 3. View mounted volumes: /sbin/mount You see a display similar to the following:
/ on /dev/vg00/lvol1 defaults on Sat Mar 8 23:19:19 1997 /var on /dev/vg00/lvol7 defaults on Sat Mar 8 23:19:28 1997
4. Determine which logical volume maps to /var. In this example, it is /dev/vg00/lvol7 5. Unmount /var: /sbin/umount /var This is required for the next step, because extendfs can only work on unmounted volumes. If you get a "device busy" error at this point, reboot the system and log on in single-user mode before continuing. 6. Extend the size of the logical volume: /sbin/lvextend -L new_size_in_MB /dev/vg00/lvol7 For example, to make this volume 332 MB: /sbin/lvextend -L 332 /dev/vg00/lvol7 7. To extend the file system size to the logical volume size: /sbin/extendfs /dev/vg00/rlvol7
Appendix B
121
8. Mount /var: /sbin/mount /var 9. Go back to the regular init state: init 3 or init 4, or reboot. 10. Wait 10 minutes after changing the system state or rebooting to let processes complete before running SD-UX commands. Increase /stand In some cases, you need to increase the size of /stand to successfully update to HP-UX 11.0. If the update fails with a message indicating that /stand is too small, follow these steps to increase the size of /stand. To increase /stand, you first have to create a larger /swap volume, because both require contiguous blocks and are adjacent volumes. Help with this procedure is in the Managing Systems and Workgroups manual available on the HP-UX Instant Information CD and on the web: http://docs.hp.com/hpux/os/11.0 Start Task 1. As root, use SAM to create a new contiguous /swap volume of the required size, for example, 300 MB. Name the new volume /dev/vg00/swap. 2. Using SAM, verify that there is no bad block relocation and the new /swap volume is contiguous. 3. As root from a console window, remove and add primary swap and dump devices: a. Remove the current dump device: lvrmboot -v -d lvol2 /dev/vg00 b. Add a new dump device: lvlnboot -d /dev/vg00/swap c. Remove the current swap device: lvrmboot -s /dev/vg00 d. Add a new swap device: lvlnboot -s /dev/vg00/swap
122
Appendix B
5. If your changes are correct, reboot the system. 6. After the system reboots, view swap information: swapinfo
Kb Kb TYPE AVAIL dev 307200 reservememory 85584 Kb PCT START/ Kb USED FREE USED LIMIT RESERVE PRI NAME 45936 216208 0% 0 1 /dev/vg00/swap 113748 -113748 23492 62092 27%
7. To verify that the same configuration exists as before the reboot, enter (again): lvlnboot -v 8. As root, use SAM to remove the old lvol2 entry from /dev/vg00. 9. Using SAM, increase /stand to the required new size. Also change the size of any other volumes as needed. 10. Define your new volume as the boot volume before the next reboot: lvlnboot -b lvol1 /dev/vg00 11. Reboot your system again. 12. Return to Chapter 3, Updating to HP-UX 11.0, on page 69 to update your system to HP-UX 11.0.
Appendix B
123
An easy way to increase the size of the root (/) volume is by using Ignite-UX's make_recovery commands. First make a recovery (backup) archive of your root volume using make_recovery, make_tape_recovery, or make_net_recovery. Then interact with the recovery menu to change the root volume size when recovering the system from the archive. For more details, see the Ignite-UX Administration Guide, available on the Instant Information CD and on the web: http://docs.hp.com/hpux/os/11.0
124
Appendix B
The boot may fail in other ways. For example, you may have to repair the file system manually: The kernel may need to be re-configured before booting. The following settings should allow the kernel to be booted, but may not be optimal for performance:
ninode = 2048 (default is 476) nproc = 1024 (default is 276) nfile = 2048 (default is 790)
Alternatively, you may re-configure the kernel using one of these methods: Select an appropriate bundle of SAM-tuned parameters from SAM's kernel configuration Actions menu. Raise maxusers to a large value, such as 200.
Appendix B
125
To determine what applications are on the system and where they are located, use swlist. If you only need to remove applications or patches from the system, use swremove. See the Managing HP-UX Software with SD-UX manual for details.
126
Appendix B
Troubleshooting Re-installing SD
Re-installing SD
If your system needs re-updating and/or you find that Software Distributor (SD) needs updating, you must re-install SD. This is explained in the Managing Software with SD-UX manual, available on the HP-UX Instant Information CD and on the web: http://docs.hp.com/hpux/os/11.0
Appendix B
127
128
Appendix B
IMPORTANT
To prevent problems when updating, you must install the latest version of Ignite-UX on your Ignite-UX server(s). Installing this latest version on your Ignite-UX servers ensures that HP-UX 11.0 and HP-UX 10.20 ACE installations will be successful for all HP workstations under all conditions. This version also fixes other problems in the Ignite-UX version supplied on HP-UX Applications CDs.
Appendix B
129
Troubleshooting Disk Space, Memory and Diagnostic Requirements To determine the available megabytes, multiply the value for Free PE by 4. If the needed space is not available, add another disk or volume group. 3. See where /usr is mounted: /usr/sbin/mount 4. Extend the logical volume. For example: /usr/sbin/lvextend -L 600 /dev/vg00/lvol8 If needed, change the volume group and logical volume number above to reflect your /var block device. 5. Extend the mounted file system: /usr/sbin/fsadm -Fvxfs -b 614400 /usr (assuming the default 1KB file system block size) HFS File System On an HFS file system (with LVM), increase the size of the /usr partition as follows: 1. Execute bdf to check the size of the /usr partition. 2. Write down the volume name (for example, /dev/vg00/lvol7). 3. Reboot. Answer Yes to the ISL prompt. Then boot single-user mode by entering: hpux -is 4. Run: /sbin/lvextend -L 600 /dev/vg00/lvol7 /sbin/extendfs -F hfs /dev/vg00/rlvol7 5. Bring system to multi-user mode: init 3
132
Appendix B
2. To increase the size of eqmemsize: a. Run SAM and go to Kernel Configuration, then to Configurable Parameters. b. Double the default value of eqmemsize, from 15 to 30. c. Select: Actions -> Process New Kernel. Confirm that you want to reboot the system when prompted.
Appendix B
133
Security Situations
Applications on Trusted Systems
Your system is a Trusted System if the /tcb directory exists and your /etc/passwd file has an asterisk (*) in the password field for each entry. Situation HP has expanded 16-bit user IDs (used by Trusted Systems) to 32 bits. These IDs (defined in the prot.h file) are used by the setprpwent(3) and getprpwent(3) library routines. This is true whether the library routines were linked "shared" (bound at run-time) or "archived" (bound at link time). Applications that were compiled on HP-UX 10.0, 10.01 or 10.10 that use these calls will not run correctly on HP-UX 11.0. Applications compiled on HP-UX 10.0, 10.01 or 10.10 and that use setprpwent or getprpwent must be recompiled on a HP-UX 11.0 system before they can run. Applications that can run on a Trusted System might not call setprpwent or getprpwent explicitly, but those that check the user's ID, explicitly or silently, probably do. Fix any source code you own or develop in-house. For third-party applications, contact the software supplier.
What To Do
134
Appendix B
Appendix B
135
Troubleshooting Hardware and Firmware Requirements To download the latest VME embedded system, do the following: 1. Go to the web: http://www.hp.com/products1/vmesystems/index.html 2. Select the appropriate model. 3. Select the Information Page menu. 4. Download the item. To install the VME Services, go to the web: http://www.hp.com/products1/vmesystems/support/vme_services_ 11.html
Start Task
Before you can use the new graphics hardware, you must configure the graphics graph3 driver: 1. Use SAM to configure the graphics driver into the HP-UX kernel. Select: Kernel Configuration -> Drivers If the graph3 driver's current state is In, the driver is already configured into your kernel. If the current state is Out, select the graph3 driver entry. Select: Actions -> Add Driver to Kernel 2. You can now reconfigure the kernel and reboot. Before HP-UX 10.0, the graphics driver was always configured into the operating system kernel. But as of HP-UX 10.0, the graphics driver could be removed from systems lacking graphics display hardware. If graphics hardware is installed later, you must configure the graphics driver into the kernel before it can be used.
Appendix B
137
Start Task
138
Appendix B
Appendix B
139
Here are descriptions of the library changes that were implemented: C++ applications can now access files greater than 2 GB. This is done by setting _FILE_OFFSET_BITS to 64 in 32-bit mode. Header files ftw.h and stdio.h were patched to enable this functionality. More details can be found in the HP-UX Large Files White Paper, in /usr/share/doc/lg_files.txt libc support for HP CxDL Development tool is included in the setjmp/longjmp() family of APIs in both 64-bit and 32-bit libc. A patch for the NIS files backend library (libnss_files.1) has been created to increase performance of gethostent() and related APIs in kernel threads environment. A new patch for the dbm libraries (libdbm.1 and libndbm.2) has been created to increase performance of dbm_nextkey().
140
Appendix B
Troubleshooting Application and Compiler Requirements If you do not specify -Ac, -Aa, or -Ae, and your C source code contains constructs that are not valid in Extended ANSI mode, your build will fail due to compile-time errors. If you do not specify -Ac, -Aa, or -Ae, and your C source code contains constructs whose semantics are different in Extended ANSI mode, then your application or library may behave differently.
Start Task
If the compiler mode (-Ac, -Aa,-Ae) had not been specified in the past, do one of the following: If you rely on compatibility mode syntax or semantics, or want to eliminate any risk, specify the -Ac flag on all compiles. This will revert the compiler to the old default behavior. Or... If you can compile your code successfully, but are worried about semantic differences that may result in even subtle run-time behavior changes, compile your code with the -Ac or -Ae option and the +M option.
The +M option will cause the C compiler to produce warnings for all source constructs whose semantics change from compatibility to ANSI mode. You will then have to examine each of those warnings and possibly change the source code that each warning describes. The differences between compatibility and ANSI modes are documented throughout the HP C/HP-UX Language Reference Manual and in the HP C/HP-UX Programmer's Guide.
Appendix B
141
General Requirements
CDE Desktop's X11 Server May Not Start After Update to 11.0
Update Situation If you are updating from HP-UX 10.01, 10.10, or 10.20, the X11 server for the CDE desktop may not start on the display device. If this occurs, you will still be able to use the console, but without the graphical user interface. The following text will appear in /var/dt/Xerrors:
date error (pid pid): Server unexpectedly died date error (pid pid): Server for display DISPLAY:0 can't be started. Fatal server error: Failed to establish all listening sockets
Why this Happens This error occurs when the nobody entry in /etc/passwd has a group ID of 60001 and either /var or /tmp is a JFS Version 2 file system. If you are updating from HP-UX 10.01 or 10.10 and have configured /var or /tmp as JFS, they will be JFS Version 2 file systems. Large files and JFS Version 2 are incompatible because the 11.0 kernel does not support large UID files (group ID > 59999). In HP-UX 11.0, when CDE desktop starts up the login daemon, it uses the nobody account. Typically on HP-UX 10.01 and HP-UX 10.10 systems, nobody has a GID greater than 59999 and remains unchanged when you update to HP-UX 11.0. The daemon process will try to create a temporary file in /var/spool. If /var is Version 2, the large GID causes the file creation to fail, which in turn, prevents the X server from starting. HP-UX 10.20 and subsequent releases are shipped with JFS Version 3 capability, but JFS Version 2 file systems on the system may still be present. When updating to a new release, HP-UX preserves the JFS version of existing file systems: JFS Version 2 file systems remain as Version 2, but any new JFS file systems will be created as Version 3.
142
Appendix B
Troubleshooting General Requirements Start Task You need to convert the JFS file system from Version 2 to Version 3. If you are updating from HP-UX 10.01 or 10.10, because the conversion can only be done after updating to HP-UX 11.0. (The conversion tool, vxupgrade, is a JFS Version 3 command.) If you are updating from HP-UX 10.20, you can do the conversion before updating to HP-UX 11.0.
To proceed: 1. Determine the version of JFS file system used by /var and /tmp by using fstyp -v on the appropriate block device; see fstyp(1M). The output shows the JFS version. For example, fstyp -v /dev/vg00/rlvol8vxfs version:3... You can get the name of the block device by running bdf; for example: bdf /var 2. If either /var or /tmp are JFS Version 2, use one of the following solutions: On the HP-UX 10.x system (that is, before updating to HP-UX 11.0), change the UID and GID entries for user nobody in /etc/passwd to -2, to match the 11.0 default settings. For example: nobody:*:-2:-2::/:
Appendix B
143
CAUTION
Conversion from JFS Version 2 to 3 is irreversible. JFS Version 3 file systems are incompatible with HP-UX 10.01 and 10.10, and cannot be mounted on a system running HP-UX 10.01 or 10.10. A JFS version 3 file system can only be mounted on a system with release HP-UX HP-UX 10.20 or later. 3. To convert /var and /tmp to JFS version 3 file systems: /sbin/vxupgrade -n3 /var /sbin/vxupgrade -n3 /tmp The X11 server should now start.
HP VUE/CDE Migration
Update Action You have the option of migrating HP VUE customizations to CDE using the VUEtoCDE utility. The options below describe the steps to take depending on whether or not you choose to migrate. Option 1: No migration of VUE customizations After the update has completed, remove VUE and MPower (which are not supported in HP-UX 11.0). Check with all users to find out if they want to migrate their VUE customizations to CDE before running the Uninstall HP VUE action from the System_Admin folder in the appmanager.
144
Appendix B
Troubleshooting General Requirements Option 2: Migrating VUE customizations During the update process, select the VUEtoCDE product. The first time you log in after the update has completed, the VUEtoCDE dialog pops up. Select the appropriate actions. Refer to the HP CDE Getting Started Guide for more information on using the VUEtoCDE utility. After the migration is completed, run appmanager's Uninstall HP-VUE action in the System_Admin folder to remove HP VUE and MPower. Systems with no Graphics Console Update Requirement If you have a system with no graphics console and want to remove HP VUE and/or MPower, run vue_swremove as follows after updating. If you are updating from HP-UX 10.01, enter: /usr/dt/bin/vue_swremove HP_VUE 10.01 /usr/dt/bin/vue_swremove MPOWER To remove both HP VUE and MPower: /usr/dt/bin/vue_swremove HPVUE_\&_MPOWER 10.01 If you are updating from HP-UX 10.10 r 10.20: /usr/dt/bin/vue_swremove HP_VUE 10.10+ /usr/dt/bin/vue_swremove MPOWER To remove both HP VUE and MPower: /usr/dt/bin/vue_swremove HPVUE_\&_MPOWER 10.10+ HP VUE Entry Left in /etc/inittab This item affects you if you are updating a HP-UX 10.x system on which HP VUE is configured to start on boot. The update leaves an obsolete entry in /etc/inittab that invokes the vuerc program, which is not supported on HP-UX 11.0. Once your system comes up on HP-UX 11.0, delete this line from /etc/inittab, if present: vue :4:respawn:/usr/vue/bin/vuerc # VUE invocation Then force the system to re-read /etc/inittab: init q
Appendix B
145
Troubleshooting General Requirements If you do not remove this entry, two process slots will be taken up unnecessarily.
CAUTION
When a file is copied to an HFS (or UFS) file system and later accessed through mmap, the data accessed through the mmap interface will be stale. Applications like ld64 use mmap interface to read data from a file. Start Task 1. Determine if patch PHKL_16499 and/or PHKL_16498 are on your system. For example: /usr/sbin/swlist -l product PHKL_16499 2. If PHKL_16499 or PHKL_16498 are installed, remove them: /usr/sbin/swremove -x autoreboot=true PHKL_16499 3. Regenerate the kernel with the mk_kernel command and update the system with HP-UX 11.0 ACE 9911. Alternatively, you can install patch PHKL_18506 or a superceding patch from the HP IT Resource Center web: http://itrc.hp.com
146
Appendix B
3. If the above lines exist, uncomment the Dtlogin*authorize line as shown below and save the file.
Dtlogin*authorize: False
4. If /etc/dt/config/Xconfig does not exist, either copy the template file from /usr/dt/config/Xconfig to /etc/dt/config/Xconfig or enter the four lines shown above into a new file called /etc/dt/config/Xconfig. 5. If you created a new file, set the following permissions and ownership on the file: chmod 444 Xconfig chown bin:bin Xconfig Be sure to remove the leading # and spaces from the Dtlogin*authorize line as shown in Step 3 above. 6. Reset the X server by logging out. Then login to CDE from the graphics console. Workaround 2 If the system is up on the network, and you can rlogin to it with root permissions: 147
Appendix B
Troubleshooting General Requirements 1. While the system is at the CDE login screen on the console monitor, rlogin to it from another system. 2. Look for filenames of format hostname AAAaNNNNN in /var/dt: cd /var/dt ll -a 3. Rename the file having the most recent timestamp (it was made right after the last system boot). For example: mv ace90AAAaNNNNN ace90AAAaNNNNN.old 4. Login to CDE on the graphics console. Workaround 3 If you cannot rlogin to the system: 1. At the CDE login prompt, select: Command line login 2. In the black and white ITE screen, login as root. 3. Deconfigure all other LANs except lan0, the core LAN. One easy way to do this is edit the /etc/rc.config.d/netconf file to delete or comment out all entries at the bottom of the file pertaining to lan1, lan2, etc. with different IP addresses. 4. Reboot the system. Upon reboot, you will be able to login to CDE. 5. After the system has rebooted, configure the other LAN cards back in either by using SAM or by editing /etc/rc.config.d/netconf.
Start Task
148
Appendix B
Troubleshooting General Requirements You have the original library if you see something like this:
/usr/lib/X11R5/libX11.1: X Window System, Version 11 HP-UX 10.* SRC_MLP R5+ (build date: Wed Mar 1 19:51:03 PST 1995)
If the build date shown is October 24, 1995 or later, you already have the patched version of the file. Further action is not needed. If the build date shown is earlier than October 24, 1995 and you intend to run swinstall'd GUI on a HP-UX 10.01 system, you need to install patch PHSS_18011, "s700_800 10.0[01]-10 X11R5/Motif1.2 Runtime May 97 Periodic Patch."
2. Obtain the patch from HP's IT Resource Center. Install the patch before running swgettools to get the new version of SD. swgettools overwrites old SD and patches. Also plan to install the latest SD patch after you have updated to HP-UX 11.0.
Appendix B
149
Troubleshooting General Requirements These errors are followed by a summary fullest error for GraphicsSBaseDK.STAR-WEBDOC. To remove these error messages and ensure complete 3-D installation, you should re-install 3-D graphics after the initial cold install and boot process. For example, to re-install the 3-D Graphics bundle (B2268AA) from the Core OS Options CD, use the command: swinstall -s /cdrom/extra.depot -x reinstall=true \ -x reinstall_files=true B6268AA The Core OS Options CD has been included in HP-UX 11.0 media kits for workstations since January 2000.
150
Appendix B
Troubleshooting General Requirements vno_close+0x20 closef+0x68 exit+0x324 psig+0x258 trap+0x1344 nokgdb+0x8 Edit the /stand/system file to change the tunable parameter "streampipes" to 0 (zero). Rebuild the kernel with mk_kernel command.
Appendix B
151
152
Appendix B
Troubleshooting Updating between 32-bit and 64-bit OS 9000/800/K580 If /etc/.supported_bits contains an entry for your system model, and your system is specified as 64-bit, you are ready to update the system from HP-UX 10. to HP-UX 11.0 ACE 9911 in 64-bit mode. To determine if your system model is in the file, enter: grep $(/usr/bin/model) /etc/.supported_bits The entry for V2250 indicates 64-bit operation only, whereas a K580 is capable of both 32- and 64-bit operation. If the /etc/.supported_bits file is not present on your system, you need to load the patch containing this file and examine it to see if it contains an entry for your system. 1. To load the patch for /etc/.supported_bits from the HP-UX 11.0 Install/Update/Recovery CD mounted at /cdrom, enter: swinstall -x allow_incompatible=true -s /cdrom \ PHCO_18222 The allow_incompatible flag must be set because you are loading an HP-UX 11.0 patch on an HP-UX 10.x system. 2. Query /etc/.supported_bits using the grep command shown above to ensure that your system is capable of 64-bit operation before proceeding.
CAUTION
Never use the -x allow_incompatible=true option when updating to HP-UX 11.0 or between the 32-bit and 64-bit versions of HP-UX 11.0. If you use this option it is likely to result in a failed update and possibly an unbootable system. You can, however, use it when loading the /etc/.supported_bits file as described above.
Before updating to a 64-bit operating system, we strongly recommend that you use the Software Transition Kit (STK) available on this web: http://devresource.hp.com/STK
Appendix B
153
Troubleshooting Updating between 32-bit and 64-bit OS The STK contains tools and documents to assess applications or libraries that run on HP-UX 10.x and helps transition them to HP-UX 11.0 64-bit operation. The web site also has release notes and an FAQ with details about supported systems and necessary firmware updates. IMPORTANT You may have to remove some 32-bit applications, such as OnLine JFS, before converting to 64-bit OS to allow the 64-bit kernel to build correctly. Then re-install needed applications after converting the OS to 64-bit. The newest versions of HP-UX applications are on the HP-UX Applications CDs included in the HP-UX 11.0 media box.
Start Task
To update from HP-UX 11.0 32-bit to 64-bit OS (or vice versa), follow these steps: 1. Verify that your system supports the intended bit operation. See Supported Systems on page 31. 2. If you plan to transition between 32-bit and 64-bit (in either direction), you need to update the SD toolset. Before going any further, perform the procedure on Updating the SD Toolset (swgettools) on page 74. 3. Use SAM to determine if a driver from the next table is configured into the kernel. These drivers are supplied on the HP-UX 11.0 Install/Update/Recovery CD: Open the Kernel Configuration menu and select Drivers. If a driver from the next table has a Current State of In, the driver is configured into the kernel.
Table B-1
Device Drivers Required for 32/64-bit Conversion Bundle J2658BA, J2157B J3701BA J2166B, J2250B J2806CA fddi fddi3 token2 atmgsc, atm2gsc Driver(s) Name Server FDDI/9000 HSC FDDI/9000 Driver HP-PB token ring HSC ATM 155/622
154
Appendix B
Troubleshooting Updating between 32-bit and 64-bit OS Table B-1 Device Drivers Required for 32/64-bit Conversion (Continued) Bundle J32070B J2793B Driver(s) strlan, osi1 syncio, nioxb, eisaxb, x25hal, sxb, wan, lapb, x25plp, x25sentry, x25idmap, plp2llc2, trcl2, trcl3 Name OTS/9000 S800 X.25/9000 Link
4. Convert your system to either 32-bit or 64-bit operation. If you have drivers configured into the kernel, proceed to the next section below. Otherwise, skip to Convert between 32-bit and 64-bit OS without Additional Drivers on page 87.
Converting between 32-bit and 64-bit Operation for Kernel with Drivers
You can either create a depot in which to consolidate all the bundles you intend to install or use a /tmp directory. Determine which of these approaches works best for you, then proceed: Option 1: Use a Depot 1. Create a depot on an HP-UX 11.0 or later network server that combines all the bundles you want to install. For example, for the English version enter: /usr/sbin/swcopy -s /cdrom HPUXEng32RT Or enter: /usr/sbin/swcopy -s /cdrom HPUXEng64RT and /usr/sbin/swcopy -s /cdrom application_bundles 2. If you have not already done so, Updating the SD Toolset (swgettools) on page 74. 3. If you have not already done so, install SD cumulative patch PHCO_18183 or its replacement: /usr/sbin/swinstall \ -x autoselect_reference_bundles=false PHCO_18183 Appendix B 155
Troubleshooting Updating between 32-bit and 64-bit OS 4. To convert the OS to 64-bit: /usr/sbin/swinstall -x match_target=true \ -x autoreboot=true \ -x reinstall=true -x reinstall_files=true \ -x os_name=HP-UX:64 -x os_release=B.11.00 To select 32- bit, replace 64 with 32 in the previous command line. Option 2: Use a /tmp Directory 1. Before you start the update, enter the following commands: mkdir /tmp/master.d mv /usr/conf/master.d/* /tmp/master.d 2. If you have not already done so, install SD cumulative patch PHCO_18183 or its replacement. Enter: /usr/sbin/swinstall \ -x autoselect_reference_bundles=false \ -s /cdrom PHCO_18183 3. Patches for HP-UX are selected along with products from the HP-UX 11.0 Install/Update/Recovery CD and update the OS simultaneously: /usr/sbin/swinstall -x match_target=true \ -x reinstall=true -x reinstall_files=true \ -x autoreboot=true \ -x os_name=HP-UX:64 -x os_release=B.11.00 \ -s /cdrom To select 32- bit, replace 32 with 64. 4. If you haven't already done so, update the SD Toolset (swgettools) as explained earlier in this chapter. 5. Update the bundles from the HP-UX Application CD: /usr/sbin/swinstall -x match_target=true \ -x reinstall=true -x reinstall_files=true \ -x autoreboot=true \ -s /cdrom If the system uses any third-party master files (that is, master files not supplied by HP), move them back from /tmp/master.d to /usr/conf/master.d after swinstall completes. Use SAM to confirm that all the additional drivers are again active in the HP-UX kernel.
156
Appendix B
Troubleshooting Updating between 32-bit and 64-bit OS If a driver's Current State is Out, it is not in the kernel. Select the drivers you need by selecting Actions -> Add Driver to Kernel. You can now reconfigure the kernel and reboot. If you do not perform the above steps, the kernel build may fail during the swinstall from the HP-UX 11.0 Install/Update/Recovery CD. In this case, you'll see output similar to this in swagent.log:
NOTE: Building a new kernel based on template file "/stand/system" Compiling /stand/build/conf.c... Loading the kernel... ld: Unknown input file type: "/usr/conf/lib/libfddi3.a" Fatal error. *** Error exit code 1 Stop. make failure
If swinstall fails, edit the file /stand/system to remove or comment out all the entries that pertain to the drivers specified from the output. Then press Resume Install on the swinstall screen. If this was a non-interactive swinstall, start again with one of the options under the subsection Converting between 32-bit and 64-bit Operation for Kernel with Drivers on page 85.
Appendix B
157
Troubleshooting Updating between 32-bit and 64-bit OS 3. If you have not already done so, install SD Cumulative patch PHCO_18183 or its replacement. For example: /usr/sbin/swinstall \ -x autoselect_reference_bundles=false \ -s /cdrom PHCO_18183 4. When invoking swinstall to update, make sure to include two additional flags: -x reinstall=true and -x reinstall_files=true For example, to convert to 64-bit operation: /usr/sbin/swinstall -x logdetail=true \ -x autoreboot=true -x match_target=true \ -x reinstall=true -x reinstall_files=true \ -x os_name=HP-UX:64 -x os_release=B.11.00 \ -s /cdrom Or, use SD-UX interactively: /usr/sbin/swinstall \ -x os_name=HP-UX:64 -x os_release=B.11.00 -i To select 32- bit, replace 64 with 32. CAUTION Never use the -x allow_incompatible=true option when updating to HP-UX 11.0 or between the 32-bit and 64-bit versions of HP-UX 11.0. If you use this option it is likely to result in a failed update and possibly an unbootable system. When using the SD-UX interactive interface, the re-install options must be set in the Options menu: 1. Select: Options -> Change Options. In the window provided, select both of these choices:
Reinstall filesets, even if same revision exists Reinstall files even if same one already there
These are the equivalent to the command-line swinstall -x options reinstall=true and reinstall_files=true. Confirm the changes by selecting the OK buttons to return to the main install window. 2. Use the right mouse button to select Mark for Install. 158 Appendix B
Troubleshooting Updating between 32-bit and 64-bit OS 3. Select: Actions -> Install (Analysis) From the Analysis and Execution dialog boxes, do not press the Logfile button in the terminal interface; closing the window on HP-UX 11.0 is only available in the graphical interface (GUI). SD-UX analyzes the build. Once the analysis completes, you can view the logfile, a product summary describing the elements ready (or skipped) for installation, and disk space impact on all affected file systems. 4. When using the GUI, if the analysis reports that disk space for a system directory is too small, extend its logical volume and file system. 5. If the program reports errors, read the logfile to resolve them before proceeding. You may then re-analyze the installation. 6. Approve the series of confirmations (including Done). 7. Log in to the system after the reboot. Once you log in, review/var/adm/sw/swagent.log and /var/adm/sw/swinstall.log.
64-bit OS Requirements
SCSI Message Logging Needs Patching Your 64-bit OS may crash with messages such as: panic in lbcopy_pcxu_method+0xc... When a system is under high stress, device drivers can generate error messages like this during error recovery. These panic messages only occur when other SCSI errors are detected. You can review these errors in: /var/adm/syslog/syslog.log To avoid this problem, install patch PHKL_24004, in the March HWE, after installing or updating to HP-UX 11.0. This problem will also be fixed in a future HP-UX 11.0 Support Plus release. You can also download individual patches from the HP IT Resource Center web: http://itrc.hp.com
Appendix B
159
160
Appendix B
Appendix C
161
The main boot menu displays. 5. Continue with the appropriate section to finish the boot process: Booting HP Workstations on page 163 Booting HP Servers on page 166 Booting V-Class Systems on page 169 Searching for Other Bootable Devices on page 171
TIP
162
Appendix C
Booting HP Workstations
This section shows examples of different boot menus for HP workstations. Boot menus vary depending on your systems firmware. Sample Workstation Boot Menu After Halting the Autoboot Process on page 162, the system displays a main boot menu. If selections at the screen bottom do not appear, press and hold Esc.
Command Description ----------------Auto [boot|search] [on|off] Display or set auto flag Boot [pri|alt|scsi.addr] [isl] Boot from primary, alternate, SCSI Boot lan[.lan_addr] [install] [isl]Boot from LAN Chassis [on|off] Enable chassis codes Diagnostic [on|off] Enable/disable diagnostic boot mode Fastboot [on|off] Display or set fast boot flag Help Display the command menu Information Display system information LanAddress Display LAN station addresses Monitor [type] Select monitor type Path [pri|alt] [lan.id|SCSI.addr]Change boot path Pim [hpmc|toc|lpmc] Display PIM info Search [ipl] [scsi|lan [install]Display potential boot devices Secure [on|off] Display or set security m
When you see the boot menu prompt appears: 1. Enter: search (or sea) If the list shows the CD device, continue with the following steps. If the list does not show the CD device, check the device and cable connections and repeat the search. 2. To boot using the SCSI address of the device, enter: boot scsi.x In this example x is the boot device. 3. If you see the following prompt, enter: n Interact with IPL (y or n)? 4. Return to Cold installing HP-UX 11.0 on page 56.
Appendix C
163
Booting HP Workstations and Servers Booting HP Workstations Sample Workstation Boot Menu Older HP Workstations display a menu similar to this:
b) Boot from specified device s) Search for bootable devices a) Enter Boot Administration mode x) Exit and continue boot sequence ?) Help Select from menu:
1. To start a search for bootable devices, enter: s You see a list of Pn selections.
=============================================================== Searching for Devices with Bootable Media. To terminate search, press and hold the ESCAPE key. Device Selection Device Path Device Type and Utilities P0 scsi.6.0 HP 2213A IPL P1 scsi.3.0 HP HP35480A IPL P2 scsi.0.0 TOSHIBA CD-ROM XM-3301TA IPL Enter boot selection, (h)elp, or e(x)it: ===============================================================
2. If your boot device does appear in the search list: At the Enter boot selection prompt, enter the Pn device selection for the device containing your install media. If you know the SCSI address of the device beforehand, you can skip the search and simply enter the following command at the Select from menu prompt: b scsi.x 3. If your boot device does not appear in the search list: a. Check the hardware. b. To exit, enter: x c. To initiate another search, enter: s d. At the prompt Enter boot selection, enter the Pn device selection for the device containing your install media.
164
Appendix C
Booting HP Workstations and Servers Booting HP Workstations 4. After choosing the boot path and loading the Ignite-UX utility, the Ignite-UX keyboard languages screen appears (if your system has a PC-style keyboard). Return to Cold installing HP-UX 11.0 on page 56.
Appendix C
165
Booting HP Servers
As noted previously, you can halt the server autoboot process and redirect it to boot from the desired media device. This section shows examples of different boot menus for HP servers. Boot menus vary depending on your systems firmware. Sample Server Boot Menu After Halting the Autoboot Process on page 162, the system displays a main boot menu. If selections at the screen bottom do not appear, press and hold Esc.
----------------------- Main Menu---------------------------Command Description BOot [PRI|ALT|<path>] Boot from specified path PAth [PRI|ALT] [<path>] Display or modify a path SEArch [DIsplay|IPL] [<path>] Search for boot devices COnfiguration menu Displays or sets boot values INformation menu Displays hardware information SERvice menu Displays service commands DIsplay Redisplay the current menu HElp [<menu>|<command>] Display help for menu or command RESET Restart the system --------Main Menu: Enter command or menu >
You only need to enter the initial capital letters to launch each command. 1. To search for available boot devices, enter: search (or sea) 2. Boot from the local CD-ROM drive. For example, enter: bo pn where pn is the path number for the install device shown in the search output. You can also specify the device by the hardware path, such as 56/52.0, in place of the path number. Here is a typical output:
========================================================== Searching for potential boot device. This may take several minutes. To discontinue, press any key. Path Number Device Path Device Type -
166
Appendix C
3. Return to Cold installing HP-UX 11.0 on page 56. Sample Server Boot Menu For Models 8x7, 845, 835, 870, and other older HP Servers, the boot display looks like this:
============================================================== Console path = 56.0.0.0.0.0.0 (dec) 38.0.0.0.0.0.0 (hex) Primary boot path = 52.2.0.0.0.0.0 34.00000002.0.0.0.0.0 (dec) (hex) (dec) (hex)
Alternate boot path = 52.0.0.0.0.0.0 34.0.0.0.0.0.0 64 MB of memory configured and tested. Autoboot from primary path enabled. To override, press any key within 10 seconds.
Boot from primary boot path (Y or N)?> n Boot from alternate boot path (Y or N)?> Enter boot path, command, or ?> ==============================================================
1. Switch the system ON. 2. Press any key to stop the autoboot process. 3. Insert the install CD. 4. Determine the hardware path of the install device from your system administrator. (There is no search capability to determine this information on older HP server models). If the primary path shown on your screen is not the same as that for the install device, at the prompt Boot from primary boot path, respond with n . In this case, you will then be asked if you want to boot from the alternate path, which is typically set to the CD device.
Appendix C
167
Booting HP Workstations and Servers Booting HP Servers If the primary path shown on your screen matches that for the install device, respond with: y If neither the primary or alternate device paths correspond to that for the CD device, respond with n to both prompts. In this case, enter the hardware path of the device (for example, 52.3.0) at the prompt Enter boot path, command, or ?>.
5. To the question Interact with IPL (y or n)?, enter: n 6. After choosing the boot path and loading the Ignite-UX utility, the Ignite-UX keyboard languages screen appears (if your system has a PC-style keyboard). Return to Cold installing HP-UX 11.0 on page 56. Loading the install kernel takes 3 to 5 minutes.
TIP
To start over at this point, simply switch the system OFF and ON again.
168
Appendix C
If the system is set to perform auto-boot, you will see the following:
Processor is starting the autoboot process.To discontinue, press any key within 10 seconds. ...
Press any key at this point. You will see the following boot menu (capital letters indicate minimum-required command):
Command Description AUto [BOot|SEArch ON|OFF] Display or set the specified flag BOot [PRI|ALT|<path> <args> Boot from a specified path BootTimer [time] Display or set boot delay time CLEARPIM Clear PIM storage CPUconfig [<proc>] [ON|OFF] Configure/Deconfigure Processor DEfault Set the system to defined values DIsplay Display this menu ForthMode Switch to the Forth OBP interface IO List the I/O devices in the system LS [<path>|flash] List the boot or flash volume OS [hpux|sppux] Display/Select Operating System PASSword Set the Forth password PAth [PRI|ALT|CON] [<path>] Display or modify a path PDT [CLEAR|DEBUG] Display/clear Non-Volatile PDT state PIM_info [cpu#] [HPMC|TOC|LPMC]Display PIM of current or any CPU RESET [hard|debug] Force a reset of the system RESTrict [ON|OFF] Display/Select restricted access to Forth mode
Appendix C
169
170
Appendix C
For this example, boot the CD with: boot p1 The install kernel then loads from the CD device.
Appendix C
171
172
Appendix C
Web Resources
Web Resources
This appendix lists the many resources on the web: Availability Matrix Overview for HP-UX releases: http://software.hp.com/MATRIX HP-UX 11.0/11i information: http://docs.hp.com/hpux/os/11.0 http://docs.hp.com/hpux/os/11i http://devresource.hp.com/STK/hpuxoverview.html http://forums.itrc.hp.com http://www.hp.com HP-UX patches and patch information from the HP ITRC: http://itrc.hp.com Select the language. Select maintenance and support, then select the appropriate patching tools. To receive HP Security Bulletins, under maintenance and support, select subscribe to security bulletins and patch digests. HP-UX software releases: http://software.hp.com/RELEASES-MEDIA HP-UX 11.0 Software Transition Kit: http://devresource.hp.com/STK HP-UX Support Plus: http://software.hp.com/SUPPORT_PLUS HP-UX supported systems: http://www.hp.com http://www.hp.com/workstations/index.html HP Technical Documentation feedback form: http://docs.hp.com/assistance/feedback.html
Appendix D
173
Web Resources
174
Appendix D
Index
Symbols /home cold install, 65 /partition free space, 130 /stand increase size, 122 requirements, 130 /usr requirements, 131 /var increase size, 120 requirements, 131 Numerics 32-bit conversion drivers, 154 OS conversion, 157 OS requirements, 152 3-D graphics troubleshoot, 149 64-bit conversion drivers, 154 OS conversion, 157 OS requirements, 152, 159 update operation, 152 A about this guide, 6 ACE9911, 136 adding patches, 102 application patches, 100 requirements, 139 verify, 38 applications install, 99 update, 105 updating, 94 autoboot process halt, 162 B back up configuration files, 47 files other, 41 system, 39, 67, 89, 107 boot HP server, 166, 167 HP systems, 161 newer server, 166 newer workstation, 163, 166 older server, 167 older workstation, 164 search for bootable devices, 164, 166 system, 169 V2200, 169 V-Class, 169 bootable devices, 164, 166 bundle patch, 24 bundles software, 111 C C compiler mode change, 140 card graphics, 114 cards LAN, 136, 147 PCI, 138 unsupported, 33 CDE HP VUE migration, 144 login failure, 147 troubleshoot, 142 checklist for migration, 21 codewords source, 50 cold install errors, 118 HP-UX 11.0, 53 information, 46 media, 55 migration, 25, 53 overview, 54 pre-migration tasks, 46 procedures, 56 pros and cons, 25 recover files, 65 requirements, 34 restore /home, 65 restore files, 66 retrieve information, 65 root directory, 65 troubleshoot, 60, 117 175
Index
command swconfig, 95 swinstall, 84 swlist, 92, 94, 95 swverify, 92, 94 command line update, 79 compiler C, 140 HP, 141 requirements, 139 configuration save files, 47 configure graphics drivers, 137 contents media, 22, 109 conventions, typographic, 7 conversion device drivers, 154 copyright notice, 2 core OS options CD, 111 core media recovery, 44 core os options install, 88 critical patches, 103 CUE security, 135 custom software depot, 49 D depot custom software, 49 devices bootable, 164, 166 diagnostic drivers, 128 requirements, 130 disk space, 36 requirements, 130 drivers 32-bit conversion, 154 64-bit conversion, 154 diagnostic, 128 graphics, 137 network, 61 SAM, 157 E enable hardware, 86 eqmemsize, 133 errors, 118 existing applications, 38 F fbackup, 41 file swagent.log, 95 files adjust sizes, 120 back up, 41 cold install, 65, 66 recover, 65 restore, 66 firmware recommendations, 29 requirements, 136 frecover, 41 G graphical user interface, 84 graphics drivers, 137 no console, 145 troubleshoot, 149 graphics card Visualize-fxe rev. B, 114 graphics driver core os options cd, 88 GSP, 138 Guardian Service Processor, 138 GUI, 84 H halt autoboot process, 162 hardware enable, 86 requirements, 136 supported, 31 unsupported, 33 HFS system, 132 HP boot, 161
176
Index
boot menu, 166, 167 VUE, 145 HP applications update, 105 HP Domain, 139 HP VUE CDE migration, 144 HP Web Quality of Service, 139 HP-UX 10.01, 77 10.10, 77 10.20, 77, 78 10.x patches, 83 11.0 CDs, 109 HP-UX 11.0, 69 already running, 24 cold install, 53 introduction, 22 uninstall, 126 HP-UX 11i, 27 migration, 70 I identify system, 30 ignited system, 55 Ignite-UX make_net_recovery, 40 make_tape_recovery, 39 upgrade, 42 use, 42 using, 105 information cold install, 46 patches, 101 install additional requirements, 129 applications, 99 core os options, 88 drivers, 128 patches, 99 pre-migration tasks, 46 installation verify, 92 instant ignite, 27 introduction HP-UX 11.0, 22 J JFS system, 131 K kernel 32-bit OS, 155 64-bit OS, 155 build failure, 146 eqmemsize, 133 supported, 33 tunables, 33 L LAN cards, 136, 147 languages, 6 legal notice, 2 libc rebuild applications, 140 LVM system, 130, 131 M make_net_recovery, 40 make_tape_recovery, 39 manpages swlist, 93 swverify, 93 mass storage drivers, 61 media cold install, 55 contents, 22, 109 mount, 73 recovery, 44 source, 50, 73 memory, 33 requirements, 130 migration checklist, 21 cold install, 25, 53 cold install process, 54 HP-UX 11i, 70 path, 25 pre-cold install tasks, 46 preparing, 19 pre-update tasks, 48, 72 pros and cons, 25 177
Index
software, 19 tasks, 28 update, 25, 69 verify system, 91 model, 30 server, 32 workstation, 31 mount media, 73 N NetScape Suitespot Pro, 139 network drivers, 61 NIS, 135 O option GUI, 84 TUI, 84 OS, 30 requirements, 152 overview cold install, 54 update process, 71 P patch compilers, 141 kernel build failure, 146 SD, 148 patch bundles, 24, 86 patches adding, 102 changing state, 95 critical, 103 determining previous, 100 individual applications, 100 information, 101 install, 99 obtaining new, 100 remove, 48, 83 removing, 101 PATH set, 75 permissions CUE, 135 pre-migration tasks, 28 178 pre-update remove patches, 48 procedure cold install, 56 process update, 71 publication history, 4 R recovery HP-UX 11.0, 44 reinstall SD, 127 remove patches, 48, 83 removing patches, 101 requirements /stand, 130 /usr, 131 /var, 131 32-bit, 152 64-bit, 152 64-bit OS, 159 additional, 129 application, 139 cold-install, 34 compiler, 139 diagnostic, 130 disk space, 36, 130 firmware, 136 general, 149 hardware, 136 memory, 130 storage, 33 system, 31 update, 35 root increase size, 124 root directory create, 65 S SAM drivers, 157 SCSI patch, 159 SD patch, 148
Index
reinstall, 127 SD-UX update, 80 security, 134 CUE, 135 NIS, 135 sendmail troubleshoot, 119 server boot, 166, 167 boot search results, 166 Ignite-UX, 42 model, 32 software, 30 bundles, 111 software bundles support plus, 115 software distributor, 148 reinstall, 127 software migration, 19 Software Transition Kit, 153 source codewords, 50 media, 50, 73 state of patches, 95 STK, 153 storage drivers, 61 requirements, 33 streampipes system panic, 150 support plus cd contents, 115 software bundles, 115 supported hardware, 31 kernel, 33 systems, 31 swagent.log file, 95 swconfig command, 95 swgettools update, 74 swinstall update, 84 swlist command, 92, 94, 95 swverify command, 92, 94 system adjust file sizes, 120 back up, 39, 67, 89, 107 boot, 161, 169 boot console, 169 boot menu, 163, 164, 166, 167 factory ignited, 55 firmware, 29 HFS, 132 HP, 161 instant ignite, 27 JFS, 131 LVM, 130, 131 model, 30 OS, 30 panic, 150 requirements, 31 running HP-UX 11.0, 24 software, 30 supported, 31 troubleshoot, 125 V2200, 169 V-Class, 169 verify migration, 91 T tasks pre-migration, 28, 48 pre-update, 48 terminal user interface, 84 trademark notices, 3 troubleshoot CDE, 142 graphics, 149 kernel, 146 migration, 117 sendmail, 119 system, 125 TUI, 84 tunables kernel, 33 typographic conventions, 7 U U.S. Government License, 2 uninstall HP-UX 11.0, 126 unsupported cards, 33 hardware, 33 USB hub, 136 update 64-bit operation, 152 179
Index
additional requirements, 129 command line, 79 command line option, 84 errors, 118 HP applications, 105 HP-UX 10.01, 77 HP-UX 10.10, 77 HP-UX 10.20, 77, 78 HP-UX 11.0, 69 hp-ux 11.0, 84 migration, 25, 69 patch bundle, 86 PATH, 75 pre-migration tasks, 48, 72 process, 71 pros and cons, 25 remove VME, 136 requirements, 35 SD Toolset, 74 SD-UX, 80 software depot, 49 swgettools, 74 swinstall command, 84 troubleshoot, 117 TUI or GUI, 84 updating HP-UX applications, 94 upgrade Ignite-UX server, 42 V V2200 boot, 169 system boot console, 169 V-Class boot, 169 system, 169 vendor verify software, 91 verify applications, 38 HP-UX installation, 92 system migration, 91 vendor software, 91 Visualize-fxe rev. B graphics card, 114 VME remove, 136 VUE, 145 180 W warranty, 2 web resources, 173 workstation, 164 boot, 163, 166 boot search results, 164 model, 31 workstations PCI card, 138