Skip Dhcp setup

Once you exit the Configure Booting IP Addresses dialog box, a registered client’s boot request is answered by instl_bootd, and the client will boot to the reserved IP address listed in the Booting IP Addresses window.

NOTE: No intervention is required to have instl_bootd pick up changes to the /etc/opt/ ignite/instl_boottab file. When a boot request is received, instl_bootd always checks whether the file was modified since last read, and rereads it before answering any boot request. Care must be taken if you edit the /etc/opt/ignite/instl_boottab file manually. For the correct procedure see instl_bootd(1M).

After exiting the Configure Booting IP Addresses dialog box, the Server Setup: DHCP (optional) dialog box appears. Select Skip DHCP Setup, then click Next.

A dialog box is displayed to tell you how to configure DHCP services later. Click OK.

The Server Setup: Software Depot Setup dialog box is then displayed (Figure 12 (page 37)).

Go to the software setup section

Proceed to “Setting up software from OE depots” (page 36) to complete the Ignite-UX server setup.

Configuring the Ignite-UX server for Itanium-based clients

Register the Itanium-based clients with the server

Registered Itanium-based clients must be entered in the /etc/bootptab file manually; they cannot be registered using the Server Setup Wizard. The /etc/bootptab file acts as the database for the bootpd daemon on the Ignite-UX server. All registered clients you intend to boot from the Ignite-UX server must be entered in the bootptab file.

A typical bootptab file has a generic, default client specification defined. The individual clients use this default definition and make their specific modifications to it, such as the IP address and the hardware address (MAC address). In the following example, IADEF is the default configuration for Itanium-based clients on the subnet, and iuxclient1 is the specific entry for that particular client.

IADEF:\

ht=ethernet:\

hn:\

dn=domain_name.com gw=190.1.48.1:\ sm=255.255.248.0:\ ds=190.1.48.11 190.1.48.12:\ vm=rfc1048:\ bf=/opt/ignite/boot/nbp.efi:\ bs=48:

iuxclient1:\

tc=IADEF:\

ip=15.1.52.204:\

ha=00306E4A3391

The tc tag indicates the use of a template for common defaults, so all the values from IADEF are assumed for iuxclient1 unless specifically overridden in the client’s definition. The ip tag indicates the client’s IP address, and the ha tag indicates the MAC address. For more information on the bootptab file syntax, see bootpd(1m).

For each client you intend to boot from the Ignite-UX server, enter their respective IPs and MAC addresses in the bootptab file.

Configuring the Ignite-UX server for Itanium-based clients 35