Technical data

Configuring the DHCP Client
8.4 Configuring the DHCP Client
HOSTNAME.[ifname]
This file contains a host name that you want to suggest that the DHCP
server use as the system’s host name. TCPIP$CONFIG puts the value of
the cluster system parameter SCSNODE from the client system into this
file. For more information about this file, see Section 8.2.2.3.
After extracting the files, TCPIP$CONFIG places the files into the directory
pointed to by the TCPIP$DHCP_CONFIG logical, if it is defined. If
TCPIP$DHCP_CONFIG is not defined, then the files are put into the
SYS$SYSDEVICE:[TCPIP$DHCP] directory. No files are created if a version
already exists.
Note
The DHCP client may not coexist on the same system as a DHCP server.
TCPIP$CONFIG will not allow you to configure the DHCP client on a
system with DHCP server configured.
8.4.3 Configuring a Cluster Environment
If you want to have multiple OpenVMS cluster nodes sharing the same
CLIENT.PCY file and the nodes have identical interface names, a conflict will
arise if you simply define TCPIP$DHCP_CONFIG to a common directory shared
between the systems.
For example, if two systems in your cluster both have an interface named SE0
under DHCP control, to configure for this situation:
1. Define the system logical TCPIP$DHCP_CONFIG as a search list first
pointing to a system-specific directory that you create for the DHCP client
and then to the common directory.
2. Place the CLIENT.PCY file in the common directory.
3. If you want, place the HOSTNAME file into the SYS$SPECIFIC: directory.
The ifname.DHC files will be created in the SYS$SPECIFIC:[] directory. For
completeness, you might want to make the default device and directory for
the TCPIP$DHCP account the SYS$SPECIFIC:[] directory, too.
8.4.4 Signaling the DHCP Client
You can use the TCPIP$DHCP_SIGNAL utility to signal the DHCP client to:
• Translate utility logicals and read configuration files
• Shutdown the DHCP client
• Dump the diagnostic state of the DHCP client to a file
Table 8–5 shows the commands available with the TCPIP$DHCP_SIGNAL
utility:
Configuring the DHCP Client 8–15