HP 6125G HP 6125G & 6125G/XG Blade Switches Fundamentals Configuration - Page 125

Automatic configuration, Typical application scenario

Page 125 highlights

Automatic configuration Automatic configuration enables a device without any configuration file to automatically obtain and execute a configuration file during startup. Automatic configuration simplifies network configuration, facilitates centralized management, and reduces maintenance workload. To implement automatic configuration, the network administrator saves configuration files on a server and a device automatically obtains and executes a specific configuration file. Typical application scenario Figure 43 Network diagram As shown in Figure 43, the device implements automatic configuration with the cooperation of the following servers: • DHCP server-Assigns an IP address and other configuration parameters such as the configuration file name, TFTP server IP address, and DNS server IP address to the device. • TFTP server-Saves files needed in automatic configuration. The device gets the files needed from the TFTP server, such as the host name file that saves mappings between host IP addresses and host names, and the configuration file. • DNS server-Resolves between IP addresses and host names. In some cases, the device resolves its IP address to the corresponding host name through the DNS server, and then uses the host name to request the configuration file with the same name (hostname.cfg) from the TFTP server. If the device gets the domain name of the TFTP server from the DHCP response, the device can also resolve the domain name of the TFTP server to the IP address of the TFTP server through the DNS server. If the DHCP server, TFTP server, DNS server, and the device are not in the same network segment, you need to configure the DHCP relay agent on the gateway, and configure routing protocols to enable each server and the device to reach one another. 119

  • 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

119
Automatic configuration
Automatic configuration enables a device without any configuration file to automatically obtain and
execute a configuration file during startup. Automatic configuration simplifies network configuration,
facilitates centralized management, and reduces maintenance workload.
To implement automatic configuration, the network administrator saves configuration files on a server
and a device automatically obtains and executes a specific configuration file.
Typical application scenario
Figure 43
Network diagram
As shown in
Figure 43
, the device implements automatic configuration with the cooperation of the
following servers:
DHCP server
Assigns an IP address and other configuration parameters such as the configuration
file name, TFTP server IP address, and DNS server IP address to the device.
TFTP server
Saves files needed in automatic configuration. The device gets the files needed from
the TFTP server, such as the host name file that saves mappings between host IP addresses and host
names, and the configuration file.
DNS server
Resolves between IP addresses and host names. In some cases, the device resolves its
IP address to the corresponding host name through the DNS server, and then uses the host name to
request the configuration file with the same name (
hostname.cfg)
from the TFTP server. If the device
gets the domain name of the TFTP server from the DHCP response, the device can also resolve the
domain name of the TFTP server to the IP address of the TFTP server through the DNS server.
If the DHCP server, TFTP server, DNS server, and the device are not in the same network segment, you
need to configure the DHCP relay agent on the gateway, and configure routing protocols to enable each
server and the device to reach one another.