Technical data

Configuring the DHCP Server
7.4 Configuring the DHCP Server
b. Delete the DHCP data files from the DHCP directory by renaming them
to a temporary subdirectory. (You can delete the files after you are sure
that the failover environment is set up correctly.) For example, enter the
following commands:
$ CREATE/DIR SYS$SYSDEVICE:[TCPIP$DHCP.SAVE]
$ PURGE SYS$SYSDEVICE:[TCPIP$DHCP]
$ RENAME SYS$SYSDEVICE:[TCPIP$DHCP]DHCPCAP.;* SYS$SYSDEVICE:[TCPIP$DHCP.SAVE]
$ RENAME SYS$SYSDEVICE:[TCPIP$DHCP]DHCPTAGS.;* SYS$SYSDEVICE:[TCPIP$DHCP.SAVE]
$ RENAME SYS$SYSDEVICE:[TCPIP$DHCP]NAMEPOOL.;* SYS$SYSDEVICE:[TCPIP$DHCP.SAVE]
$ RENAME SYS$SYSDEVICE:[TCPIP$DHCP]NETMASKS.;* SYS$SYSDEVICE:[TCPIP$DHCP.SAVE]
$ RENAME SYS$SYSDEVICE:[TCPIP$DHCP]NETS.;* SYS$SYSDEVICE:[TCPIP$DHCP.SAVE]
$ RENAME SYS$SYSDEVICE:[TCPIP$DHCP]SERVER.PCY;* SYS$SYSDEVICE:[TCPIP$DHCP.SAVE]
$ RENAME SYS$SYSDEVICE:[TCPIP$DHCP]DB%.%%%;* SYS$SYSDEVICE:[TCPIP$DHCP.SAVE]
$ RENAME SYS$SYSDEVICE:[TCPIP$DHCP].DDNSKEYS;* SYS$SYSDEVICE:[TCPIP$DHCP.SAVE]
4. On each cluster node that is to serve as a potential DHCP server, set up the
TCPIP$DHCP_CONFIG logical name as follows:
a. Define TCPIP$DHCP_CONFIG as a systemwide logical name. For
example:
$ DEFINE/SYSTEM TCPIP$DHCP_CONFIG WORK1$:[DHCP_CONFIG]
b. Before you run the TCPIP$STARTUP.COM procedure, add
the TCPIP$DHCP_CONFIG logical name definition to the
TCPIP$DHCP_SYSTARTUP.COM file.
5. On each cluster node that you want to be a DHCP server, run
TCPIP$CONFIG to enable the DHCP service (see Section 7.4.1).
The TCPIP$CONFIG procedure creates the TCPIP$DHCP account and stores
initial copies of the DHCP configuration data files in the directory pointed
to by the logical name TCPIP$DHCP_CONFIG. If you choose to roll over
your BOOTP database to DHCP, TCPIP$CONFIG creates your initial DHCP
binary database files in the TCPIP$DHCP_CONFIG directory.
6. Make sure that the
auto_sync_dbs parameter is set in the SERVER.PCY file.
This parameter causes the DHCP server databases to be flushed after each
update. You can set the parameter by editing the SERVER.PCY file or by
setting the auto_sync_dbs parameter to True on the Server/Security tab in
the DHCP GUI.
7. Ensure that the files in TCPIP$DHCP_CONFIG: and the directory itself
are owned by TCPIP$DHCP and have owner-only protection (O:RWED). For
example:
$ DIRECTORY/SECURITY WORK1$:[DHCP_CONFIG]
$ DIRECTORY/SECURITY WORK1$:[000000]DHCP_CONFIG.DIR
8. Edit the NETS. file and set the ownership of any existing IP address range to
0.0.0.0.
7–22 Configuring the DHCP Server