Solved

Unable to configre AP7522

  • 11 February 2019
  • 13 replies
  • 358 views

Hi,

If similar questions have been asked before, please forgive me asking again.

I am trying to add some AP's to an NX5500 (5.8.6.9).

I already have about 7 AP7522's connected and they appear to be communicating ok.

I am now trying to add an additional 7522 (5.8.6.9) that was previously connected to another controller. The AP appears to be adopted to the controller but is not loading the default policy as the other units have. The Auto Provisioning profile is configured for this AP type though.
When I query the AP in the dashboard I can see the old Wireless LAN SSID's an d it is also not being assigned an IP as it should, based on the profile.

I also have an AP650 that was originally configured against old RFS controller. When connected to the NX5500, it appeared to be adopted and the firmware upgrade to 5.8.6.9.
This AP is also not downloading the profile from the controller but I can get onto this unit with SSH and can see it is just loading the default profile from the AP, not the controller.
There is no option in the NX5500 to add the Auto Provisioning to ap650 profile.
The radios on this unit are "off" and complaining about the country code not being set. However the country code is set by the RF Domain, which is associated with the Auto Provisioning Policy and as this can't be set against the ap650 I have tried to override the country code at the device level but I guess that because it isn't getting any policy it's also not accepting changes.
I have tried sending a factory reset but end up in the same situation.

Any help is appreciated as I'm new to the Extreme Wing type devices.

Thanks
icon

Best answer by peawet08 12 February 2019, 16:48

Hi Chris,

Thanks for your help. It was a configuration issue in the default-ap650 profile I had created.

The key was you saying it might be layer2/3 connectivity to the controller. The issue was that I had accidentally ticked the "Tag Native VLAN" in the ethernet settings.

It looks like it is working now.

If we were in a bar together, I'd buy you both a beer!!!

Mark
View original

13 replies

Userlevel 5
For the 7522, I would start by factory defaulting the AP and then letting it be adopted again.
You indicate that it has a matching rev of WiNG firmware, so that's not the hang up.
Userlevel 3
Try this

Log into the CLI of the controller and enter the following command

show adoption statue.

Scroll down to the new APs and look at the status column. It should say configured.. If it says "ERROR" it means the configuration that was pushed from Controller caused the AP to lose adoption. This results in it reverting back to its last known good configuration
For the 7522, I would start by factory defaulting the AP and then letting it be adopted again.
You indicate that it has a matching rev of WiNG firmware, so that's not the hang up.


Hi Chris,

Thanks for your reply.

For the 7522, if I use the GUI and tell it to Factory reset the AP, it tells me "Application Error, This feature is not supported".
I have used the CLI on the controller to run "factory-default ap650-######" which it accepted but the AP did not reset.
As the AP doesn't have an IP address, I can't connect to the console.

The unit is currently mounted so it would be difficult to connect via serial at the moment.

Mark
Try this

Log into the CLI of the controller and enter the following command

show adoption statue.

Scroll down to the new APs and look at the status column. It should say configured.. If it says "ERROR" it means the configuration that was pushed from Controller caused the AP to lose adoption. This results in it reverting back to its last known good configuration

Hi Andrew,

Thanks for that.
I am seeing the following....

code:
Adopted Devices:
---------------------------------------------------------------------------------------------------------------
DEVICE-NAME VERSION CFG-STAT MSGS ADOPTED-BY LAST-ADOPTION UPTIME
---------------------------------------------------------------------------------------------------------------
ap650-###### 5.8.6.9-003R error Yes nx5500-###### 0 days 00:20:47 0 days 00:22:54
ap7522-###### 5.8.0.0-050R version-mismatch No nx5500-###### 0 days 00:03:02 0 days 01:01:10


Thanks

Mark
Userlevel 5
If there's no IP address and a direct serial connection isn't convenient, your last method of connection is using MiNT.

On the CLI of one of the other online APs, issue the command:
# show mint neighbors
In the resultant output, see if you can find the the 650.
If you can, copy the 4 Byte MiNT-ID (xx:xx:xx:xx)

Now, from the same CLI, enter the command:
# connect mint-id [650 MiNT ID that you copied]

If this works, you'll see a login prompt just like you do when you SSH into the AP.
Userlevel 3
Ok

You can log into the controller and find the HOST NAME of the adopted AP

you can then enter the following

connect
Ok, the firmware on the AP7522 hadn't updated. I could have swore it had.

I'm updating that now.

But the AP650 IS on the correct version
Userlevel 5
So looks like the 7522 does NOT have a matching version of WiNG firmware. This is why the 7522 isn't getting a config push from the controller.
You need to upgrade the 7522 and then all will be good.

The 650 is a different story.
There's an error.
Indicates almost certainly that the 650 DID receive a config from the controller, but the config contained something that caused it to lose its connection with the controller. The AP then auto-reverts back to the last known config that allowed it to re-adopt to the controller.
Chris/Andrew,

Thank you. The AP7522 is now working.

It didn't surprise me when I had issues with the 650 but did when the 7522 didn't work.

Now for the 650...

I do have access to the CLI on the 650 as it has an IP address. Can I change the default logging so that after reboot I might be able to lift something from the logs?

Mark

PS: Thanks for the speedy responses!!
Hi,

I have tried setting the buffered logging to debugging (7) and then rebooting the AP, but the logs don't seem to contain any additional information on the error that is causing the AP not to apply the profile from the controller.

Is there a command I can use to force the AP to re communicate with the controller such that it tries to apply the profile?

Thanks

Mark
Userlevel 5
You can force the controller to send the config again using this command:

# service force-send-config on "AP Name" (hit the TAB key after "on" to see a list of the APs)

If the config is the issue, which it appears to be, the same thing will happen. The AP will try to re-adopt several times and finally give up...and then revert to the previous config.

What you can do though is log into the AP after force-sending the config (and BEFORE it reverts again) and take a copy of the running-config so that it can be analyzed offline. You're dealing with a networking related issue at this point so you would be looking for things in the config that would break either layer-2 or layer-3 connectivity to the controller. So things like ge1 interface setup is wrong or the controller-host entry is wrong, or mint mlcp [VLAN or IP] is missing. Something along these lines. Look for config entries that could prevent the AP from being able to reach the controller.
Hi Chris,

Thanks for your help. It was a configuration issue in the default-ap650 profile I had created.

The key was you saying it might be layer2/3 connectivity to the controller. The issue was that I had accidentally ticked the "Tag Native VLAN" in the ethernet settings.

It looks like it is working now.

If we were in a bar together, I'd buy you both a beer!!!

Mark
Userlevel 5
Good work, Mark!
This exact scenario is usually the most difficult to troubleshoot when you have adoption problems....because you don't know what is causing it.
What's really nice though is the reversion feature since it at least gets the AP re-adopted again so you can see it/access it...and doesn't leave the AP orphaned somewhere.

Reply