Ignite-UX Installation Booting

25
Booting from CD/DVD (HP9000 and/or HP Integrity systems)
This section no longer discusses how to create custom CD/DVD boot media for HP9000 or HP
Integrity servers. Instead, please refer to the Ignite-UX Custom Configuration Files document in the
section titled, “How do I create the CD equivalent of a tape created by make_boot_tape?”
The bootsys (1m) command
The bootsys command allows you reinstall or recover an existing HP-UX system on its next reboot.
The bootsys command does this by copying an install kernel and filesystem to /stand on the
client from an Ignite-UX server. (This means you must have enough free space on the client to hold a
copy of the install kernel and filesystem.) The bootsys command then modifies how the system will
next boot so it points at the install kernel in /stand.
Note that you must have a functional HP-UX system before you can use bootsys. If the system is
down and is not currently bootable, you will not be able to take advantage of bootsys as an
installation or recovery method.
Important:
The bootsys command does not support Auto-Port Aggregation (APA).
If you need to contact an Ignite-UX server through an aggregate link, the
aggregate must be broken before running bootsys, and a LAN
interface must be set up with the IP address information through which
you wish to contact the Ignite-UX server.
Please consult the bootsys(1m) man page for more information on the bootsys command.
Customizing the media
The following are customization ideas for environments where it is not feasible or desirable to boot
systems over the network.
If you provide enough information in the install filesystem, you can have individually customized
media that can set the IP address and disable DHCP so you do not need to gain an IP address over
the network. This would require sets of CDs/DVDs unique to subnets to allow you to boot the
CDs/DVDs on systems and not have conflicting IP addresses.
An extension to this would be to add tests to the configuration in the install filesystem to test on
MAC addresses of systems on a subnet. This would allow a system to use the IP address it normally
uses (with a default route defined) so the system could be booted for install or recovery using its
own IP address without having to worry about network booting, bootp, DHCP, boot helper setup,
and so forth.