10-31-2024 01:50 AM - edited 10-31-2024 01:51 AM
Hello everyone,
I have a Cisco AIR-CAP2702I-UXK9 access point running firmware version 15.3(3)JK7, connected to a 5520 Controller with firmware 8.10.171.0. The access point successfully connects to the controller, obtains an IP address from the correct subnet, and clients can connect to the AP without any issues. Everything seems to be working as expected.
However, I noticed the status LED on the access point cycles through green-red-off repeatedly.
After some research, I found the following Cisco documentation:
This document suggests that this may relate to regulatory domain settings, but it’s quite outdated, and I’ve read that the configuration utility has been removed from the Android platform.
Does anyone know how to address this LED status issue?
10-31-2024 01:57 AM
The reason could be due configuration. Try to disable It.
config ap led-state flash disable Cisco_AP
10-31-2024 02:09 AM
Thank you for your response. Unfortunately, this solution doesn’t fully address the root cause of the issue. Since these devices are deployed on-site, disabling the status LED might lead personnel to mistakenly believe the device is not functioning. For this reason, it may be more effective to resolve the underlying issue rather than applying a temporary fix.
10-31-2024 02:15 AM - edited 10-31-2024 02:17 AM
No. You did not get It. What I meant is, you can, via configuration make the AP Blink the LEDs. For many reason this can be done, for example to identify one AP among many. I did this a lot
My suggestion is to make sure you accidentally did not enable this feature
This command Will not chance the LED normal behavior, It Will only undo the configuration in case It was done by mistake.
10-31-2024 02:55 AM - edited 10-31-2024 02:55 AM
I implemented what you said, but it appears to be already configured.
10-31-2024 03:03 AM
Ok, this means the LED is not blinking due configuration. Let´s try to find out what else could cause this.
10-31-2024 03:10 AM
As per the information below, on this case, the AP is awaiting to be priming and that´s why the LED is blinking. As you well told, the APP is no longer available so you probably need to accept this behavior.
I believe this WLC is not under support anymore so probably Cisco TAC is not an option.
"
Boot up the universal AP.
For a universal AP awaiting priming, its status LED cycles through Red-Green-Off. For more information on the LED states, see AP Status LED States."
10-31-2024 04:51 AM
10-31-2024 05:23 AM
it is indeed very odd. I had to do this once and it took me a day. But, if you have the APP then you can do this.
Make sure you can get internet access while doing this.
10-31-2024 03:39 AM
- Probably the AP does not get sufficient power.It can work but not with full capacity,
M.
10-31-2024 04:54 AM
Hello,
As you suggested, I checked the power status and can see that it’s drawing 16.8W. It's connected to Port 32.
10-31-2024 07:06 AM
@Zemherir (wrote) >...As you suggested, I checked the power status and can see that it’s drawing 16.8W. It's connected to Port 32.
- Power is good. You could either reboot the AP and post the full boot process here to get insights ; usually that is not possible for a remote AP anywhere in a building ; therefore do the same and just after boot connect to it with SSH and
issue the command show logging
(when doing this just after the AP has booted , most of the boot information is still available) ;==> look for errors , if any
M.
10-31-2024 10:51 PM
11-01-2024 12:58 AM
- I don't see any problem with the boot sequence ; is AP available in the list of joined APs on the controller ?
M.
11-01-2024 01:14 AM
Yes, I can see it in the list of joined APs.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide