This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Extreme Networks
- Community List
- Wireless
- ExtremeWireless (General)
- Re: AP3000 don’t Connect to XCC
Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
AP3000 don’t Connect to XCC
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-11-2023 10:19 AM
Hello, we have several AP3000s that do not connect to the XCC. Actually, you have to connect the access points to the cloud and send them into local mode because you can no longer switch to WingOS from the new generation.
Earlier generations such as the AP305 connect without problems.
Unfortunately, I don't know how to connect the access point to the controller manually via SSH or how to set it to local mode.
I hope someone can help me.
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-13-2023 05:27 AM
Hey we finally got the problem fixed. The port UDP 12222 was not maintained in our firewall. We were also given a command to boot the access point locally via SSH. The command is: _system boot-os WING
In addition, they can be redirected via SSH using:
capwap ping redirector.aerohive.com
to check whether your connection to Extreme IQ Pilot is also faulty.
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-12-2023 06:27 AM
Starting not long ago and going forward, any model AP that HAS the ability to be managed by ExtremeCloud IQ (Cloud) but also supports management by either Cloud IQ Controller (aka XCC) and/or WiNG management platforms, must FIRST connect to ExtremeCloud IQ and then be changed to 'local' mode using the Cloud platform.
If you have APs that are not following this logic, it's likely because they are loaded with factory firmware that predates this operation.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-12-2023 05:43 AM
We had issues with the AP4000 not onboarding as local, and had multiple tickets open with GTAC in an attempt to address it. Initially I was told that this was an issue with the ExtremeCloud IQ Pilot. An upgrade was made to the Pilot, but that did not resolve the issues we had.
What was odd was some of the AP4000's onboarded properly, and others did not. As time when by, one AP, and then another onboarded as local, and not as a result of a configuration change or AP reset to factory defaults. Personally, I am not liking this onboarding via the ExtremeCloud IQ Pilot. Some model APs onboard properly (AP5050D), and others do not, and as far as I know, GTAC has not identified what the issue that affected our AP4000s is.
All that said, your best bet may be to contact GTAC, since AFAIK there isn't a way to manually have your AP onboard as local due to the fact that they need to be assigned a regulatory "fingerprint" based on the country you are in, prior to onboarding locally as a WiNG device.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
10-13-2023 05:27 AM
Hey we finally got the problem fixed. The port UDP 12222 was not maintained in our firewall. We were also given a command to boot the access point locally via SSH. The command is: _system boot-os WING
In addition, they can be redirected via SSH using:
capwap ping redirector.aerohive.com
to check whether your connection to Extreme IQ Pilot is also faulty.
