Welcome to Cisco Support Community. We would love to have your feedback.
For an introduction to the new site, click here. And see here for current known issues.
I have 3 access points associted with a WLC running version 188.8.131.52, all of them have the interfaces going down and UP all the time.
Everything is fine when all sudenly the wireless user lost connection.
I have monitored the logs and have ssen the radio interfaces on the APs are going down and UP for no reason.
How are they being powered?
Via power injector.
I've suspected of it and chenged the power supply to direct AC power source.
Lest's see if it works.
When you use power injectors it's worth setting the power settings on the controller. Set it to power injector state.
I have found that AP's will join the controller but their radios will not power unless you set this.
I had it already set when the problem was ocurring. To take out any doubt about PoE I pluged it direct AC power on AP but it keep droping the users.
I set up an syslog server and the messages are like this:
2008-11-21 08:35:28 Local0.Error 192.168.X.139 abc_WIRELESS: *Nov 21 07:35:42.860: %DOT1X-3-MAX_EAP_RETRIES: 1x_auth_pae.c:2866 Max EAP identity request retries (3) exceeded for client 00:1b:77:b2:fa:8d
2008-11-21 08:35:39 Local7.Error 192.168.y.193 177: AP:001f.ca64.6777: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
2008-11-21 08:35:40 Local7.Error 192.168.y.193 178: AP:001f.ca64.6777: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
2008-11-19 16:52:26 Local0.Alert 192.168.x.139 abc_WIRELESS: *Nov 19 15:52:39.848: %APF-1-CAN_NOT_ASS_WITH_ROGUE_AP: apf_rogue_detect.c:1693 Can not associate with 00:1B:11:F6:73:10 Rogue AP.
2008-11-19 16:52:26 Local7.Error 192.168.44.193 35: AP:001f.ca64.6777: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to down
2008-11-19 16:52:27 Local7.Error 192.168.44.193 36: AP:001f.ca64.6777: %LINK-3-UPDOWN: Interface Dot11Radio0, changed state to up
Do you have rogue containment enabled?
Can you post the message logs from the WLC?
It might also be worth upgrading the WLC code to the latest version.
Hi, yes, I have rogue containement enabled, and it's already in the latest version, 184.108.40.206.
Here is the logs. The message logs is set to debug on wlc.
In you WLAN configuration, have you set DHCP required? Are the Clients IP's static or DHCP?
There is two SSIDs, one with DHCP required the other no.
In both of them the IP assignement should be through DHCP (internal in wlc), but only one is marked as required.