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>Search


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


IP address conflict on BRAS

Publication Date:  2013-12-31 Views:  123 Downloads:  0

Issue Description

Some users can't get online when ME60 acts as DHCP server.

Handling Process

Check whether authentication passes for these users or not? (use command test-aaa). Authentication passes successfully.
Check whether IP address is allocated by IP pool. Is there available IP addresses in IP pool:

< ME60_1>dis ip pool


 IP address Statistic

    Total       :46042

    Used        :44835      Free      :9

    Conflicted  :1115       Disable   :83
There are too few IP addresses in IP pool.
But there are many conflicted IP addresses that can't be used.

Root Cause

In the scenario where the ME60 servers as the DHCP server, when detecting that an address in the address pool is being used but not assigned by itself, the ME60 sets the address to the conflict state so that the address is not to be assigned later. This prevents IP address conflict. The ME60 sets some addresses to the conflict state and does not automatically delete them. In this manner, several IP addresses may be in the conflict state after a period of time. This decreases available IP addresses. Thus, users cannot obtain IP addresses to get online.


To solve this problem, you can use the "reset conflict-ip-address" command to delete those IP addresses in the conflict state.

Make ME60 do not set these conflict ip address as conflict flag, instead, ME60 still make it idle flag,

which means these ip address still usable, so the conflict ip address won’t be more and more in the ip pool.

 [ME60]dhcp-decline ip-address-status ?

  conflict  set IP address status to conflict (default)

  idle      set IP address status to idle