11i Installation and Upgrade PDF

HP-UX 11i Installation and Update Guide
HP Servers and Workstations

Edition 8
Important: Review the
Read Before Installing or Updating to HP-UX 11i
booklet accompanying the HP-UX 11i OE Media
before installing or updating to 11i.
Manufacturing Part Number : 5187-2239

March 2003
Printed in U.S.A.
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-2002 Hewlett-Packard Company. All rights reserved.
Reproduction, adaptation, or translation of this document without prior
written permission is prohibited, except as allowed under the copyright
laws.
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.
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,

Printed, CD-ROM, and Web
Third Edition: September 2001,

Fourth Edition: March 2002,

Fifth Edition: June 2002, 5187-0161,

Sixth Edition: September 2002,

Seventh Edition: December 2002,

Eighth Edition: March 2003,

5971-2215,
5185-6511,
5185-6593,
5187-1350,
5187-1827,
5187-2239,
For the latest version, see the HP-UX 11i Documentation section on the
Web at:
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
About this Guide

This guide describes installing HP-UX 11i on HP systems and assumes
that you are the systems administrator and familiar with basic HP-UX
commands and operations.
This guide applies to the December 2002 version of HP-UX 11i. If you
need information for a previous version of HP-UX 11i, refer to that
releases 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 (select localized documentation).
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 accounts home
directory, enter:
cd
Italics
Manual titles, variable in commands and emphasized

words appear in italics. For example, you would
substitute an actual directory name for
directory_name in this command:
cd directory_name
[ ] and |
Brackets [] enclose optional items in command syntax.

The vertical bar | separates syntax items in a list of
choices. For example, you can enter any of these three
items in this syntax:
ls [-a | -i | -x]
Enter
Text in this bold, sans-serif font denotes keyboard keys

and on-screen menu items. A notation like Ctrl-Q
indicates that you should hold the Ctrl key down and
press Q. It is also used to display web page links.
Contents
1. Overview
The Purpose of this Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What You Will Find In This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Supported Paths to HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
18
19
21
24
2. Choosing a Migration Path

Migrating from Previous HP-UX Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
On Mission Critical OE Support? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Deciding Which Method to Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cold Install When... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Update When... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Additional Considerations (Cold-install or Update) . . . . . . . . . . . . . . . . . . . . . . . . . .
Firmware Patches Should Not Be Included Cold-Install or Update Session. . . . .
MLIB Temporarily Removed from TCOE Operating Environment . . . . . . . . . . . .
Updating Network Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing or updating HP Apache-based web server . . . . . . . . . . . . . . . . . . . . . . .
Installing or Updating Netscape Directory Server . . . . . . . . . . . . . . . . . . . . . . . . .
HP 3D Graphics No Longer Supported pre-PA-RISC 2.0 Systems . . . . . . . . . . . .
Update Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating from an HP-UX 11i TCOE With MLIB . . . . . . . . . . . . . . . . . . . . . . . . . .
VxVM Rootability Not Enabled with update-ux . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating to 64-bit OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cold-Install Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using VxVM Rootability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cold-Installing on Partitioned Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Instant Ignition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Alternate Cold-Install Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
If You Have an Existing HP-UX 11i System... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cold-Installing or Updating from DVD media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How is the New DVD Packaging Organized? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DVD Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
26
27
28
29
30
30
30
31
31
31
32
33
33
33
33
34
36
36
36
36
36
38
39
40
41
42
3. Install/Update System Requirements

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
How to Identify Your Systems Model, OS and Software . . . . . . . . . . . . . . . . . . . . 46
Contents
Unsupported Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C3700 and J6700 Workstations Need Processor Board Upgrade . . . . . . . . . . . . . . .
OLA/R Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP 3D Graphics No Longer Supported pre PA-RISC 2.0 Systems . . . . . . . . . . . . . .
Firmware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Current System Firmware Versions and Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Verify Your Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking Workstation Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Checking Server Firmware Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Download Firmware Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Apply Firmware Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCI Adapter Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk Space and Memory Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
47
47
48
48
49
53
54
54
54
58
59
61
62
65
4. Preparing To Move To HP-UX 11i

What is Installed with HP-UX 11i?. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX 11i Operating Environments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OE Application History. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changing Individual OE Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX 11i Software Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX 11i Selectable Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating Your Ignite-UX Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Diagnostics Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning Your Disk Space Needs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Planning Hints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
VxVM Rootability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing your system for HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Prepare Your System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Back up Your System!. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing to Cold-Install Your System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Collect Key Install Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Save Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Preparing to Update Your Existing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Record Software Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rebuild Kernel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
68
68
69
70
70
72
74
75
76
76
77
78
78
79
81
81
82
82
83
83
Contents
Clean Out Your Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Locate Source Media for Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
5. Cold Installing HP-UX 11i

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Cold-Install HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Next Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Retrieve Information After Cold-Installing . . . . . . . . . . . . . . . . . . . . . . . . . .
Create a New Directory for Root Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recover Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore /home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restore Other Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Verify Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
88
89
91
98
98
98
99
99
99
99
6. Updating to HP-UX 11i

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Quickstart/Overview for the Update Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating Tips. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Update to HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
In Case of Trouble. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Optional Step: Create a Network Depot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 1: Install the update-ux Command (Required Task!) . . . . . . . . . . . . . . . . . . . .
Step 2: Using update-ux to Update to HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . .
update-ux Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Step 3: Update Drivers (Existing HP-UX 11i Systems) . . . . . . . . . . . . . . . . . . . . . .
Step 4: Verify the Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
102
103
106
109
109
110
111
113
114
120
120
7. Verifying System Migration

How to Verify Your HP-UX Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Verifying HP-UX Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
How to Verify Application Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
8. Updating Applications
HP-UX Patching Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Use Custom Patch Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Downloading Individual Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
9
Contents
HP Security Bulletins. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP-UX Support Plus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Other HP-UX Patching Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing MLIB (TCOE Customers). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding and Removing Individual Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Using Software Distributor Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managing Software Depots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating LicensePower/iFOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
How to Convert the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling iFOR Version 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
129
129
129
129
131
132
134
135
135
136
136
137
9. Next Steps
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Maintaining Your HP-UX 11i System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
A. Booting HP Servers and Workstations

Halting the Autoboot Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Booting Workstations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Booting HP Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Booting V-Class Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Searching for Other Bootable Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
146
147
149
152
154
B. Known Problems and Troubleshooting

Known Problems Discovered in this Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
HP Apache 2.0 Will Not Start on Reboot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Cold-Install Warnings from DVD Media . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A6974A Adapter Card for IETHER-00 Not to be Released . . . . . . . . . . . . . . . . . . .
VxVM Checklist Errors During TCOE Golden Archive Install . . . . . . . . . . . . . . . .
OpenView SNMP Agent Produces Error with Upgrade to HP-UX 11i . . . . . . . . . .
X11MotifDevKit Produces Incompatible Error After Upgrade from HP-UX 10.20
cdrecord Application Requires Patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MLIB 8.3 Produces Warning During Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Install Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
MLIBPROD.MLIB Produces Multiple swverify Warnings and Errors . . . . . . . . .
10
156
157
157
159
159
160
161
163
163
164
164
Contents
System Console "kthread table full" or "fork failed" Messages . . . . . . . . . . . . . . . .
Kernel Build Fails on 64-bit Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Known Issues With OE Media Install Tool and Network Depots . . . . . . . . . . . . . .
Update Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Initialize of the ITO Control Agent failed Error During update-ux Session . . . .
Firmware Patches Should Not Be Included Cold-Install or Update Session . . . . .
Analyzing Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Update Fails on J2250 Workstation With SCSI Floppy Drive . . . . . . . . . . . . . . . . .
Update Fails if nstrpty Kernel Parameter Set as a Formula . . . . . . . . . . . . . . . . . .
Kernel Build Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
X.25 Cards Not Supported on Some Workstations . . . . . . . . . . . . . . . . . . . . . . . . . .
HP A3740A Fibre Channel PCI Tachyon Not Supported . . . . . . . . . . . . . . . . . . . . .
Common Install and Update Error and Warning Messages . . . . . . . . . . . . . . . . . . . .
Warning Displays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Selected Locale Not Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Multiple OE Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk Space Usage Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
swinstall Analysis Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Post-update swverify Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Root (/) Volume Lock Error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EISA 100BT Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problems Configuring HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling AutoFS on High Availability Servers Can Cause NFS Packages to be
Dropped . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Changes to Hardware Diagnostics Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware Information Not Captured on Systems With Floppy Drive . . . . . . . . . .
Auto-Port Aggregation Will Not Work on rp7410 Systems . . . . . . . . . . . . . . . . . . .
EISA Cards Not Supported on 64-bit OS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
100BT HSC-FX Cards Do Not Work on HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI PCI Restrictions for OLA/R . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SCSI PCI HBA Documentation Correction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adjusting Required Minimum File System Sizes . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Update Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increasing /var . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Increasing /stand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problems with Large Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Un-installing HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Re-installing SD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recovering a Corrupt System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
165
165
166
167
167
168
168
169
169
169
170
171
172
172
172
173
173
174
174
174
175
176
176
177
178
178
179
179
179
180
182
182
182
184
186
187
188
189
11
Contents
Verifying and Adding Diagnostic Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Problems Affecting non-C Locales. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Difference between English and Japanese HP-UX STK . . . . . . . . . . . . . . . . . . . . .
Warning when updating to non-C locales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restrictions with Netscape Communicator 4.75 . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Character-code handling with Perl and Apache . . . . . . . . . . . . . . . . . . . . . . . . . . . .
190
191
191
191
191
191
C. Using the update-ux Tool

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
About update-ux. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
update-ux Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
D. Configuring Built-In PCI Networking

1000Base-T (Gigabit Ethernet) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PCI 10/100Base-TX and 100Base-FX/9000. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compatibility and Installation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring Network Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Manual Speed and Duplex Mode Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Speed and Duplex Mode at Boot Time (workstation only). . . . . . . . . . . .
Autonegotiation and Auto-sensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
RJ-45 and AUI Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
What Happens During Card Initialization Sequence? . . . . . . . . . . . . . . . . . . . . .
V-Class PCI 10/100Base-TX Card Specifications . . . . . . . . . . . . . . . . . . . . . . . . .
Hardware Regulatory Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
199
201
201
202
205
207
207
208
208
210
211
212
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
12
Tables
Table 2-1. Migrating from Previous HP-UX Releases . . . . . . . . . . . . . . . . . . . . . . . . .26
Table 2-2. Patch Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Table 3-1. Supported Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Table 3-2. Minimum Firmware Versions for HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . .50
Table 3-3. Older Workstation Firmware Requirements . . . . . . . . . . . . . . . . . . . . . . . .51
Table 3-4. Minimum Firmware Versions for OL* Support . . . . . . . . . . . . . . . . . . . . .51
Table 3-5. Current System Firmware Versions and Patches . . . . . . . . . . . . . . . . . . . .53
Table 3-6. Free Disk-space Requirements for /usr and /opt . . . . . . . . . . . . . . . . . . . .63
Table 4-1. HP-UX 11i Software Bundles and Descriptions . . . . . . . . . . . . . . . . . . . . .70
Table 4-2. HP-UX 11i Selectable Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
13
Tables
14
Figures
Figure 1-1. HP-UX 11i Migration Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Figure 2-1. Comparison of CD-ROM and DVD Packaging. . . . . . . . . . . . . . . . . . . . . .40
Figure 5-1. Cold-installing HP-UX 11i . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Figure 6-1. Updating HP-UX 10.20 or 11.0 to 11i . . . . . . . . . . . . . . . . . . . . . . . . . . .105
Figure 9-1. Reactive Software Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143
Figure 9-2. Proactive Software Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .144
15
16
Overview
Overview
This chapter provides a high-level overview of how to install or update
your HP9000 system to HP-UX 11i.
What You Will Find in This Chapter:
The Purpose of this Book on page 18 outlines the scope of this book
What You Will Find In This Book on page 19 provides a summary

of the contents of this book.
Supported Paths to HP-UX 11i on page 21 provides a high-level

overview of the supported migration paths to install or update to
HP-UX 11i
Other Resources on page 24 lists other HP documentation and

information we recommend you read prior to installing or updating
HP-UX 11i
Chapter 1
17
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. This new version of HP-UX delivers
hardware enablement, software functionality, and bundles of important
HP-UX applications in operating environments. HP-UX 11i Operating
Environments (OEs) are described in the HP-UX 11i March 2003 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 releases.
HP-UX 11i 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
Media booklet for March 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 Operating Environment has already been
installed. You do not need to re-install it.
18
Chapter 1
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
from start to finish. The following list summarizes what you will find in
the chapters ahead:
Chapter 2, Choosing a Migration Path, on page 25 provides

information and scenarios to help you decide the most appropriate
method to move your system to HP-UX 11i.
Chapter 3, Install/Update System Requirements, on page 43 details

the system requirements to either install or update to HP-UX 11i.
Chapter 4, Preparing To Move To HP-UX 11i, on page 67 details the

required and recommended tasks to prepare your system for HP-UX
11i. This chapter also includes additional information about
required, default and optional software installed with HP-UX 11i.
Chapter 5, Cold Installing HP-UX 11i, on page 87 shows you how to

cold-install HP-UX 11i 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, on page 101 shows you how to

update your system to HP-UX 11i using the update-ux command.
Several examples are provided to assist you with your update
scenario.
Chapter 7, Verifying System Migration, on page 123 shows you how

to verify a successful install or update to HP-UX 11i.
Chapter 8, Updating Applications, on page 127 shows you how to

update applications on your system that are not installed or updated
with HP-UX 11i operating environments.
Chapter 9, Next Steps, on page 139 provides you an overview of

additional configuration and maintenance tasks.
Appendix A, Booting HP Servers and Workstations, on page 145

describes booting various HP servers and workstations using the
built-in Boot ROM firmware interface.
Chapter 1
19
Overview
Appendix B, Known Problems and Troubleshooting, on page 155

contains critical information for you to review before you start
installing or updating to HP-UX 11i.
Appendix C, Using the update-ux Tool, on page 193 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 199

describes configuring built-in (or core) PCI networking cards in HP
workstations and servers.
20
Chapter 1
Overview
Supported Paths to HP-UX 11i

There are two basic supported methods for moving to HP-UX 11i:
Cold-install HP-UX 11i This method overwrites everything on

the target disk. Use cold-install for new systems and on existing
systems when overwriting the root (/) volume will not cause loss of
applications or data. The process described in this guide cold-installs
a single system from local media. If you plan to install many systems
simultaneously, you should plan on using an Ignite-UX server.
Ignite-UX is a free product available on the HP-UX 11i CD1 or
DVD1. 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 43
Chapter 4, Preparing To Move To HP-UX 11i, on page 67
Chapter 5, Cold Installing HP-UX 11i, on page 87
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 43
Chapter 4, Preparing To Move To HP-UX 11i, on page 67
Chapter 6, Updating to HP-UX 11i, on page 101
Chapter 1
21
Overview
NOTE
For more information about cold-installing or updating your system,

please read Chapter 2, Choosing a Migration Path, on page 25.
22
Chapter 1
Overview
Figure 1-1
HP-UX 11i Migration Overview
1. Prepare Your System

Enough Disk Space? See page 62
HP-UX 11i supported on your system? See page 44
Is your system firmware up-to-date? See page 49
Installing a new OE with HP-UX 11i? See page 26
Your applications certified to run on HP-UX 11i?
Decide: Migrate by either cold-installing or updating
Backup Your System:
- Collect Key Install Information
- Backup Existing System
- Save 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
Read Chapter 2 to determine path
2. Cold -Install HP-UX 11i

Verify System Requirements
Insert HP-UX 11i CD1 or DVD1
Boot From CD or DVD
Install HP-UX 11i
Restore config & personal files
Backup Your System
Reference: Chapter 5
3. Update to HP-UX 11i

Verify System Requirements
Insert HP-UX 11i CD1 or DVD1
Install update-ux
Create optional update depot
Update to HP-UX 11i
Backup Your System
4. Verify the Migration

Verify HP-UX 11i installation using swlist and swverify
5. Update Other Applications

Update additional applications with swinstall
Install critical patches and remove unneeded patches
References: Chapter 8 and HP-UX 11i Release Notes
HP-UX 11i Migration Overview
Chapter 1
23
Overview
Other Resources
Other Resources
You can find other important information about HP-UX 11i updates and
issues in several resources:
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 releases.
Read Before Installing or Updating to HP-UX 11i - 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 page, then select the appropriate
Patching tools. To receive HP Security Bulletins, select: Maintenance
and Support -> Support Information Digests.
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/
Local-language user manuals:

http://docs.hp.com (select: localized documentation)
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/
24
Chapter 1
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.
Migrating from Previous HP-UX Releases on page 26 details the

supported paths based on your current version of HP-UX 11i.
Deciding Which Method to Use on page 28 defines the supported

methods for moving to HP-UX 11i and offers addition information to
consider when making your decision.
If You Have an Existing HP-UX 11i System... on page 38 details the

bundles that will be updated if you are already running HP-UX 11i.
Chapter 2
25

Migrating from Previous HP-UX Releases

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

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

operating environment:a
HP-UX 9.x, 10.01,

or 10.10
Cold-install HP-UX 11i or update to HP-UX 10.20 before

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

updating to HP-UX 11i.b
HP-UX 11.0
Cold-install HP-UX 11i or update.b
HP-UX 11.10
Cold-install HP-UX 11i.c
HP-UX 11i
Update HP-UX 11i 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 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 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/
26
Chapter 2

On Mission Critical OE Support?
On Mission Critical OE Support?

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
27

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
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 79), 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 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. If you
need to continue using DFS, do not update to HP-UX 11.x or HP-UX
11i.
Depending on your systems current configuration, here are some general

guidelines to help you choose the best migration path to HP-UX 11i.
28
Chapter 2

Cold Install When...

We recommend using Ignite-UX to cold-install HP-UX 11i in the
following situations:
You are managing several systems with similar OS configurations.
You need fast, predictable deployment.
Your disk space needs reconfiguration. See Planning Your Disk

Space Needs on page 76.
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 44.)
The cold-install process using Ignite-UX is described in Chapter 5. See
Preparing to Cold-Install Your System on page 81 for more
information.
Chapter 2
29

Update When...
You can update rather than cold-install HP-UX 11i when you are
updating from HP-UX 10.20 or 11.0 as well as the following:
NOTE
You are only updating a few (1-3) systems to HP-UX 11i.
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.
Each system has a unique configuration.
Current disk space is sufficient for HP-UX 11i (see Planning Your
Disk Space Needs on page 76).
update-ux removes all HP-UX 10.x patches from the system prior to
updating to HP-UX 11i. Any 10.x applications left on the system after
the update may not be supportable if they required those patches. After
migrating your system, consult the documentation for those remaining
applications for HP-UX 11i requirements.
If your system meets these requirements, follow the update procedure in

Chapter 6. See Preparing to Update Your Existing System on page 82
for more information about preparing to update your system.
Additional Considerations (Cold-install or Update)

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
A-Class
You?
L-Class
30
N-Class
Chapter 2

Many of the HP-UX 11i firmware patches rely on HP-UX 11i 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 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. Specific HP-UX 11i firmware patches are available
at the following website:
http://itresourcecenter.hp.com
MLIB Temporarily Removed from TCOE Operating Environment
With the December 2002 release of HP-UX 11i, MLIB was temporarily
removed from the OE media. A supplemental CD-ROM has been
provided and instructions for installing or updating MLIB can be found
in Installing MLIB (TCOE Customers) on page 132
Updating Network Drivers
Installing or updating to HP-UX 11i will install a minimum set of default
networking drivers that apply to the system (see Table 4-1, HP-UX 11i
Software Bundles and Descriptions, on page 70). You may need to select
or specify other available networking drivers to enable other cards on
your system (see Table 4-2, HP-UX 11i Selectable Drivers, on page 72).
This can easily be done during install or update by following the
instructions for your selected migration path.
Installing or updating HP Apache-based web server
If your system already is running any version of the HP Apache-based
Web Server, installing or updating to an HP-UX 11i Operating
Environment will not install the version of Apache included with the
HP-UX 11i OE. If you wish to install the version of Apache provided with
HP-UX 11i, you should swinstall it after migrating your system to
HP-UX 11i. See Chapter 8 for example uses of the swinstall command.
Chapter 2
31

Installing or Updating Netscape Directory Server
Although the Netscape Directory Server (NDS) Version 6.02 is included
in HP-UX 11i 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. For more on this, see Updating Netscape Directory Server
on page 119.
NOTE
Currently, Netscape Directory Server Version 6.02 is included with the

HP-UX 11i 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, 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, the server will cease to work and all client systems may
lose the ability to have anyone log in.
After NDS is installed or updated with HP-UX 11i, additional

configuration steps are required to initiate NDS. See the NDS release
notes available on the HP-UX 11i Instant Information CD for
instructions.
32
Chapter 2

HP 3D Graphics No Longer Supported pre-PA-RISC 2.0 Systems
As of the September 2002 HP-UX 11i 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 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.
Update Considerations
The following sections provide additional information to assist you in
your decision to update to HP-UX 11i:
Updating from an HP-UX 11i TCOE With MLIB
Due the the temporary removal of MLIB software from the the TCOE
operating environment media, if you are updating your system from a
previous or current version of the HP-UX 11i TCOE operating
environment, you will need to remove MLIB prior to installing MLIB
from the HP Math Library (MLIB) supplemental CD. For more information,
please review the update procedures in Chapter 6, Updating to HP-UX
11i, on page 101 and Installing MLIB (TCOE Customers) on page 132.
VxVM Rootability Not Enabled with update-ux
With the September 2002 release of HP-UX 11i, 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, see Using VxVM Rootability on page 36
Chapter 2
33

using the VxVM conversion tools provided in the Base-VXVM and

FEATURE11-11 bundles that are installed with HP-UX 11i (for more
information about HP-UX 11i software bundles, see What is
Installed with HP-UX 11i? on page 68). For more information, see
the VERITAS Volume Manager 3.5 Release Notes and VERITAS
Volume Manager 3.5 Administrators 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.
Updating
considerations
and workarounds
You can update a system from 32-bit OS to 64-bit OS while updating to

HP-UX 11i, provided that you consider these hardware and firmware
issues:
Is your system capable of running 64-bit operation? See Table 3-1,

Supported Systems, on page 44 in Chapter 3.
Is your systems firmware recent enough to support 64-bit operation?

See Firmware Requirements on page 49 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 system from 32-bit to 64-bit OS,

do not include the HP-UX 11i 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.
34
Chapter 2

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,
changing from 32-bit to 64-bit OS and installing the HP-UX 11i
Quality Pack (GOLDQPK11i) bundle, you must install patch
PHSS_23644 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 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 Table 4-1, HP-UX 11i
Software Bundles and Descriptions, on page 70. Other drivers can
be specified in the update-ux command or installed later using
swinstall.)
To determine if any EISA drivers are installed on the system, use
swlist. For example:
/usr/sbin/swlist -l bundle 100BaseT-00 FDDI-03 \
TermIO-01 TokenRing-02
If any EISA drivers are on the system, remove them. For example, to
remove the TermIO-01 EISA MUX driver, as root enter:
/usr/sbin/swremove -x autoreboot=true TermIO-01
The kernel will automatically regenerate and the system will reboot
after you remove each driver. After removing all EISA drivers,
proceed to update as explained below.
If you're updating from HP-UX version 11.0 or higher, update-ux will
determine if your hardware and firmware are compatible with 64-bit
operation. If you're updating from HP-UX version 10.20, however, refer
to the Software Transition Kit available on the HP-UX Applications
media. The STK contains tools and documents to assess applications or
libraries that run on HP-UX 10.20 and 11.0 and help transition them to
the HP-UX 11i 64-bit operation. The ITRC web site
Chapter 2
35

(http://www.itresourcecenter.hp.com/) also has release notes and a
FAQ with details about supported systems and necessary firmware
updates.
Cold-Install Considerations
The following sections provide additional information to assist you in
your decision to cold-install HP-UX 11i:
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 77
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 Instant Information CD and on HPs 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 partitions 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:
36
Chapter 2

Installing From Software Depots Use Software Distributor
commands to create depots containing OS, OE, and other software
bundles, then install from the depot using Ignite-UX. For help with this
method, see the swinstall (1M) manpage and Software Distributor
Administration Guide and Ignite-UX Administration Guide.
Installing from Golden Images If you need to install the same
OS/OE and applications on many systems in your network, use an
Ignite-UX server as explained in the Ignite-UX Administration Guide.
With Ignite-UX, you can create a single install image (golden image)
containing OS/OE bundles, application bundles and patch bundles, then
install the image on multiple systems in your environment.
Chapter 2
37

If You Have an Existing HP-UX 11i System...
If You Have an Existing HP-UX 11i System...

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

delivers critical patches for
HP-UX 11i systems.
Defect fixes for HP-UX 11i
OS and network drivers
included in OEs.
Defect fixes for HP-UX 11i
OE applications.
Available via:
HP-UX CD1/DVD1
SupportPlusa
Xb
Xb
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 HPs Enterprise Patch Test Center.
For instructions on installing patch bundles on an existing HP-UX 11i

system, see Chapter 6, Updating to HP-UX 11i, on page 101
38
Chapter 2

Cold-Installing or Updating from DVD media

With the December 2002 release of HP-UX 11i, 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
no disks to shuffle during installation - all of the core HP-UX 11i

operating system software is contained on one DVD
fewer installation steps
shortened installation times
Chapter 2
39

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 operating environment, and all of the HP-UX
11i 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 OE (2 CDs)
HP-UX 11i OE (1 DVD)
HP-UX 11i Applications
HP-UX 11i 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
40
Chapter 2

DVD Availability
DVD drives are now available for both PA-RISC servers and
workstations. Contact your HP Customer Engineer for more details
about your systems requirements.
Chapter 2
41

Next Steps
Next Steps
Once you have decided how you want to move to HP-UX 11i, you can now
evaluate the system requirements to run HP-UX 11i against your
systems configuration. For more information please read Chapter 3,
Install/Update System Requirements, on page 43 for detailed
information about:
IMPORTANT
System Requirements on page 44
Firmware Requirements on page 49
PCI Adapter Requirements on page 61
Disk Space and Memory Requirements on page 62
Be sure to review the Read Before Installing or Updating to HP-UX 11i

media booklet for situations not discussed in this chapter that may apply
to your system.
42
Chapter 2
Install/Update System Requirements
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.
IMPORTANT
System Requirements on page 44
Firmware Requirements on page 49
Disk Space and Memory Requirements on page 62
PCI Adapter Requirements on page 61
Be sure to review this entire guide and the Known Problems

information in the Read Before Installing or Updating to HP-UX 11i
media booklet for March 2003 before proceeding to install or update your
system. Carefully review Appendix B, Known Problems and
Troubleshooting, on page 155 for situations that may apply to your
system.
If you have just received a system that was ordered with Instant
Ignition, the HP-UX 11i Operating Environment has already been
installed. You do not need to re-install it.
Chapter 3
43

System Requirements
System Requirements
This section lists systems that support HP-UX 11i. Unsupported systems
are also listed in Unsupported Systems on page 47. To determine if
HP-UX 11i is supported on your system, see How to Identify Your
Systems Model, OS and Software on page 46 and compare your system
information with Table 3-1.
Supported Systems
HP-UX 11i 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,
743, 744, 745, 748i, 748
B132L, B132L+, B160L, B180L
B1000, B2000, B2600
C100, C110, C160L
C160, C180, C180-XP, C200, C240, C360
C3000, C3600, C3650, C3700, C3750 (See

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

Firmware Requirements on page 49 for
additional requirements)
44
X
X
Chapter 3

System Requirements
Table 3-1
Supported Systems (Continued)

Bezel or Model
32-bit
64-bit
Servers:
A180, A180C
A400, A500
Dx10, Dx20, Dx30, Dx50, Dx60
Dx70, Dx80, Dx90
Kx00, Kx10, Kx20
Kx50, Kx60, Kx70, Kx80
L1000, L1500, L2000, L3000
N4000-36, N4000-44
R380, R390
rp2400, rp2450 (HP-UX model string is A4xx-xx

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

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

N4000-8X)
rp7405 and rp7410
rp-8400 (model S16K-A)
Superdome (models SD16000, SD32000, SD64000)
T500, T520
T600
Chapter 3
45

System Requirements
Table 3-1
Supported Systems (Continued)

Bezel or Model
32-bit
64-bit
V22xx, V2500, V2600
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 Systems 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 is supported on your system (see Table 3-1,
Supported Systems, on page 44).
Identify OS and OE To identify the OS version that your system is currently running, enter:
uname -r
To update to HP-UX 11i, your system must be currently running either
B.10.20 or B.11.00. After cold-installing or updating to HP-UX 11i,
youll notice that uname identifies the HP-UX 11i release as B.11.11.
When a system has HP-UX 11i installed, you can determine which
revision of HP-UX 11i 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.0209) and the description text
(for example, Hardware Enablement Patches for HP-UX 11i, March
2003).
To identify the Operating Environment currently installed on your
system, use swlist. For example:
46
Chapter 3

System Requirements
/usr/sbin/swlist | grep Operating Environment Component
For example, the HP-UX 11i OE March 2003 release generates the
following output:
HPUX11i-OE B.11.11.0303 HP-UX 11i Operating Environment Component
Identify installed
software
To identify the software products on a system or media, use swlist. For

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 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 Operating Environment. See
the Read Before Installing or Updating to HP-UX 11i 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. Contact your HP Customer Engineer for more details.
Chapter 3
47

System Requirements
OLA/R Support
Online addition and replacement (OLA/R) is not supported on HP-UX 11i
with the A5801A HIPPI PCI I/O adapter. The GigEther-01 driver also
does not support OLA/R on rp7410 core cards. For more about OLA/R
support, see SCSI PCI Restrictions for OLA/R on page 179 in
Appendix B and this web site:
http://itrc.hp.com
HP 3D Graphics No Longer Supported pre PA-RISC

2.0 Systems
As of the September 2002 HP-UX 11i 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 March 2003 release of the
Technical Computing (TCOE) or Minimal Computing Operating
Environments (MCOE).
Previous releases of HP-UX 11i 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 Systems 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.
48
Chapter 3

Firmware Requirements
Some systems may need a firmware upgrade prior to updating to HP-UX
11i:
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 61. If not, or if you do
not know what firmware version is on your system, please read on.
Chapter 3
49

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/onlinedocs/2218/System_Firmware_Matr
ix_3_2.htm
Table 3-2
Minimum Firmware Versions for HP-UX 11ia

Firmware and Patch for HP-UX 11i Support
Minimum Available Patches
Model or Bezel
A-Class
Firmware
Version
HP-UX 11.0/11i
Tape Patch
Name
41.18
PHSS_25314
PHSS_25315
PF_CCRW4118
B-Class, C-Class,
J-Classa
5.0
PHSS_25982
PHSS_25983
PF_CBCJ0050
C3650, C3700,
C3750, J6700,
J6750
1.9
n/a
n/a
L1000, L2000,
rp5400, rp5450
41.38
PHSS_25105
PHSS_25106
PF_CRHW4138
L3000 Rev A.
40.43
All Firmware
n/a
L1500, L3000,
rp5430, rp5470
41.36
All Firmware
PF_CMAW4136
N4000, rp7400
41.02
PHSS_22657
PHSS_22658
PF_CPRW4102
a. For older workstations, see Table 3-3
50
Chapter 3

Table 3-3
Older Workstation Firmware Requirements

Model or Bezel
Firmware
Version
32/64
bit
Tape Patch Namea
B132L, B132L+,
B160, B180
6.1
32-bit
PF_CB1X0061
B2600b
1.4
64-bit
PF_CB260014
B[12]000, C3X00,
J[567]X00b
5.0
64-bit
PF_CBCJ0050
C160L
5.8
32-bit
PF_CB1X0058
C160, C180
6.1
32 and
64-bit
PF_CC2X0061
C200, C240
6.3
32 and
64-bit
PF_CC2X0063
J280, J282
2.5 (updated)
32 and
64-bit
PF_CJ28X025
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
Table 3-4
Minimum Firmware Versions for OL* Support

Firmware and Patch for OL*a Support
Model or Bezel
Minimum Current Patches

Firmware
Version
A-Class (A400,
A500)
B-Class, C-Class,
J-Class
L1000, L2000,
rp5400, rp5450
Chapter 3
HP-UX 11.0/11i
Tape Patch
Name
(OL* not available on A-Class)

(Also, OL* not available on workstations.)
41.39
PHSS_25684
PHSS_25685
PF_CRHW4139
51

Table 3-4
Minimum Firmware Versions for OL* Support (Continued)

Firmware and Patch for OL*a Support
Model or Bezel
Minimum Current Patches

Firmware
Version
HP-UX 11.0/11i
Tape Patch
Name
L3000 Rev A.
41.46
PHSS_25686
PHSS_25687
L1500, L3000,
rp5430, rp5470
42.19
PHSS_25686
PHSS_25687
PF_CCAW4219
N4000, rp7400
42.06
PHSS_22688
PHSS_25931
PF_CPIW4206
rp7410
Firmware
Version 4.0
PDC rev. 16.009
PF_CRP7410040
0
rp8400
Firmware
Version 4.0
PDC rev. 16.009
PF_CRF8400040
0
a. OL* = OnLine add, delete, and replace
IMPORTANT
OL* functionality is only supported on HP-UX 11i 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 servers:
PHCO_25831
PHKL_25712 (or later)
For more information on SCSI OLA/R restrictions, see the following web
page: http://www.techsolutions.hp.com/scsi/scsi_olar.html
52
Chapter 3

