08-06-2009 02:19 AM - edited 07-03-2021 05:54 PM
Problem:the AP is associated,and then disassociated,and ....
Why?I can't find any discreption on www.cisco.com
Thanks.
The syslog is as following:
0
Thu Aug 6 16:03:10 2009
AP Associated. Base Radio MAC: xx:xx:xx:xx:xx:xx
1
Thu Aug 6 16:03:10 2009
AP Disassociated. Base Radio MAC:xx:xx:xx:xx:xx:xx
2
Thu Aug 6 16:03:10 2009
AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:xx:xx:xx:xx:xx:xx Cause=New Discovery
3
Thu Aug 6 16:03:10 2009
AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:xx:xx:xx:xx:xx:xx Cause=New Discovery
4
Thu Aug 6 16:02:10 2009
AP Associated. Base Radio MAC: xx:xx:xx:xx:xx:xx
5
Thu Aug 6 16:02:09 2009
AP Disassociated. Base Radio MAC:xx:xx:xx:xx:xx:xx
08-06-2009 05:15 AM
Hi,
can you log into the AP via Console?
If so, what is the log of the AP saying when it disconnects?
Greets,
Sebastian
08-06-2009 12:44 PM
I've seen this occur when an AP gets confused about which controller is the primary controller (in a multi-controller network). Cold booting the AP solved the problem.
08-09-2009 10:41 PM
thank you for your reply.
the problem has beed solved,because I set the primary and secondary controller.But, the primary controller's time was not set,so,the ap can not join the primary controller.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: