APs continually registering with secondary controller

Hi All,
For some reason all of the APs on a particular controller deregister from it and register with their secondary controller. Both controllers are running version 4.1.171.0 and I cannot see any issues on the LAN that would disrupt comms between the APs and their primary controller.
Any pointers will be greatly appreciated.
Many Thanks
Scott

Hi Eric,
I haven't tried either of those but I will do as soon as.
I'm using names for the first and second controllers (I'm haven't spec'd a third due to the controllers being geographically distant).
These particular APs had been quite stable until I upgraded the controllers to said s/w version around a month ago, though APs on other upgraded controllers are fine. Also no matter where the APs are registered to they report (via WCS) that they are running vers 3.2.195.10 s/w, however interrogating the relevant controller directly says they are running vers 4.1.171.0.
I was also in the midst of adding some new APs; these were autonomous ones that I converted (at my desk) and specified the suspect controller for them to register with during the conversion, the new APs registered ok with the controller and I set the same controller as their primary and set them aside for installation. After your reply to my initial query I've booted one of the newly converted ones again and they have registered with a random controller elsewhere on our network (I'm using option 43) rather than their primary.
Apologies for the info overload, hopefully you can make some sense out of it.
Many Thanks
Scott

Similar Messages

Why some APs would register with Secondary WLC while they are configured to Primary WLC

Dears,
I faced strange behavior i have two WLC one primary and the other one secondary.
some AP join to secondary WLC for short period (2 min or less) and returned to primary, while they are configured to primary WLC.
Two WLC image version: 7.4.121.0
Wait your replies plz.
Thanks,

please find Logs from Secondary WLC. and i can't get Access point logs cause i Remote site.
465   Tue Jun 3 13:20:36 2014   AP '90068-02', MAC: 34:a8:4e:bb:08:90 disassociated previously due to Link Failure. Uptime: 0 days, 18 h 46 m 25 s . Reason: Capwap WTP Event request.
466   Tue Jun 3 13:20:36 2014   AP on the 802.11a radio with Base Radio MAC 34:a8:4e:bb:08:90 (90068-02) is unable to associate. The regulatory domain configured on it '-E' does not match the controller's regulatory domain: -C
493   Tue Jun 3 13:16:59 2014   AP '90068-02', MAC: 34:a8:4e:bb:08:90 disassociated previously due to Link Failure. Uptime: 0 days, 18 h 42 m 55 s . Reason: Capwap WTP Event request.
494   Tue Jun 3 13:16:59 2014   AP on the 802.11a radio with Base Radio MAC 34:a8:4e:bb:08:90 (90068-02) is unable to associate. The regulatory domain configured on it '-E' does not match the controller's regulatory domain: -C
59   Tue Jun 3 13:20:42 2014   AP '90068-01', MAC: 34:a8:4e:bb:06:30 disassociated previously due to Link Failure. Uptime: 0 days, 18 h 47 m 17 s . Reason: Capwap WTP Event request.
460   Tue Jun 3 13:20:42 2014   AP on the 802.11a radio with Base Radio MAC 34:a8:4e:bb:06:30 (90068-01) is unable to associate. The regulatory domain configured on it '-E' does not match the controller's regulatory domain: -C
0   Tue Jun 3 14:51:09 2014   Coverage hole pre alarm for client[1] 94:01:c2:82:26:27 on 802.11b/g interface of AP 54:78:1a:88:2c:c0 (90002-01). Hist: 0 0 1 1 4 8 26 30 22 24 12 21 9 7 3 7 2 2 1 1 0 0 0 0 0 0 0 0 0 0 0
1   Tue Jun 3 14:51:09 2014   Coverage hole pre alarm for client[1] 88:32:9b:5f:e7:91 on 802.11b/g interface of AP 54:78:1a:88:2c:c0 (90002-01). Hist: 1 4 7 15 4 9 4 4 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
2   Tue Jun 3 14:51:09 2014   Coverage hole pre alarm for client[1] cc:3a:61:69:d9:4c on 802.11b/g interface of AP 54:78:1a:88:2c:c0 (90002-01). Hist: 0 0 0 0 0 2 13 16 19 13 5 6 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
3   Tue Jun 3 14:51:09 2014   Coverage hole pre alarm for client[1] bc:44:86:09:f1:ec on 802.11b/g interface of AP 54:78:1a:88:2c:c0 (90002-01). Hist: 0 0 0 3 21 24 13 6 2 1 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 2 3 0 0
Wait your feedback plz.
Thanks,

APs not registering with WLC

Hi guys, i'll try to explain our trouble as best as i can:
Im trying to do some basic scenario here. Picture this: One L3 Switch connecting a 4402 Controller, 3 Administrative Vlans for APs (63, 93 and 127) and 3 Vlans for clients (one for each Administrative vlan, 16, 64 and 95 respectively). Also, in one of the administrative vlans (63) lives the Management and AP Manager interfaces of the controller. The L3 Switch does the DHCP business also, including giving the Controller IP (option 43).
Here is the deal: When i try to connect one LWAP AP in to the same VLAN as the controller (63) it does gets an IP address of the segment and also gets the Controller IP. BUT, it cannot reach the Controller Management interface, not by ping nor by registering. (i connected a laptop to chek this behavior and it cant ping the Management Interface either)
Then, if i connect the same AP to another VLAN (say.. 93)it will get an IP address of the segment, IP of the controller and it will reach the Controller by means of PING and also discovery request/discovery response. BUT, it wont register with the controller. In both cases, the L3 switch can ping just fine the APs and the Management Interface.
After sniffing little bit I can see that the AP does in fact send the Join request message to the AP Manager interface of the Controller, but it wont get an answer. Then, in the CLI of the Controller (debug lwapp events enable) i can see that the controller does recive the discovery request and send the discovery response messages, but never sees the join request frome the AP.
Configs of the switch and controller attached.
Also, i checked the date of the controller and its up to date, the certificates of the APs should be fine, they will expire in 2 o 3 more years.
Oh, and the Controller its not directly connected to the Switch, its connected to another 3500 switch using a GBIC, but its just used as a media converter... after that switch its connected to a trunk in the L3 Switch.. and yes, the Switch with the controller has all the needed vlans configured so they can be seen on the trunks.
Any help would be greately appretiated.

Hi again... guess what? I came to work today, turned on all the equipment.. and it works! God knows why but now the APs can register. For your information I did reset the devices before, so i dont know what happened.
Anyway there is still a problem. If the APs are in the same VLAN as the controller, they cant see it. And this goes for every device, if I have 2 APs and one laptop in the same vlan they cant ping each other but can ping their GW. Any comments on this?
Thanks in advance!

Can LAP1242s register with DNS?

We have a need for some 1242s that are connected to a controller to be pingable by DNS name.
Is it possible to get the APs to register with DNS when they get an IP address? I don't recall seeing it as an option - if it can how do I do it?
Thanks in advance

Thanks, Robert.
The scenario is that we have some APs that we want to move from site to site for training. We will prime them for the WLC, but let DHCP allocate the IP addresses.
Just want an easy way to find them.

1131 APs have refused to register with WLC2106