Current System Firmware Versions and Patches

In addition to verifying that your system meets the minimum
requirements to support HP-UX 11i 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 functionality.
Table 3-5
Current System Firmware Versions and Patches

Current Firmware Version and Patch Support
Available Patches
Model or Bezel
Latest
Firmware
Version
B1000, B2000,
J5x00, J6x00
C3650, C3700,
C3750, J6700,
J6750
B2600 Workstation
5.0
SD-UX
Patch Name
HP-UX 11i /11.0
Tape Patch
Name
PHSS_25982
PF_CBCJ0050
PHSS_25983
1.9
n/a
1.4
n/a
PHSS_26926
PF_CB260014
PHSS_26927
A400, A500, rp24xx
42.19a
PHSS_27383
PF_CHAW4219
PHSS_27384
L1000, L2000,
rp5400, rp5450
41.39
PHSS_25684
PF_CRHW4139
L1500, L3000,
rp5430, rp5470
42.19b
rp7410
4.0c,d
n/a
PF_CRP74100400
S16K-A, rp8400
4.0c,d
n/a
PF_CRP84000400
PHSS_25685
PHSS_27466
PF_CARIW4219
PHSS_27467
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.
Chapter 3
53

b. Added support for CPU product numbers A6152B and A6805B.
c. Added support 875 MHz PA-8700 3.0 and 3.1 processors.
d. Boot over Ultra160 SCSI is now supported.
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:
Step 1. As root, shut down the system:
1. Enter: shutdown -h
2. Switch the system OFF.
Step 2. Switch the system ON and watch console messages. Press any key when
prompted to cancel the automatic boot feature.
Step 3. Check the 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 58.
NOTE
Even if your workstations firmware is 2.3 or later, HP recommends (but

does not require) that you update to the most current firmware version
(version 5.0 at the time of this printing).
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. Use OnlineDiagnostics if you do
not want to reboot your system.
54
Chapter 3

Using OnlineDiagnostics: If the OnlineDiagnostics are not already
on your system, you can find them on the HP-UX 11i Support Plus CD,
OE DVD1, or on OE CD2.
Chapter 3
55

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
===
1
34
35
Path
====================
system
...
160
166
Product
=========================
system ()
CPU (5c4)
CPU (5c4)
Select any one of the processors (CPU) to use in the next step.
Step 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
56
Chapter 3

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 58
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.
Step 2. Youll 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. Youll see the information menu:

---Information Menu------------------------------------------Command
Description
------------------------ALL
Display all system information
BootINfo
Display boot-related information
Cache
Display cache information
Chapter 3
57

ChipRevisions
FRU
FwrVersion
...
Main
Display revisions of major VLSI

Display FRU information
Display firmware information
Return to Main Menu
Information Menu: Enter command>
Enter: FV (for Firmware Version)

Youll see something like the following:
FIRMWARE INFORMATION
Firmware Version:
40.14
Step 4. Continue with the boot (example commands are in bold):

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 58
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.
58
Chapter 3

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 44 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.
Step 6. After downloading the patch, proceed to How to Apply Firmware
Patches on page 59.
How to Apply Firmware Patches

Follow these steps to install each patch youve downloaded on each
system prior to updating it to HP-UX 11i:
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
Chapter 3
59

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.
60
Chapter 3

PCI Adapter Requirements
PCI Adapter Requirements

Before installing HP-UX 11i, 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. Connect any fibre
channel mass storage devices previously connected to A3740A to the
A5158A adapters.
Chapter 3
61

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 182 in Appendix B for directions
on how to increase file system sizes.
To update your HP server or workstation to HP-UX 11i, 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 184 in Appendix B)
/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 63)
62
4GB root disk, minimum, whether installing or updating to HP-UX

11i, with or without an OE. This can be a single disk drive or
combination of physical disks configured as one root volume.
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 Update Task
/usr
/opt
10.20 -> 11i default update: HPUXBase,

HPUXBaseAux, network drivers, CDE and
OnlineDiag
400 MB
225 MB
10.20 -> 11i 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,

HPUXBaseAux, HWEnable11i, BUNDLE11i,
network drivers, CDE and OnlineDiag.
220 MB
225 MB
11.0 -> 11i 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 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
63

Extra space
Cold-installing the HP-UX 11i 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 booklet supplied with the
HP-UX 11i CD or DVD media. Be sure to review that booklet as well as
Appendix B, Known Problems and Troubleshooting, on page 155 before
continuing.
64
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, on page 67 will guide you through
important tasks such as:
listing what is installed with HP-UX 11i
determining which migration path to choose
preparing your system based on the migration path you have chosen
backing up your system.
Chapter 3
65

Next Steps
66
Chapter 3
Preparing To Move To HP-UX 11i
Preparing To Move To HP-UX

11i
This chapter helps you to prepare to install or update your system with
HP-UX 11i.
What is Installed with HP-UX 11i? on page 68 lists the software

bundles and drivers installed with HP-UX 11i.
Updating Your Ignite-UX Server on page 74 explains critical next

steps if you are planning to update an existing Ignite-UX server.
Diagnostics Dependencies on page 75 provides a brief description

and importance of the OnlineDiag bundle installed with HP-UX 11i.
Planning Your Disk Space Needs on page 76 provides hints and

information to help you determine your disk needs for HP-UX 11i.
Preparing your system for HP-UX 11i on page 78 provides an

overview and preparation steps required to either cold-install or
update your system to HP-UX 11i.
Back up Your System! on page 79 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 79
make_tape_recovery on page 80
make_net_recovery on page 80
Locate Source Media for Migration on page 84 helps you determine

the media source to install or update your system with HP-UX 11i.
Next Steps on page 85 provides details on next steps based on your

decision to either cold-install or update your system.
Chapter 4
67

What is Installed with HP-UX 11i?

HP-UX 11i 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 systems needs. The following section, HP-UX 11i Operating
Environments details the OEs currently available.
HP-UX 11i Operating Environments

Operating Environments are tested and integrated application bundles
designed to work with the operating system and provide the
functionality needed for your systems purpose. OEs are incremental,
meaning that each OE includes the previous OEs bundle set as well as
additional software and applications. The following list details the
currently available HP-UX 11i OEs:
HP Servers
The following OEs are available for HP Servers:
HP-UX 11i OE Designed for the demands of Web servers,
content servers and front-end servers, this OE is provided at
no-charge and includes applications such as Apache Web Server,
Java, Netscape Communicator and WebQoS. This OE is bundled
as HPUX11i-OE.
HP-UX 11i Enterprise OE Designed for database
application servers and logic servers, this OE is an extra-cost
package containing HP-UX 11i OE and additional applications
such as GlancePlus to enable an enterprise-level server. This OE
is bundled as HPUX11i-OE-ENT.
HP-UX 11i Mission Critical OE 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.
68
Chapter 4

HP Workstations
The following OEs are available for HP Workstations
HP-UX 11i Minimal Technical OE Designed for
workstations running HP-UX 11i, this OE is provided at no
charge and includes the Netscape, NDS, Perl, VxVM, and Judy
applications, plus the OpenGL Graphics Developers Kit. This
OE is bundled as HPUX11i-MTOE.
HP-UX 11i Technical Computing Operating
Environment Designed for compute-intensive workstation
and server applications, this OE includes most applications in
the HP-UX11i OE plus extensive graphics applications. This OE
is bundled as HPUX11i-TCOE.
IMPORTANT
NOTE
TCOE Customers: With the December 2002 release of HP-UX

11i, MLIB was temporarily removed from the OE media. A
supplemental CD-ROM has been provided and instructions for
installing MLIB can be found in Installing MLIB (TCOE
Customers) on page 132
For more details about the contents of each OE, please read the Read
Before Installing or Updating to HP-UX 11i booklet supplied with the
HP-UX 11i CD or DVD media.
OE Application History
The current versions of applications installed with each HP-UX 11i OE
are listed in the Read Before Installing or Updating to HP-UX 11i media
booklet supplied with the HP-UX 11i 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 OE applications,
see this web site:
http://www.software.hp.com/RELEASES-MEDIA/
Chapter 4
69

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 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.
If you still wish to add individual OE products to an HP-UX 11i system
or remove a product from an installed OE, first please read this
document available on HPs documentation Web:
http://docs.hp.com/hpux/onlinedocs/os/11i/filesets.html
Updating OE
Applications
Most applications included in HP-UX 11i OEs are also available as

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 booklet.
HP-UX 11i Software Bundles

Table 4-1
HP-UX 11i Software Bundles and Descriptions
SD Bundle Name
Description
These HP-UX 11i OS bundles are installed by default from the media:
HPUXBase32 or
HPUXBase64
HP-UX 11i Base OS installation, either 32- or 64-bit
HPUXBaseAux
Additional OS software including SD, SCR+DMI, EMS Framework,

Judy Libraries, Update-UX, Obam5, and Partition Manager
OnlineDiag
HP-UX 11i Support Tools

70
Chapter 4

Table 4-1
HP-UX 11i Software Bundles and Descriptions (Continued)
SD Bundle Name
Description
HWEnable11i
Support for new hardware
BUNDLE11i
Required OS patches
CDE-xxx
Servers: CDE-English
Workstations: all CDE bundles
FibrChanl-00
PCI FibreChannel adapter (64-bit OS only)
RAID-00
PCI RAID 4Si Controller (64-bit OS only)
FDDI-00
FDDI PCI driver (32-bit OS only)
IEther-00a
PCI 10/100Base-TX Ethernet
GigEther-00
10/100/1000BaseT Ethernet
GigEther-01
1000BaseT Ethernet (supports the A6825A and A6847A add-on

cards for several servers)
FibrChanl-00
PCI FibreChannel Tachyon TL

HSC Tachlite (A180, D, K, R-Class)
perl
Perl
Base-VXVM
Base VxVM (v 3.5)
FEATURE11-11
Feature Enablement Bundle:

Required if you want to use VxVM on your root volume. See VxVM
Rootability on page 77.
Appropriate base OS bundle and standard software above are installed by

default with each of these OE bundles:b
HPUX11i-OE
Default environment for commercial servers
HPUX11i-OE-Ent
Enterprise environment for commercial servers
HPUX11i-OE-MC
Mission Critical environment for commercial servers
HPUX11i-MTOE
Minimal technical workstation environment
HPUX11i-TCOE
Environment for technical workstations and servers
Chapter 4
71

Table 4-1
HP-UX 11i Software Bundles and Descriptions (Continued)
SD Bundle Name
Description
The following product bundles are customer selectable (for selectable drivers,
see Table 4-2, HP-UX 11i Selectable Drivers, on page 72):
B5725AA
Ignite-UX-10-20
Ignite-UX-11-00
Ignite-UX-11-11
Ignite-UX utilities
J4258CA
Netscape Directory Server
JAVAOOB
Java Out-of-Box
J5083AA
IDS 9000 (commercial server OEs only)
B9901AA
IPFilter (commercial server OEs only)
a. Although HP has decided not to release the A6974A adapter card, the IETHER-00
driver software will remain in 11i to support future cards.
b. Contents of each OE are listed in the Read Before Installing or Updating to HP-UX
11i booklet supplied with the HP-UX 11i media.
HP-UX 11i Selectable Drivers

Table 4-2
HP-UX 11i Selectable Drivers

Driver
Description
ATM Drivers:
ATM-00
PCI ATM
ATM-01
HSC ATM
FDDI/9000 Drivers:
FDDI-00
FDDI-01
FDDI-02
FDDI-03
72
PCI (A180, L, N, V-Class)

PCI
HSC (K, T-Class)
HSC (B, C, D, J-Class)
HPPB (K, T-Class)
EISA
Supported I/O Adapters

A5483A,A5513A, A5515A,
J3557A
J2468A, J2469A, J2499A,
J3420B, J3573A
A3739A
A3739B
A3722A
A3723
J2157B
A3659A, B5502BA
Chapter 4

Table 4-2
HP-UX 11i Selectable Drivers (Continued)

Driver
Description
FibrChanl-00
RS-232 MUX Drivers:

TermIO-00
TermIO-01
Token Ring Drivers:
TokenRing-00
TokenRing-01
TokenRing-02
100BaseT Drivers:
100BaseT-00
100BaseT-01
Supported I/O Adapters
PCI FibreChannel Tachyon

TL
HSC Tachlite (A180, D, K,
R-Class)
A5158A
A6684A, A6685A, A6795A
8 port PCI MUX

64 port PCI MUX
EISA MUX (32-bit OS only)
A6748A, J3592A
A6749A, J3593A
J2482A, J2483A
PCI Token Ring

HPPB Token Ring
EISA Token Ring (32-bit OS
only)
A5783A, A4930A
J2166B
J2165B
EISA 100BT (32-bit OS only)

HPPB 100BT (K, T-Class)
A4308B
A3495A
Chapter 4
73

Updating Your Ignite-UX Server
Updating Your Ignite-UX Server

The HP-UX 11i OE CD1/DVD1 contains the complete Ignite-UX product.
When you cold-install HP-UX 11i from the media, a subset of Ignite-UX
is used to perform the installation on a single system.
If you plan to update an existing Ignite-UX server to install HP-UX 11i
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 on page 113 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:
74
Chapter 4

Diagnostics Dependencies
Diagnostics Dependencies
HP-UX 11i 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 (it will be installed by
default with any HP-UX 11i 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
75

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. If you need more disk space (HP-UX 11i
generally requires a 4GB root volume), be sure to order the equipment
and plan on installing it after backing up your current system as
explained later in this chapter.
Planning Hints
Record the hardware path to the CD 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 Operating Environment (OE), consider the vendors
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
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.
76
Chapter 4

VxVM Rootability
VxVM Rootability
With the September 2002 release of HP-UX 11i, you can choose to
manage your root volume using either HPs 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
77

Preparing your system for HP-UX 11i

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:
Decide the method you want to use to move to HP-UX 11i. See
Chapter 2, Choosing a Migration Path, on page 25 for detailed
information about supported migration paths.
Decide which Operating Environment to install (usually matches the

media or depot). See HP-UX 11i Operating Environments on
page 68 and the Operating Environments chapter in the HP-UX
11i March 2003 Release Notes for detailed information. The Read
Before Installing or Updating to HP-UX 11i 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 March 2003 Release Notes or the Read Before Installing or
Updating to HP-UX 11i).
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
Appendix B, Known Problems and Troubleshooting, on
page 155 in this book
Chapter 3, Install/Update System Requirements, on page 43 of
this book
Pay particular attention to the following:
System backups
78
Chapter 4

Disk space requirements. See Disk Space and Memory
Requirements on page 62
Firmware revisions. See Firmware Requirements on page 49
Back up your system. See Back up Your System! on page 79.
If you are planning to cold-install your system, using Ignite-UX, see

Preparing to Cold-Install Your System on page 81
If you are planning to update your system using update-ux, see

Preparing to Update Your Existing System on page 82.
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 on page 78). Do this
first before performing a cold-install or update, and again after the
cold-install or update. If a problem occurs, its a very simple procedure to
restore the system to its original state.
This section offers three alternatives for performing system backups:
fbackup, make_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 is provided on the HP-UX
11i OE CD1 or DVD1, and can be either cold-installed along with HP-UX
11i to create a new server or specified in the update-ux command to
update an existing Ignite-UX server to HP-UX 11i. See Chapter 2 for
details.
Chapter 4
79

Using make_tape_ The Ignite-UX servers make_tape_recovery command creates a bootable
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 Instant Information CD and at this web site:
http://docs.hp.com/
Using make_net_
recovery
The Ignite-UX server also has the make_net_recovery command to

create a system recovery archive on another system on the network. The
archive created by make_net_recovery is specific to the system 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.
80
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 Chapter , Preparing your system for
HP-UX 11i, on page 78.
Collect Key Install Information
During the cold-install process, you will be prompted for your systems
identity and network addresses. Record the following data on paper or on
another computer for access during the migration:
Hostname (for example, elvis) To get your systems hostname,

enter:
hostname
Host IP address (for example, 15.0.68.12). To get the above

systems IP address, enter:
nslookup elvis
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
81

