Installation

This chapter describes how to install the JOIN DHCP server:

  1. Check minimum system requirements
  2. Install the JOIN server software
  3. Set up the netmasks file
  4. Update NIS
  5. Configure DHCP/BOOTP addressing
  6. Configure DHCP parameters

Check Minimum System Requirements

 Before installing JOIN, check that you have the minimum system requirements for your UNIX host and systems:

Digital UNIX

HP-UX

Solaris

Sun OS 4.1.x

NIS (Yellow Pages)

 To update NIS (Yellow Pages) you need a computer running as an NIS server:

Install the JOIN server software
  1. Login as root.
  2. Select a partition with at least 12 MB of free disk space. Once the tar files are removed, the server software occupies 5 MB of disk space.
  3. Create a temporary directory for extracting and decompressing the server files.
  4. Insert the Server disk (Disk 1) into the disk drive of the server.
  5. Change directories to the temporary directory.
  6. Extract the contents of the Server disk using tar xvf:

    Platform Command
    SUN OS 4.x tar xvf /dev/fd0
    Solaris 2.x volcheck -v
    tar xvf /vol/dev/diskette0/unlabeled
    Digital UNIX tar xvf /dev/rfd0a
    HP-UX tar xvf /dev/rfloppy/c20Ad1s0

  7. Repeat Step 6 with the GUI disk.
  8. To continue the installation, enter:

    # ./install_join_server

    The install script backs up your existing installation (if one exists), and prompts you for installation directories. Appendix A contains sample installation logs.
JOIN software distribution consists of three main components: the configuration files, the executables and the JOIN databases. They are installed into three directories. The following table describes the default locations:

JOIN component default directory symbol to alternate
configuration files/etc/joinJOINCONFIG
executables/opt/joinn/a
database files/var/joinJOINSPOOL

If you install the configuration and database files without using the default values, you must define the corresponding symbols (JOINCONFIG and JOINSPOOL) to tell the DHCP server where to look for these files.

Set up the netmasks file

 JOIN requires that netmasks are defined properly. If your network is subnetted, this must be reflected in the netmasks file. The default JOIN netmasks file resides in /etc/join/netmasks.

The following table describes the standard netmask for each network class:

Network Class Netmask
Class A 255.0.0.0
Class B 255.255.0.0
Class C 255.255.255.0

If your netmask is not standard you must correct it in the netmask file or JOIN cannot operate successfully.

Update NIS

 NIS support is provided on SunOS 4.1.x, Solaris 2.x and HP-UX 10 only.

  1. Login as root.
  2. Enter:

    # newkey -h <hostname>

    where <hostname> is the name of the DHCP server to create a public key for DES authentication.
  3. Enter:

    # cd /var/yp/<domainname>
    # makedbm /dev/null join

    to create the JOIN pseudo map in /var/yp/<domainname>.
  4. Install the updaters file in /var/yp.

NIS only

 Install the executable file updtjoin in a suitable directory, and modify the updaters file with the pathname of updtjoin. NIS+ servers will automatically update NIS+ files, no extra steps are necessary.

Configure DHCP/BOOTP addressing

 After the server is installed, you can configure addresses for these different classes of client:

Once the IP addresses are configured, you may want to configure additional DHCP parameters for the clients.

Using dynamic IP addressing

To use dynamic IP addressing, specify a pool of IP addresses for the server to use. To configure a pool of IP address:

  1. Click the Server/Security tab.
  2. Choose IP Ranges, then choose [New IP Range].
  3. Enter the subnet address
  4. Enter the DHCP server address (your server host).
  5. Enter the range of IP addresses.

Using static IP addressing for BOOTP clients

 To use static IP addressing, specify a specific IP address for a specific MAC address.

  1. Click the Nodes tab.
  2. Choose [New Record].
  3. Enter the hostname (Name).
  4. Enter the MAC/hardware address. For example, 08:00:20:3f:12:4b.
  5. Choose Hardware Type from Key Parameters. Enter the type of network to which the node is connected, such as Token Ring or Ethernet. You can specify the hardware type using the symbol or the type number:
    Symbol Number
    ethernet or ether 1
    ethernet3 or ether3 2
    ax.25 3
    protnet 4
    chaos 5
    token-ring,tr,ieee802 6
    arcnet 7

  6. Choose Host IP Address, then enter the Host IP address of the host computer for this node.

Using static IP addressing for DHCP clients

 Select this option if you want to assign a specific IP address to a DHCP client. Usually, you want a permanent lease time with this IP address. Additionally, you don't want the IP address releasable by the client. Since any address within an IP pool is reuseable and thus releaseable by the client, you need to select an IP address that is not part of any IP pool. This will allow the server to specify a permanent mapping between a DHCP client's MAC address and the desired IP address.

To configure a specific, permanent address of a DHCP client:

  1. Click the Server/Security tab.
  2. Choose Active IP Snapshot, then choose [New Record].
  3. Enter the MAC address.
  4. Enter the MAC type.
  5. Enter the MAC address length.
  6. Enter an IP address that doesn't belong to any IP pools.
  7. Enter the Lease Expiration with -1 (infinite lease).
  8. Enter the Server IP Address.
  9. If you want a name associated to the client, specify its hostname and domain name.
Note: Depending on the DHCP client, the MAC address field may not be the actual MAC address of the client's network adapter. If you have ``Use MAC addr as Client ID'' set to True the server will use the MAC address to uniquely identify the clients. For more information refer to the descriptions that follow.

Clients known to modify the structure of the MAC address before sending it to the server:

Windows `95
Windows NT
Windows for Workgroups 3.11 with Microsoft TCP/IP

MAC Address is prefixed with the hardware type. The MAC type is 0 and the length is 7 (instead of 6). For example, if your Ethernet address is 11:22:33:44:55:66 then you need to specify the following for the static IP mapping:

MAC Address: 01:11:22:33:44:55:66
MAC Type: 0
MAC length: 7

FTP Software's
OnNet client

 MAC Address is prefixed with the string ``cid-''. The MAC type is 0 and the length is 16. For example, if you have your Ethernet address is 11:22:33:44:55:66 then you need to specify the following for the static IP mapping:

MAC Address: cid-112233445566
MAC Type: 0
MAC length: 16

Configure DHCP parameters

 You can specify various DHCP parameters to be offered to DHCP clients. Typically, you specify additional DHCP parameters on a per-subnet basis.

  1. Select the Subnet panel.
  2. Select New Record.
  3. Enter the subnet name (Name).
  4. Enter the Subnet IP address.
  5. Configure any other additional DHCP parameters.
    By default, only basic DHCP parameters are listed. For additional parameters, click Basic DHCP Parameters to display DHCP parameters or JOIN Parameters.

    Note: BOOTP parameters are specified in the Node panel when you configure static IP addressing.

This is the minimum information needed to configure MAC-to-IP mapping. Depending on your site requirements, you may need to specify additional parameters such as netmask, default routers, and DNS servers.

Start the JOIN server

 If you are restarting the server, you must kill the joind process first. To start the server, execute the following shell script:

# /opt/join/dhcp_startup
Note: Do not kill the server using the -9 option or SIGKILL; this will cause database corruption.

The dhcp_startup shell script does the following:

  1. Checks to see if the license manager, lmgrd, is running. If not, lmgrd will be started.
  2. Starts the DHCP server, joind. By default, the server is started with the -l2 option which will log all warning and error messages to syslog. If you want the server to run with other options, modify the startup script accordingly. For more information, refer to the joind man page.

Last Modified: 11:17am , November 11, 1996