For 2 years, we have APs failing to reconnect to our RFS after programmed electricity cut. They are shown as offline in Wing and phisically the Amber led is blinking every 2 sec. or so and the green led is off. I tried connecting them directly to the RFS but nothing changed. We bought 3 more APs on e-bay and we have the same issue. Tried to reset the AP using the Motorola_AP_Discovery_Tool but I see the AP connecting to the RFS and then disconnecting itself 3 or 4 seconds later. For now we have at least 5 unusable APs all with the same symptoms. Any help or advice would be appreciated as we still have to continue with this infrastructure for atl least 8 months. Thank you
There are a number of reasons why an AP650 would not adopt.
1) As in the previous response, the release on the controller and AP is important. If the AP in on Ver 4.X code and the Controller is on 5.4 or better, there is a sequence that needs to be followed to upgrade them. Please see your RELEASE NOTES.
2) How are you adopting. If the APs are in the same Broadcast domain, they will try to adopt over LAYER 2. If they are on a different subnet, you will need the set the CONTROLLER HOST variable on the AP to point back to the controller
3) If you are pushing a configuration to the AP that causes it to loose ADOPTION to the controller, the AP will revert back to its' last known good configuration
4) Do you have sufficient licenses
Yes we do have sufficient licenses. The problem is that APs that worked fine, suddenly won't work anymore after the electricity cut. The APs that we have are not manageable and have no IPs on their own. They do connect to the RFS over layer2.
Strange thing is that even connected directly to the RFS I still get this amber light blinking and no adoption.
They are not the only ones causing the issues. 2 other APs previously adopted by the RFS are having the same problems. I admit I don't know if they were properly factory defaulted before they were put on sale but I'm sure I did not factory defaulted them before putting on our network. Is there a way to do that now?
A couple of points...
- The cluster looks okay.
The APs are showing lots of uptime, but the adoption time is relatively short, just over a month. Have the RFSes been rebooted or some other loss of network connectivity occurred? Destabilization of the shared DB can also cause unadoption/readoption. There are some useful commands that can help pinpoint the issue, but you need to understand what you're looking at. I'm not sure if this CLI command is available in 5.4.1, but "show mint mlcp history" will detail what conversations are taking place between the APs and the RFS during discovery and adoption.
I noticed that there is a * in the command prompt, this indicates that a component on the RFS crashed at some point. This can occur for many reasons, you can use "service show crash-info" to get details on what that was, and "service clear crash-info" to reset the flag.
Version 5.4.1 is really really old (2012) and has loads of bugs. You can get covered with maintenance for less money than you think by getting Software & TAC coverage on your APs. This gives you access to latest software for APs and the RFS, including the ability to open cases with GTAC. I don't know what region you are in, but for reference, Software & TAC part number for an AP650 (AP0650-66030-US) is 97000-H30939 and it is $17 USD List price for 1 year coverage.
It looks like you've found the problem!
The good news is that it is possible to convert older OEMed AP650s, but I think this is onfirmware 5.7.0 and above, so you'd definitely need to get maintenance to get access to these versions.
Check here for more info: http://documentation.extremenetworks.com/release_notes/wing/WiNG_v5_7_Release_Notes.pdf
Sorry, I just can't answer that because I don't know your environment. You'd probably want to hire a wireless expert to manage this type of upgrade, as you may not be able to go straight to that version (or preferable the latest version) without passing through certain intermediate versions. What I can say is that keeping up to date with the current versions is good IT practice for many reasons, both from an operational and security perspective. In addition, it allows you to add current model APs to your system without having to resort to secondary markets like ebay and the challenges associated with that.
Thank you for your answer. We do try to keep all of our equipments updated but wifi infrastructure somehow slipped between our fingers. Anyway it is weird that some of our APs suddenly loose the adoption after a reboot. Does the blinking amber led every 2 or 3 senconds mean a firmware problem? We did not find this kind of behavior in any ReleaseNotes we've read.