Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Community Member

Newly LWAPPED APs will not stay joined to controller

I am having an issue where I have 4 WISMS with all the controllers on the WISMS running 6.0.182.0 code.  I have converted a total of about 70 1252 access points from autonoumous as well as added some new out of the box 1141s that are already lightweight.  I have a single controller that when the AP joins it shows up for maybe 10 secons and then goes away.  I keep getting the following in the logs:

11:56:01 2009 AP Disassociated. Base Radio MAC:00:24:14:32:3a:e0
1 Tue Dec 15 11:56:01 2009 AP's Interface:1(802.11a) Operation State Down: Base Radio MAC:00:24:14:32:3a:e0 Cause=Max Retransmission
2 Tue Dec 15 11:56:01 2009 AP's Interface:0(802.11b) Operation State Down: Base Radio MAC:00:24:14:32:3a:e0 Cause=Max Retransmission
3 Tue Dec 15 11:55:53 2009 AP 'APTEST', MAC: 00:24:14:32:3a:e0 disassociated previously due to AP Reset. Uptime: 13 days, 13 h 43 m 15 s . Last reset reason: operator changed 11g mode
4 Tue Dec 15 11:55:50 2009 AP 'APTEST', MAC: 00:24:14:32:3a:e0 disassociated previously due to AP Reset. Uptime: 13 days, 13 h 43 m 15 s . Last reset reason: operator changed 11g mode
5 Tue Dec 15 11:55:47 2009 AP 'APTEST', MAC: 00:24:14:32:3a:e0 disassociated previously due to AP Reset. Uptime: 13 days, 13 h 43 m 15 s . Last reset reason: operator changed 11g mode
6 Tue Dec 15 11:55:44 2009 AP 'APTEST', MAC: 00:24:14:32:3a:e0 disassociated previously due to AP Reset. Uptime: 13 days, 13 h 43 m 15 s . Last reset reason: operator changed 11g mode
7 Tue Dec 15 11:55:44 2009 WIPS Alert: Reason "NoProfile" detected on AP MAC: 00:24:14:32:3a:e0, AP Name: APTEST

I have actually opened a case with TAC and they have gone through a config from a a controller I am not having issues and this one and apprently the settings look good from what they can see.

I don't know what the operator changed 11g mode is supposed to mean.......

Anyone seen anything like this before??

4 REPLIES
Hall of Fame Super Blue

Re: Newly LWAPPED APs will not stay joined to controller

If the LAP can ping the Management IP address of the WiSM, console into the LAP in question and in enable mode, type the command "lwapp ap controller ip address ".

If this doesn't work, enter the command "clear lwapp private".

If this still doesn't work, convert the LAP to Autonomous and re-convert it back into LAP.

Hope this helps.

Community Member

Re: Newly LWAPPED APs will not stay joined to controller

I have converted about 70 access points and they all do the same thing with this controller.  I have a total of 4 Wisms so I have have 8 controllers total and these APs work fine with any of the other controllers.  Also, a new lightweight AP out of the box does the same thing.

Community Member

Re: Newly LWAPPED APs will not stay joined to controller

Hello there, were you able to get an answer for the message, "Reason: operator changed 11g mode"?

Community Member

Newly LWAPPED APs will not stay joined to controller

I think there may be different reasons for this error message. I finally fixed it on my system by removing 'storm-control' commands from the switch ports that the APs connected into. I don't know why that would cause the 'operator changed 11g mode' problem, but it did.

Good luck!

4402
Views
0
Helpful
4
Replies
CreatePlease to create content