WLC DHCP issue with 6500

Hi,
I configured WLC as DHCP server and is working fine when connected to 3750 core switch. The AP's and clients are getting IP address.
When the same WLC is connected to 6500 , the DHCP is not working from WLC . The same port of 6500 switch is verified by connecting a 3750 switch as dhcp server and AP as well as clients are getting IP.
DHCP snooping and port security is not enabled in the 6500 and the configuration is simple. The WLC is untagged and the 6500 port is a trunk port with 242 as native VLAN.
Please help

Dear Surendra,
Please see the answers in line.
1.As per your previous post, if we connect WLC to 3750 core everything works fine.. so in this case, i assume that we have INTERFACE VLAN on the switch and then the management interafce on the WLC are in the same subnet?? correct??
"Yes , All are in the same Vlan . Interface VLAN and management interface are in same subnet."
2. Similarly, if we swap the 3750 with 6500, it doesnt work.. in this case.. have you created the interface vlan on the 6500 in the same subnet as that of management interface of the WLC??
" Yes, the 6500 has vlan interface without IP. The same way we configured 3750 "
Or
3.are we not swapping the 6500 and we are connecting the WLC to the WLC to the 6500 and then this 6500 to the 3750??
"We connected WLC LAP to 3750 and the dhcp of wlc is working fine.. When WLC & AP connected to 6500 , the WLC DHCP is not working. We verified the 6500 port by coonecting 3750 as DHCP server and WLC is connected to 3750 and all were working fine. When WLC is directly connected to 6500 , the LAP is not joing to WLC. When static IP is given to LAP, the LAP joined WLC but the clients were not getting IP."
4.Layer 2 means... interface VLAN on the switch and the WLC management and the AP DHCP pool are all in the same subnet. correct?
"Yes all are in the same subnet"
Thanks for your efforts.
Regards,
Savad

Similar Messages

10.5 DHCP issues with Wireless - self assigned IPs?

We're having an issue with Mac OSX 10.5.4 clients, running the latest software updates, not getting an IP address via DHCP on our wireless network.
We're using Cisco APs, with multiple VLANs & SSIDs. They authenticate, but get automatic self-assigned IP addresses. None of our PC clients are experiencing this issue, nor older 10.4.x OSX clients. This looks like a bug, from what I was able to discover:
http://forums.macrumors.com/showthread.php?t=384947
Is Apple aware of this, and/or working on a fix? I've seen many issues over the last year or so with Airport clients and wireless connectivity..

This is a "user to user" help forum that is designed as a self-help system, independent of Apple's Technical Support system. No one here can say what Apple knows or is doing about a specific issue (pure speculation is discouraged). We share experience and suggest possible solutions or workarounds.
One way to ensure that your issue is brought to Apple's attention is to use their feedback form for OSX - http://www.apple.com/feedback/macosx.html
Since the link you posted is from late last year, there have been many updates to Leopard. Some of the updates mention network reliability. Even though Apple has stated that the Pram chips don't control network connections, I have had some luck by Zapping The Pram - http://support.apple.com/kb/HT1379 - Remember to check your System Prefs for things like date/time settings after you Zap.

Client DHCP issues with 4400 WLC

Authentication to ACS working okay.
Clients are unable to obtain an IP from DHCP.
DHCP server is configured on a dynamic interface but is on a different subnet located in a branch office. DHCP scope is running on a 4500 switch in the branch.
Is it preferable to have DHCP running on the internal WLC or a DHCP server close to the WLC rather than at the remote location?
TIA

Usually you don't want to have a dhcp server on a remote site, but it also should work as long as wired users are able to obtain an IP from the remote dhcp server. Preferred, like I said is to have a local dhcp, but if that doesn't work for you, then configuring the wlc to bbe a dhcp isn't a bad think either. Some like to have more control over the dhcp.

DHCP issue with mobility anchor