Hi all, my 1131 AP has refused to register with a WLC2106.
I get this on my AP console when i enable DHCP:
*Mar 1 00:00:09.493: %SNMP-5-COLDSTART: SNMP agent on host AP001d.e555.df68 is undergoing a cold start
*Mar 1 00:00:10.368: %LINK-3-UPDOWN: Interface FastEthernet0, changed state to up
*Mar 1 00:00:10.509: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio1, changed state to down
*Mar 1 00:00:10.509: %LINEPROTO-5-UPDOWN: Line protocol on Interface Dot11Radio0, changed state to down
*Mar 1 00:00:11.368: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to down
*Mar 1 00:00:19.368: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to up
*Mar 1 00:00:28.507: %LWAPP-5-CHANGED: LWAPP changed state to DISCOVERY
*Mar 1 00:00:36.645: %DHCP-6-ADDRESS_ASSIGN: Interface FastEthernet0 assigned DHCP address 10.10.10.101, mask 255.2
55.255.0, hostname AP001d.e555.df68
*Mar 1 00:00:48.953: %LWAPP-5-CHANGED: LWAPP changed state to JOIN
*Mar 1 00:00:48.954: %LINK-5-CHANGED: Interface Dot11Radio0, changed state to administratively down
*Mar 1 00:00:48.954: %LINK-5-CHANGED: Interface Dot11Radio1, changed state to administratively down
*Jun 15 23:13:04.091: %CDP_PD-4-POWER_OK: Full power - HIGH_POWER_CLASSIC inline power source
*Jun 15 23:13:05.221: %LWAPP-5-CHANGED: LWAPP changed state to CFG
*Jun 15 23:13:10.221: LWAPP_CLIENT_ERROR_DEBUG: spamHandleCfgReqTimer: Did not recieve the Config response
*Jun 15 23:13:10.295: %SYS-5-RELOAD: Reload requested by LWAPP CLIENT. Reload Reason: DID NOT GET CONFIG RESPONSE.
*Jun 15 23:13:10.295: %LWAPP-5-CHANGED: LWAPP changed state to DOWN.
When i disable DHCP, the AP just stays up without registering as well.
I can view them all via cdp. I also cannot configure the APs, the give an ERROR!!! command disabled response.
Pls what can i do.

Thanks,
that was risky for me to erase the private configs! well done that and problems remain. i think that the reason i get that error message is because the LAP has already connected (or at least tried) to connect to the WLC. i have 3 LAPs and i was able to set IP address and hostname on one of them before connecting it to the WLC; i connected the other two without any entering any configs. now all of them are giving me the error. i think the WLC somehow disables configuration attempts on the LAP
I did a reset by holding down the reset button before powering the LAP, then i got a prompt and i entered reset- and it did. i did this for all of them. the hostname i set on one of them remained even after reset and deleting private configs, it also picks the controller IP addy.
I hv turned on all debugging as well and this is all i get:
AP1#debug lwapp client error
LWAPP Client ERROR display debugging is on
AP1#debug lwapp c
AP1#debug lwapp client con
AP1#debug lwapp client config ?
AP1#debug lwapp client config
LWAPP Client config display debugging is on
AP1#debug lwapp client ev
AP1#debug lwapp client event
LWAPP Client EVENT display debugging is on
AP1#debug lwapp client event
*Mar 1 00:04:59.240: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
*Mar 1 00:05:09.254: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
f
AP1#debug lwapp client fwd
LWAPP Client Forwarding display debugging is on
AP1#
*Mar 1 00:05:19.270: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
no
*Mar 1 00:05:29.285: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
AP1#no
*Mar 1 00:05:39.300: LWAPP_CLIENT_EVENT: spamHandleDiscoveryTimer: Could not discover any MWAR
*Mar 1 00:05:49.314: LWAPP_CLI
Thanks again for ur support, i'm still thinking of what to do with these babies.

APs registering to anchor controller

What would make some of our APs register with the anchor controller rather than the primary? All APs are getting DHCP information pointing them to the primary controller, they are all in the same VLAN, etc but for whatever reason some register with the anchor controller. I’m not sure how this is even possible to be honest…
Any thoughts?

So, is your anchor controller in the same mobility group as the 'internal'?
And to explain.
DHCP option 43, DNS, L2 broadcast etc. Are simply Discovery Mechanisms for an AP.
When the AP sends the Discovery Request to a WLC, the WLC responds with a Discovery Reply. In the Discovery Reply, is a list of all the WLC in the mobility group, their current AP count, their max AP count, and their excess availability.
Using this information the AP will join the WLC with the Greatest Excess Availability.
So DHCP Option 43 points to WLCA. In the Mobility group are WLCA(100), WLCB(100), WLCC(50).
WLCA has 53 AP
WLCB has 51 AP
WLCC has 0 AP.
Which WLC will the next AP join. It will join WLCC, as WLCC has the Greatest Excess Availability.
Make Sense?
HTH,
Steve
Please remember to rate useful posts, and mark questions as answered

