Ignite-UX Administration Guide for HP-UX 11i (B3921-90079, October 2013)

booted from a source local to the client system. Regardless of how Ignite-UX is started, it has the
same network capabilities once it is running.
• Use bootsys to boot a system already running HP-UX
If the client system is already running HP-UX, the Ignite-UX bootsys command may be used
to copy the install kernel and install file system to the client system's HP-UX file system. After
reboot, the HP-UX boot loader can boot for installation using that copied content. Ignite config
content in the install file system may be used to cause Ignite to automatically switch to use the
master Ignite server. Because the initial install environment is copied from the Ignite server,
you can be confident the Ignite versions of the initial boot content and software on the Ignite
server have the same versions. See “Using bootsys on the Client Console” (page 98).
• Use DVD media to boot a system for network installation
Ignite supports booting for network installation using standard HP installation media or custom
boot media. The version of the Ignite on the media must match the version of Ignite running
on the master Ignite server. The simplest way to ensure the versions match is to use
make_media_install on the Ignite server to create custom boot media. This custom boot
media may be constructed to include [W|V|I]INSTALLFS config content, which automatically
switches to using the Ignite server on startup. Standard HP-UX installation media may also be
used to boot the system, as long as the Ignite version on the media matches the master server
Ignite version. Standard HP-UX media config content cannot be modified to automatically
switch to your Ignite server. See “Creating a Boot CD/DVD or an Installation DVD” (page 182)
and “Tape Recovery With No Tape Boot Support — Two-Step Media Recovery” (page 214).
• Use vMedia USB DVD to boot a system for network installation
Many Integrity systems support Integrated Lights Out (iLO) Virtual Media (vMedia). This feature
must be enabled using a license key. Once enabled, a DVD device or an ISO DVD image on
a remote system, such as a PC, may be used. In either case, the client system will appear to
have a local USB DVD device.
For more information, see Appendix D (page 238) and the HP Integrity iLO 2 MP Operations
Guide available at http://www.hp.com/go/hpsc.
• Boot your Integrity system from a USB memory stick device
It is possible to configure your Integrity system and a USB flash drive in order to boot HP-UX
directly from a memory stick device. Once the system is booted to the HP-UX Ignite-UX install
environment, you can perform a variety of installation or recovery actions. See the Ignite-UX
USB Memory Stick Boot white paper, available at http://www.hp.com/go/ignite-ux-docs,
for more information.
Complex Networks
Setting up an Ignite server on a simple network assumes there is a single subnet with only one
Ignite server that supports network boot and installation. Often, real network environments are
significantly more complex. Configuring an Ignite server to operate correctly while avoiding
interference with other boot and installation servers on the network requires special consideration.
For a detailed discussion, see Chapter 5 (page 47).
Diagnosing Network Boot Issues
When configuring a network, sometimes boot and installation will not work at all or will not work
as expected. Especially when configuring a complex network, you should expect to spend time
diagnosing and resolving issues due to the complexity of the network and interactions between
servers. You should also expect that problems might occur in the future as the complex network
changes.
This section includes suggested tools and techniques for diagnosing problems.
Complex Networks 27