Hi Guys,
I am having a bit of trouble to get the DHCP to work in my configuration. basically I have configured one SSID on two WLCs (running same version of code), I configured WLC 1 as anchor controller and configured itself as mobility anchor (local), and on foreign controller (WLC2), I have configured the anchor as a mobility anchor. I have added both of the WLCs in each other's mobility list, however WLC1 and 2 are not in the same mobility group. clients are getting IP address through an external DHCP server.
the problem is that when I used the management interface for the WLAN, I could get IP address through DHCP without any problem, however if I use another dynamic interface created for the SSID, then I could not get IP address anymore. I did another test with two WLCs configured in the same mobility group, then everythnig works fine. I have double checked my configuration for the dynamic interface but could not find anything wrong.
so my question is
is it possible to do auto anchoring configuration with two WLCs in different mobility group (different mobility group name), since based on my test management interface works, but another dynamic interface did not work. in the configuration guide, it says: "you must add controllers to the mobility group member list before you can designate them as mobiolity anchors for a WLAN", does that mean the mobility group name has to be the same for both of the WLCs? if that's the case why does management interface worked?
thanks in advance for you help.

Hi Nicolas,
thanks for your reply, i guess that's where the problem is - I could not ping the dynamic interface from the DHCP server. (eping and mping works fine)
however I could ping the dynamic interface of the foreign controller (i have created another dynamic interface on the same subnet on the foreign controller, i understand it's not really necessary since we getting IP in the range defined on the anchor controller). the only difference between the two controllers is that the foreign controller enabled LAG, and only connected to the core swithc number 1, but the anchor controlelr is not (it has two connections to two core switches respectively).
so does this mean I can not use this controller to be a anchor controller if it has two connections to two differnet switches? if yes is there any documentation on this point?
Thanks very much for your help.

DHCP issues with Cisco WAP 321

I have 4 Cisco WAP 321's in my office connected to our Cisco 2911 ISR for DHCP, everything is fine on the office wifi on vlan 1 but vlan 3 with the guest wifi network it fails to obtain an IP address. I have tried under each of the WAPs to make sure it wasnt just the one nearest my desk. I was on the phone yesterday with Cisco about this and we turned on debugging and watched the DHCP requests and no requests even hit the ISR (only thing I have smartnet support on). I noticed our firmware was a few versions old so updated that this morning but still have the same issues so now I am turning to you all to help me figure this out.
Thanks
Jake
This topic first appeared in the Spiceworks Community

I have 4 Cisco WAP 321's in my office connected to our Cisco 2911 ISR for DHCP, everything is fine on the office wifi on vlan 1 but vlan 3 with the guest wifi network it fails to obtain an IP address. I have tried under each of the WAPs to make sure it wasnt just the one nearest my desk. I was on the phone yesterday with Cisco about this and we turned on debugging and watched the DHCP requests and no requests even hit the ISR (only thing I have smartnet support on). I noticed our firmware was a few versions old so updated that this morning but still have the same issues so now I am turning to you all to help me figure this out.
Thanks
Jake
This topic first appeared in the Spiceworks Community

WLC 2504 - Issue with using Microsoft NPS for Radius Management Login

Hello,
In our environment we like to have our network admins and engineers use their Active Directory credentials when logging into devices so we can log who logged into which devices and if any changes were made. To do this we use a Server 2008 R2 NPS server with all our routers, switches and ASA's. We recently purchased a WLC to begin adding wireless to our environment. (See WLC_Radius_Config.png and NPS_Radius_Config.png)
On the WLC, I am able to authenticate in using my AD credentials but when I go to apply any config changes I get a message saying "Authorization Failed. No sufficient privileges." (See error.png) I have a feeling I am missing something small but this is very important to us.
I checked the Radius server and there are no login errors or NPS errors pointing to the WLC logins. Has anyone else run into this issue or know what I can do to solve it?
Thanks,

Hi Kyujin,
I wish I had finished my guide. Didn't realize it would take this long.
But what I meant is that when adding the attributes to my NPS (Microsoft's Network Policy Server) I only had to add the role and virtual domain if using Prime Infrastructure.
If you use NCS, you have to add the role, all the tasks, and the virtual domain.
See the screenshots and see if that helps explain it. Not sure how TACACS will work as I'm not familiar with it.
Microsoft NPS - Attributes for NCS
Microsoft NPS - Attributes for PI

DHCP issues with Time Capsule

When I connect my MBP via direct ethernet cable, I have no issue. However, when I connect my Time Capsule to the modem and try and connect using wifi I do not get any joy.
The cable modem I use come from TekSavvy in Canada and seems to function correctly when connecting my MBP directly. However, the Time Capsule does not connect. I have used the Airport Utility and it looks as though the IP address shown is wrong -- I have renewed the DHCP lease when connected by ethernet -- and I wonder if that is problem. When I use the edit function, there is a button to renew the DHCP lease but when I click it nothing seems to happen.
This set up was working without issue two days ago. I woke up to find that my modem was not 'provisioning'. I called my ISP who have cleared that error but now I can not connect through my Time Capsule.
Any thoughts?
E

This set up was working without issue two days ago. I woke up to find that my modem was not 'provisioning'. I called my ISP who have cleared that error but now I can not connect through my Time Capsule.
Any thoughts?
This was looking pretty easy and standard problem until this point... ahhh... why do things work and then stop working.. hard to say. Cable being a fairly mysterious thing at the best of times.
Several things matter..
Did it work only only one computer.. when it was working, were you able to have several devices connected.. if you only tested with one, it could have always been wrong.
I need you to clarify...
When I connect my MBP via direct ethernet cable, I have no issue. However, when I connect my Time Capsule to the modem and try and connect using wifi I do not get any joy.
Direct ethernet cable to the Modem or to the TC??
When you swap over and plug the TC into the modem, are you power cycling the modem.. this is essential unless the modem is also working as a router.
Tell us modem model and if you know which it is .. modem or router and if running in router mode.. otherwise tell us the IP you get when you plug the MBP into the modem by ethernet.. assuming that is the case.
Power cycle the modem for at least 20min whenever you swap.. some ISP will accept less.. 5min.. and some require more, several hours. Check with the ISP for time required.
What model TC and is it in router mode?
What firmware is it running?
I have renewed the DHCP lease when connected by ethernet -- and I wonder if that is problem. When I use the edit function, there is a button to renew the DHCP lease but when I click it nothing seems to happen.
Please post a screenshot of the IP you get.. or tell us the details.. You can blank out or cover the last numbers if you are actually getting public IP.. but if private IP leave it.. as it is irrelevant if you post it.

WLC 5508 issue with 4 ports in portchannel

Hi,
We have one WLC 5508 and LAG is enabled on it but when we connect 4 cables to a distribution switch only 3 links are sending and receiving traffic and the 4th one is up with outgoing traffic from the distribution switch to WLC but nothing incoming.
Some APs went down and refuse to be registered back to the WLC. when we shut down the 4th port everything is back to normal.
the etherchannel config is identical and I can see all ports are active and not suspended :
interface GigabitEthernet2/2/1
description PortChannel-WLC1-Port1
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 60-67,2808,2922,2923,2932
switchport mode trunk
channel-group 99 mode on
interface GigabitEthernet2/2/2
description PortChannel-WLC1-Port2
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 60-67,2808,2922,2923,2932
switchport mode trunk
channel-group 99 mode on
interface GigabitEthernet2/2/3
description PortChannel-WLC1-Port3
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 60-67,2808,2922,2923,2932
switchport mode trunk
channel-group 99 mode on
interface GigabitEthernet2/2/4
description PortChannel-WLC1-Port4
switchport
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 60-67,2808,2922,2923,2932
switchport mode trunk
channel-group 99 mode on

sh etherchannel 99 sum
Flags: D - down        P - bundled in port-channel
        I - stand-alone s - suspended
        H - Hot-standby (LACP only)
        R - Layer3      S - Layer2
        U - in use      N - not in use, no aggregation
        f - failed to allocate aggregator
        M - not in use, no aggregation due to minimum links not met
        m - not in use, port not aggregated due to minimum links not met
        u - unsuitable for bundling
        d - default port
        w - waiting to be aggregated
Number of channel-groups in use: 38
Number of aggregators:           38
Group Port-channel Protocol    Ports
------+-------------+-----------+-----------------------------------------------
99     Po99(SU)         -        Gi2/2/1(P)     Gi2/2/2(P)     Gi2/2/3(D)
                                 Gi2/2/4(P)
Last applied Hash Distribution Algorithm: Fixed
Gi2/2/3 is down becasue we had to shut down the interface because when it is up many APs refuse to register.

DHCP issue with Airport Express??

HI again, another home networking on a budget question for you all:
I want to create a home network with 2 seamless wireless access points and 2 wired points in two different rooms, on a budget of...well whatever I have my hands on right now. I want to be able to heavily use iTunes Home sharing as well as regular family home internet access.
Here is my setup:
DSL signal to Actiontec Modem/Router
From Actiontec, I broadcast Wifi, and connect a Mac G4 via ethernet, and a second ethernet line uses a powerline adapter to get signal to a Westell router/modem on the other end of the house (small house)
From Westell I connected a PC with no Wifi via ethernet and an Airport Express to broadcast the Wifi
Here are the settings changed from default:
Actiontec: changed ip range to start at 192.168.1.4
changed Wifi name and password
Westell: assigned static IP 192.168.1.2
disabled Wifi (doesn't have the same encryption)
Disabled DHCP (unchecked Private LAN DHCP Server enable)
Airport Express (1st Gen single band)
Wireless Mode: Create a Wireless Network
same Wifi name, password and encryption as Actiontec
Connect Using Ethernet
Connection Sharing:Off, Bridge Mode
Assigned static IP (not sure if I needed to) 192.168.1.3
(configure IPv4:Manually;IP address 192.168.1.3; router address 192.168.1.1; DNS server fields are blank and domain name is blank)
After hooking it all up, programming them all, I powered all the devices down and turned them on Actiontec first, then Westell, then AX.
Problems:
#1 Everything works fine until I plug in the Airport Express. Then ethernet still functions. However, I came home to an IP address conflict on my G4. Wifi will connect on SOME devices. An iPad connected fine, my iPhone 2 inches away would connect but never get a network signal and no internet;it stayed on cellular. As soon as I unplug the AX functionality is resumed but I don't get WiFi out as far as I'd like. Plus I am using it as a Print Server so I dont have to keep a computer on but I havent even attached that one yet.
#2 I can never seem to get all of my libraries to show up on HOme Sharing with iTunes. Specifically the PC connected to the Westell is missing even with the AX disconnected.
What did I miss??
Thank you for reading!!
Joey

Do I need to direct the AX to the 192.168.1.1 for DHCP or is it automatic? If so where?

6500 DHCP ISSUE

Hello All,
I am having an issue do DHCP from the 6500, and was hoping someone cant help. So, I tried to setup DHCP from the FWSM to the clients and this worked fine with giving out the IP, however the gateway for devices on the inside is supposed to be the 6500, not the FWSM, which is why the clinets wouldn't get out to the internet. Do I need to set up DHCP relay on the FWSM or does anyone know the way I can setup DHCP on the 6500 to give out IP's to the clients. Again just to reiterate, when I setup DHCP on the FWSM the clinets get the IP's but do not get out to the internet and when I setup DHCP on the 6500 the clients do not get an IP. Also I know tghis is a dhcp issue becasue when I assign a static address on the network the clients get out fine. Thanks in advance for the help!
6500 Config
ip dhcp pool TEST
   network 1.1.1.0 255.255.255.0
   default-router 1.1.1.1
   dns-server x.x.x.x y.y.y.y
FWSM Config
FWSM/TEST# show run
interface Vlan3
nameif outside9
bridge-group 1
security-level 0
interface Vlan203
nameif inside9
bridge-group 1
security-level 100
interface BVI1
ip address 1.1.1.4 255.255.255.0
passwd 2KFQnbNIdI.2KYOU encrypted
access-list INSIDE1_IN extended permit ip any any
global (outside1) 1 x.x.x.x
nat (inside1) 1 1.1.1.0 255.255.255.0
access-group INSIDE1_IN in interface inside1
route outside1 0.0.0.0 0.0.0.0 1.1.1.1 1
FWSM/TEST#

Hello Alain,
Thanks for your quick response. I attached a Diagram of the layout. Just to let you know this is an FWSM with many virtual contexts and most including this one that are Transparent. I understand that I need an access-list on both ends to specifiy so the FWSM opens it, I am just having issue because the FWSM sees this as unsual traffic and the access-list needs to be on-point to work. Thank you for the response and I'll look forward to hearing back from you.

Cisco WLC DHCP upgrade issues

Hi,
I've discovered an issue with our WLC 4400 series controllers when we do firmware upgrades (recently moved to 6.0.199) it seems to reset the dhcp server on the controller but the Access points still retain their old IP until the lease runs out (48hrs). This means that any AP's requesting a new lease often get an IP conflict for the first 48hrs after the upgrade and we experienced areas where AP's wouldnt connect.
Is this a common issue and is there anyway to get the AP's to request a new address from the controller?
thanks,
Matt

Hi Matt,
When you do a WLC upgrade, a WLC reboot is required, this results in the DHCP lease table getting restarted as well.
Solution:
1-Setup an external DHCP Server to overcome this.
2- Restart the access points, so they request a new IP address.
This is mentioned on WLC release notes 6.0.199.0 that you are running, it is for clients, for the rule still applies:
Link
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn6_0_199.html#wp581125
Internal DHCP Server
When clients use the controller's internal DHCP server, IP addresses are not preserved across reboots. As a result, multiple clients can be assigned the same IP address. To resolve any IP address conflicts, clients must release their existing IP address and request a new one.
The same also applies on newer releases such as 6.0.199.4 and 7.0.
Have a good day.
Serge

Nokia 6500 on 3 - known issue with signal recepti...

Does anyone know if Nokia and 3 have yet developed a fix for the known issue with 3 reception on the 6500?
I just spent close to two hours talking to 3 about this. We got a 6500 "upgrade" from 3 and have discovered that the phone doesnt work anywhere around our home, or the locality of our home. We have reverted to a 4 year old 6680 from the back of our wardrobe which will show 4 bars of signal when the brand new 6500 shows no signal at all.
3 advised that very poor ability to get a signal is a known issue with this phone, however as we did not report it to 3 within the 14 day period they expect us to stay out the contract or pay a near £400 termination fee. (or take a much inferior phone which is "the only model we are authorised to offer as a replacement"). (The reason we didnt report it was that as we had been happy with our existing model we didnt swap the sim card over straight away. When we did discover it we tried 3's suggestion of upgrading the firmware (the phone arrived with a 2007 version) but this did nothing to help.
What really bugs me is that 3 contacted us in September and spent close to an hour an the phone persuading us to upgrade to the 6500. That's five months at least after it was a known issue and being worked on by Nokia and 3. (There are posts within this Support Forum discussing the issue that go back to April at least.)
I will be reporting 3 to trading standards but am curious as to what progress has been made (if any) on sorting this issue out?
I also thought it may be useful for others to be aware of as it will allow them to make a more informed decision about the phone, and about 3's attitude to their customers. We have been with them for over 5 years.
At one point, when I told the manager/supervisor that I had become aware of the fact that it was an issue that was well-known 5 months before 3 persuaded us to upgrade, he suggested that it was out fault for not researching the web and forums well enough, and that I should have discovered this before agreeing to take the phone.
Amazing.
Be warned!!!!!
Stormy

Hi all - sorry I stopped monitoring the thread in the run up to christmas but thanks for your replies.
shumboy, redroxy, roslily, ginger25
very sorry to hear you are all experiencing the same problems and that 3 are as unhelpful with you as they were with us. my guess is that the problem with this phone is so widespread that they would let themselves open to too much cost if they started actually doing the right thing and replcing them like for like. I also think the suggesiton that the only way out of a contract is to pay out £260+ (£300 in our case) after it was their own promises of what a good phone it is, despite the fact that this significnt problem has been known about for months, that persuaded people to take the contract is tantamount to fraud and that certainly trading standrads should be informed.
gaz_level2 - thanks for the information you gave which confirms that there are known issues with H3G signals and the 6500 especially. I didnt understand some of the detail as I am not technical but I hope others seeing this post may get the info they need to make an informed decision should 3 continue with their despicable practice of enticing people into signing up based on what a great phone this is.
wafush - if you are considering 3 : NO NO NO
Ben - you are lucky to have a 6500 that is working (based on replies to this thread and on other boards) and you are right that people dont start threads complimenting phones. I started this one for two reasons: a) to see if/how-many others had the same problem and b) inform people about it and what help they could expect from 3 when the problem does occur
Steve/Hamraam - we seem to be in a ridiculous situation where the newest phones are actually less good at making and receving phone calls than phones of 5-6 years ago! They're brilliant for taking photos, browsing the web, playing MP3's. But for simple phone calls... ? And dont get me started on battery life! My old 6310 can last two weeks if I switch it off overnight. Most of the new phones require re-charging at least every other day and if you use push email make that once per day minimum.

WLC 5508 series issues with APs

Hi All,
we recently upgrade our WLC to a new hardware 5508 running 7.6.120.0 and we seem to notice
now and then users ring up and complain that they can not connect to the APs most are AIR-CAP3502I-N-K9 or AIR-LAP1242AG-N-K9
We can see the APs in the controller and can not see anything wrong.
We reboot the APs and it fix the problems.
Just wondering if anybody experience the same issues with this IOS & hardware ???
Any feedback is much appreciated
Thanks
qle

Cisco has issued a "deferred notice" for 7.6.120.X. Cisco openly recommends everyone to use the newer code, 7.6.130.X.
If you "read between the lines", Cisco is saying everyone needs to AVOID 7.6.120.X.

BYOD Onboarding issue with Redirects on ISE 1.2

Hi there,
I'm having intermittent issues with onboarding endpoints (both wired and wireless) with ISE 1.2 (Patch 12).
I get three differing scenarios upon attempting:
1). I get redirected to the ISE Self Registration Portal, register, download the supplicant OK and then can browse with no problems.
2) I dont get redirected at all and so never see the Self Registration portal. All browsing tries to go to the selected website and fails (presumably as the redirect URL is in place even if the browser is not "seeing" it). If I force the browser URL to to ISE I get the Self Registration Portal displayed but with no MAC details present so I can get no further.
3) I get redirected, and seemingly Register OK, download the profiles etc...but after a "Registered Sucessfully" message, any attempt to browse to external website is again redirected to the Portal. I can then re-register again (it lets me do that as if the first time) but I just end up in that loop forever.
These problems are mostly seen wirelessly (I have a WLC 5508) but also wired clients via 3850 wired ports. I am using a collection of endpoints (Andorid, IPads, Laptops) to test and de-registering them between attempts and the results are entirely random among the three scenarios.
I am not changing any policies in between attempts so they are working fine at times, and not at others.
Any help welcome!

