Release Specific Server Configuration

With the release of Ignite-UX B.4.1, unique server configurations have become necessary. The server specific configurations described in this section are considered cumulative with each release unless specifically stated otherwise.

Follow the specific server configuration that is appropriate for the Ignite-UX version you are installing:

Ignite-UX B.4.2 PA/IPF Server Setup

The Ignite-UX B.4.2 and later releases provide enhanced support for server response to anonymous IPF clients with changes to the instl_bootd server. This enhancement is available for both PA and IPF server architectures.

The changes to instl_bootd requires that the bootpd daemon is not running on the given Ignite-UX server, rather the instl_bootd daemon is used by Ignite-UX to respond to all boot requests from clients. The instl_bootd daemon normally runs on a set of unique network ports, 1067/1068, that are used only for booting IPF clients. However, in this implementation the instl_bootd will run on the standard bootpd ports, 67/68.

Using instl_bootpd to support anonymous IPF clients

Follow these steps to configure your server to run instl_bootd as a replacement for bootpd:

Set up your Ignite-UX server as described in “Installing an Ignite-UX Server”.
Once your server has been setup, ensure that bootpd is disabled on ports 67/68 by commenting out the following line in /ect/inetd.conf as shown in this example:
#boots dgram udp wait root /usr/lbin/bootpd bootpd
Restart the inetd daemon:
/usr/sbin/inetd -c
Enable the instl_bootd daemon on ports 67/68 by adding the following line to /ect/inetd.conf:
boots dgram udp wait root /opt/ignite/lbin/instl_bootd instl_bootd
You must restart inetd again to invoke the change made in the previous step:

/usr/sbin/inetd -c

See the instl_bootd(1M) and inetd(1M) manpages for more details. Your Ignite-UX server is now configured to respond to anonymous clients.

Ignite-UX B.4.1 IPF Server Setup

Ignite-UX release B.4.1 and later support the installation of IPF systems running HP-UX 11i Version 1.6.

Configuring DHCP support for anonymous IPF clients

Network installation of an IPF system with Ignite-UX B.4.1 requires that you perform the following unique network installation steps.

At a minimum, the Ignite-IA-11-22 bundle should be loaded on your system. If it is not, load this bundle with swinstall.
Add your client's entries to /etc/bootptab on the server. The following example is provided in /etc/bootptab :
```
ignite-defaults:\
        ht=ethernet:\
        hn:\
        bf=/opt/ignite/boot/nbp.efi:\
        bs=48
System-IPF:\
        tc=ignite-defaults:\
        ha=00d009000000:\
        ip=190.40.101.22:\
        sm=255.255.248.0:\
        gw=190.1.48.1:\
        ds=190.1.48.11
```
All entries in the ignite-defaults section can be used without modification.
Duplicate (cut and paste) the System-IPF entries and change this section in the following ways:
1. Change System-IPF to reflect the client system's hostname.
2. Change the ha and ip fields for that client.
3. Change the sm, gw, and ds fields to reflect your network.
You can modify the system name, hardware address, IP address and other information for the client.
The following describes fields you may need to change per system and which fields are unique to your network:
- The ha field requires setting to the hardware address ( Mac or LLA address of the client system). This address can be found from the firmware's user interface when adding a boot option. See , “IPF Client Network Booting Option ” of Chapter 4 “Installing HP-UX with Ignite-UX on Clients Locally”. If the system is up and running, the lanscan command can also be used to find this value.
- The ip field is the IP address that has been reserved for the client you are about to install and must be an IP address that is valid for your network.
- The sm field is the network subnet mask and is probably the same for all systems on your network.
- The gw field is the network gateway. It is optional for booting purposes, but useful to provide the system defaults.
- The ds field is the domain name server (DNS) and is also optional for booting purposes, but useful to provide as a default.
Enable bootp services in the /etc/inetd.conf file by uncommenting the bootps entry.
Restart the Internet daemon by entering:
/usr/sbin/inetd -c

See the bootpd(1M) and inetd(1M) manpages for more details. Your Ignite-UX server is now configured to respond to anonymous clients.

Release Specific Server Configuration

Technical documentation

» Table of Contents

» Index

Ignite-UX B.4.2 PA/IPF Server Setup

Using instl_bootpd to support anonymous IPF clients

Ignite-UX B.4.1 IPF Server Setup

Configuring DHCP support for anonymous IPF clients