LAP 1250 can't join the controller
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-01-2011 12:25 AM - edited 07-03-2021 08:01 PM
Good day!
Briefly about the problem:
- I have upgraded one of our autonomus AP to lightweight AP
- At first everything went ok - the LAP dowloaded the image from the WLC and then I was able to successfuly manage it though the controller.
- After that the LAP was switched off and waited for her destiny for several months
- During the installation we noticed that in several minutes all the indicators stopped blinking. The issue was not about power, because in the CLI we saw it actively functioning. But it couldn't assotiate with the controller
- Debug
- %CAPWAP-3-ERRORLOG: SM handler: Failed to process timer message.
- %CAPWAP-3-ERRORLOG: Failed to handle timer message.
- %CAPWAP-3-ERRORLOG: Failed to process timer message.
- %CAPWAP-3-ERRORLOG: Discovery interval timer expiry handler failed.
I downgraded the LAP to AP, then returned it again to LAP
After that the indicators bwgan to blink in normal mode, but still no assosoation with the WLC
- Labels:
-
Wireless LAN Controller
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2011 10:30 AM
I think your AP has a problem with the IOS RCVK image.
%Error opening flash:/info (No such file or directory)
%Error opening flash:/c1250-rcvk9w8-mx/info (No such file or directory)cisco AIR-AP1252AG-A-K9
flashfs[1]: Initialization complete....done Initializing flashfs.%Error opening flash:/info (No such file or directory)
capwap_read_version_info: Info file flash:/info not find
I would recommend you to format flash and upload the latest RCVK IOS to this unit...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2011 04:15 PM
*Apr 22 06:28:43.907: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
Date is incorrect. Have you set the WLC to the correct time OR a valid NTP source?- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-18-2011 01:55 AM
leolaohoo wrote:
Date is incorrect. Have you set the WLC to the correct time OR a valid NTP source?*Apr 22 06:28:43.907: %CAPWAP-3-ERRORLOG: Failed to handle timer message.
If the LAP tries to join the wlc for the first time, is it obligatory for both WLC and LAP to have the same time value
I would recommend you to format flash and upload the latest RCVK IOS to this unit...
I deleted the rcvk image from flash and uploaded the new one, but it didn't help
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2011 03:39 PM
yes, I'm able to ping boyh WLC interfaces: managment, ap-manager
This is sooooooooooooooooooooooooooooooo wrong. You CANNOT ping the AP-Manager interface IP address.
How many APs can't join the WLC?
Is the AP in an switch access port?
Firewall? Did you enable UDP 5246 and 5247?
Have you seen or read this document?
Troubleshoot a Lightweight Access Point Not Joining a Wireless LAN Controller
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2011 03:46 PM
Leolaohoo
Unfortunately, yes it is possible to ping some ap-manager interfaces.
I personally saw that when I was in TAC, I couldnt determine why sometimes it is pingable...
Well... from the inside you should be able to ping the IP address of the dynamic interface you are connected to...
I know it was pingable on its first versions, but I cant say the same about the latest codes, even thought it is still stange why sometimes ap-manager gives a reply...
And By the way, the times I saw it pingable, I was sure there was no duplicate Ip address on the network...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-07-2011 03:59 PM
Bizarre.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2011 01:36 AM
What else can I say - the fact is, that AP-Manager is pingable
there is only one LAP that cannot join the wlc. All the others work fine
yes, the LAP is in access port
there is no firewall between LAP and WLC
The WLC has the correct time
I'll tre to upload the RCVK image, thank you

- « Previous
-
- 1
- 2
- Next »