MBP will not register with iCloud servers (and most iCloud features + Handoff and Continuity do not work)

Hi all,
I have an extremely strange issue on my rMBP which has not been solved yet despite over 2 hours on the phone with Apple support, and another hour after being put through to a Senior Advisor, and several online chats.
I have a Apple Certified Refurbished Late 2013 Retina Macbook Pro, which has a 2.3Ghz i7, 16GB of RAM, 500 Flash Storage and the NVIDIA discrete graphics. It was purchased in December 2014 on the Apple Store. It is running 10.10.2.
For some reason, my computer WILL NOT register with iCloud. Messages and Facetime both would not work, my iPhone 4S which is capable of text message forwarding would not recognise it and allow me to turn it on. Handoff, Continuity and Instant Hotspot - basically any of the features to do with iCloud or connecting to another device - do not work.
Originally I believed it was just an issue with Messages and Facetime so I reinstalled the OS back to 10.10.1, but that did not solve the problem. All my Messages contacts kept on coming back as 'not registered with iMessage' and I could not turn on SMS Relay either.
I contacted Apple on Wednesday night and ended up talking to several different people, the Senior Advisor was the most helpful - really tried to help me figure out what was wrong, and to fix it - wonderful help, really was. They used screen sharing and were quite confused. They figured out as well that Handoff, Instant Hotspot, and all those other features don't work either. At this point, they made me update to 10.10.2 to see if it was an issue with the update, but to no avail.
Eventually, the SA checked my iCloud account and saw that the computer hadn't even connected to iCloud, and wasn't even showing up as one of my devices, despite the fact that I had signed into iCloud on this computer.
The SA told me that he suspected it must have been something to do with hardware, but didn't know what it could be. He said the only time he had seen this before was on a refurbished laptop when the serial number hadn't been put back on, but my serial number was there, so he said it must have been something to do with Bluetooth or Wifi.
Wireless seems to work completely fine, but there is a strange thing with Bluetooth in which within System report says that the computer is not discoverable or connectable, despite the fact that in the Menu Bar it says it is on and discoverable. It becomes discoverable and connectable once you toggle the switch in System Preferences.
I was planning to book a Genius Bar Appointment as suggested by the SA, but something strange happened today - all of a sudden, some (not all of them) of my iMessages from earlier today came through. Still no working Handoff or Facetime or Continuity, but now I am starting to wonder what is really wrong.
Despite the fact they said it was hardware (especially Bluetooth), what could explain why it (seldom) or will not register with iCloud? Can anybody shed some light on the situation and whether a Genius Bar appointment could help fix it?
Cheers and thanks in advance.

Needed to add some clarification here:
iCloud shows me as signed in, but Calendars are NOT checked
Internet Accounts shows Calendars as syncing

APs not associating with Controller after upgrade

This is pretty bad.
I've been upgrading our controllers to 4.2.209.0 without any problems untill today. The controller upgraded fine but, the APs aren't showing up anywhere. They aren't associating with any controller. I've shut/no shut the PoE ports. They show connected. The WCS says they are not associated with any controller. What should I do. Roll back the image? Will this help?
Thanks Pat.

Surendra,
Thanks for the response. I got this from debug dhcp detail
DHCP: QScan: Timed out Selecting state%Unknown DHCP problem.. No allocation possible
I was pretty desparate at the time so, I wasn't able to trouble-shoot any further. After I saw the DHCP debug I deleted the normal DHCP server address, created a scope for the APs and configured it on the AP management interface and the APs got addresses. After the APs got their addresses, the clients got their addresses from the regular DHCP server. I will try again with the upgrade as I rolled back to 4.2.112.0. Atleast I know I can get an ip from the controller if I need.
Do you know of any reason why my APs weren't getting addresses. Even when I rolled back they weren't getting addresses. The config hadn't changed.
Thanks, Pat.

