This document describes the most common procedure for setting up an Ignite-UX server, adding
a client to the Ignite-UX server, and cold-installing HP-UX on that client.
Glossary terms are italicized when used for the first time in this manual.
Intended Audience
This document is intended for system and network administrators with minimal experience
installing, configuring, and managing HP-UX. Administrators are expected to have knowledge
of operating system concepts, but not in-depth knowledge of HP-UX or Ignite-UX. It is helpful
to have knowledge of Transmission Control Protocol/Internet Protocol (TCP/IP) networking
concepts and network configuration.
Typographic Conventions
This document uses the following typographical conventions:
#
audit(5)A manpage. The manpage name is audit, and it is located in Section 5.
Command
Computer output
KeyThe name of a keyboard key. Return and Enter both refer to the same
TermAn important word or phrase defined in the glossary.
User input
Variable
CAUTIONA caution calls attention to important information that if not understood
A number sign represents the superuser prompt.
A command name or qualified command phrase.
Text displayed by the computer.
key.
Commands and other text that you type.
The name of a placeholder in a command, function, or other syntax
display that you replace with an actual value.
or followed will result in data loss, data corruption, or damage to
hardware or software.
Related Information
The most current edition of this and the following documents are found at the HP Technical
Documentation website at:
http://www.docs.hp.com/
Related Documents
•Ignite-UX Administration Guide
•Ignite-UX Reference
•Ignite-UX Custom Configuration Files
•Successful System Cloning using Ignite-UX White Paper
•Successful System Recovery using Ignite-UX White Paper
•Installing and Updating Ignite-UX White Paper
•Ignite-UX Installation Booting White Paper
•Read Before Installing or Updating to HP-UX
•HP-UX Installation and Update Guide
•HP-UX Release Notes
•HP-UX Reference
Intended Audience5
•HP-UX System Administrator’s Guide
•Managing Systems and Workgroups: A Guide for HP-UX System Administrators
•Software Distributor Administration Guide
•HP-UX Patch Management
•nPartition Administrator's Guide
•Getting Started with Software Package Builder
•VERITAS File System 4.1 (HP OnlineJFS/JFS) and VERITAS Volume Manager 4.1 Installation
Guide
Some or all of these documents are available on the Instant Information media and in printed
form.
Publishing History
The document printing date and part number indicate the document’s current edition. The
printing date will change when a new edition is printed. Minor changes might be made at reprint
without changing the printing date. The document part number will change when extensive
changes are made. Document updates might be issued between editions to correct errors or
document product changes. To ensure you receive the updated or new editions, you should
subscribe to the appropriate product support service. See your HP sales representative for details.
You can find the latest version of this document on line at
http://www.docs.hp.com.
Manufacturing Part Number
Systems
HP Encourages Your Comments
HP encourages your comments concerning this document. We are committed to providing
documentation that meets your needs. Send any errors found, suggestions for improvement, or
compliments to:
http://www.docs.hp.com/en/feedback.html
Include the document title, manufacturing part number, and any comment, error found, or
suggestion for improvement you have concerning this document.
Publication DateEdition NumberSupported Operating
September, 20084HP-UX 11i v1, v2, and v35992–5230
June, 20083HP-UX 11i v1, v2, and v35992–4815
March, 20082HP-UX 11i v1, v2, and v35992–3879
September, 20071HP-UX 11i v1, v2, and v35992-0678
6
1 Setting up an Ignite-UX Server
This chapter describes setting up an Ignite-UX server to cold install HP-UX 11i v1, v2, and v3 on
clients over the network. You must have superuser privileges to set up an Ignite-UX server. You
can stop anywhere in this procedure and resume where you left off at a later time.
This document assumes the network boot clients are on the same subnet as the Ignite-UX server.
This document also assumes the network DHCP and DNS servers are already set up. These
network services are vital to Ignite-UX server operation. If the Ignite-UX server is intended to
support these network functions on an isolated subnet, the user should consult documentation
that indicates how to set them up. Network services should be set up before the Ignite-UX server
is set up. See http://www.docs.hp.com for networking documentation.
Make Sure Your System Meets Ignite-UX Server Requirements
1.Make sure the version of HP-UX running on the Ignite-UX server system matches the HP-UX
version on the operating environment (OE) DVD set you are getting the Ignite-UX software
from. Use the uname -r command to query the HP-UX revision on the server system. The
uname command will report the release identifier, which can be mapped to the HP-UX
release as follows: B.11.31 is HP-UX 11i v3, B.11.23 is 11i v2, and B.11.11 is 11i v1.
Procedure
# uname -r
B.11.23
Common Errors
sh: typo: not found.
Diagnosis: Mistyped “uname”
Correction: Retype command.
uname: illegal option – R
usage: uname [-amnrsvil] [-S nodename]
Diagnosis: Used a capital R instead of a lowercase r.
Correction: Reissue the uname command with a lowercase r.
Explore
See uname(1) by issuing the command
# man uname
If you require a version of Ignite-UX that can be installed onto any supported version of HP-UX, please read
the section about downloading Ignite-UX from the HP Software Depot website in the Ignite-UX AdministrationGuide, available at http://www.docs.hp.com/en/IUX/infolib.html.
2.Use the bdf command to make sure you have at least 2 GB of free disk space available in
/opt to support installation of all three HP-UX releases.
Procedure
# bdf /opt
Common Errors
Make Sure Your System Meets Ignite-UX Server Requirements7
Detection: The number of kbytes free on /opt is less than 2000000.
Diagnosis: Not enough space.
Correction: Extend the size of the logical volume with the lvextend command, and then extend the size of the
file system within the logical volume with the extendfs command. Detailed instructions for this procedure
are found in the HP-UX administration guides listed below, depending on your version of HP-UX.
For HP-UX 11i v3, see the HP-UX System Administrator's Guide (volume 3): Logical Volume Management. Within
this guide, look for the chapter on administering LVM, and then the section on extending a file system.
For HP-UX 11i v2 and earlier versions, see Managing Systems and Workgroups. Within this guide, look for the
chapter on managing disks and files, and then the section on extending the size of a file system within a logical
volume.
Both administration guides are available at http://www.docs.hp.com.
Explore
See bdf(1M) by issuing the command
# man bdf
See lvextend(1M).
See extendfs(1M).
See fsadm(1M)
3.Use the bdf command to make sure you have enough disk space in /var to hold the OE
depots. You will need roughly 4.5 GB per DVD in the OE set.
Procedure
# bdf /var
Common Errors
Detection: The number of kbytes free on /var is less than 9 GB for a two-DVD OE set.
Diagnosis: Not enough space.
Correction: Extend the size of the logical volume with the lvextend command, and then the size of the file
system within the logical volume with the extendfs command. Detailed instructions for this procedure are
found in the HP-UX administration guides listed below, depending on your version of HP-UX.
For HP-UX 11i v3, see the HP-UX System Administrator's Guide (volume 3): Logical Volume Management. Within
this guide, look for the chapter on administering LVM, and then the section on extending a file system.
For HP-UX 11i v2 and earlier versions, see Managing Systems and Workgroups. Within this guide, look for the
chapter on managing disks and files, and then the section on extending the size of a file system within a logical
volume.
Both administration guides are available at http://www.docs.hp.com
Explore
Consider making room in /var/opt/ignite for recovery archives, golden images, and software depots. Estimate
approximately 4 GB per recovery and golden image archive. See the section on Ignite-UX server requirements
in the Ignite-UX Administration Guide at http://docs.hp.com/en/IUX/infolib.html. For information on how to do
this, see the HP-UX administration guides listed below, depending on your version of HP-UX.
For HP-UX 11i v3, see the HP-UX System Administrator's Guide (volume 3): Logical Volume Management. Within
this guide, look for the chapter on administering LVM, and then the section on extending a file system.
For HP-UX 11i v2 and earlier versions, see Managing Systems and Workgroups. Within this guide, look for the
chapter on managing disks and files, and then the section on extending the size of a file system within a logical
volume.
Both administration guides are available at http://www.docs.hp.com
8Setting up an Ignite-UX Server
Consider creating a new file system for /var/opt/ignite. This could keep Ignite-UX from impacting other
applications using /var if it fills /var/opt/ignite with depots and archives. Detailed instructions for this
procedure are found in the HP-UX administration guides listed below, depending on your version of HP-UX.
If you do create a file system for /var/opt/ignite, then you will see it in the bdf listing and will be able
to manage your disk space to a greater level of detail.
For HP-UX 11i v3, see the HP-UX System Administrator's Guide (volume 3): Logical Volume Management. Within
this guide, look for the chapter on administering LVM, and then the section on creating a file system.
For HP-UX 11i v2 and earlier versions, see Managing Systems and Workgroups. Within this guide, look for the
chapter on managing disks and files, and then the section on creating a file system.
Both administration guides are available at http://www.docs.hp.com
See newfs(1M).
See lvcreate(1M).
Install the Ignite-UX Software and the HP-UX OE Depot on the Server
1.Gain access to the DVD drive on your system. This document assumes the DVD-ROM device
is called /dev/dsk/c1t2d0 – substitute your actual device name throughout this document.
Procedure
a. Use the ioscan command to get the DVD-ROM device name, for example: /dev/dsk/c1t2d0. You are
looking for DVD in the Description column of the ioscan output.
# ioscan -fnkC disk | more
b. Create the device directory:
# mkdir /dvdrom
c. Put the OE DVD in the drive and mount it onto the new directory as a file system. Note that you must
unmount the DVD-ROM with the # umount /dvdrom command before you can extract it from the drive.
# mount /dev/dsk/c1t2d0 /dvdrom
Common Errors
/dev/rdsk/cntndn is an invalid operand
Diagnosis: The /dev/rdsk device file was used instead of the /dev/dsk device file.
Correction: Reissue the mount command with the /dev/dsk device file.
/dev/dsk/cntndn: unrecognized file system
Diagnosis: The device file name was mistyped.
Correction: Check that the device file was entered correctly.
/dev/dsk/cntndn: I/O error
Diagnosis: The DVD isn't in the drive.
Correction: Insert the OE DVD into the drive.
mount: /dev/dsk/cntndn was either ignored or not found in /etc/fstab
Diagnosis:The mount directory, /dvdrom, was omitted from the mount command.
Correction: Reissue the mount command with the mount directory.
Install the Ignite-UX Software and the HP-UX OE Depot on the Server9
The ioscan command lists no devices.
Diagnosis: If the system is running HP-UX 11i v3, the system might have legacy mode disabled. To find out,
issue the following command.
# insf -Lv
Correction: If legacy mode is disabled, issue the following command to get the DVD-ROM device name (add
an “N” to the ioscan command options). Do not enable legacy mode without talking to the system
administrator responsible for the Ignite-UX server.
# ioscan -fNnkC disk | more
Explore
You can navigate the output of the more command, including the ioscan -C disk -f -n -k | more
command above, with the following shortcuts:
• space – Scroll down one page of the listing.
• j – Scroll down one line of the listing.
• k – Scroll up one line of the listing.
• q – Quit.
See ioscan(1M).
See mkdir(1).
See mount(2).
See mount(1M) by issuing the command
# man 1M mount
2.Make sure you are installing a later version of Ignite-UX on the system.
Procedure
a. Get the version of Ignite-UX currently installed on the server, if it is already installed:
# swlist Ignite-UX
b. Get the version of Ignite-UX from the OE DVD:
# swlist -s /dvdrom | grep Ignite-UX
Common Errors
ERROR: Software “Ignite-UX” was not found on host “system_name:/”.
Diagnosis: Depending on the command you issued, Ignite-UX is not currently installed on the server or it's
not on the DVD currently in the drive.
Correction: If Ignite-UX is not installed on the server, continue to the next step. If Ignite-UX is not on the DVD,
replace the DVD with another in the media set. Remember to unmount the current DVD in order to extract it
from the drive.
ERROR: The expected depot or root does not exist at “/dvdrom”.
ERROR: There is currently no depot software on host “hostname” at location “/dvdrom”. Make sure that
an absolute pathname is specified for location (beginning with “/”).
Diagnosis: The DVD is no longer mounted at /dvdrom or you have typed the wrong directory name.
Correction: Check for typos. You can use bdf to check the name of the DVD mount point. If the DVD is not
mounted, mount it as described in the previous step.
Explore
For an overview on getting and installing Ignite-UX, see the Ignite-UX Administration Guide available at http://
www.docs.hp.com/en/IUX/infolib.html. For detailed information, see the white paper Installing and Updating
Ignite-UX, available at http://www.docs.hp.com/en/IUX/infolib.html.
10Setting up an Ignite-UX Server
3.Install the Ignite-UX software using swinstall if the Ignite-UX version on the DVD is later
than any currently installed version of Ignite-UX and the HP-UX version on the OE media
matches the HP-UX version on the Ignite-UX server.
Procedure
# swinstall -s /dvdrom Ignite-UX
Common Errors
ERROR: Could not apply the software selection “Ignite-UX”; it is not available from depot or root
“server_name:/dvdrom”.
Diagnosis: The DVD in the drive does not have Ignite-UX on it.
Correction: Unmount the DVD drive with this command:
# umount /dvdrom
Put in another OE DVD and mount it as in step 1c. Then use the swinstall command again.
ERROR: “server_name:/” 19 filesets have a version with a higher revision number already installed.
Diagnosis: A higher version of Ignite-UX is already installed on the server system.
Correction: Proceed to the next step.
Explore
You can list all the software bundles on the DVD with
# swlist -s /dvdrom
4.Unmount the DVD so you can extract it from the drive.
In this case, the shell attempting to run unmount had /dvdrom as its current working directory, and
changing to another directory would allow the DVD to be unmounted.
5.Create the HP-UX OE depot, named core_media, by running make_depots on each of the
HP-UX OE DVDs. In this example we are using HP-UX 11i v2, but this process can easily
be customized for any HP-UX release by substituting your release information for the HP-UX
11i v2 information. The make_depots command takes a long time to complete. When
make_depots completes without errors, no messages are printed to the screen – all messages
are printed to the /var/opt/ignite/depots/Rel_B.11.23/swagent.log file
Install the Ignite-UX Software and the HP-UX OE Depot on the Server11
(substitute your release directory if it's different from 11.23). If the make_depots command
returns quickly with no errors, the depot already exists on the system.
Procedure
Run the make_depots command below for all DVDs in the OE set. Remember to substitute your device file
name and the appropriate release directory (Rel_B.11.xx) for your version of HP-UX.
The depot will be put in the /var/opt/ignite/depots/Rel_B.11.23 directory and will be named
core_media.
This process is described fully in the section on installation configurations using Software Distributor (SD-UX)
depots in the Ignite-UX Custom Configuration Files web-only document, available at http://docs.hp.com/en/IUX/
infolib.html.
The depot we're creating is called core_media in order to distinguish it from other depots of the same HP-UX
version. (All depots of the same version are kept in the appropriate Rel_B.xx.xx directory.) Consider naming
depots with names that indicate what release of HP-UX the depot contains. This will make the depots easier
to identify. For instance, if you are creating a depot for the December 2007 HP-UX 11i v2 Mission Critical OE
release, you could name the depot core_0712_mc.
Create the HP-UX OE Configuration Information on the Ignite-UX Server
1.Create the configuration file, named core_media_cfg, to describe this HP-UX OE depot,
named core_media. In this example we are using HP-UX 11i v2, but this process can easily
be customized for any HP-UX release by substituting your release information for the HP-UX
11i v2 information.
If you want more than one configuration available for a version of HP-UX, such as 11i v2
June, 2008 and 11i v2 December, 2007, then each configuration must have a unique name
for the configuration file created with make_config in this step and the configuration
clause created and modified by manage_index in Step 2.
If you wish, you may safely complete the section “Configure the System as an Ignite-UX
Correction: Check the make_config command line for typos.
Explore
List the /var/opt/ignite/data/Rel_B.11.23 directory to see the core_media_cfg file just created
with the make_config command.
Configuration files are typically named after the depot, with a _cfg appended.
This process is described fully in the section on creating the configuration file to describe the depot in the
Ignite-UX Custom Configuration Files web-only document, available at http://docs.hp.com/en/IUX/infolib.html.
2.Add the configuration information to the Ignite-UX /var/opt/ignite/INDEX file. First,
the default B.11.23 configuration clause is copied to a new clause called “B.11.23 From OE
Media”, and then the core_media_cfg file we created in step 1 is added to the “B.11.23
From OE Media” clause.
If you want more than one configuration available for a version of HP-UX, such as 11i v2
June, 2008 and 11i v2 December, 2007, then each configuration must have a unique name
for the configuration file created with make_config in Step 1 and the configuration clause
created and modified by manage_index in this step.
NOTE: Cannot access index file /var/opt/ignite/INDEX: No such file or directory.
ERROR: Couldn't accomplish the requested operation.
Diagnosis: The /var/opt/ignite/INDEX file is missing or mistyped.
Correction: Check for typos. Otherwise, list the /var/opt/ignite directory to see if the INDEX file is there
under another name. Check with a systems administrator responsible for the Ignite-UX server to find the
correct INDEX file.
Explore
This process is described fully in the section on creating a minimalist cfg clause for installation in the Ignite-UX
Custom Configuration Files web-only document, available at http://docs.hp.com/en/IUX/infolib.html.
View the description of the “B.11.23 From OE Media” configuration clause to see that it is the same as the
default clause we copied, “HP-UX B.11.23 Default”. Note that when no INDEX file is specified, the manage_index
command defaults to /var/opt/ignite/INDEX.
# manage_index -x -c "B.11.23 From OE Media"
Change the description to something that makes sense to you.