Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
Installing and Updating Hardware Extensions (HWE)for HP-UX 10.20 (April 1999): HP 9000 Computers

Appendix A Sample Configuration File

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The HP-UX cold-install process is driven by information stored in configuration files. There are three primary locations where a network cold-install can find configuration file information on the server:

  1. In the area accessed by the instl_adm(1M) tool. This information is immediately available to clients when they boot. The data stored in this location is limited to 8 KB.

  2. In the file /usr/lib/sw/hpux.install/config.local. This information is available after the client enables networking. It does not have a fixed size limit.

  3. The file /usr/lib/sw/hpux.install/config is where the default configuration information that comes with HP-UX is stored.

Please see the instl_adm(1M) and instl_adm(4) manual pages for more details.

The following set of examples may be useful when saved to a file, and then installed using the instl_adm -f file command:

# Set the default netmask and gateway for all clients
# (can also be set using instl_adm with -m & -g options)

netmask = "255.255.248.0"
gateway = "15.1.48.1"

# Set the default install/tftp server:

server = "15.1.54.114"

# Set the default hostname, IP address and disk to use as the
# root disk for the system matching the lan-link address shown:
LLA_ADDR == "08000941C3BD" {
system_name = "swig"
ip_addr = "15.1.54.104"
best = disk[52.2.0]
}

# Specify the networking information for another system, and also
# specify that the installation should be done non-interactively:

LLA_ADDR == "08000978BBBB" {
system_name = "swbba"
ip_addr = "15.1.54.138"
RUN_UI = FALSE
# Give users 10 seconds to respond to warnings before
# continuing with the automatic installation:
env_vars +="INST_ALLOW_WARNINGS=10"
}

This example can be added to the /usr/lib/sw/hpux.install/config.local file. It does not have the same 8 KB restriction as the examples above.

# Specify the possible SD-UX servers and depot locations.  This example
# also shows how to use the "use model" variables to provide a
# selector that the user will see during the install:
radio_sel {
[ "Depot Server:.*" ]
}
"Depot Server:Jupiter" {
sd_depot_dir = "/depot/hp-ux_700"
sd_server = "15.1.54.112" # Jupiter
}
"Depot Server:Orion (CD-ROM)" {
sd_depot_dir = "/SD_CDROM" #depot on CD-ROM
sd_server = "15.1.54.20" # Orion
}
# For systems matching these lan-link addresses, specify that
# they execute the shown post_config_cmd. This particular
# post_config_cmd will copy over some extra files and some files
# that are specific for each system using tar(1) and remsh(1).
# The result depends on what is copied over, but if the files
# consist of the /etc/rc.config.d/netconf and other configuration
# files, the system will boot up without the need for further
# manual configuration.
LLA_ADDR == "08000978BBBB" | LLA_ADDR == "08000941C3BD"
{
post_config_cmd="
cd /;
remsh 15.1.54.114 \"(tar -cf - -C /sdux/systemenvs/generic . \
-C /sdux/systemenvs/`hostname` .)\" | tar -xvf -;
swinstall -s 15.1.54.112:/languages/depot XDB;
# If a RUN_ME file was copied over, run it:
[ -x /RUN_ME ] & /RUN_ME"
}

# Define a whole-system level use model for a system, and
# make it the default for that system (note that this is
# the same system that was configured to do an automatic
# install in the previous section).
init "SYS:Custom config for swbba" = (LLA_ADDR == "08000978BBBB")
"SYS:Custom config for swbba" {
init "Software Selection:Runtime Environment" = true
init "Software Language:Japanese" = true
init "Disk Layout:Logical Volume Manager" = true
# Load the ASX bundle from a different depot during the
# post config phase (in addition to other post_config_cmd).
post_config_cmd += "
swinstall -s 15.1.54.112:/asx B3782CA_ABJ"
# For LVM configurations, adjust the volume size
# for /var and create a /extra volume:
"Disk Layout:Logical Volume Manager" {
volume_group "vg00"
{
logical_volume {
mount_point = "/var"
usage = HFS
size = 100Mb
nbpi = 2048
"File system file name length:Short" {
file_length=short
}
}
logical_volume {
mount_point = "/extra"
usage = HFS
size = remaining
}
}
}
}
# Define a new software selection that will appear along with
# with other software selections. Note that the software language
# specification will be ignored when this is selected.

"Software Selection:Software config for our office."
help_text "This is a custom software selection that selects only what
our office needs. (Desktop, ANSI-C, and our own software)"
"Software Selection:Software config for our office." {
sd_software_list = "
Product_Name
Product_Number
OurSW
"
}

When a system is installed, the configuration that was selected for that system is stored in the /usr/lib/sw/hpux.install/config.local file. A system that is configured as a network cold-install server will provide its own configuration to its clients as an option from which the user can select.

It is also possible to concatenate another system's config.local file to that of the server's in order to have multiple configurations available to clients. Alternatively, the config.local file may be hand-crafted (as shown in the previous example) to make slight modifications to the default configuration.

rcp system1:/usr/lib/sw/hpux.install/config.local /tmp/cfg1
cat /tmp/cfg1 >> /usr/lib/sw/hpux.install/config.local

rcp system2:/usr/lib/sw/hpux.install/config.local /tmp/cfg2
cat /tmp/cfg2 >> /usr/lib/sw/hpux.install/config.local

Then run the instl_adm command to test the configuration syntax before proceeding:

               instl_adm -T
Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1999 Hewlett-Packard Development Company, L.P.