cancel
Showing results for 
Search instead for 
Did you mean: 

AP's not connecting to XIQ

AP's not connecting to XIQ

Kaspervtz
New Contributor

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?

1 ACCEPTED SOLUTION

Ash_Finch
Contributor III

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

View solution in original post

7 REPLIES 7

Kaspervtz
New Contributor

@StephanH : Yes i released the IP on the old Pilot account and added it as described.

 

@Ash Finch ; i don't have the option ‘show capwap client’ while i'm connected with SSH.

i only have these options:

49c6aa5ceda54cfb98448c6740ebb653_7379778b-27ec-446e-84c5-30962d7deab6.jpg

 

StephanH
Valued Contributor III

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

Regards Stephan

Ash_Finch
Contributor III

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).

GTM-P2G8KFN