08-22-2012 10:26 AM - edited 07-03-2021 10:33 PM
Hi,
Here is the situation encountered.
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.
Any ideas?
Thanks,
E
08-22-2012 10:33 AM
that could be a misbehaving radio. If you have a spare, I'd roll it out and see if the issues persists.
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
08-22-2012 10:36 AM
Hi Steve,
Thanks for your reply.
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.
Thanks,
E
09-06-2012 07:45 AM
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
*Aug 27 09:38:19.395: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor 0023.ac18.d70f VIDB Virtual-Dot11Radio0 going down
--More-- *Aug 27 09:38:19.399: %LINK-3-UPDOWN: Interface Virtual-Dot11Radio0, changed state to down
*Aug 27 09:38:20.399: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to down
*Aug 27 09:39:05.967: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor 001e.495a.320f VIDB Virtual-Dot11Radio0 dot1x control
*Aug 27 09:39:05.971: %LINK-3-UPDOWN: Interface Virtual-Dot11Radio0, changed state to up
*Aug 27 09:39:06.971: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to up
*Aug 27 09:39:19.483: %MESH-6-LINK_UPDOWN: Mesh station 001e.495a.320f link Down
*Aug 27 09:39:19.683: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor 001e.495a.320f VIDB Virtual-Dot11Radio0 going down
*Aug 27 09:39:19.687: %LINK-3-UPDOWN: Interface Virtual-Dot11Radio0, changed state to down
*Aug 27 09:39:20.687: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to down
*Aug 27 09:42:18.103: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor 0023.ac18.d70f VIDB Virtual-Dot11Radio0 dot1x control
*Aug 27 09:42:18.107: %LINK-3-UPDOWN: Interface Virtual-Dot11Radio0, changed state to up
*Aug 27 09:42:19.107: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Dot11Radio0, changed state to up
*Aug 27 09:42:31.607: %MESH-6-LINK_UPDOWN: Mesh station 0023.ac18.d70f link Down
*Aug 27 09:42:31.807: %MESH-6-ADJ_VIDB_LINK: Mesh neighbor 0023.ac18.d70f VIDB Virtual-Dot11Radio0 going down
*Aug 27 09:42:31.811: %LINK-3-UPDOWN: Interface Virtual-Dot11Radio0, changed state to down.
This is happening on all Virtual Dot11 Radios, 0 - 4. There is no reason why, other than mesh station link is down.
Can anyone recommend any debug commands I could consider to dig deeper into why the dot11radios are not accepting MAP links?
09-24-2014 10:20 PM
10-27-2014 03:48 AM
Bump. Same problem here, anybody found solution?
11-28-2014 12:55 AM
hi, i have the same problem. still no solutions?
12-08-2014 12:27 AM
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.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide