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

Warning: If a client installation or recovery fails, Ignite-UX might return to the Waiting_To_Install

phase to get instructions from the server on how to proceed.

The Ignite-UX ignite command provides a user interface that uses more understandable phase names

than the ones listed above. However, we recommend you do not attempt to provide a similar mapping with

CMS software. Any improvement is minimal compared to the risk of a broken CMS integration because of

future Ignite-UX changes.

Client-Specific File: config

The config file is used to specify the installation configuration settings supplied by CMS software that are

client-specific. It might include the INDEX configuration clause to be used, the root disk, and any other

Ignite-UX config content (see instl_adm(4)).

cfg "HP-UX B.11.31 Default"=TRUE

_ip_cfg_detail_levels="ivsp"

init _hp_root_disk="WWID='0x5000c50005e33057'"

Note: The Ignite-UX _hp_cfg_detail_level variable indicates the type of config content in the file.

This variable allows Ignite-UX to optimize config content processing. You should consult instl_adm(4)

for details regarding correct values.

Client-Specific File: config.sys

At the phase Prepare_Config_File Complete, this is the config file content that will be used for

installation. Prior to that phase, the file may be used to hold partial and temporary config file content.

Client-Specific File: env.vars

At the phase Prepare_Config_File Complete, this file holds environment variable values. Prior to

that phase, the file may be used to hold partial and temporary environment variable values.

# cat env.vars

SOURCE=10.3.1.2

SOURCE_TYPE=NET

NET_STATUS=UP

TERM=unknown

INST_CLIENT_DIR=/var/opt/ignite/clients/0x001083049436

INST_LOG_FILE=/var/opt/ignite/clients/0x001083049436/install.log

INST_SERVER_MOUNTED=1

TZ=MST7MDT

INST_ALLOW_WARNINGS=5