Ignite-LUX: Management and Integration of Ignite-UX Software on a Server Running Linux

24
Client-Specific config Content
Typically, CMS software will provide a method for controlling deployment content and configuration for a
specific client system. These CMS user interface or policy choices must be converted to Ignite-UX config file
content to control installation or recovery.
The config file in the client-specific directory is used to control client-specific installation or recovery
details. Ignite-UX defaults will be used for client-specific config content that is not specified. The following
config content shows some of the most commonly used settings:
# cat /var/opt/ignite/clients/0x001083049436/config
cfg "HP-UX B.11.31 Default"=TRUE
_ip_cfg_detail_levels="ivsp"
init _hp_root_disk="WWID='0x5000c50005e33057'"
The cfg Ignite-UX keyword specifies the INDEX file configuration clause to be installed. Valid values can
be obtained by listing configuration clauses using the ignite or manage_index commands.
The _ip_cfg_detail_levels variable must be set to indicate what config content is specified in the
client-specific config file. Ignite-UX software will use this value to help decide what configuration information
comes from standard config files and what comes from client-specific content. The Ignite-UX
instl_adm(4) man page should be consulted for further details.
The _hp_root_disk variable indicates the disk to use as the HP-UX installation target device. If not
specified, Ignite-UX will choose a disk using a default selection method. Typically, users prefer to explicitly
indicate which disk to use. The Ignite-UX instl_adm(4) man page details the parameters that may be
used for selection. The io.info inventory data file lists the client’s disks.
Initiating Client Installation or Recovery
Once all Ignite-UX server, CMS-general, and client-specific config files are set up, the Ignite-UX server is
ready to support client installation.
If the non-interactive installation approach is used, installation may be initiated by network-booting the client
system to use the Ignite-UX server.
The following command may be used to initiate server-controlled installation.
# ignite client control –x action=start_install 0x001083049436
In this example, the client system is identified using its MAC Address.
Warning: It is possible to interrupt a non-interactive or server controlled installation to make client system
configuration modifications via the Ignite-UX user interface. CMS software should be designed to
appropriately handle this interruption if possible.
Client Installation Progress
It is common for CMS software to report progress on operations that take a long time, such as HP-UX
installation and recovery. The following command may be used to monitor install progress.
# ignite client list -m xml -l status <mac address>