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

install kernel booted on the client. We assume these config clauses have been previously set up by an

administrator.

The following Ignite-LUX command will list all available client configurations. The XML output shows

available config clauses plus information about each clause, including the HP-UX release.

# ignite config list –m xml

Alternatively, the Ignite-LUX package includes the Ignite-UX manage_index command, which can be used

to list the set of INDEX and client-specific CINDEX configuration clauses available for HP-UX installation. The

manage_index –r option may be used to constrain the list to those appropriate for the install kernel that

will be booted for installation or recovery. For example, to list the configuration clauses in the INDEX file for

HP-UX 11i v3, use the following command.

# manage_index –lr B.11.31

Client-specific configuration clauses are stored in a CINDEX file in the client directory. Listing these entries is

not currently supported by the Ignite-LUX ignite command. The manage_index command may be used

to list configuration clauses in a CINDEX file. For example:

# manage_index –lr B.11.31 –i /var/opt/ignite/clients/hpuxsys1/CINDEX

Appropriate clauses in either the INDEX or CINDEX file may be used for installation.

Listing Clients Known to an Ignite-UX Server

The Ignite-UX server maintains knowledge of client systems that have been previously installed, are currently

being installed, or are waiting for server controlled installation.

The CMS software will need to keep track of what client systems are being managed by the Ignite-UX server

for HP-UX deployment. Use the following command to list clients. The summary and detail levels can be

used to determine the current status of clients.

# ignite client list –m xml –l summary

Client status information might also be available in the client files within client-specific directories at

/var/opt/ignite/clients. A directory for each uniquely identified client system is created on the

Ignite-UX server via NFS. Symbolic links are created in the /var/opt/ignite/clients directory using

other client system identifiers. For example:

# ls -l /var/opt/ignite/clients/ | grep 000E7FED52C5

drwxr-xr-x 3 bin bi 8192 Mar 19 02:13 0x000E7FED52C5

lrwxrwxrwx 1 bin bin 14 Mar 19 01:50 hpuxsys1 -> 0x000E7FED52C5

Network Boot for Automated Installation or Recovery

You might want to use the CMS software to automate booting. This is sometimes called “automated

redeployment” and “cold dead iron provisioning.” You can also elect to have the initial system boot for

install occur outside CMS control (for example, via manual operation).

The Ignite-LUX package does not include the Ignite-UX bootsys command. That Ignite-UX server command

requires the client system to have HP-UX already installed and running. Often it is not reasonable to assume

the client system is already running HP-UX. Also, many CMS solutions provide a separate method for client

system power and boot control, so a consistent method is used regardless of the status of the client system.

The Ignite-UX Administration Guide provides considerable detail regarding alternatives for client boot and

Ignite-UX startup.