Ignite-UX Custom Configuration files

is_hppa {
dhcp_class_id = "Ignite_PA_clients"
} else {
dhcp_class_id = "Ignite_IA_clients"
}
The else condition implicitly means Itanium®-based systems since Ignite-UX currently supports
only PA-RISC and Itanium®-based systems. This also assumes that you would want to share the
same installation file system configuration. This condition effectively limits what the client
responds to
71
.
 dhcp_server—this keyword can be used to limit the responses that are accepted by a
particular server.
This is not as flexible as the dhcp_class_id keyword. If the DHCP server is down, no response
is accepted. Compare that to a setup where you have two DHCP servers, each one willing to
serve out different IP addresses to the one class id. If one Ignite-UX server goes down, the other
DHCP server can still provide an IP address (although not as many are available).
The dhcp_server configuration item can apply to all LAN interfaces (for example,
dhcp_server = "10.0.0.53") or to one particular LAN interface (for example,
dhcp_server[0/0/0] = "10.0.0.54").
 dhcp_misc_opts—the dhcp_misc_opts configuration item can apply to all LAN interfaces
(for example, dhcp_misc_opts = "-l 6") or to one particular LAN interface (for example,
dhcp_misc_opts[0/0/0] = "-l 6").
Care should be taken when using the dhcp_misc_opts configuration item. The options
provided are for /usr/lbin/dhcpclient. Since this is a back-end command, its options are
not officially documented and this option should only be used when requested by HP.
The only option you are likely to be asked to add is the option to print debugging output:
dhcp_misc_opts = "-l 6".
 disable_dhcp—when set to TRUE in the installation file system, this item prevents Ignite-UX
from attempting to get an IP address using DHCP. You can use this item when you want to
manually give Ignite-UX its information (or if you have defined the IP address information in the
installation file system).
71 In a recovery situation, if you want to use DHCP to gain an IP address, Ignite-UX only adds the specific client IP address that actually
created the recovery archive into the /etc/exports file. If you can accept DHCP responses from anyone, the
potential list of IP addresses that
you may need to configure can get quite large, so many manual changes maybe required to the /etc/exports file on the Ignite-UX server. This
assumes that archives are written to the Ignite-UX server.
149