Technical data

Configuring BOOTP
9.4 Managing the BOOTP Service
To preserve site-specific parameter settings and commands, you can create
the following files. These files are not overwritten when you reinstall TCP/IP
Services:
• SYS$STARTUP:TCPIP$BOOTP_SYSTARTUP.COM can be used as a
repository for site-specific definitions and parameters to be invoked when
BOOTP is started.
• SYS$STARTUP:TCPIP$BOOTP_SYSHUTDOWN.COM can be used as a
repository for site-specific definitions and parameters to be invoked when
BOOTP is shut down.
9.5 Creating a BOOTP Database
If you choose to configure BOOTP while configuring TCP/IP Services,
TCPIP$CONFIG creates an empty BOOTP database.
If you need to create it manually, use the TCP/IP management
command CREATE BOOTP. This command creates the file
SYS$SYSTEM:TCPIP$BOOTP.DAT. The command uses the logical name
TCPIP$BOOTP to point to the BOOTP database file. To create a separate
database, perhaps in a different disk directory or with a different file name,
modify this logical name.
To create a temporary, separate, and empty BOOTP file, you can use a process-
specific logical name. However, Compaq does not recommend creating separate or
private BOOTP databases because the TCPIP$BOOTP user account requires read
access to the database file.
9.5.1 Populating the BOOTP Database
For each BOOTP client in the BOOTP database, use the SET BOOTP command
to enter the following required information:
• Client’s hardware address (required).
• Either the client’s name or IP address (required).
• Network mask (required).
• Client’s system image file name (required).
• Interim gateway (routing) systems.
• Either the name or IP address of other network servers. Some of the optional
servers that you can specify are:
Cookie servers
IEN-116 name servers
IMPRESS network image servers
LPR print servers
MIT-LCS UDP logging servers
DNS (BIND) name servers
Resource location (RLP) servers
Network time servers
9–6 Configuring BOOTP