Unable to configre AP7522

[peawet08]

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

[peawet08]

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!!

[ckelly]

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.

[peawet08]

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

[aholden]

Ok

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

you can then enter the following

connect

[ckelly]

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.