Multi-capable subnet boot serverIt is possible to set up a boot server that supports boot for multiple operating systems, including HP-UX. The multi-capable boot server may be an HP-UX system or a non-HP-UX system. If this boot server is an HP-UX system, the challenge becomes: how do I configure the HP-UX boot server to support non-HP-UX boot and installation. If the system is not an HP-UX system, the challenge becomes: how do I set up HP-UX boot and installation on the non-HP-UX system.
The information in this section is intended to provide general information to assist those setting-up a multi-capable boot server to initiate or fully support the installation of a variety of systems, including HP-UX installation. There is no general recipe for configuring these systems. In all cases, expertise is required to adapt these approaches to practical solutions.
For more detailed information about setting up specific types of boot/installation servers to support specific operating systems, see Chapter 6 (page 61).
Non-HP-UX Next server boot helper
If the non-HP-UX boot server supports configuration of the DHCP PXE Server Address (SiAddr) response data, the simplest approach is to have the response specify the master Ignite server (Next Server) to be used for all additional boot content. The non-HP-UX boot server will still need to be configured to determine when boot control needs to be passed to the Ignite server for HP-UX installation, and when control needs to be retained to perform other installations. This can be accomplished by using MAC addresses or with a menu of boot options, for example.
Note that the directory where the nbp.efi boot loader is located must match the location of other HP-UX boot content on the Ignite master server. If necessary, a symbolic link may be used from the directory path matching the non-HP-UX server location to the standard HP-UX location for boot content.
For more information, see “HP-UX DHCP PXE Next server boot helper for integrity systems” (page 57).
Non-HP-UX bootp boot helper
If the non-HP-UX boot server cannot be configured to support a custom DHCP PXE Server Address value, it is necessary for the server to provide the initial Ignite install environment content. To make this approach work, copy content in the /opt/ignite/boot directory to the non-HP-UX boot server.
While best practice might be to use the same directory path, there is no particular need for the path to be the same. The path where the Ignite install environment is located on the non-HP-UX boot server must match the DHCP PXE Boot File response value, but does not need to match the default location on an Ignite server. The initial install environment will be entirely taken from the non-HP-UX bootp boot helper system.
Note that the version of any Ignite content copied to a non-HP-UX boot server must match the version of the content on the Ignite master server; it will have to be updated when a new version of Ignite is installed.
Also, note that the AUTO file and IINSTALLFS files include Ignite-UX configuration content. It is important to keep this configuration content consistent with the Ignite-UX server.
Keeping versions and configuration content consistent between these servers can be difficult. If these servers are managed by different groups, ongoing administration might make this approach impractical.