Introduction

Dynamic Host Configuration Protocol (DHCP) is a protocol that dynamically configures and centrally manages the network parameters of the hosts based on TCP / IP protocol, which can be used to:

• Dynamically assign IP addresses to network hosts. Assign an IP address to a host via DHCP with an expiration time (often called a lease time). The default lease time is one hour.

• Provide other network parameters for network hosts, such as the IP address of the DNS server, domain name information and default gateway address.

Configuration Notes

Pay attention to the following points when configuring DHCP server:

• Enabling DHCP client, DHCP relay or DHCP server functions in block VLAN is not supported.

• Enabling DHCP client, DHCP snooping/relay and DHCP server functions in the same VLAN is not supported. Where DHCP snooping and DHCP relay don’t have this limitation, they can be enabled in the same VLAN.

• Enabling both DHCP relay and DHCP server functions in the same VRF is supported.

• If both DHCP server and DHCP relay are deployed on the same switch, don’t use the VLAN interface enabled with DHCP server to connect to the remote DHCP server.

• DHCP server feature supports only IPv4, and doesn’t support IPv6.

• DHCP server supports VRF by binding the address pool and the VLAN interface (which is connected to the DHCP client side) to the same VRF.

• One VRF will run a DHCP server instance. So different VRFs will have different DHCP server instances.

• In each VRF, at most 1000 DHCP clients are allowed. 

• Multiple address pools can be configured in the same VRF, but there cannot be address overlap between individual pools. However, address pools in different VRFs do not have this restriction.

• When multiple address ranges are configured under one address pool, there should be no address overlap between these ranges.

• The default router is the default gateway of the DHCP client, which is required to be on the same network segment as the address pool.

• In a VRRP topology, if the DHCP server function is enabled, the address pool configured on the master cannot overlap with that configured on the backup switch.

• Adding, deleting and modifying any parameter in the DHCP address pool will result in the deletion of DHCP server binding table in this VRF.

Configuring DHCP Server

Procedure

Step 1        Create an address pool and specify the IPv4 network segment that can be dynamically allocated to the DHCP clients.

Step 2        Configure the VLAN interface connected to the DHCP client.

Step 3        (Optional) Associate the VLAN interface with a VRF.

Step 4        (Optional) Configure the lower and upper boundaries of an address range in the address pool.  

Step 5        (Optional) Configure a lease time for the IP addresses in an address pool.

Step 6        (Optional) In a DHCP relay scenario, the following command needs to be used to enable the DHCP server function on the Layer 3 interface.

Step 7       (Optional) Configure the IP address of the DNS server and domain name for the DHCP address pool.

Step 8        (Optional) Configure a default gateway address for the DHCP clients.

Step 9        (Optional) Assign a DHCP address pool to a VRF.

                  set protocols dhcp server pool <pool-name> vrf <vrf-name>

Step 10      (Optional) Configure the IP address for the TFTP server. After the client sends request packets to the DHCP server, the TFTP server with this IP address will be replied.

Step 11      (Optional) Configure the IP address for the Syslog server. After the client sends request packets to the DHCP server, the Syslog server with this IP address will be replied.

Step 12      (Optional) Configure the file name with path on the TFTP server or the file name with URL on the HTTP server. After the client sends request packets to the DHCP server, the file name with path or URL will be replied.

Step 13      (Optional) Configure the file name with path on the TFTP server or the file name with URL on the HTTP server. After the client sends request packets to the DHCP server, the file name with path or URL will be replied.

Configuration Example

Networking Requirements

Figure 1. DHCP Server Configuration Example

Open

As shown in Figure 1, an enterprise has planned two network segments for the office terminals. PCs in the network segment 10.1.10.0/24 are the fixed terminals, and the network segment 10.2.10.0/24 is used for temporary users accessing to the network. To facilitate unified administration, the enterprise terminals can automatically obtain IP address and DNS server address from the DHCP server.

By configuring DHCP server on Pica8 switch, IP address and DNS server address can be dynamically assigned to the terminals in the two separate network segments of the enterprise. Among them, the PCs in network segment 10.1.10.0/24 are the fixed office terminal, and the IP lease time is 30 days; the network segment 10.2.10.0/24 provides temporary accesses to the network for business travelers, and the IP lease time is 2 days.

Procedure

Step 1       Configure the VLAN interface connected to the DHCP client.

Step 2       Create two address pools and specify the IPv4 network segment that can be dynamically allocated to the DHCP clients.

Step 3       Configure the lease time for the IP addresses in the address pool.

                  By default, the IP address lease is one hour.

Step 4       Configure the IP address of the DNS server and domain name for the DHCP clients.

                  By default, no DNS server is configured in an address pool.

Verify the Configuration

• The IP address and DNS server address of the 10.1.10.0/24 network segment can be obtained from the DHCP server by the PCs in the zone of DHCP client A, and the IP address and DNS server address of the 10.2.10.0/24 network segment can be obtained from the DHCP server by the PCs in the zone of DHCP client B.

• Run the command run show dhcp server binding on the switch to view the allocated IP address binding information.