Ignite-UX Reference (March 2010, B3921-90005)

bootsys(1M) bootsys(1M)
NAME
bootsys − reboot and install clients using Ignite-UX
SYNOPSIS
/opt/ignite/bin/bootsys [ -a|-w ][-dvhrfS ][-i configuration
|-R target_operating_system_release][[-l sw-sel=true|false]...]
[-V var[=value]...] [ -s grace ][-t Ignite-UX_server ]
[ -g gateway ][-m netmask] [client1[:IP_address]] [client2[:IP_address]...] [-?]
/opt/ignite/bin/bootsys -c Ignite-UX_Server [-a|-w][-dvhrfS]
[-i configuration | -R target_operating_system_release]
[-l sw-sel=true|false]...] [-V var[=value]...] [-s grace]
[ -g gateway ][-m netmask][-?]
DESCRIPTION
bootsys is used to remotely initiate HP-UX operating system installation on one or more clients without
the need to interact with the console of each client. The requirements are that each client must be running
HP-UX version B.10.20 or later, be accessible over the network, and have enough space in /stand to
hold the Ignite-UX kernel and RAM file system for the desired target release of HP-UX. The Ignite-UX
kernels (*INSTALL) and RAM file systems (*INSTALLFS) are located on the Ignite-UX server in
/opt/ignite/boot/Rel_release.
bootsys copies an Ignite-UX kernel and RAM file system to each client and then sets the client’s AUTO
file, so that it will boot from the Ignite-UX kernel at the next system reboot. bootsys also modifies sta-
ble storage (also known as nonvolatile memory) using the setboot command to set the primary boot
path and auto-boot flag to the disk from which it is currently booted. If you want to boot back to HP-UX
from the disk that bootsys has modified and the -r option of bootsys was used, then use
/tmp/bootsys_prep -u on the client. If -r was not used, reboot the client, interact with the ISL,
and manually select /stand/vmunix to boot, and the changes will be undone. The command
/tmp/bootsys_prep is left on the client by the bootsys command and is removed when its -u
option is used.
The bootsys command may be executed from an Ignite-UX server, or by using the -c option on the
client to be installed. The user running bootsys must have privileged user permission on each of the tar-
geted clients. (See the privileges(5) manpage for more information on the privileged user.) If the user does
not have remsh access to a client, bootsys prompts for the privileged user password (unless the -d
option is used, which causes the client to be skipped).
The target operating system release is required data for the bootsys command to transfer the correct
Ignite-UX kernel and RAM file system. The target operating system release can be explicitly indicated
with the -R option. If the -i option is used, bootsys will determine the operating system release that
is supported by that configuration and use it. If neither the -R option nor the -i option are given, bootsys
will set the target operating system to match the operating system release currently on the client. If the
client has historical configuration information on the Ignite-UX server and the current target operating sys-
tem release differs from the historical configuration, the -f option will be required for bootsys to suc-
cessfully complete.
The -a, -w, and -i options cause bootsys to add information to any existing parameters specified in
the /opt/ignite/boot/Rel_release/*INSTALLFS file. These parameters are added during the
transfer of this file to the client. The original file on the server is not modified.
Client systems may block the use of the bootsys command with the existence of the /.boot-
sys_block file in the client’s root directory. See the section, Blocking bootsys Attempts.
Options
bootsys recognizes the following options:
-a Automatically start the install process with no interaction. This means that the client will
not wait for the user to specify any configuration parameters and it uses all the defaults dur-
ing installation.
1