bootsys.1m (2012 03)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

bootsys(1M) bootsys(1M)

NAME

bootsys - reboot and install clients using Ignite-UX

SYNOPSIS

/opt/ignite/bin/bootsys

[ -a

|-w ][-dvhrfS ][-i conﬁguration

-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 conﬁguration | -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 run-

ning 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 ﬁle system for the desired target release of HP-UX. The Ignite-UX

kernels (*INSTALL) and RAM ﬁle systems (

*INSTALLFS) are located on the Ignite-UX server in

/opt/ignite/boot/Rel_release

bootsys copies an Ignite-UX kernel and RAM ﬁle system to each client and then sets the client’s

AUTO

ﬁle, so that it will boot from the Ignite-UX kernel at the next system reboot. bootsys

also modiﬁes

stable storage (also known as nonvolatile memory) using the

setboot command to set the primary boot

path and auto-boot ﬂag to the disk from which it is currently booted. If you want to boot back to HP-UX

from the disk that bootsys has modiﬁed 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

targeted 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 ﬁle 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 conﬁguration 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 conﬁguration information on the Ignite-UX server and the current target

operating system release differs from the historical conﬁguration, the

-f option will be required for

bootsys to successfully complete.

The

-a, -w, and -i options cause bootsys to add information to any existing parameters speciﬁed in

the /opt/ignite/boot/Rel_release /*INSTALLFS ﬁle. These parameters are added during the

transfer of this ﬁle to the client. The original ﬁle on the server is not modiﬁed.

Client systems may block the use of the

bootsys command with the existence of the

/.bootsys_block ﬁle. 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 conﬁguration parameters and it uses all the defaults during

installation.

-w Causes the client system to boot Ignite-UX and then wait for the ignite user interface run-

ning on the Ignite-UX server to instruct the client on how to proceed with the installation.

If neither the

-a nor the -w option is given, the client will boot using the default mode stored

in the /opt/ignite/boot/Rel_release /*INSTALLFS ﬁle. The keywords that control

executing the user interface are control_from_server and run_ui. See instl_adm (4)

HP-UX 11i Version 3: March 2012 − 1 − Hewlett-Packard Company 1

Summary of content (6 pages)

PAGE 1
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].
PAGE 2
bootsys(1M) bootsys(1M) for more information on configuration keywords. -d Causes bootsys to ignore any clients listed that are down, cannot be accessed with remsh, or are incompatible with the indicated target operating system. bootsys will continue operating on systems that can be accessed and are compatible with the target operating system. Without the -d option, bootsys will prompt for the root password of clients that do not allow remsh access, and will exit if any client appears to be down.
PAGE 3
bootsys(1M) bootsys(1M) -s grace Causes bootsys to use shutdown with the specified grace period (in seconds). Normally bootsys uses the reboot -q command and reboots the system immediately with no warning to users. -S Directs bootsys to use ssh based protocols instead of remsh based protocols when communicating with remote systems. For more information, see the section Using SSH with bootsys. -t install_tftp_server Specifies the default system to be used as the Ignite-UX install server.
PAGE 4
bootsys(1M) bootsys(1M) bootsys must use public/private key authentication in conjunction with an ssh-agent process. This allows bootsys to automatically perform its tasks without intervention. When bootsys is invoked with the -S flag, it verifies that the user has created a public RSA or DSA key, and checks the SSH_AGENT_PID environment variable to determine whether an ssh-agent process has been started.
PAGE 5
bootsys(1M) bootsys(1M) http://www.docs.hp.com/en/internet.html#Secure%20Shell RETURN VALUE bootsys will exit with a status of 0 (zero) if all clients were rebooted successfully. A non-zero value is returned if any problem occurred.
PAGE 6
bootsys(1M) bootsys(1M) /var/opt/ignite/data/INDEX The INDEX file used on the Ignite-UX server to define the configurations available. The -i option may be used to specify one of these configurations. SEE ALSO ssh(1), ssh-agent(1), ssh-add(1), instl_adm(1M), isl(1M), setboot(1M), remsh(1M), ignite(5), ssh-config(5), http://www.docs.hp.com/en/internet.