Wireless Access

after the upgrade to version 6.1.2.6 we are experiencing this error

Module DHCP Daemon is busy. Please try later

 

killing the proccess with 

process restart dhcpdwrap

didn't helped either .

 

any suggestions ?

---

@kdisc98 wrote:

after the upgrade to version 6.1.2.6 we are experiencing this error

Module DHCP Daemon is busy. Please try later

 

killing the proccess with 

process restart dhcpdwrap

didn't helped either .

 

any suggestions ?

---

How many devices are you providing DHCP for?  The built-in DHCP server is only meant for small guest networks. 

 

 

We have seen this happen with ver 3.3.3.2, so it's not a version issue.  It only happens when the DHCP pool gets full and requests keep coming.

 

To resolve it:

 

1. confi ter

2. clear ip dhcp binding

 

 

---

@salvi wrote:

We have seen this happen with ver 3.3.3.2, so it's not a version issue.  It only happens when the DHCP pool gets full and requests keep coming.

 

To resolve it:

 

1. confi ter

2. clear ip dhcp binding

 

 

---

NOOOOOOOO!

 

If you clear ip dhcp binding, you will have alot of clients that already have ip addresses that will be given out again by the DHCP controller.  You should first make sure that you are not passing 250 clients in the first place, because the internal DHCP server is only for small deployments.

 

If you have less than 250 clients and you are getting that message, you need to open a TAC case.

 

What we have seen in the real world is that the DHCP server will not release the IP bindings.  By releasing the bindings it will be able to release new IP addresses again to requesting users.

100% agree with Colin, you need to get an external DHCP server. Clearning the binding is a bad idea, because the server is going to start handing out the same addresses that are already in use. 

 

The mobilty controller DHCP server was never meant to be something that would be used in a large network, it was there to get you going, help out with setup, etc.. If you have a Windows server you should really move to that, other wise an inexpensive Linux or BSD box is your best bet. You can probably run it off an older server you have sitting around. 

 

-awl

True, but when you have users calling the Help Desk with issue you cannot say that it will be fixed once you configure and setup a DHCP servers for each seperate site that the issue is happening. The conected clients will lose connection and will have to reconnect, but this is only guest access.

 

What would be the recommended network setup with a master and multiple local controllers that are all using the internal DHCP server,but you want to migrate all off to an external DHCP server that is located in a centralized location?

Okay, but what about the connected clients?

The long term solution is to use an external server.

Okay, but what about the connected clients?

The long term solution is to use an external server.

The use who started this thread had a question about dhcp and a single controller. That is the question we are answering. The answer is an external dhcp server.