wism-ap disassociated!!

Unanswered Question
Aug 6th, 2009
User Badges:

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

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
SJessulat_2 Thu, 08/06/2009 - 05:15
User Badges:

Hi,


can you log into the AP via Console?

If so, what is the log of the AP saying when it disconnects?


Greets,

Sebastian

Robert.N.Barrett_2 Thu, 08/06/2009 - 12:44
User Badges:
  • Bronze, 100 points or more

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.

haijason Sun, 08/09/2009 - 22:41
User Badges:

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.

Actions

This Discussion

 

 

Trending Topics: Other Wireless Mobility

client could not be authenticated
Network Analysis Module (NAM) Products
Cisco 6500 nam
reason 440 driver failure
Cisco password cracker
Cisco Wireless mode