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

ManualsBrandsHP ManualsSoftwareHP Ignite-UX

bootsys(1M) bootsys(1M)

The host key prompt above is only issued once. Upon answering "yes", that host’s public key is stored in

the user’s ˜/.ssh/known_hosts ﬁle and is validated for each new ssh session. If the private host key

changes for any reason, a message similar to

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!

Someone could be eavesdropping on you right now

(man-in-the-middle attack)!

It is also possible that the RSA host key has just been changed.

The fingerprint for the RSA key sent by the remote host is

4b:85:69:9a:ed:9d:b9:0a:e0:23:d7:d9:1c:c0:38:0e.

Please contact your system administrator.

Add correct host key in /home/smith/.ssh/known_hosts to get

rid of this message.

Offending key in /home/smith/.ssh/known_hosts:32

RSA host key for test4 has changed and you have requested

strict checking.

Host key verification failed.

is issued. This may occur for several reasons. It is possible that OpenSSH has been removed and rein-

stalled, HP-UX has been reinstalled, a networking misconﬁguration problem exists so that you are con-

nected to the wrong client, or a genuine breach of security has occurred. Before taking any action, the user

should determine what has caused the host key to change. If the host key changed for a legitimate reason,

such as reinstallation of the operating system of the client, it is safe to remove the offending entry (in this

case, line 32) from the known_hosts ﬁle. See ssh(1) and ssh-keygen(1) for more information.

For more information on the features, beneﬁts, and assistance with troubleshooting ssh, please review the

material available at the following URL:

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.

EXAMPLES

Boot the following three systems immediately from the Ignite-UX server, such that the clients wait for the

Ignite UI to conﬁgure them:

bootsys -w client1 client2 client3

Automatically install client1 specifying the conﬁguration for it to use:

bootsys -a -i ’HP-UX B.11.23 Default’ client1

Automatically install client1 providing 10 minutes for users to log off:

bootsys -a -s 600 client1

Automatically install client1 using a different IP address than what it is currently assigned:

bootsys -a client1:1.2.3.45

Automatically install the systems listed, and ignore clients that cannot be accessed:

bootsys -a -d client1 client2 client3

If a client had bootsys executed on it, but you want to reboot back to HP-UX off the disk on which

bootsys modiﬁed the AUTO ﬁle and the -r option was used, you can execute the command

/tmp/bootsys_prep -u on the client. If -r was not used, you can interact with the ISL to get the

system to boot from the normal kernel /stand/vmunix, and the changes will automatically be undone.

The command /tmp/bootsys_prep is left on the client by the bootsys command and is removed