AP disappearing from WLC AP list

Unanswered Question
May 21st, 2009
User Badges:

Hi,


Two 1522 APs are randomly disappearing from the 4402 WLC (5.2.157.0) AP list. 802.11a is used by this Mesh APs to connect to Root AP.


"debug capwap events enable" command shows the following message:


*May 21 19:50:46.681: 00:24:f7:ad:c6:00 Discovery Request from 10.5.5.12:31840


*May 21 19:50:46.681: 00:24:f7:ad:c6:00 Discovery Response sent to 10.5.5.12:318

40


This message appears periodically and nothing happens, i.e. 10.5.5.12 does not register.


Also there is a "RRM Verify Coverage Hole returned L7_FAILURE" error.


Why AP is not registering, how can I troubleshoot?


TIA

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
naks Thu, 05/21/2009 - 09:10
User Badges:

Hi,


The debug message doesn't give much info since it only shows a discovery request from one of the mesh aps and the response from the WLC.


If it is not an issue, can you post the entire o/p of the following debugs on the WLC:


debug capwap events enable

debug mesh security events enable


I assume you have entered the MAC address of both the mesh aps in the mac filter on the WLC.


Regards,


Nagendra

osumbekov Thu, 05/21/2009 - 19:14
User Badges:

Hi Nagendra,


(Cisco Controller) >debug capwap events enable


(Cisco Controller) >*May 22 08:51:30.335: 00:24:f7:ac:ef:00 Echo Request from 10

.5.5.18:32497


*May 22 08:51:30.335: 00:24:f7:ac:ef:00 Echo Response sent to 10.5.5.18:32497


*May 22 08:51:31.147: 00:24:f7:ad:84:00 Echo Request from 10.5.5.19:30785


*May 22 08:51:31.147: 00:24:f7:ad:84:00 Echo Response sent to 10.5.5.19:30785


*May 22 08:51:31.383: 00:24:f7:ad:84:00 WTP Event Request from 10.5.5.19:30785


*May 22 08:51:31.383: 00:24:f7:ad:84:00 WTP Event Response sent to 10.5.5.19:307

85


*May 22 08:51:31.390: 00:24:f7:ad:84:00 WTP Event Request from 10.5.5.19:30785


*May 22 08:51:31.390: 00:24:f7:ad:84:00 WTP Event Response sent to 10.5.5.19:307

85


*May 22 08:51:33.530: 00:24:f7:ad:ad:00 Echo Request from 10.5.5.21:31441


*May 22 08:51:33.530: 00:24:f7:ad:ad:00 Echo Response sent to 10.5.5.21:31441


*May 22 08:51:36.166: 00:24:c3:73:06:00 Echo Request from 10.5.5.15:12386


*May 22 08:51:36.167: 00:24:c3:73:06:00 Echo Response sent to 10.5.5.15:12386


*May 22 08:51:40.349: 00:24:c3:72:d2:00 Echo Request from 10.5.5.10:15648


*May 22 08:51:40.349: 00:24:c3:72:d2:00 Echo Response sent to 10.5.5.10:15648


*May 22 08:51:43.566: 00:24:f7:ad:b8:00 Echo Request from 10.5.5.11:31616


*May 22 08:51:43.566: 00:24:f7:ad:b8:00 Echo Response sent to 10.5.5.11:31616


*May 22 08:51:48.356: 00:24:f7:ad:c6:00 Echo Request from 10.5.5.12:31840


*May 22 08:51:48.356: 00:24:f7:ad:c6:00 Echo Response sent to 10.5.5.12:31840


*May 22 08:51:48.836: 00:24:f7:ad:c6:00 WTP Event Request from 10.5.5.12:31840


*May 22 08:51:48.837: 00:24:f7:ad:c6:00 WTP Event Response sent to 10.5.5.12:318

40


*May 22 08:51:48.840: 00:24:f7:ad:c6:00 WTP Event Request from 10.5.5.12:31840


*May 22 08:51:48.840: 00:24:f7:ad:c6:00 WTP Event Response sent to 10.5.5.12:318

40


*May 22 08:51:54.891: 00:24:f7:ad:b9:00 Echo Request from 10.5.5.16:31632


*May 22 08:51:54.891: 00:24:f7:ad:b9:00 Echo Response sent to 10.5.5.16:31632


*May 22 08:51:56.004: 00:24:f7:ad:37:00 Echo Request from 10.5.5.20:29553


*May 22 08:51:56.004: 00:24:f7:ad:37:00 Echo Response sent to 10.5.5.20:29553



As you see 10.5.5.12 is back again. Its MAC address is in the MAC filter list of WLC.


There was not any output from the

"debug mesh security events enable" command for 30 minutes, maybe its because AP has already registered?



naks Mon, 05/25/2009 - 05:39
User Badges:

Hi,


The debugs here are within a span of 30 seconds only and no disconnection has happened in that time.

Can you provide the following info:

How often does your mesh aps get disconnected?

What kind of a mesh set up do you have? Is it a point-to-multipoint or point-to-point?

How is the signal strength between the root access point and the mesh access points?

What does the trap logs say when the aps are disconnected?

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