H3C Technologies H3C S10500 Series Switches - Manual (Page 46)

35
DHCP server configuration
Introduction to DHCP server
Application environment
The DHCP server is well suited to networks where:
• Manual configuration and centralized management are difficult to implement.
• Many hosts need to acquire IP addresses dynamically. This may be because the number of hosts
exceeds the number of assignable IP addresses, so it is impossible to assign a fixed IP address to
each host. For example, an ISP has a limited number of host addresses.
• A few hosts need fixed IP addresses.
NOTE:
In addition to assigning IP addresses to DHCP clients on public networks, a multi-VPN-instance customer
edge (MCE) serving as the DHCP server can also assign IP addresses to DHCP clients on private networks.
Note that the IP address ranges of public and private networks or those of private networks on the DHCP
server cannot overlap each other. For more information about MCE, see the MPLS Configuration Guide.
DHCP address pool
Address pool types
DHCP address pools include common and extended address pools.
• Common address pool: Supports both static binding and dynamic allocation.
• Extended address pool: Supports only dynamic allocation.
Common address pool structure
The common address pool database is organized as a tree. The root of the tree is the address pool for
natural networks, branches are address pools for subnets, and leaves are addresses statically bound to
clients. For the same level address pools, a previously configured pool has a higher selection priority than
a new one.
At the very beginning, subnets inherit network parameters and clients inherit subnet parameters.
Therefore, common parameters, for example a DNS server address, should be configured at the highest
(network or subnet) level of the tree.
The new configuration at the higher level (parent) of the tree will be:
• Inherited if the lower level (child) has no such configuration, or
• Overridden if the lower level (child) has such configuration.