Add AP 4000 1 WW to Extrem IQ Controller on prem.

[Sebu]

Hello everyone,

how can I connect/add an AP-4000-1-WW to the Extrem IQ Controller on prem? 

With the AP-3935i-ROW I was able to set a static auth IP using the following commands:

cset authip 1 <ctrlIP>
capply
csave
reboot

I haven't been able to find any suitable settings on the AP-4000 when I connect to the device via SSH.

If I add a static IP address to the mgt0 interface. I still can't find the device on the Extrem IQ Controller.

[Ken_Applebaum · Accepted solution]

Hi,

I believe this AP first needs to connect to the ExtremeCloud IQ Pilot (Extreme's cloud based onboarding/management platform at https://extremecloudiq.com/login), so it can apply the correct regulatory fingerprint. You would need to enter the serial number of the AP in this portal, and chose to "Manage your devices locally". If all works properly, it should onboard to your on-prem Cloud IQ controller. My experience has been that this does not always work as designed, and you may need to have GTAC assist if the AP does not onboard properly.

[AntonScholz · Accepted solution]

All Universal APs, also the AP4000, are starting out of the box with the "HiveOS" for Cloud-Deployment.
Please change the OS first to Wing, following the steps as "Ken_Applebaum" described.

Wing-OS is splitted in two operating-modes:
centralized (XIQ-Controller) -> your need this
distributed (WING-Controller)

The AP will normally find out the correct mode after OS-Change at the discovery-process by itself.

Here a step-by-step Guide for the doing:
https://extremeportal.force.com/ExtrArticleDetail?an=000092794

Best Regards

[Sebu]

Okay,

I'll take the steps one by one.

Thank´s all for the information and help

Best regards

[Jan_Reister · Accepted solution]

The standard procedure is 1) onboarding the AP on XIQ cloud as a locally deployed device; 2) have the AP connect to XIQ cloud, and auto reboot with a Wing firmware image for local deployment; 3) let the AP discover the controller IP via DNS, DHCP or other; 3b) you can specify the controller IP when you onboard it on XIQ cloud.

AP4000 needs a slightly different process because it ships with an old firmware (at least it's my experience) that fails the local deployment process. You must onboard it as a cloud managed AP first, upgrade the firmware, and only then change OS to Wing as explained in the below link, section 2 Switching from IQE (ExtremeCloud IQ Engine)  to WiNG in XIQ (2nd method).

https://extreme-networks.my.site.com/ExtrArticleDetail?an=000092794&q=onboard%20locally

[AntonScholz · Accepted solution]

All Universal APs, also the AP4000, are starting out of the box with the "HiveOS" for Cloud-Deployment.
Please change the OS first to Wing, following the steps as "Ken_Applebaum" described.

Wing-OS is splitted in two operating-modes:
centralized (XIQ-Controller) -> your need this
distributed (WING-Controller)

The AP will normally find out the correct mode after OS-Change at the discovery-process by itself.

Here a step-by-step Guide for the doing:
https://extremeportal.force.com/ExtrArticleDetail?an=000092794

Best Regards

[Ken_Applebaum · Accepted solution]

Hi,

I believe this AP first needs to connect to the ExtremeCloud IQ Pilot (Extreme's cloud based onboarding/management platform at https://extremecloudiq.com/login), so it can apply the correct regulatory fingerprint. You would need to enter the serial number of the AP in this portal, and chose to "Manage your devices locally". If all works properly, it should onboard to your on-prem Cloud IQ controller. My experience has been that this does not always work as designed, and you may need to have GTAC assist if the AP does not onboard properly.