Technical data

Configuring the DHCP Server
7.2 DHCP Server Components
Table 7–5 DHCP Server Logical Names
Logical Name Description
TCPIP$DHCP_CONFIG directory If defined, places the following DHCP files (during
TCPIP$CONFIG) in the directory you specify:
• DHCP configuration files in ASCII format (for example,
SERVER.PCY)
• DHCP database files in binary format (for example,
DBA.BTR)
• Binary database lock files (for example, RWLOCKDBA)
• Temporary files created by TCPIP$CONFIG during the
BOOTP-to-DHCP rollover
• The server’s process identification file (JOIN.PID)
Setting this logical name is useful when you want to
move the file location off the system disk or when you
want to set up a DHCP cluster failover environment (see
Section 7.4.5). The logical name must be defined before
running TCPIP$CONFIG.
If not defined, the preceding DHCP-related files are
placed in SYS$SYSDEVICE:[TCPIP$DHCP] during the
TCPIP$CONFIG procedure.
TCPIP$DHCP_DEBUG value Logs full diagnostics. Valid numeric values are 1 to 6. If you
define this logical, the value of TCPIP$DHCP_LOG_LEVEL
is ignored.
TCPIP$DHCP_LOG name Defines the name of the DHCP server log file. The default is
TCPIP$DHCP_RUN.LOG.
If defined, each time the auxiliary server starts a DHCP
server process, two log files are created: the one you
define with TCPIP$DHCP_LOG name and the default
TCPIP$DHCP_RUN.LOG.
TCPIP$DHCP_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.
You define system wide TCPIP$DHCP logical names in the
SYS$STARTUP:TCPIP$DHCP_SYSTARTUP.COM file. After making changes
to the file, enter the following commands:
$ @SYS$STARTUP:TCPIP$DHCP_SHUTDOWN.COM
$ @SYS$STARTUP:TCPIP$DHCP_STARTUP.COM
Alternatively, you can follow these steps:
1. Manually define the system logical names.
2. Use DHCPSIGHUP to signal the DHCP server.
7–16 Configuring the DHCP Server