Has anyone seen a 3502i's LED light turn white? Ifso, what does it mean? The info on the LED lights does not mention white. The serial port and the data port are non responsive, but the unit stays powered over PoE.
I have a TAC case open to RMA the AP, I was just wondering if anyone else had ever experienced this issue with the 3502i. We have 2000 on site and I have never seen a white light.
It's just a DOA... White light doesn't mean anything in a working AP. so it's white probable because it hung on boot up.
Sent from my iPhone
The wierd part is that if you power cycle the unit, it will function properly for roughly 24 hours or less, then turns white.
I am currently doing an implementaion of 39 3502E's and I have had no less than SEVEN APs with this problem. Very worrying rate of failure!
We rolled out about 500 and had 1 DOA.. Wonder if you have a bad run maybe?
That's nothing compared to the "quality control".
We pulled out a 3500 from the site because it wouldn't work. So I have it here on my desk with the underside facing up. I plugged the console cable and a PoE in and it didn't work. Fair enough. Plugged a power brick and it worked. Ok ... Anyway, something happened which made me take my console cable and my PoE away. Anyway I came back and was in a rush to get this WAP RMA-ed. Whoops. Forgot what the serial number is and I sure don't want to read it. Forgetting what the issue was (remember that the WAP wouldn't accept PoE), I INCORRECTLY PLUGGED THE PoE cable and the console cable around, that's right: the console cable into the Ethernet port and the PoE into the console port. Anyone hazard to guess what happened?
The bl00dy WAP went LIVE! It stared at this setup for a good three or four minutes. Then I had a careful look at the WAP. Yes, I plugged the console and PoE incorrectly alright. But I also looked the "plate" or sticker and I found out why the WAP didn't work. The bl00dy sticker was UPSIDE DOWN!
Here's an update on this issue. I have had about a 2% failure rate on my 3502i's due to blue, green, and white light freezing. We sent several unit to Cisco's wireless engineer team in Richfield. They have found the issue and have written a fix and are currently doing testing this weekend. They are sending a senior wireless engineer to my office on Monday morning to apply the fix on the 200 units that we have yet to deploy. This is the bad part: the fix can only be applied through the console port and they won't have this integrated into a controller code until May/June. The good news is they have a fix or will just RMA with no questions. I have a webex with their wireless team to explain exactly what the issue is, but from what I gathered is something to do with the boot loader image and the IBM chip in the unit. I will follow up with you guys on Mon/Tues.
Sent from Cisco Technical Support iPhone App
There is a known issue as thomas03usmcsf has stated. The bug for this particular issue "White LED" is CSCtw90465. Feel free to take a look on the Cisco Bug Toolkit. The root cause has been possibly linked to a few other bugs, but this is tracking the problems associated with the white LED behavior. At this time, contact TAC to process an RMA on the unit until there is a true fix available. You may be asked to submit your unit for Failure Analysis once the RMA is processed.
Yes we have recently been hit by 3 3502i with the "white" light use.
At first Cisco was just RMA'ing them through the normal channel then on the last one the engineer explained it is a known issue and was having us send the defective unit to a non standard RMA address when cross shipping the replacement.
Sounds like they have a good handle on it and as we experience it (3 out of about 95) we just process an RMA with support.
For us the issue came in from the last 2 batches and have no issues with the original 70 or so units deployed.
This issue appears to have been resolved by a newer version of code for the APs and the controllers. Details can be found here: http://www.cisco.com/en/US/partner/ts/fn/635/fn63537.html
This link is at least for me "forbidden".
Anyway, this issue should be fixed with controller release 184.108.40.206. Please not, the accesspoint will bright the white LED some seconds/minutes while doing the software upgrade, do NOT unplug it in this time.
Apologies. Here is the short version of the solution:
Revised September 25, 2012
Calibration between DRAM and processor on AIR-CAP350x and AIR-LAP126x results in Access Points (APs) failing to boot properly. One symptom includes a white LED and no console output.
The root cause is the DDR memory calibration process that was performed on the Access Points (APs) at the time of manufacture. The fix recalibrates the existing memory hardware, so it will operate more reliably.
The fix for this issue is now publicly available. Go to www.cisco.com to obtain Access Point (AP) IOS code version: 15.2(2)JA or later and/or WLC software version: 220.127.116.11 (or later 7.0 release), 18.104.22.168 (or later 7.2 release) or 22.214.171.124 (or later 7.3 release).
As of June 2012, new AP3500 and AP1260 products with version ID (VID) V02 are free of this issue.
If you need assistance with downloading this code, I would suggest contacting your Cisco partner...
Please remember to rate useful posts, and mark questions as answered
I agree with most of this post and have had the same problem. For whatever reason, after an AP would register to a controller the LED would stay lit for a 3502. After you rebooted the AP, the LED would NOT BE LIT.
The fix for this, which is very odd, was to do the following:
Go to the Controller via SSH/Telnet. Do the following command...
config ap led-state enable all
After we did this, the LEDs on all 3500s came online and stayed online. You will also get a message saying something like this (for all APs having issues):
Successfully set LED-State for AP GSH_1_AP48
We then rebooted a couple problematic APs and they stayed online after the reboot. Weird, weird bug.
We were running version 126.96.36.199 version of code on the controller, V02 3502i APs on code 12.4(23c)JA6
Hope this helps as this is what helped us.
I just ran into this also with a client of mine on 188.8.131.52 and I just run the config ap led-state enable all from the CLI and be done with it. We shall see if the lights stay on or end up turning off again.
Help out other by using the rating system and marking answered questions as "Answered"