Hi Neno,
Thanks for your reply. I have attached some info as requested. For AuthZ rules they should first hit an EAP-MSCHAPv2 rule via the secure SSID which redirects them to the NSP process and gives them an ACL on the WLC that only allows DHCP, DNS and traffic to from ISE.
Afterward registration they should then get a certificate and then after a COA reauthenticate using EAP-TLS.
All this works fine at times, but at other times Web traffic NEVER gets redirected to ISE to begin the registration process or alternatively endpoints are STUCK in a circle of registration in that the th redirect works OK and you register OK but the redirect is permanently on and you keep getting asked to re-register your device despite the fact you have already done it once.
If you can avoid either of these scenarios, it works absolutely fine. It feels like the endpoints themselves are the issue, as I am using a small set of test devices to register (and then de-register) to test with.
However the same device that wont work at all for many many attempts, will eventually suddenly work OK and the BYOD process completes. I do however seem to have a permanent problem with Surface Pro's in that I can never get them to see the redirect at all.

AP 1140 DHCP Issue

Hi All
I am installing a 3750 switch with integrated controller and 12 x Cisco 1140 AP's. I have configured the 3750 WLC with a management and AP Manager IP address along with 3 WLAN profiles and security settings. I am confident that these are correct, and in any case are, I believe, not related to the problem I have.
None of my AP's would connect to the controller and when I checked the DHCP (Windows Server) server they had not been issued with an IP address. I logged into an AP via the console and saw the following message "Not sending discovery request AP does not have an ip" If I plug a laptop into the port the AP connects to I pick up an IP address without a problem from the DHCP server. This is not a faulty AP issue as none of the AP's are getting an IP address.
The only other relevant fact is that the Windows DHCP server is on a different subnet (VLAN)though I have enabled DHCP forwarding which obviously works as my laptop gets an IP address.
I have raised this with Cisco TAC and their first response has been to get me to configure Option 43. I will try this but am not expecting it to work as the only thing this will do is to return the IP address of the controller. My AP's however are not getting any response.
Any suggestions as to how to resolve would be gratefully received.

Wouldn't option 43 only work when the AP's are actually getting an IP address?
Could you post an extended capture of the AP output during the boot and lack of join?
To make sure you connectivity is what it should be, you could always try manually assigning an IP address to the AP, and also manually tell the AP the controller IP address. If that works, then you likely have a problem with your DHCP server or scope definition. Do you have any MAC assignments/reservations in the DHCP scope? Have you tried reserving the AP IP addresses by MAC address within the relevant DHCP scope?

WLC DHCP issue with 6500

Similar Messages

Maybe you are looking for