Save Configuration Files
If you are planning to cold-install HP-UX 11i 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 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.
82
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.
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
Chapter 4
83

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 (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 media kit:
HP-UX 11i 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 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 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
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 85
to determine your next steps.
84
Chapter 4

Next Steps
Next Steps
After you have chosen your migration path and prepared your system for
HP-UX 11i, you are now ready to either cold-install or update to HP-UX
11i.
For cold-install information: see Chapter 5, Cold Installing

HP-UX 11i, on page 87
For update information: see Chapter 6, Updating to HP-UX 11i,

on page 101
Chapter 4
85

Next Steps
86
Chapter 4
Cold Installing HP-UX 11i

This chapter describes cold-installing from the HP-UX 11i 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 90, along with alternate methods of cold-installing
11i.
Before You Begin on page 88
Installing HP-UX 11i on page 89
Next Steps on page 98
How to Retrieve Information After Cold-Installing on page 98
Chapter 5
87

Before You Begin
Before You Begin

Before you cold-install HP-UX 11i, 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 30
Cold-Install Considerations on page 36
You are sure your system meets the system requirements to install
and operate HP-UX 11i. For more information see Chapter 3,
Install/Update System Requirements, on page 43
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, on page 67. Pay particular attention to:
Preparing to Cold-Install Your System on page 81
88
Chapter 5

Installing HP-UX 11i

This section describes cold-installing from the HP-UX 11i 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 90, along with alternate methods of cold-installing
11i:
Chapter 5
89

Figure 5-1
Cold-installing HP-UX 11i
Determine
install
approach
If Factory
Integrated
From
Media
Install 11i OS/OE using
Ignite-UX
Install non-OE applications

using swinstall
From Golden
Image **
From
Depots *
Create 2 install depots:
OE depot: OS/OE, QPK
Create Install Golden

Image using
Ignite-UX Server **
AR depot: Applications,
QPK
(see notes below)
(see Chapter 8)
Install QPK patches from

Support Plus CD using
swinstall (see Chapter 8)
Using tools from ITRC,

identify and install needed
patches ***
Install from OE depot using

Ignite-UX
Install image using

Ignite-UX Server
Install non-OE applications

from AR depot using
swinstall
(see Chapter 8)
Notes:
Install 3rd-party and

internal software
Create
archive/recovery
image
QPK - Quality Pack from Support Plus CD contains

patch bundles for OS/OE and applications
* For help creating depots, see the Software
Distributor Administration Guide
** Golden image can contain OE/OE, patches,
and application bundles.
For help creating golden images, see the
Ignite-UX Administration Guide
*** The Custom Patch Manager (CPM) can be
found at the ITRC (http://itrc.hp.com)
Done
Cold-installing HP-UX 11i

90
Chapter 5

How to Cold-Install HP-UX 11i

Required media
Have thee following media ready from the HP-UX 11i media kit:
HP-UX 11i OE CDs 1 and 2 or DVD 1, March 2003 or later.
Support Plus CD, March 2003 or later (for hardware enablement,

quality pack, and diagnostics.
Typical install time Cold-installing HP-UX 11i typically takes from 2-3 hours, depending
upon the system and whether you are installing only the OS or also
installing an OE.
Begin Cold
Installation
Use the following steps to cold install HP-UX 11i on your system:
Step 1. Insert the HP-UX 11i CD1 or DVD1 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 145.
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 , Halting the
Autoboot Process, on page 146. 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
3. Return to the Main Menu: MA
(Remember to switch Fast Boot back OFF after installing 11i.)
Chapter 5
91

Step 4. Search for bootable devices, using the choices displayed (for example,
enter search or sea). Youll see a table similar to this:
Path#
----P0
P1
P2
Device Path
----------SESCSI.2.0
LAN.1.2.3.4.5.6
FWSCSI.6.0
Device Type
----------TOSHIBA CD-ROM
1.2.3.4
IBM DDRS-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, youll be asked Interact with IPL? Press: n
The install kernel will load (takes 3-5 minutes), after which a screen
might ask you to enter the keyboard language of your console. Enter the
number and press Return/Enter and again to 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]
+---------------------+---------------+-------------------+
[
92
Install HP-UX
Run a Recover Shell
Advanced Options
Chapter 5

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 62.
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
93

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 34).
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.
94
Chapter 5

Additional Software: Select networking drivers and other applications

for your system (see HP-UX 11i Selectable Drivers on page 72).
IMPORTANT
Do not de-select the HPUXBaseAux, HWEnable11i,

OnlineDiag or BUNDLE11i bundles. If in doubt, leave the
selections as default. Other software products may be selectable,
however, we recommend that you do not de-select any products at
this time. For more about Online Diagnostics, see Diagnostics
Dependencies on page 75 in Chapter 4.
TIP
If youre installing an Ignite-UX server, be sure to select the entire

Ignite-UX server product, B5725AA, thus installing the new
make_tape_recovery 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.
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.
NOTE
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.
Chapter 5
95

Step 11. When prompted, replace HP-UX 11i CD1 or DVD1 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 ...
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,
GOLDAPPS11i, which updates OE applications, and GOLDBASE11i, which
updates the Base OE (including the always-installed and selectable
driver products).
After installing or updating applications, insert the HP-UX Support Plus
CD and install the Quality Pack patch bundles to update the Base OE
and OE applications on your system. 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
Step 14. TCOE customers only: If you want to install MLIB, see Installing
MLIB (TCOE Customers) on page 132
Problems?
If you encounter a problem during the cold-install process, first review

Appendix B, Known Problems and Troubleshooting, on page 155 for
possible solutions.
96
Chapter 5

You can also find help on this web site:
http://forums.itrc.hp.com/
NOTE
This concludes the cold-install procedure. For more information about

additional tasks you will need to perform, see Next Steps on page 98
Chapter 5
97

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-1 on page 70
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 roots 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.
98
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 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 123
Chapter 5
99

Next Steps
100
Chapter 5
Updating to HP-UX 11i

This chapter describes updating your system to HP-UX 11i 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 25.
Before You Begin on page 102
Quickstart/Overview for the Update Process on page 103
Updating Tips on page 106
How to Update to HP-UX 11i on page 109
Chapter 6
101

Before You Begin
Before You Begin

Before you update to HP-UX 11i, 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 30
Update Considerations on page 33
You are sure your system meets the system requirements to install
and operate HP-UX 11i. For more information see Chapter 3,
Install/Update System Requirements, on page 43
You have completed the preparation tasks required to update your

system. For more information see Chapter 4, Preparing To Move To
HP-UX 11i, on page 67. Pay particular attention to:
Preparing to Update Your Existing System on page 82
102
Chapter 6

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 March 2003 Release Notes.)
Step 1. Select your OE
Step 2. Review the Update Process flow chart (Figure 6-1 on page 105).
Step 3. Read Updating Tips on page 106.
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 111 for more
information.
From the CD/DVD
media:
swinstall -r -s /cdrom 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
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 OS (OE Installed) on
page 115 for more information.
From the CD/DVD
media:
update-ux -s /cdrom HPUX11i-OE-Ent
From a depot:
update-ux -s dept_server:/var/depots/my_depot \
HPUX11i-OE-Ent
Chapter 6
103

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.
Step 7. TCOE Customers: If you are updating from a previous HP-UX 11i
release and want to install MLIB, you need to remove the old MLIB
version from your system.
104
Chapter 6

Figure 6-1
Updating HP-UX 10.20 or 11.0 to 11i

Create
archive/recovery
image
update
Determine
update
approach
cold-install
Cold-Install from
media, depots or
golden image
(see page 87)
Important!
Install
update-ux
(page 111)
depots
Determine
source
Create depots(s)
(see page 110)
from media
Update to 11i OE from
depot containing
OS/OE and Support
Continue to update
Plus bundles using
OS/OE from 11i OE
update-ux
media using update-ux
(see page 117)
(start at page 113)
Update non-OE
applications from
Application media
using swinstall
(Chapter 8)
Install patches from

Support Plus media
using swinstall
(see Chapter 8)
Update non-OE
applications using
swinstall (Chapter 8)
Identify and install

non-OE
patches
(use
Identify and
install
Custom
Patch
non-OE
patches
using Custom
Manager)Patch
Install 3rd-party and

internal software
Updating
HP-UX 10.20/11.0 to 11i
Create
archive/recovery
image
DONE
Chapter 6
105

Updating Tips
Updating Tips
Before You Begin
Your Update:
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.
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
Update:
Monitor The Update Process

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:
106
Chapter 6

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 155 for possible
solutions.
After the Update:
Configuring OE Applications
After updating to an HP-UX 11i 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 products installation
instructions for details. Location of OE product documentation is listed
in the tables at the back of the Read Before Installing or Updating to
HP-UX 11i booklet and in the HP-UX 11i March 2003 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 such as HP
Apache-based Web Server, will not automatically get updated if a version
of the product not previously installed with an OE already exists on the
system. Youll have to update or re-install those products after updating
11i. For more information about how to update these additional software
bundles, please see Update Selectable Software on page 120.
Chapter 6
107

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 123.
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. 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. See Back up Your System! on page 79 in Chapter 4.
108
Chapter 6

How to Update to HP-UX 11i

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

create a network depot for other systems to update to HP-UX 11i,
then follow this procedure.
Step 1: Install the update-ux Command (Required Task!) on page

111: Shows you how to install the update-ux command on your
system.
Step 2: Using update-ux to Update to HP-UX 11i on page 113:

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: Update Drivers (Existing HP-UX 11i Systems) on page 120:

If you are updating an existing 11i system, be sure to follow this
procedure.
Step 4: Verify the Update on page 120: Shows you how to verify the
update once update-ux has finished.
TCOE Customers: With the December 2002 release of HP-UX 11i, MLIB
was temporarily removed from the TCOE OE media. A supplemental
MLIB CD-ROM has been provided for you to install MLIB after you have
completed updating your system.
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).
Chapter 6
109

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 172
in Appendix B.
Optional Step: Create a Network Depot

HP-UX 11i is delivered on two 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 111
As root, follow this procedure to create a network depot from the HP-UX
11i CDs or DVD onto a depot server or other system running HP-UX 11i
in your network:
Step 1. Verify that you have at least 1,230 MB of free space to create the network
depot on another system in your network. If this space is not available,
use sam to either create a new volume group or extend an existing
volume group. For help, see either SAM help or the Managing Systems
and Workgroups manual.
Step 2. 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 CD1 or DVD1 and wait for the drives 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.
110
Chapter 6

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
DVD: mount /dev/dsk/c1t2d0 /dvdrom
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 using CD-ROM, follow steps 9 10; DVD users, continue to Step 1: Install the update-ux
Command (Required Task!) on page 111
Step 9. Insert the HP-UX 11i CD2. Wait for the drives busy light to stop
blinking.
Step 10. Repeat Steps 6 through 8 using CD2 and the Support Plus CD.
The network depot is now ready to update your HP-UX 10.20 or 11.0
system to HP-UX 11i.
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:
Step 1. Insert the HP-UX 11i CD1 or DVD1 and wait for the drives busy light to
stop blinking.
Chapter 6
111

DVD: mkdir /dvdrom
example:
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
media:
CD-ROM: swinstall -r -s /cdrom Update-UX \

DVD: swinstall -r -s /dvdrom Update-UX \

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 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.
112
Chapter 6

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.
Step 2: Using update-ux to Update to HP-UX 11i

After you have installed update-ux on the target system (see Step 1:
Install the update-ux Command (Required Task!) on page 111) and,
optionally, created an update depot containing all software to be
installed, (see Optional Step: Create a Network Depot on page 110),
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 196
Chapter 6
113

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 OS (OE Installed) on page 115 shows you how
to update to HP-UX 11i with an operating environment
Update to HP-UX 11i OS (No OE Installed) on page 116 shows you

how to update the HP-UX 11i OS without an operating environment.
Adding or Upgrading an OE on page 116 shows you how to update

your system by either adding or upgrading the operating
environment on your system.
Downgrading an OE on page 117 shows you how to move your

system from an advanced operating environment to a smaller
operating environment.
Update From a Network Depot on page 117 shows you how to

update your system from a server on the network.
Update Using match_target on page 117 shows you how to update

your system using the match_target option.
Update Using Interactive Software Selection on page 118 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 119 shows you how to move a

32-bit system to a 64-bit OS.
Updating Netscape Directory Server on page 119 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 120 shows you how to update

your system with selectable software bundles.
114
Chapter 6

We Recommend
this Update:
Update to HP-UX 11i OS (OE Installed)

To update to HP-UX 11i 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
HPUX11i-OE-Ent
HPUX11i-OE-MC
HPUX11i-MTOE
HPUX11i-TCOE
HP-UX 11i Operating Environment

HP-UX 11i Enterprise OE
HP-UX 11i Mission Critical OE
HP-UX 11i Minimal Technical OE
HP-UX 11i Technical Computing OE
For example, to update to 11i and install the default 11i OE, insert an
HP-UX 11i 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 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 120 for more information
For details on what is included in each of the Operating Environments,
see Chapter 4 of the HP-UX 11i March 2003 Release Notes or the HP-UX
11i OE Contents section of the Read Before Installing or Updating to
HP-UX 11i media booklet. These books can be found on the HP
documentation web site: http://docs.hp.com/hpux/os/11i/
Chapter 6
115

Update to HP-UX 11i 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
OS, networking, diagnostic and CDE bundles listed on page 70. Any
additional software bundles associated with an OE are not installed.
For example, to update the HP-UX 11i OS, insert HP-UX 11i CD1 or
DVD1 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 OE to Enterprise OE)
insert the HP-UX 11i media in the CD or DVD drive and specify the new
OE using update-ux. For example, to add the default HP-UX 11i 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 11i OE CD1
with 11i OE CD2, then 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.
116
Chapter 6

Downgrading an OE
If you wish to downgrade your system from a higher-level OE, say, from
Mission Critical OE to 11i OE, first use update-ux to install the smaller
OE from the la set of HP-UX 11i 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 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 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 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
DVD: /usr/sbin/update-ux -s /dvdrom -x match_target=true

HPUX11i-OE
Chapter 6
117

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
OE Components
Only
CD-ROM: /usr/sbin/update-ux -s /cdrom -x

match_target=true HPUX11i-OE.
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 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 swinstalls 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.
CAUTION
Do not combine -i and -x options in the same update-ux command.
118
Chapter 6

When the -i option is specified, swinstalls interactive user interface is
active only when swinstall is running to load software from each source
location. When installing from HP-UX 11i CDs, you will have to select
non-default software twice; once for each CD. If you do set swinstall
options like match_target, be sure to re-select those options in the
second swinstall session.
For help using 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 34.
If you have decided to upgrade an HP-UX 11i 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, you should update
to 11i as explained in Installing or Updating Netscape Directory Server
on page 32. Be sure to specify the new NDS bundle in the update-ux
command. For example, this command updates to the default HP-UX 11i
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
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 Administrators Guide, available on
the Netscape web site:
http://www.netscape.com
Chapter 6
119

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 and include additional selectable software (such
as Ignite-UX):
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 default HP-UX 11i OS

bundles listed on page 70, plus the Ignite-UX server bundle, B5725AA.
Step 2. Complete any post-install configuration explained in the HP-UX 11i
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 Chapter 2 in the Ignite-UX
Step 3: Update Drivers (Existing HP-UX 11i Systems)

After updating an existing 11i system to the latest 11i release, be sure to
use swinstall to update hardware drivers from the new HWEnable11i
bundle. Insert either the HP-UX 11i OE media or the latest Support
Plus CD in your local drive and enter (as root):
CD-ROM: /usr/sbin/swinstall -x autoselect_patches=true

-s /cdrom HWEnable11i
DVD: /usr/sbin/swinstall -x autoselect_patches=true -s

/dvdrom HWEnable11i
Step 4: Verify the Update

IMPORTANT
TCOE Customers: MLIB has not been updated yet. To update MLIB,
please see Installing MLIB (TCOE Customers) on page 132.
120
Chapter 6

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 123.
Chapter 6
121

122
Chapter 6
Verifying System Migration

After installing or updating to HP-UX 11i, 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, see Appendix B.
How to Verify Your HP-UX Installation on page 124
How to Verify Application Installation on page 126
Chapter 7
123

How to Verify Your HP-UX Installation

Verifying HP-UX Installation
To verify that HP-UX 11i was successfully installed, use Software
Distributors 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:
CDE-English
FDDI-00
GigEther-00
GigEther-01
OnlineDiag
HPUX11i-OE
B.11.11...
B.11.11...
B.11.11...
B.11.11...
B.11.11...
B.11.11...
HPUXBase64
HPUXBaseAux
B.11.11...
B.11.11...
English CDE Environment

PCI FDDI;Supported ...
PCI/HSC/EFF-HSC...
PCI/HSC/EFF-HSC...
Online Diagnostics
HP-UX Internet Operating
Environment Component
HP-UX 64-bit Base OS
HP-UX Auxilary Software
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 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.
Step 2. Run swverify to verify that each bundle is intact. For example, to verify
that HP-UX 11i 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:
124
Chapter 7

