DHCP clients on S series switch cannot detect IP address conflicts

35

Before a DHCP client binds an obtained IP address to a VLANIF interface, it proactively sends a gratuitous ARP packet to check for IP address conflict. The VLANIF interface does not have an IP address, so its protocol status cannot go Up. When the physical interface in the corresponding VLAN receives the gratuitous ARP packet with the conflicting IP address, it cannot send the packet to the CPU. As a result, the DHCP client cannot detect IP address conflict.
To resolve this problem, configure the dhcp server ping function on the DHCP server to check for IP address conflict. When there is a large number of DHCP clients, this function requires a high cost, so you need to decide whether to use this function after thorough consideration.

Other related questions:
DHCP client cannot detect IP address conflict
A DHCP client sends gratuitous ARP packets to check whether addresses conflict after obtaining an IP address and before binding an IP address to the VLANIF interface. However, the VLANIF interface cannot go Up because the VLANIF interface has no IP address. As a result, the physical interface corresponding to the VLANIF interface cannot send gratuitous ARP packets with conflicting IP addresses to the CPU. The DHCP client cannot detect the conflicting IP addresses. You can configure the DHCP server ping function on the DHCP server to check IP address conflicts. However, when there are many DHCP clients, the cost is high. You need to use it with caution through evaluation.

Detect IP address conflicts on S series switch
On an S series switch, except S1700: When the IP addresses of two network devices conflict, the CPU usage on the switch becomes high and route flapping will occur on the switch. User services may be interrupted. To manage IP addresses efficiently and detect IP address conflicts promptly, enable IP address conflict detection. The switch can record logs for IP address conflicts. The configuration procedure is as follows: 1. Run the system-view command to enter the system view. 2. Run the arp ip-conflict-detect enable command to enable IP address conflict detection. By default, IP address conflict detection is disabled. 3. Run the display arp ip-conflict track command in any view to check IP address conflict records.

How to resolve DHCP IP address conflict on S series switch
For S series switches (except S1700 switches), if IP addresses in a DHCP address pool have been configured for clients but have not been excluded from the address pool, the IP addresses may be allocated to other clients, resulting in IP address conflicts. For details about how to locate and rectify the IP address conflict problem, see "The IP Address Obtained by a Client Conflicts with the IP Address of Another Client" in Configuration Guide - IP Service.

Solution to the problem of conflicting DHCP addresses on S series switches
For S series switches excluding the S1700, the IP address obtained by a client conflicts with that of another client. The possible cause is that the IP address of another host has been manually configured and the DHCP server does not delete the IP address from the address pool.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top