Ignite-LUX: Management and Integration of Ignite-UX Software on a Server Running Linux
7
Client Console Configuration
Integrity EFI supports administrator interaction using any console when multiple console interfaces are
enabled. Many OS’s also support this capability. The HP-UX OS only supports the one console configured
as the primary interface. If you are using another console to boot the client system, it might look like the HP-
UX kernel has hung during boot. The HP-UX boot loader writes a message to all consoles prior to the HP-UX
OS boot regarding the issue. If the message stays on the screen, switch to the correct console and consider
if another interface should be configured to act as the primary console.
Client Network Configuration
Networking requires special consideration. Some HP-UX OS software depends on name service use for the
client system to lookup its own IP address. You will need to configure a DNS server or change the HP-UX
name services configuration to favor files on the client system. If the client system is unable to lookup its own
IP address, you will experience significant delays during system boot.
To configure the client to favor files for name services you will need to modify /etc/nsswitch.conf and
/etc/hosts.
# /etc/nsswitch.conf:
passwd: compat
group: compat
hosts: files dns [NOTFOUND=return] nis [NOTFOUND=return]
ipnodes: files dns [NOTFOUND=return]
networks: files nis [NOTFOUND=return]
protocols: files nis [NOTFOUND=return]
rpc: files nis [NOTFOUND=return]
publickey: files nis [NOTFOUND=return]
netgroup: files nis [NOTFOUND=return]
automount: files nis
aliases: files nis
services: files nis [NOTFOUND=return]
This example is meant to highlight the general issue. Consult networking documentation for details.
If you use dynamically assigned IP addresses via DHCP, you should be aware that the auto_parms
command will edit /etc/hosts during system boot to add or update the client system’s entry.
Client-Specific Server Content
Ignite-UX saves client-specific content in the directory
/var/opt/ignite/clients/<MAC_address>
To aid usability, Ignite-UX creates a symbolic link for the client hostname at:
/var/opt/ignite/clients/<hostname>