* 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
125

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 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
systems architecture or operating system.
The indicated software (xyz) has not been updated to 11i. To update the
software, mount the HP-UX 11i 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 applications 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 applications help or
documentation to determine the problem.
126
Chapter 7
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 operating environments.
HP-UX Patching Resources on page 128
Updating Applications on page 131
Installing MLIB (TCOE Customers) on page 132
Adding and Removing Individual Patches on page 134
Using Software Distributor Tools on page 135
Updating LicensePower/iFOR on page 136
Chapter 8
127
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
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 HPs 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 134.
Downloading Individual Patches

When you need to find and download a single patch, use HPs Patch
Database. Begin at HPs 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.
128
Chapter 8
HP Security Bulletins
HP Security Bulletins are e-mailed periodically to announce critical
patches for your system. To subscribe, go to HPs IT Resource Center:
http://itrc.hp.com
Select: Maintenance and Support -> Support Information Digests
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 HPs IT Resource Center.
Other HP-UX Patching Resources

If you are not familiar with patching HP-UX, documents in the Patch
Management section of HPs 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 youve downloaded on each
system prior to updating it to HP-UX 11i:
Step 1. Back up your system!
Step 2. Log in as root.
Chapter 8
129
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
130
Chapter 8
After migrating to HP-UX 11i and backing up your new system, you
should update and/or install other applications not installed with the
HP-UX 11i OE. 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 OS and OE bundle(s) you just
installed. For example, to install HP-UX 11i on other systems after
installing 11i, insert HP-UX 11i CD1 and enter:
/usr/sbin/swinstall -s /cdrom B5725AA
After installing selectable software, complete any post-install
configuration explained in the HP-UX 11i March 2003 Release Notes.
To complete the Ignite-UX server installation, see Chapter 2 in the
Ignite-UX Administration Guide.
Chapter 8
131
Installing MLIB (TCOE Customers)

With the December 2002 release of HP-UX 11i, MLIB was temporarily
removed from the TCOE OE media. TCOE users must install MLIB from
a supplemental HP Math Library (MLIB) CD.
Before You Begin:
If you are updating from either a previous or current HP-UX 11i release,
you must remove the old MLIB software from your system prior to
installing the MLIB from the HP Math Library (MLIB) CD. To remove
MLIB, use the following command:
# swremove -x loglevel=2 MLIBPROD
To Install MLIB:
Use the following steps to install MLIB from the HP Math Library (MLIB)
CD:
Step 1. Start the swagentdt daemon by running the following command

/usr/sbin/swagentd
Step 2. Insert the HP Math Library (MLIB) CD in your CD/DVD drive and wait
for the drives busy light to stop blinking.
DVD: mkdir /dvdrom
example:
Step 6. Use the swinstall command to install MLIB from the HP Math Library
(MLIB) CD, assuming the CD is mounted in /cdrom:
132
Chapter 8
/usr/sbin/swinstall -x mount_all_filesystems=false -x
rpc_timeout=9 -s /cdrom ProductNumber
Where ProductNumber is the identification for MLIB on the CD.
Chapter 8
133
Adding and Removing Individual Patches
Adding and Removing Individual Patches

If you migrated to HP-UX 11i 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 128). 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 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
134
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 media.
Updating SD is easily accomplished using the install-sd command.
See Re-installing SD on page 188 in Appendix B for details.
Managing Software Depots

After updating your depot-management server to HP-UX 11i, 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
135
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 Isogons 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.
136
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
137
138
Chapter 8
Next Steps
Next Steps
Now that you have completed installing or updating your system to
HP-UX 11i, you can begin to configure your system to meet your needs.
System Configuration on page 140 provides you with a list of

resources to information about more common configuration tasks you
may want to perform
Maintaining Your HP-UX 11i System on page 142 provides you

with an overview of how you can maintain your HP-UX 11i system
Chapter 9
139
Next Steps
System Configuration
Now that you have installed or updated to HP-UX 11i, 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 systems 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 Administrators
Guide on the Instant Information CD.
140
Chapter 9
Next Steps
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 can be found at
http://docs.hp.com/hpux/11i/index.html
Chapter 9
141
Next Steps
Maintaining Your HP-UX 11i System

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

cold-installing or updating OEs.
HP-UX 11i 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
142
Chapter 9
Next Steps
Figure 9-1
Reactive Software Maintenance
Encounter Problem
Receive New
3rd Party Software
Search patch
database on
itrc.hp.com
Download patches
(see page 128)
Download patches
(see page 128)
Update or create new

install depot*
Update or create new

install depot*
Install new version

of software
Update software using

swinstall with
match_target
(see page 117)
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
143
Next Steps
Figure 9-2
Proactive Software Maintenance

Receive
Application
Release
Receive Custom
Patch Bundle
Create new
OE install depot*
Create new
OE install depot*
Create new OE
and AR install depots*
Add Support Plus

patch bundle(s) to
depot
Find and add patches

to depot (use Custom
Patch Manager)
Patch software using

swinstall with
patch_match_target
Update OS/OE
using update_ux
(see Chapter 6)
Update software using

swinstall
Receive new
11i OE
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
144
Chapter 9
Booting HP Servers and Workstations
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:
NOTE
Halting the Autoboot Process on page 146
Booting Workstations on page 147
Booting HP Servers on page 149
Booting V-Class Systems on page 152
Searching for Other Bootable Devices on page 154
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
145

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 systems boot process.
If you need help during the boot process, enter: help
146
Appendix A

Booting Workstations
Newer workstation After stopping the boot process, the system displays a menu:
boot menu
Command
Auto [boot|search] [on|off]
Boot [pri|alt|scsi.addr] [isl]
Boot lan[.lan_addr] [install] [isl]
Chassis [on|off]
Diagnostic [on|off]
Fastboot [on|off]
Help
Information
LanAddress
Monitor [type]
Path [pri|alt] [lan.id|SCSI.addr]
Pim [hpmc|toc|lpmc]
Search [ipl] [scsi|lan [install]]
Secure [on|off]
Description
Display or set auto flag
Boot from primary, alternate or SCSI
Boot from LAN
Enable chassis codes
Enable/disable diagnostic boot mode
Display or set fast boot flag
Display the command menu
Display system information
Display LAN station addresses
Select monitor type
Change boot path
Display PIM info
Display potential boot devices
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
147

Older workstation
boot menu
Older HP Workstations display a menu similar to this:

b)
Boot from specified device
s)
Search for bootable devices
a)
Enter Boot Administration mode
x)
Exit and continue boot sequence
?)
Help
Select from menu:
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.
148
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>]
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
149

Booting HP Servers
Newer server
search results
Here is a typical output:
Searching for potential boot device.

This may take several minutes.
To discontinue, press any key.
Path Number
Device Path
P0
56/52.0
(dec)
P1
56/52.3
(dec)
P2
56/52.4
(dec)
P3
56/52.6
(dec)
Main Menu: Enter command or menu >
Device Type
Seq. record access media
Seq. record access media
Random access media
Random access media
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
38.0.0.0.0.0.0
Primary boot path
= 52.2.0.0.0.0.0
(dec)
34.00000002.0.0.0.0.0
Alternate boot path = 52.0.0.0.0.0.0

34.0.0.0.0.0.0
(dec)
(hex)
(hex)
(dec)
(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.
150
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
151

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
AUto [BOot|SEArch ON|OFF]
BOot [PRI|ALT|<path> <args>]
BootTimer [time]
CLEARPIM
CPUconfig [<proc>] [ON|OFF]
DEfault
DIsplay
ForthMode
IO
LS [<path>|flash]
OS [hpux|sppux]
PASSword
PAth [PRI|ALT|CON] [<path>]
PDT [CLEAR|DEBUG]
PIM_info [cpu#] [HPMC|TOC|LPMC]
RESET [hard|debug]
RESTrict [ON|OFF]
SCSI [INIT|RATE] [bus slot val]
SEArch [<path>]
152
Description
Display or set the specified flag
Boot from a specified path
Display or set boot delay time
Clear PIM storage
Configure/Deconfigure Processor
Set the sytem to defined values
Display this menu
Switch to the Forth OBP interface
List the I/O devices in the system
List the boot or flash volume
Display/Select Operating System
Set the Forth password
Display/clear Non-Volatile PDT state
Display PIM of current or any CPU
Force a reset of the system
Display/Select restricted access to Forth mode
List/Set SCSI controller parms
Search for boot devices
Appendix A

SECure [ON|OFF]
TIme [cn:yr:mo:dy:hr:mn[:ss]]
VErsion
Command:
Display or set secure boot mode

Display or set the real-time clock
Display the firmware versions
To determine the boot path, enter:

pa
Primary boot path
Alternate boot path
Console path
Keyboard path
Booting from the

primary path
=
=
=
=
1/0:0.4.0
15/3
15/1
15/1
If your boot device (CD) is mounted at the primary path, enter:

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
153

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
P2
1/2:0.9.0
Disk
: SEAGATE ST19171W
0019
P3
1/0:0.4.0
Disk
: SEAGATE ST19171W
0019
Command:
For this example, boot the CD with:

boot p1
The Install kernel then loads from the CD device.
154
Appendix A
Known Problems and Troubleshooting
Known Problems and

Troubleshooting
This section contains critical information for you to review before you
start installing or updating to HP-UX 11i. 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 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 Operating Environment Update & Installation
Test Procedures white paper at HPs documentation web site:
http://docs.hp.com/hpux/os/11i
What You Will Find in This Appendix:
Known Problems Discovered in this Release on page 156
Install Known Problems on page 164
Update Known Problems on page 167
Common Install and Update Error and Warning Messages on

page 172
Problems Configuring HP-UX 11i on page 176
Adjusting Required Minimum File System Sizes on page 182
Problems with Large Systems on page 186
Un-installing HP-UX 11i on page 187
Re-installing SD on page 188
Recovering a Corrupt System on page 189
Verifying and Adding Diagnostic Drivers on page 190
Problems Affecting non-C Locales on page 191
Appendix B
155

Known Problems Discovered in this Release

The following issues were discovered in the March 2003 release of
HP-UX 11i:
HP Apache 2.0 Will Not Start on Reboot on page 157
Cold-Install Warnings from DVD Media on page 157
A6974A Adapter Card for IETHER-00 Not to be Released on

page 159
VxVM Checklist Errors During TCOE Golden Archive Install on

page 159
OpenView SNMP Agent Produces Error with Upgrade to HP-UX

11i on page 160
See X11MotifDevKit Produces Incompatible Error After Upgrade

from HP-UX 10.20 on page 161
cdrecord Application Requires Patch on page 163
MLIB 8.3 Produces Warning During Update on page 163
156
Appendix B

HP Apache 2.0 Will Not Start on Reboot

By default, HP Apache 2.0 (B9416AA) will not start after rebooting your
system. To fix this problem:
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 129 for more information on how to
install patches.
Step 3. As root, manually start HP Apache using the following command:
/opt/hpapache2/bin/apachectl1 start
IMPORTANT
TCOE Customers: Due to an ld defect, HP Apache will hang. At the

time of this writing, HP is unable to include a patch for the March 2003
release. For more information please read the Dependencies section in
the HP Apache documentation listed below.
Additional
Documentation
For detailed configuration and installation instructions, see the following

HP Apache documentation in the paths listed below (or at
http://machinename/hp_apache_docs/document after the web server
is started):
HP Apache Admin Guide:
/opt/hpapache2/hp_apache_docs/hpapache.admin.guide
HP Apache Release Notes:
/opt/hpapache/hp_apache_docs/hpapache.release.notes
Cold-Install Warnings from DVD Media

Due to a control script error related to the ordering of HP-UX 11i filesets
on the DVD media, you may receive a series of warning messages in your
swagent.log file.
Appendix B
157

How Do You Know If you cold-install HP-UX 11i from DVD media and your swagent.log
If This Affects
file has the following (or similar) error messages:
You?
NOTE:
New paths were added to /etc/MANPATH
Usage: mod_pathfile -{a|d} {P | MP | SP} path

mod_pathfile -i {P | MP | SP} path path
WARNING: /usr/lib could not be added to /etc/SHLIB_PATH
WARNING: /usr/bin could not be added to /etc/PATH
WARNING: /usr/ccs/bin could not be added to /etc/PATH
WARNING: /usr/contrib/bin could not be added to /etc/PATH
WARNING: The "configure" script for "OS-Core.UX-CORE" had a

warning
(exit code "2"). The script location was
"/var/adm/sw/products/OS-Core/UX-CORE/configure".
* This script had warnings but the execution of this
fileset
will still proceed.
Check the above output from the
script
for further details.
* Summary of Execution Phase:

WARNING:
Configured
OS-Core.UX-CORE,l=/,r=B.11.11
WARNING: 1 of 907 filesets had Warnings.
158
Appendix B

* 906 of 907 filesets had no Errors or Warnings.
WARNING: The Execution Phase had warnings.
output for details.
What To Do
See the above
Ignore these warning message and verify your filesets paths using the
swverify command. Your log may look like the following:
* [140112] Checking files for fileset
"OS-Core.UX-CORE,l=/,r=B.11.11".
WARNING: [140114] Fileset "OS-Core.UX-CORE,l=/,r=B.11.11" had
file
warnings.
WARNING: [140044]
Verified with warnings OS-Core.UX-
CORE,l=/,r=B.11.11
A6974A Adapter Card for IETHER-00 Not to be

Released
HP has decided not to release the A6974A adapter card. However, the
driver software associated with the adapter card will remain on the
media in order to support future cards.
VxVM Checklist Errors During TCOE Golden Archive

Install
During a TCOE golden archive installation, VxVM produces several
checklist errors if you use a saved configuration from the original
machine.
How Do You Know The problem is isolated to only customers who are installing the TCOE
If This Affects You operating environment from a golden image, using the original systems
VxVM configuration file. You may see the following types of checklist
errors after you reboot the system installed with the golden image:
Configure system crash dumps
Output from "/sbin/rc1.d/S080crashconf start":
---------------------------EXIT CODE: 0
Appendix B
159

VxVM device node check

Output from "/sbin/rc1.d/S091vxvm-nodes-check start":
---------------------------/sbin/rc1.d/S091vxvm-nodes-check[4]: /usr/sbin/lsdev:
found
not
VxVM general startup Dynamically linked vxconfigd not

accessible
Output from "/sbin/rc1.d/S092vxvm-startup start":
----------------------------
Output from "/sbin/rc1.d/S093vxvm-reconfig start":

---------------------------/sbin/rc1.d/S093vxvm-reconfig[47]: /etc/vx/lib/vxcommon:
found
not
"/sbin/rc1.d/S093vxvm-reconfig start" FAILED
Mount file systems

Output from "/sbin/rc1.d/S100localmount start":
---------------------------checking quotas
What To Do
There are no fixes or workarounds at this time. However, VxVM should

continure to work properly after reboot.
OpenView SNMP Agent Produces Error with Upgrade

to HP-UX 11i
Due to a preinstall script error, customers upgrading to HP-UX 11i may
see the following error:
* [140184] Installing fileset "OVSNMPAgent.MASTER,r=B.11.11"
(54 of 1293).
160
Appendix B

* [20255] Running "postinstall" script for fileset
"OVSNMPAgent.MASTER".
* [20255] Running "preinstall" script for fileset
"OVSNMPAgent.SUBAGT-HPUNIX".
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, you may
if this Affects You receive this error message during the installation of the OpenView
SNMP bundle.
What To Do
You can ignore this message.
X11MotifDevKit Produces Incompatible Error After

Upgrade from HP-UX 10.20
After updating from HP-UX 10.20 to HP-UX 11i, 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).
Appendix B
161

---
* [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".
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, 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, you need to re-install
the HP-UX 11i Developers Kit located in the HP-UX 11i
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 127
162
Appendix B

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)
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
What To Do
the filesets contained in the product
You can disregard this warning message; there is no problem with the
installation
Appendix B
163

Install Known Problems

MLIBPROD.MLIB Produces Multiple swverify
Warnings and Errors
Problem
After installing or updating to the March 2003 release of HP-UX 11i,

swverify produces numerous errors and warnings for MLIB.
The problem is caused by the removal of MLIB from the TCOE operating
environment and having an older version of MLIB residing on your
system.
How Do You Know If you are migrating from an older version of HP-UX (10.20, 11.0 or older
if This Affects
versions of 11i), and install or update the March 2003 TCOE operating
You?
environment without installing the supplemental HP Math Library (MLIB)
CD, you will see some of the following error messages from swverify:
WARNING: [40257] Directory "/opt/mlib/doc" should have mode "755"
but the actual mode is "555".
WARNING: [40257] Directory "/opt/mlib/include" should have mode
"755" but the actual mode is "555".
WARNING: [40257] Directory "/opt/mlib/lib/pa1.1" should have mode
"755" but the actual mode is "555"
...
ERROR:
[40263] File "/opt/mlib/share/man/man3.Z/auxiliary.3m"
should have mtime "913047122" but the actual mtime is "1022260564".
ERROR:
[40263] File "/opt/mlib/share/man/man3.Z/blas.3m" should
have mtime "913047123" but the actual mtime is "1022260564".
ERROR:
[40263] File "/opt/mlib/share/man/man3.Z/blas2.3m" should
have mtime "913047123" but the actual mtime is "1022260564".
What To Do
Install the the supplemental HP Math Library (MLIB) CD (see Installing

MLIB (TCOE Customers) on page 132) and run swverify again. The
error messages should disappear.
164
Appendix B

System Console "kthread table full" or "fork failed"

Messages
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:
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 to 200:
Step 1. Log on as root

Step 2. Edit /stand/system and add maxusers 200
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:
Appendix B
165

vi /stand/system
Step 2. Delete the line: sflop
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:
166
Appendix B

Update Known Problems

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:
* 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
What To Do
No action required. The ITOAgent unconfigure script generates the error

prior to the file sets being removed.
Appendix B
167

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
A-Class
You?
L-Class
N-Class
Many of the HP-UX 11i firmware patches rely on HP-UX 11i 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 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. Specific HP-UX 11i 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.
168
Appendix B

Update Fails on J2250 Workstation With SCSI Floppy

Drive
See Kernel Build Fails on 64-bit Install on page 165.
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 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:
Appendix B
169

Loading the kernel...
/usr/ccs/bin/ld: Unsatisfied symbols:
wsio_get_service (code)
Stop...
ERROR: The kernel build failed...
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 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.

170
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. Before you install HP-UX 11i, 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
171

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.
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)
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.
172
Appendix B

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 116.
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 182.
Appendix B
173

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 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 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
systems architecture or operating system.
The indicated software (xyz) has not been updated to 11i. To update the
software, mount the HP-UX 11i 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:

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.
174
Appendix B

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
175

