Starting an Automatic Installation with bootsys

Using a "Saved" Configuration

When using Ignite-UX during an install session, you may choose to save the result as a named configuration when finished specifying the configuration for particular target. This will save any changes that you made during the session for use in subsequent sessions. Then either specify the configuration as the default, and/or just use the name you give it to bootsys using the -i option.

Specifying Defaults in the config.local File

The /var/opt/ignite/config.local file is normally included in every cfg clause in the INDEX file. This provides a convenient location to store default parameters that are the same for all configurations. Typically this will be networking, default software selections, kernel modifications.

It may be easiest to cut and paste information written to the files /var/opt/ignite/clients/*/config by the user interface. However you can do more here than with the Ignite-UX screen. See the instl_adm(4) manpage for more details. Below is an example of what a config.local file could look like. The sw_sel's will depend on what you have defined in config files on the server.

dns_domain="fc.hp.com"
dns_nameserver[0] = "15.2.72.2" 
nis_domain="udl"
wait_for_nis_server=FALSE 
root_password="rlW2xSrugUvi2" 
timezone="MST7MDT" 
ntpdate_server="15.1.48.11"
init sw_sel "Misc_Patches"=TRUE
init sw_sel "B3919DA_AGP"=TRUE
mod_kernel += "maxuprc 100" 
mod_kernel += "dbc_max_pct 80"

Always run this after making manual edits to verify that the syntax is correct:

instl_adm -T

“Setting Install Parameters Dynamically” to see how default information may be specified dynamically depending on the target system's configuration.

Setting defaults with instl_adm

Some network parameters need to be known by the target clients when they first boot. bootsys or DHCP/BOOTP can supply the hostname and IP address; however, the netmask and gateway need to be supplied in the RAM filesystem (INSTALLFS). This can done by using the instl_adm command, which has options to set netmask, gateway, Ignite-UX/tftp server, etc. Or you can dump the current settings to a file and edit it, then load the settings back. Just loading Ignite-UX sets some of the parameters.For example, you may want to set the keyboard language so that it never prompts you for it when booting from Ignite-UX. The file you store using instl_adm -f may look like this:

# instl_adm defaults: 
server="15.2.72.150"
route_gateway[0]="15.2.70.1"
route_destination[0]="default"
netmask[]="255.255.248.0"
# end instl_adm defaults.
kbdlang="PS2_DIN_US_English"

Using the per-target client config file

Until now, we have discussed specifying default parameters that all target systems may use. If you would like to specify a specific configuration for an individual target system, you may use the following procedure.

When Ignite-UX begins an install session, it scans the directory /var/opt/ignite/clients for a directory matching the LLA of the target system. As an example, if the LLA of the target is 0x08000992E346, Ignite-UX looks for a file named config in:
/var/opt/ignite/clients/0x08000992E346/config

Ignite-UX keeps the last configuration installed to the respective system in this file so it can perform a repeat install.

If found, the configuration data in this file is used to overwrite the default values. This file has the highest precedence over all other config files listed in the INDEX file.

	CAUTION: Ignite-UX will write over this file at the end of the install, so you may want to keep an original copy elsewhere.

The easiest way to create the config file is to use one already built by Ignite-UX. If you've previously installed a system (it's best to use one from a similar system to your target,) you can find a config file in the /var/opt/ignite/clients/LLA directories. Use this as the basis for your new file. Copy it to: /var/opt/ignite/clients/LLA/config

Edit its contents to correspond to your new system.

Example config Ffle

Here is an example config file:

cfg "HP-UX B.11.00 archive"=TRUE 
_hp_cfg_detail_level="ipvs"
#
# Variable assignments
# init _hp_disk_layout="Whole disk (not LVM) with HFS"
init _hp_pri_swap=68304K
init _hp_root_disk="2/0/1.5.0"
init _hp_sec_swap=0K 
init _hp_root_grp_disks=1 
init _hp_root_grp_striped="NO"
init_hp_locale="SET_NULL_LOCALE"
init_hp_keyboard="PS2_DIN_US_English"
init _hp_default_final_lan_dev="lan0" 
init _hp_boot_dev_path="2/0/1.6.0" 
# 
# Software Selections
# init sw_sel "golden image"=TRUE
init sw_sel "English"=TRUE
# 
# System/Networking Parameters
# hp_custom_sys+={"Current System Parameters", "Original Defaults"} 
init _hp_custom_sys="Current System Parameters"
_hp_custom_sys help_text "Final System/Networking Parameters"
(_hp_custom_sys=="Current System Parameters")
{
final system_name="hpfcnjm2"
final ip_addr["lan0"]="15.2.75.14" 
final netmask["lan0"]="255.255.248.0"
final dns_domain="fc.hp.com"
final dns_nameserver[0]="15.2.72.254" TIMEZONE="MST7MDT" 
is_net_info_temporary=TRUE
} 
# end "Current System Parameters"

Typically, you would want to change the networking parameters to the correct values. For example:

final system_name="system11"
final ip_addr["lan0"]="15.2.75.193"

The values specified should be self explanatory, and should be edited to the desired new values. It is also possible to add kernel parameters to this file. See “Setting Install Parameters Dynamically” later in this chapter.

You should also update the variable, _hp_cfg_detail_level when adding new types of parameters or they will get lost by the UI or by the file rewrite.

To perform an automatic install with a config file: