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

23
Regardless of how the system is to be booted, it is necessary to boot the Ignite-UX install environment to
accomplish installation or recovery. This might include management of DHCP PXE bootp from the Linux
server – this is intentionally not handled by Ignite-LUX.
Per-release AUTO files in the Ignite-LUX package are set up to automatically initiate server controlled
installation. They also have entries for automated installation for the specific HP-UX release that do not wait
for the server, and entries for manual installation for all supported HP-UX releases. These manual installation
menu entries help you avoid issues such as when an administrator needs to install a specific HP-UX release
but does not have administrative privileges on the Ignite-UX server to modify the AUTO file. In this situation,
the administator can interrupt the boot process and select the correct HP-UX release for boot.
Booting the correct install kernel requires the use of the correct DHCP PXE boot file path. In this example an
HP UEFI dbprofile is used to show the set of expected DHCP PXE response values:
Shell> dbprofile
Profile Name: iuxserv31
Network Type: IPv4
Client IP address: 15.1.48.199
Gateway IP address: 15.1.48.1
Subnet Mask: 255.255.248.0
Server IP address: 15.1.53.172
Boot File: /opt/ignite/boot/Rel_B.11.31/nbp.efi
Optional Data:
An HP UEFI directed boot using a dbprofile may be used for testing to see if the Ignite-UX server is
correctly set up.
Boot paths for a specific release are set up for server controlled installation. Upon boot, the client system
will start the install environment and will wait for the server to instruct the client to proceed. You can use this
to discover clients by having the CMS software use Ignite-UX client status and inventory data.
General CMS config Content
It might be useful for CMS software to provide an Ignite-UX config file that includes CMS-specific content
appropriate for all client systems. The config file could be included in all INDEX file cfg clauses. For
example:
cfg "HP-UX B.11.31 Custom Config" {
description "User-Supplied 11.31 Config"
"/opt/ignite/data/Rel_B.11.31/config"
"/opt/ignite/data/Rel_B.11.31/hw_patches_cfg"
"/var/opt/ignite/data/CMS_cfg"
"/var/opt/ignite/data/config.local"
}
In this case, the CMS-specific config file /var/opt/ignite/data/CMS_cfg will be included in the
config file list.
Hewlett-Packard does not recommend using CMS software to automatically “fix” user-created INDEX file
configuration clauses to include the CMS-specific config file. Instead, it might be more appropriate to limit
the list of available configuration clauses presented in CMS user interfaces to those that include the required
config file.