Ignite-UX enables you to install client systems
manually from the Ignite-UX GUI, as explained in this chapter, or
automatically, as explained in Chapter 11. You can also install clients from a remote
system by using bootsys, or install the client
locally using an operating system obtained from an Ignite-UX server,
as explained in Chapter 7.
Each installation method requires a configuration
(config) file, as explained in Chapter 10. The configuration can include any supported
HP-UX 11i operating system, plus any required patches and applications.
This chapter describes installing from the Ignite-UX
server, either using the Ignite-UX GUI or remotely using the bootsys command.
Begin your installation process with “Preparing the Client for Installation ”.
 |
| |
|
 | WARNING! Any data on the client disks that are used for
installation, including the operating system, are removed entirely
as part of this installation process. |
|
| |
|
|
| |
|
 | IMPORTANT: During HP-UX 11i v3 installation and recovery,
connected Active/Passive devices will cause long delays (one hour
or more) or may cause a system to hang. Similarly, connecting an Active/Passive
device before installing the Active/Passive Switch (APSW) plug-in
can cause some commands to take a long time. Disconnect any Active/Passive
devices connected to your system before installing or recovering HP-UX
11i v3. After installation or recovery, it is important that the APSW
plug-in be installed before connecting an Active/Passive device to
the system. |
|
| |
|
Supported Peripherals |
|
If a disk device is visible, it does not mean
it is supported for installation. It is important to verify that the
disk is supported by the system, the host bus adaptor (HBA), the firmware,
the HP-UX release, and the volume manager to be used.
Computer system hardware documentation should be consulted for
supported I/O configurations. See http://www.docs.hp.com for HP computer system hardware documentation.
At times you might need new firmware to support a new device
or HBA. Ensure that the client’s firmware supports the devices
and HBA to be used for boot and root. For example, after the HP9000
rp8400 system was first released, firmware changes enabled the system
to boot from disks connected to Ultra 160 HBAs. Check the Installation and Update Guide for your HP-UX release,
available at http://www.docs.hp.com, for instructions on finding firmware information.
Additionally, firmware support for Fibre Channel,
tape devices, and LAN cards might vary. In some cases, devices are
supported for data use, but device boot is not supported.
VxVM support is provided for a specific set of devices.
The list of supported devices should be consulted – see http://docs.hp.com/en/oshpux11iv2.html#VxFS. Look for
the section Support Matrixes, and the document
entitled Device Support for Veritas Products on HP-UX.
LVM supports all the devices HP-UX supports. See the HP-UX Supported
Mass Storage Devices Matrix for a table of I/O devices supported
for each version of HP-UX.
Other Client Installation Considerations |
|
You can install disk arrays using HP-UX, but the
installation tasks do not support configuring an array. The disk array
must be configured first; see your array documentation for configuration
instructions. In some cases, system firmware may be used to set up
disk arrays. The Ignite-UX install environment contains tools that
are also used to help configure disk arrays. To use these tools in
the install environment, you will need to use the Expert Recovery
functionality to start an install environment shell. It might also
be necessary to load files that are not normally included in the install
environment by using the Ignite-UX loadfile command.
When array configuration is complete, it is necessary to reboot the
system in order to use the newly configured disk LUNs during install.
The Ignite-UX client-side operating system installation
tools support VT100 and Wyse 60 terminals, compatible terminal emulators,
and all HP terminals. Additional information regarding how to navigate
within the Ignite-UX GUI with the keyboard is found in Appendix E.
Network Requirements |
|
Only one LAN interface can be used during installation,
configured in the Ignite-UX GUI, or handled automatically by bootsys. If a client has multiple LAN interfaces, you can
select the one that is configured on the correct network by using
the Additional Interfaces... button
on the System tab (see “System Tab ”).
In addition, you need to consider the following:
If you plan to perform
a network boot for a client, then the Ignite-UX server must be on
the same subnet as the client that will be installed.
If you have more than
one LAN connection, you must select the one to be used for the installation
process.
If you want
to use a more advanced method, you can implement a boot-helper system
on each subnet from which to boot clients. See Appendix D for more information, or use the bootsys or make_boot_tape commands.
If you use bootsys to boot the system, you cannot select an interface that is part
of an HP Auto Port Aggregation (APA) group. The bootsys command does not support interfaces that are part
of an APA group. See “Installation Using bootsys” for more information.
|
| |
|
 | TIP: Normally, you can only use the Ethernet interface
for booting and only depend on the built-in Ethernet interface on
the primary I/O interface being bootable. Other LAN interfaces may
not have boot support so you might consider booting from media (CD,
DVD, or tape) devices, and then contact an Ignite-UX server over these
other network interfaces. |
|
| |
|
Printable version
