09-22-2011 08:56 AM - edited 07-03-2021 08:48 PM
I have a few APs that keep doing this where WCS generates alarms saying that the AP is down and a/b/g interface is all down. If I check the WCS, I see the AP up for more than 10 days or so but the CAPWAP is up only for 4 minutes. Eventually clients associate to that AP but they see downtime.
Is it because the AP is bad (hardware issue)?
CAPWAP Up Time | 4 m 17 s |
AP Up Time | 10 d 0 h 24 m 4 s |
Meena
09-22-2011 09:25 AM
The capwap up is a relation between the AP and the WLC. The uptime is how long the AP how been powered on.
For example -- If the AP moves WLC on its own or if you direct it, the capwap timer restarts.
If you reboot or power down the AP, the up time restarts..
Make sense?
Hey -- Did you get your autonomous AP working ? I have some free time today I can stop by ..
09-22-2011 09:30 AM
Hi George,
Thanks for your quick reply. The AP stayed with the same WLC and so what could have triggered the capwap down time when AP is still up? I I understand the AP uptime.
I am still having problems with my autonmous AP. DO you think you can come by today? I am free all afternoon.
Meena
09-22-2011 09:38 AM
Well based on the uptime we know one thing is for sure. Something interrupted the capwap tunnel between the AP and the WLC and this is what triggered the alarm. And you are correct. Clients will be impacted. The most common thing you will see is that the AP moves from one WLC to another WLC. However, if you are sure this is not the case.
Then something else could have intruped the tunnel.
Down vlan
A number of missed heart beats (between the AP and WLC)
Routing issue
I know... Im strecthing it ... The list could go on ...
shoot me an email of the address. I can shoot over at lunch ...
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: