HP 6125XLG R2306-HP 6125XLG Blade Switch Fundamentals Configuration Guide - Page 132

DHCP server configuration guidelines, TFTP server configuration guidelines

Page 132 highlights

• TFTP server-Stores files needed 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 DHCP server configuration requirements vary depending on whether the devices use the same configuration file: • If all devices that need to be automatically configured share the same configuration file, configure the dynamic address allocation mechanism on the DHCP server. To allow these devices to have some different configurations, you can put the configurations that the devices share to the configuration file and provide a way for device administrators to change the configurations after the 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 different devices need different configurations, configure the static address and parameter allocation mechanism on the DHCP server so the server assigns pre-configured IP addresses and parameters to the devices. With this method, you can configure all configuration items required for each device on the DHCP server. Before you configure a static binding for a device, you must obtain the client ID of the device. To do so, ask the device administrator to turn on the device and, after the device starts up, execute the display dhcp server ip-in-use command on the DHCP server to view the client ID of the device. After you complete the static binding configuration, ask the device administrator to turn off the device and then turn on it again so the device gets the IP address and configuration parameters you configured for it. TFTP server configuration guidelines You must configure the configuration files and host name files required for device automatic configuration on the TFTP server, including the default configuration file named device.cfg. To use the host name file network.cfg, configure a configuration file for each device on the TFTP server, name the file in the format host name.cfg, and configure a mapping entry in the format ip host host-name ip-address for the host name file. For example, you can configure the following entries for the host name file: ip host host1 101.101.101.101 ip host host2 101.101.101.102 ip host client1 101.101.101.103 ip host client2 101.101.101.104 If a device resides in a network different than the TFTP server, configure the UDP helper function on the gateway so the gateway changes the broadcast TFTP request from the device to a unicast packet and 125

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155

125
TFTP server
—Stores files needed 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
DHCP server configuration requirements vary depending on whether the devices use the same
configuration file:
If all devices that need to be automatically configured share the same configuration file, configure
the dynamic address allocation mechanism on the DHCP server. To allow these devices to have
some different configurations, you can put the configurations that the devices share to the
configuration file and provide a way for device administrators to change the configurations after
the 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 different devices need different configurations, configure the static address and parameter
allocation mechanism on the DHCP server so the server assigns pre-configured IP addresses and
parameters to the devices. With this method, you can configure all configuration items required for
each device on the DHCP server.
Before you configure a static binding for a device, you must obtain the client ID of the device. To
do so, ask the device administrator to turn on the device and, after the device starts up, execute the
display dhcp server ip-in-use
command on the DHCP server to view the client ID of the device.
After you complete the static binding configuration, ask the device administrator to turn off the
device and then turn on it again so the device gets the IP address and configuration parameters
you configured for it.
TFTP server configuration guidelines
You must configure the configuration files and host name files required for device automatic configuration
on the TFTP server, including the default configuration file named device.cfg.
To use the host name file
network.cfg
, configure a configuration file for each device on the TFTP server,
name the file in the format
host name
.cfg, and configure a mapping entry in the format
ip host
host-name
ip-address
for the host name file. For example, you can configure the following entries for the host name
file:
ip host host1 101.101.101.101
ip host host2 101.101.101.102
ip host client1 101.101.101.103
ip host client2 101.101.101.104
If a device resides in a network different than the TFTP server, configure the UDP helper function on the
gateway so the gateway changes the broadcast TFTP request from the device to a unicast packet and