An HP-UX 10.20 cold install can be made from two different
sources.
You can also choose to load only the Install Kernel from the
installation media and then load the Core OS bundles and products
from a network source. This would be especially useful for a Series
800 system, which does not support booting over a network at this
time.
Setting Up the Network Install Source |
 |
A "network cold install" uses another machine on the network
as its installation source. Once this is set up, a network install
is the fastest installation method. Complete network cold
installs can be performed on a Series 700 system only,
but you can use either a Series 700 or Series 800 as the install
server. After an install server is set up on your network, you can
boot new systems from the server, and once booted, the installation
process is similar to installing from physical media.
Requirements for a network install server are:
HP-UX 10.20 on the server system. See “Hardware Requirements ”, in this chapter.
Your server must be on the same network subnet as
the system that will be booted. This may require having one server
on each subnet from which to boot clients.
You must have the HPUX-Install
product or NetInstall bundle loaded on the
server. If HPUX-Install
is not installed on your server, you must load it from the 10.20
Core-OS media using the swinstall
command. You can obtain the HPUX-Install
product by loading the entire NetInstall
bundle from the Core-OS media.
You will need about 21 MB of free space in the server
/usr/lib directory
to accommodate HPUX-INSTALL.
You must edit the file /etc/instl_boottab
on the server and add at least one IP address that is reserved for
booting install clients. The IP addresses you add should be for
cold installs only and should not be used by any other systems.
However, if you know the LAN Link Addresses (LLA) of the systems
you will be installing, you can use the IP addresses of those systems,
providing you append the keyword "reserve". See the examples in
the file /etc/instl_boottab
for more guidance.
If you want to boot multiple systems from the server
at the same time, you must add more than one IP address to this
file. The server may deny boot services if multiple systems try
to use the same IP address during booting.
Optional Install Server Configuration Steps
After your install server is set up, you may want to create
some default parameters to make the process easier. Running the
instl_adm command
on the server can do this.
For example:
Use instl_adm(1M)
to set the default SD-UX server and depot as in the following command
line (where sd_server is replaced by
the hostname of the swinstall server, and /var/hpux_depot
is the location of its software depot):
instl_adm -s sd_server:/var/hpux_depot |
You can also create a message that can be displayed to users
during the installation.
For example:
The instl_adm -a
option can be given a filename that contains the message or, if
given a "—" (dash) as shown below, the command will prompt
you to type in the message followed by Ctrl-D
"end-of-file". Adding the -d
option will cause the command to display the default information
after making the changes, as follows:
The instl_adm(1M)
utility can also allow the advanced user to set up enough information
to completely automate the installation. This is done by specifying
configuration information as listed in the instl_adm(4)
man page.
For examples of install configuration files, see Appendix A “Sample Configuration File ”, in this manual.
For general information, see the online information on the
install program in /usr/share/doc/10.20RelNotes.
For more details on setting up a network server, see the comments
in the /etc/instl_boottab
file, and the instl_bootd(1M) man page
If you have problems in booting systems, look in the file
/var/adm/syslog/syslog.log
for error messages which will tell you whether more IP addresses
are needed.
For more details on depots and the swinstall
command, see the manual Managing HP-UX Software with
SD-UX.
Information on HP Software Deport
See the HP Information website, www.hp.com
(Business and Technical Computing: Documentation) for additional
HP-UX documentation.
Printable version
