Anchor WLC stops giving DHCP addresses

Answered Question
Oct 26th, 2011
User Badges:


We are running Cisco WLC as our foreign WLC and anchor WLC in the DMZ. Usually, all is fine but we observe sometimes that client cannot obtain dhcp address anymore. The DHCP server configured is the management interface of the anchor WLC and it works well except that sometimes, is stops working.

The clients are listed as associated client on the Anchor WLC but their status is DHCP REQ.

Sometimes, a reboot is required, sometimes it re-works few hours later without any intervention.

When it happens, we can see dhcp request reaching the Anchor WLC but it is like if no reply is sent.

Has anyone observed such behavior already ?

Thanks in advance,


Correct Answer by Surendra BG about 5 years 9 months ago


Here is the software bug on the WLC software code that we are running!!

Please upgrade the WLC to the latest code that we have and this will resolve the issue!!

Please dont forget to rate the usefull posts!!


  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
david_mayor Wed, 10/26/2011 - 23:50
User Badges:


Thank you so much for your reply ! It was since several weeks that I look for any bug or anyone with that problem.

We will update our WLC very soon then.

Thanks a lot,


Surendra BG Wed, 10/26/2011 - 23:52
User Badges:
  • Cisco Employee,

Lemme know if u need any kinda assistance and i will be more than happy to assist you!!



david_mayor Fri, 11/18/2011 - 00:56
User Badges:


I still have some problems. But it is even more strange because an SSID works perfectly while another one keeps clients in DHCP_REQD mode.

This does not make sense because the two SSID's share the same dhcp pool on the anchor WLC and both have the same mobility anchor to the same Anchor WLC.

We are using for foreign WLC and for anchor WLC.

Can anyone help me ?

Thanks a lot.

Oscar Jaime Fri, 11/18/2011 - 05:58
User Badges:

I had the same problem with different earlier code versions and decided to go to an external DHCP server and never saw the problem again. I didn't get to try with latest 7.x code, tough.


This Discussion

Related Content



Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode