Technical data

Configuring the DHCP Client
8.2 DHCP Client Components
options are super encapsulated into the vendor field (#43); within a specific
DHCP packet there may be several instances of option #43.
• Pseudotags
These are fields of the BOOTP packet and are not defined in RFC2131. Do
not change these fields.
In general, the DHCP server knows little about the semantics of the first three
options. Its only duty is to deliver those values to clients that need them.
The responsibility for understanding and using the data rests with the client.
Pseudotags have a meaning specific to TCP/IP Services.
8.2.3 Command Files
Table 8–3 lists the command files that the DHCP client uses to start up and shut
down the component.
Table 8–3 DHCP Client Command Files
Command File Name Description
TCPIP$DHCP_CLIENT_STARTUP.COM Installs the DHCP client image.
TCPIP$DHCP_CLIENT_SHUTDOWN.COM Stops DHCP client.
8.2.4 System Logicals
Use the logicals listed in Table 8–4 to alter the behavior of the DHCP client.
Table 8–4 DHCP Client System Logicals
Logical Name Purpose
TCPIP$DHCP_DEBUG Turns on DHCP client diagnostics. Refer to
Section 7.2.4 for a description of this logical.
TCPIP$DHCP_CONFIG directory Specifies the directory from which to read
input files (CLIENT.PCY, DHCPTAGS. and
HOSTNAME.) and to which to write output
files (
ifname .DHC). Note that DHCP client
log files will still go to the default directory of
the DHCP client account.
TCPIP$LOG_LEVEL value Writes the specified level of diagnostic
information to the log file. Ignored if
TCPIP$DHCP_DEBUG is defined.
Valid numeric values are:
0 No logging (default).
1 Log warning messages.
2 Log all messages.
8.2.5 Log Files
DHCP client creates a log file named TCPIP$DHCP_CLIENT_RUN.LOG in the
directory SYS$SYSDEVICE:[TCPIP$DHCP].
Configuring the DHCP Client 8–11