Problems Configuring HP-UX 11i

Read these items before installing or updating to 11i.
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
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.
176
Appendix B

Changes to Hardware Diagnostics Monitors

If you are updating from an old version of the hardware diagnostics, the
old monitors for disc30, sdisk and disk array devices will no longer
work.
You may be affected if:
You are using a version of diagnostics earlier than February 1999 (an
STM version lower than A.14.00). To check your version, enter:
/usr/sbin/cstm
The STM version is displayed in the start-up messages. Exit by
entering: quit
AND:
You customized the configuration files for the diaglogd exec

programs (disk30_exec.cfg, sdisk_exec.cfg, and
haraymon_exec.cfg). Check these files by looking in the directory
/var/stm/config/diaglogd_progs/. If the files exist and
monitoring is enabled inside the files, then your system may be
affected.
Do these checks before you update your system to 11i.

After Updating to
11i:
To achieve the same results as with the obsolete monitors, use the EMS
Hardware Monitors on the updated system. See the EMS Hardware
Monitors User's Guide available at:
http://docs.hp.com/hpux/diag/
NOTE
As of the February 1999 release of the hardware diagnostics, there has

been a change to the way monitoring is done for disc30, sdisk and the
HA Disk Array Models 10, 20, and 30FC. Formerly, the diaglogd exec
programs (pdisc30_exec, pharaymon_exec, and psdisk_exec) handled
driver error entries for these devices. As of the February 1999 release,
these programs have been deleted and their functionality is now
provided by the EMS Hardware Monitors.
Appendix B
177

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.
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).
178
Appendix B

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

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
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 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
Appendix B
179

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 hbas
5. Select technical support
This takes you to a page titled "scsi hbas." (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
The content fo 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
180
Appendix B

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.
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
Appendix B
181

Adjusting Required Minimum File System Sizes
Adjusting Required Minimum File System

Sizes
Update Requirements
The absolute minimum /usr file-system sizes needed to update to
HP-UX 11i are listed in Disk Space and Memory Requirements on
page 62 in Chapter 3. 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. See Disk Space and Memory
Requirements on page 62 in Chapter 3.
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:
/sbin/vgdisplay /dev/vg00
You should see output like this:
- Volume groups VG Name
/dev/vg00
VG Write Access
read/write
VG Status
available
182
Appendix B

Max LV
Cur LV
Open LV
Max PV
Cur PV
Act PV
Max PE per PV
VGDA
PE Size (Mbytes)
Total PE
Alloc PE
Free PE
Total PVG
255
8
8
16
1
1
2000
2
4
249
170
79
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
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:
Appendix B
183

/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
In some cases, you will need to increase the size of /stand prior to
completing a successful update to HP-UX 11i. 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, youll 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 Instant Information CD
and on HPs documentation web site:
http://docs.hp.com/hpux/os/11i/oe/
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:
184
Appendix B

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
TYPE
dev
reserve
memory
Kb
AVAIL
307200
85584
Kb
USED
45936
113748
23492
Kb
PCT START/
Kb
FREE USED
LIMIT RESERVE PRI NAME
216208
0%
0
1 /dev/vg00/swap
-113748
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 using the
update-ux command.
Appendix B
185

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
nfile
= 1024 (default is 276)

= 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
sams kernel configuration Actions menu.
Raise maxusers to a large value, such as 200.
Determine the correct configuration for your system.
186
Appendix B

Un-installing HP-UX 11i
Un-installing HP-UX 11i

If you cannot resolve problems after installing or updating to HP-UX 11i,
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 Administration Guide, available on the HP-UX 11i Instant Information CD and
on this web page:
http://docs.hp.com/
If you dont 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 Administration Guide for details.
Appendix B
187

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 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/hpux/onlinedocs/B2355-90699/B2355-90699.html
Help on using install-sd is also on the Software Distributor web site:

http://www.hp.com/products/SD_AT_HP
188
Appendix B

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/
Appendix B
189

Verifying and Adding Diagnostic Drivers
Verifying and Adding Diagnostic Drivers

HP-UX 11i automatically installs Support Tools on all systems to provide
required hardware support. These tools, contained in the OnlineDiag
bundle, give you a complete solution 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 Users Guide, available on the Support
Plus CD in:
/cdrom/DIAGNOSTICS/DIAG_USR.PDF
190
Appendix B

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
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 172.
Restrictions with Netscape Communicator 4.75

The trial version of Netscape Communicator provided with HP-UX 11i
OEs has these problems with several Asian locales, including Japanese,
Korean and Chinese:
Asian-character input is not allowed in several dialogs.
Asian characters are not be displayed properly in some dialogs where

a font switch is not available.
Character-code handling with Perl and Apache

You may encounter the following problems when trying to handle Asian
character-codes with Perl15.005_03 bundled with HP-UX 11i:
In case of Japanese Shift-JIS code and T-Chinese BIG5 code and

S-Chinese GB18030 code, characters containing 0x5c will not be
displayed correctly unless you add the back slash character (\).
In case of EUC-JP code, translation commands such as tr may not

work properly.
Appendix B
191

For example, when you try to convert a double-byte Hiragana
character to a double-byte Katakana character, you may find the
character itself has been changed, not just the type.
What To Do
Get the patch jperl5.005_03 and apply it to Perl. This patch is open
source and available at a number of non-HP FTP sites.
Follow these steps:
Step 1. Get the Perl 5.005_03 source files from: http://devresource.hp.com

Step 2. Download patch jperl5.005_03 from an open-source Perl site.
Step 3. Apply the patch to the source code, and build it.
NOTE
Once patched with jperl5.005_003, Perl cannot be used as Mod_perl

under the Apache server.
192
Appendix B
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
193

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 195).
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
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)
194
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. Youll have
to cold-install 11i on a diskless server, making it a stand-alone
system.
Checks for minimal disk space in /, /stand, /opt, /usr and
/var on a system using LVM.
Removes the no-longer-needed SW-DIST.RUPDATE 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
195

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 systems 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.
196
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
197

update-ux Syntax
198
Appendix C
Configuring Built-In PCI Networking

1000Base-T (Gigabit Ethernet)
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.
Optional Step: Configure Jumbo Frame Size

Step 1. Ensure that all switches in the data path support the jumbo frame size.
Also, make sure that both ends of the connection are using jumbo frames.
Step 2. Obtain the PPA Number of the card by executing:
Appendix D
199

lanscan
Step 3. Set the MTU value to 9000 for jumbo frames by executing:
lanadmin -M 9000
PPA_number
Step 4. To verify MTU change, execute:

netstat -rn.
Step 5. To check the current Ethernet frame size, execute:
lanadmin -m
NOTE
PPA_number
An alternative way to configure the jumbo frame size is to edit the file
/etc/rc.config.d/hpgelanconf (or
/etc/rc.config.d/hpigelanconf). Set the parameter
HP_GELAN/IGELAN_MTU[0]=9000 and insert the proper
HP_GELAN/IGELAN_INTERFACE_NAME. When the system reboots,
the interface will be configured for jumbo frame operation.
200
Appendix D

PCI 10/100Base-TX and 100Base-FX/9000

The following subsections apply to the PCI 10/100Base-TX and
100Base-FX/9000 network cards. The information on the
100Base-FX/9000 (fiber) card is only applicable to the V-class server.
The PCI 10/100Base-TX and 100Base-FX/9000 products interface
various types of HP servers and workstations to either a 10Base-T,
100Base-TX, or 100Base-FX network. The same card port that supports
100Base-TX operation can also support 10Base-T operation.
The category-5 UTP cable used in 100Base-TX networks between devices
such as an HP computer and a 100Base-TX hub must be less than 100
meters long.
For more information on network topologies and associated specifications
for 100Base-TX networking, refer to the IEEE 802.3u specification. Also,
a useful practical reference is Fast Ethernet, Dawn of a New Network by
Howard W. Johnson (published 1996 by Prentice Hall PTR, Upper Saddle
River, New Jersey 07458. Phone 800-382-3419. The ISBN number is
0-13-352643-7).
Compatibility and Installation Requirements

The limits of the current PCI 10/100Base-TX and 100Base-FX/9000 are:
The PCI 10/100Base-TX/9000 card supports autonegotiation and

autosensing. You should not normally need to manually configure the
speed, autonegotiation, or duplex mode of the card. If your switch
does not support autonegotiation but is set to full-duplex mode, there
may be a mismatch between the card and the switch, because the
card defaults to half-duplex for switches that do not support
autonegotiation. You can determine what the card is set to using
lanadmin -x and reset it if necessary using lanadmin -X. See
Manual Speed and Duplex Mode Configuration on page 205 for
details.
By default, autonegotiation is on.
If you manually set the speed and duplex mode of the Base-TX card,
autonegotiation will be turned off.
Appendix D
201

The PCI 100Base-FX (fiber) card operates only at 100Mbits/s

half-duplex mode. The fiber card does not support autonegotiation or
autosensing.
Only the PCI 100Base-TX card supports both full and half-duplex
modes. If your hub or switch does not support autonegotiation,
ensure that your hub or switch is set to the desired duplex mode.
The PCI 10/100Base-TX and 100Base-FX/9000 LAN software is for

use with only the following protocols: TCP/IP, ARPA, and NFS.
When using the ioscan -f command to verify installation, the last

digit of the H/W Path (hardware path) will show the port number of
the card. The other fields of the output will show the driver as btlan,
and the Hardware Type Description will show the product number of
each link card.
The built-in PCI card for workstations has a nettl subsys_id of 173.
The built-in workstation card also uses a dynamic major number.
On the built-in PCI card for workstations, the RJ-45 connector

operates at either 10 or 100 Mbits/s, but the AUI connector operates
only at 10 Mbits/s.
Configuring Network Connectivity

These instructions apply to the PCI 10/100Base-TX and
100Base-FX/9000 cards for the HP V-Class server and the PCI
10/100Base-TX card for HP Workstations. They assume that the PCI
network card has been factory installed and the software already loaded
on your disk. The PCI 10/100Base-TX card operates at both 10Mbits/s
and 100Mbits/s. The Base-TX card supports autonegotiation and
autosensing. The PCI 100Base-FX card operates only at 100Mbits/s,
half-duplex mode only, and the fiber card does not support
autonegotiation or autosensing.
Step 1. Attach the system to the network:
a. Ensure that the system is shut down completely and the power is
OFF. Ensure that the system is grounded.
b. If your Base-TX network uses 8-pin RJ-45 connectors, attach the
RJ-45 plug on your twisted-pair LAN cable into the RJ-45 connector
on the PCI 10/100Base-TX card. The same RJ-45 connector is used
for either 10 or 100 Mbits/s operation.
202
Appendix D

If your network uses BNC connections, attach the LAN cable to the
10 Mbits/s BNC connector.
If your network uses Attachment Unit Interfaces (AUIs), attach your
10 Mbits/s Media Access Unit (MAU) to the AUI connector. Only use
one of the three connectors at a time; disconnect the other two
connectors on the card.
The RJ-45 connection operates at either 10 or 100 Mbits/s, but the

BNC and AUI connections operate only at 10 Mbits/s. Also, the Link
Status LED is for the RJ-45 connector only; the Link Status LED is
dark if the AUI or BNC port is used.
NOTE
For 100 Base-FX (fiber), attach the fiber optic cable to the duplex SC
connector. Cabling can be either 62.5 or 125 micron multimode fiber
optic cable. The operating distances for fiber optic cable for V-Class
systems are:
c.
Node-to-repeater hub: 150 m.
Half-duplex from node to switch or hub: 400 m.
The fiber card does not support full-duplex node.
Attach the free end of the cable to any unused port on the
appropriate hub or switch (or into a wall jack that is connected to a
hub or switch). Connect power cable to system. Set the hub or switch
speed and duplex mode. The PCI 10/100Base-TX card operates in
either full-duplex or half-duplex mode. The Base-TX card
autonegotiates; the fiber card does not. If using the 100Base-FX card,
set the duplex mode manually to half-duplex.
d. Power up the system. When the system is up, any error messages
will appear on the terminal display or system console. You can also
use the dmesg command to retrieve start-up messages later.
e.
If you are using the RJ-45 connector on the PCI 10/100Base-TX or

you are using the 100Base-FX card, verify that the Link LED on the
card is on. The Link LED will remain dark if you are using either the
BNC or AUI connector.
Appendix D
203

Step 2. Configure the card using SAM:
a. Log in as root and verify that the card and its hardware path are
displayed by executing:
ioscan
b. Run the System Administration Manager: sam
c.
Double click Networking and Communications.
d. Double click Network Interface Cards.

e.
Highlight the PCI 10/100Base-TX or 100Base-FX card and choose

Configure from the Actions menu.
f.
Fill in the form according to the instructions.
g.
Click on the OK button to activate the card. Then select Exit from the
File menu until you exit SAM.
Step 3. Verify the installation:

a. Obtain the PPA (on HP-UX 10.20, it is the NMIDnumber) and the
station address of your card by executing:
lanscan
b. To verify that no errors have occurred during installation, enter:
linkloop -i PPA_number station_address
If there is a problem, you can obtain error messages by entering:
dmesg
c.
Verify connectivity with a remote system by entering:

ping remote_IP_address and netstat -in
d. PCI 10/100Base-TX/9000 or 100Base-FX installation is complete

when you have successfully ran these two commands:
linkloop
ping
204
Appendix D

e.
To configure remote systems, see the Using PCI

10/100Base-TX/9000 guide, available on the Instant Information
CD and on the Web at:
http://docs.hp.com/
Do this step only if remote systems have not been previously
configured.
Manual Speed and Duplex Mode Configuration

Because this PCI 10/100Base-TX/9000 LAN card supports
autonegotiation, you should not normally need to manually set the
duplex mode. Sometimes you may need to manually set the duplex mode
of the card, for example, if the switch is operating at full-duplex but does
not autonegotiate. Because the card defaults to half-duplex when
autonegotiation is turned off, this could cause a mismatch between the
card and switch (at either 10 or100 Mbits/s). To fix this, use lanadmin -X
as described later in this section.
The CSMA/CD media access method used in IEEE 802.3u-1995 is
inherently a half-duplex mechanism. That is, at any one time, there can
be only one sender of data on the link segment. It is not possible for
devices on either end of the link segment to transmit simultaneously.
Devices on both ends of a link segment can send data to each other
simultaneously (full-duplex mode). While the details of full-duplex
operation are not currently defined by IEEE 802.3u-1995 (full-duplex
mode essentially involves turning off the CSMA/CD access method
which is the foundation of IEEE 802.3), the autonegotiation mechanism
defined in IEEE 802.3u-1995 allows devices to advertise and configure
themselves to operate in a full-duplex mode which is essentially
vendor-specific. Devices that do not support autonegotiation can
sometimes be manually configured to operate in full-duplex mode.
Full-duplex mode is most-commonly found in either 10 Mbit/s or 100
Mbit/s switches rather than hubs. Full-duplex mode may provide a
throughput advantage under some circumstances, depending upon the
application. The PCI 10/100Base-TX card supports both half- and
full-duplex operation. The fiber card supports only 100 Mbit/s
half-duplex operation.
Appendix D
205