Aps not finding secondary controller

I have just installed a secondary WLC 4402 where a client has 1121 APs and 1010 APs and I am slightly confused.
We have 2 CISCO-LWAPP-CONTROLLER entries in DNS
The WLCs are WLC1 and WLC2
The 1010 APs fail over to the secondary controller perfectly well.
The 1121 APs do not fail over.
I have given the APs primary and secondary controller names of WLC1 and WLC2.
Is this due to Option 43 not being configured correctly.
I believe though I have not investigated that there is a single entry for the 1121 APs in the DHCP scope for option 43 of the original conmtroller but there is no entry for the 1010 APs.
They are using the same DHCP scope in a layer 2 implementation.
Any help appreciated

When the ap has joined a wlc, the dns and dhcp option 43 is not used. The information created in the mobility group (mac address, ip address and mobility group name) is used. This is how ap's learn of the other wlc. Setting the ap's primary and secondary and or tertiary wlc is required for ap's to be able to join the other wlc. Option 43 and dns is used if the ap goes throught the proccess of finding a wlc if the primary, secondary and or tertiary wlc is not found. It seems to me that the ap's have properly joined a wlc, there for, you need to verify why the 1121'a are not joining the secondary.
First of all, is the mobility group configured correctly and is ap fallback enabled or not. Also, verify that you can mping and eping the controllers. Is the wlc set to layer 2 or layer 3 mode? I think that the 1121 needs the wlc to be in layer 3, but I will check.
What you should also do is console into the ap and post the log so we can see what errors the ap is getting.
Here is a link. Search for layer 2
http://www.cisco.com/en/US/prod/collateral/wireless/ps5678/ps6306/prod_bulletin0900aecd80321a2c_ps6521_Products_Bulletin.html
Here is a link for AP Fallback:
http://www.cisco.com/en/US/tech/tk722/tk721/technologies_tech_note09186a00807a85b8.shtml

Tried to send iMessage from iPod touch (5th generation) but continuously says "contact not registered with iMessage". The contact IS registered with iMessage, but won't send any messages to anyone.

I have an iPod touch 5th generation (7.1.2) that has not been sending iMessages to other iMessage users. At first my iPod would not let me sign in to use iMessage, but I searched on different discussion boards that helped me log in. Now the trouble is not being able to send messages at all. I tried to delete the contact I was trying to message and restart the conversation board, but that didn't help at all. The contact continues to say 'xxxxxx not registered with iMessage" when, in fact, they are. I need help to resolve this issue.
Thanks

Can you receive Message?
If so can you reply?
Have you tried when connect to another network?
Also see:
iOS: Troubleshooting Messages
Using FaceTime and iMessage behind a firewall

Still having issues with AP primary/secondary controller option

Customer has two primary controllers each in HA SSO, each using v7.6.130.0, FUS 1.9.0.0; the AP population is a mixture of mostly 3502, 3602 and 1142. Both WLC's management interfaces are in the same vlan and the mobility communication is up. AP fallback is enabled on both WLC.
Over the weekend the upgrade to 7.6.130.0 was completed and the first AP tested with primary controller defined worked on the first attempt. Every successive reboot of the AP always worked. This did not work previously when the WLC was on v7.6.100.0.
L2 client roaming between APs joined to different controllers also worked great.
While the roaming test was being carried out, a few APs not involved with the testing migrated over to the new controller. This wouldn't be a problem but there are about 15 APs that must reside only one controller. As luck would have it, 5 of the APs which migrated to the new controller are APs which must stay on the other controller. Setting their primary controller had no affect. Each time these 5 APs were reset they ignored the primary controller setting and joined the new controller. These were 4 1142 and 1 3502.
What am I missing? I have checked and double checked the configuration, read and reread the documentation. I am working as a contractor and this is starting to look very bad for me if this problem can not be solved.
Thank you for your assistance.

I would like to follow up and share the resolution to this problem.
After upgrading to 7.6.130.0 and finally determining that one of the test APs was actually bad, we were able to move forward. Since removing the bad AP from the test, we now have the ability to direct APs to a specific controller at will.
In the testing, we found that using just the system name worked in all test cases. This was confusing since using the FQDN worked for some APs but not all. This issue is why I started this discussion. Nobody homed in on that detail, so I hope this will help someone in the future.
Both the primary controllers are in the same management vlan, we only used the system name.
Good luck to all!

APs don't associate with 4402 controller at correct time

WLAN Controller 4402, software version 5.1.151.0; 1131AG APs
A problem started several weeks ago after the WLAN Controller was powered down/up in order to move power cords. Now, we are experiencing a problem with the 1131AG APs associating with the WLAN Controller at the correct time.
Network is a Wide Area Ethernet. The controller's interfaces are configured to use LAG and are connected to ports on a 4507 switch. There are 32 1131AG APs on the network. All switches and routers throughout the network are configured with either NTP or SNTP server parameters. The clock timezone and summer-time parameters are the same on all switches/routers throughout the network. The clocks on all switches/routers and the WLAN controller display the correct date and time of day.
We use an ACL on the switches to apply a time-range, since this cannot be done on the WLAN Controller. During the week, the VLAN that the APs are on should pass packets from 6:00 am to 9:15 pm.
For a week or so, the APs were not associating with the controller until 9:20 am, but were being blocked by the ACL at the correct time at 9:15 pm. Then the problem seemed to correct itself for a week or so. Now, it's started again in the last couple of days.
I've tried resetting a couple of the APs, but this didn't change anything. The problem still persists.
I've checked time parameters over and over, but everything displays the correct time. One thing that displays differently now, as opposed to when the problem originally surfaced several weeks ago. On the controller's web admin pages, the APs used to display the same time for Controller Association Time and Controller Association Latency. Oddly, this calculated to the 6:00 am time, even though the APs display ring was still flashing through the red-pink-chartreuse-amber cycle. Now, however, the Controller Associated Time and Controller Association Latency are different and exactly the 3 hours and 20 minute difference that would be expected.
Rick

We use an ACL on the switches to apply a time-range, since this cannot be done on the WLAN Controller. During the week, the VLAN that the APs are on should pass packets from 6:00 am to 9:15 pm.
If you upgrade your PoE switches IOS to the 12.2(50) series, you'll get the option of EnergyWise.
Why don't you disable your time-based ACL and see if this works?

7921 not registering with CME through repeater

I have this environment:
CME 7.0 running in Cisco2851.
WLC2106 with 6 1242 APs
15 phones 7921
I have to extend the wireless coverage to an specific point (warehouse), 150 meters away. This point only have a PC and a phone, so I don't think a bridge is necessary. I have an 1131 AP configured as repeater. In my tests (locally) I see the 1131 is registering to the main wireless network. Using site survey feature in the 7921 I see the SSID broadcast from the repeater AP, but if I use Neighbor list feature the network is not allocated and obviously the phone can't register with CME. Only for tests I had disabled all security features for this SSID.
The 1131 association table only shows the root AP but it indicates the IP address assigned to the controller.
Can somebody give me some tips to identify what I'm missing?
Thanks in advance

I think H-REAP is a feature not usable for this case, isn't
I'm reading the "Cisco Wireless LAN Controller Configuration Guide", in page 7-19 and follow, Workgrouup Bridge is explained. I think it should be the solution for my requirements, although I will test tomorrow (Wendesday), I have some questions:
The example shows a hub in remote site, I guess it can be replaced with a switch without any problem.
Could it be possible to set another AP attached to the switch to get wireless access? Otherwise, I will need a desktop phone.
The manual indicates NO VLAN are supported (page 7-21), so this option will need PC and phone for this site running in the same VLAN?
I appreciate your assistance.
Daniel Escalante.

