Configuring
network boot IP addresses is hardware architecture dependent. Choose
the appropriate method for your hardware (PA-RISC or Itanium-based).
PA-RISC Configuration
Select Configure Booting
IP Addresses.... The dialog box shown in Figure 3-8 is displayed.
During the installation process, the clients must
do a network boot from the Ignite-UX server. In order to do this,
the clients must be assigned a temporary IP address.
In the IP Range fields, enter an initial range
of available IP addresses from which this Ignite-UX server can execute
the initial client boot. The following example enables Ignite-UX to
perform 20 simultaneous installations using this range of IP addresses:
This temporary IP address is only used to boot
over the network during the initial transfer of the kernel from the
server to the client. You may only need one or two addresses, depending
on how many systems are performing network boots at the same time.
 |
| |
|
 | IMPORTANT: Be sure that the temporary IP addresses you enter
here are not assigned. If they are, this creates a network conflict
and unexpected results. |
|
| |
|
If you need to change these addresses later, you
must edit the /etc/opt/ignite/instl_boottab file.
For more information, see instl_bootd(1M).
Itanium-Based Configuration
Select Add DHCP Addresses.... The dialog box shown in Figure 3-9 is displayed.
The IP addresses you provide are used during the
operating system download and application installation. These addresses
are in use for most of the Ignite-UX download to a client. One address
is required for each simultaneous download.
This provision of DHCP capability is for the installation only. You
might want to limit configurations so that they do not interfere with
prior DHCP server functions.
Permanent IP addresses are distributed using DHCP
Services. Unless you are familiar with DHCP services, do not modify
the DHCP Class ID field or the DHCP Addresses
are temporary check box. The DHCP service is only used
for client configurations that do not have predefined system hostnames
and IP addresses.
Provide a range of available, permanent IP addresses
in the DHCP Addresses fields to indicate the range from lowest number
to highest. For example:
You can supply these addresses once in Ignite-UX. After this initial definition, use SAM to modify these
IP addresses.
For more information about configuring DHCP, see Appendix B. For more information
about setting up DHCP functions, addresses, and class IDs, see setup_server(1M) and instl_adm(4).
Printable version