Ensure that the speed, duplex mode, and autonegotiation of the
associated switch are configured the same as on the PCI 10/100Base-TX
card. If the switch supports autonegotiation on the ports connected to the
cards, this should be enabled as explained in Autonegotiation and
Auto-sensing on page 207.
To list the current speed and duplex mode of a PCI 10/100Base-TX/9000
card, use the -x option (lowercase x) in the lanadmin command.
Determine the speed and duplex mode of your hub or switch before
performing manual configuration:
lanadmin -x ppa
To manually set the duplex mode of the interface, enter:
lanadmin -X mode ppa
where: mode can be any one of the following strings (fd or hd are
case-insensitive):
10fd =10 full-duplex
10hd =10 half-duplex
100fd =100 full-duplex
100hd =100 half-duplex
lanadmin -X auto_on ppa turns autonegotiation on.
The ppa is the physical point of attachment on HP-UX 10.30 or 11.0. On
HP-UX 10.20, use the nmid or Network Management ID of the card. You
can get the ppa (nmid) from the output of the lanscan command.
For example, if the ppa (nmid on HP-UX 10.20) of the 100Base-TX
interface is 5, this command sets the card to 10Mbits/s and full-duplex:
lanadmin -X 10fd 5
You must wait at least 11 seconds before attempting to use the specified
network interface.
If you want the Duplex Mode setting to be effective in all subsequent
reboots, you must create a script that includes the appropriate command
in the /sbin/init.d directory so it gets executed on each reboot. Manually
configuring the speed or duplex setting of a switch port on some switches
may disable that switch port from doing autonegotiation. Verify that
both the card and the switch port are operating in the same speed and
duplex mode as desired.
206
Appendix D

If you use manual configuration to change the card to a different speed
and duplex mode, you may need to turn autonegotiation on first before
the manual setting takes place.
NOTE
Mismatches between the speed, autonegotiation, or duplex mode of the

card and switch will cause incorrect operation.
Setting Speed and Duplex Mode at Boot Time (workstation only)

With this method you may set both the speed and duplex mode of the
interface, and have this setting be in effect across subsequent system
reboots.
To access the LAN configuration commands: From the boot console,
select the Configuration Menu and from there select LAN Configuration.
From this menu you can configure and display the current mode of
the10/100 Base-T interface using these commands:
LanConfig Display current configuration settings.
LanConfig 10/Half_dx
Operate in 10 Mbit/s, half-duplex mode.
LanConfig 100/Half_dx Operate in 100 Mbit/s, half-duplex mode.

LanConfig 10/Full_dx
Operate in 10 Mbit/s, full-duplex mode.
LanConfig 100/Full_dx Operate in 100 Mbit/s, full-duplex mode.

LanConfig AUTO_detect (default) Enable auto-negotiation.
If you don't use this method, the system boots up with the default setting
AUTO_Detect.
Autonegotiation and Auto-sensing

Autonegotiation enables devices sharing a link segment to operate at the
optimal mode: 10Base-T or 100Base-TX and half- or full-duplex modes.
If the PCI 10/100Base-TX/9000 card is connected to a device, such as a
switch, that is autonegotiating, the PCI card will autonegotiate with the
device to mutually determine the highest possible speed and duplex
settings.
Appendix D
207

The fiber card (100Base-FX/9000) operates at 100 Mbit/s and in
half-duplex mode only. It does not support autonegotiation or
autosensing.
NOTE
If the PCI 10/100Base-TX/9000 card is connected to a device that does

not support autonegotiation or a device that has autonegotiation disabled,
the PCI card will autosense the speed of the link and set itself accordingly.
The card will be set to half-duplex in this case. If you want the card
to operate in full-duplex mode, you have to set it using the method
described previously in Manual Speed and Duplex Mode Configuration.
The PCI 10/100Base-TX card will sense when the connection between
itself and a hub or switch on the other end of a link has been broken. If a
connection is made to another (or the same) device, the autosensing
process will be done again automatically. Autosensing is also done
whenever the interface is reset.
RJ-45 and AUI Ports

The 10/100 Base-TX link works with both an RJ-45 and (on the V-class)
an AUI port. The RJ-45 port can be used for either 100 Base-T or 10
Base-T networking; the AUI port is used only for 10 Base-T. Only one of
these ports should be connected to a network at any given time. The link
will normally attempt to automatically sense which port is connected
and configure that port, unless this is overridden via the Boot Time LAN
configuration described above.
If the RJ45 port is not connected to the network, the system will
configure itself to use the AUI port during boot-up or reset.
Performance
The 100 Base-T product is initially set with a conservative value for the
transmit threshold (that is, the number of bytes that must be in the
transmit FIFO buffer before transmission can begin). The transmit
threshold is set to a store and forward value. This means that the
entire Ethernet frame must be in the transmit FIFO before transmission
of data onto the wire will begin.
208
Appendix D

The initial transmit threshold value is set to eliminate transmit
underruns (that is, when the transmitter encounters an empty transmit
FIFO during the transmission). However, it can also reduce transmit
performance by not being able to pre-fetch the next packet until the
current frame is completely transferred. This causes a slight delay
between frames, resulting in an overall drop in transmit performance.
The transmit threshold value is adjustable. Adjusting the threshold to
either 1024 or 512 bytes can increase performance. If the transmit
threshold is 1024 or 512, the CORE 100 Base-T interface will start
transmitting data onto the wire after 1024 or 512 bytes are in the
transmit FIFO. This allows the CORE 100 Base-T hardware to start
pre-fetching the next frame in the transmit FIFO before the current
frame is completely transmitted. This results in less time between
subsequent frames and therefore increases the transmit performance.
Setting the
The CORE 100 Base-T product supports three levels of transmit
transmit threshold threshold. These three levels are modified via lanadmin:
lanadmin -S transmit_threshold PPA
where:
transmit_threshold of 512 is most aggressive.
transmit_threshold of 1024 is somewhat aggressive.
transmit_threshold of 1500 is conservative.
After issuing lanadmin -S, you must wait at least 8 seconds before
attempting to use the specified network interface.
If you want the transmit threshold setting to be effective in all
subsequent reboots, you must create an SD script and include the
command in the /sbin/init.d directory so it gets executed on each reboot.
CAUTION
Be careful when adjusting the transmit threshold. While lowering the

threshold may increase performance, it also makes the CORE 100
Base-T interface more susceptible to Transmit Underrun errors.
A large number of transmit underrun errors (more than 1 out of every

1000 packets) may cause a noticeable drop in networking performance.
The performance drop will depend on the application being used.
Applications that send data in a continuous stream (FTP, for example)
Appendix D
209

may have a more noticeable drop in performance (when more than 1 out
of every 1000 packets have errors) than applications which are
request-response in nature (NFS, for example).
Transmit underrun errors may occur on some HP systems when there is
sufficient bus contention from competing I/O devices on the system I/O
bus. These errors can be monitored in two ways:
1. Examine the output from the netstat -I command. If the number of
output errors is high (more than 1 out of every 1000 packets), then
the system is most likely suffering from transmit underruns on the
specified network interface, and corrective action must be taken to
resolve the problem.
2. Turn on nettl errors and warnings for the network interface being
monitored. The following command will turn on disasters, errors and
warnings for the network interface with Instance number 1:
nettl -log 0xe -e base100 -C 1
NOTE
Be sure to keep nettl disaster and error logging enabled at all times.
Check the nettl log file /var/adm/nettl.LOG00 for the following message:
HP CORE 10/100BASE-T driver encountered a Transmit Underflow
If a significant number of these messages occur and the timestamps for

each of the messages are within 30 seconds of each other, the specified
networking interface will suffer a noticeable performance drop.
Corrective action must be taken to resolve this problem.
What Happens During Card Initialization Sequence?
Following is an overview of the initialization sequence for the PCI
10/100Base-TX and (for V-Class servers) the 100Base-FX cards.
Initialization of a PCI 10/100Base-TX or 100Base-FX card happens
during system bootup only, and it is driven by the btlan driver for the
card. Whenever initialization fails, it prints a message on the console
identifying the failure. You can later retrieve initialization messages
after the system is fully booted up by using the dmesg command. Finally,
the driver tries to establish a good data link between the card and the
hub or switch.
210
Appendix D

The Link Status LED is for the RJ-45 connector only. The link LED is lit
only when the RJ-45 connector on the card is connected properly to a
10/100 Mbit/s switch or hub.When the RJ-45 cable connection is used,
the link LED must be lit to indicate proper functioning. If there is no
RJ-45 cable connection, or if the cable connection is bad, or if the hub or
switch is not compatible, that is, not 10Base-T or 100Base-TX capable, no
LEDS will be lit. Also, a message indicating the detection of a bad cable
connection is printed on the console as well as logged in NETTL logs.
The Link LED functions as follows:
LED solid green = link established in 100Base-TX mode.
LED solid yellow = link established in 10Base-T mode.
LED remains dark in 10Base2 (BNC) or 10Base5 (AUI) mode. The

Status LED is dark if the AUI or BNC port is used.
The Activity LED flashes whenever the switch is sending link pulses. If
the activity LED on the card is not blinking, then there may be a problem
with the driver or the card. Contact HP.
NOTE
The RJ-45 connection operates at either 10 or 100 Mbits/s, but the BNC
and AUI connections operate only at 10 Mbits/s.
V-Class PCI 10/100Base-TX Card Specifications

Physical:
Dimensions (A3738A): 5.839 x 4.78 inches.
Dimensions (A5172A): 5.075 x 3.9 inches. (PCI short card

specification).
Power requirement: +5 Volts @ 0.5 Amps max.

Environmental: (degrees F = (1.8 x degrees C) + 32)
Operating temperature: 5 degreesC to 50 degreesC.
Humidity: 5 to 85% non-condensing.
Altitude: 3000 m.
Appendix D
211

Electromagnetic:
FCC Class A: USA, Canada, and Latin America.
CISPR-22 Class A, EN55022 Class A: Europe.
Cable Interfaces:
The 10-Mbit/s twisted-pair port is compatible with IEEE

802.3u-1995 Type 10Base-T. Cat 5 UTP.
The 100-Mbit/s twisted-pair port is compatible with IEEE

802.3u-1995 standard. Cat 5 UTP.
The fiber card uses one-pair multimode fiber cable with duplex SC
connectors.
Cable Distances: (HP A5172A Fiber Card)
Node-to-switch cable distance up to 412 m in half duplex mode.
Node-to-repeater cable distance up to 137 m in half duplex mode

only.
Line speed is 100 Mbits/s half-duplex.
Communications Standards:
IEEE 802.3u-1995 Type 10Base-T (10Mbit/s).
IEEE 802.3u-1995 standard for Base-TX and FX (100-Mbit/s)
Hardware Regulatory Statements

This section contains hardware regulatory statements for the V-Class
PCI 100Base-TX product (A3738A) and 100Base-FX product (A5172A)
use in the United States, Canada, and the European community. Refer to
your PCI 10/100Base-TX 9000 Quick Install card for product installation
instructions.
212
Appendix D

FCC Statement (for U.S.A.)
Federal Communications Commission Radio Frequency
Interference Statement
WARNING
This device complies with Part 15 of the FCC rules. Operation is

subject to the following two conditions:
(1) This device may not cause harmful interference and
(2) this device must accept any interference received, including
interference that might cause undesired operation.
This equipment has been tested and found to comply with the
limits for a Class A digital device, pursuant to Part 15 of the FCC
rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in
a commercial environment. This equipment generates, uses and
can radiate radio frequency energy, and, if not installed and
used in accordance with the instruction manual, may cause
harmful interference to radio communications.
Operation of this equipment in a residential area is likely to
cause interference, in which case the user at his own expense
will be required to take whatever measures may be required to
correct the interference.
Hewlett-Packards system certification tests were conducted
with HP-supported peripheral devices and cables, such as those
received with your system. Changes or modifications to this
equipment not expressly approved by Hewlett-Packard could
void the users authority to operate the equipment.
Canada
WARNING
This Class A digital apparatus meets all requirements of the

Canadian Interference-Causing Equipment Regulations.
Cet appareil numrique de la classe A respecte toutes les
exigences du rglement sur le matriel brouilleur du Canada.
Appendix D
213

EMI and LED Safety (European Community)
NOTE
This is a class A product. In a domestic environment, this product may

cause radio interference, in which case you may be required to take
adequate measures.
LED Safety - European Union - Optical Transceiver (A5172A

only)
NOTE
This optical transceiver meets LED AEL Class 1 requirements per EN

60825-1:1994(+A11) and EN 60825-2:1994.
214
Appendix D
Index
Symbols
/etc, 82
/etc/passwd, 98, 99
/home, 98, 99
/home, restoring, 99
/local, 99
/opt, 62, 82, 99
disk space, 63
/opt/ifor/ls/bin, 136
/stand, 62
increasing, 184
/usr, 62, 99
disk space, 63
/usr/local, 82
/usr/sbin, 113
/var, 62, 95
increasing size, 182
/var/opt/ifor, 136
Numerics
100BT HSC-FT card
not supported on 11i, 179
32-bit OS
changing from 64-bit OS, 34
3D Graphics, 33, 48
64-bit OS
considerations, 34
update example, 119
updating to, 34
A
A-Class, 49
adapters
PCI Requirements, 61
adding
groups, 141
OE, 116
patches, 134
users, 141
Additional Considerations, 30
administration
file system, 140
analyzing log files, 168
Apache
character-code handling w/ Perl, 191
updating an existing version, 31
application
releases, 142
applications, 84
changing OE apps, 70
configuring after update, 107