Access points not registering with WLC

Hi all,
I have a 5508 WLC in LAG mode and have 14 1231G WAPs connected to it already. However I still have to migrate 9 more WAPs from my old 4404 controller to the new 5508 controller. I cannot get remaining 9 WAPs to register with new WLC. I found following debug message from the WLC. My WLC license is valid for 50 APs. Have any of you guys seen this? What am I doing wrong here? Any lead is much appriciated.
I have LAG setup with 2 ports out of 8 ports. Don't understand why it's giving error of not having enough capacity.
Any advice is much appriciated. Thanks in advance.
*spamApTask4: May 21 18:58:29.468: 00:23:04:c9:72:00 Echo Timer Expiry: Did not receive heartbeat reply from AP 00:23:04:c9:72:00 (10:4:12:26/36602)
*spamApTask0: May 21 18:58:50.588: 00:13:60:7e:28:30 Join Priority Processing status = 0, Incoming Ap's Priority 0, MaxLrads = 50,joined Aps =14
*spamApTask0: May 21 18:58:50.588: 00:13:60:7e:28:30 Refusing Discovery Request from AP 00:13:60:7e:28:30 - no AP manager with available capacity
*spamApTask0: May 21 18:58:50.588: 00:13:60:7e:28:30 Join Priority Processing status = 0, Incoming Ap's Priority 0, MaxLrads = 50,joined Aps =14
*spamApTask0: May 21 18:58:50.588: 00:13:60:7e:28:30 Refusing Discovery Request from AP 00:13:60:7e:28:30 - no AP manager with available capacity
*spamApTask0: May 21 18:59:00.589: Could not find BoardDataPayload
*spamApTask0: May 21 18:59:00.636:
*spamApTask0: May 21 18:59:05.593: Could not find BoardDataPayload
*spamApTask0: May 21 18:59:05.639:
*spamApTask0: May 21 18:59:53.564: 00:13:60:7e:28:30 Join Priority Processing status = 0, Incoming Ap's Priority 0, MaxLrads = 50,joined Aps =14
*spamApTask0: May 21 18:59:53.565: 00:13:60:7e:28:30 Refusing Discovery Request from AP 00:13:60:7e:28:30 - no AP manager with available capacity
*spamApTask0: May 21 18:59:53.565: 00:13:60:7e:28:30 Join Priority Processing status = 0, Incoming Ap's Priority 0, MaxLrads = 50,joined Aps =14
*spamApTask0: May 21 18:59:53.565: 00:13:60:7e:28:30 Refusing Discovery Request from AP 00:13:60:7e:28:30 - no AP manager with available capacity

Guess the SSC got corrupted..
Run the command "debug pm pki enable" on the WLC, copy the SSC and paste it on the WLC and see if that helps.. here is the link to do the same!!
http://www.cisco.com/en/US/products/ps6366/products_configuration_example09186a00806a426c.shtml
Lemme know if this answered ur question and please dont forget to rate the usefull posts!!
Regards
Surendra

Remote Mesh AP with Centralized Controller

Need help to clarify this technical requirement. we are in the midst of designing a wireless Mesh AP solution for our customer.
Customer Requirement:-
1. Customer wants to deploy REmote MEsh APs (1500 Series) with a centralized 4404 Controller at HQ site.
2. The Remote and HQ site is linked thru a leased line with 2 routers in between
Based on cisco's document REAP and HREAP is not supported in LWAPP Mesh APs. So if the Mesh APs were to be deployed at Remote sites (3 total). How this be achieved?
Your input would be very much appreciated.
Thanks.

Well since the mesh AP's don't support h-reap, you would have to run them like local mode AP's. So depending on your WAN connection/bandwidth you can possible achieve this. Currently the mesh isn't designed or remote site wireless, since there is no h-reap function, but you can get it to work if you have a good wan connection.
Sent from Cisco Technical Support iPhone App

APs continually registering with secondary controller

Similar Messages

Maybe you are looking for