Ignite-UX Installation Booting
8
The vPars boot process is as follows:
1. The vparboot command locates
the installation kernel and file
system.
2. The vparboot command
transfers the installation kernel and
file system to the vPars monitor.
3. The monitor places them into the
memory that is used by the host
being started.
4. The kernel in the virtual partition is
started.
Once the vPar host2 has started and is
running the kernel in the installation file
system, it must be able to contact the Ignite-
UX server.
This is accomplished either by the client
contacting a DHCP server to obtain an IP
address, or by entering the information on
the client console designating the IP
address and Ignite-UX server to use (and
possibly a default route).
To advance the booting process, the client
must be connected via the network to the
Ignite-UX server.
If the booting partition cannot contact the Ignite-UX server because there is no network connectivity,
the installation cannot succeed.
Remember that being able to boot a virtual partition from an Ignite-UX server does not mean there
is network connectivity between the two systems, so consider the following:
• When you choose a network interface on the booting vPars system, it
must
have network
connectivity to the Ignite-UX server.
• If you experience problems, troubleshoot the connectivity issue as a network problem.
host1
host2
host3
vPars
monitor