ā05-11-2021 03:44 PM
Hi all,
When switching from XIQ Pilot to Connect, the access points doesn't connect to the new XIQ.
Tried to login to the SSH portal of the AP305 and pinged to Google, which works.
'show adoption status' shows: 'Discovering adoption mode (controller / cloud / ws-controller)'
Waited for about 24h now..
Does anyone know what to do next?
Solved! Go to Solution.
ā05-11-2021 05:15 PM
Ah I see, as it was an AP305C I expected it to be on IQ Engine firmware rather than WiNG. Iāve not tried this myself and not fully sure of the postiveās/negatives, but I think it would be better for the personality to be switched if youāre natively using XIQ.
https://extremeportal.force.com/ExtrArticleDetail?an=000091773&q=ap305c%20wing
ā05-11-2021 05:06 PM
i only have these options:
ā05-11-2021 04:19 PM
Hello Kaspervtz,
to be sure the basics are done.
Have you released the APs in the old āpilotā account add added in the ānewā connect account?
As described here?
https://extremeportal.force.com/ExtrArticleDetail?an=000060683
https://extremeportal.force.com/ExtrArticleDetail?an=000056853
ā05-11-2021 04:00 PM
Iād guess the APs are still looking at the āoldā server address. Have you deleted the APs from the Pilot instance?
āShow capwap clientā will give you where itās pointing to currently.
Use ācapwap client server name redirector.aerohive.comā and itāll go through the discovery process again and the redirector should point them into the Connect instance (as long as the serial numbers are in there).