HP

HP-UX 11i Version 1 Installation and
Update Guide
HP Servers and Workstations
Edition 11
Important: Review the
Read Before Installing or Updating to HP-UX 11i v1
booklet accompanying the HP-UX 11i v1 OE Media
before installing or updating to HP-UX 11i v1.
Manufacturing Part Number : 5187-4496

December 2003
United States
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.
Restricted Rights Legend

Use, duplication or disclosure by the U.S. Government is subject to
restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013
for DOD agencies, and subparagraphs (c) (1) and (c) (2) of the
Commercial Computer Software Restricted Rights clause at FAR
52.227-19 for other agencies.
HEWLETT-PACKARD COMPANY
3000 Hanover Street
Palo Alto, California 94304 U.S.A.
Use of this document and any supporting software media (DVDs,
CD-ROMs, flexible disk, and tape cartridges) supplied for this pack is
restricted to this product only. Additional copies of the programs may be
made for security and back-up purposes only. Resale of the programs, in
their present form or with alterations, is expressly prohibited.
Copyright Notices
Copyright  1983-2003 Hewlett-Packard Development Company, L.P.
Reproduction, adaptation, or translation of this document without prior
written permission is prohibited, except as allowed under the copyright
laws.
2
Trademark Notices
ActivePerl is a registered trademark of ActiveState Tool Corporation.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Sun Microsystems, Inc. in the U.S. and other
countries. Hewlett-Packard is independent of Sun Microsystems.
Netscape is a registered trademark of Netscape Communications
Corporation.
OpenGL is a registered trademark of Silicon Graphics, Inc.
OSF/Motif is a trademark of the Open Software Foundation, Inc. in the
U.S. and other countries.
UNIX is a registered trademark in the United States and other
countries, licensed exclusively through The Open Group.
VERITAS is a registered trademark of VERITAS Software
Corporation.
VERITAS File System is a trademark of VERITAS Software
Corporation.
X Window System is a trademark of the Massachusetts Institute of
Technology.
3
Publication History
The manual publication date and part number indicate its current
edition. The publication date will change when a new edition is released.
The manual part number will change when extensive changes are made.
To ensure that you receive the new editions, you should subscribe to the
appropriate product support service. See your HP sales representative
for details.
• First Edition: December 2000 B2355-90703,

Printed, CD-ROM (Instant Information), and Web
(http://www.docs.hp.com/)
• Second Edition: June 2001, 5971-2215,
Printed, CD-ROM, and Web
• Third Edition: September 2001, 5185-6511,
• Fourth Edition: March 2002, 5185-6593,
• Fifth Edition: June 2002, 5187-0161,
• Sixth Edition: September 2002, 5187-1350,
• Seventh Edition: December 2002, 5187-1827,
• Eighth Edition: March 2003, 5187-2239,
• Ninth Edition: June 2003, 5187-2774,
• Tenth Edition: September 2003, 5187-3614,
• Eleventh Edition: December 2003, 5187-4496,
For the latest version, see the HP-UX 11i v1 Documentation section on
the Web at:
4
http://docs.hp.com
To send us feedback regarding this manual, use the form at the following
URL:
http://docs.hp.com/assistance/feedback.html
5
About this Guide
This guide describes installing HP-UX 11i v1 on HP systems and
assumes that you are the system’s administrator and familiar with basic
HP-UX commands and operations.
This guide applies to the September 2003 version of HP-UX 11i v1. If you
need information for a previous version of HP-UX 11i v1, refer to that
release’s printed book or Instant Information CD (included in your media
kit for that release).
If you need to set up your system in different languages, please refer also
to Configuring HP-UX For Different Languages, available on the Instant
Information CD and on the HP documentation web site
(http://docs.hp.com). A localized version of that manual is available
with localized media kits. Latest versions are available at the HP
documentation web site.
Typographic Conventions
This guide uses the following typographic conventions:
Boldface Words defined for the first time appear in boldface.
This font is also used to strongly emphasis an item.
Computer Computer font indicates literal and system items
displayed by the computer. For example:
file not found
User input Bold, computer text indicates literal items that you
type. For example, to change to your account’s home
directory, enter:
cd
Italics Manual titles, variable in commands and emphasized
words appear in italics. For example, you would
substitute an actual directory name for
directory_name in this command:
cd directory_name
[ ] and | Brackets [] enclose optional items in command syntax.
The vertical bar | separates syntax items in a list of
choices. For example, you can enter any of these three
items in this syntax:
6
ls [-a | -i | -x]
Enter Text in this bold, sans-serif font denotes keyboard keys
and on-screen menu items. A notation like Ctrl-Q
indicates that you should hold the Ctrl key down and
press Q. It is also used to display web page links.
7
8
Contents
1. Overview
HP-UX 11i Release Names and Release Identifiers. . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
The Purpose of this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
What You Will Find In This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Supported Paths to HP-UX 11i v1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Other Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2. Choosing a Migration Path

Migrating from Previous HP-UX Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Deciding Which Method to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Cold Install When... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Update When... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Additional Considerations (Cold-install or Update) . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Firmware Patches Should Not Be Included In Cold-Install or Update Session . . 33
Updating Network Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Installing or updating HP-UX Web Server Suite . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Installing or Updating Netscape Directory Server . . . . . . . . . . . . . . . . . . . . . . . . . 34
HP 3D Graphics No Longer Supported pre-PA-RISC 2.0 Systems . . . . . . . . . . . . 35
Small Memory Systems (<1GB/CPU) May Need to Configure VxFS 3.5 Tunables
After Install/Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Update Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Update May Fail If Latest Version of Update-UX is Not Installed . . . . . . . . . . . . 35
VxVM Rootability Not Enabled with update-ux . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Updating to 64-bit OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Cold-Install Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Using VxVM Rootability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Cold-Installing on Partitioned Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Instant Ignition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Alternate Cold-Install Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
If You Have an Existing HP-UX 11i v1 System.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Cold-Installing or Updating from DVD media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Important: Problems Reading HP-UX 11i v1 DVD Media During Update . . . . . . . . 42
DVD Media Advantages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
DVD Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
How is the New DVD Packaging Organized? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3. Install/Update System Requirements
9
Contents
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
How to Identify Your System’s Model, OS and Software . . . . . . . . . . . . . . . . . . . . 50
Unsupported Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
C3700 and J6700 Workstations Need Processor Board Upgrade . . . . . . . . . . . . . . . 51
OLA/R Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
HP 3D Graphics No Longer Supported pre PA-RISC 2.0 Systems . . . . . . . . . . . . . . 52
Firmware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Current System Firmware Versions and Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
How to Verify Your Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Checking Workstation Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Checking Server Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
How to Download Firmware Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
How to Apply Firmware Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
PCI Adapter Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Disk Space and Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Adjusting Required Minimum File System Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Update Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Increasing /var. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Increasing /stand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
4. Preparing To Move To HP-UX 11i v1

What is Installed with HP-UX 11i v1? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
HP-UX 11i v1 Operating Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
OE Application History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Changing Individual OE Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
HP-UX 11i v1 Software and Driver Bundle Type Definitions . . . . . . . . . . . . . . . . . . 78
HP-UX 11i v1 Core Software Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
HP-UX 11i v1 Always-Installed Software Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . 80
HP-UX 11i v1 Always-Installed Network Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
HP-UX 11i v1 Default-Installed Software Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . 84
HP-UX 11i v1 Selectable Software Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
HP-UX 11i v1 Selectable Network Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Updating Your Ignite-UX Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Diagnostics Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
10
Contents
Planning Your Disk Space Needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Planning Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
VxVM Rootability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Preparing your system for HP-UX 11i v1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
How to Prepare Your System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Back up Your System!. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Preparing to Cold-Install Your System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Collect Key Install Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Save Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Preparing to Update Your Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Record Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Update maxdsiz Configurable Kernel Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Rebuild Kernel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Clean Out Your Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Locate Source Media for Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
5. Cold Installing HP-UX 11i v1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Installing HP-UX 11i v1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
How to Cold-Install HP-UX 11i v1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
How to Retrieve Information After Cold-Installing . . . . . . . . . . . . . . . . . . . . . . . . . 112
Create a New Directory for Root Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Recover Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Restore /home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Restore Other Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Verify Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
6. Updating to HP-UX 11i v1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Problems Reading HP-UX 11i v1 DVD Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Patching Your System to Read DVD Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Using pfs_mount to Mount a DVD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Quickstart/Overview for the Update Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Updating Tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
How to Update to HP-UX 11i v1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
In Case of Trouble. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
11
Contents
Optional Step: Create a Network Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Step 1: Install the update-ux Command (Required Task!) . . . . . . . . . . . . . . . . . . . . 128
Step 2: Using update-ux to Update to HP-UX 11i v1 . . . . . . . . . . . . . . . . . . . . . . . . 131
update-ux Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Step 3: Verify the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
7. Verifying System Migration

How to Verify Your HP-UX Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Verifying HP-UX Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
How to Verify Application Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
8. Updating Applications
HP-UX Patching Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Use Custom Patch Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Downloading Individual Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
HP Security Bulletins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
HP-UX Support Plus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Other HP-UX Patching Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Updating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Adding and Removing Individual Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Using Software Distributor Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Managing Software Depots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Updating LicensePower/iFOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
How to Convert the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Uninstalling iFOR Version 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
9. Next Steps
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Maintaining Your HP-UX 11i v1 System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
A. Booting HP Servers and Workstations

Halting the Autoboot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Booting Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Booting HP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
12
Contents
Booting V-Class Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Searching for Other Bootable Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
B. Known Problems and Troubleshooting

Known Problems Discovered in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
vPars version A.02.03 Required for rp7405, rp7410 and rp8400 Servers with PDC
Firmware Version 17.005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
EMS checkinstall Script Fails When Updating From HP-UX 11.0 to HP-UX 11i v1 . .
171
EMS May Fail on IPv4 Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Problems Reading HP-UX 11i v1 DVD Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Ignore Warning Message When Installing PHCO_29566 . . . . . . . . . . . . . . . . . . . . 174
xntpd Fails to Start on Reboot After Installing GOLDQPK11i Patch Bundle . . . . 174
Install Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
“Kernel size is very large” Warning During Cold-Install . . . . . . . . . . . . . . . . . . . . . 176
System Console "kthread table full" or "fork failed" Messages . . . . . . . . . . . . . . . . 176
Kernel Build Fails on 64-bit Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Known Issues With OE Media Install Tool and Network Depots . . . . . . . . . . . . . . 178
Update Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
DMI/SCR Become Unbundled After Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Unsupported Upgrade of ServiceControl Manager Causes SCR Error During Update
179
Boot Error Messages Appear After Updating from HP-UX 11.0 (with MirrorDisk/UX
Installed) to HP-UX 11i v1 TCOE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
ApacheStrong Becomes Unbundled After Update . . . . . . . . . . . . . . . . . . . . . . . . . . 181
parmgr.1m Errors on MCOE Update from HP-UX 11.0 to HP-UX 11i v1 . . . . . . . 181
HP Apache May Hang On Reboot after System Update from Golden System Image
(GSI) Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
MLIB 8.3 Produces Warning During Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
X11MotifDevKit Produces Incompatible Error After Upgrade from HP-UX 10.20 183
OpenView SNMP Agent Produces Error with Upgrade to HP-UX 11i v1. . . . . . . . 184
“Initialize of the ITO Control Agent failed” Error During update-ux Session . . . . 185
Firmware Patches Should Not Be Included Cold-Install or Update Session . . . . . 186
Analyzing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Update Fails on J2250 Workstation With SCSI Floppy Drive . . . . . . . . . . . . . . . . . 187
Update Fails if nstrpty Kernel Parameter Set as a Formula . . . . . . . . . . . . . . . . . . 187
Kernel Build Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
X.25 Cards Not Supported on Some Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . 188
HP A3740A Fibre Channel PCI Tachyon Not Supported . . . . . . . . . . . . . . . . . . . . . 189
13
Contents
Common Install and Update Error and Warning Messages . . . . . . . . . . . . . . . . . . . . 190
Using Ignite-UX with HP-UX 11i v1 OEs and Patch Bundles . . . . . . . . . . . . . . . . . 190
Warning Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Selected Locale Not Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Multiple OE Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Disk Space Usage Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
swinstall Analysis Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Post-update swverify Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Root (/) Volume Lock Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
EISA 100BT Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Problems Configuring HP-UX 11i v1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Kernel Build Warnings For krm Module During Cold-Install or Update . . . . . . . . 196
cdrecord Application Requires Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Enabling AutoFS on High Availability Servers Can Cause NFS Packages to be
Dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Hardware Information Not Captured on Systems With Floppy Drive . . . . . . . . . . 197
Auto-Port Aggregation Will Not Work on rp7410 Systems . . . . . . . . . . . . . . . . . . . 198
EISA Cards Not Supported on 64-bit OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
100BT HSC-FX Cards Do Not Work on HP-UX 11i v1. . . . . . . . . . . . . . . . . . . . . . . 198
SCSI PCI Restrictions for OLA/R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
SCSI PCI HBA Documentation Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
HP-UX Apache-based Web Server Requires LD Patch to Start and Stop . . . . . . . . 201
Problems with Large Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Un-installing HP-UX 11i v1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Re-installing SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Recovering a Corrupt System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Patch Required for fbackup (1M) and frecover (1M) on SDLT320, SDLT220 and
DLTvs80 Tape Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Verifying and Adding Diagnostic Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Problems Affecting non-C Locales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Difference between English and Japanese HP-UX STK . . . . . . . . . . . . . . . . . . . . . 208
Warning when updating to non-C locales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
C. Using the update-ux Tool

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
About update-ux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
update-ux Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
14
Contents
D. Configuring Built-In PCI Networking
1000Base-T (Gigabit Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Optional Step: Configure Jumbo Frame Size (Jumbo Frames only supported at 1000
Mbit/s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Optional: Troubleshooting a Fast Ethernet Migration to HP-UX 11i . . . . . . . . . . . . 218
How the Automatic Merge Works Using the BTLAN.100 Script . . . . . . . . . . . . . . . 218
Optional: Manual Merging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Manual Merging Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
E. Controlling Memory Utilization of VxFS 3.5 on HP-UX 11i v1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Controlling the inode Cache . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Controlling the Buffer Cache. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
15
Contents
16
Tables
Table 1-1. HP-UX 11i Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Table 2-1. Migrating from Previous HP-UX Releases . . . . . . . . . . . . . . . . . . . . . . . . .30
Table 2-2. December 2003 Patch Bundles (By Media Location) . . . . . . . . . . . . . . . . .41
Table 3-1. Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Table 3-2. Minimum Firmware Versions for HP-UX 11i v1. . . . . . . . . . . . . . . . . . . . .54
Table 3-3. Older Workstation Firmware Requirements . . . . . . . . . . . . . . . . . . . . . . . .55
Table 3-4. Minimum Firmware Versions for OL* Support . . . . . . . . . . . . . . . . . . . . .56
Table 3-5. Current System Firmware Versions and Patches . . . . . . . . . . . . . . . . . . . .58
Table 3-6. Free Disk-space Requirements for /usr and /opt . . . . . . . . . . . . . . . . . . . .67
Table 4-1. Supported Operating Environments for Servers & Workstations . . . . . . .77
Table 4-2. HP-UX 11i v1 Core Software Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79
Table 4-3. HP-UX 11i v1 Always-Installed Software Bundles (by OE) . . . . . . . . . . . .80
Table 4-4. HP-UX 11i v1 Always-Installed Network Drivers . . . . . . . . . . . . . . . . . . .82
Table 4-5. HP-UX 11i v1 Default-Installed Software Bundles . . . . . . . . . . . . . . . . . .84
Table 4-6. HP-UX 11i v1 Selectable Software Bundles (all OEs) . . . . . . . . . . . . . . . .85
Table 4-7. HP-UX 11i v1 Selectable Network Drivers . . . . . . . . . . . . . . . . . . . . . . . .86
17
Tables
18
Figures
Figure 1-1. HP-UX 11i v1 Migration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Figure 2-1. Comparison of CD-ROM and DVD Packaging. . . . . . . . . . . . . . . . . . . . . .45
Figure 5-1. Cold-installing HP-UX 11i v1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .104
Figure 6-1. Updating HP-UX 10.20 or 11.0 to 11i . . . . . . . . . . . . . . . . . . . . . . . . . . .122
Figure 9-1. Reactive Software Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .157
Figure 9-2. Proactive Software Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .158
Figure B-1. Example patch bundle definition from Ignite-UX configuration file. . .191
Figure B-2. Example sw_source Definition from Ignite-UX Configuration File. . . .192
19
Figures
20
Overview
1 Overview
This chapter provides a high-level overview of how to install or update

your HP9000 system to HP-UX 11i v1.
What You Will Find in This Chapter
• “HP-UX 11i Release Names and Release Identifiers” on page 22

identifies the various releases in the HP-UX 11i family
“The Purpose of this Book” on page 23 outlines the scope of this book
• “What You Will Find In This Book” on page 24 provides a summary
of the contents of this book.
• “Supported Paths to HP-UX 11i v1” on page 26 provides a high-level
overview of the supported migration paths to install or update to
HP-UX 11i v1
• “Other Resources” on page 28 lists other HP documentation and
information we recommend you read prior to installing or updating
HP-UX 11i v1
Chapter 1 21
Overview
HP-UX 11i Release Names and Release Identifiers
HP-UX 11i Release Names and Release

Identifiers
With HP-UX 11i, HP delivers a highly available, secure, and manageable
operating system that meets the demands of end-to-end Internet-critical
computing. HP-UX 11i is available on both PA-RISC systems and
Itanium-based systems.
Each HP-UX 11i release has an associated release name and release
identifier. The uname (1) command with the -r option returns the
release identifier. The following table shows the releases available for
HP-UX 11i.
Table 1-1 HP-UX 11i Releases
Supported
Release Identifier Release Name Processor
Architecture
B.11.11 HP-UX 11i v1 PA-RISC
B.11.20 HP-UX 11i v1.5 Intel Itanium
B.11.22 HP-UX 11i v1.6 Intel Itanium
B.11.23 HP-UX 11i v2 Intel Itanium
22 Chapter 1
Overview
The Purpose of this Book
The Purpose of this Book

This guide describes migrating HP Servers and Workstations to the
latest release of HP-UX 11i v1. This new version of HP-UX delivers
hardware enablement, software functionality, and bundles of important
HP-UX applications in operating environments. HP-UX 11i v1 Operating
Environments (OEs) are described in the HP-UX 11i Release Notes
available on the Instant Information CD and the Hewlett-Packard
documentation web site: http://docs.hp.com. That document also lists
major changes from the previous HP-UX 11.0 and HP-UX 11i v1
releases.
HP-UX 11i v1 is the recommended next-level enterprise release for all
HP-UX systems currently running HP-UX 10.x and HP-UX 11.0.
This manual deals only with the software steps required to update your
HP-UX operating system. For hardware upgrades, either see the
documentation included with your hardware or consult your HP Support
Engineer.
IMPORTANT Be sure to review this entire guide and the “Known Problems”
information in the Read Before Installing or Updating to HP-UX 11i v1
Media booklet for December 2003 before proceeding to install or update
your system. Carefully review Appendix B, Known Problems and
Troubleshooting, for situations that may apply to your system.
If you have just received a system that was ordered with “Instant
Ignition,” the HP-UX 11i v1 Operating Environment has already been
installed. You do not need to re-install it.
Chapter 1 23
Overview
What You Will Find In This Book

This book is organized to assist you to successfully complete all of the
tasks necessary to either install or update your system to HP-UX 11i v1
from start to finish. The following list summarizes what you will find in
the chapters ahead:
• Chapter 2, “Choosing a Migration Path,” on page 29 provides

information and scenarios to help you decide the most appropriate
method to move your system to HP-UX 11i v1.
• Chapter 3, “Install/Update System Requirements,” on page 47
details the system requirements to either install or update to HP-UX
11i v1.
• Chapter 4, “Preparing To Move To HP-UX 11i v1,” on page 75 details
the required and recommended tasks to prepare your system for
HP-UX 11i v1. This chapter also includes additional information
about required, default and optional software installed with HP-UX
11i v1.
• Chapter 5, “Cold Installing HP-UX 11i v1,” on page 101 shows you
how to cold-install HP-UX 11i v1 operating system, a selected
operating environment, network drivers, CDE language bundle,
diagnostics, and required patches. Alternative cold-install methods
such as installing from depots or from golden images are also
discussed.
• Chapter 6, “Updating to HP-UX 11i v1,” on page 115 shows you how
to update your system to HP-UX 11i v1 using the update-ux
command. Several examples are provided to assist you with your
update scenario.
• Chapter 7, “Verifying System Migration,” on page 139 shows you
how to verify a successful install or update to HP-UX 11i v1.
• Chapter 8, “Updating Applications,” on page 143 shows you how to
update applications on your system that are not installed or updated
with HP-UX 11i v1 operating environments.
• Chapter 9, “Next Steps,” on page 153 provides you an overview of
additional configuration and maintenance tasks.
24 Chapter 1
Overview
• Appendix A, “Booting HP Servers and Workstations,” on page 159

describes booting various HP servers and workstations using the
built-in Boot ROM firmware interface.
• Appendix B, “Known Problems and Troubleshooting,” on page 169
contains critical information for you to review before you start
installing or updating to HP-UX 11i v1.
• Appendix C, “Using the update-ux Tool,” on page 209 provides a brief
overview of how to use the update-ux tool during the update process.
• Appendix D, “Configuring Built-In PCI Networking,” on page 215
describes configuring built-in (or core) PCI networking cards in HP
workstations and servers.
Chapter 1 25
Overview
Supported Paths to HP-UX 11i v1

There are two basic supported methods for moving to HP-UX 11i v1:
• Cold-install HP-UX 11i v1— This method overwrites everything on
the target disk. Use cold-install for new systems and on existing
systems when overwriting the root (/) volume will not cause loss of
applications or data. The process described in this guide cold-installs
a single system from local media. If you plan to install many systems
simultaneously, you should plan on using an Ignite-UX server.
Ignite-UX is a free product available on the HP-UX 11i v1 CD or
DVD media. Additional information on Ignite-UX and newer
versions are available on this web site:
http://software.hp.com/products/IUX/
For more information about cold installing your system, read
— Chapter 3, “Install/Update System Requirements,” on page 47

— Chapter 4, “Preparing To Move To HP-UX 11i v1,” on page 75
— Chapter 5, “Cold Installing HP-UX 11i v1,” on page 101
• Update using update-ux — Use the update-ux command when
you do not want to erase data or application files on your root disk.
update-ux adds or replaces functionality based on what you choose
when running the command. For more information about updating
your system using update-ux read:
— Chapter 3, “Install/Update System Requirements,” on page 47

— Chapter 4, “Preparing To Move To HP-UX 11i v1,” on page 75
— Chapter 6, “Updating to HP-UX 11i v1,” on page 115
NOTE For more information about cold-installing or updating your system,

please read Chapter 2, “Choosing a Migration Path,” on page 29.
26 Chapter 1
Overview
Figure 1-1 HP-UX 11i v1 Migration Overview
1. Prepare Your System

• Enough Disk Space? See page 66
• HP-UX 11i v1 supported on your system? See page 48
• Is your system firmware up-to-date? See page 53
• Installing a new OE with HP-UX 11i v1? See page 30
• Your applications certified to run on HP-UX 11i v1?
Decide: Migrate by either cold-installing or updating
• Backup Your System:
- Collect Key Install Information
- Backup Existing System
- Save configuration files
• Prepare source media for migration
References: Chapter 2, Chapter 3, Chapter 4, Appendix B,

“Read Before Installing or Updating to HP-UX 11i v1”
Read Chapter 2 to determine path

2. Cold -Install HP-UX 11i v1 3. Update to HP-UX 11i v1
• Verify System Requirements • Verify System Requirements
• Insert HP-UX 11i v1 CD or DVD • Insert HP-UX 11i v1 CD or DVD
• Boot From CD or DVD • Install update-ux
• Install HP-UX 11i v1 • Create optional update depot
• Restore config & personal files • Update to HP-UX 11i v1
• Backup Your System • Backup Your System
Reference: Chapter 5 Reference: Chapter 6
4. Verify the Migration

Verify HP-UX 11i v1 installation using swlist and swverify
Reference: Chapter 7
5. Update Other Applications

• Update additional applications with swinstall
• Install critical patches and remove unneeded patches
References: Chapter 8 and “HP-UX 11i v1 Release Notes”
HP-UX 11i v1 Migration Overview
Chapter 1 27
Overview
Other Resources
Other Resources
You can find other important information about HP-UX 11i v1 updates
and issues in several resources:
• HP-UX 11i v1 Release Notes - available on the Instant

Information CD and the Hewlett-Packard documentation web site:
http://docs.hp.com. That document also lists major changes from
the previous HP-UX 11.0 and HP-UX 11i v1 releases.
• Read Before Installing or Updating to HP-UX 11i v1 - contains
critical, late-breaking installation issues that are not included in this
document
• HP IT Resource Center - download the latest patches and patch

information at: http://itrc.hp.com
Select the maintenance and support for hp products page, then select
the appropriate Patching tools. To receive HP Security Bulletins,
select: maintenance and support for hp products -> support information
digests (under the notifications heading).
• HP Workstation and Server Information - find out about the

latest HP workstations and servers.
For workstations, see http://www.hp.com/workstations/
For servers, see http://www.hp.com/products1/unixservers/
• Ignite-UX - for information and downloads see:
• Latest versions of HP-UX manuals and white papers:

http://docs.hp.com/hpux/os/11i/
• HP-UX 11.0 Software Transition Kit - for more information, see
http://devresource.hp.com/STK/
• HP-UX Support Plus:
http://software.hp.com/SUPPORT_PLUS/
28 Chapter 1
Choosing a Migration Path
2 Choosing a Migration Path
This chapter provides information and scenarios to help you decide the
most appropriate method to move your system to HP-UX 11i v1.
What You Will Find in This Chapter:
• “Migrating from Previous HP-UX Releases” on page 30 details the

supported paths based on your current version of HP-UX 11i v1.
• “Deciding Which Method to Use” on page 31 defines the supported
methods for moving to HP-UX 11i v1 and offers addition information
to consider when making your decision.
• “If You Have an Existing HP-UX 11i v1 System...” on page 41 details
the bundles that will be updated if you are already running HP-UX
11i v1.
IMPORTANT If your system is on HP Mission Critical Support, discuss the proper

method of installing and patching the Mission Critical OE with your HP
Customer Engineer.
Chapter 2 29
Migrating from Previous HP-UX Releases
Migrating from Previous HP-UX Releases

You can cold-install HP-UX 11i v1 and its accompanying operating
environment on any supported system listed in Table 3-1, “Supported
Systems,” on page 48, running any HP-UX OS. If you choose to update
an existing HP-UX OS to the December 2003 version of HP-UX 11i v1,
the system must be running either HP-UX 10.20 or 11.0. If you are
updating from a previous HP-UX 11i v1 release, see “If You Have an
Existing HP-UX 11i v1 System...” on page 41. Updating from any other
release directly to HP-UX 11i v1 is not a supported migration path.
Table 2-1 Migrating from Previous HP-UX Releases
To this HP-UX 11i v1 release with or without an

From:
operating environment:a
HP-UX 9.x, 10.01, Cold-install HP-UX 11i v1 or update to HP-UX 10.20

or 10.10 before updating to HP-UX 11i v1.b
HP-UX 10.20 Cold-install HP-UX 11i v1 or update.b
HP-UX 10.30 Cold-install HP-UX 11i v1 or update to HP-UX 11.0

before updating to HP-UX 11i v1.b
HP-UX 11.0 Cold-install HP-UX 11i v1 or update.b
HP-UX 11.10 Cold-install HP-UX 11i v1.c
HP-UX 11i v1 Update HP-UX 11i v1 OS and/or OE.b
a. Contents of the HP-UX operating environments are listed in the Read

Before Installing or Updating to HP-UX 11i v1 Media booklet supplied
with the 11i OE Media.
b. Update using update-ux command. You can also change from 32-bit to
64-bit OS and install patches and other applications using an install
archive.
c. Cold-install HP-UX 11i v1 using Ignite-UX install tool. You can also
change from 32-bit to 64-bit OS and install patches and other
applications using an install archive.
For help updating from HP-UX 10.20 or 10.30, use the Software
Transition Kit available at this web site:
http://devresource.hp.com/STK/
30 Chapter 2
Deciding Which Method to Use

Now that you have evaluated your system and ordered any additional
needed hardware, you need to decide whether to cold-install HP-UX 11i
v1 on your system or update it.
Cold-install means installing system software on a new (un-installed)
or existing system disks by completely rebuilding the volume group (see
“Back up Your System!” on page 93), erasing the existing operating
system and data on that volume and installing the new operating system
and specified software and data. An advantage of cold-install is that
supported software can be installed without regard for the software
currently on the system, or concern for cleaning up old software.
Update means using the update-ux command and Software Distributor
(SD) tools to selectively overwrite the operating system and application
software from a media or network source depot. An advantage of
performing an update is that it leaves user data, configuration, and
applications in place. Updating to HP-UX 11i v1 requires that the system
be running at 10.20 or 11.0, with or without extension or Additional Core
Enhancement (ACE) packs installed.
CAUTION If the Distributed File System (DFS) is installed and in use on your
HP-UX 10.20 system to manage large numbers of files, update-ux will
remove it and associated data during the update to HP-UX 11i v1. If you
need to continue using DFS, do not update to HP-UX 11.x or HP-UX
11i v1.
Depending on your system’s current configuration, here are some general

guidelines to help you choose the best migration path to HP-UX 11i v1.
Cold Install When...

We recommend using Ignite-UX to cold-install HP-UX 11i v1 in the
following situations:
• You are managing several systems with similar OS configurations.

• You need fast, predictable deployment.
Chapter 2 31
• Your disk space needs reconfiguration. See “Planning Your Disk

Space Needs” on page 90.
• Your systems are organized with clean separation of the OS from
user, application and data files.
You can cold-install from any supported HP-UX OS. (See Table 3-1,
“Supported Systems,” on page 48.)
The cold-install process using Ignite-UX is described in Chapter 5. See
“Preparing to Cold-Install Your System” on page 95 for more
information.
Update When...
You can update rather than cold-install HP-UX 11i v1 when you are
updating from HP-UX 10.20 or 11.0 as well as the following:
• You are only updating a few (1-3) systems to HP-UX 11i v1.
• You are concerned about recovering unique applications and data on
your root volume, and do not want to write over non-OS files when
installing HP-UX 11i v1.
• Each system has a unique configuration.
• Current disk space is sufficient for HP-UX 11i v1 (see “Planning
Your Disk Space Needs” on page 90).
IMPORTANT If /stand is not of sufficient size, the partition can be resized,

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

Chapter 6. See “Preparing to Update Your Existing System” on page 96
for more information about preparing to update your system.
Additional Considerations (Cold-install or Update)
Firmware Patches Should Not Be Included In Cold-Install or

Update Session
If you are migrating from either HP-UX 10.20 or HP-UX 11.0, HP
strongly recommends you do not include firmware patches while running
a cold-install or update session.
How Do You Know The following systems are affected:

If This Affects
You? • A-Class
• L-Class
• N-Class
Many of the HP-UX 11i v1 firmware patches rely on HP-UX 11i v1 tools
and system calls. The cold-install or update process uses a subset of
existing commands and system calls. The firmware installation fails
because of system call differences between the HP-UX 11i v1 operating
system and the install session version.
What To Do: HP strongly recommends that you install any firmware patches after you
have completed the cold-install or update process and your system is
running HP-UX 11i v1. Specific HP-UX 11i v1 firmware patches are
available at the following website:
http://itresourcecenter.hp.com
Updating Network Drivers

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

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

Although the Netscape Directory Server (NDS) Version 6.02 is included
in HP-UX 11i v1 OEs, you must explicitly select NDS during the install
or update process. If you do not select NDS, it will not be installed with
HP-UX 11i v1. For more on this, see “Updating Netscape Directory
Server” on page 137.
NOTE Currently, Netscape Directory Server Version 6.02 is included with the
HP-UX 11i v1 Operating Environments. If you wish to have the iPlanet
5.0 product, order the AR1202 CD or DVD for this product separately.
CAUTION If you have NDS version B.02.00.05 and are updating to HP-UX 11i v1,
be sure to either select the new version of NDS during the update or
remove the old version from your system. If you run NDS version
B.02.00.05 with HP-UX 11i v1, the server will cease to work and all
client systems may lose the ability to have anyone log in.
After NDS is installed or updated with HP-UX 11i v1, additional

configuration steps are required to initiate NDS. See the NDS release
notes available on the HP-UX 11i v1 Instant Information CD for
instructions.
34 Chapter 2
HP 3D Graphics No Longer Supported pre-PA-RISC 2.0 Systems

As of the September 2002 HP-UX 11i v1 release, HP 3D Graphics are no
longer supported on PA-RISC systems older than version 2.0. If you have
an older PA-RISC workstation and need 3D Graphics, HP recommends
that you do not install or update to the this release of the Technical
Computing (TCOE) or Minimal Computing Operating Environments
(MCOE).
Previous releases of HP-UX 11i v1 still support PA-RISC 2.0 and older
systems. If you have any questions about your particular situation,
please contact your local HP Country Response Center.
How to Determine Your PA-RISC Version

With the System Administration Manager (SAM), select: Performance
Monitors > System Properties. Your PA-RISC version will appear next
to the CPU Version line.
Small Memory Systems (<1GB/CPU) May Need to Configure

VxFS 3.5 Tunables After Install/Update
If you have a system with less than 1GB/CPU of RAM, and you plan to
use VxFS 3.5, you may need to modify some of the default VxFS tunables
for optimal performance after you install or update your system to
HP-UX 11i v1. For more information, see Appendix E, “Controlling
Memory Utilization of VxFS 3.5 on HP-UX 11i v1,” on page 223
Update Considerations
The following sections provide additional information to assist you in
your decision to update to HP-UX 11i v1:
Update May Fail If Latest Version of Update-UX is Not Installed

If your updating from the June 2003 HP-UX 11i v1 release or earlier, you
must installed the latest version of Update-UX prior to updating your
system if your system has one of the following DCE Client IPv6 patches
installed:
• PHSS_24261
• PHSS_25473
• PHSS_25710
Chapter 2 35
• PHSS_26394
• PHSS_27258
To determine if any of these patches are installed on your system, enter
the following:
/usr/sbin/swlist -l patch | grep <patch_name>
If any of these patches appear in standard output, you have the patch
installed and need to install the latest version of Update-UX before
starting the update process.
See “Step 1: Install the update-ux Command (Required Task!)” on
page 128 describes the steps required to install the latest version of
Update-UX.
VxVM Rootability Not Enabled with update-ux

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

page 39
• using the VxVM conversion tools provided in the Base-VXVM and
FEATURE11-11 bundles that are installed with HP-UX 11i v1 (for
more information about HP-UX 11i v1 software bundles, see “What
is Installed with HP-UX 11i v1?” on page 76). For more information,
see the VERITAS Volume Manager 3.5 Release Notes and VERITAS
Volume Manager 3.5 Administrator’s Guide on the Instant
Information CD
Updating to 64-bit OS
update-ux defaults to the OS word-width that your system is currently
running. For example, if the target system is running 32-bit OS, this will
be the default for the new OS to be installed.
NOTE Changing an existing 64-bit OS to 32-bit is not supported. To return a

64-bit OS to 32-bit, use the Ignite-UX make_tape_recovery or
make_net_recovery command to restore the 32-bit OS.
36 Chapter 2
Updating You can update a system from 32-bit OS to 64-bit OS while updating to
considerations HP-UX 11i v1, provided that you consider these hardware and firmware
and workarounds issues:
• Is your system capable of running 64-bit operation? See Table 3-1,

“Supported Systems,” on page 48 in Chapter 3.
• Is your system’s firmware recent enough to support 64-bit operation?
See “Firmware Requirements” on page 53 in Chapter 3.
• 64-bit binary data cannot be used by 32-bit applications. 64-bit is
useful if you need large address space, such as for use with very large
databases and large-scale modeling. 64-bit applications can be
compiled and linked on 32-bit systems; however, these applications
cannot be run on a 32-bit system.
• If updating an existing HP-UX 11i v1 system from 32-bit to 64-bit
OS, do not include the HP-UX 11i v1 Quality Pack (GOLDQPK11i)
bundle in the update-ux command. Doing so may cause a mk_kernel
failure. Instead, install the GOLDQPK11i bundle from the Support
Plus CD using swinstall after updating to this release.
• If updating an HP-UX 10.20 system with the CDE Spanish language
keyboard enabled: After updating from HP-UX 10.20 to HP-UX 11i
v1, changing from 32-bit to 64-bit OS and installing the HP-UX 11i
v1 Quality Pack (GOLDQPK11i) bundle, you must install patch
PHSS_23644 (or superceding patch PHSS_23818) from the
GOLDBASE11i quality pack bundles on the latest Support Plus CD
to re-enable the CDE Spanish language keyboard. Obtain this patch
from the HP IT Resource Center (http://itrc.hp.com). This
problem does not occur with other languages.
• If updating an existing HP-UX 11i v1 system having any of the
following EISA network drivers installed, you must remove all EISA
drivers before updating from 32-bit to 64-bit OS:
— 100BaseT-00 — EISA 100BaseT

— FDDI-03 — EISA FDDI
— TermIO-01 — EISA MUX
— TokenRing-02 — EISA Token Ring
(New drivers installed by default are listed in “HP-UX 11i v1
Always-Installed Network Drivers” on page 82. Other drivers can be
specified in the update-ux command or installed later using
swinstall.)
Chapter 2 37
To determine if any EISA drivers are installed on the system, use

swlist. For example:
/usr/sbin/swlist -l bundle 100BaseT-00 FDDI-03 \
TermIO-01 TokenRing-02
If any EISA drivers are on the system, remove them. For example, to
remove the TermIO-01 EISA MUX driver, as root enter:
/usr/sbin/swremove -x autoreboot=true TermIO-01
The kernel will automatically regenerate and the system will reboot
after you remove each driver. After removing all EISA drivers,
proceed to update as explained below.
If you're updating from HP-UX version 11.0 or higher, update-ux will
determine if your hardware and firmware are compatible with 64-bit
operation. If you're updating from HP-UX version 10.20, however, refer
to the Software Transition Kit available on the HP-UX Applications
media. The STK contains tools and documents to assess applications or
libraries that run on HP-UX 10.20 and 11.0 and help transition them to
the HP-UX 11i v1 64-bit operation. The ITRC web site
(http://www.itresourcecenter.hp.com/) also has release notes and a
FAQ with details about supported systems and necessary firmware
updates.
38 Chapter 2
Cold-Install Considerations
The following sections provide additional information to assist you in
your decision to cold-install HP-UX 11i v1:
Using VxVM Rootability

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

HP-UX must be installed on the boot disk assigned to each partition
after the partition has been configured. Configuring the boot disk is
explained in the HP System Partitions Guide manual, available on the
HP-UX 11i v1 Instant Information CD and on HP’s user-documentation
web site:
http://docs.hp.com
Once each partition has been configured for installation, follow the
cold-installation instruction on the following pages to install HP-UX on
each partition’s boot disk.
Instant Ignition
For customers ordering new systems with the “Instant Ignition” option
(also known as “factory integrated”), the cold-installation process
described here has already been performed. Skip this chapter and
proceed to install application software.
Alternate Cold-Install Methods

In addition to the procedures described in this chapter, you can
cold-install your system using the following methods:
Installing From Software Depots Use Software Distributor

commands to create depots containing OS, OE, and other software
bundles, then install from the depot using Ignite-UX. For help with this
method, see the swinstall (1M) manpage and Software Distributor
Administration Guide and Ignite-UX Administration Guide.
Chapter 2 39
Installing from Golden Images If you need to install the same

OS/OE and applications on many systems in your network, use an
Ignite-UX server as explained in the Ignite-UX Administration Guide.
With Ignite-UX, you can create a single install image (golden image)
containing OS/OE bundles, application bundles and patch bundles, then
install the image on multiple systems in your environment.
40 Chapter 2
If You Have an Existing HP-UX 11i v1 System...
If You Have an Existing HP-UX 11i v1 System...

If your system is already running HP-UX 11i v1, you may only need to
install one or more patch bundles to bring your system up-to-date or to
enable new hardware. Rather than doing a complete migration to the
current HP-UX 11i v1 OS or OE, consider using swinstall to install the
latest patch bundles to meet your system needs:
Table 2-2 December 2003 Patch Bundles (By Media Location)
HP-UX 11i
Patch Bundle Description
v1 OE Media SupportPlusa
HWEnable11i Enables new hardware and

delivers critical patches for X X
HP-UX 11i v1 systems.
GOLDBASE11i Defect fixes for HP-UX 11i

v1 OS and network drivers Xb
included in OEs.
GOLDAPPS11i Defect fixes for HP-UX 11i

Xb
v1 OE applications.
a. Support Plus bundles are available quarterly via CD and the

Web. For more details and to download recent bundles, see this
web site: http://software.hp.com/SUPPORT_PLUS/
b. These bundles contain patches with the highest ratings from

tests in HP’s Enterprise Patch Test Center.
For instructions on installing patch bundles on an existing HP-UX 11i v1

system, see Chapter 6, “Updating to HP-UX 11i v1,” on page 115
Chapter 2 41
Cold-Installing or Updating from DVD media
Important: Problems Reading HP-UX 11i v1 DVD

Media During Update
The HP-UX 11i v1 DVD media contain large volumes of data that may
cause your DVD device to fail while reading the DVD media contents
during an update. This particularly affects you if you use Update-UX or
other Software Distributor (SD) tools. For example, you may encounter
similar error messages if you attempt to read DVD media with a large
volume of data from Update-UX:
ERROR: File "/dvd/catalog/SOE/SOE.2/INFO": No such file or
directory(2). Cannot copy it to file
"/var/tmp/BAAa04482/catalog/SOE/SOE.2/INFO".
ERROR: File "/var/tmp/BAAa04482/catalog/SOE/SOE.2/INFO" does

not exist.
ERROR: The catalog files for product "SOE,r=B.11.11" failed to

load. Check the above output for details.
ERROR: Cannot continue the Analysis Phase until the previous

errors " are corrected.
To resolve this problem, do one of the following:
• install the appropriate patches listed below before you update to the
latest version of HP-UX 11i v1 (recommended), or
• use the pfs_mount (1M) command to mount the DVD
To patch your system use the following patches (patch descriptions are in
parenthesis) for your current OS version:
NOTE The HP-UX 11i v1 patches listed below are included in the December
2003 (and later) version of the HP-UX 11i v1 install kernel. If you are
planning to cold-install HP-UX 11i v1 (December 2003 or later), you do
not need to install these patches, nor do you need to use the pfs_mount
(1M) command to mount the DVD.
42 Chapter 2
For Systems Currently Running HP-UX 11i v1:
• PHKL_26269 (11.11 Rock Ridge extension for ISO-9660)

• PHCO_25841 (11.11 Add Rock Ridge extension to mount_cdfs (1M))
For Systems Currently Running HP-UX 11.0:
• PHCO_26450 (11.00 Y2k; Rock Ridge extension for ISO-9660)

• PHKL_28060 (11.00 Add Rock Ridge extension to mount_cdfs (1M))

There are no patches available. Use the pfs_mount (1M) command to
mount the DVD and update to HP-UX 11i v1
Determining If You Need to Install the Patches

To determine if your system already has the listed patches installed, run
the following:
where <patch_name> is one of the patches listed above for your operating
system version. If nothing is printed to standard output, you need to
install the patches from one of the following sources:
• the GOLDBase11i bundle on the Support Plus CD (June 2003 or later)

for HP-UX 11i v1
• the QPK1100 bundle on the Support Plus CD (September 2003 or
later) for HP-UX 11.0
• the IT Resource Center website (requires login):
http://itrc.hp.com
• the anonymous IT Resource Center FTP site:
ftp://ftp.itrc.hp.com
Chapter 2 43
DVD Media Advantages

With the December 2002 release of HP-UX 11i v1, you can choose to
either cold-install or update from either CD-ROM or DVD media.
Digital Versatile Disks (DVD) provide you with several benefits
compared to CD-ROM:
• fewer disks containing all of the data needed to install or update to

HP-UX 11i v1
• no disks to shuffle during installation - all of the core HP-UX 11i v1
operating system software is contained on one DVD
• fewer installation steps
• shortened installation times
DVD Availability
DVD drives are now available for both PA-RISC servers and
workstations. Contact your HP Customer Engineer for more details
about your system’s requirements.
44 Chapter 2
How is the New DVD Packaging Organized?

Because DVDs can hold significantly more data (over 4GB vs. 650MB for
CD-ROM), the HP-UX 11i v1 operating environment, and all of the
HP-UX 11i v1 applications have been optimized to fit on 1 DVD each.
Figure 2-1, “Comparison of CD-ROM and DVD Packaging,” shows you
the differences between CD-ROM and DVD packaging:
Figure 2-1 Comparison of CD-ROM and DVD Packaging
HP-UX 11i v1 OE (3 CDs) HP-UX 11i v1 OE (1 DVD)
HP-UX 11i v1 Applications HP-UX 11i v1 Applications

(1 DVD)
Support Plus (1 CD) Support Plus (1 CD)
Software Pack (1 CD) Software Pack (1 CD)
Instant Information (1 CD) Instant Information (1 CD)

CD-ROM ONLY DVD
Chapter 2 45
Next Steps
Next Steps
Once you have decided how you want to move to HP-UX 11i v1, you can
now evaluate the system requirements to run HP-UX 11i v1 against your
system’s configuration. For more information please read Chapter 3,
“Install/Update System Requirements,” on page 47 for detailed
information about:
• “System Requirements” on page 48

• “Firmware Requirements” on page 53
• “PCI Adapter Requirements” on page 65
• “Disk Space and Memory Requirements” on page 66
IMPORTANT Be sure to review the Read Before Installing or Updating to HP-UX 11i
v1 media booklet for situations not discussed in this chapter that may
apply to your system.
46 Chapter 2
Install/Update System Requirements
3 Install/Update System
Requirements
This chapter will help you determine how prepared your system
(hardware, OS, disk space, etc.) is to support HP-UX 11i v1.

• “System Requirements” on page 48
• “Firmware Requirements” on page 53
• “Disk Space and Memory Requirements” on page 66
• “PCI Adapter Requirements” on page 65
IMPORTANT Be sure to review this entire guide and the “Known Problems”
information in the Read Before Installing or Updating to HP-UX 11i v1
media booklet for December 2003 before proceeding to install or update
your system. Carefully review Appendix B, “Known Problems and
Troubleshooting,” on page 169 for situations that may apply to your
system.
If you have just received a system that was ordered with “Instant
Ignition,” the HP-UX 11i v1 Operating Environment has already been
installed. You do not need to re-install it.
Chapter 3 47
System Requirements
System Requirements
This section lists systems that support HP-UX 11i v1. Unsupported
systems are also listed in “Unsupported Systems” on page 51. To
determine if HP-UX 11i v1 is supported on your system, see “How to
Identify Your System’s Model, OS and Software” on page 50 and compare
your system information with Table 3-1.
Supported Systems
HP-UX 11i v1 is supported on the HP servers and workstations listed
below (newly supported systems are shown in bold).
Table 3-1 Supported Systems
Bezel or Model 32-bit 64-bit
Workstations:
Series 700: 712, 715/64/80/100/100XC, 725/100,

X
743, 744, 745, 748i, 748
B132L, B132L+, B160L, B180L X
B1000, B2000, B2600 X
C100, C110, C160L X
C160, C180, C180-XP, C200, C240, C360 X X
C3000, C3600, C3650, C3700, C3750 (See

“Firmware Requirements” on page 53 for X
additional requirements)
J200, J210, J210XC X
J280, J282, J2240 X X
J5000, J5600, J6000, J7000, J6700, J6750 (See

“Firmware Requirements” on page 53 for X
additional requirements)
48 Chapter 3
System Requirements
Table 3-1 Supported Systems (Continued)
Servers:
A180, A180C X
A400, A500 X
Dx10, Dx20, Dx30, Dx50, Dx60 X
Dx70, Dx80, Dx90 X X

Kx00, Kx10, Kx20 X
Kx50, Kx60, Kx70, Kx80 X X
L1000, L1500, L2000, L3000 X

N4000-36, N4000-44 X
R380, R390 X X
rp2400, rp2450 (HP-UX model string is A4xx-xx

or A5xx-xx. Use the model command to display X
the model string.)
rp3440 X X
rp4440 X X
rp5405 (HP-UX model string is L3000-6X) X

rp5400, rp5430, rp5450, rp5470 (HP-UX model
X
string is Lxxxx-xx)
rp7400 (HP-UX model string is N4000-7X or

X
N4000-8X)
rp7405 and rp7410 X

rp8400 (model S16K-A) X
Superdome (models SD16000, SD32000, SD64000) X
T500, T520 X
T600 X X
Chapter 3 49
System Requirements
Table 3-1 Supported Systems (Continued)
V22xx, V2500, V2600 X
For the latest list of supported systems, see the “what systems are
supported” question on this web site:
http://devresource.hp.com/STK/hpux_faq.html#C1
How to Identify Your System’s Model, OS and Software

The following topics will show how to obtain your current system
information:
Identify model To determine the model number of your system, enter:

model
Verify that HP-UX 11i v1 is supported on your system (see Table 3-1,
“Supported Systems,” on page 48).
Identify OS and OE To identify the OS version that your system is currently running, enter:
uname -r
To update to HP-UX 11i v1, your system must be currently running
either B.10.20 or B.11.00. After cold-installing or updating to
HP-UX 11i v1, you’ll notice that uname identifies the HP-UX 11i v1
release as B.11.11.
When a system has HP-UX 11i v1 installed, you can determine which
revision of HP-UX 11i v1 is installed by entering the following command:
/usr/sbin/swlist -l bundle
The HWEnable11i and HPUXBaseAux bundles indicate the current
installed revision level. The revision level is indicated both in the bundle
version number (for example, B.11.11.0603) and the description text
(for example, Hardware Enablement Patches for HP-UX 11i,
December 2003).
To identify the Operating Environment currently installed on your
system, use swlist. For example:
/usr/sbin/swlist | grep “OE Component”
50 Chapter 3
System Requirements
For example, the HP-UX 11i v1 Technical Computing OE December 2003

release generates the following output:
HPUX11i-TCOE B.11.11.1203 HP-UX 11i Technical Computing OE Component
Identify installed To identify the software products on a system or media, use swlist. For
software example, to list all products and their versions on a CD mounted at
/cdrom, enter:
/usr/sbin/swlist -s /cdrom
To get a table of contents and product details, enter:
/usr/sbin/swlist -dvl product -a readme @ /cdrom
swlist has many options to expand or narrow the listing to specific
attributes; see the swinstall (1M) manpage or the Software Distributor
Administrator Guide, available on the HP-UX 11i v1 Instant Information
CD and on this web site: http://docs.hp.com/hpux/os/11i/
After identifying all software products, compare the list with products
that will be installed with the HP-UX 11i v1 Operating Environment.
See the Read Before Installing or Updating to HP-UX 11i v1 media
booklet.
Unsupported Systems
These workstations and graphics adapters are no longer supported:
• Workstations: 705, 710, 715/33, 715/50, 715/75, 720, 725/50, 725/75,

730, 735, 750, 755
• Graphics adapters: GRX, CRX, CRX-24, CRX-48Z
• HP J3525A and J3526A PCI cards on these workstations: B1000,
B2000, C3X00, J5000, J7000
C3700 and J6700 Workstations Need Processor Board

Upgrade
C3700 and J6700 workstations currently support HP-UX 11.0 but
require PA-8700 processor board upgrades (to version 2.3) to support
HP-UX 11i v1. Contact your HP Customer Engineer for more details.
Chapter 3 51
System Requirements
OLA/R Support
Online addition and replacement (OLA/R) is not supported on HP-UX 11i
v1 with the A5801A HIPPI PCI I/O adapter. For rp7410 servers: slots
0-0-0-1 and 0-0-1-8 are dedicated to the LAN/SCSI card portion of the
MP Core I/O, and do not support OLA/R if cards in these slots are
considered "critical resources". For more about OLA/R support, see
“SCSI PCI Restrictions for OLA/R” on page 199” in Appendix B and this
web site:
http://itrc.hp.com
HP 3D Graphics No Longer Supported pre PA-RISC

2.0 Systems
IMPORTANT As of the September 2002 HP-UX 11i v1 release, HP 3D Graphics are no

longer supported on PA-RISC systems older than version 2.0. If you have
an older PA-RISC workstation and need 3D Graphics, HP recommends
that you do not install or update to the December 2003 release of
the Technical Computing (TCOE) or Minimal Computing Operating
Environments (MCOE).
Previous releases of HP-UX 11i v1 still support PA-RISC 2.0 and older
systems. If you have any questions about your particular situation,
please contact your local HP Country Response Center.
How to Determine Your System’s PA-RISC Version

With the System Administration Manager (SAM), select: Performance
Monitors > System Properties. Your PA-RISC version will appear next
to the CPU Version line:
PA 8600-8600 CPU 3.1
If this lines reads less than 8000, then your CPU version is older than
version 2.0
52 Chapter 3
Firmware Requirements
Some systems may need a firmware upgrade prior to updating to HP-UX
11i v1:
• Servers:
— A-Class
— L-Class
— N-Class
• Workstations:
— B-Class: B1000, B2000

— C-Class: C3000, C3600,
— J-Class: J5000, J5600, J6000, J7000
If you are about to install or upgrade one of the systems listed above,
verify that it has the minimum required firmware version. If needed,
install the patches for your system listed here in the following tables.
If the needed firmware version or later is already on your system,
proceed to “PCI Adapter Requirements” on page 65. If not, or if you do
not know what firmware version is on your system, please read on.
Chapter 3 53
IMPORTANT The information in the following tables represents minimum firmware

requirements. HP strongly recommends that you update your system
firmware with the latest patches available at the following website:
http://docs.hp.com/hpux/hw/index.html#System%20Firmware
Table 3-2 Minimum Firmware Versions for HP-UX 11i v1a
Firmware and Patch for HP-UX 11i v1 Support
Minimum Available Patches

Model or Bezel Firmware
Version Tape Patch
HP-UX 11.0/11i
Name
A-Class 41.18 PHSS_25314

PF_CCRW4118
PHSS_25315
B-Class, C-Class, 5.0 PHSS_25982

PHSS_25983 PF_CBCJ0050
J-Classa
C3650, C3700, 1.9 PHSS_29342

C3750, J6700, PHSS_29341 PF_CCJ70020
J6750
L1000, L2000, 41.38 PHSS_25105

PF_CRHW4138
rp5400, rp5450 PHSS_25106
L3000 Rev A. 40.43 All Firmware n/a
L1500, L3000, 41.36

All Firmware PF_CMAW4136
rp5430, rp5470
N4000, rp7400 41.02 PHSS_22657

PF_CPRW4102
PHSS_22658
a. For older workstations, see Table 3-3
54 Chapter 3
Table 3-3 Older Workstation Firmware Requirements
Firmware 32/64
Model or Bezel
Version bit Tape Patch Namea
B132L, B132L+, 6.1 32-bit PF_CB1X0061

B160, B180
B2600b 1.4 64-bit PF_CB260014
B-Class: 5.0 64-bit PF_CBCJ0050

B1000
B2000
C-Class
C3000
C3600
J-Class:b
J5000
J5600
J6000
J7000
C160L 5.8 32-bit PF_CB1X0058

C160, C180 6.1 32 and PF_CC2X0061
64-bit
C200, C240 6.3 32 and PF_CC2X0063
64-bit
J280, J282 2.5 32 and PF_CJ28X025
64-bit
a. Tape patches are available at http://itrc.hp.com by

selecting individual patches and searching for the specific
models
b. features automatic firmware updates without user
intervention
Chapter 3 55
Table 3-4 Minimum Firmware Versions for OL* Supporta
Firmware and Patch for OL*b Support
Model or Bezel System Minimum Current Patches

Firmware
Version HP-UX 11.0/11i Tape Patch Name
A-Class (A400, (OL* not available on A-Class)

A500)
B-Class, C-Class, (Also, OL* not available on workstations.)

J-Class
L1000, L2000, 41.39 PHSS_25684 PF_CRHW4139

rp5400, rp5450 PHSS_25685
L3000 Rev A. 41.46 PHSS_25686

PHSS_25687
L1500, L3000, 42.19 PHSS_25686 PF_CCAW4219

rp5430, rp5470 PHSS_25687
N4000, rp7400 42.06 PHSS_22688 PF_CPIW4206

PHSS_25931
rp7410 c,e Release PDC rev 17.005 PF_CKEYMAT0600

Version 6.0 MP rev. 4.013
Not Customer
Installable
rp8400 c,e Release PDC rev 17.005 PF_CKEYMAT0600

MP rev. 4.013
Version 6.0d Not Customer
Installable
Superdomee Release PDC rev. 36.1 Not Customer

Version 5.1 MP rev. 7.26 Installable
a. The latest system firmware is required for OL* operations on

supported servers.
b. OL* = OnLine add, delete, and replace
c. For rp7410 and rp8400, the OnLine 'Delete' function is not
enabled. These servers only support OnLine Add/Replace.
56 Chapter 3
d. This firmware is required for enabling systems to use the new

Server Expansion Unit (SEU - see the HP-UX 11i v1 Release
Notes for more information). Current rp8400 customers
wishing to add the SEU to their existing server musts replace
the Core I/O boards in the main chassis with next-generation
Core I/O boards (A7109-60001)
e. System Firmware and Service Processor Firmware are not
customer installable. Please contact your HP Customer
Engineer
IMPORTANT OL* functionality is only supported on HP-UX 11i v1 for servers and PCI
I/O adapaters meeting the OLA/R support requirements. The following
patches are required to support OLA/R with SCSI Ultra160 adapters on
HP-UX 11i v1 servers:
PHCO_25831
PHKL_25712 (or later)
For a more complete list of systems that support OL*, go to the following
web site:
http://docs.hp.com
and search for “Interface Card OL* Support Matrix”
Current System Firmware Versions and Patches

In addition to verifying that your system meets the minimum
requirements to support HP-UX 11i v1 in Table 3-2, the following table
describes the latest recommended firmware versions available for your
system. These patches contain additional enhancements and fixes to
your system and also support HP-UX 11i v1 functionality.
Chapter 3 57
NOTE System firmware versions may change after the printing of this manual.
For further additional up-to-date information, please see the System
Firmware Matrix at the following URL:
http://docs.hp.com/hpux/hw/index.html#System%20Firmware
Table 3-5 Current System Firmware Versions and Patches
Current Firmware Version and Patch Support
Available Patches
Latest
Model or
System SD-UX
Bezel
Firmware Patch Name
Tape Patch Name
Version HP-UX 11i v1
/11.0
B1000, B2000, 5.0 PHSS_25982 PF_CBCJ0050

C3x00, J5x00, PHSS_25983
J6000, J7000
C3650, C3700, 2.0 PHSS_29342 PF_CCJ70020

C3750, J6700, PHSS_29341
J6750
B2600 1.4 PHSS_26926 PF_CB260014

Workstation PHSS_26927
A400, A500, 42.24a,b,c PHSS_28611 PF_CHAW4324

rp24xx PHSS_28612
L1000, L2000, 41.39 PHSS_25684 PF_CRHW4139

rp5400, rp5450 PHSS_25685
L1500, L3000, 43.22b,c,d PHSS_28607 PF_CARIW4322

rp5430, rp5470 PHSS_28608
rp7400 43.22b,c PHSS_28609 PF_CPIW4322

PHSS_28610
rp7410 Release PDC rev. 17.049 PF_CKEYMAT0600

Version MP rev. 4.013
Not Customer Installable
6.0b,c
58 Chapter 3
Table 3-5 Current System Firmware Versions and Patches (Continued)
Current Firmware Version and Patch Support
Available Patches
Latest
Model or
System SD-UX
Bezel
Firmware Patch Name
Tape Patch Name
Version HP-UX 11i v1
/11.0
rp8400 Release PDC rev. 17.049 PF_CKEYMAT0600

Version 6.0 MP rev. 4.013
b,e
Not Customer Installable
Superdome Release PDC rev. 36.5 Not Customer Installable

MP rev. 7.30
Version 5.1c
a. Starting with firmware revsion 42.03, the software id (SWID) was

calculated incorrectly. Firmware revision 42.19 corrects this error and
calculates the SWID correctly. The incorrect SWID prevents the
intallation of HP-UX 11.00 Predictive.
b. Added boot, swap and dump support for the following PCI I/O cards:
A6826A: PCI 2 Port 2GB FibreChannel Card
A7173A: PCI-X 2 Port Ultra320 SCSI Card
A9782A: PCI-X 2GB FC/1000Base-SX (Fibre) Combo Card
A9784A: PCI-X 2GB FC/1000Base-T (Copper) Combo Card
c. Added boot, swap and dump support for A7143A Raid U160 Card (This
new card is not supported on rp8400 and SuperDome servers)
d. Added support for CPU product numbers A6152B and A6805B.
e. This firmware is required for enabling systems to use the new Server
Expansion Unit (SEU - see the HP-UX 11i v1 Release Notes for more
information). Current rp8400 customers wishing to add the SEU to
their existing server musts replace the Core I/O boards in the main
chassis with next-generation Core I/O boards (A7109-60001)
How to Verify Your Firmware Version
Checking Workstation Firmware Version

Follow these steps to check workstation firmware version prior to
migrating to HP-UX 11i v1:
Step 1. As root, shut down the system:
Chapter 3 59
1. Enter: shutdown -h
2. Switch the system OFF.
Step 2. Switch the system ON and watch console messages. Press any key when
prompted to cancel the automatic boot feature.
Step 3. Check the firmware version displayed at the beginning of the boot
process. If the firmware version for your B-, C- or J-Class workstation is
less than 2.3, it needs upgrading. Continue with “How to Download
Firmware Upgrades” on page 63.
NOTE HP continues to revise the firmware for all the systems listed above,
adding support for more types of plug-in PCI cards and memory modules
and improving the ability to debug dump output for OC/HPMC/panic.
Updating to the latest firmware ensures that your workstation takes
advantage of these improvements.
Checking Server Firmware Version

There are two methods to check firmware version on HP servers:
OnlineDiagnostics or the boot display (see page 61). Use
OnlineDiagnostics if you do not want to reboot your system.
Using OnlineDiagnostics: If the OnlineDiagnostics are not already

on your system, you can find them on the HP-UX 11i v1 Support Plus
CD, or on your OE media (CD or DVD).
Step 1. As root, run the Support Tools Manager (STM) utility:

/usr/sbin/cstm
Step 2. Use the map command to find the device number (Dev Num) for the
processors on your system; search for items with the product description
CPU:
cstm>map
systemA.hp.com
Dev
Num Path Product
=== ==================== =========================
1 system system ()
60 Chapter 3
...
34 160 CPU (5c4)
35 166 CPU (5c4)
Select any one of the processors (CPU) to use in the next step.
Step 3. Use the CPU device number as input to the sel dev command to request
information on that processor. For example:
cstm>sel dev 34; info

-- Updating Map --
Updating Map...
Step 4. Use the information log command (il) to find the firmware version
number:
cstm>il
-- Converting a (5060) byte raw log file to text. --
... (output lines are omitted)
-- Information Tool Log for CPU on path 160 --

Log creation time: Wed May 10 10:21:53 2000
Hardware path: 160
...(output lines are omitted)
Firmware Revision: 40.14
Step 5. Enter q to leave this screen. Then press Enter at the next prompt, and
enter exit to exit the utility.
Step 6. If your system requires a firmware upgrade, proceed to “How to

Download Firmware Upgrades” on page 63
Using the Boot Display (this requires a reboot):
Step 1. As your system is booting up, interrupt the auto-boot sequence by

pressing any key when prompted. For example:
...
Primary boot path: 0/0/2/0.2
Alternate boot path: 0/0/2/0.2
Console path: 0/0/4/0.0
Keyboard path: 0/0/4/0.0
Processor is booting from first available device.
To discontinue, press any key with 10 seconds.
Chapter 3 61
Step 2. You’ll see the boot Main Menu:

---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
...
HElp [<menu>|<command>] Display help for menu or command
RESET Restart the system
Main Menu: Enter command or menu>
Enter: IN (for INformation)
Step 3. You’ll see the information menu:

---Information Menu-------------------------------------------
Command Description
------------ --------------
ALL Display all system information
BootINfo Display boot-related information
Cache Display cache information
ChipRevisions Display revisions of major VLSI
FRU Display FRU information
FwrVersion Display firmware information
...
Main Return to Main Menu
Information Menu: Enter command>
Enter: FV (for Firmware Version)
You’ll see something like the following:
FIRMWARE INFORMATION
Firmware Version: 40.14
Step 4. Continue with the boot (example commands are in bold):
62 Chapter 3
Information Menu: Enter command > BO PRI

Interact with IPL (Y, N, or Cancel)?> N
Booting...
Step 5. If your system requires a a firmware upgrade, proceed to “How to

Download Firmware Upgrades” on page 63
How to Download Firmware Upgrades
NOTE To get a firmware patch free of charge via ftp:

For the Americas and Asia-Pacific:
ftp://us-ffs.external.hp.com
For Europe:
ftp://europe-ffs.external.hp.com
To get a firmware patch over the Web:
Step 1. Go to this web site:

http://itrc.hp.com/
From the home page, select individual patches.
Step 2. If you are already registered, log in with your user ID and password. If
not registered, following the instructions on the screen. Remember to
save your user ID and password.
Step 3. From the patch database main page, select hp-ux.
Step 4. Select Series 700 for workstations or Series 800 for servers.
Select the OS your system is running, either 10.20 or 11.00.

Step 5. Choose Search By Keyword, enter the patch name for your system listed
on Table 3-1, “Supported Systems,” on page 48 and click search.
The patch you entered or its successor should be listed. Select that patch
(click select all, then add to selected patch list, then download). Ignore any
comments that the firmware patch is “Not yet HP recommended”.
Chapter 3 63
Step 6. After downloading the patch, proceed to “How to Apply Firmware

Patches” on page 64.
How to Apply Firmware Patches

Follow these steps to install each patch you’ve downloaded on each
system prior to updating it to HP-UX 11i v1:
Step 1. Back up your system!
Step 2. Log in as root.
Step 3. Copy the patches to the /tmp directory.
Step 4. Change your working directory to /tmp and extract each patch using the
sh command. For example, to extract patch PHSS_23184:
cd /tmp
sh PHSS_23184
Step 5. Run swinstall to install each patch. For example:
/usr/sbin/swinstall -x autoreboot=true -x \
patch_match_target=true -s /tmp/PHSS_23184.depot
CAUTION Do not interrupt the update process. Do not power down the system
or resume similar actions during the update. The process requires
multiple reboots. Once the system has rebooted HP-UX completely, it is
safe to perform any other normal operation.
64 Chapter 3
PCI Adapter Requirements
PCI Adapter Requirements

Before installing HP-UX 11i v1, be sure to replace any HP A3740A PCI
adapters in your system with A5158A PCI Tachyon TL adapters. The
A3740A PCI adapter is not supported on HP-UX 11i v1. Connect any
fibre channel mass storage devices previously connected to A3740A to
the A5158A adapters.
Chapter 3 65
Disk Space and Memory Requirements

update-ux checks for required swap space but does not check for
minimum memory. For more information, see “Adjusting Required
Minimum File System Sizes” on page 68 for directions on how to
increase file system sizes.
To update your HP server or workstation to HP-UX 11i v1, it must have
the following:
• All servers require a minimum of 128 MB (256 MB recommended).

Exceptions include the following:
— A-Class servers with HP A5838A LAN-SCSI Combo Card: 256

MB minimum
— All other systems: 64 MB minimum (256 MB recommended)
• Total swap space required when updating or installing is 1 GB. A
minimum of 128 MB of free swap space is required.
• LVM or VxVM partitions:
— / (root): 30 MB free space

— /usr: 220-771 MB free space (see Table 3-6, Free Disk-space
Requirements for /usr and /opt,)
— /stand: 100 MB free space (to expand /stand, see “Increasing
/stand” on page 70)
— /var: 160 MB free space.
— /opt: 225-685 MB free space (see Table 3-6, “Free Disk-space
Requirements for /usr and /opt,” on page 67)
• 4GB root disk, minimum, whether installing or updating to HP-UX
11i v1, with or without an OE. This can be a single disk drive or
combination of physical disks configured as one root volume.
66 Chapter 3
Disk-space requirements for the /usr and /opt partitions depend upon
the update task. Typical requirements for various updates are listed
next.
Table 3-6 Free Disk-space Requirements for /usr and /opt
HP-UX 11i v1 Update Task /usr /opt
10.20 -> 11i default update: HPUXBase, 400 MB 225 MB

HPUXBaseAux, network drivers, CDE and
OnlineDiag
10.20 -> 11i Foundation OE 681 MB 525 MB

10.20 -> 11i Enterprise OE 731 MB 685 MB
10.20 -> 11i Mission Critical OE 771 MB 685 MB
10.20 -> 11i Technical Computing OE 731 MB 885 MB

10.20 -> 11i Minimal Technical OE 681 MB 665 MB
11.0 -> 11i default update: HPUXBase, 220 MB 225 MB

HPUXBaseAux, HWEnable11i, BUNDLE11i,
network drivers, CDE and OnlineDiag.
11.0 -> 11i Foundation OE 531 MB 435 MB

11.0 -> 11i Enterprise OE 591 MB 635 MB
11.0 -> 11i Mission Critical OE 611 MB 635 MB
11.0 -> 11i Technical Computing OE 591 MB 955 MB

11.0 -> 11i Minimal Technical OE 531 MB 575 MB
11i (no OE) -> 11i Foundation OE 320 MB 415 MB
11i (no OE) -> 11i Enterprise OE 372 MB 645 MB

11i (no OE) -> 11i Mission Critical OE 410 MB 645 MB
11i (no OE) -> 11i Technical Computing OE 372 MB 820 MB
11i (no OE) -> 11i Minimal Technical OE 372 MB 385 MB
Chapter 3 67
Extra space Cold-installing the HP-UX 11i v1 Technical Computing OE and the
needed with TCOE Minimal Technical OE installs all CDE languages, rather than just a
and MTOE selected language. To remove unneeded CDE language bundles after
installing the TCOE or MTOE, list them using swlist and remove
unneeded bundles using swremove. See Chapter 7 for example uses of
swlist and swremove.
IMPORTANT Any last-minute install and update issues are described in the Read
Before Installing or Updating to HP-UX 11i v1 booklet supplied with the
HP-UX 11i v1 CD or DVD media. Be sure to review that booklet as well
as Appendix B, “Known Problems and Troubleshooting,” on page 169
before continuing.
Adjusting Required Minimum File System Sizes
Update Requirements
If the required file-system size for the bundle you copy to a depot exceeds
the file system limit set by your disk installation, you will get an error
condition during the copy process. You can use lvextend and extendfs
in this situation to create a larger file system.
You might have a problem updating your systems if any of these volumes
are too small: /usr, /opt, /stand or /var.
If you try an update, swinstall will determine how much disk space is
required. If sufficient space is not available, swinstall will report an
error like this:
ERROR: The used disk space on filesystem "/var" is estimated
to increase by 57977 Kbytes.
This operation will exceed the minimum free space for this
volume. You should free up at least 10854 Kbytes to avoid
installing beyond this threshold of available user disk space.
In this example, you would need to increase the file system size of /var
by 10 MB, which actually needs to be rounded up to 12 MB.
Increasing /var
Follow these steps to increase the size limit of /var:
Step 1. Determine if any space is available for the /dev/vg00:
68 Chapter 3
/sbin/vgdisplay /dev/vg00
You should see output like this:

- Volume groups -
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 8
Open LV 8
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 2000
VGDA 2
PE Size (Mbytes) 4
Total PE 249
Alloc PE 170
Free PE 79
Total PVG 0
The "Free PE" indicates the number of 4MB extents available, in this
case 79 (equivalent to 316 MB).
Step 2. Change to single user state:

/sbin/shutdown
This will allow /var to be unmounted.
Step 3. View mounted volumes:

/sbin/mount
You will 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
Step 4. Determine which logical volume maps to /var. In this example, it is

/dev/vg00/lvol7
Step 5. Unmount /var:

/sbin/umount /var
Chapter 3 69
This is required for the next step, since 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
Step 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
Step 7. To extend the file system size to the logical volume size:
/sbin/extendfs /dev/vg00/rlvol7
Step 8. Mount /var:
/sbin/mount /var
Step 9. Go back to the regular init state: init 3 or init 4, or reboot.

Step 10. Wait 10 minutes after changing the system state or rebooting to let
processes complete before your enter an update-ux command.
Increasing /stand
IMPORTANT Increasing the /stand partition requires reformatting your root disk.
You will need to cold-install HP-UX 11i v1 on your system.
Before you begin this step, back up your system. See “Back up Your
System!” on page 93.
In some cases, you will need to increase the size of /stand prior to
completing a successful update to HP-UX 11i v1. If the update-ux
command fails with a message indicating that /stand is too small, follow
these steps to increase the size of /stand.
To increase /stand, you’ll first have to create a larger /swap volume,
since both require contiguous blocks and are adjacent volumes. If you
need help with this procedure, refer to the Managing Systems and
Workgroups manual, available on the HP-UX 11i v1 Instant Information
CD and on HP’s documentation web site:
http://docs.hp.com/hpux/os/11i/oe/ or,
70 Chapter 3
http://devrsrc1.external.hp.com/STK/howtosystems.html
Step 1. As root, use sam to create a new contiguous /swap volume of the required
size, say, 300 MB. Name the new volume /dev/vg00/swap.
Step 2. Using sam, verify that there is no bad block relocation and the new
/swap volume is contiguous.
Step 3. As root from a console window, remove and add primary swap and dump
devices:
1. Remove the current dump device:
lvrmboot -v -d lvol2 /dev/vg00
2. Add a new dump device:

lvlnboot -d /dev/vg00/swap
3. Remove the current swap device:
lvrmboot -s /dev/vg00
4. Add a new swap device:
lvlnboot -s /dev/vg00/swap
Step 4. Verify your change by entering:

lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (8/0/19/0.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t6d0
Root: lvol3 on: /dev/dsk/c0t6d0
Swap: swap on: /dev/dsk/c0t6d0
Dump: swap on: /dev/dsk/c0t6d0, 0
Step 5. If your changes are correct, reboot the system.
Step 6. After the system reboots, view swap information by entering:

swapinfo
Kb Kb Kb PCT START/ Kb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 307200 45936 216208 0% 0 - 1 /dev/vg00/swap
Chapter 3 71
reserve - 113748 -113748

memory 85584 23492 62092 27%
Step 7. To verify that the same configuration exists as before the reboot, enter
(again):
lvlnboot -v
Step 8. As root, use sam to remove the old lvol2 entry from /dev/vg00.
Step 9. Using sam, increase /stand to the required new size. Also change the
size of any other volumes as needed.
Step 10. Define your new volume as the boot volume at the next reboot:
lvlnboot -b lvol1 /dev/vg00

Step 11. Reboot your system again.
Return to Chapter 2 to update your system to HP-UX 11i v1 using the

update-ux command.
72 Chapter 3
Next Steps
Next Steps
If your system meets all of the requirements detailed in this chapter, you
are now ready to prepare your system for installation. Chapter 4,
“Preparing To Move To HP-UX 11i v1,” on page 75 will guide you
through important tasks such as:
• listing what is installed with HP-UX 11i v1

• determining which migration path to choose
• preparing your system based on the migration path you have chosen
• backing up your system.
Chapter 3 73
Next Steps
74 Chapter 3
Preparing To Move To HP-UX 11i v1
4 Preparing To Move To HP-UX

11i v1
This chapter helps you to prepare to install or update your system with
HP-UX 11i v1.

• “What is Installed with HP-UX 11i v1?” on page 76 lists the software
bundles and drivers installed with HP-UX 11i v1.
• “Updating Your Ignite-UX Server” on page 88 explains critical next
steps if you are planning to update an existing Ignite-UX server.
• “Diagnostics Dependencies” on page 89 provides a brief description
and importance of the OnlineDiag bundle installed with HP-UX 11i
v1.
• “Planning Your Disk Space Needs” on page 90 provides hints and
information to help you determine your disk needs for HP-UX 11i v1.
• “Preparing your system for HP-UX 11i v1” on page 92 provides an
overview and preparation steps required to either cold-install or
update your system to HP-UX 11i v1.
• “Back up Your System!” on page 93 shows you how to back up your
system before you cold-install or update your system. Three different
backup methods are discussed:
— fbackup on page 93
— make_tape_recovery on page 94
— make_net_recovery on page 94
• “Locate Source Media for Migration” on page 98 helps you determine
the media source to install or update your system with HP-UX 11i
v1.
• “Next Steps” on page 99 provides details on next steps based on your
decision to either cold-install or update your system.
Chapter 4 75
What is Installed with HP-UX 11i v1?

HP-UX 11i v1 is delivered with bundles of applications to help you install
a complete operating system in a single-pass process. Depending on your
needs, your system can install one of five different operating
environments (OE). OEs bundle the operating system, core software
applications and patches, and drivers with additional applications to
meet your system’s needs. The following section, “HP-UX 11i v1
Operating Environments” details the OEs currently available.
HP-UX 11i v1 Operating Environments

Operating Environments are tested and integrated application bundles
designed to work with the operating system and provide the
functionality needed for your system’s purpose. The following list details
the currently available HP-UX 11i v1 OEs:
• HP-UX 11i v1 Foundation OE (FOE) — Designed for the demands

of Web servers, content servers and front-end servers, this OE,
formerly known as the Base OE, is provided at no-charge and
includes applications such as HP-UX Web Server Suite, Java, and
Mozilla. This OE is bundled as HPUX11i-OE.
• HP-UX 11i v1 Enterprise OE (EOE) — Designed for database
application servers and logic servers, this OE is an extra-cost
package containing the HP-UX 11i v1 Foundation OE and additional
applications such as GlancePlus Pak to enable an enterprise-level
server. This OE is bundled as HPUX11i-OE-ENT.
• HP-UX 11i v1 Mission Critical OE (MCOE) — Designed for the
large, powerful back-end application servers and database servers
that access customer files and handle transaction processing, this OE
is an extra-cost package containing the Enterprise OE, plus
applications such as MC/ServiceGuard and Workload Manager to
enable a mission-critical server. This OE is bundled as
HPUX11i-OE-MC.
• HP-UX 11i v1 Minimal Technical OE (MTOE) — Designed for
workstations running HP-UX 11i v1, this OE is provided at no
charge and includes the Mozilla, Perl, VxVM, and Judy applications,
plus the OpenGL Graphics Developer’s Kit. This OE is bundled as
HPUX11i-MTOE.
76 Chapter 4
• HP-UX 11i v1 Technical Computing Operating Environment

(TCOE) — Designed for both computer-intensive workstation and
server applications, this OE includes the MTOE plus extensive
graphics applications and Math Libraries. This OE is bundled as
HPUX11i-TCOE.
Table 4-1 Supported Operating Environments for Servers & Workstations
FOE EOE MCOE MTOE TCOEa
HP Commercial Servers X X X X
HP Workstations (& Technical X X

Servers)
a. Can be purposed as either a workstation or compute-intensive technical server.
NOTE For more details about the contents of each OE, please read the Read
Before Installing or Updating to HP-UX 11i v1 booklet supplied with the
HP-UX 11i v1 CD or DVD media.
OE Application History
The current versions of applications installed with each HP-UX 11i v1
OE are listed in the Read Before Installing or Updating to HP-UX 11i v1
media booklet supplied with the HP-UX 11i v1 media. Version numbers
in bold indicate OE applications that have been added or updated since
the previous release. For a complete history of HP-UX 11i v1 OE
applications, see this web site:
http://www.software.hp.com/RELEASES-MEDIA/
Changing Individual OE Applications

HP strongly recommends that only a complete operating environment
(OE) be installed and that no products be added to or removed from the
OE. HP-UX 11i v1 OEs have been designed and tested to work as
complete solutions. Installing or removing individual products in the OE
may impact the quality of the OE.
Chapter 4 77
If you still wish to add individual OE products to an HP-UX 11i v1

system or remove a product from an installed OE, first please read this
document available on HP’s documentation Web:
http://docs.hp.com/hpux/onlinedocs/os/11i/filesets.html
Updating OE Most applications included in HP-UX 11i v1 OEs are also available as
Applications separate products on HP-UX Applications CDs or DVD supplied in the
OE media kit. Due to the product-testing process, some applications
installed with an OE may be older versions than those available on the
HP-UX Applications CDs or DVD. To identify product versions available
on Application CDs, view the CD_TABLE_OF_CONTENTS file on each
Application CD or DVD.
If you wish to install a more-recent version of an OE application from an
HP-UX Application CD or DVD, you may need a code word when
installing the newer version over the OE version. Use the code word
supplied on a separate document in the OE media kit. Applications
requiring a code word during installation are indicated by (CW) in the
tables at the back of the Read Before Installing or Updating to
HP-UX 11i v1 booklet.
HP-UX 11i v1 Software and Driver Bundle Type

Definitions
The HP-UX 11i v1 media contains all of the software and network driver
bundles for your system to run the latest version of HP-UX 11i v1.
Additional software and network driver bundles are included, which you
may choose to either select or de-select prior to install or update. HP-UX
11i v1 contains three types of bundles:
• Always-Installed: Software and network driver bundles required

by HP-UX 11i v1. Other bundles included as part of your operating
environment are also always-installed. Examples include the core OS
bundles and network drivers. For a detailed listing of
always-installed bundles see:
— “HP-UX 11i v1 Core Software Bundles” on page 79

— “HP-UX 11i v1 Always-Installed Software Bundles” on page 80
— “HP-UX 11i v1 Always-Installed Network Drivers” on page 82
78 Chapter 4
• Default-Installed: Software bundles that are installed by default.

You can manually de-select the bundles before you install or update
system. Examples include Perl and the HP Apache bundles. For a
detailed list of default-installed bundles see:
— “HP-UX 11i v1 Default-Installed Software Bundles” on page 84

• Selectable: Software bundles that are not installed or updated by
default. You must manually select these bundles before you install or
update your system. Examples include the Ignite-UX and non-core
network drivers. For a detailed list of selectable bundles see:
— “HP-UX 11i v1 Selectable Software Bundles” on page 85

— “HP-UX 11i v1 Selectable Network Drivers” on page 86
HP-UX 11i v1 Core Software Bundles

The following software bundles comprise the base software installed for
all operating environments:
Table 4-2 HP-UX 11i v1 Core Software Bundles
Bundle Name Description
HPUXBase32 or HP-UX 11i v1 Base OS installation, either 32-

HPUXBase64 or 64-bit
HPUXBaseAux a Additional OS software including SD, SCR

EMS Framework, Judy Libraries,
Update-UX, ObAM5, and Partition Manager
OnlineDiag a HP-UX 11i v1 Support Tools
HWEnable11ia Support for new hardware
BUNDLE11i Required OS Patches
FEATURE11-11 Feature Enablement Bundle - includes

required patches for the following bundles:
Base-VXVM
See “VxVM Rootability” on page 91
Base-VXVM Base VxVM (v3.5)
a. New or Updated for this release
Chapter 4 79
HP-UX 11i v1 Always-Installed Software Bundles

In addition to the core software bundles installed in Table 4-2, the
following software bundles are installed by operating environment (for
the latest version information, please see the Read Before Installing
HP-UX 11i v1 booklet):
Table 4-3 HP-UX 11i v1 Always-Installed Software Bundles (by OE)
Mission
Bundle / Description Foundation Enterprise TCOE MTOE
Critical
B8724AA X X X X
CIFS/9000 Clienta
B8725AA X X X X
CIFS/9000 Server
B5139DA X
Enterprise Cluster
Master Toolkit
B6268AA X X
Graphics and Technical
Computing Software
B3736DA a X X
HA Monitors
T1868AA a X
HP 3D Technology API
for Java 1.3
T1869AA a X
HP 3D Technology API
for Java 1.4
B8324BA a X
HP Cluster Object
Manager
80 Chapter 4
Mission
Critical
B3701AA a X X
HP GlancePlus Pak
B6061AA a X
HP MLIB Math Software

Library
B6060BA a X
HP MPI
B3935DA X
MC/ServiceGuard
B5140BA a X
MC/ServiceGuard NFS
Toolkit
B5403BA X X
MirrorDisk/UX
MySQL a X X X
MySQL open-source
database
B5118CA X X
Online JFS (v3.3)
J5849AA X X X X
PAM Kerberos (v1.10)
B3835DA X X
Process Resource
Manager
Chapter 4 81
Mission
Critical
B8339BAa X X X
Service Control Manager
TechSysConfa X X
Technical System
Configuration
B7580AA X
Visualize Conference
B8843CA a X
Workload Manager
T1302AA a X
Workload Manager
Toolkit
a. New or Updated for this release
HP-UX 11i v1 Always-Installed Network Drivers

The following drivers are always-installed on your system (all operating
environments):
Table 4-4 HP-UX 11i v1 Always-Installed Network
Drivers a
Contents / Supported IO
Driver
Description Adapters
PCI TachyonTL A5158A

A6684A
FibrChanl-00
HSC FibreChannel A6685A
A6795A
82 Chapter 4
Table 4-4 HP-UX 11i v1 Always-Installed Network

Drivers a (Continued)
Contents / Supported IO
Driver
Description Adapters
FibrChanl-01 PCI-X Fibre Channel A6826A

A9782A
A9784A
HSC GigEther A4924A

A4925A
GigEther-00 PCI GigEther A4926A

100B-SX
PCI GigEther A4929A
GigEther-01 b NextGen PCI A6847A

GigEther A6825A
A6794A
IEther-00 PCI/PCI-X IEther A7011A

A7012A
RAID-00 PCI RAID A5856A
FDDI-00 PCI FDDI A3739A

A3739B
a. Many of these drivers require HP-UX patches for sucessful

installation. HP recommends that you install the latest
HWEnable11i bundle (found on your OE media or the Support
Plus CD) along with these drivers.
b. New or Updated for this release
Chapter 4 83
HP-UX 11i v1 Default-Installed Software Bundles

The following software bundles are installed on all operating
environments by default. You can de-select any of these bundles before
you cold-install your system.
Table 4-5 HP-UX 11i v1 Default-Installed Software
Bundles
B6848BA a Ximian GNOME 1.4 GTK+ Libraries
MOZILLA a Mozilla Application Suite
MOZILLAsrc a Mozilla Source Distribution
perl a Perl 5.6.1 Programming Language
HP-UX Web Server Suite b
hpuxwsApache a HP-UX Apache-based Web Server
hpuxwsTomcat a HP-UX Tomcat-based Servlet Engine
hpuxwsWebmin HP-UX Webmin-based Admin
hpuxwsXml a HP-UX XML Web Server Tools
Java Bundles
B9098AA a Java 2 Plugin for HP-UX (v1.2)
B8111AA a Java 2 Runtime Environment (v1.2)
T1455AA a Java 2 Netscape Plugin (v1.3)
B9789AA a Java 2 Runtime Environment (v1.3)
T1458AA a Java 2 Netscape Plugin (v1.4)
T1457AA a Java 2 Runtime Environment (v1.4)
a. New or updated for this release
84 Chapter 4
b. In June 2003, HP Apache rebundled into four separate

bundles as part of the HP-UX Apache Web Server Suite, and
replaces the HP Apache bundle in previous releases.
HP-UX 11i v1 Selectable Software Bundles

The following bundles are not installed or updated by default. You must
select the desired bundles prior to installing or updating your system.
Table 4-6 HP-UX 11i v1 Selectable Software Bundles (all
OEs)
B5725AA a HP-UX Installation Utilities (Ignite-UX)

Includes the following packages:
Ignite-IA-11-22 - Ignite-UX for 11.22
Ignite-UX-10-20 - Ignite-UX for 10.20
Ignite-UX-11-00 - Ignite-UX for 11.0
Ignite-UX-11-11 - Ignite-UX for 11i v1
J5083AA HP IDS 9000 (Commercial Servers Only)
B9901AA a HP IPFilter (Commercial Servers Only)
JAVAOOB a Java Out-of-box
J4258CA Netscape Directory Server
T2351AA a Pay Per Use
SwPkgBuilder a Software Package Builder
a. New or updated for this release
Chapter 4 85
HP-UX 11i v1 Selectable Network Drivers

The following network drivers are not installed or updated by default.
You must select the desired bundles prior to installing or updating your
system.
Table 4-7 HP-UX 11i v1 Selectable Network Drivers a
Supported IO
Adapters
FDDI-01 HSC FDDI A3722A

A3723A
FDDI-02 NIO FDDI J2157B
FDDI-03 EISA FDDI A3659A

B5502BA
TermIO-00 PCI MUX J3592A

J3593A
A6748A
A6749A
TermIO-01 EISA MUX J2482A

J2483A
100BaseT-00 EISA 100BT A4308B
100BaseT-01 NIO 100BT A3495A
TokenRing-00 PCI Token Ring A5783A
TokenRing-01 NIO Token Ring J2166B
TokenRing-02 EISA Token Ring J2165B
ATM-00 PCI ATM A5483A

A5513A
A5515A
J3557A
ATM-01 HSC ATM J2468A

J2469A
J2499A
J3420B
J3573A
86 Chapter 4
Table 4-7 HP-UX 11i v1 Selectable Network Drivers a
Supported IO
Adapters
PCI HyperFabric V A4919A
HSC HyperFabric K A4920A
HyperFab-00 HSC HyperFabric A6092A

L/N A6386A
HSC HyperFabric A4921A

D/R
RAID-01 b RAID 160 A7143A
a. Many of these drivers require HP-UX patches for sucessful

installation. HP recommends that you install the latest
HWEnable11i bundle (found on your OE media or the Support
Plus CD) along with these drivers.
b. New or updated in this release
Chapter 4 87
Updating Your Ignite-UX Server
Updating Your Ignite-UX Server

The HP-UX 11i v1 OE CD1/DVD1 contains the complete Ignite-UX
product. When you cold-install HP-UX 11i v1 from the media, a subset of
Ignite-UX is used to perform the installation on a single system.
If you plan to update an existing Ignite-UX server to install HP-UX 11i
v1 on more than one system in your network, you should update your
Ignite-UX server first. Follow the instructions for “Step 2: Using
update-ux to Update to HP-UX 11i v1” on page 131 in Chapter 6.
Updating your Ignite-UX server and using it to update other systems
will ensure that you have the new make_tape_recovery command to
backup and recover your systems (see the make_tape_recovery (1M)
manpage for information). You will also be assured of keeping consistent
kernel configuration with specific drivers, daemons, and kernel tunables
on all systems.
The latest Ignite-UX software and documentation can also be
downloaded from HP via this web site:
88 Chapter 4
Diagnostics Dependencies
Diagnostics Dependencies
HP-UX 11i v1 automatically installs support tools on all systems to
provide required hardware support. These tools, contained in the
OnlineDiag bundle, give you a solution to verify, troubleshoot, and
monitor HP servers and workstations system hardware, including CPUs,
memory, interface cards, some mass storage and other devices.
CAUTION Uninstalling the OnlineDiag bundle prevents products with dependencies

on the support tools from functioning correctly. This currently includes
iCOD client software, some auxiliary support software, and some
peripherals.
Not installing the OnlineDiag bundle also removes protections against
hardware failures that the support tools provide. Without these tools,
you will find it much harder to troubleshoot and fix the problem if a
hardware failure occurs.
To ensure the reliability of your computer system, we highly recommend
installing the OnlineDiag bundle with HP-UX 11i v1 (it will be installed
by default with any HP-UX 11i v1 Operating Environment).
The tools in OnlineDiag:
• Protect you against some hardware failures (for example, some

memory problems)
• Notify you hardware events that may indicate impending failure
• Maintain logs that can give you critical help in determining the
cause of failures
• Let you troubleshoot system problems with the system online
For most computer systems, no special configuration of the OnlineDiag
support tools are necessary.
For complete information, see our diagnostics web site:
http://docs.hp.com/hpux/diag/
Chapter 4 89
Planning Your Disk Space Needs
Planning Your Disk Space Needs

This section provides hints and information to help you determine your
disk needs for HP-UX 11i v1. If you need more disk space (HP-UX 11i v1
generally requires a 4GB root volume), be sure to order the equipment
and plan on installing it after backing up your current system as
explained later in this chapter.
Planning Hints
• Record the hardware path to the CD or DVD drive.
• Develop a clear configuration plan, including:
— File system sizes

— Swap space size
— Dump device
— Disk and file-system parameters
— Mirroring information
• If installing application programs other than those supplied within
an HP-UX 11i v1 Operating Environment (OE), consider the vendor’s
size recommendations.
• When planning disk space, refer to these books:
— Managing Systems and Workgroups: A Guide for HP-UX System

Administrators or HP System Partitions Guide: Administration
for Partitions — Both manuals are available on the HP-UX 11i v1
Instant Information CD and at the Hewlett-Packard
documentation web site:
http://docs.hp.com
— Disk and File Management Tasks on HP-UX — Prentice-Hall
Hewlett-Packard Professional Books, 1997.
90 Chapter 4
VxVM Rootability
VxVM Rootability
With the September 2002 release of HP-UX 11i v1, you can choose to
manage your root volume using either HP’s Logical Volume Manager
(LVM) or VERITAS Volume Manager (VxVM) 3.5.
You can choose to configure your root volume during installation with
Ignite-UX, or you can use the conversion tools installed with VxVM 3.5 to
configure your root volume at a later time. For more information, please
read the VERITAS Volume Manager 3.5 Installation Guide for more
details.
NOTE You can not configure your root volume with VxVM during the update
process using the update-ux command. Instead, you must use the
cold-install process using Ignite-UX to enable rootability.
IMPORTANT Before you consider setting your root volume to VxVM 3.5, be sure to
read the VERITAS Volume Manager 3.5 Release Notes and the VERITAS
Volume Manager 3.5 Migration Guide for more detailed information
about VxVM and rootability
Chapter 4 91
Preparing your system for HP-UX 11i v1

Before you cold-install or update your system we recommend you read
the next section for all the recommended steps you need to take.
How to Prepare Your System

Use the following list to prepare to either install or update your system
to HP-UX 11i v1:
❏ Decide the method you want to use to move to HP-UX 11i v1. See
Chapter 2, “Choosing a Migration Path,” on page 29 for detailed
information about supported migration paths.
❏ Decide which Operating Environment to install (usually matches the
media or depot). See “HP-UX 11i v1 Operating Environments” on
page 76 and the “Operating Environments” chapter in the
HP-UX 11i v1 Release Notes for detailed information. The Read
Before Installing or Updating to HP-UX 11i v1 media booklet also
contains a table containing the applications included in each
operating environment along with their version numbers. These
documents are available at the HP technical documentation web site,
http://docs.hp.com.
❏ Decide which selectable software on the OE media that is not
automatically installed with the Operating Environment you want
(HP-UX 11i v1 Release Notes or the Read Before Installing or
Updating to HP-UX 11i v1).
❏ Verify that your system is ready for updating by reviewing the
following material:
— “Known Problems and Workarounds section in the Read Before

Installing or Updating to HP-UX 11i v1
— Appendix B, “Known Problems and Troubleshooting,” on
page 169 in this book
— Chapter 3, “Install/Update System Requirements,” on page 47 of
this book
Pay particular attention to the following:
— System backups
92 Chapter 4
— Disk space requirements. See “Disk Space and Memory

Requirements” on page 66
— Firmware revisions. See “Firmware Requirements” on page 53
❏ Back up your system. See “Back up Your System!” on page 93.
❏ If you are planning to cold-install your system, using Ignite-UX, see
“Preparing to Cold-Install Your System” on page 95
❏ If you are planning to update your system using update-ux, see
“Preparing to Update Your Existing System” on page 96.
Back up Your System!

In addition to your normal, periodic system backup procedures, you
should create a backup tape or a network backup of your root volume
group (see “Preparing your system for HP-UX 11i v1” on page 92). Do
this first before performing a cold-install or update, and again after the
cold-install or update. If a problem occurs, it’s a very simple procedure to
restore the system to its original state.
This section offers three alternatives for performing system backups:
fbackup, make_tape_recovery, and make_net_recovery.
Using fbackup Many administrators use the basic fbackup command to back up the
entire system to tape. You do not need to unmount any imported file
systems; fbackup does not cross NFS boundaries unless specified.
Using the normal tape location to do a full backup, insert a new tape and
enter:
fbackup -f/dev/rmt/0m -i -v
Later, if you wish to return the system to its previous state, use the
frecover command. See the fbackup (1M) manpage for examples.
Ignite-UX recovery For recovering a system, a better alternative to using fbackup and
commands frecover is to use the recovery commands available with Ignite-UX,
which offer more flexibility than fbackup and frecover, including the
ability to recover non-bootable systems.
The Ignite-UX server software for HP-UX 11i v1 is provided on the
HP-UX 11i v1 OE media, and can be either cold-installed along with
HP-UX 11i v1 to create a new server or specified in the update-ux
command to update an existing Ignite-UX server to HP-UX 11i v1. See
Chapter 2 for details.
Chapter 4 93
Using The Ignite-UX server’s make_tape_recovery command creates a bootable

make_tape_recovery recovery tape for an LVM or whole disk file system while it is up and
running. When a system has a logical volume layout, the recovery tape
will only include data from the root volume group, plus data from any
non-root volume group containing the /usr directory.
You can run make_tape_recovery either on the Ignite-UX server or
locally on the system from which you are trying to make a recovery tape.
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. Also, more than one volume group can be specified with
the -x option.
If a tape drive other than the default (/dev/rmt/0m) will be used, modify
the command to point to the device you want to use, for example a tape
drive at /dev/rmt/3mn:
/opt/ignite/bin/make_tape_recovery -Av -d /dev/rmt/3mn
To recover a failed system disk or volume group after a recovery tape has
been made, simply load the recovery tape, boot the system, interrupting
the boot sequence (see Appendix A) to redirect to the tape drive. Allow
the install process to complete. Do not intervene. 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 backup utilities.
For more information on using make_tape_recovery, see the
make_tape_recovery (1M) manpage on an Ignite-UX server or Chapter 11
of the Ignite-UX Administration Guide. The guide is available on the
HP-UX 11i v1 Instant Information CD and at this web site:
http://docs.hp.com/
Using The Ignite-UX server also has the make_net_recovery command to

make_net_recovery create a system recovery archive on another system on the network. The
archive created by make_net_recovery is specific to the system it was
created for and its identity includes hostname, IP_address, networking
information, and so on. In the event of a root disk failure, you use the
Ignite-UX server to restore the system by installing the recovery archive.
94 Chapter 4
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 pre-defined 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 the
make_net_recovery (1M) manpage or Chapter 11 of the Ignite-UX
Administration Guide.
Preparing to Cold-Install Your System

This section details the recommended tasks you should perform before
you cold-install your system. These tasks should be completed in
addition to the tasks listed in “Preparing your system for HP-UX 11i v1”
on page 92.
Collect Key Install Information

During the cold-install process, you will be prompted for your system’s
identity and network addresses. Record the following data on paper or on
another computer for access during the migration:
• Hostname (for example, elvis) To get your system’s hostname,

enter:
hostname
• Host IP address (for example, 15.0.68.12). To get the above
system’s IP address, enter:
nslookup elvis
• Domain Name Server (DNS) name (for example, memphis) and IP
address. For this example, enter:
nslookup memphis
• Software depot name (for example, vegas) and IP address. For this
example, enter:
nslookup vegas
Chapter 4 95
Save Configuration Files

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

The update-ux command is new to HP-UX 11i v1 and replaces
swinstall for operating system updates. It performs many of the steps
that used to be manual operations needed prior to calling swinstall, as
well as incorporating the swinstall mechanisms.
96 Chapter 4
Preparation Tasks Before you update your system, we recommend that you take the
following actions:
Record Software Versions

To identify what software still needs updating after the OS update, print
a swlist listing of all products and bundles prior to the update. For
example, enter:
/usr/sbin/swlist | lp
Then compare it with a similar swlist executed after the update.
Update maxdsiz Configurable Kernel Parameter

If you are updating from either HP-UX 10.20 or HP-UX 11.0, you will
need to increase the maxdsiz configurable kernel parameter to at least
128MB prior to rebuilding the kernel. This will ensure that the kernel
will not run out of memory during mk_kernel after the update.
Rebuild Kernel
Your update could fail if the HP-UX kernel build fails in the starting
environment. To ensure that you have a reliable starting point, rebuild
the kernel before you update:
1. As root, run the mk_kernel (1) command.

2. Fix any problems listed in the mk_kernel output.
3. Reboot your system to ensure that your new kernel boots.
Clean Out Your Log Files

To make it easier to check for problems encountered during an update,
rename the log files before starting an update:
1. cd /var/adm/sw
2. As root, rename each log file. For example:
mv swagent.log swagent_old.log
Chapter 4 97
Locate Source Media for Migration
Locate Source Media for Migration

Now that you have backed up your system and important data files, and
you have decided how to migrate to HP-UX 11i v1 (cold-install or
update), you need to locate the source media needed for the migration:
• If you are migrating one system at a time — Migrate directly

from the CDs or DVDs in the HP-UX 11i v1 media kit:
— HP-UX 11i v1 OE media (2 CDs, 1 DVD) — Boot and install a

new system or update an existing HP-UX 10.20, 11.0, or 11i
system.
— Support Plus CD — Install current HP-UX 11i v1 patch
bundles to fix defects in the OS and OE applications.
— HP-UX Application media (multiple CDs, 1 DVD) — Install
applications not installed with the OE or install a newer version
of an OE application. Some applications installed with an HP-UX
11i v1 OE may be older versions than those available on the
HP-UX Applications CDs/DVD supplied in the media kit.
Products available on Application CDs/DVD are listed in the
CD_TABLE_OF_CONTENTS file on each CD or DVD.
• If you plan to migrate many systems in your enterprise — We
recommend using an Ignite-UX server to create a “golden image”
from which to migrate. This install image can contain the HP-UX 11i
v1 OS, and OE, other applications and any needed patches. Once the
archive is in place, either on the Ignite-UX server or on another
system, migration on each client system is a single-pass operation;
you will only need to reboot each client once.
For details on installing an Ignite-UX server, see the Ignite-UX
Administration Guide, supplied on the HP-UX Instant Information
CD and on this web site:
NOTE This completes preparing the system. Please see “Next Steps” on page 99
to determine your next steps.
98 Chapter 4
Next Steps
Next Steps
After you have chosen your migration path and prepared your system for
HP-UX 11i v1, you are now ready to either cold-install or update to
HP-UX 11i v1.
• For cold-install information: see Chapter 5, “Cold Installing

HP-UX 11i v1,” on page 101
• For update information: see Chapter 6, “Updating to HP-UX 11i
v1,” on page 115
Chapter 4 99
Next Steps
100 Chapter 4
Cold Installing HP-UX 11i v1
5 Cold Installing HP-UX 11i v1
This chapter describes cold-installing from the HP-UX 11i v1 media,

including the operating system, a selected operating environment (OE)
bundle, network drivers, CDE language bundle, diagnostics, and
required patches from the Support Plus CD. The overall process is shown
in Figure 5-1 on page 104, along with alternate methods of
cold-installing 11i.
• “Before You Begin” on page 102

• “Installing HP-UX 11i v1” on page 103
• “Next Steps” on page 112
• “How to Retrieve Information After Cold-Installing” on page 112
Chapter 5 101
Before You Begin
Before You Begin

Before you cold-install HP-UX 11i v1, be sure you have done the
following:
❏ You understand all of the considerations provided in Chapter 2, and

particularly:
— “Additional Considerations (Cold-install or Update)” on page 33

— “Cold-Install Considerations” on page 39
❏ You are sure your system meets the system requirements to install
and operate HP-UX 11i v1. For more information see Chapter 3,
“Install/Update System Requirements,” on page 47
❏ You have completed the preparation tasks required to cold-install
your system. For more information see Chapter 4, “Preparing To
Move To HP-UX 11i v1,” on page 75. Pay particular attention to:
— “Preparing to Cold-Install Your System” on page 95
102 Chapter 5
Installing HP-UX 11i v1

This section describes cold-installing from the HP-UX 11i v1 media,
including the operating system, a selected operating environment (OE)
bundle, network drivers, CDE language bundle, diagnostics, and
required patches from the Support Plus CD. The overall process is shown
in Figure 5-1 on page 104, along with alternate methods of
cold-installing 11i:
Chapter 5 103
Figure 5-1 Cold-installing HP-UX 11i v1
Determine
install
approach
If Factory
Integrated
From From From
Media Depots 1 Golden
Install 11i OS/OE using Create 2 install depots: Create Install Golden
Ignite-UX Image using
• OE depot: OS/OE, QPK5
Ignite-UX Server 2
• AR depot: Applications,
Install non-OE applications QPK5
using swinstall Install image using
(see Chapter 8) Install from OE depot using Ignite-UX Server
Ignite-UX with config files
for both depots4
Install QPK patches from
Support Plus CD using
Install non-OE applications
swinstall (see Chapter 8)
from AR depot using
swinstall
(see Chapter 8)
Using tools from ITRC,
1 For help creating depots, see the Software Distributor
identify and install additional
Administration Guide
needed patches 3
2 Golden image can contain OS/OE, patches, and application
bundles. For help creating golden images, see the Ignite-UX

Install 3rd-party and Administration Guide
internal software 3 The Custom Patch Manager (CPM) can be found at the
ITRC (http://itrc.hp.com) and can be used to find additional
needed patches, such as patches for non-OE applications
and new security patches
Create
archive/recovery 4See “Using Ignite-UX with HP-UX 11i v1 OEs and Patch
image Bundles” on page 190
5
Quality Pack on Support Plus CD contains patch bundles for
the OS, OEs and applications; Select the GOLDQPK11i
Done depot, which contains both the GOLDBASE11i and
GOLDAPPS11i bundles, for both the OE depot and AR depot.
104 Chapter 5
How to Cold-Install HP-UX 11i v1
Required media Have the following media ready from the HP-UX 11i v1 media kit:
• HP-UX 11i v1 OE CDs or DVD December 2003 or later (also
includes bundles for hardware enablement and diagnostics).
• Support Plus CD, December 2003 or later (for hardware
enablement, quality pack, and diagnostics).
Typical install time Cold-installing HP-UX 11i v1 typically takes from 2-3 hours, depending
upon the system and whether you are installing only the OS or also
installing an OE.
Begin Cold Use the following steps to cold install HP-UX 11i v1 on your system:
Installation
Step 1. Insert the HP-UX 11i v1 CD1 or DVD into the drive.
Make sure any external devices connected to the target system are
turned ON and operational. Then turn the system ON or cycle power.
For more information about starting the autoboot process, see Appendix
A, “Booting HP Servers and Workstations,” on page 159.
Step 2. Stop the autoboot:

• On workstations, press and hold down the Esc key.
• On servers, press any key.
You will see the boot console menu. Boot procedures vary somewhat
between computers. For more information, see Appendix A, “Booting HP
Servers and Workstations,” on page 159. If you need help, enter:
HELP
Step 3. Ensure that Fast Boot is enabled (the full memory check run when Fast
Boot is OFF may take several hours on a large system):
1. Select the Configuration Menu: CO

2. If the Fast Boot selection is available, switch Fast Boot ON:
FB ON
Chapter 5 105
3. Return to the Main Menu: MA

(Remember to switch Fast Boot back OFF after installing 11i.)
Step 4. Search for bootable devices, using the choices displayed (for example,
enter search or sea). You’ll see a table similar to this:
Path# Device Path Device Type
----- ----------- -----------
P0 SESCSI.2.0 TOSHIBA CD-ROM
P1 LAN.1.2.3.4.5.6 1.2.3.4
P2 FWSCSI.6.0 IBM DDRS-34560WS
Of the media listed, a fast/wide SCSI device (FWSCSI) is usually a disk,

whereas a single-ended SCSI device (SESCSI) can be a disk or CD/DVD
drive. CDs usually default to a device path ending in 2.
Step 5. Boot from the CD or DVD drive using the listed path number. For the
example shown above (P0), enter: BOOT P0
Step 6. After a few minutes, you’ll be asked Interact with IPL? Press: n
The install kernel will load (takes 3-5 minutes), after which a screen
might ask you to enter the keyboard language of your console. Enter the
number and press Return/Enter and again to confirm.
Step 7. When the initial Ignite-UX screen appears, take a moment to read how
to navigate and select choices using this terminal interface:
Welcome to the HP-UX installation/recover process!
Use the <tab> key to navigate between fields, and the arrow keys
within the fields. Use the <return/enter> key to select an item.
Use the <return> or <space-bar> to pop-up a choices list. If the
menus are not clear, select the “HELP” item for more information.
Hardware Summary: System Model: 9000/812/80

+---------------------+---------------+-------------------+ [Scan Again]
| Disks: 1 ( 4.0GB) | Floppies: 1 | LAN Cards: 1 |
| CD/DVDs: 1 | Tapes: 0 | Memory: 128Mb |
| Graphics Ports: 1 | IO Buses: 3 | CPUs: 1 | [H/W Details]
+---------------------+---------------+-------------------+
[ Install HP-UX ]
[ Run a Recover Shell ]
106 Chapter 5
[ Advanced Options ]
[ Reboot ] [ Help ]
• 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.
• To navigate more quickly, enter the underlined letter of an item (such

as I for Install HP-UX).
Step 8. Select: Install HP-UX
a. From the User Interface and Media Options screen, choose:
• Source Location Options: Media-only installation
• User Interface Options: Guided Installation — provides an install

wizard with limited choices. Select if you are not familiar with
Ignite-UX.
Alternately, select Advanced Installation to see tabbed screens,
enabling you to customize your system. Use this mode to change
LVM or VxVM settings and set system parameters, network
services, file-system characteristics, and other configuration
details. Minimum file-system requirement are listed on page 66.
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.
b. If your system has a tape drive attached, the Media Installation
Selection screen appears:
Chapter 5 107
Media Installation Selection
This screen provides an option to switch the install source

from the default CD/DVD to a recovery tape. This is helpful
for those systems and for tape devices which do not support
booting from a tape.
[ * ] CD/DVD Installation
[ ] Boot from CD/DVD, Recover from Tape
[ OK ] [ Cancel ] [ Help ]
Tab to [ OK ] and hit Enter.
Step 9. Whether using Guided Installation or Advanced Installation, proceed

through each screen to configure your system:
• Configurations: Lists the OS version (initially B.11.11).
• Environments: Specify desired OE from those available on the CD or

DVD. If your system is 32/64-bit capable, select the bundle for the OS
word-width you wish to install, 32 or 64 (page 36).
• 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.
• Additional Software: Select networking drivers and other applications

for your system (see “HP-UX 11i v1 Selectable Software Bundles” on
page 85, and “HP-UX 11i v1 Selectable Network Drivers” on page
86).
IMPORTANT Do not de-select the HPUXBaseAux, HWEnable11i,

OnlineDiag, FEATURE11-11 or BUNDLE11i bundles. If in
doubt, leave the selections as default. Other software products may
108 Chapter 5
be selectable, however, we recommend that you do not de-select any

products at this time. For more about Online Diagnostics, see
“Diagnostics Dependencies” on page 89 in Chapter 4.
TIP If you’re installing an Ignite-UX server, be sure to select the entire

Ignite-UX server product, B5725AA, thus installing the new
make_tape_recovery command (see the make_tape_recovery (1M)
manpage) command on your Ignite-UX server.
• At the end of the Guided Installation session, a screen allows you to

review any messages that Ignite-UX encountered. If there are any
errors, resolve them before continuing with the installation.
NOTE Ignore any message stating that /var needs to be larger than
available to hold a dump file. /var typically only needs to be set to
50-100% as large as the current memory to handle dump files.
Step 10. When finished configuring your installation:
• 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 you selecting Finish or GO!, the system configures the hard disks
and loads a minimum set of commands and libraries. SD then downloads
all the products and patches from CD1 or DVD1.
Step 11. When prompted, replace HP-UX 11i v1 CD or DVD with the requested
CD or DVD from the media kit. Software will be automatically loaded
from each CD or DVD. If you see the message:
Unable to verify CD-ROM media content ...
Chapter 5 109
You may have pressed Enter before changing the CD or DVD. If so, verify
that you have changed the CD/DVD and then select the displayed
Recovery Action 1: Retry software Load... and press Enter again.
Step 12. The system automatically reboots after all software has been loaded.
Eject the last CD or DVD. Be sure to store all CDs or DVDs in a safe
place. You may need them later to install drivers or to install or change
the OE.
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, gateways, file systems, and so forth after
you log in. Changes to the kernel, such as adding devices, will require a
reboot to enable them.
Step 13. The depot named GOLDQPK11i includes two quality pack bundles,
GOLDBASE11i, which provides defect fixes for the Base OE (including the
always-installed and selectable driver products), and GOLDAPPS11i,
which provides defect fixes for the OE applications.
After installing or updating applications, insert the HP-UX Support Plus

CD and install the Quality Pack patch bundles to fix defects in the
operating system and OE applications in order to ensure your system is
functioning at the highest quality. For example:
/usr/sbin/swinstall -s /cdrom/GOLDQPK11i \
-x patch_match_target=true -x autoreboot=true
For more about this package, see the Quality Pack page available at the
following web site:
http://software.hp.com/SUPPORT_PLUS/qpk.html
Problems? If you encounter a problem during the cold-install process, first review
Appendix B, “Known Problems and Troubleshooting,” on page 169 for
possible solutions.
You can also find help on this web site:
http://forums.itrc.hp.com/
110 Chapter 5
NOTE This concludes the cold-install procedure. For more information about
additional tasks you will need to perform, see “Next Steps” on page 112
Chapter 5 111
Next Steps
Next Steps
• Your task is nearly complete. If you cold-installed to enable a
hardware upgrade, proceed with the hardware phase of the upgrade.
Ask your HP Customer Engineer for more information.
• To potentially improve performance, run sam as root and remove any
unneeded network drivers. The drivers listed in Table 4-4 on page 82
are installed by default. For help using sam, see its Help screens or
the Managing Systems and Workgroups: A Guide for HP-UX System
Administrators manual.
How to Retrieve Information After Cold-Installing

After completing the cold-install, you can retrieve the information you
had previously saved onto another system. Here are some tips:
Create a New Directory for Root Users

Consider creating a root home directory that is not /. This keeps the user
root dot files out of the / directory. Make sure it is on the root volume by
not locating it under the mount point of the file system. A good name to
uses /homeroot (not /home/root) as /home is often a mount point. This
is especially important if you are using LVM or VxVM and /home is a
separate volume.
Step 1. From the CDE login screen, select Options -> Command Line Login and
login as root.
Step 2. Except on trusted systems, edit /etc/passwd to change the home

directory from root to /homeroot and save it.
Step 3. Create the /homeroot directory:
mkdir /homeroot
Step 4. Move root’s personal files (files beginning with . ) to /homeroot:
ls -a | grep “^\.” | grep -v “^\.$” | grep -v “^\.\.$” | \

cpio -pdmv /homeroot
Step 5. Exit and log in again as root.
112 Chapter 5
Next Steps
Recover Files
Recover all the 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:
• For instance, if you copied it to, /backup/moe/home, enter these

commands:
cd /backup/moe/home
find . -depth | cpio -pdm /moe/home
• If you backed it up to tape with fbackup, enter:
frecover -x -i /moe/home -v
Restore Other Files

Carefully use the same techniques to restore other files and directories,
such as /usr, /local and /opt. For help in importing entire volume
groups, see either the Managing Systems and Workgroups: A Guide for
HP-UX System Administrators or the Managing Superdome Complexes.
The commands above will not write over newer files, so your new
operating system and any files you update are well protected.
Verify Your Installation

After Ignite-UX has finished installing HP-UX 11i v1 and all
applications associated with your selected Operating Environment, you
will need to verify that no errors occurred during the installation. For
more details, see “Verifying System Migration” on page 139
Chapter 5 113
Next Steps
114 Chapter 5
Updating to HP-UX 11i v1
6 Updating to HP-UX 11i v1
This chapter describes updating your system to HP-UX 11i v1 using the
update-ux command. To help you decide whether you should update or
cold-install, see Chapter 2, “Choosing a Migration Path,” on page 29.
• “Before You Begin” on page 116

• “Quickstart/Overview for the Update Process” on page 120
• “Updating Tips” on page 123
• “How to Update to HP-UX 11i v1” on page 126
Chapter 6 115
Before You Begin
Before You Begin

Before you update to HP-UX 11i v1, be sure you have done the following:
❏ You understand all of the considerations provided in Chapter 2, and
particularly:
— “Additional Considerations (Cold-install or Update)” on page 33

— “Update Considerations” on page 35
❏ You are sure your system meets the system requirements to install
and operate HP-UX 11i v1. For more information see Chapter 3,
“Install/Update System Requirements,” on page 47
❏ You have completed the preparation tasks required to update your
system. For more information see Chapter 4, “Preparing To Move To
HP-UX 11i v1,” on page 75. Pay particular attention to:
— “Preparing to Update Your Existing System” on page 96
116 Chapter 6
Problems Reading HP-UX 11i v1 DVD Media

cause your DVD device to fail while reading the DVD media contents.
This particularly affects you if you use Update-UX or other Software
Distributor (SD) tools. For example, you may encounter similar error
messages if you attempt to read DVD media with a large volume of data
from Update-UX:

not exist.


• use the pfs_mount (1M) command to mount the DVD (see “Using
pfs_mount to Mount a DVD” on page 118).
Patching Your System to Read DVD Media


Chapter 6 117


mount the DVD and update to HP-UX 11i v1, see “Using pfs_mount to
Mount a DVD” on page 118.
the following:

for HP-UX 11i v1
http://itrc.hp.com
Using pfs_mount to Mount a DVD

You can use the pfs_mount (1M) command to mount a DVD on any
supported HP-UX system updating to HP-UX 11i v1. For HP-UX 10.20,
this is the only supported method for reading DVD media with large
volumes of data.
On HP-UX 11.0 and HP-UX 11i v1 systems, you can alternately install
patches to read DVD media correctly (see “Patching Your System to Read
DVD Media” on page 117). If you have already installed the patches, you
do not need to use the pfs_mount command to mount the DVD media.
118 Chapter 6
To use the pfs_mount command:
Step 1. Start the pfs daemons:
/usr/sbin/pfs_mountd &
/usr/sbin/pfsd &
Step 2. Mount the DVD:
mkdir /dvdrom
pfs_mount /dev/dsk/c0t2d0 /dvdrom
Chapter 6 119
Quickstart/Overview for the Update Process

The following steps outline the basic steps to update your current OS to
the new 11i Operating Environments. (The OEs are described in detail in
the HP-UX 11i v1 Release Notes.)
Step 1. Select your OE
Step 2. Review the Update Process flow chart (Figure 6-1 on page 122).
Step 3. Read “Updating Tips” on page 123.
Step 4. Use swinstall to install the update-ux command from the CD, DVD or
the depot; the depot examples use
depot_server:/var/depots/my_depot. Read “Step 1: Install the
update-ux Command (Required Task!)” on page 128 for more
information.
From the CD/DVD swinstall -r -s /cdrom Update-UX \

media: \@ /var/adm/sw/update-ux.root 2> /dev/null
From a depot: swinstall -r -s depot_server:/var/depots/my_depot \

Update-UX \@ /var/adm/sw/update-ux.root 2> /dev/null
The \ at the end of the first line is not needed if you enter the complete
command on one line.
Step 5. Create fresh log files, and copy old contents to different files
(swagent.log, update-ux.log, sys.log, rc.log).
Step 6. Run the update-ux command from the CD, DVD or the Depot to update
to the new OE. Read “Update to HP-UX 11i v1 OS (OE Installed)” on
page 133 for more information.
From the CD/DVD update-ux -s /cdrom HPUX11i-OE-Ent

media:
From a depot: update-ux -s dept_server:/var/depots/my_depot \

HPUX11i-OE-Ent
120 Chapter 6
NOTE You now only use one source regardless of which OS is the starting point.
Although you may be used to specifying the target OS, this is not a
requirement anymore.
NOTE You can run update-ux in command line or interactive mode. For
interactive, use the -i option.
Chapter 6 121
Figure 6-1 Updating HP-UX 10.20 or 11.0 to 11i
Create
archive/recovery
image
update Important! depots

Determine
Install Create depots(s)
update Determine
update-ux (see page 127)
approach source
(page 128)
from media
cold-install Update to 11i OE from
depot containing
Continue to update OS/OE and Support
Cold-Install from Plus bundles using
OS/OE from 11i OE
media, depots or update-ux
media using update-ux
golden image (see page 135)
(start at page 131)
(see Cold Installing
HP-UX 11i v1)
Update non-OE Update non-OE

applications from applications using
Application media swinstall (Chapter 8)
using swinstall
(Chapter 8)
Identify and install
non-OE patches
Identify and (use
install
Install patches from Custom
non-OE Patch
patches
Support Plus media using Custom
Manager)Patch
using swinstall
(see Chapter 8)
Install 3rd-party and
internal software
Create
archive/recovery
Updating image
HP-UX 10.20/11.0 to 11i v1
DONE
122 Chapter 6
Updating Tips
Updating Tips
Before You Begin Record Software Versions
Your Update:
To identify what software still needs updating after the OS update, print
a swlist listing of all products and bundles prior to the update. For
example, enter:
/usr/sbin/swlist | lp
Then compare it with a similar swlist executed after the update.
Rebuild Kernel
Your update could fail if the HP-UX kernel build fails in the starting
environment. To ensure that you have a reliable starting point, rebuild
the kernel before you update:
1. As root, enter:
/usr/sbin/mk_kernel
2. Fix any problems listed in the mk_kernel output.
3. Reboot your system to ensure that your new kernel boots.
Clean Out Your Log Files

To make it easier to check for problems encountered during an update,
rename the log files before starting an update:
1. cd /var/adm/sw
2. As root, rename each log file. For example:
mv swagent.log swagent_old.log
During The Monitor The Update Process

Update:
If you wish to view the update process in detail, open another terminal
window (drag it aside so you can also watch for any messages on the
window running update-ux) and use the tail command to view
swinstall messages being logged:
Chapter 6 123
Updating Tips
tail -f /var/adm/sw/swagent.log
You may also wish to log all messages directed to the console by using
the script command. For example, to log all messages into a file named:
/tmp/updateOS, enter:
script -a /tmp/updateOS
To halt the script log process, enter: exit
Running Other Commands

You can run other commands during an update, such as viewing files and
tail. However, do not run other Software Distributor commands during
an update; doing so may cause the commands to function improperly.
Updating Problems?
If you encounter a problem during the update process, review Appendix
B, “Known Problems and Troubleshooting,” on page 169 for possible
solutions.
After the Update: Configuring OE Applications

After updating to an HP-UX 11i v1 operating environment (OE), some
OE products will need post-installation configuration to make them
functional. This may be indicated by a message logged in
/var/adm/sw/swagent.log. Refer to each product’s installation
instructions for details. Location of OE product documentation is listed
in the tables at the back of the Read Before Installing or Updating to
HP-UX 11i v1 booklet and in the HP-UX 11i v1 Release Notes (available
on the Instant Information CD and http://docs.hp.com).
All Software Does Not Get Updated

The update-ux command updates the HP-UX OS and any software
specified in additional software bundles available on the source media or
depot. When an OE is specified, some products in the OE will not
automatically get updated if a version of the product not previously
installed with an OE already exists on the system. You’ll have to update
or re-install those products after updating 11i. For more information
about how to update these additional software bundles, please see
“Update Selectable Software” on page 138.
124 Chapter 6
Updating Tips
Verify The Update

To verify the software versions after updating, list the products using the
swlist command. To verify that all software products are compatible
with the new OS, run swverify. These operations are explained in
Chapter 7, “Verifying System Migration,” on page 139.
Back Up Your System!

After you update, please back up your system. We recommend using the
Ignite-UX make_tape_recovery or make_net_recovery command to
create a recovery archive immediately after updating to HP-UX 11i v1.
By backing up your system, you will have a reliable system image to
return to if subsequent system changes or a system failure corrupts your
system. To use these recovery commands, you need to first install the
Ignite-UX bundle as shown later in the update examples.
Use the same process you used to back up your system before migrating
to HP-UX 11i v1. See “Back up Your System!” on page 93 in Chapter 4.
Chapter 6 125
How to Update to HP-UX 11i v1

After determining if your system meets the requirements for updating to
HP-UX 11i v1 and preparing your system, you are ready to update your
system. Updating your system using update-ux includes the following
steps:
• “Optional Step: Create a Network Depot” on page 127: If you want to

create a network depot for other systems to update to HP-UX 11i v1,
then follow this procedure.
• “Step 1: Install the update-ux Command (Required Task!)” on page
128: Shows you how to install the update-ux command on your
system.
• “Step 2: Using update-ux to Update to HP-UX 11i v1” on page 131:
Shows you how to use update-ux to update your system. Several
examples are provided to assist you with some of the most common
scenarios for using update-ux.
• “Step 3: Verify the Update” on page 138: Shows you how to verify the
update once update-ux has finished.
In Case of Trouble
The update-ux command returns an error value when it is not
successful:
1 - Error during execution; update aborted.
2 - Update aborted via user action (-n or keyboard press).
Messages are recorded in /var/adm/sw/swagent.log and
/var/adm/sw/swinstall.log.
When updating Ignite-UX, also look at its log in /var/adm/sw/.
Typical update-ux error messages and recovery actions are listed
“Common Install and Update Error and Warning Messages” on page 190
in Appendix B.
126 Chapter 6
Optional Step: Create a Network Depot

HP-UX 11i v1 is delivered on three CDs or one DVD. If you are using
CDs, you will need to swap CDs during the update process. If you want to
update without having to swap CDs, you can either use DVD media or
you can create a remote depot on an existing 11i system that contains all
the necessary software, then update from that single source.
NOTE If you are now attempting to update your system from a network depot,
start with “Step 1: Install the update-ux Command (Required Task!)” on
page 128
As root, follow this procedure to create a network depot from the HP-UX
11i v1 CDs or DVD onto a depot server or other system running HP-UX
11i v1 in your network:
Step 1. Verify that you have at least 2,055 MB of free space to create the
network depot on another system in your network. If this space is not
available, use sam to either create a new volume group or extend an
existing volume group. For help, see either SAM help or the Managing
Systems and Workgroups manual.
Step 2. Log in as root and mount the logical volume on a new directory named
/update. This directory will hold your network depot.
Step 3. Insert the HP-UX 11i v1 CD1 or DVD and wait for the drive’s busy light
to stop blinking.
Step 4. Find the CD-ROM or DVD-ROM device file name:

ioscan -f -C disk | more
/dev/dsk/c1t2d0 is a typical CD-ROM device name.
Step 5. Create the directory under root(/):

CD-ROM: mkdir /cdrom
DVD: mkdir /dvdrom
Step 6. Mount the CD or DVD onto the new directory as a file system. For
example:
CD-ROM: mount /dev/dsk/c1t2d0 /cdrom
Chapter 6 127
DVD: mount /dev/dsk/c1t2d0 /dvdrom
NOTE HP-UX 10.20 systems must use the pfs_mount (1M) command to mount
DVD media (see “Using pfs_mount to Mount a DVD” on page 118);
HP-UX 11.0 or HP-UX 11i v1 systems can either install the patches
described in “Patching Your System to Read DVD Media” on page 117, or
use the pfs_mount command.
Step 7. Merge all products on the mounted CD/DVD to the target depot, for
example /update/update-depot:
CD-ROM: swcopy -s /cdrom \* @ /update/update-depot

DVD: swcopy -s /dvdrom \* @ /update/update-depot
Step 8. Unmount the CD or DVD from its directory
CD-ROM: umount /cdrom

DVD: umount /dvdrom
If you are updating to HP-UX 11i v1 using CD-ROM, follow steps

9 - 10; DVD users, continue to “Step 1: Install the update-ux
Command (Required Task!)” on page 128
Step 9. Insert the requested HP-UX 11i v1 CD. Wait for the drive’s busy light to
stop blinking.
Step 10. Repeat Steps 6 through 8 for the requested OE CDs and the Support
Plus CD.
The network depot is now ready to update your HP-UX 10.20 or 11.0
system to HP-UX 11i v1.
Step 1: Install the update-ux Command (Required

Task!)
Unless you are already running a previous version of 11i, you must
install the update-ux command to update to 11i from CDs. Follow these
steps:
128 Chapter 6
IMPORTANT If you are updating to the December 2003 HP-UX 11i v1 release or later,
and you currently are running the June 2003 HP-UX 11i v1 release or
earlier, you will need to install the latest version of Update-UX if your
system currently has one of the following DCE Client IPv6 patches
installed on your system
• PHSS_24261
• PHSS_25473
• PHSS_25710
• PHSS_26394
• PHSS_27258
Use the following steps to install Update-UX on your system:
Step 1. Insert the HP-UX 11i v1 CD1 or DVD and wait for the drive’s busy light
to stop blinking.
Step 2. Find the CD-ROM or DVD-ROM device file name:

ioscan -f -C disk | more
/dev/dsk/c1t2d0 is a typical CD-ROM device name.
Step 3. Create the directory under root(/):

CD-ROM: mkdir /cdrom
DVD: mkdir /dvdrom
Step 4. Mount the CD or DVD onto the new directory as a file system. For
example:
CD-ROM: mount /dev/dsk/c1t2d0 /cdrom
DVD: mount /dev/dsk/c1t2d0 /dvdrom
Chapter 6 129
NOTE HP-UX 10.20 systems must use the pfs_mount (1M) command to mount
DVD media (see “Using pfs_mount to Mount a DVD” on page 118);
HP-UX 11.0 or HP-UX 11i v1 systems can either install the patches
described in “Patching Your System to Read DVD Media” on page 117, or
use the pfs_mount command.
Step 5. Using either ksh, Posix-sh or Bourne shell, install update-ux on the
target system; the depot example uses
depot_server:/var/depots/my_depot.
From the CD/DVD • CD-ROM: swinstall -r -s /cdrom Update-UX \

media: \@ /var/adm/sw/update-ux.root 2> /dev/null
• DVD: swinstall -r -s /dvdrom Update-UX \

\@ /var/adm/sw/update-ux.root 2> /dev/null
From a depot: swinstall -r -s depot_server:/var/depots/my_depot \

Update-UX \@ /var/adm/sw/update-ux.root 2> /dev/null
TIP The \ at the end of the first line is not needed if you enter the complete
command on one line.
The -r option writes log files to the specified alternate root (pseudo-root)
location, update-ux.root (Do not specify any other alternate root
location). Since the HP-UX 11i v1 Software Distributor tool contains
many keywords that 10.20 and 11.00 SD do not recognize, installing
update-ux initially at this alternate root location eliminates many
unnecessary update-ux warnings.
Immediately after update-ux is installed, a script copies update-ux to

/usr/sbin/. When update-ux runs for the first time, it will remove the
initial version at the alternate root location.
130 Chapter 6
Step 2: Using update-ux to Update to HP-UX 11i v1

After you have installed update-ux on the target system (see “Step 1:
Install the update-ux Command (Required Task!)” on page 128) and,
optionally, created an update depot containing all software to be
installed, (see “Optional Step: Create a Network Depot” on page 127),
you can now proceed to update your target system. Use the following
syntax to run update-ux:
update-ux -s source_location [-?] [-a 32|64] [-n|-y] [-i]
[-x option=value] [sw_spec]
NOTE For more information about update-ux syntax, see “update-ux Syntax”
on page 212
Chapter 6 131
update-ux Examples
Your system configuration and your planning will determine how you
use update-ux. In this section, we provide some scenarios and examples
of how you might use update-ux to update your system:
• “Update to HP-UX 11i v1 OS (OE Installed)” on page 133 shows you

how to update to HP-UX 11i v1 with an operating environment
• “Update to HP-UX 11i v1 OS (No OE Installed)” on page 134 shows
you how to update the HP-UX 11i v1 OS without an operating
environment.
• “Adding or Upgrading an OE” on page 134 shows you how to update
your system by either adding or upgrading the operating
environment on your system.
• “Downgrading an OE” on page 135 shows you how to move your
system from an advanced operating environment to a smaller
operating environment.
• “Update From a Network Depot” on page 135 shows you how to
update your system from a server on the network.
• “Update Using match_target” on page 135 shows you how to update
your system using the match_target option.
• “Update Using Interactive Software Selection” on page 136 shows you
how to use the interactive option to manually select the software you
want to update.
• “Updating to a 64-bit OS” on page 137 shows you how to move a
32-bit system to a 64-bit OS.
• “Updating Netscape Directory Server” on page 137 shows you how to
update NDS. If you are using NDS version 3.1 (HP J3667AA)
and plan to continue using NDS, you should read this
example.
• “Update Selectable Software” on page 138 shows you how to update
your system with selectable software bundles.
132 Chapter 6
We Recommend Update to HP-UX 11i v1 OS (OE Installed)

this Update:
To update to HP-UX 11i v1 and include an 11i operating environment,
you need to specify the OE bundle name in the update-ux command. The
OE bundles names are:
HPUX11i-OE HP-UX 11i v1 Foundation OE
HPUX11i-OE-Ent HP-UX 11i v1 Enterprise OE
HPUX11i-OE-MC HP-UX 11i v1 Mission Critical OE
HPUX11i-MTOE HP-UX 11i v1 Minimal Technical OE
HPUX11i-TCOE HP-UX 11i v1 Technical Computing OE
For example, to update to 11i and install the default 11i Foundation OE,
insert an HP-UX 11i v1 CD1 or DVD1 in the local drive mounted at
/cdrom or /dvdrom. As root, enter:
CD: /usr/sbin/update-ux -s /cdrom HPUX11i-OE
DVD: /usr/sbin/update-ux -s /dvdrom HPUX11i-OE
Alternately, if you wanted to update to HP-UX 11i v1 and include the
Enterprise OE, you would enter:
CD: /usr/sbin/update-ux -s /cdrom HPUX11i-OE-Ent
DVD: /usr/sbin/update-ux -s /dvdrom HPUX11i-OE-Ent
NOTE We recommend that you install all of the selectable OE bundles that you
want (such as Ignite-UX, IPFilter/9000, and the selectable network
drivers) at the same time that you do your update. See “Update
Selectable Software” on page 138 for more information
For details on what is included in each of the Operating Environments,
see Chapter 4 of the HP-UX 11i v1 Release Notes or the “HP-UX 11i v1
OE Contents” section of the Read Before Installing or Updating to
HP-UX 11i v1 media booklet. These books can be found on the HP
documentation web site: http://docs.hp.com/hpux/os/11i/
Chapter 6 133
Update to HP-UX 11i v1 OS (No OE Installed)
NOTE HP strongly recommends that you update your system with an operating
environment to provide you with the an integrated and tested set of
supporting software and applications.
If you do not specify an OE bundle update-ux will only the install the
Core components (Table 4-2, “HP-UX 11i v1 Core Software Bundles,” on
page 79). Any additional software bundles associated with an OE are not
installed.
For example, to update the HP-UX 11i v1 OS, insert HP-UX 11i v1 CD1
or DVD in the local mounted drive and enter the following command:
• CD-ROM: /usr/sbin/update-ux -s /cdrom

• DVD: /usr/sbin/update-ux -s /dvdrom
Adding or Upgrading an OE
To install an OE on an 11i system not containing an OE, or to upgrade
11i to higher-level OE (for example, HP-UX 11i v1 Foundation OE to
Enterprise OE) insert the HP-UX 11i v1 media in the CD or DVD drive
and specify the new OE using update-ux. For example, to add the default
HP-UX 11i v1 OE, enter:
• CD-ROM: /usr/sbin/update-ux -s /cdrom HPUX11i-OE

• DVD: /usr/sbin/update-ux -s /dvdrom HPUX11i-OE
If you are using CDs, update-ux will prompt you to replace the current
11i OE CD with the next OE CD to complete the update. Similarly, if you
did not initially install or upgrade a workstation with the Minimal
Technical OE or Technical Computing OE, you can add that bundle
using update-ux from the Technical Computing OE media. For example,
to install the no-cost MTOE, enter:
• CD-ROM: /usr/sbin/update-ux -s /cdrom HPUX11i-MTOE

• DVD: /usr/sbin/update-ux -s /dvdrom HPUX11i-MTOE
When the update is complete, the original OE bundle wrapper (if one
existed) will be removed and replaced with the new bundle wrapper.
134 Chapter 6
Downgrading an OE
If you wish to downgrade your system from a higher-level OE, say, from
Mission Critical OE to 11i Foundation OE, first use update-ux to install
the smaller OE from the la set of HP-UX 11i v1 media, then use
swremove to remove the unwanted OE bundle and its software. For
example, to move from the 64-bit Mission Critical OE to the 64-bit
default 11i OE:
Step 1. As root, add default HP-UX 11i v1 OE:
• CD-ROM: /usr/sbin/update-ux -s /cdrom -y HPUX11i-OE
• DVD: /usr/sbin/update-ux -s /dvdrom -y HPUX11i-OE

The -y option tells update-ux to ignore warning messages and complete
the update.
Step 2. Remove the Mission Critical software:
/usr/sbin/swremove HPUX11i-OE-MC
This command removes the IPD entries and software for the additional
(superset) software in the Mission Critical OE, leaving the default
HP-UX 11i v1 OE software intact.
Update From a Network Depot

To update from an network depot on a remote system named homer,
include the path to the depot in the update-ux command. The following
example does an update to the HP-UX 11i v1 Enterprise OE:
/usr/sbin/update-ux -s homer:/update/update_depot
HPUX11i-OE-Ent
Update Using match_target

The following command using the match_target option installs the
entire HPUX11i-OE bundle, including all OS, networking, CDE, and
diagnostic bundles described in the previous example and any software
selected by match_target. Note that software installed with
match_target may not be contained in a bundle.
• CD-ROM: /usr/sbin/update-ux -s /cdrom \

-x match_target=true HPUX11i-OE
Chapter 6 135
• DVD: /usr/sbin/update-ux -s /dvdrom -x match_target=true

HPUX11i-OE
The following command updates the same OE (HPUX11i-OE) and installs
the OS, networking, CDE, and diagnostics bundles. The difference from
the previous example is that the dot (.) following the OE bundle name
installs the OE bundle wrapper, not the entire OE. With this variation,
only those OE components that are already installed on your system get
updated. Any new OE components and products will not be installed:
Updating existing • CD-ROM: /usr/sbin/update-ux -s /cdrom -x

OE Components match_target=true HPUX11i-OE.
Only
• DVD: /usr/sbin/update-ux -s /dvdrom -x match_target=true
HPUX11i-OE.
If no argument is specified, then only the OS and its components are
updated. However, HP does not recommend using match_target to
update your system to an OE without also specifying an argument
because:
• If software arguments are not specified, match_target only installs

filesets matching those already on your system. Filesets containing
any new HP-UX 11i v1 functionality introduced will not be selected.
• Software that is installed may not include bundle wrappers, making
identification of software on the system more difficult.
Update Using Interactive Software Selection

To interactively select software for an update, use the -i option. For
example:
/usr/sbin/update-ux -s /cdrom -i
update-ux displays swinstall’s interactive user interface with software
already selected to match the default update. Now you can change
software selections. For example, you can select a non-default network
driver or a web browser before performing the update. Since update-ux
selects OS, networking, language, and diagnostic bundles by default, the
interactive user interface provides a way to de-select the default software
and use a pure match_target instead. Due to the problems explained
above, using a pure match_target is not recommended.
136 Chapter 6
CAUTION Do not combine -i and -x options in the same update-ux command.
When the -i option is specified, swinstall’s interactive user interface is

active only when swinstall is running to load software from each source
location. When installing from HP-UX 11i v1 CDs, you will have to select
non-default software for each CD. If you do set swinstall options like
match_target, be sure to re-select those options in the second
swinstall session.
For help using swinstall in interactive mode, see the swinstall (1M)
manpage or the Software Distributor Administration Guide.
Updating to a 64-bit OS
IMPORTANT Make sure that your system can support the 64-bit OS before running
this command. For more information, see “Updating to 64-bit OS” on
page 36.
If you have decided to upgrade an HP-UX 11i v1 32-bit system to a 64-bit

OS, use the following command:
• CD-ROM: /usr/sbin/update-ux -s /cdrom -a 64

• DVD: /usr/sbin/update-ux -s /dvdrom -a 64
Updating Netscape Directory Server

If you have the HP J3667AA Netscape Directory Server (NDS) version
3.1 and plan to continue using NDS with HP-UX 11i v1, you should
update to 11i as explained in “Installing or Updating Netscape Directory
Server” on page 34. Be sure to specify the new NDS bundle in the
update-ux command. For example, this command updates to the default
HP-UX 11i v1 Operating Environment and also installs the new NDS
6.02 bundle, J4258CA:
• CD-ROM: /usr/sbin/update-ux -s /cdrom HPUX11i-OE J4258CA

• DVD: /usr/sbin/update-ux -s /dvdrom HPUX11i-OE J4258CA
Chapter 6 137
For instructions on migrating your directory server database to version

6.02 after installing the new version of NDS, refer to the Netscape
document, Netscape Directory Server Administrator’s Guide, available on
the Netscape web site:
http://www.netscape.com
After migrating your directory server database to NDS 6.02, you should
remove the old version of NDS using swremove. For example:
/usr/sbin/swremove J3667AA
Update Selectable Software

To update to HP-UX 11i v1 and include additional selectable software,
such as Ignite-UX (see Table 4-6, “HP-UX 11i v1 Selectable Software
Bundles (all OEs),” on page 85 and Table 4-7, “HP-UX 11i v1 Selectable
Network Drivers,” on page 86 for a listing of other selectable bundles:
Step 1. As root, enter:
• CD-ROM: /usr/sbin/update-ux -x /cdrom B5725AA
• DVD: /usr/sbin/update-ux -x /dvdrom B5725AA

In the above command, update-ux installs the core HP-UX 11i v1 OS
bundles listed in Table 4-2, “HP-UX 11i v1 Core Software Bundles,” on
page 79, plus the Ignite-UX server bundle, B5725AA.
Step 2. Complete any post-install configuration explained in the HP-UX 11i v1

Release Notes available on the Instant Information CD and on
http://docs.hp.com/hpux/os/11i. In this example, to complete the
Ignite-UX server installation, see the Ignite-UX Administration Guide.
Step 3: Verify the Update

To verify the success of your update, review the update messages logged
in /var/adm/sw/swagent.log. For more information on how to verify
your update, see Chapter 7, “Verifying System Migration,” on page 139.
138 Chapter 6
Verifying System Migration
7 Verifying System Migration
After installing or updating to HP-UX 11i v1, backing up the new system
and adding or upgrading your applications, follow these steps to verify
that your system is back in production. If you are having problems with
updating to HP-UX 11i v1, see Appendix B.
• “How to Verify Your HP-UX Installation” on page 140

• “How to Verify Application Installation” on page 142
Chapter 7 139
How to Verify Your HP-UX Installation
Verifying HP-UX Installation

To verify that HP-UX 11i v1 was successfully installed, use Software
Distributor’s swlist and swverify commands:
Step 1. To list all products on your system, enter:
/usr/sbin/swlist -a state -l fileset
For example, running swlist on a newly installed partition on an HP

Superdome system could list these product bundles:
# Accounting
Accounting.ACCOUNTNG configured
Accounting.ACCOUNTNG2 configured
Accounting.ACCT-ENG-A-MAN configured
Accounting.ACCT-JPN-E-MAN configured
Accounting.ACCT-JPN-S-MAN configured
# ApacheStrong
ApacheStrong.APACHE-STRONG configured
ApacheStrong.TOMCAT configured
# Asian-Core
Asian-Core.ASX-JPN-E-MAN configured
Asian-Core.ASX-JPN-MAN configured
Asian-Core.ASX-JPN-S-MAN configured
Asian-Core.ASX-MAN configured
# Asian-PRINTER
Asian-PRINTER.PRNTR-COM configured
Asian-PRINTER.PRNTR-JPN-RUN configured
For a cold-install, compare your listing with the list of software products
provided with 11i, as listed in the tables in the Read Before Installing or
Updating to HP-UX 11i v1 booklet.
For an update, compare your listing with the swlist output obtained
before the update. Software products whose versions have not changed
have not been updated. Use the swverify command to determine
whether those products are compatible with HP-UX 11i v1.
140 Chapter 7
Step 2. Run swverify to verify that each bundle is intact. For example, to verify
that HP-UX 11i v1 OS is intact, enter:
/usr/sbin/swverify HPUXBase64
Or, to verify all software on your system, enter:

/usr/sbin/swverify \*
The Selection process locates all required filesets for the product. After
the list you should see:
* Selection succeeded.
Then the Analysis process verifies that each required file is loaded
(existence and version), all required dependencies are met, and runs any
available verification scripts for the product. This will take some time.
After the analysis you should see:
* Analysis succeeded.
If the analysis fails, either view /var/adm/sw/swagent.log to review

the analysis log or run the swjob... command listed at the end of the
swverify report sent to stdout.
For help with these commands, see the swlist (1M) and swverify (1M)
manpages and the Software Distributor Administration Guide.
Chapter 7 141
How to Verify Application Installation
How to Verify Application Installation

To verify that all required applications have been installed or updated,
use swlist and swverify, as explained in the previous section. For
example, to verify that the HP-UX 11i v1 default operating environment
is intact on your system, enter:
/usr/sbin/swverify HPUX11i-OE
If you get an error similar to this;
The product "xyz,l=/,r=B.xx.xx" is not compatible with this
system’s architecture or operating system.
The indicated software (xyz) has not been updated to 11i. To update the
software, mount the HP-UX 11i v1 Applications CD that contains the
software and install the new version using the swinstall command. For
more details on using swinstall, see Chapter 8.
The best way to verify each application’s operation is to exercise it. Open
each application, view a working document or project, and perform
typical production operations (edit a file, print a report, etc.). If the
application does not work as expected, refer to the application’s help or
documentation to determine the problem.
142 Chapter 7
Updating Applications
8 Updating Applications
This chapter provides you with information about how to update

applications on your system that are not installed or updated with
HP-UX 11i v1 operating environments.
• “HP-UX Patching Resources” on page 144

• “Updating Applications” on page 147
• “Adding and Removing Individual Patches” on page 148
• “Using Software Distributor Tools” on page 149
• “Updating LicensePower/iFOR” on page 150
Chapter 8 143
HP-UX Patching Resources

The cold-install and update processes now includes installing critical
patches from the HWEnable11i bundle provided with the HP-UX 11i v1
media. Immediately after your system is running 11i, your should install
any additional critical or required patches to your base OS and
applications which may have occurred since the install 11i media was
produced.
Use Custom Patch Manager

You can identify and download all needed patches for your system by
using HP’s Custom Patch Manager:
http://itrc.hp.com/wps/bin/doc.pl/sid=00f2dea61cb1fc364e
If you are already registered, log in with your user ID and password. If
not registered, following the instructions on the screen. Remember to
save your user ID and password.
Once you have downloaded needed patches, install them using the
swinstall command, as explained in “Adding and Removing Individual
Patches” on page 148.
Downloading Individual Patches

When you need to find and download a single patch, use HP’s Patch
Database. Begin at HP’s IT Resource Center web site:
http://itrc.hp.com
From the home page, select individual patches.
If you are already registered, log in with your user ID and password. You
will need to fill and submit a registration form if you do not currently
have a user ID and password.
From the patch database main page, select hp-ux and use the search tool to
find required patches and download them.
144 Chapter 8
HP Security Bulletins
HP Security Bulletins are e-mailed periodically to announce critical
patches for your system. To subscribe, go to HP’s IT Resource Center:
http://itrc.hp.com
Select: maintenance and support for hp products -> support information
digests (under the notifications heading)
HP-UX Support Plus

To keep your OS and HP-UX applications up-to-date, critical patches and
general-release patches are delivered periodically to subscribers of
HP-UX Support Plus service. You will need to install those patch bundles
when they arrive. For more information on Support Plus, go to this web
site:
http://software.hp.com/SUPPORT_PLUS
After installing the needed patch bundles from the Support Plus CD
supplied with 11i, you should maintain your system by using the patch
management tools available on HP’s IT Resource Center.
Other HP-UX Patching Resources

If you are not familiar with patching HP-UX, documents in the Patch
Management section of HP’s documentation web site may be helpful:
General guidelines for patching HP-UX are provided in the HP-UX
11.0/11i Software Transition Kit:
http://devresource.hp.com/STK/hpuxpatch.html
Also see “Managing Patches” in the Software Distributor Administration
Guide.
Installing Patches
Follow these steps to install each patch you’ve downloaded on each
system prior to updating it to HP-UX 11i v1:
Step 1. Back up your system!

Step 2. Log in as root.
Chapter 8 145
Step 3. Copy the patches to the /tmp directory.
Step 4. Change your working directory to /tmp and extract each patch using the
sh command. For example, to extract patch PHSS_23184:
cd /tmp
sh PHSS_23184
Step 5. Run swinstall to install each patch. For example:
/usr/sbin/swinstall -x autoreboot=true -x \
patch_match_target=true -s /tmp/PHSS_23184.depot
146 Chapter 8
After migrating to HP-UX 11i v1 and backing up your new system, you
should update and/or install other applications not installed with the
HP-UX 11i v1 operating environment. Here are some tips:
• To determine what products and versions are on your system, use

swlist:
/usr/sbin/swlist -l product
• You can also verify that all products are compatible with the new OS
by running swverify, as explained in Chapter 7.
• Use swinstall to install new software or update each application
not included in the HP-UX 11i v1 OS and OE bundle(s) you just
installed. For example, to install HP-UX 11i v1 on other systems
after installing 11i, insert the HP-UX 11i v1 media and enter:
/usr/sbin/swinstall -s /cdrom B5725AA
After installing selectable software, complete any post-install
configuration explained in the HP-UX 11i v1 Release Notes. To
complete the Ignite-UX server installation, see the Ignite-UX
• Note that some networking and mass-storage driver products require
HP-UX patches for successful installation. HP recommends that
install the latest HWEnable11i bundle (found on the OE media and
the Support Plus CD) before you install these drivers.
Chapter 8 147
Adding and Removing Individual Patches
Adding and Removing Individual Patches

If you migrated to HP-UX 11i v1 via the update-ux command (Chapter
6), all previous OS patches were automatically removed from the system.
If your new OS or OE requires any new patches, they can be installed
from the HP-UX Support Plus media (see “HP-UX Patching Resources”
on page 144). For a list of previous patches incorporated into 11i, see the
file:
/usr/share/doc/sw_patches.txt
New or replacement patches may be required as dependencies for
application software installed on your system. Before removing a patch
or a patch bundle, determine the dependencies required by the installed
software. This information can be found in the Release Notes for the
products and the readme files for patches. If necessary, you may have to
remove some installed software from your system.
To remove any patches from your system, first determine which patches
are installed. They may vary depending on system configuration and OS
type (32-bit or 64-bit). To display installed patches, enter:
/usr/sbin/swlist -l patch \*.\*,c=patch
To preview the removal analysis, enter:
/usr/sbin/swremove -p patch_name1 patch_name2 ...
Patch dependencies must be interpreted manually from the patch
documents.
For help on adding patches, see the Software Distributor Administration
Guide, available on the HP-UX 11i v1 Instant Information CD and on
this web site:
General guidelines for patching HP-UX are provided in the HP-UX
11.0/11i Software Transition Kit:
http://devresource.hp.com/STK/hpuxpatch.html
148 Chapter 8
Using Software Distributor Tools
Using Software Distributor Tools

The latest version of Software Distributor (SD) tools are installed when
you cold-install or use the update-ux command to update your OS. If,
after updating the OS, you find that an SD tool is missing or out-of-date,
you need to update the entire SD toolset to the latest version from
HP-UX 11i v1 media.
Updating SD is easily accomplished using the install-sd command.
See “Re-installing SD” on page 205 in Appendix B for details.
Managing Software Depots

After updating your depot-management server to HP-UX 11i v1, you can
manage HP-UX 10.20, 11.0 and 11i software on the same system. This is
the preferred depot-management solution. If your depot-management
server is running HP-UX 11.0 and has Ignite-UX version 3.5 or higher, it
can also handle 10.20, 11.0 and 11i depots. However, if your 11.0
depot-management server is running an Ignite-UX version lower than
3.5, it will not be able to handle 11i depots.
For help setting up and using a depot-management server, see Chapter 4
in the Software Distributor Administration Guide, available on the
Instant Information CD and on this web site:
Chapter 8 149
Updating LicensePower/iFOR
HP plans to remove LicensePower/iFOR from HP-UX in a future release.
To download the latest version of or patches for LicensePower/iFOR, go
to Isogon’s web site:
http://www.isogon.com/support/sptlpifor/sptlpifor.htm
How to Convert the Database

When upgrading to the LicensePower/iFOR version 4.0 license server,
any existing version 3.0.x databases must be converted to version 4.0.
This will ensure that existing licenses are made available in the new
database (for other changes, see the readme file installed with 4.0).
After installing version 4.0, perform this conversion:
Step 1. Reconfigure the license server using the i4config from version 4.0.
Step 2. Start the license server and run the i4tv verification utility to make sure
the installation was successful.
Step 3. Stop the license server.
Step 4. Make sure the /var/opt/ifor is your current directory and that
/opt/ifor/ls/bin is in your PATH.
Step 5. Enter: v3tov4
This command completes without displaying messages.
Step 6. Start the license server back up and run: i4admin Licenses from the
version 3.0.x database are now in the version 4.0 database.
IMPORTANT Do not remove transition links while you are using this product.
150 Chapter 8
Uninstalling iFOR Version 4

iFOR version 4 requires converting licenses from the previous version to
a new format. If you un-install version 4 and then reinstall version 3.0.x,
you will not be able to use the new version 4 database. You can restore
the copies of the version 3.0.x database files that were saved with the
"V3" extension in the /var/opt/ifor directory. This can be done by
renaming these files and removing the "V3" extension. Doing this,
however, will lose any licenses that were added when version 4 was
installed.
Chapter 8 151
152 Chapter 8
Next Steps
9 Next Steps
Now that you have completed installing or updating your system to

HP-UX 11i v1, you can begin to configure your system to meet your
needs.
• “System Configuration” on page 154 provides you with a list of

resources to information about more common configuration tasks you
may want to perform
• “Maintaining Your HP-UX 11i v1 System” on page 156 provides you
with an overview of how you can maintain your HP-UX 11i v1 system
Chapter 9 153
Next Steps
System Configuration
Now that you have installed or updated to HP-UX 11i v1, and installed
any additional software and patches, your next task is to configure your
system. Many of these tasks can be found in Managing Systems and
Workgroups: A Guide for HP-UX System Administrators. The following
list breaks these tasks in to several categories to assist you in finding the
information you need:
• Networking and Connectivity
— Manually setting system information: you can use the

set_parms command to configure your system’s hostname, IP
Address, DNS and other network and system data. For more
information about set_parms, see the “Making Adjustments”
topic in Chapter 3, “Configuring a System” of the Managing
Systems and Workgroups: A Guide for HP-UX System
Administrators book, or the set_parms (1M) manpage.
— Configuring Built-in PCI Networking: depending on the type
of network interface your system has, see the following
documents on http://docs.hp.com:
— Ethernet (10/100Base-TX): Using PCI 10/100Base-TX/9000

— Gigabit Ethernet: Using PCI 1000Base-T and HSC/PCI
1000Base-SX (Gigabit Ethernet)
— Configuring LAN: If you plan to manage a local area network,
see Installing and Administering LAN/9000 Software on
http://docs.hp.com.
• File System Administration
— Setting Up File Systems: Depending on how you want to manage

your physical volumes, choose one of the following:
— LVM: “Administering a System: Managing Disks and Files”
in the Managing Systems and Workgroups: A Guide for
HP-UX System Administrators on http://docs.hp.com.
— VxVM: VERITAS Volume Manager 3.5 Administrator’s
Guide on the Instant Information CD.
154 Chapter 9
Next Steps
NOTE If your system has less than 1GB of memory, and you are
using VxFS 3.5, see Appendix E, “Controlling Memory
Utilization of VxFS 3.5 on HP-UX 11i v1,” on page 223 for
details about optimizing VxFS for your system.
— Network File Systems (NFS): If you want make local directories

available to other hosts on the network, please read Installing
and Administering NFS Services on http://docs.hp.com
• Managing Users and Groups

— Adding Users and Groups: for more information, see Managing
Systems and Workgroups: A Guide for HP-UX System
Administrators on http://docs.hp.com
• Printers and Peripherals
— Printers: for more information see Managing Systems and

Workgroups: A Guide for HP-UX System Administrators on
http://docs.hp.com.
— Peripherals: for more information see Configuring HP-UX for
Peripherals
• Other Tasks
Information about other tasks for HP-UX 11i v1 can be found at
http://docs.hp.com/hpux/11i/index.html
Chapter 9 155
Next Steps
Maintaining Your HP-UX 11i v1 System

The following flowcharts offer recommended methods for maintaining
your 11i system using HP’s software support services
• HP-UX 11i v1 OE media (distributed quarterly) — Includes media

for cold-installing or updating OEs.
• HP-UX 11i v1 application releases (distributed quarterly) —
Includes media for HP-UX Applications.
• Support Plus (distributed quarterly) — Includes HP-UX OS and
OE application patches, support tools, iCOD, and other support
products.
• Custom patch bundles are available for your system from Custom
Patch Manager (CPM), a Web-based tool available on this web site:
http://itrc.hp.com
156 Chapter 9
Next Steps
Figure 9-1 Reactive Software Maintenance
Receive New 3rd Party

Encounter Problem Software
Search patch Download patches

database on (see page 144)
itrc.hp.com
Update or create new

Download patches
install depot*
(see page 144)
Update or create new Install new version of

install depot* software
Update software using

swinstall with
match_target
(see page 135)
Create
archive/recovery
image
* For help creating depots, see the Software Distributor Administration Guide.
Depots can contain applications from the HP-UX Application media,
Support Plus media, etc.
Reactive Software Maintenance
Chapter 9 157
Next Steps
Figure 9-2 Proactive Software Maintenance

Receive Application Receive Custom Patch
Receive new 11i OE
Release Bundle
Create new OE install Create new OE install Create new OE and

depot* depot* AR install depots*
Add Support Plus Find and add patches Patch software using
patch bundle(s) to to depot (use Custom swinstall with
depot Patch Manager) patch_match_target
Update OS/OE Update software using

using update_ux swinstall
(see Chapter 6)
Create
archive/recovery
image
* OE depot contains OS/OE bundles and Gold patch bundles from Support
Plus media. AR depot contains non-OE applications.
For help creating depots, see the Software Distributor Administration Guide.
Depots can contain applications from the HP-UX Application media,
Support Plus media, etc.
Proactive Software Maintenance
158 Chapter 9
Booting HP Servers and Workstations
A Booting HP Servers and

Workstations
This appendix describes booting various HP servers and workstations

using the built-in Boot ROM firmware interface. As explained here, the
built-in boot process differs between newer and older workstations and
servers.
What You Will Find in This Appendix:

• “Halting the Autoboot Process” on page 160
• “Booting Workstations” on page 161
• “Booting HP Servers” on page 163
• “Booting V-Class Systems” on page 166
• “Searching for Other Bootable Devices” on page 168
NOTE For help booting partitions in HP Superdome and S-Class servers, see
the Managing HP Superdome Complexes manual, available on the
Instant Information CD and on the Web:
NOTE If you need help during the boot process, enter: help
Appendix A 159
Halting the Autoboot Process
Halting the Autoboot Process

1. Make sure any external devices connected to the target system are
switched ON.
2. Switch ON the target computer or cycle power.
3. Insert the install media into the drive. At the Stop Autoboot
message:
• Workstations: Press and hold down Esc.

• Servers: Press and hold down Esc or any other key.
4. See the appropriate following section for your system’s boot process.
If you need help during the boot process, enter: help
160 Appendix A
Booting Workstations
Newer workstation After stopping the boot process, the system displays a menu:
boot menu
Command Description
Auto [boot|search] [on|off] Display or set auto flag
Boot [pri|alt|scsi.addr] [isl] Boot from primary, alternate or 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 mode
When you see the boot menu:
Step 1. Enter: search
Step 2. If the CD or DVD device is identified in the list shown by the search
command, proceed with the following steps. Otherwise, check the device
and cable connections and repeat the search.
Step 3. Enter: boot scsi.x
Use the SCSI address of the boot device for x.
Step 4. If you see the prompt, Interact with IPL (y or n)?, enter: n
(The bottom selections may not appear unless you hold down Esc.)
Appendix A 161
Older workstation Older HP Workstations display a menu similar to this:

boot menu
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:
To start a search for bootable devices, enter: s
Older workstation
search results
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:
You will see a list of Pn selections, as shown above.
If your boot device does not appear in the search list:
Step 1. Check the hardware.
To exit, enter: x
Step 2. To initiate another search, enter: s

Step 3. At the prompt Enter boot selection, 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 this at the Select from menu prompt:
b scsi.x
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). From this point on, respond to the requests for
information on this and successive screens.
162 Appendix A
Booting HP Servers
Booting HP Servers
As noted previously, you can halt the server autoboot process and
redirect it to boot from the desired media device. To do so, press any key
during the autoboot process to display a Main Menu:
Newer server boot

menu
----------------------- 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 for each command.
Step 1. Determine the boot device that contains the Install media. The Alternate
Boot Device is typically set to the CD/DVD drive. If this is the case,
enter: bo alt
Step 2. To search for available boot devices, type: search (or sea)
Appendix A 163
Booting HP Servers
Newer server Here is a typical output:

search results
Searching for potential boot device.
This may take several minutes.
To discontinue, press any key.
Path Number Device Path Device Type
---------------------------------------------------------------------
P0 56/52.0 (dec) Seq. record access media
P1 56/52.3 (dec) Seq. record access media
P2 56/52.4 (dec) Random access media
P3 56/52.6 (dec) Random access media
Main Menu: Enter command or menu >
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.
Booting a server 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 (dec)

34.00000002.0.0.0.0.0 (hex)
Alternate boot path = 52.0.0.0.0.0.0 (dec)

34.0.0.0.0.0.0 (hex)
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 ?>
Step 1. Switch the system ON.
Step 2. Press any key to stop the autoboot process.

Step 3. Insert the install media.
164 Appendix A
Booting HP Servers
Step 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, respond with n to Boot from primary boot path.
In this case, you will then be asked if you want to boot from the
alternate path, which is typically set to the CD or DVD device.
• 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 or DVD 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 ?>
Step 5. To the question Interact with IPL (y or n)?, enter: n
TIP To start over at this point, simply switch the system OFF and ON again.
After choosing the boot path and the install utility loads, the keyboard
languages screen appears (if your system has a PC-style keyboard).
Respond to the requests for information on this and the following
screens. Loading the install kernel takes 3 to 5 minutes.
Appendix A 165
Booting V-Class Systems

V2200 system boot To boot the system from the install media, first power-up the system and
console any external drive, as explained earlier. Portions of a typical V-Class
boot display are shown below. To stop the system boot process and select
the device with the install media, press any key within 10 seconds after
you see “System is HP9000 V2000 series”:
OBP reboot
SPP2000, POST version 3.1.4.0, compiled 1997/06/27 10:38:45 LAB #0001
Booting OBP...
System is HP9000 V2000 series

Autoboot and Autosearch flags are both OFF or we are in HP core mode.
Processor is entering manual boot mode. ...
If the system is set to auto-boot, you will see this:
Processor is starting the autoboot process.
To discontinue, press any key within 10 seconds. ...
Press any key to see the boot menu:
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 sytem 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
SCSI [INIT|RATE] [bus slot val] List/Set SCSI controller parms
SEArch [<path>] Search for boot devices
SECure [ON|OFF] Display or set secure boot mode
TIme [cn:yr:mo:dy:hr:mn[:ss]] Display or set the real-time clock
VErsion Display the firmware versions
Command:
166 Appendix A
To determine the boot path, enter:

pa
Primary boot path = 1/0:0.4.0
Alternate boot path = 15/3
Console path = 15/1
Keyboard path = 15/1
Booting from the If your boot device (CD) is mounted at the primary path, enter:
primary path
bo pri
Device : /pci@fe,90000/symbios@0,0/sd@4,0:cntl
Directory : LIF
File : HPUX
Arguments : hpux
Loading : HPUX ............ %%xxxxxx%% bytes loaded.
101456 + 61440 + 864184 start 0xd01cc0
Boot: disc(1/0/0.4.0;0)/disc(1/0/0.4.0;0):INSTALL
7245824 + 1328048 + 706428 start 0x29168
HPUX: kernel load begins
...
The install kernel then loads from the CD device.
Appendix A 167
Searching for Other Bootable Devices
Searching for Other Bootable Devices

If your CD is not mounted at the primary path, enter sea (search) at the
command prompt to see a general listing of devices. The CD will be listed
with its hardware path. For example:
Command: sea
Searching for Devices with Bootable Media.
Device Selection Device Path Device Type
-----------------------------------------------------------------
P0 5/2:0.2.0 Disk : SEAGATE ST34371W 0484
P1 5/2:0.3.0 CD-ROM : TOSHIBA CD
Command:
For this example, boot the CD with:

boot p1
The Install kernel then loads from the CD device.
NOTE The latest system firmware is required to support HP-UX Boot for the
newer IO HBA Cards.
The latest system firmware also corrects search problems with new
bootable devices.
168 Appendix A
Known Problems and Troubleshooting
B Known Problems and

Troubleshooting
This section contains critical information for you to review before you
start installing or updating to HP-UX 11i v1. Before installing or
updating to 11i, be sure to read this entire appendix as well as Read
Before Installing or Updating to HP-UX 11i v1 CD booklet for additional
late-breaking information. For information and patches on other known
problems, go to the HP IT Resource Center web site:
http://itrc.hp.com
For information about messages detected during installation or update to
11i, see the HP-UX 11i v1 Operating Environment Update & Installation
Test Procedures white paper at HP’s documentation web site:
http://docs.hp.com/hpux/os/11i

• “Known Problems Discovered in this Release” on page 170
• “Install Known Problems” on page 176
• “Update Known Problems” on page 179
• “Common Install and Update Error and Warning Messages” on
page 190
• “Problems Configuring HP-UX 11i v1” on page 196
• “Problems with Large Systems” on page 203
• “Un-installing HP-UX 11i v1” on page 204
• “Re-installing SD” on page 205
• “Recovering a Corrupt System” on page 206
• “Verifying and Adding Diagnostic Drivers” on page 207
• “Problems Affecting non-C Locales” on page 208
Appendix B 169
Known Problems Discovered in this Release

The following issues were discovered in the December 2003 release of
HP-UX 11i v1:
• “EMS checkinstall Script Fails When Updating From HP-UX 11.0 to

HP-UX 11i v1” on page 171
• “EMS May Fail on IPv4 Systems” on page 171
• “Problems Reading HP-UX 11i v1 DVD Media” on page 172
• “Ignore Warning Message When Installing PHCO_29566” on
page 174
• “xntpd Fails to Start on Reboot After Installing GOLDQPK11i Patch
Bundle” on page 174
170 Appendix B
vPars version A.02.03 Required for rp7405, rp7410 and

rp8400 Servers with PDC Firmware Version 17.005
If you received an rp7405, rp7410 or rp8400 server with PDC firmware
version 17.005 (overall firmware version 6.0), and you intend to use
Virtual Partions (vPars), you must obtain vPars version A.02.03. This
latest version of vPars addresses compatibility issues with PDC
firmware version 17.005.
rp7405, rp7410 and rp8400 servers shipped from the factory on or after
September 5, 2003 have PDC version 17.005 installed. Otherwise, to
determine if you are using this PDC firmware version, see “How to Verify
Your Firmware Version” on page 59.
PDC firmware version 17.005 is required to support the latest PCI and
PCI-X I/O cards.
If you have any questions, please contact your Customer Support
Engineer for additional details and information.
EMS checkinstall Script Fails When Updating From

HP-UX 11.0 to HP-UX 11i v1
During an update from HP-UX 11.0 to HP-UX 11i v1, you may encounter
the following warning message:
* [20255] Running "checkinstall" script for fileset
"EMS-Core.EMS-CORE".
touch: /etc/opt/resmon/monitors/ems_sys_update cannot create
How Do You Know You will encounter this warning if EMS was not installed on your HP-UX
if This Affects You 11.0 system. The /etc/opt/resmon/monitors/ems_sys_update flag file
is required to ensure that earlier versions of the EMS p_client do not
attempt to link to newer EMS libraries during an update, causing a core
dump.
What To Do You can safely disregard the warning.
EMS May Fail on IPv4 Systems

The latest release of EMS (A.04.00) has been enabled to support IPv6 on
HP-UX 11i v1. The EMS client may fail or produce a core dump if you
attempt to run on an IPv4 system.
Appendix B 171
What To Do To resolve this problem, you will need to change the following entry in
your inetd.conf file:
registrar stream tcp6 nowait root
/etc/opt/resmon/lbin/registrar
with:
registrar stream tcp nowait root

cause your DVD device to fail while reading the DVD media contents
during an update. This particularly affects you if you use Update-UX or
other Software Distributor (SD) tools. For example, you may encounter
similar error messages if you attempt to read DVD media with a large
volume of data from Update-UX:

not exist.


• use the pfs_mount (1M) command to mount the DVD
172 Appendix B
NOTE The HP-UX 11i v1 patches listed below are included in the December
2003 (and later) version of the HP-UX 11i v1 install kernel. If you are
planning to cold-install HP-UX 11i v1 (December 2003 or later), you do
not need to install these patches, nor do you need to use the pfs_mount
(1M) command to mount the DVD.



mount the DVD and update to HP-UX 11i v1
Determining If You Need to Install the Patches

the following:

for HP-UX 11i v1
Appendix B 173
http://itrc.hp.com
Ignore Warning Message When Installing PHCO_29566

The patch PHCO_29566 and dependent patches enable attention buttons
(also known as Doorbells) for PCI OLAR operations on HP-UX 11i v1
servers. When you install this patch on systems with no OLAR
capability, it issues a warning message during the patch installation. If
you see the following warning message in the swagent.log file, you can
safely ignore it.
* Installing fileset "PHCO_29566.UX-CORE,r=1.0" (79 of 102).
Creating OLA/R device node at major 5...
Note that this system must have OLA/R capable hardware
and firmware for these features to be enabled.
WARNING: OLA/R capabilities not supported on this platform

WARNING: The "postinstall" script for "PHCO_29566" had a
warning (exit code "2"). The script location was
"/var/tmp/BAAa05060/catalog/PHCO_29566/pfiles/postinstall"
PHCO_29566 is found the December 2003 HWEnable11i (B.11.11.0312.4)
bundle.
xntpd Fails to Start on Reboot After Installing

GOLDQPK11i Patch Bundle
After installing the GOLDQPK11i patch bundle, xntpd may fail to start
after the initial reboot of the system.
How Do You Know In your syslog.log file, you may encounter a similar message:
If This Affects You
Sep 23 14:46:23 <system_name> xntpd[1812]: tickadj = 625, tick
= 10000,
tvu_maxslew = 6
1875
Sep 23 14:46:23 <system_name> xntpd[1812]: precision = 6 usec
Sep 23 14:46:23 <system_name> xntpd[1812]: bind() fd 4, family
2, port 123,
addr 000000
00, in_classd=0 flags=1 fails: Address already in use
174 Appendix B
Additionally, you might find a similar message in your rc.log file:

Start time synchronization
Output from ‘/sbin/rc2.d/S660xntpd start’:
----------------------------
23 Sep 14:46:23 ntpdate[1810]: the NTP socket is in use,
exiting xntpd
What To Do To resolve this problem:
Step 1. Stop xntpd:
/sbin/init.d/xntpd stop
Step 2. Verify xntpd is down:
ps -ef | grep xntpd

Step 3. Start xntpd
/sbin/init.d/xntpd start
Appendix B 175
Install Known Problems
“Kernel size is very large” Warning During

Cold-Install
During a cold-install, the following warning message may appear in your
swagent.log:
WARNING: Kernel size is very large. The kernel may not boot or
may show decreased performance in small memory systems.
Actual kernel size: 33118076 bytes
* Build_Kernel: Complete
* Boot_From_Client_Disk: Begin
* Rebooting machine as expected.
What To Do Please disregard the above warning, the check for the kernel size limit
incorrectly uses the 32MB value instead of the 64MB value supported on
HP-UX 11i v1. PHKL_27447 will correctly set the kernel size limit that
gets checked during the creation of new HP-UX 11i v1 kernels.
System Console "kthread table full" or "fork failed"

Messages
NOTE This section was modified in the March 2003 release to reflect how the
maxusers tunable value varies depending on the type of system you
have.
After a successful cold install, the system starts displaying console

messages such as kthread table full or fork failed console. These
messages are also logged in /var/adm/syslog.log.
This is caused by the maxusers kernel tunable not set at high enough
value.
How Do You Know An example of what you might see is the following message logged onto
if This Affects You the system console:
176 Appendix B
kthread: table is full

You would also see the following message being logged in
/var/adm/syslog.log:
Jan 30 09:21:39 sd2600 vmunix: kthread: table is full
The above example demonstrates table is full messages; however, you
might see the similar “fork failed” messages.
What To Do To correct this, increase the maxusers tunable:
Step 1. Log on as root
Step 2. Edit /stand/system and add the following value (depending on your
system):
• Large 64-way systems (Superdome): maxusers 400

• 16-way systems: maxusers 200
NOTE Consult your HP Customer Engineer for information and assistance for
setting the appropriate values on your system
Step 3. Run the following commands:

mk_kernel -v -o /stand/vmunix
kmupdate
reboot -r
Kernel Build Fails on 64-bit Install

On J2240 workstations having an SCSI floppy drive, cold-installing
64-bit OS will fail during the kernel build with an “unsatisfied symbols”
error.
What To Do Edit the /stand/system file to delete the floppy driver:
Step 1. In the shell provided, use vi to edit the /stand/system file:
vi /stand/system
Step 2. Delete the line: sflop
Appendix B 177
Step 3. Press Cntl D to close the window.
The install process should now rebuild the kernel and complete
successfully. The SCSI floppy drive will be non-operational, and is not
supported on this system with 64-bit 11i OS.
Known Issues With OE Media Install Tool and

Network Depots
The Ignite-UX install tool on the OE media supports the use of network
depots. However, network depots must match the media depots for the
choices in the install tool to work properly.
The Ignite-UX documentation also explains the setup and use of network
depots without using the OE media for each installation. See the
following web site for information on the Ignite-UX product:
178 Appendix B
Update Known Problems
DMI/SCR Become Unbundled After Update

After updating to the September 2003 release (or later) of HP-UX 11i v1,
you may encounter a warning after running the swlist command
indicating that DMI/SCR (B6816AA) was unbundled during the update:
#
# Product(s) not contained in a Bundle:
#
DMI B.11.11.30 Desktop Management Interface for HP-UX

SCR B.11.11.30 System Configuration Repository
How Do You Know You will encounter this warning if DMI/SCR (B6816AA) was installed
If This Affects prior to updating.
You?
What To Do DMI/SCR will continue to work after the update. If you plan to continue
using DMI/SCR, HP recommends that you download the latest version of
DMI from http://software.hp.com. Starting with the September 2003
release, DMI will no longer be shipped as part of the operating
environments. Instead, it will be available and supported as a web-only
product.
Unsupported Upgrade of ServiceControl Manager

Causes SCR Error During Update
While updating a 10.20 system to either the Foundation, Enterprise or
Mission Critical operating environment, you may encounter the
following error messages in swagent.log appearing to affect SCR:
ERROR: [300076] Cannot delete the definition for product "SCR" from
the target "/". The product is not empty, it still contains
filesets.
These error messages are caused by an unsupported upgrade of
ServiceControl Manager 3.0 from a version of SCM earlier than version
2.5. SCM 3.0 only supports upgrades from version 2.5 or higher.
Because this is an unsupported upgrade path, no changes will be made to
either SCR or ServiceControl Manager.
Appendix B 179
How You You If you are updating a 10.20 system to either the Foundation, Enterprise,
Know If This or Mission Critical operating environment, and you have a version of
Affects You? ServiceControl Manager earlier than version 2.5, you will encounter
these errors.
What To Do To resolve this problem:
Step 1. Use the swremove (1M) command to remove the existing ServiceControl
Manager bundle from the system
Step 2. With your HP-UX 11i v1 media, use the swinstall (1M) command to
install the latest version of ServiceControl Manager (B8339BA) on your
system.
Boot Error Messages Appear After Updating from

HP-UX 11.0 (with MirrorDisk/UX Installed) to HP-UX
11i v1 TCOE
If you are updating to HP-UX 11i v1 TCOE from HP-UX 11.0 with
MirrorDisk/UX installed, the following error message may appear during
the boot process:
/sbin/bcheckrc:
Checking for LVM volume groups and Activating (if any exist)
Volume group "/dev/vg00" has been successfully changed.
vgsync: Error, "vgsync" is not a valid LVM command.
vxfs fsck: sanity check: root file system OK (mounted
read/write)
Checking hfs file systems
/sbin/fsclean: /dev/vg00/lvol1 (mounted) ok
HFS file systems are OK, not running fsck
Checking vxfs file systems
/dev/vg00/lvol8 :
vxfs fsck: sanity check: /dev/vg00/lvol8 OK
/dev/vg00/lvol3 :
vxfs fsck: sanity check: root file system OK (mounted
read/write)
/dev/vg00/lvol4 :
/dev/vg00/lvol5 :
/dev/vg00/lvol6 :
/dev/vg00/lvol7 :
180 Appendix B
Cleaning /etc/ptmp...
How Do You Know This error message may appear during reboot after the updating from
If This Affects HP-UX 11.0 with MirrorDisk/UX installed to HP-UX 11i v1 TCOE.
You?
MirrorDisk/UX for HP-UX 11i is not included with TCOE. As a result,
when the HP-UX 11.0 version of MirrorDisk/UX is removed from the
system, the commands associated with HP MirrorDisk/UX are not
properly deleted. This causes the LVM startup script to believe that HP
MirrorDisk/UX is installed on the system.
What To Do To resolve this problem you must purchase and install MirrorDisk/UX
for HP-UX 11i v1. See Chapter 8, “Updating Applications,” on page 143
for more information about installing applications after install or
updating your system.
ApacheStrong Becomes Unbundled After Update

After updating to the June 2003 release of HP-UX 11i v1, you may
encounter a warning after running the swlist command, indicating that
ApacheStrong was unbundled during the update:
#
# Product(s) not contained in a Bundle:
# ApacheStrong 1.3.26.06.09 HP Apache-based Web Server with Strong
(128bit) Encryption
How Do You Know If you previously installed ApacheStrong 1.3.x prior to updating to this
If This Affects release, you may encounter this warning.
You?
What To Do You can safely disregard this warning. The HP-UX Web Server Suite and
ApacheStrong 1.3.x will function properly.
parmgr.1m Errors on MCOE Update from HP-UX 11.0

to HP-UX 11i v1
After updating from HP-UX 11.0 to HP-UX 11i v1 MCOE, the following
mtime, stime, and permission errors may appear in your swverify.log
file:
Appendix B 181
* [140112] Checking files for fileset

"OS-Core.CORE-JPN-S-MAN,l=/,r=B.11.11".
ERROR: [40258] File "/usr/share/man/ja_JP.SJIS/man1m.Z/parmgr.1m"
should have mode "444" but the actual mode is "555".
should have mtime "974188800" but the actual mtime is
"1032497544".
should have size "3244" bytes but the actual size is "3472"
bytes.
ERROR: [140113] Fileset "OS-Core.CORE-JPN-S-MAN,l=/,r=B.11.11" had
file errors.
What To Do You can disregard these errors. The parmgr (1M) manpage will work
correctly.
HP Apache May Hang On Reboot after System Update

from Golden System Image (GSI) Depot
When upgrading from a GSI-installed system containing an OE with HP
Apache 2.0, some systems may hang while attempting to shutdown the
Apache Web Server. The problem is caused by an obsolete PID from the
httpd daemon being copied from the GSI Golden Image Depot to the
client system.
How Do You Know You may be affected if you are upgrading from a GSI HP-UX 11.0 Depot
If This Affects containing HP Apache 2.0 to HP-UX 11i v1.
You?
What To Do GSI Depot (Server):

1. Shut down your HP Apache Web Server before creating the GSI
Depot by typing
/opt/hpapache2/bin/apachectl stop
2. Verify that the following file has been deleted:
/opt/hpapache2/logs/httpd.pid
Client System:
Delete the following file (if present) after installing the GSI Depot and
before an update install:
/opt/hpapache2/logs/httpd.pid
182 Appendix B
MLIB 8.3 Produces Warning During Update

When updating from MLIB 8.1 (or earlier) to MLIB 8.3 the following
warning may appear in the /var/adm/sw/swagent.log:
WARNING: Incomplete definition for the product "MLIBPROD",
beginning at line 44452. The following attributes are not
defined:
filesets the filesets contained in the product
What To Do You can disregard this warning message; there is no problem with the
installation
X11MotifDevKit Produces Incompatible Error After

Upgrade from HP-UX 10.20
After updating from HP-UX 10.20 to HP-UX 11i v1, the following errors
may appear in your swverify.log:
ERROR: [140167] The product "X11MotifDevKit,l=/,r=B.10.20.02" is
not compatible with this system's architecture or
operating system.
* [140061] Configured X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02
---
[140155] The corequisite "X11.X11R6-SHLIBS,r=B.10.*" for

fileset "X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02" cannot be
successfully resolved.
ERROR: [140151] The dependencies for fileset

"X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02" cannot be
resolved (see previous lines).
---
* [140112] Checking files for fileset

"X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02".
WARNING: [40257] Directory "/" should have mode "555" but the
actual mode is "755".
WARNING: [40261] Directory "/" should have group,gid "other,1" but
the actual group,gid is "root,0".
Appendix B 183
WARNING: [40259] Directory "/usr/newconfig" should have owner,uid

"root,0" but the actual owner,uid is "bin,2".
WARNING: [40261] Directory "/usr/newconfig" should have group,gid

"other,1" but the actual group,gid is "bin,2".
WARNING: [140114] Fileset
"X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02"
had file warnings.
---
ERROR: [140043] Verify failed

X11MotifDevKit.X11R6-PRG,l=/,r=B.10.20.02
The problem is caused by configuration differences in the
X11MotifDevKit between HP-UX 10.20 and HP-UP 11i.
How Do You Know You may experience this problem if you are updating from HP-UX 10.20
if this Affects You? to HP-UX 11i v1, and have not updated your system with the latest
HP-UX 10.20 patch bundles.
What To Do After you have updated your system to HP-UX 11i v1, you need to
re-install the HP-UX 11i v1 Developer’s Kit located in the HP-UX 11i
v1 Application Software media kit (CD/DVD).
• For servers, install B3394BA

• For workstations, install B3392BA
For more information about installing applications, See “Updating
Applications” on page 143
OpenView SNMP Agent Produces Error with Upgrade

to HP-UX 11i v1
Due to a preinstall script error, customers upgrading to HP-UX 11i v1
may see the following error:
* [140184] Installing fileset "OVSNMPAgent.MASTER,r=B.11.11"
(54 of 1293).
* [20255] Running "postinstall" script for fileset
"OVSNMPAgent.MASTER".
* [20255] Running "preinstall" script for fileset
"OVSNMPAgent.SUBAGT-HPUNIX".
184 Appendix B
kill: 616: The specified process does not exist.

NOTE: You may need to restart SNMP agents.
The error is caused by the kill command trying to end a process that is
already terminated. When the OVSNMPAgent.MASTER fileset is installed,
it invokes a kill command to terminate any existing SNMP agents. The
next fileset, OVSNMPAgent.SUBAGT-HPUNIX, also attempts to terminate
any SNMP Agent processes.
How Do You Know If you are migrating from HP-UX 10.20 or 11.0 to HP-UX 11i v1, you may
if this Affects You receive this error message during the installation of the OpenView
SNMP bundle.
What To Do You can safely ignore this message.
“Initialize of the ITO Control Agent failed” Error

During update-ux Session
Beginning in June 2002, the ITO-SE single system event management
component was removed from the GlancePlus Pak 2000 product.
How Do You Know If you are updating from HP-UX 10.20 or 11.0 and you have a version of
If This Affects GlancePlus Pak 2000 released prior to June 2002, update-ux will try to
You? remove the ITO-SE component prior to updating to a newer GlancePlus
Pak. You may encounter the following error when update-ux removes
the file sets belonging to the ITO-SE component:
* Beginning the Unconfigure Execution Phase.
* Filesets: 3
* Files: 163
* Kbytes: 15427
* Running remove setup command /usr/lbin/sw/remove_setup.
Error opcctla (Control Agent)(14791) : Initialize of the ITO
Control Agent failed. (OpC30-1036)
Can't lookup servers: Communications failure (dce / rpc).

(OpC20-108)
Can't lookup servers: Communications failure (dce / rpc).
(OpC20-108)
Stopping all ITO Agent processes... (OpC30-1192)
/usr/bin/ps: couldn't get console device alias
/usr/bin/ps: not enough memory for hash table
Appendix B 185
What To Do No action required. The ITOAgent unconfigure script generates the error
prior to the file sets being removed.
Firmware Patches Should Not Be Included

Cold-Install or Update Session
If you are migrating from either HP-UX 10.20 or HP-UX 11.0, HP
strongly recommends you do not include firmware patches while running
a cold-install or update session.
How Do You Know The following systems are affected:

If This Affects
You? • A-Class
• L-Class
• N-Class
Many of the HP-UX 11i v1 firmware patches rely on HP-UX 11i v1 tools
and system calls. During the cold-install or update process, your system
is still running either the 10.20 or 11.0 kernel. The firmware installation
fails because of system call differences between the HP-UX 11i v1 kernel
and older kernel versions.
What To Do: HP strongly recommends that you install any firmware patches after you
have completed the cold-install or update process and your system is
running HP-UX 11i v1. Specific HP-UX 11i v1 firmware patches are
available at the following website:
http://itresourcecenter.hp.com
Analyzing Log Files

To help identify a problem with running update-ux, remember that
errors are logged in two separate log files:
• update-ux errors:
/var/adm/sw/update-ux.log and /var/adm/sw/swagent.log
• swinstall errors:
/var/adm/sw/swinstall.log and /var/adm/sw/swagent.log
SD commands log errors to /var/adm/sw/swagent.log, plus their own
log. Simply checking more than one log file may reveal the problem you
are troubleshooting.
186 Appendix B
Update Fails on J2250 Workstation With SCSI Floppy

Drive
See “Kernel Build Fails on 64-bit Install” on page 177.
Update Fails if nstrpty Kernel Parameter Set as a

Formula
If the value of the nstrpty kernel parameter is specified as a formula
(for example, nstrpty (NPTY*2)), then updating to 11i will fail with this
error:
/var/tmp/BAAa10554/catalog/Streams-TIO/STRTIO-KRN/postinstall[82]: (NPTY):
The specified number is not valid for this command.
ERROR: The “postinstall” script for “Streams-TIO.STRTIO-KRN” failed (exit code “1”).
The script location was
“/var/tmp/BAAa10554/catalog/Streams-TIO/STRTIO-KRN/postinstall”.
To prevent this, convert the value of nstrpty to a number.
How Do You Know To check the kernel parameters, run SAM and select: Kernel Configuration
If This Affects -> Configurable Parameters
You?
What To Do If the nstrpty kernel parameter is specified as a formula, then before

you update, use SAM (Kernel Configuration -> Configurable Parameters) to
change the formula to a numeric value. You do not need to rebuild the
kernel or reboot the system.
Kernel Build Failure

When updating a workstation running on a HP-UX 10.20 32-bit OS to
11i 32-bit OS/OE, the update may fail if a USB driver is configured on
the system. This will not occur when updating to 11i 64-bit OS.
If this occurs, update-ux displays this message on the console before
quitting:
Loading the kernel...
/usr/ccs/bin/ld: Unsatisfied symbols:
wsio_get_service (code)
Stop...
ERROR: The kernel build failed...
Appendix B 187
What To Do Remove the USB drivers and repeat the update:
Step 1. As root, edit /stand/system:
vi /stand/system
Step 2. Find and delete all USB drivers: usbd, hsd, hub, hid
Step 3. Save the system file and quit the editor.
Step 4. Continue the update by entering:
update-ux -kernel_build
X.25 Cards Not Supported on Some Workstations

J3525A and J3526A PCI cards are not supported under HP-UX 11i v1 on
these workstations:
• B1000
• B2000
• C3X00
• J5000
• J7000
If either of these cards is installed on a workstation listed above, the
system will crash during the upgrade. If the workstation is already
running 11i, it will crash when you try to add the card. These cards are
supported on older B-, C- and J-Class workstations, as well as on
L-[123]000, N- and A-Class servers and Superdome servers.
How Do You Know To see if these cards are installed in your system, enter:
If This Affects
ioscan -kf | egrep '(10140078)|(1133b921)'
You?
If one or both cards are installed, ioscan will output one or more rows
containing the numbers 10140078 or 1133b921.
What To Do Be sure to remove those cards before updating to 11i.
188 Appendix B
HP A3740A Fibre Channel PCI Tachyon Not

Supported
The HP A3740A Fibre Channel PCI Tachyon adapter is not supported on
HP-UX 11i v1. Before you install HP-UX 11i v1, please replace any
A3740A PCI adapters in your system with A5158A PCI 1 Gb Tachyon TL
adapters or A6795A PCI 2 Gb Tachlite adapters. Then connect any Fibre
Channel Mass Storage devices previously connected to A3740A adapters
to either of the adapters.
Appendix B 189
Common Install and Update Error and Warning Messages
Common Install and Update Error and

Warning Messages
As an install or update progresses, you will see messages relating to the
progress being entered into the log file. These messages usually refer to
normal behavior. ERROR and WARNING messages, however, have the
following significance:
ERROR Indicates a serious problem, usually requiring action
from the user in order to proceed with an installation.
WARNING Indicates something out of the ordinary and may
require action.
If you see a message or experience unusual behavior, see the following
pages for likely solutions.
This section includes some update-ux error messages and typical
recovery actions.
Using Ignite-UX with HP-UX 11i v1 OEs and Patch

Bundles
In order for Ignite-UX to properly load patch bundles, the configuration
file for the install depot needs to be modified. The sd_software_list
definition needs to be removed from the bundle definitions for all patch
bundles in the depot. It is important that all the patch bundles in the
configuration file are modified to allow for patch supersession to work
properly.
The following patch bundles are supported for installation with the
desired HP-UX 11i v1 OE from a single depot source:
BUNDLE11i
HWEnable11i
FEATURE11-11
GOLDAPPS11i
GOLDBASE11i
190 Appendix B
If you have added any custom patch bundles to your install depot, the
sd_software_list definition for those bundles should be removed also.
With the sd_software_list definition removed, SD will use
autoselect_patches to resolve which patches should be installed.
Figure B-1 Example patch bundle definition from Ignite-UX configuration

file
sw_sel "HWEnable11i" {
description = "Hardware Enablement Patches for HP-UX 11i,
March 2003"
sw_source = "core"
sw_category = "HPUXAdditions"
sd_software_list =
"HWEnable11i,r=B.11.11.0303.4,a=HP-UX_B.11.11_32/64,v=HP"
(_hp_os_bitness == "32") {
impacts = "/sbin" 2016Kb
impacts = "/var" 110304Kb
impacts = "/opt" 31784Kb
impacts = "/usr" 76480Kb
impacts = "/etc" 24Kb
}
(_hp_os_bitness == "64") {
impacts = "/sbin" 2016Kb
impacts = "/var" 115792Kb
impacts = "/opt" 31784Kb
impacts = "/usr" 81968Kb
impacts = "/etc" 24Kb
}
load_with_any ~ "HPUXBaseOS" . "*
}
The following line should be removed:
sd_software_list =
"HWEnable11i,r=B.11.11.0303.4,a=HP-UX_B.11.11_32/64,v=HP"
If you are installing patch bundles from one or more depots, separate
from the 11i OE depot, the sd_software_list needs to be removed from
the patch bundle definition and the following needs to be added to the
sw_source section at the top of the configuration file:
sd_command_line +=" -x patch_match_target=true"
Appendix B 191
Figure B-2 Example sw_source Definition from Ignite-UX Configuration File
sw_source "core" {
description = "HP-UX Core Software"
source_format = SD
sd_server = "192.1.83.191"
sd_depot_dir = "/depot/GOLDQPK11i"
sd_command_line +=" -x patch_match_target=true "
}
If you are cold installing systems with the sd_software_list defined for
patch bundles, you will see notes and warnings in the install and
swagent logs. Here is an example of the type of notes and warnings that
you will see:
NOTE: The patch fileset "PHSS_25169.WLMB-RUN,r=1.0" may only be
installed upon a previously installed base fileset. The
specification for this base fileset is
"Workload-Mgr.WLMB-RUN,fr=A.01.02,v=HP". Since there is no
fileset on the target or selected from the source which
matches this specification, fileset
"PHSS_25169.WLMB-RUN,r=1.0" will be excluded.
WARNING: The software specification

"GOLDAPPS11i,r=B.11.11.0306.2,a=HP-UX_B.11.11_32/64,v=HP"
refers to a bundle (or to a product, subproduct or fileset
within a bundle). Only some of the software specified could be
selected. The messages below show those items which could not
be selected and those items which were selected but generated
a warning:
* Could not apply the software selection
"PHCO_25887,r=1.0,a=HP-UX_B.11.11_32/64,v=HP"; it is not
available from depot or root "ant9:/".
Warning Displays
WARNING: There were errors installing from the first depot.
See the /var/adm/sw/swagent.log for details.
WARNING: Continuing could cause the OS update to fail

Do you want to continue ? (y/n)
192 Appendix B
What To do Press y to continue the update. Afterward, review

/var/adm/sw/swagent.log.
Selected Locale Not Available

Warning! One or more of your selected locales are not
available.
Please invoke the commands "locale" and "locale -a" to verify
your selections and the available locales.
Continuing processing using the "C" locale.
What To Do Ignore this message which appears when updating from 10.20 in every
locale except C. The local environment, such as Japanese, is temporarily
disabled during the update session.
Multiple OE Errors
Installing both the HP-UX 11i Operating Environment and the
Enterprise Operating Environment on the same system is not a
standard update path. If you continue with this operation,
swremove(1M) the Enterprise Operating Environment after the
update is complete.
What To Do Complete the update. Then remove the HPUX11i-OE-Ent bundle using
the swremove command.
Changing from the Enterprise Operating Environment to the
Mission Critical Operating Environment at the same time as you
change from a 32 bit OS to a 64 bit OS is not a tested
operation...
Although you can change OS word-width and move from one OE to
another at the same time, we recommend performing separate
operations. In this case:
Step 1. Update OS to new word-width:
/usr/sbin/update-ux -s /cdrom -a 64
Step 2. Install the desired OE:
/usr/sbin/update-ux -s /cdrom HPUX11i-OE-MC
For more about changing OEs, see “Adding or Upgrading an OE” on

page 134.
Appendix B 193
Disk Space Usage Error

To perform this OS update, it is required that the xxx
partition have at least yyy KB of free space and it currently
has zzz KB of free space
What To Do Reconfigure your disk per the minimum recommendations in the

message. Then run the update-ux command again. For help configuring
disk space usage, see “Adjusting Required Minimum File System Sizes”
on page 68.
swinstall Analysis Error

The analysis phase failed while installing from the first
depot. See the /var/adm/sw/swagent.log for details.
What To Do The swinstall analysis on software from HP-UX 11i v1 CD1 failed and
update-ux quit. Correct the indicated problem and run the command
again.
Post-update swverify Error

After updating your system to an HP-UX 11i v1 OE, run swverify to
ensure that all application software previously on you system is still
compatible with the new OS. If you get an error like this:
The product "xyz,l=/,r=B.xx.xx" is not compatible with this
system’s architecture or operating system.
The indicated software (xyz) has not been updated to 11i. To update the
software, mount the HP-UX 11i v1 Applications CD that contains the
software and install the new version using the swinstall command. For
more details, see Chapter 8.
Root (/) Volume Lock Error

If update-ux quits after you extended a volume size, you may see an
error containing these lines:
ERROR: The command: /var/adm/sw filter
/var/adm/sw/update-ux/swinstall...
This error will be logged in /var/adm/sw/swinstall.log:
194 Appendix B
Error: Cannot lock “/” because another command hold a

conflicting lock ...
This error indicates that other processes have locked the root volume,
preventing update-ux from completing a successful update.
What To Do Wait 10 minutes and retry the update-ux command again.
EISA 100BT Warning Message

When you remove an EISA 100BT product from a system or update a
system having EISA 100BT to any later releases of HP-UX, you may find
the following message in the /var/adm/sw/swagent.log file:
Running remove setup command /usr/lbin/sw/remove_setup.
/dev/diag/ether* not found.
This behavior is present in HP-UX 10.20 to 11i (B.11.11) versions of this
product. Presence or absence of this file on a system will not have any
impact on this product. You may safely ignore this message.
Appendix B 195
Problems Configuring HP-UX 11i v1

Read these items before installing or updating to 11i.
Kernel Build Warnings For krm Module During

Cold-Install or Update
During a cold-install or update, you may encounter a warning message in
either /var/opt/ignite/local/install.log or
/var/adm/sw/update-ux.log indicating that debug information may be
corrupted. The warning may appear as follows:
Generating module: krm...
/usr/lbin/sw/bin/mkdir -p /stand/build
Compiling /stand/build/conf.c...
Loading the kernel...
(Warning) Optimizing ADDILs in the presence of the debug

information. Debug information may be corrupted (1594)
Generating kernel symbol table...
What To Do: You may safely disregard this warning
cdrecord Application Requires Patch

The cdrecord application delivered with the XCDROAST-RUN fileset in the
TC-OpenSource product requires kernel patch PHKL_24283 or one of its
successors (including PHKL_26410 and PHKL_27225)
Enabling AutoFS on High Availability Servers Can

Cause NFS Packages to be Dropped
Restarting NFS clients (with nfs.client stop/start) or NFS servers
(with nfs.server stop/start) while NFS packages are running on the
High Available (HA) server will cause the exported file systems that tie
to NFS packages to be dropped.
This is because the SG-NFS exported file systems are handled
interactively and they are not in the /etc/exports file. When stopping
NFS clients or NFS servers, it will unexport all the file systems on the
196 Appendix B
system through the /usr/sbin/exportfs -au command. The file

systems will be re-exported if they have the entries in /etc/exports file
at the starting phase again, but not the file systems exported
interactively by the NFS packages.
How Do You Know You are affected if you enable AutoFS on an HA server.
if This Affects
You?
What To Do Enabling AutoFS on the HA NFS server needs to be done with caution.
However, this kind of configuration is fully supported if one of these two
actions is taken before stopping the AutoFS daemon:
1. Manually move all NFS packages to the adoptive server node.

2. Halt all NFS packages.
The Auto FS daemon can be stopped either with the kill -9 command,
the nfs.client script, or the nfs.server script.
Once the AutoFS daemon is restarted, the NFS packages can be
restarted or manually moved back to the server node. AutoFS can be
restarted either with the /usr/sbin/automountd command or the
nfs.client script.
Hardware Information Not Captured on Systems With

Floppy Drive
On systems with a floppy-disk drive attached, hardware information will
not be captured in the System Configuration Repository (SCR) under 11i.
After updating a system with a floppy drive from 10.20 to 11i, you will
find a core file in /usr/dmi/bin, and hpuxci (HP-UX DMI Component
Instrumentation) will not be running.
How Do You Know This problem affects you if there is a floppy drive attached to (or installed
If This Affects in) your system, and you use the System Configuration Repository (SCR)
You? to store hardware information. Since the hpuxci is not running,
hardware information will not be captured. The problem occurs if
/dev/floppy exists.
What To Do A fix for the problem will be made available in the earliest follow-up
patch release for 11i. In the meantime, if you depend on the SCR, you
should either not update to 11i, or remove the floppy drive.
Appendix B 197
NOTE If /dev/floppy exists, hpuxci sets default attributes for the device. The
code that does this does not null-terminate the string passed to atoi()
which results in a segfault (segmentation fault). The fix for this will
terminate the string correctly.
Auto-Port Aggregation Will Not Work on rp7410

Systems
The igelan driver for core rp2710 cards does not support Auto-Port
Aggregation (APA).
What To Do To fix this problem install patch PHNE_25833 (or any patch that
supersedes it).
EISA Cards Not Supported on 64-bit OS

EISA I/O drivers for TermIO, FDDI, 100BT and Token Ring cards are
supported on HP-UX 32-bit OS, but not 64-bit OS. You will not see an
error or warning message stating that these EISA products will not work
after installing or updating to 64-bit OS.
100BT HSC-FX Cards Do Not Work on HP-UX 11i v1

The100BT HSC-FX cards, J3514A#002 and J3516A#002, do not work
under 11i. The card is claimed, but the link does not come up.
This card is supported on K-Class, D-Class and A-180 systems. If you are
not sure whether or not the card is installed in your system, use the
appropriate command:
ioscan -kfClan | grep J3514A#002 (on K-Class)
ioscan -kfClan | grep J3516A#002 (on A-180 or D-Class)
If the card is installed, you will see the hardware path, interface number
and other details displayed on the screen.
To fix the problem, either install patch PHNE_22727 or replace the
HSC-FX card with an HSC-TX card, J3514A#001 (K-class) or
J3516A#001 (A-180 and D-Class). If you replace the card, you will also
198 Appendix B
need an FX-to-TX converter. The converter is not an HP product but has

been qualified for use with HP cards; it is made by Transition Networks,
part number C/E-100BTX-FX-04(SC).
SCSI PCI Restrictions for OLA/R

Online addition and replacement (OLA/R) of PCI HBAs is available in
HP-UX 11i v1 on the HP 9000 L-Class, N-Class, and Superdome
systems. This feature allows you to add or replace a failed HBA without
having to reboot the system.
Some restrictions in the ability to perform online addition (OLA) and/or
online replacement (OLR) apply with these SCSI HBAs:
• A4800A
• A5149A
• A5150A
• A5159A
• A5838A
You can find more information about SCSI HBA OLA/R restrictions by
going to the HP-IT Resource Center (ITRC), at the following URL:
http://itrc.hp.com
1. Go to the area for knowledge trees

2. Under "Hardware" select Networks
3. Select mass storage connectivity
4. Select scsi hba’s
5. Select technical support
This takes you to a page titled "scsi hba’s." (You might want to
bookmark this page, for future reference.)
6. Select the ola/r support link in the list on the left side of the page; this
takes you to the SCSI HBA OLA/R restrictions.
SCSI PCI HBA Documentation Correction

An error exists in the current manual for each of following SCSI PCI
Host Bus Adapters (HBAs): A4800A, A5149A, A5150A, and A5159A
Appendix B 199
The content for the “Setting the SCSI IDs” section of the “Installing the
Adapter” chapter is not correct. The correct content for the “Setting the
SCSI IDs” section is as follows:
You must assign the SCSI host bus adapter and each SCSI device a
separate SCSI ID (0 through 15 for a 16-bit SCSI bus). The device's
priority on the SCSI bus is determined by the device's SCSI ID. The
order of SCSI ID priorities (from highest to lowest) is 7, 6, 5, 4, 3, 2,
1, 0, 15, 14, 13, 12, 11, 10, 9, and 8. A device with SCSI ID 7 has
the highest priority, and one with SCSI ID 8 has the lowest.
When you are assigning SCSI IDs, we recommend you give the
SCSI host bus adapter higher priority than the other SCSI devices
on the bus. SCSI ID 7 is the preset SCSI ID for your HP SCSI host
bus adapter (giving it the highest priority on the SCSI bus). Set
each of the other SCSI devices on the bus to one of the remaining
SCSI ID's.
For a multi-initiator (High Availability [HA]) configuration-where
multiple SCSI host bus adapters are connected to the same SCSI
bus-the SCSI host bus adapter that carries the most traffic should
be assigned a SCSI ID of 7 (giving it the highest priority), then you
must change the SCSI ID of each of the remaining SCSI host bus
adapter's on the bus from the preset setting (7), to the next highest
priority remaining SCSI IDs (e.g. 6, 5, 4... and so on).
If you plan to boot your system from a hard disk drive on the SCSI
bus, you should assign that drive the next highest priority
unassigned SCSI ID. If there is only one SCSI host bus adapter
(SCSI ID = 7), the hard disk drive would be assigned a SCSI ID of
6. If there are multiple SCSI host bus adapters, the hard disk drive
would be assigned the next highest priority SCSI ID available after
all of the SCSI host bus adapters have been assigned higher
priority SCSI IDs.
The peripheral device SCSI IDs are usually set with jumpers or a
switch on the peripheral. Refer to the peripheral manufacturer's
instructions to determine the ID of each device and how to change
it.
You must have no duplication of SCSI IDs on a SCSI bus-the
system will hang or crash if duplicate SCSI IDs are on the bus.
See the “Checking SCSI Bus Compatibility” section of the Service
and User Guide for details on conforming and changing SCSI IDs.
200 Appendix B
The following manuals are affected:
• HP A4800A PCI FWD SCSI Host Bus Adapter Service and User
Guide (A3725-96031, E0201), page 30
• HP A5149A PCI Ultra2 SCSI Host Bus Adapter Service and User
Guide (A5149-96003, E0201), page 31
• HP A5150A PCI Dual Port Ultra2 SCSI Host Bus Adapter Service
and User Guide (A5150-96002, E0201), page 35
• HP A5159A PCI Dual Port FWD SCSI Host Bus Adapter Service and
User Guide (A5159-96002), page 31
HP-UX Apache-based Web Server Requires LD Patch

to Start and Stop
IMPORTANT Due to an ld defect, you may encounter problems starting and stopping
HP-UX Apache-based Web Server (hpuxwsApache). At the time of this
writing, HP is unable to include a patch. To fix this problem, follow the
steps below:
To verify and install the required version of ld and libdld for the
HP-UX Apache-based Web Server:
Step 1. Verify that you are using ld and libdld version B.11.32 or higher. To
determine the version, enter the following command:
ld -V
Step 2. If the version number is less than B.11.32, install Patch PHSS_26560.
See “Installing Patches” on page 145 for more information on how to
install patches.
Step 3. As root, manually start HP Apache using the following command:
/opt/hpws/apache/bin/apachectl1 start
Additional For detailed configuration and installation instructions, see the following
Documentation HP Apache documentation in the paths listed below (or at
http://machinename/hp_docs/apache/document after the web server
is started):
Appendix B 201
HP Apache Admin Guide:

/opt/hpws/hp_docs/apache/apache.admin.guide
HP Apache Release Notes:
/opt/hpws/hp_docs/apache/apache.release.notes
202 Appendix B
Problems with Large Systems
Problems with Large Systems

After a system is cold-installed, you may wish to add all the file systems
that existed under the previous installation, either manually or using
sam. However, for a large number of file systems (for example, over a
hundred), some tables in the kernel may be too small to allow correct
booting. This is because the newly-installed kernel contains default
values for kernel tables sizes, and does not allow for special
configurations made to the previous kernel.
For example, the first boot after adding the file systems may result in
error messages displayed to the console, such as:
inode: table is full
proc: table is full
file: table is full
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.
Determine the correct configuration for your system.
Appendix B 203
Un-installing HP-UX 11i v1
Un-installing HP-UX 11i v1

If you cannot resolve problems after installing or updating to HP-UX 11i
v1, you may wish to un-install 11i. The process depends upon the install
or update process you followed:
• Assuming that you have made a make_tape_recovery or

make_net_recovery tape using Ignite-UX, boot the system from that
media to return the OS and any archived applications to the previous
release. This is covered in Chapter 11 of the Ignite-UX Administra-
tion Guide, available on the HP-UX 11i v1 Instant Information CD
and on this web page:
http://docs.hp.com/
If you don’t use Ignite-UX or do not have a current
make_tape_recovery tape, read on....
• If your applications and data are on a separate disk from the OS,
cold-install the previous OS over 11i. This ensures a clean OS
installation, removing all previous upgrade and patch information.
• If applications and/or data are on the same volume with the OS, boot
from the previously-saved system recovery tape to return to a
previous OS. These "expert recovery" processes are in Chapter 11 of
the Ignite-UX Administration Guide.
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 Software Distributor Admin-
istration Guide for details.
204 Appendix B
Re-installing SD
Re-installing SD
If your system needs re-updating and/or you find that Software
Distributor (SD) needs updating, you can re-install SD.
To update SD, you must first load the install-sd utility onto your
system, then use install-sd to get the new version of SD.
Step 1. The install-sd utility is in the catalog/SW-DIST/pfiles directory on

the HP-UX 11i v1 OE CD1. If install-sd is not in /var/tmp, load it. For
example, to load install-sd from a local CD mounted at /cdrom, enter:
cp /cdrom/catalog/SW-DIST/pfiles/install-sd /var/tmp
The install-sd command uses the /var/tmp directory by default and

needs at least 2MB of free space.
Step 2. Copy the swagent.Z file from the CD-ROM:
cp /cdrom/catalog/SW-DIST/pfiles/swagent.Z /var/tmp
Step 3. Make install-sd executable:
chmod +x /var/tmp/install-sd
Step 4. Run install-sd to install the SW-DIST product onto your system:
/var/tmp/install-sd -s /sd_cdrom
For more about the install-sd command, see Appendix C of the

Software Distributor Administration Guide, available on the Instant
Information CD and on this web page:
http://docs.hp.com
Help on using install-sd is also on the Software Distributor web site:
http://www.hp.com/products/SD_AT_HP
Appendix B 205
Recovering a Corrupt System
Recovering a Corrupt System

If your system will not boot at the login prompt, or the system boots but
critical files are corrupt, adversely affecting system performance, it may
be useful to restore system elements from the HP-UX Install/Update/
Recovery media. If there are little or no user applications or data on the
system, the best recovery method is usually to cold-install the OS, as
explained in Chapter 5. This will erase all data and software on the root
disk.
If you wish try to preserve user data or applications on the root disk,
however, procedures are available to rebuild the OS. These “expert
recovery” procedures are explained in Chapter 11 of the Ignite-UX
Administration Guide. This guide is available on the HP-UX Instant
Information CD (which you can view via an HP-UX or Windows/NT
system), and also on this web page:
http://docs.hp.com/hpux/os/11i/oe/
Patch Required for fbackup (1M) and frecover (1M) on

SDLT320, SDLT220 and DLTvs80 Tape Drives
Patch PHCO_28998 is now available from the ITRC. PHCO_28998 fixes
defects with the fbackup and frecover commands to work with the
latest SDLT320, SDLT220 and DLTvs80 tape drives.
To download the patch:
Step 1. Go to the following URL:
http://www.itresourcecenter.hp.com
Step 2. Log in with your IT Resource Center user ID and password
Step 3. Under maintenance and support for hp products, select individual patches
(under the patching heading), then enter the desired patch number
NOTE You can also download a patch using anonymous ftp on the
ftp://ftp.itrc.hp.com server.
206 Appendix B
Verifying and Adding Diagnostic Drivers
Verifying and Adding Diagnostic Drivers

HP-UX 11i v1 automatically installs Support Tools on all systems to
provide required hardware support. These tools, contained in the
OnlineDiag bundle, give you a complete solution for verifying,
troubleshooting, and monitoring HP system hardware. This includes
CPUs, memory, interface cards, mass storage devices, and other devices.
To see if the diagnostic drivers are present and to use sam to install them
if they are not:
Step 1. cd /stand
Step 2. Run the what command on the kernel file from which the system is
booted, usually vmunix:
/usr/bin/what vmunix | grep diag
If the diagnostic drivers are there, the output contains diag1, and diag2
on workstations and diag0, diag1, and diag2 on servers. If not, load the
drivers as follows:
Step 3. As root, run sam:
/usr/sbin/sam
Step 4. From the sam menus, select Kernel Configuration/Subsystems, then select
the DIAGNOSTICS subsystem. Pull down the Actions menu and select Add
Subsystem to Kernel.
The third column of the matrix, Pending, should now show In for the
DIAGNOSTICS subsystem.
Step 5. Select Actions -> Process New Kernel. Confirm that you want to reboot the
system when prompted.
Help with using Support Tool Manager and the other diagnostics is in
the Support Plus: Diagnostics User’s Guide, available on the Support
Plus CD in:
/cdrom/DIAGNOSTICS/DIAG_USR.PDF
Appendix B 207
Problems Affecting non-C Locales
Problems Affecting non-C Locales
Difference between English and Japanese HP-UX STK

The English and Japanese versions of the STK bundled with HP-UX 11i
v1 may contain differing documentation (the STK tools are identical for
both languages). To verify that you have the latest Japanese
documentation set, view these web sites:
http://devresource.hp.com/STK_ja_JP.SJIS
http://devresource.hp.com/STK_ja_JP.eucJP
Warning when updating to non-C locales

See “Selected Locale Not Available” on page 193.
208 Appendix B
Using the update-ux Tool
C Using the update-ux Tool
This appendix describes the update-ux tool.

Beginning with the 11i release, the update-ux command replaces
swgettools to perform these OS update tasks:
• Update the HP-UX OS from 10.20 or 11.0 to 11i, including adding a

new operating environment (OE)
• Update an existing 11i system to a later release
• Change the OS word-width from 32-bit to 64-bit on appropriate
systems
• Change from one OE to another
For more information on using update-ux, see the update-ux (1M)
manpage.
Appendix C 209
Overview
Overview
The update-ux command updates your system in this order:
1. Performs preparation steps including checking the root volume (see
“About update-ux” on page 211).
2. Calls swinstall to install software bundles from CD1. swinstall
does its Selection and Analysis processes on the software loaded from
the CD, then replaces the existing OS with 11i OS bundles and
default network drivers.
3. Prompts you after about an hour to replace CD1 with CD2 then calls
swinstall again to load any remaining software that you specified
in the update-ux command.
4. Reboots the system after all software has been loaded. These OS and
network driver bundles are loaded by default:
HPUXBase32 or HPUXBase64
HPUXBaseAux
HWEnable11i
BUNDLE11i
FEATURE11-11
FibrChanl-00 (64-bit OS only)
GigEther-00
GigEther-01
RAID-00 (64-bit OS only)
FDDI-00 (32-bit OS only)
(other networked drivers if needed)
OnlineDiag
perl
BaseVXVM
CDE-English (or appropriate language bundles)
210 Appendix C
About update-ux
About update-ux
The update-ux command improves the usability and robustness of the
update process by eliminating many of the manual steps required by
swgettools in previous HP-UX updates. In addition to ensuring a safe
environment on the target system for the OS update, update-ux
performs these update preparation steps before initiating the update:
• Before updating from HP-UX 10.20, update-ux performs these

operations for you:
— Verifies that FibreChannel Storage is not on the system. If

present, it must be manually removed.
— Ensures that you are not updating a diskless server. You’ll have
to cold-install 11i on a diskless server, making it a stand-alone
system.
— Checks for minimal disk space in /, /stand, /opt, /usr and
/var on a system using LVM.
— Removes the no-longer-needed SW-DIST.RUPDATE fileset.
— Removes any 10.x patch information and 10.20 OS bundle
wrappers.
— Upgrades to JFS version 3 if needed.
• Before updating from HP-UX 11.0 or an earlier version of 11i,
update-ux performs these operations:
— Checks for minimal disk space in /, /stand, /opt, /usr, and

/var on a system using LVM.
— Removes HP-UX 11.0 OS bundle wrappers.
— Removes MirrorDisk/UX bundles prior to update.
If any requirements are not met, update-ux will display an appropriate
message and exit.
update-ux installs a new version of HP-UX Software Distributor (SD),
plus any patches to it, from the source depot before initiating an OS
update.
Appendix C 211
update-ux Syntax
update-ux Syntax
update-ux -s source_location [-?] [-a 32|64] [-n|-y] [-i]
[-x option=value] [sw_spec]
where:
-s source_location Specifies the source containing the new software
depot. Possible locations are a local directory, a
mounted CD containing a depot, or a remote
system-and-depot combination. All paths used in the
source_location must be absolute paths. If
source_location is a remote system/depot
combination, the remote system should be specified
first, followed by the absolute path to the remote depot,
separated by a colon with no spaces; for example:
swperf:/var/spool/sw
-? Prints the usage statement.
-a 32|64 Specifies the OS architecture (word width), 32 bit or 64
bit. Omitting this defaults to the system’s currently set
OS word-width. update-ux will not install an
unsupported word-width (only 64-bit OS is supported
on B-, C- and J-class systems). Changing an existing
system from 64-bit OS to 32-bit OS is not supported.
-n | -y update-ux issues a message and waits for your
response to continue whenever something unexpected
is attempted. Specify -n at first (or omit this option) to
have update-ux “not continue” when an error is issued.
When you have reviewed/resolved all errors, use -y
instead of -n to have update-ux ignore all messages
which would otherwise cause update-ux to wait for a
user response.
-i Specifies the swinstall interactive user interface to
select software products from a depot or bundle during
the update. For more information, see the swinstall
(1M) manpage.
-x option=value Specifies swinstall options to be applied during the
update. For a typical update, no swinstall options are
required. swinstall -p (preview) is not supported.
212 Appendix C
update-ux Syntax
For information on swinstall options, see the swinstall

(1m) manpage or the Software Distributor
sw_spec Specifies one or more optional software bundles to be
updated, such as an operating environment (OE)
bundle name, a network-driver bundle or Ignite-UX. If
an OE bundle name is not included on the command
line, only the core OS will be updated.
For more about update-ux, see the update-ux (1M) manpage.
Appendix C 213
update-ux Syntax
214 Appendix C
Configuring Built-In PCI Networking
1000Base-T (Gigabit Ethernet)
D Configuring Built-In PCI

Networking
This appendix describes configuring built-in (or core) PCI networking

cards in HP workstations and servers.

These instructions apply to the 1000Base-T (Gigabit Ethernet) product.
They assume that the card has been factory installed and the software
already loaded on your disk.
Step 1. Log in as root and verify that the card and its hardware path are
displayed by executing the command: ioscan.
Step 2. Run the System Administration Manager: sam.
Step 3. Double click Networking and Communications.
Step 4. Double click Network Interface Cards.
Step 5. Highlight the Gigabit Ethernet card and choose Configure from the
Actions menu.
Step 6. Fill in the form according to the instructions.
Step 7. Click on the OK button to activate the card and then select exit from the
“File” menu until you exit SAM.
Appendix D 215
Optional Step: Configure Jumbo Frame Size (Jumbo

Frames only supported at 1000 Mbit/s)
Jumbo frames have an mtu_size of 9000 bytes. If using Jumbo Ethernet
frames, ensure that all end stations on a given LAN (that is, no routers
or layer 3 switches in between) have the same MTU setting. However
switch ports in the LAN can have any MTU setting greater than or equal
to the end station MTU.
1. Obtain the PPA number of the card by executing: lanscan

2. Choose one of two configuration methods that will permanently save
your configuration. You can either:
• use the GUI-based system admin manager (SAM).

To use SAM, type sam at the HP-UX system prompt; then
double-click Networking and Communications, and then
Advanced Configuration--see the Ethernet Support Guide for
details, and then do the steps for verifying the MTU size;
or
• edit the configuration file in /etc/rc.config.d/using an editor
such as “vi.” Depending on your driver, the filename can be
either hpgelanconf, hpigelanconf, or hpietherconf.
Set the mtusize by editing either
HP_GELAN_MTU[0]=mtusize,
HP_IGELAN_MTU[0]=mtusize, or
HP_IETHER_MTU[0]=mtusize, and insert the proper interface
name: HP_GELAN_INTERFACE_NAME,
HP_IGELAN_INTERFACE_NAME, or
HP_IETHER_INTERFACE_NAME. When the system reboots,
the interface will be configured for jumbo frame operation.
3. Verify MTU change by executing: netstat -rn. If MTU has not
changed, execute the following commands:
ifconfig lan PPA_number unplumb
ifconfig lan PPA_number ip_address netmask netmask up
4. To check (or verify) the current Ethernet frame size, execute:
lanadmin -m PPA_number
Alternative way to temporarily configure jumbo frame size: Execute:
lanadmin -M mtu_size PPA_number.
The PPA number is the one we obtained from the output of lanscan.
216 Appendix D
For jumbo frames set the mtu_size to 9000 (bytes). Note: using lanadmin
will not preserve your settings across reboots.
Appendix D 217
Optional: Troubleshooting a Fast Ethernet Migration to HP-UX 11i
Optional: Troubleshooting a Fast Ethernet

Migration to HP-UX 11i
The following information is applicable only if your Fast Ethernet update

to HP-UX 11i fails.
In HP-UX 11i, the drivers for PCI and HSC-based Fast Ethernet
networking are consolidated into one driver called btlan, which is
pre-installed as part of the kernel. The configuration files used by these
networking drivers in HP-UX 10.20 and 11.0—hpbtlanconf (btlan),
hpbase100conf (btlan3), hpgsc100conf (btlan4), hppci100conf
(btlan5), and hpsppci100conf (btlan6), which are in the
/etc/rc.config.d directory, are merged into one file.
IMPORTANT The configuration files used by the PCI and HSC-based Fast Ethernet
networking drivers are automatically updated as part of the process of
migrating to HP-UX 11i.
If the update process fails, the PCI and HSC pre-update configuration
files have to be merged manually as explained further in the following
paragraphs.
How the Automatic Merge Works Using the

BTLAN.100 Script
During an update, a configuration script called BTLAN.100,

automatically merges HSC and PCI pre-11i Fast Ethernet configuration
files into one file called hpbtlanconf.
Once the BTLAN.100 script creates the merged configuration file, it is
placed temporarily in the /var/adm/sw/save_custom/UNIFIED_MER
directory, and the original configuration files are saved with the
extension .obsolete. During the consolidated btlan driver installation,
the merged configuration file is then moved to the /etc/rc.config.d
directory as hpbtlanconf.
218 Appendix D
Note that the BTLAN.100 script will only merge the driver-specific
configuration files if the corresponding hardware is present on the
system, and if the files have at least one LAN interface configured. (For
example, if the system had the HSC-based Fast Ethernet networking
driver [btlan4] and corresponding hardware [HSC cards], then the
hpgsc100conf configuration file should have at least one card configured
in it.)
Optional: Manual Merging

If the update process is abandoned because of preupdate script failures
(other than syntax errors in configuration files or a duplicate LAN
interface error), then the configuration files have to be merged manually.
Once this has been done, you can then continue the update process.
(Once the update process is restarted, answer NO (N) at the prompt, Do
you want to proceed in merging the configuration files into
one? [Y|N].)
Manual Merging Procedure
1. Find out which of the five configuration files listed below exists in
the /etc/rc.config.d directory.
• hpbtlanconf (btlan)
• hpbase100conf (btlan3)
• hpgsc100conf (btlan4)
• hppci100conf (btlan5)
• hpsppci100conf (btlan6)
2. For each of the files found in Step 1, use the command ioscan -kfC
lan to find out if corresponding hardware is present.
Driver Name: File Name
a. btlan -- hpbtlanconf
b. btlan3 -- hpbase100conf
c. btlan4 -- hpgsc100conf
d. btlan5 -- hppci100conf
e. btlan6 -- hpsppci100conf
Appendix D 219
If hardware is present, check to see if any LAN interface is

configured. For example, the configuration for hpbtlanconf (btlan)
would show as follows:
HP_BTLAN_INTERFACE_NAME[0]=lan1
HP_BTLAN_STATION_ADDRESS[0]=0x080009C4686E
HP_BTLAN_SPEED[0]=100HD
3. Create the file hpbtlanconf.merge in the directory
/etc/rc.config.d as shown below:
#####################################################################
(#) hpbtlanconf
# hpbtlanconf: contains config values for HP PCI/HSC 100Base-T interfaces
#
# HP_BTLAN_INTERFACE_NAME Name of interface (lan0, lan1, . . .)
# HP_BTLAN_STATION_ADDRESS Station address of interface
# HP_BTLAN_SPEED Speed and duplex mode
#
# The interface name, major number, card instance and ppa may be
# obtained from the lanscan (1m) command.
# The station address and speed are set through the lanadmin command.
#####################################################################
HP_BTLAN_INTERFACE_NAME[0]=
HP_BTLAN_STATION_ADDRESS[0]=
HP_BTLAN_SPEED[0]=
#####################################################################
# The HP_BTLAN_INIT_ARGS are reserved by HP. they are NOT user changeable.
#####################################################################
HP_BTLAN_INIT_ARGS="HP_BTLAN_STATION ADDRESS HP_BTLAN_SPEED"
# End of hpbtlanconf configuration file
4. As described in steps a, b, and c below, merge every LAN interface (as
shown to be configured in Step 2) into the file hpbtlanconf in the
/var/adm/sw/save_custom/UNIFIED_MER directory.
a. First, note that a set of three parameters is required for each

LAN interface:
• HP_BTLAN_INTERFACE_NAME,
• HP_BTLAN_STATION_ADDRESS and
• HP_BTLAN_SPEED.
b. Second, note that the index value used for the set of three
parameters should be unique for each interface. For example:
220 Appendix D
HP_BTLAN_STATION_ADDRESS[0]=0x080009C4686E
HP_BTLAN_SPEED[0]=100HD
HP_BTLAN_STATION_ADDRESS[1]=0x080009C4B23C
HP_BTLAN_SPEED[1]=FULL
c. Finally, merge all LAN interfaces by creating a set of three
parameters with a unique index for each:
• Copy the value of the interface name into the parameter

HP_BTLAN_INTERFACE_NAME.
• Copy the value of the station address into the parameter
HP_BTLAN_STATION_ADDRESS.
• If the SPEED parameter exists, and if its value (lowercase or
uppercase) is 100FD or 100HD, 10FD or 10HD or auto_on,
copy the value into the HP_BTLAN_SPEED parameter.
However, if the SPEED parameter does not exist, and the
DUPLEX parameter has been set and its value (lowercase or
uppercase) is FULL or HALF, copy the value to
HP_BTLAN_SPEED parameter.
If neither the SPEED nor DUPLEX parameter values have
not been set, do not put any value for the
HP_BTLAN_SPEED parameter.
5. If the hpbtlanconf configuration file already exists (as
/etc/rc.config.d/hpbtlanconf), copy it to
/etc/rc.config.d/hplanconf.obsolete.
6. Move the file hpbtlanconf.merge to hpbtlanconf by using the
command
mv -f /etc/rc.config.d/hpbtlanconf.merge /etc/rc.config.d/hpbtlanconf
7. Restart the update process. Answer NO (N) at the prompt, Do you
want to proceed in merging the configuration file into one? [Y|N].
Appendix D 221
222 Appendix D
Controlling Memory Utilization of VxFS 3.5 on HP-UX 11i v1
E Controlling Memory Utilization

of VxFS 3.5 on HP-UX 11i v1
This appendix discusses the effect of two VxFS tunables vx_ninode and
vx_bc_bufhwm, on system memory consumption and provides guidelines
on setting them for machines with relatively low RAM.

• “Introduction” on page 224
• “Controlling the inode Cache” on page 225
• “Controlling the Buffer Cache” on page 226
• “Conclusion” on page 227
Appendix E 223
Introduction
Introduction
VxFS 3.5 resorts to caching objects in memory as a way to improve
performance. Most of the memory consumed by VxFS is used to cache
inodes (in the inode cache) and metadata (in the buffer cache). The sizes
of these caches and the behavior of VxFS are controlled by a set a
tunables. The performance of VxFS can be tailored to meet a variety of
usage scenarios taking into account variations in machine configurations
via the use of these tunables.
The default settings of these tunables are meant to provide good
performance for typical deployment configurations. However, the4se
default values can result in the VxFS driver consuming more memory,
especially when the file systems are stressed (under heavy file system
load). For machines low on RAM, these tunables may need to be
manually turned down depending on the expected use of the machine
and the performance required of the file system.
VxFS 3.5 exposes two global tunables, vx_ninode and vx_bc_bufhwm,
that control the size of the inode cache respectively and thereby affect
system memory consumption by the file system driver.
This appendix discusses when and why the sizes of the inode and buffer
caches will need to be tuned down from their default values on certain
configurations. the following sections describe these tunables in detail as
well as the effects of changing their default values.
224 Appendix E
Controlling the inode Cache
Controlling the inode Cache

As a matter of course, VxFS file systems allocate and free up inodes as
required by the load on the file system. VxFS caches these inodes for
better performance (faster lookups). In general, larger inode caches help
file systems perform better for file/web server loads. The global (static)
tunable vx_ninode, represents the maximum possible size of the VxFS
inode cache. Normally, the size of the inode cache is decided (auto-tuned)
at boot time by VxFS depending on the amount of physical memory in
the machine, provided that the value of vx_ninode is set to zero
(default).
However, system low on RAM (typically less than or equal to 1GB/CPU
may not require a large inode cache if file systems are not exposed to
file/web server loads, or file system performance is not critical. It is
recommended that the value of vx_ninode be set to more than that of
nfile, an HP-UX tunable that represents the maximum number of file
descriptors.
Appendix E 225
Controlling the Buffer Cache
Controlling the Buffer Cache

VxFS 3.5 implements a private buffer cache used exclusively for
metadata. The allocations made for this buffer cache are not static but
grow and shrink during system usage depending on the load on the file
system. The global (static) tunable, vx_bc_bufhwm, represents the
maximum possible size of the VxFS buffer cache. The maximum size of
the metadata buffer cache is decided (auto-tuned) at boot time based on
system memory size, provided that the value of vx_bc_bufhwm is set to
zero (default).
As with the tunable vx_ninode, a large metadata buffer cache can help
improve file system performance especially during metadata-intensive
loads (stat, create, remove, link, lookup operations). However, systems
low on RAM (having typically 1GB/CPU or less) may not need a large
metadata buffer cache if file system load is not metadata-intensive or
performance is not critical. In such circumstances, the value of
vx_bc_bufhwm can be manually tuned down, subject to a minimum of
6144 (6MB).
226 Appendix E
Conclusion
Conclusion
VxFS uses in-memory caches for objects that results in improved file
system performance. The cache sizes are controlled by tunables that are
auto-tuned at boot time by the driver. For situations where the
auto-tuned values are not optimal, users are provided with the ability to
set these tunables.
Appendix E 227
Conclusion
228 Appendix E
Index
Symbols RAID-00, 83
/etc, 96 Software
/etc/passwd, 112, 113 CIFS/9000 Client, 80
/home, 112, 113 CIFS/9000 Server, 80
/home, restoring, 113 Cluster Object Manager, 80
/local, 113 Enterprise Cluster Master Toolkit, 80
/opt, 66, 96, 113 GlancePlus Pak, 81
disk space, 67 Graphics and Technical Computing
/opt/ifor/ls/bin, 150 Software, 80
/stand, 66 HA Monitors, 80
increasing, 70
Java 3D, 80
/usr, 66, 113
MC/ServiceGuard, 81
disk space, 67
/usr/local, 96 MirrorDisk/UX, 81
/usr/sbin, 130 MLIB, 81
/var, 66, 109 MPI, 81
increasing size, 68 MySQL, 81
/var/opt/ifor, 150 Online JFS, 81
PAM Kerberos, 81
Numerics Process Resource Manager, 81
Service Control Manager, 82
100BaseT-00, 86
100BaseT-01, 86 Technical System Configuration, 82
100BT HSC-FT card Visualize Conference, 82
not supported on 11i, 198 Workload Manager, 82
32-bit OS Workload Manager Toolkit, 82
changing from 64-bit OS, 36 analyzing log files, 186
3D Graphics, 35, 52 Apache
64-bit OS updating an existing version, 34
considerations, 36 applications, 98
update example, 137 changing OE apps, 78
updating to, 36 configuring after update, 124
LicensePower/iFOR, 150
A releases, 156
updating, 147
A-Class, 53
adapters verifying install, 142
PCI Requirements, 65 ATM-00, 86
adding ATM-01, 86
autoboot
groups, 155 halting, 160
OE, 134
patches, 148
B
users, 155
Additional Considerations, 33 backup, 93, 94, 125
administration make_net_recovery, 125
file system, 154 make_tape_recovery, 125
Always-Installed, 78 Base OE, 133
Drivers Base-VXVM, 79
FDDI-00, 83 B-Class
FibreChanl-00, 82 B1000, 53
GigEther-00, 83 B2000, 53
GigEther-01, 83 before updating
229
Index
rebuild kernel, 97 restore /local, 113
before you begin, 102 restore /opt, 113
updating, 116 restore /usr, 113
boot retrieve information, 112
verifying firmware, 61 preparing, 92, 95
boot device types, 106 process, 103
boot information required CDs, 105
newer Series 800, 163, 164 required software bundles, 109
older Series 700, 162 saving key information, 95
older Series 800, 164 troubleshooting, 177
Superdome, 39 typical problems, 177
built-in PCI networking, 154 typical time, 105
BUNDLE11i, 79
bundles verify install, 113
OnlineDiag, 89 vs. update, 31, 67
commands, 125
i4admin, 150
C
ioscan, 127, 129
C3700 workstations, 51 make_net_recovery, 125
C-Class make_tape_recovery, 125
C3000, 53 mk_kernel, 123
C3600, 53 mount, 127, 129
C3700, 51 sam, 127
changing file system size, 68 script, 123
Next Steps, 46 set_parms, 154
swcopy, 128
CIFS/9000
Client, 80 swinstall, 120, 123, 130, 137, 147
Server, 80 swlist, 123, 125, 140, 142, 147
cleaning log files, 123 swremove, 135, 148
Cluster Object Manager, 80 swverify, 140, 142
cold-install tail, 123
advanced installation, 106 update-ux, 115, 120, 121, 123, 126, 128, 130,
alternate methods, 39 131, 133, 148
before you begin, 102 v3tov4, 150
considerations, 39 configuration, 154
Golden Images, 40 adding groups, 155
Instant Ignition, 39 adding users, 155
Software Depot, 39 Built-in PCI Networking, 154
Deciding a Method, 31 LAN, 154
definition, 26 networking, 154
flowchart, 104 OE Applications, 124
guided installation, 106 peripherals, 155
How To, 105 printers, 155
install wizard, 106 tasks, 155
kernel build fails, 177 configuration files
Netscape Directory Server, 34 save before cold-install, 96
next steps, 112 configuring HP-UX 11i
create new root, 112 problems, 196
recover files, 113 considerations
64-bit OS, 36
restore /home, 113
230
Index
additional, 33 bundle, 89
cold-install, 39 not installed, 207
Golden Images, 40 overview, 89
Instant Ignition, 39 verifying and adding, 207
Software Depots, 39 Web pages, 89
Netscape Directory Server, 34 web site, 89
update, 35 disk space
Core Software Bundles /opt, 67
Base-VXVM, 79 /usr, 67
BUNDLE11i, 79 planning, 90
FEATURE11-11, 79 requirements, 66
HPUXBase32, 79 usage errors, 194
HPUXBase64, 79 documentation
HPUXBaseAux, 79 Disk and File Management Tasks, 90
HWEnable11i, 79 for planning disk space, 90
OnlineDiag, 79 Managing HP-UX Software with SD-UX,
corrupt system 141
recovering, 206 patches, 145
create depot, 127 downgrading OE, 135
create new root download
after cold-install, 112 firmware, 63
critical patches, 145 patches, 144
installing, 148 drivers
Custom Patch Manager, 144 updating network, 33
custom patches, 156
E
D
EISA
Deciding a Method 100BT, 86
cold-install, 31 FDDI, 86
update, 32 MUX, 86
Default-Installed, 79 Token Ring, 86
Software Enterprise Cluster Master Toolkit, 80
Gnome GTK+, 84 Enterprise OE, 133
HP Apache-based Web Server, 84 error codes
HP Tomcat-based Servlet Engine, 84 with update-ux, 126
HP Webmin-based Admin, 84 error messages, 190
HP XML Web Server Tools, 84 error recovery, update-ux, 190
Java Plug-in 1.2, 84 errors
Java Plug-in 1.3, 84 disk space usage, 194
Java Runtime Environment 1.2, 84 disk-space usage, 194
Java Runtime Environment 1.3, 84 I/O, 193
Mozilla, 84 multiple I/O, 193
Mozilla Source, 84 post-update verify, 194
Perl, 84 root vol. locked, 194
depots swinstall, 194
creating, 127 update/install, 190
managing with SD, 149 update-ux, 126
determine your disk needs, 90 examples
diagnostics adding OE, 134
downgrading OE, 135
231
Index
update from network depot, 135 frecover, 93
update NDS, 137
update selectable software, 138 G
update to 64-bit OS, 137 General Release patch bundle, 41
update using Interactive Software GigEther-00, 83
Selection, 136 GigEther-01, 83
update using match_target, 135 OLA/R, 52
update-ux, 132 GlancePlus Pak, 81
updating 11i OE, 133 Gnome GTK+, 84
upgrading OE, 134 GOLDAPPS11i patch bundle, 41
GOLDBASE11i patch bundle, 41
F Golden Images, 98
installing from, 40
Fast Boot, enable, 105 Graphics Software, 80
fbackup, 93 groups
FDDI-00, 83 adding, 155
FDDI-01, 86
FDDI-02, 86
H
FDDI-03, 86
FEATURE11-11, 79 HA Monitors, 80
FibrChanl-00, 82 halting autoboot, 160
file system Hardware Enablement, 79
administration, 154 How To
LVM, 154 Apply Firmware Patches, 64
NFS, 155 cold-install, 105
VxVM, 154 Identify OS, 50
file system size, adjusting, 68 Identify Software, 50
firmware Identify System Model, 50
applying patches, 64 plan disk space needs, 90
download updgrades, 63 prepare your system, 92
minimum requirements, 53 update, 126
requirements update using interactive Software
L-Class, 53 Selection, 136
requirements table, 54 verify application installation, 142
upgrade, 53 Verify Firmware Version, 59, 60, 61
B-Class, 53 verify installation, 140
C-Class, 53 HP Apache
J-Class, 53 Admin, 84
L-Class, 53 Tomcat, 84
N-Class, 53 Web Server, 84
verifying, 59, 60 XML Web Server Tools, 84
from boot display, 61 HP-UX 11i
firmware patches 100BT HSC-FT card supported, 198
downloading, 63 64-bit OS considerations, 36
installing, 64, 145 cold-install, 105
firmware upgrade deciding when, 31
A-Class, 53 cold-installing, 105
floppy drives configuration problems, 196
update problems, 197 considerations, 33, 35, 39
flowchart Deciding which method, 31
update process, 122 default OS bundles, 210
232
Index
Golden Images, 40 I
maintaining, 156 I/O errors, 193
migrating from older releases, 30 i4admin, 150
Migration Path, 27 Identifying
migration paths, 30 Model, 50
Minimal Computing Operating OS, 50
Environment, 76 Software, 50
OLA/R support, 199 IDS 9000, 85
Other Resources, 28 iFor/LicensePower
patch bundles, 41 uninstalling, 151
preparing your system, 92 Ignite-UX, 85, 93, 94, 98, 125, 149
proactive maintenance, 158 updating the server, 88
reactive maintenance, 157 VxVM, 39
rebuilding kernel, 97 increasing /stand, 70
rebuilding kernel before updating, 123 increasing /var, 68
install kernel
release version, 50 autobooting (S800), 163
requirements, 48
booting (s700), 161
security patches, 145
stopping autoboot (S800), 163
Software Depots, 39 installing
support media, 156 critical patches, 148
Support Plus, 145 verify, 113
Supported Systems, 48 installing from
Technical Computing Operating Golden Images, 40
Environment, 77 Instant Ignition, 39
un-installing, 204 Software Depots, 39
Unsupported Systems, 51 install-sd, 205
update Instant Ignition
deciding when, 32 installing from, 39
update (no OE), 134 interactive mode
update procedure, 131 updating with, 136
update to 64-bit OS, 137 Interactive Software Selection, 136
updating, 115, 126 ioscan, 127, 129
verify install, 113 IPFilter, 85
verifying install, 140 ITRC, 144, 145, 156
Web resources, 28
HPUXBase32, 79 J
HPUXBase64, 79 J6700 workstations, 51
HPUXBaseAux, 79 Java
HSC 3D, 80
ATM, 86 Out-of-Box, 85
FDDI, 86 Plug-in 1.2, 84
GigEther, 83 Plug-in 1.3, 84
HyperFabric Runtime Environment 1.2, 84
D/R, 87 Runtime Environment 1.3, 84
HyperFabric L/N, 87 JAVAOOB, 85
HWEnable11i, 79 J-Class
HWEnable11i patch bundle, 41 J5000, 53
HyperFab-00, 87 J5600, 53
J6000, 53
233
Index
J6700, 51 monitoring update, 123
mount, 127, 129
K Mozilla, 84
Source, 84
Kerberos, 81 MPI, 81
kernel, 97, 123 MTOE, 133
NTPY Parameter, 187 multiple I/O errors, 193
rebuilding, 97, 123 MySQL, 81
L N
LAN N-Class, 53
configuring, 154 upgrading firmware, 53
large systems, 203 NDS
last-minute install/update issues, 68 updating, 34, 137
L-Class, 53 Netscape Directory Server, 85
LicensePower/iFOR considerations, 34
updating, 150 updating, 34, 137
locales network depot, 127
problems with non-C, 208 update example, 135
locate media, 98 networking
log files configuring, 154
cleaning, 97, 123
configuring built-in PCI, 154
LVM, 154
vs. VxVM, 91 configuring LAN, 154
NFS, 155
updating drivers, 33
M
networking data
maintaining save before cold-install, 95
HP-UX 11i, 156 Next Steps
make_net_recovery, 93, 94, 125 Choosing a Migration Path, 46
make_tape_recovery, 93, 94, 109 Cold-Installing HP-UX 11i, 112
match_target, 135 Preparing to Move to HP-UX 11i, 99
using, 136 next steps
MC/ServiceGuard, 81 system requirements, 73
MCOE, 133 NFS, 155
media NIO
locating, 98 100BT, 86
support, 156 FDDI, 86
memory Token Ring, 86
requirements, 66
NTPY, 187
migration flowchart, 27
Migration Paths, 30
Deciding a Method, 31 O
from previous HP-UX releases, 30 OEs
Next Steps, 46 adding, 134
to HP-UX 11i, 27 Base OE, 133
Minimal Computing Operating bundle names, 133
Environment, 76 changing applications, 78
minimum memory requirements, 66 configuring applications, 124
MirrorDisk/UX, 81 downgrading, 135
mk_kernel, 123 Enterprise OE, 133
MLIB, 81 MCOE, 133
234
Index
MTOE, 133 GOLDAPPS11i, 41
TCOE, 133 GOLDBASE11i, 41
updating, 115 HWEnable11i, 41
OLA/R patches
support, 52, 199 adding, 148
Older HP-UX Releases applying firmware, 64
Migrating to HP-UX 11i, 30 BUNDLE11i, 79
Online JFS, 81 critical, 148
OnlineDiagnostics, 79 custom bundles, 156
verifying firmware, 60 Custom Patch Manager, 144
operating Environments downloading individual, 144
Technical Computing Operating firmware, 63
Environment, 77 HP-UX security bulletins, 145
operating environments installed, 148
adding, 134
LicencePower/iFOR, 150
Base OE, 133 management tools, 145
configuring applications, 124
removing, 148
downgrading, 135
resources, 144, 145
Enterprise OE, 133 Support Plus, 145
locate media, 98
Pay Per Use, 85
MCOE, 133 PCI
Minimal Computing Operating ATM, 86
Environment, 76 configuring built-in networking, 154
MTOE, 133 FDDI, 83
TCOE, 133 GigEther, 83
updating, 115, 133 GigEther 100B-SX, 83
upgrading, 134 HyperFabric K, 87
operating envronments HyperFabric V, 87
MTOE, 133 MUX, 86
OS NextGen GigEther, 83
un-installing, 204
RAID, 83
updating, 115 TachyonTL, 82
Other Resources, 28
Token Ring, 86
Overview, 21
overview, 21 PCI Adapters
diagnostics, 89 Requirements, 65
Other Resources, 28 peripherals
configuring, 155
purpose of this book, 23
supported paths, 26 Perl, 84
planning
updating, 120 disk space, 90
post-install
P verify, 113
PAM Kerberos, 81 post-install tasks, 112, 113
parameters preparing
NTPY, 187 clean out log files, 97
PA-RISC locate media, 98
3D Graphics, 35, 52 rebuild kernel, 97
Determining Version, 35, 52 record software versions, 97
patch bundles to cold-install, 95
available bundles, 41 to update, 96
235
Index
preparing your system, 92 retrieving information
printers after cold-install, 112
configuring, 155 root, 66
proactive maintenance, 158 root directory
problems creating a new, 112
configuring HP-UX 11i, 196 root disk
floppy drives, 197 minimum size, 66
non-C locales, 208 rootability
update, 124, 187 VxVM, 39, 91
X.25 cards not supported, 188
process S
update, 120 sam, 96, 127
Process Resource Manager, 81 script, 123
purpose of this book, 23 SCSI
OLA/R, 52
Q SD
Quality Pack patch bundle, 41 managing depots, 149
quarterly releases, 156 re-installing, 205
quickstart, 120 tools, 149
using, 149
R security
RAID-00, 83 patches, 145
reactive software maintenance, 157 Selectable, 79
rebuild kernel, 97, 123 Drivers
before updating, 97 100BaseT-00, 86
rebuilding kernel, 97, 123 100BaseT-01, 86
record software versions, 97, 123 ATM-00, 86
recover, 93 ATM-01, 86
corrupt system, 206 FDDI-01, 86
recover files FDDI-02, 86
after cold-install, 113 FDDI-03, 86
re-installing SD, 205 HyperFab-00, 87
release version, 50 TermIO-00, 86
releases, 156 TermIO-01, 86
removing
TokenRing-00, 86
patches
update-ux, 148 TokenRing-01, 86
TokenRing-02, 86
requirements, 48
CDs for cold-install, 105 Software
next dteps, 73 IDS 9000, 85
to update, 66 Ignite-UX, 85
resources IPFilter, 85
Custom Patch Manager, 144 Java Out-of-Box, 85
patches, 144 Netscape Directory Server, 85
Support Plus, 145 Pay Per Use, 85
restore updating, 138
/home, 113 selected locale not availavble, 193
/local, 113 servers
/opt, 113 A-Class, 53
/usr, 113 L-Class, 53
N-Class, 53
236
Index
requirements, 66 make_net_recover, 125
supported systems, 48 make_tape_recovery, 125
unsupported systems, 51 system configuration, 154
verifying firmware, 60 system firmware
Service Control Manager, 82 minimum requirements, 53
Servlet Engine, 84 System Requirements, 48
set_parms, 110, 154 /opt, 67
size /usr, 67
adjusting file system, 68 3D Graphics, 35, 52
software C3700 workstations need upgrade, 51
record versions, 97, 123 Disk Space, 66
updating selectable software, 138 firmware, 53
software depot, 120 J6700 workstations need upgrade, 51
installing from, 39 Memory Requirements, 66
Software Distributor, 149 next Steps, 73
Software Distributor Administration Guide, OLA/R, 52
148
PA-RISC, 35, 52
Software Selection
interactive mode, 136 PCI Adapters, 65
Software Transition Kit, 30 Supported Systems, 48
source media verifying firmware, 59, 60, 61
locating, 98
steps T
verifying update, 138 Table
STK, 145 Firmware Requirements, 54
Web, 28 tail, 123
Superdome tasks
booting patitions, 39 cleaning log files, 97
installing HP-UX, 39 configuration, 155
support, 89 post-install, 112, 113
media, 156 preparing to cold-install, 95
OLA/R, 52 preparing to update, 96
Support Plus, 98, 156 rebuild kernel, 97
patch bundles, 41 TCOE, 133
services, 145 Technical Computing Operating
Web, 28 Environment, 77
supported migration paths, 30 Technical System Configuration, 82
to HP-UX 11i, 26 TermIO-00, 86
supported systems, 48, 50 TermIO-01, 86
swcopy, 128 tips
swinstall, 96, 120, 123, 130, 137, 147 updating, 97, 123
errors, 194 TokenRing-00, 86
swlist, 123, 125, 140, 142, 147 TokenRing-01, 86
swremove, 135, 148 TokenRing-02, 86
swverify, 125, 140, 141, 142 tools
system SD, 149
backup, 93, 94 troubleshooting
preparing to install, 92 installs/updates, 190
preparing to update, 96 large systems, 203
system backup update, 126
fbackup, 125
237
Index
U all software not updated, 124
uninstalling backup system, 125
HP-UX 11i, 204 clean log files, 123
iFor/LicensePower, 151 configuration, 124
Unsupported Systems, 51 monitor process, 123
update rebuild kernel, 123
64-bit OS, 36 record software versions, 123
applications, 147 verify, 125
before you begin, 116 to 64-bit OS, 36
considerations, 35 to an 11i OE, 133
Deciding a Method, 32 to HP-UX 11i, 131
definition, 26 troubleshooting, 126, 190
error codes, 126 update-ux command, 131
examples vs. cold-install, 31
adding OE, 134 X.25 cards not supported, 188
from network depot, 135 update process
Interactive Software Selection, 136 all software doesn’t get updated, 125
NDS, 137 flowchart, 122
selectable software, 138 monitoring, 123
to 64-bit OS, 137 recording software versions, 97, 123
upgrading OE, 134 running other commands, 124
using match_target, 135 update-ux, 96, 115, 120, 121, 123, 126, 130
flowchart, 122 analyzing log files, 186
from a network depot, 135 command syntax, 131
How To, 126 do not use -i and -x together, 137
Ignite-UX server, 88 error codes, 126
interactive mode, 136 errors, 126
LicensePower/iFOR, 150 examples, 132
NDS, 34, 137 downgrading OE, 135
Netscape Directory Server, 34 from network depot, 135
network drivers, 33 install using swinstall, 130
NPTY parameter failure, 187 installing, 128
operating environments, 115 Interactive Software Selection, 136
OS, 115 match_target option, 135
OS without OE, 134 multiple I/O errors, 193
overview, 120 overview, 211
preparing, 92, 96 preliminary checks, 211
problem with floppy drives, 197 problems, 187
problems, 124 update 11i OE, 133
requirements, 66 using, 131
selected locale not available, 193 upgrading
software depot, 120 C3700 workstations, 51
steps firmware, 63
create network depot, 127 J6700 workstations, 51
installing update-ux, 128 N-Class systems, 53
using update-ux, 131 usage errors
verify update, 138 disk space, 194
swcopy, 128 users
adding, 155
tips, 97, 123
238
Index
using
Custom Patch Manager, 144
SD, 149
V
v3tov4, 150
verify
application install, 142
HP-UX installation, 140
update, 125, 138
VERITAS
rootability, 39, 91
Version
PA-RISC, 35, 52
Visualize Conference, 82
VxVM, 154
Base-VXVM, 79
FEATURE11-11, 79
Online JFS, 81
rootability, 39, 91
vs. LVM, 91
W
web
patches, 144, 145
web access
Ignite-UX, 88
Software Distributor Administration
Guide, 148
Web resources, 28
Web Server, 84
Workload Manager, 82
Workload Manager Toolkit, 82
workstations
B-Class, 53
C3700, 51
C-Class, 53
J5000, 53
J6000, 53
J6700, 51
J7000, 53
requirements, 66
supported systems, 48
unsupported systems, 51
verifying firmware, 59
X
X.25 cards, 188
XML, 84
239
Index
240

HP

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

HP

Hochgeladen von

Copyright:

Verfügbare Formate

HP-UX 11i Version 1 Installation and

Manufacturing Part Number : 5187-4496

Restricted Rights Legend

• First Edition: December 2000 B2355-90703,

2. Choosing a Migration Path

3. Install/Update System Requirements

4. Preparing To Move To HP-UX 11i v1

5. Cold Installing HP-UX 11i v1

6. Updating to HP-UX 11i v1

7. Verifying System Migration

A. Booting HP Servers and Workstations

B. Known Problems and Troubleshooting

C. Using the update-ux Tool

E. Controlling Memory Utilization of VxFS 3.5 on HP-UX 11i v1

This chapter provides a high-level overview of how to install or update

What You Will Find in This Chapter

• “HP-UX 11i Release Names and Release Identifiers” on page 22

HP-UX 11i Release Names and Release

Table 1-1 HP-UX 11i Releases

B.11.11 HP-UX 11i v1 PA-RISC

B.11.20 HP-UX 11i v1.5 Intel Itanium

B.11.22 HP-UX 11i v1.6 Intel Itanium

B.11.23 HP-UX 11i v2 Intel Itanium

The Purpose of this Book

What You Will Find In This Book

• Chapter 2, “Choosing a Migration Path,” on page 29 provides

• Appendix A, “Booting HP Servers and Workstations,” on page 159

Supported Paths to HP-UX 11i v1

— Chapter 3, “Install/Update System Requirements,” on page 47

— Chapter 3, “Install/Update System Requirements,” on page 47

NOTE For more information about cold-installing or updating your system,

Figure 1-1 HP-UX 11i v1 Migration Overview

1. Prepare Your System

References: Chapter 2, Chapter 3, Chapter 4, Appendix B,

Read Chapter 2 to determine path

4. Verify the Migration

5. Update Other Applications

HP-UX 11i v1 Migration Overview

• HP-UX 11i v1 Release Notes - available on the Instant

• HP IT Resource Center - download the latest patches and patch

• HP Workstation and Server Information - find out about the

• Latest versions of HP-UX manuals and white papers:

2 Choosing a Migration Path

What You Will Find in This Chapter:

• “Migrating from Previous HP-UX Releases” on page 30 details the

IMPORTANT If your system is on HP Mission Critical Support, discuss the proper

Migrating from Previous HP-UX Releases

To this HP-UX 11i v1 release with or without an

HP-UX 9.x, 10.01, Cold-install HP-UX 11i v1 or update to HP-UX 10.20

HP-UX 10.20 Cold-install HP-UX 11i v1 or update.b

HP-UX 10.30 Cold-install HP-UX 11i v1 or update to HP-UX 11.0

HP-UX 11.0 Cold-install HP-UX 11i v1 or update.b

HP-UX 11.10 Cold-install HP-UX 11i v1.c

HP-UX 11i v1 Update HP-UX 11i v1 OS and/or OE.b

a. Contents of the HP-UX operating environments are listed in the Read

Deciding Which Method to Use

Depending on your system’s current configuration, here are some general

Cold Install When...

• You are managing several systems with similar OS configurations.

• Your disk space needs reconfiguration. See “Planning Your Disk

IMPORTANT If /stand is not of sufficient size, the partition can be resized,

If your system meets these requirements, follow the update procedure in

Additional Considerations (Cold-install or Update)

Firmware Patches Should Not Be Included In Cold-Install or