1552E Rap will "lock" up, and not allow MAPs to connect through it to join. the WLC. Rebooting the Rap will resolve the issue, but the problem comes back and some random point in the future.
Prior to rebooting the Rap to fix the issue, the Rap shows as joined to the WLC, but I have noticed that the neighbor details look stale, meaning my MAPs don't show up as neighbors, but other MAPs in the area are in the neighbor list, listed by MAC address. At this time, I can not confirm whether or not the neighbor detials are changing (updating), but I can confirm that my MAPs never show up as neighbors.
As soon as the RAP is rebooted, MAPs join the controller again.
I can tell you that this is happening to two different RAPs, each connected to different MPLS locations. I am not sure if this issue happened at the same time for both RAPs, but both had to rebooted to service MAPs again.
So the problem has come back, the RAP looks "connected" to the WLC, but it isn't servicing MAPS. Neighbor Details of said RAP are stale, and not updating. I know a reboot will resolve the issue, but the problem will come back. While this problem is happening, i can still telnet to the RAP, and have noticed the following:
*Aug 27 09:38:12.183: %LINK-3-UPDOWN: Interface Virtual-Dot11Radio0, changed state to up
*Aug 27 09:38:13.183: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to up
*Aug 27 09:38:19.195: %MESH-6-LINK_UPDOWN: Mesh station 0023.ac18.d70f link Down
I see that this is an old thread now but I meet exactly the same issue.
For a couple of months everything was ok but since yesteday and without any config changes, a large number of my LAP1522E appears to have the same behavior as described above with the same logs. Power cycling them could solve the issue for a while but it reappears in the day.
I'm using a WLC 8500 in SSO with version 126.96.36.199
Does anyone solved this issue in the past ?
We encountered the same problem and after changing the VLAN for users (going out of WLC) to be different than VLAN for CAPWAP tunnel it seems that this issue is solved in our case (MAPs are connected now for nearly one week vs. previously there was at least one RAP dropping the MAPs / day).
Since this was a network that we "inherited" and the problems started all of a sudden (and everything seemed to work before), noone suspected that part of the network/design.