WLC and DHCP for AP

Unanswered Question
Sep 30th, 2008

We have one 4402 and one WiSM in a 6513. I have been using the 4402 controllers internal DHCP to assign IP addresses to the APs. The other day we rebooted the 4402 running DHCP and started getting IP conflicts on the APs. Seems like after the reboot the internal DHCP didn't know what AP had what addresses. In time things settled back in.

Since then I have been thinking about switching to static IPs on the APs. I was going to leave a small pool just to prime the APs out of the box then give them static IPs. Should I be running more then one DHCP server and break up the AP subnets if I wanted a more stable DHCP enviroment?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
jwadleigh Tue, 09/30/2008 - 11:36

It's probably not necessary to run a second DHCP server. However, based on how large your deployment is, you might want to use your infrastructure DHCP server to assign IP's to the AP's. (More of a benefit to administration than to stability.)

I would suggest that you assign static IP's to all of your AP's though. In the event that the AP loses connectivity to the controller, the AP will come up that much faster when it restarts. It also helps troubleshooting to be able to recognize a given AP by IP address in a network trace file.

To set a static IP:

1.) Click on the Wireless tab from the WLC web interface.

2.) Click on the name of the AP that you want to edit.

3.) Click on the AP Static IP checkbox.

4.) Enter the IP, mask, and gateway info where prompted.

5.) Click the Apply button.

6.) If you're changing IP information for that AP, you will have to click on the AP name again, and at the bottom of the AP config screen, click the 'Reset AP now' button. NOTE: This will restart the AP and will cause a service interruption for any clients associated to that particular AP.

Hope this helps!


This Discussion



Trending Topics - Security & Network