LicensePower/iFOR, 136
updating, 131
verifying install, 126
AUI port, 208
autoboot
halting, 146
autonegotiation, 207
autosensing, 207
B
backup, 79, 80, 108
make_net_recovery, 108
make_tape_recovery, 108
Base OE, 115
B-Class
B1000, 49
B2000, 49
before updating
rebuild kernel, 83
before you begin, 88
updating, 102
boot
verifying firmware, 57
boot device types, 92
boot information
newer Series 800, 149, 150
older Series 700, 148
older Series 800, 150
Superdome, 36
built-in PCI networking, 140
bundles
OnlineDiag, 75
C
C3700 workstations, 47
C-Class
C3000, 49
C3600, 49
changes
to hardware monitors, 177
changing file system size, 182
Next Steps, 42
cleaning log files, 106
cold-install
considerations, 36
Golden Images, 37
Instant Ignition, 36
215
Index
Software Depot, 37
Deciding a Method, 29
definition, 21
How To, 91
kernel build fails, 165
Netscape Directory Server, 32
next steps, 98
create new root, 98
recover files, 99
restore /home, 99
restore /local, 99
restore /opt, 99
restore /usr, 99
retrieve information, 98
preparing, 78, 81
process, 89
saving key information, 81
troubleshooting, 165
typical problems, 165
verify install, 99
vs. update, 28, 63
cold-installing
advanced installation, 92
alternate methods, 37
flowchart, 90
guided installation, 92
install wizard, 92
required CDs, 91
required software bundles, 95
typical time, 91
commands, 108
i4admin, 136
ioscan, 110, 112, 132
make_net_recovery, 108
mk_kernel, 106
mount, 111, 112, 132
sam, 110
script, 106
set_parms, 140
swcopy, 111
swinstall, 103, 106, 112, 119, 120, 131
swlist, 106, 108, 124, 126, 131
swremove, 117, 134
swverify, 124, 126
tail, 106
update-ux, 101, 103, 104, 106, 109, 111, 112,
113, 115, 134
v3tov4, 136
216
configuration, 140
adding groups, 141
adding users, 141
Built-in PCI Networking, 140
LAN, 140
networking, 140
OE Applications, 107
peripherals, 141
printers, 141
tasks, 141
configuration files
save before cold-install, 82
configuring built-in PCI card, 202
configuring HP-UX 11i
problems, 176
considerations
64-bit OS, 34
additional, 30
cold-install, 36
Golden Images, 37
Software Depots, 37
update, 33
corrupt system
recovering, 189
create depot, 110
create new root
after cold-install, 98
critical patches, 129
installing, 134
Custom Patch Manager, 128
custom patches, 142
D
Deciding
Method to HP-UX 11i, 28
Deciding a Method
cold-install, 29
update, 30
depots
creating, 110
managing with SD, 135
determine your disk needs, 76
diagnostics
bundle, 75
changes to hardware monitors, 177
overview, 75
verifying and adding, 190
Web pages, 75
Index
web site, 75
diagnostics subsystem
not installed, 190
disk space
/opt, 63
/usr, 63
planning, 76
requirements, 62
usage errors, 173
documentation
Disk and File Management Tasks, 76
for planning disk space, 76
Managing HP-UX Software with SD-UX,
125
patches, 129
downgrading OE, 117
download
firmware, 58
downloading
patches, 128
drivers
updating, 120
updating network, 31
E
Enterprise OE, 115
error codes
with update-ux, 109
error messages, 172
error recovery, update-ux, 172
errors
disk space usage, 173
disk-space usage, 173
I/O, 173
multiple I/O, 173
post-update verify, 174
root vol. locked, 174
swinstall, 174
update/install, 172
update-ux, 109
examples
adding OE, 116
downgrading OE, 117
update from network depot, 117
update NDS, 119
update selectable software, 120
update to 64-bit OS, 119
update using Interactive Software
Selection, 118
update using match_target, 117
update-ux, 114
updating 11i OE, 115
upgrading OE, 116
F
Fast Boot, enable, 91
fbackup, 79
file system
administration, 140
LVM, 140
NFS, 141
VxVM, 140
file system size, adjusting, 182
firmware
applying patches, 59
download updgrades, 58
minimum requirements, 49
requirements
L-Class, 49
requirements table, 50
upgrade, 49
B-Class, 49
C-Class, 49
J-Class, 49
L-Class, 49
N-Class, 49
verifying, 54, 55
from boot display, 57
firmware patches
downloading, 58
installing, 59, 129
firmware upgrade
A-Class, 49
floppy drives
update problems, 178
flowchart
update process, 105
frecover, 79
G
General Release patch bundle, 38
GigEther-01
OLA/R, 48
GOLDAPPS11i patch bundle, 38
GOLDBASE11i patch bundle, 38
Golden Images, 84
installing from, 37
groups
adding, 141
217
Index
H
halting autoboot, 146
hardware monitors
changes, 177
How To
Apply Firmware Patches, 59
cold-install, 91
Identify OS, 46
Identify Software, 46
Identify System Model, 46
plan disk space needs, 76
prepare your system, 78
update, 109
update using interactive Software
Selection, 118
verify application installation, 126
Verify Firmware Version, 54, 55, 57
verify installation, 124
HP-UX 11i
100BT HSC-FT card supported, 179
64-bit OS considerations, 34
cold-install, 91
deciding when, 29
cold-installing, 91
configuration problems, 176
considerations, 30, 33, 36
Deciding which method, 28
default OS bundles, 194
Golden Images, 37
maintaining, 142
migrating from older releases, 26
Migration Path, 23
migration paths, 26
Minimal Computing Operating
Environment, 69
OLA/R support, 179
Other Resources, 24
patch bundles, 38
preparing your system, 78
proactive maintenance, 144
reactive maintenance, 143
rebuilding kernel, 83
rebuilding kernel before updating, 106
release version, 46
Requirements, 44
security patches, 129
Software Depots, 37
support media, 142
Support Plus, 129
218
Supported Systems, 44
Technical Computing Operating
Environment, 69
un-installing, 187
Unsupported Systems, 47
update
deciding when, 30
update (no OE), 116
update procedure, 113
update to 64-bit OS, 119
updating, 101, 109
verify install, 99
verifying install, 124
Web resources, 24
HWEnable11i patch bundle, 38
I
I/O errors, 173
i4admin, 136
Identifying
Model, 46
OS, 46
Software, 46
iFor/LicensePower
uninstalling, 137
Ignite-UX, 79, 80, 84, 108, 135
updating the server, 74
VxVM, 36
increasing /stand, 184
increasing /var, 182
install kernel
autobooting (S800), 149
booting (s700), 147
stopping autoboot (S800), 149
installing
critical patches, 134
verify, 99
installing from
Golden Images, 37
Software Depots, 37
install-sd, 188
Instant Ignition
installing from, 36
interactive mode
updating with, 118
Interactive Software Selection, 118
ioscan, 110, 112, 132
ITRC, 128, 129, 142
Index
J
J6700 workstations, 47
J-Class
J5000, 49
J5600, 49
J6000, 49
J6700, 47
K
kernel, 83, 106
NTPY Parameter, 169
rebuilding, 83, 106
L
LAN
configuring, 140
large systems, 186
last-minute install/update issues, 64
L-Class, 49
LicensePower/iFOR
updating, 136
locales
problems with non-C, 191
locate media, 84
log files
cleaning, 83, 106
LVM, 140
vs. VxVM, 77
M
maintaining
HP-UX 11i, 142
make_net_recovery, 79, 80, 108
make_tape_recovery, 79, 80, 95
match_target, 117
using, 118
MCOE, 115
media
locating, 84
support, 142
memory
requirements, 62
migration flowchart, 23
Migration Paths, 26
from previous HP-UX releases, 26
Next Steps, 42
to HP-UX 11i, 23

Environment, 69
minimum memory requirements, 62
Mission Critical OE
Support, 27
mk_kernel, 106
monitoring update, 106
mount, 111, 112, 132
MTOE, 115
multiple I/O errors, 173
N
N-Class, 49
upgrading firmware, 49
NDS
updating, 32, 119
Netscape Directory Server
considerations, 32
updating, 32, 119
Netscape, restrictions, 191
network depot, 110
update example, 117
networking
configuring, 140
configuring built-in PCI, 140
configuring LAN, 140
NFS, 141
updating drivers, 31
networking data
save before cold-install, 81
Next Steps
Choosing a Migration Path, 42
Cold-Installing HP-UX 11i, 98
Preparing to Move to HP-UX 11i, 85
System Requirements, 65
NFS, 141
NTPY, 169
O
OEs
adding, 116
Base OE, 115
bundle names, 115
changing applications, 70
configuring applications, 107
downgrading, 117
Enterprise OE, 115
MCOE, 115
MTOE, 115
TCOE, 115
219
Index
updating, 101
OLA/R
support, 48, 179
Older HP-UX Releases
Migrating to HP-UX 11i, 26
OnlineDiagnostics
Operating Environment
Environment, 69
operating environments
adding, 116
Base OE, 115
configuring applications, 107
downgrading, 117
Enterprise OE, 115
locate media, 84
MCOE, 115
Environment, 69
Mission Critical OE, 27
TCOE, 115
updating, 101, 115
upgrading, 116
operating envronments
MTOE, 115
OS
un-installing, 187
updating, 101
Other Resources, 24
Overview, 17
Other Resources, 24
Purpose of this book, 18
Supported Paths, 21
overview
diagnostics, 75
updating, 103
P
parameters
NTPY, 169
PA-RISC
3D Graphics, 33, 48
Determining Version, 33, 48
patch bundles
available bundles, 38
GOLDAPPS11i, 38
GOLDBASE11i, 38
HWEnable11i, 38
patches
220
adding, 134
applying firmware, 59
critical, 134
custom bundles, 142
downloading individual, 128
firmware, 58
HP-UX security bulletins, 129
installed, 134
LicencePower/iFOR, 136
management tools, 129
removing, 134
resources, 128, 129
Support Plus, 129
PCI
configuring built-in networking, 140
PCI Adapters
Requirements, 61
PCI card
configuring, 202
initialization sequence, 210
setting speed and mode, 207
specifications, 201
peripherals
configuring, 141
Perl, character-code handling w/ Apache, 191
planning
disk space, 76
post-install
verify, 99
post-install tasks, 98, 99
preparing
clean out log files, 83
locate media, 84
rebuild kernel, 83
record software versions, 83
to cold-install, 81
to update, 82
preparing your system, 78
printers
configuring, 141
proactive maintenance, 144
problems
configuring HP-UX 11i, 176
floppy drives, 178
non-C locales, 191
update, 107, 169
X.25 cards not supported, 170
process
update, 103
Index
Purpose of this book, 18
Q
Quality Pack patch bundle, 38
quarterly releases, 142
quickstart, 103
R
reactive software maintenance, 143
rebuild kernel, 83, 106
before updating, 83
rebuilding kernel, 83, 106
record software versions, 83, 106
recover, 79
recover files
recovering
corrupt system, 189
recovering a corrupt system, 189
re-installing SD, 188
release version, 46
releases, 142
removing
patches
update-ux, 134
Requirements, 44
Next Steps, 65
requirements
CDs for cold-install, 91
to update, 62
resources
patches, 128
Support Plus, 129
restore
/home, 99
/local, 99
/opt, 99
/usr, 99
retrieving information
RJ-45 port, 208
root, 62
root directory
creating a new, 98
root disk
minimum size, 62
rootability
VxVM, 36, 77
S
sam, 82, 110
script, 106
SCSI
OLA/R, 48
SD
managing depots, 135
re-installing, 188
tools, 135
using, 135
security
patches, 129
selectable software
updating, 120
selected locale not availavble, 173
servers
A-Class, 49
L-Class, 49
N-Class, 49
requirements, 62
supported systems, 44
unsupported systems, 47
set_parms, 96, 140
size
adjusting file system, 182
software
record versions, 83, 106
updating selectable software, 120
software depot, 103
Software Depots
installing from, 37
Software Distributor, 135
Software Distributor Administration Guide,
134
Software Selection
interactive mode, 118
Software Transition Kit, 26
source media
locating, 84
steps
update drivers, 120
verifying update, 120
STK, 129
Web, 24
Superdome
booting patitions, 36
installing HP-UX, 36
Support
OLA/R, 48
support, 75
221
Index
media, 142
Mission Critical OE, 27
Support Plus, 84, 142
patch bundles, 38
services, 129
Web, 24
supported migration paths, 26
Supported Paths
to HP-UX 11i, 21
supported systems, 44, 46
swcopy, 111
swinstall, 82, 103, 106, 112, 119, 131
errors, 174
updating drivers, 120
swlist, 106, 108, 124, 126, 131
swremove, 117, 134
swverify, 108, 124, 126
system
backup, 79, 80
preparing to install, 78
preparing to update, 82
system backup
fbackup, 108
make_net_recover, 108
system configuration, 140
system firmware
minimum requirements, 49
PCI I/O card and boot device support, 52
System Requirements, 44
/opt, 63
/usr, 63
3D Graphics, 33, 48
C3700 workstations need upgrade, 47
Disk Space, 62
firmware, 49
J6700 workstations need upgrade, 47
Memory Requirements, 62
Next Steps, 65
OLA/R, 48
PA-RISC, 33, 48
Supported Systems, 44
verifying firmware, 54, 55, 57
System Requirments
PCI Adapters, 61
T
Table
Firmware Requirements, 50
tail, 106
222
tasks
cleaning log files, 83
configuration, 141
post-install, 98, 99
preparing to cold-install, 81
preparing to update, 82
rebuild kernel, 83
TCOE, 115
Environment, 69
tips
updating, 83, 106
verify update, 108
tools
SD, 135
troubleshooting
large systems, 186
update, 109
troubleshooting installs/updates, 172
U
uninstalling
iFor/LicensePower, 137
un-installing HP-UX 11i, 187
Unsupported Systems, 47
update
64-bit OS, 34
applications, 131
considerations, 33
definition, 21
error codes, 109
examples
adding OE, 116
from network depot, 117
NDS, 119
selectable software, 120
to 64-bit OS, 119
upgrading OE, 116
using match_target, 117
flowchart, 105
from a network depot, 117
How To, 109
LicensePower/iFOR, 136
NDS, 32, 119
Index
network drivers, 31
NPTY parameter failure, 169
operating environments, 101
OS, 101
OS without OE, 116
overview, 103
preparing, 78, 82
problem with floppy drives, 178
problems, 107
selected locale not available, 173
software depot, 103
steps
create network depot, 110
installing update-ux, 111
update drivers, 120
using update-ux, 113
verify update, 120
swcopy, 111
tips, 83, 106
all software not updated, 107
backup system, 108
clean log files, 106
configuration, 107
monitor process, 106
rebuild kernel, 106
record software versions, 106
verify, 108
to 64-bit OS, 34
to an 11i OE, 115
to HP-UX 11i, 113
troubleshooting, 109, 172
update-ux command, 113
vs. cold-install, 28
X.25 cards not supported, 170
update process
all software doesnt get updated, 108
flowchart, 105
monitoring, 106
recording software versions, 83, 106
running other commands, 107
update-ux, 82, 101, 103, 104, 106, 109, 112
analyzing log files, 168
command syntax, 113
do not use -i and -x together, 118
error codes, 109
errors, 109
examples, 114
downgrading OE, 117
from network depot, 117
install using swinstall, 112

installing, 111
match_target option, 117
multiple I/O errors, 173
overview, 195
preliminary checks, 195
problems, 169
update 11i OE, 115
update drivers, 120
using, 113
updating
Ignite-UX server, 74
NDS, 119
requirements, 62
upgrading
C3700 workstations, 47
firmware, 58
J6700 workstations, 47
N-Class systems, 49
usage errors
disk space, 173
users
adding, 141
using
SD, 135
V
v3tov4, 136
verify
application install, 126
HP-UX installation, 124
update, 120
verify update, 108
VERITAS
rootability, 36, 77
Version
PA-RISC, 33, 48
VxVM, 140
rootability, 36, 77
vs. LVM, 77
W
web
patches, 128, 129
web access
Ignite-UX, 74
223
Index
Software Distributor Administration
Guide, 134
Web resources, 24
workstations
B-Class, 49
C3700, 47
C-Class, 49
J5000, 49
J6000, 49
J6700, 47
J7000, 49
requirements, 62
supported systems, 44
unsupported systems, 47
X
X.25 cards, 170
224

11i Installation and Upgrade PDF

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

11i Installation and Upgrade PDF

Enviado por

Direitos autorais:

Formatos disponíveis

HP-UX 11i Installation and Update Guide

HP Servers and Workstations

Manufacturing Part Number : 5187-2239

First Edition: December 2000 B2355-90703,

Second Edition: June 2001,

Third Edition: September 2001,

Fourth Edition: March 2002,

Fifth Edition: June 2002, 5187-0161,

Sixth Edition: September 2002,

Seventh Edition: December 2002,

Eighth Edition: March 2003,

About this Guide

Words defined for the first time appear in boldface.

Computer font indicates literal and system items

Bold, computer text indicates literal items that you

Manual titles, variable in commands and emphasized

Brackets [] enclose optional items in command syntax.

Text in this bold, sans-serif font denotes keyboard keys

2. Choosing a Migration Path

3. Install/Update System Requirements

4. Preparing To Move To HP-UX 11i

5. Cold Installing HP-UX 11i

6. Updating to HP-UX 11i

7. Verifying System Migration

A. Booting HP Servers and Workstations

B. Known Problems and Troubleshooting

C. Using the update-ux Tool

D. Configuring Built-In PCI Networking

What You Will Find In This Book on page 19 provides a summary

Supported Paths to HP-UX 11i on page 21 provides a high-level

Other Resources on page 24 lists other HP documentation and

The Purpose of this Book

Be sure to review this entire guide and the Known Problems

What You Will Find In This Book

Chapter 2, Choosing a Migration Path, on page 25 provides

Chapter 3, Install/Update System Requirements, on page 43 details

Chapter 4, Preparing To Move To HP-UX 11i, on page 67 details the

Chapter 5, Cold Installing HP-UX 11i, on page 87 shows you how to

Chapter 6, Updating to HP-UX 11i, on page 101 shows you how to

Chapter 7, Verifying System Migration, on page 123 shows you how

Chapter 8, Updating Applications, on page 127 shows you how to

Chapter 9, Next Steps, on page 139 provides you an overview of

Appendix A, Booting HP Servers and Workstations, on page 145

Appendix B, Known Problems and Troubleshooting, on page 155

Appendix C, Using the update-ux Tool, on page 193 provides a brief

Appendix D, Configuring Built-In PCI Networking, on page 199

Supported Paths to HP-UX 11i

Cold-install HP-UX 11i This method overwrites everything on

Update using update-ux Use the update-ux command when

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

HP-UX 11i Migration Overview

1. Prepare Your System

Read Chapter 2 to determine path

2. Cold -Install HP-UX 11i

3. Update to HP-UX 11i

4. Verify the Migration

5. Update Other Applications

HP-UX 11i Migration Overview

HP-UX 11i Release Notes - available on the Instant Information

Read Before Installing or Updating to HP-UX 11i - contains

HP IT Resource Center - download the latest patches and patch

HP Workstation and Server Information - find out about the

Ignite-UX - for information and downloads see: