No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


DHCP Users Connected to an ME60 Failed to Go Online Because IP Address Conflict

Publication Date:  2013-09-30 Views:  59 Downloads:  0
Issue Description

Version: V600R005C00SPC600

Networking: User --- ME60 --- DHCP server


Users failed to go online because of IP address conflict.
Handling Process

Possible causes include:

1. The ME60 did not process the DHCP procedure properly.

2. The ME60 and the DHCP server did not cooperate properly.

Huawei performed the following operations to address the problem:

Checked the ME60 configurations and found that a remote address pool was configured on the ME60.

dhcp-server group vod
ip pool vod-04 bas remote
 dhcp-server group vod

The address of a user was obtained from the remote address pool. When not receiving any lease extension request from the user, the DHCP server released the address upon the lease expiry. However, the ME60 functioning as a DHCP relay did not provide the lease management function for the remote address pool. Therefore, the ME60 kept the table entry for a user that did not send lease extension requests to the DHCP server but responded to the ARP detection packets from the ME60 even after the user's address had been released by the DHCP server. The DHCP server then allocated the address to another new user. Because the ME60 did not release the previous user that used the address (ARP detection was responded), the new user failed to go online because of an IP hash conflict.
Root Cause

The problem occurred when the following conditions were met:

1. The ME60 served as a DHCP relay agent.

2. The user did not send any lease extension request.

3. The user properly responded to the ARP detection packet from the ME60.

4. The IP address allocated by the DHCP server to a new user was the same as that of the previous user.
Configure dhcp conflict-ip-address offline to resolve the problem.