HP MSR2000/3000/4000 Router Series Fundamentals Configuration Guide

130
Deploying and configuring servers for automatic
configuration
To implement automatic configuration, you do not need to perform any configuration on the device.
However, you must deploy DHCP, TFTP, and DNS servers and configure the servers to cooperate with the
device as follows:
• DHCP server—Assigns the device a set of parameters for automatic configuration, which might
include a temporary IP address, a configuration file name, a TFTP server domain name, a TFTP
server IP address, and a DNS server IP address. For more information about the DHCP server, see
Layer 3—IP Services Configuration Guide.
• TFTP server—Stores files required for device automatic configuration, including the configuration
files and host name files. For more information about the TFTP server, see "Configuring TFTP."
• DNS server—Resolves the device's temporary IP address to its host name so the device can request
a configuration file named in the format host name.cfg from the TFTP server. The DNS server might
also need to resolve the TFTP server domain name to the TFTP server IP address. For more
information about the DNS server, see Layer 3—IP Services Configuration Guide.
If the DHCP server, the TFTP server, the DNS server, and the device are not in the same network segment,
configure the DHCP relay agent on the gateway, and configure routing protocols to make sure the servers
have routes to the device and vice versa.
DHCP server configuration guidelines
When you configure the DHCP server, follow these guidelines:
• If the devices on a network segment share the same configuration file, configure the dynamic
address allocation mechanism on the connected interface of the DHCP server.
• If the devices on a network segment share most of their configurations, configure the dynamic
address allocation mechanism on the connected interface of the DHCP server. You can put the
configurations that the devices share to the configuration file, and provide a method for the device
administrators to change the configurations after their devices start up. For example, you can
configure a configuration file that enables the Telnet service and creates a local user, so
administrators can Telnet to their devices to perform specific configurations after their devices start
up.
• If the devices on a network segment need different configurations, configure the static address
allocation mechanism on the connected interface of the DHCP server. This method allows you to
configure a separate configuration file for each device.
Before you configure a static binding for a device, you must obtain the client ID of the device. To
do so, you can ask the device administrator for the client ID or use the following procedure to view
the client ID:
a. Configure dynamic address allocation on the DHCP server's interface that is connected to the
client.
b. Ask the device administrator to power on the device.
c. Execute the display dhcp server ip-in-use command on the DHCP server to view the client ID of
the device after the device starts up.