Header Only - DO NOT REMOVE - Extreme Networks

Problems with AP650 being adopted by RFS6000


Hello,

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

35 replies

Userlevel 2
It seems to be a firmware problem.
Which version now runs on the RFS600?
Do you have a Cluster configuration on the RFS600?
Userlevel 3
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
Hello Edmundo,

Thank you for your answer. Here is the version of our RFS that is running in a clustered environment:

5.4.1.0-020R
Userlevel 2
Flaviu

From the RFs6000 that shows you with the following command via CLI

!### show adoption status
Hello Andy,

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.
Edmundo,

issuing the mentioned command will only show me the 22 adopted (working) APs
Userlevel 3
The AP650 is a "DEPENDENT" AP. It needs the controller to push out the configuration. If the AP is on the same broadcast domain, there will be no issue. If the AP is on a different subnet then the controller, the "CONTROLLER HOST" variable is needed. On a power fail/ reboot, all configuration data is lost on the AP650 and if they are on a different subnet, they will not be able to locate the Controller. If this is the case, the CONTROLLER HOST variable can be set using DHCP Option 191
Andrew Holden wrote:

The AP650 is a "DEPENDENT" AP. It needs the controller to push out the configuration. If the AP is on the same broadcast domain, there will be no issue. If the AP is on a different subnet then the controller, the "CONTROLLER HOST" variable is needed. On a power fail/ reboot, all configuration data is lost on the AP650 and if they are on a different subnet, they will not be able to locate the Controller. If this is the case, the CONTROLLER HOST variable can be set using DHCP Option 191

Andy,

connecting the failing APs directly to the RFS ports should allow the AP to locate the controller without any problems, right?
Userlevel 3
That is correct.

You mat want to consider opening a SUPPORT Case.
🙂 I would have done it if our support was still active ... unfortunately it isn't 😞
what in your opinion would the problem be? It's strange that we have 5 APs (2 previously adopted ) and 3 newly purchased (from ebay, I agree that the guarantee is not assured) that won't work.
Userlevel 1
When you have the power interuption is it causing the network switches to either power or or brownout,? are the AP's being powered localy or via a POE switch ?
Hello Phil,

All our APs are powered through a POE switch.
Userlevel 1
Does the switch go off when the power fail's or is it backed up on a UPS ?

Have the AP's gone in to the default RFdomain where there is no policy's for them ?
The switches hosting the APs are backed up but the electricity cut may vary. For maintenance reasons, sometimes, the whole building will go off for several hours and eventually the UPS will shut down. We only back up the main server room hosting the servers and the main RFS.
Userlevel 3
You indicated that the ones bought off ebay are causing the issues. Were these units properly factory defaulted before putting them on the network?
Hello Andrew,

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?
Userlevel 3
Maybe your cluster isn't working correctly. I've seen instances where the a split-brain cluster can cause similar issues. Please post the output of the CLI commands:

show cluster members
show licenses
show adoption status[/code]
Andrew Webster wrote:

Maybe your cluster isn't working correctly. I've seen instances where the a split-brain cluster can cause similar issues. Please post the output of the CLI commands:

show cluster members
show licenses
show adoption status[/code]



Ok, I'll post the results tomorrow but everything seems to work fine
Userlevel 3
If you can log into the AP, you can delete the STARTUP-CONFIG. If you are unable to log into the AP, we do have a tool that will reset them, however you will need to open a support case to receive it
Andrew Holden wrote:

If you can log into the AP, you can delete the STARTUP-CONFIG. If you are unable to log into the AP, we do have a tool that will reset them, however you will need to open a support case to receive it

Hello Andy,

I imagine that I do need a valid support license to be able to open a support case. Is this tool the same one as the Motorola_AP_Discovery_Tool ? Thanks
Userlevel 3
Andrew Holden wrote:

If you can log into the AP, you can delete the STARTUP-CONFIG. If you are unable to log into the AP, we do have a tool that will reset them, however you will need to open a support case to receive it

It is a different version that also has a reset function, otherwise it works similarly. You also need the AP's serial number to make it work.
Andrew Holden wrote:

If you can log into the AP, you can delete the STARTUP-CONFIG. If you are unable to log into the AP, we do have a tool that will reset them, however you will need to open a support case to receive it

Hello Andrew,

Here are the commands results.

Andrew Holden wrote:

If you can log into the AP, you can delete the STARTUP-CONFIG. If you are unable to log into the AP, we do have a tool that will reset them, however you will need to open a support case to receive it

Hello Andy,

Is there another way to have that tool?
Userlevel 3
Gutan,

A couple of points...

  1. The cluster looks okay.
  2. 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.
  3. 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.
  4. 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.

Reply