When Ignite-UX begins an installation session,
it scans the directory /var/opt/ignite/clients for a directory matching the MAC address of
the client. For example, if the MAC address of the client is 0x08000992E346, Ignite-UX looks for a file named config in /var/opt/ignite/clients/0x08000992E346. However, to enable you to find clients easily Ignite-UX also creates
a symbolic link between the client’s name and the MAC address.
If the client has more than one LAN interface, the MAC address of
each interface is used until a matching directory is found.
Ignite-UX overwrites this client-specific config
file at the end of the installation, creating a record of the parameters
defined for this client’s most recent installation.
The configuration data in this file is used to
override the default installation parameters. For more information
regarding configuration files, see “Using Configuration Files”.
The easiest way to create a client-specific custom
configuration file is to start with one of the default files provided
by Ignite-UX. However, if you have previously installed a client,
you can start with a configuration file in the /var/opt/ignite/clients/client directories. It is best to use one
from a client similar to the one you want to install. You could use
this as the basis for your new configuration file.
The following is an example configuration file:
 |
cfg "HP-UX B.11.11 archive"=TRUE
#
# setting _hp_cfg_detail_level to ipvs indicates that the file
# contains information about which cfg INDEX selection to be used,
# the variable settings, software selection settings, and system
# parameters.
_hp_cfg_detail_level="ipvs"
#
# Variable assignments
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 "English"=TRUE
#
# System/Networking Parameters
init _hp_custom_sys="Current System Parameters"
_hp_custom_sys help_text "Final System/Networking Parameters"
{
final system_name="server"
final ip_addr["lan0"]="10.2.75.14"
final netmask["lan0"]="255.255.248.0"
final dns_domain="xx.corp.com"
final dns_nameserver[0]="10.2.72.254"
TIMEZONE="MST7MDT"
is_net_info_temporary=TRUE
} |
|
To customize this configuration file, change the
final networking parameters in the example file to the correct values
for your client. For example:
final system_name="system11"
final ip_addr["lan0"]="10.2.75.193" |
It is also possible to add kernel parameters to this file. See “Setting Installation Parameters Dynamically”.
|
| |
|
 | IMPORTANT: You should update the variable _hp_cfg_detail_level to reflect the parameters that you have modified to indicate that
they should be used by Ignite-UX; by default this variable is set
to ipvs. This variable is fully described
in instl_adm(4). |
|
| |
|
To perform an automatic installation of a client
using a custom configuration file, execute the following steps on
your Ignite-UX server:
Determine
the MAC address of the client, either through the boot_admin commands at boot time or by using lanscan(1M) after the client is booted.
For more information, see boot(1M), efi(4), isl(1M), and pdc(1M).
Create
the following directory, assuming the MAC address is 0x08000992E346:
mkdir /var/opt/ignite/clients/0x08000992E346
Copy
an example configuration file to be used as a starting point:
cp config /var/opt/ignite/clients/0x08000992E346/config
These
files are accessed using NFS so you must ensure that the correct ownership
and directory access permissions are assigned.
Set the client directory to 644 and change the ownership to ensure
that bin can read and write to the directory:
chmod 644 /var/opt/ignite/clients/0x08000992E346
chown bin:bin /var/opt/ignite/clients/0x08000992E346
chown bin:bin /var/opt/ignite/clients/0x08000992E346/config
Edit
your new configuration file to define your client-specific information.
Run bootsys on the Ignite-UX server to begin the installation:
bootsys -a -v client_hostname
The client is booted and the operating system
is installed without interaction using the client-specific configuration
file you created. Errors are reported in /var/opt/ignite/clients/0x08000992E346/install.log and in the client status dialog box (see “Client Status... Dialog Box”) in the Ignite-UX GUI on the Ignite-UX
server.
Printable version
