×

Warning message

  • Cisco Support Forums is in Read Only mode while the site is being migrated.
  • Cisco Support Forums is in Read Only mode while the site is being migrated.

AP's randomly disconnect after upgrade to 4.0.206.0

Unanswered Question
Jan 14th, 2007
User Badges:
  • Silver, 250 points or more

Anyone running 4.0.206.0 yet? Upgraded from 4.0.155.5 (LWAPP) and now seeing the access points randomly disconnect and reconnect to the controller much like the old CSCse64027 bug. Below are the traps but I have not made any config changes as noted by the log. The AP id keeps increasing as if the AP were power cycled, but they have not been.


Sat Jan 13 11:20:09 2007 [ERROR] spam_lrad.c 1893: AP 00:15:c7:83:ba:20 associated. Last AP failure was due to Configuration changes, reason: did not get join response


Sat Jan 13 11:20:08 2007 AP Associated. Base Radio MAC: 00:15:c7:83:ba:20

Sat Jan 13 11:18:05 2007 AP Disassociated. Base Radio MAC:00:15:c7:83:ba:20


Anyone sees this?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
christopher.coc... Thu, 01/18/2007 - 11:50
User Badges:

Thought it was just a fluke until it happened three times... Tested with the AP fine throughout the day (my first testing with the 4.0 code) -- but the next morning when I came in to test, the AP was in discovery mode as if it lost contact with the controller.


Have had other occurrences where it would reconnect to an older controller in the lab (running 3.2 code) -- so had to wait for the firmware download to finish before putting it back on the 4.0.206 controller.


Interested to see if anyone else sees this...

Darren Ramsey Thu, 01/18/2007 - 14:37
User Badges:
  • Silver, 250 points or more

Update, I have a TAC case open but not much movement there. I installed 4.0.206.0 at a smaller site and have seen no problems. The site not having problems has older AP1230 that were converted to LWAPP. The site having issues is comprised of all AP1242 and one converted AP1232. Strangely enough the converted AP is having no problems, but the AP1242 which shipped LWAPP are dropping out. I also have a console log from one of the AP1242 that I'll attach. For some reason the LWAPP association times out and the AP reloads and then subsequently joins.



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