This chapter describes the proclaim dynamic network configuration software package. The following topics are covered:
The proclaim system overview. See “The proclaim Dynamic Network Configuration System”.
Installing proclaim on a server. See “Installing proclaim on a Server”.
Installing proclaim on a client system. See “Installing proclaim on a Client”.
Configuring proclaim on a server system. See “Configuring proclaim”.
Sample entries in proclaim configuration files. See “Sample Configuration File”.
Information on limitations of this implementation with respect to the DHCP software standard. See “Limitations and Restrictions of This Release”.
The purpose of proclaim is to allow the site administrator to set up one or more server systems that dynamically distribute network IP addresses and site configuration parameters to new and requesting client systems. In this way, a site with only a few available addresses can serve a large number of hosts that connect to the network only occasionally, or a very large site can manage the permanent assignment of addresses with a minimum of human attention. The proclaim application is based on the Dynamic Host Configuration Protocol described in IETF RFC 1541.
The proclaim application consists of a daemon that runs on the server or servers, a set of configuration files for each server. The client process is distributed with the standard IRIX operating system and can be set up to be run through the bootup process or it can be run by hand. For more information, see the proclaim(1) reference page.
The following sections provide information on the installation of proclaim on servers and clients.
Like all of IRIXpro, proclaim is installed using inst(1). When you install proclaim, you are installing the server daemon and the initialized configuration files. (There is template information in the configuration file.) Files are also added to the /etc/init.d directory and an option is added to your chkconfig list.
The following list shows each file installed on your server:
| /etc/config/dhcp_bootp.options |
| |
| /etc/config/proclaim_server |
| |
| /usr/IRIXpro/proclaim/config/config.Default |
| |
| /usr/etc/dhcp_bootp |
|
After installing the proclaim subsystem of the IRIXpro product, you need to perform the following steps in order:
Enter this command:
chkconfig proclaim_server on |
Next, you must modify the /etc/inetd.conf file to use dhcp_bootp rather than the standard bootp protocols. Place a hashmark (#) at the beginning of the bootp entry to make that line a comment, and open a new line below that entry. Enter the following text all on one line:
bootp dgram udp wait root /usr/etc/dhcp_bootp dhcp_bootp -P -o /etc/config/dhcp_bootp.options |
In the above example, the -P option signifies that this is a dhcp bootp server. The -o option is used to specify a dhcp_bootp configuration file for specifying any additional proclaim specific options.
Save and exit the inetd.conf file when you have made this entry.
Reboot your system for these changes to take effect.
The proclaim server may modify the following files on your system:
/etc/hosts
/etc/ethers
/usr/IRIXpro/proclaim/etherToIP
To start the proclaim daemon at any time on a server, log in as root and enter this command
chkconfig proclaim_server on |
Then reboot your system for the change to take effect.
The following sections provide information on configuring proclaim on servers, and on the various configuration files, and limitations of this implementation of DHCP. If you are not comfortable with the basic concepts of networking, IP addresses, and netmasks, read Chapters 15 through 18 of the IRIX Advanced Site and Server Administration Guide before you continue reading this section.
The proclaim server implementation uses three levels of configuration parameters based upon the subnet number of the originating client request. The configuration files are all placed in the directory /usr/IRIXpro/proclaim/config and are named in the form config.netnumbers. For example, the configuration files for configuring clients on the 192.26.61 network are named config.192.26.61.0. If the configuration file for a client request originating on a particular subnet is not found, then the next level of configuration is supplied in the file config.Default in the same directory. If the default configuration file is not present or is unreadable, all clients are supplied the same configuration as the proclaim server itself.
The following configuration parameters can be supplied in the standard configuration file for each network, or the default configuration file. Host address specification can either be in standard IP address dot notation or as a hex number prefixed with a 0x. Most of the fields may be left blank to render them non-applicable.
| pro_address_counter |
| ||
| pro_host_pfx_counter |
| ||
| pro_netmask | This field takes a netmask in address form (xx.xx.xx.xx). For more information on netmasks, see the IRIX Advanced Site and Server Administration Guide. This field specifies the subnetmask that will be used by the client systems. | ||
| pro_lease | This unsigned integer field specifies the client address lease time in seconds. This implementation of the DHCP software assigns only infinite leases, and thus the leases expire only when explicitly surrendered by the client. | ||
| pro_propel_server |
| ||
| pro_host_prefix |
| ||
| pro_choose_name |
| ||
| pro_ipaddress_range |
In the above example, the server would issue IP addresses with the base address specified in the configuration filename (such as config.192.26.61.0). Each client is issued an IP address matching the name of the configuration file, suffixed with the numbers 1 through 3, and 5 through 7, and 9, but not 4 or 8. This option is used to restrict the IP addresses offered by a given server. This option is very useful if the administrator wants to assign only certain block(s) of addresses using proclaim, or in the absence of a server to server protocol, wishes to have multiple servers serve clients on the same subnetwork. | ||
| pro_router_addr |
| ||
| pro_timeserver_addr |
| ||
| pro_dnsserver_addr |
| ||
| pro_nisserver_addr |
| ||
| pro_dns_domain |
| ||
| pro_nis_domain |
| ||
| pro_mtu | This unsigned short integer field specifies the MTU (maximum transmission unit) to use on the network interface configured in this file. The minimum legal value for the MTU is 68. | ||
| pro_allnets_local |
| ||
| pro_broadcast |
| ||
| pro_domask_disc |
| ||
| pro_resp_mask_req |
| ||
| pro_static_route |
The static route field specifies a list of static routes that the client should install in its routing cache. If multiple routes to the same destination are specified, they should be listed in descending order of priority. The routes consist of a list of IP address pairs. The first address is the destination address; its counterpart address, separated by a dash (-), is the address of the router to the destination. The default route (0.0.0.0) is an illegal destination for a static route. |
The following are the contents of a sample config.150.166.61.0 configuration file.
pro_address_counter: 25 pro_host_pfx_counter: 5 pro_netmask: 255.255.255.0 pro_lease: 100000 pro_propel_server: 150.166.75.20 pro_host_prefix: irixpro pro_choose_name: 0 pro_ipaddress_range: 3, 9-11, 40-75, 200-254 pro_router_addr: 150.166.61.19 pro_timeserver_addr: 150.166.61.27 pro_dnsserver_addr: 192.26.61.24 pro_nisserver_addr: 192.48.150.150 pro_dns_domain: sgi.com pro_nis_domain: engr.sgi.com pro_mtu: 1600 pro_allnets_local: 1 pro_broadcast: 150.166.61.255 pro_domask_disc: 0 pro_resp_mask_req: 0 pro_static_routes: 192.26.80.118 - 192.26.80.10, 192.26.80.118 - 150.166.61.33 |
The /etc/config/dhcp_bootp.options file may specify the following additional options. The options may be specified on individual lines or on the same line separated by white spaces.
| -s propel_database |
| |
| -y | The proclaim server uses the existing NIS maps for hostname, IP address, and network hardware address resolution. This host is required to be the NIS Master. | |
| -h hostname | Specifies the name of the host where the propel lock manager is running if it is not running on this system. | |
| -w hosts_map | Specifies the optional location of the hosts map. Not valid with the -s option. The default is /etc/hosts. | |
| -e ethers_map | Specifies the optional location of the ethers map. Not valid with the -s option. The default is /etc/ethers. | |
| -u sysname | Specifies the name for an optional sysname file. The default is /unix. | |
| -c proclaim config dir |
|
The following restrictions and limitations are present in proclaim in this release:
The server must be the NIS Master if it is using NIS for hostname, IP address, or network hardware address validation and mapping. Note that NIS is an optional software product, and not all systems and networks use it.
This release of the server software assigns only infinite (meaning roughly 10-year) address leases. A client requesting a shorter lease must actually surrender the lease in order for the lease to be considered expired.
The server will not serve proclaim and standard bootp clients in the same request packet.
Clients requesting additional configuration parameters that are part of RFC1533 but are not supported in this release are not served by the proclaim server.