Begin your installation process with “Preparing the Client for Installation ”.
You can use bootsys to start
a noninteractive system installation on one or more clients without
logging onto the client system, as illustrated in Figure 8-1.
You can invoke bootsys from
the command line interface (CLI), or from the Ignite-UX
GUI (see “ Installation Using the Ignite-UX GUI”).
The bootsys command copies
the Ignite-UX kernel and file system from the Ignite-UX server to
each client and then sets the system AUTO file
in the LIF area of the root disk to automatically boot from this kernel
at the next system reboot.
For more information, see bootsys(1M). Common problems using bootsys with
Ignite-UX are covered in Appendix A.
 |
| |
|
 | WARNING! The bootsys command does not
support network interfaces that are grouped using HP Auto Port Aggregation
(APA). You must not select an APA group as the interface through
which Ignite-UX will communicate with the Ignite-UX server. In these
cases select an interface outside the APA group, or break the APA
group and use a single ungrouped interface with bootsys (this may require reconfiguring the switch the APA group is connected
to.) |
|
| |
|
Examples
This sample command boots the client system from
the Ignite-UX server, boot1, and
waits for installation instructions from this server:
bootsys -R release -w boot1
where release is the
release that you want to install on the client. For example, B.11.23.
If you have already run an installation session
from the Ignite-UX server, issuing bootsys without
the -w option
results in automatic installation without further intervention.
To automatically install client1 using a different IP address than what is currently assigned and
without waiting for Ignite-UX server interaction, use this command:
bootsys -a client1:10.2.3.45
Printable version
