topic Re: Access points in gui shows full config but SSH is still default in ExtremeCloud IQ

Access points in gui shows full config but SSH is still default

paul_roberts25 — Thu, 26 Jun 2025 19:32:13 GMT

I have a large estate of 600 access points. Have recently added 20 new AP305CX, they were registered a couple of months ago but just installed.

In the gui shows all connected and configuration in the audit shows all ok. Though if I SSH it is still default username and password and just has the 1 default SSID on the 5 GHZ and none on the 2.4GHZ.

I have another AP305C on the same network and IP range all works.

Only thing I can think is when came live this week temporarily ran out of licences so needed to unmanaged some devices we no longer use.

Any assistance appreciated.

Paul

Re: Access points in gui shows full config but SSH is still default

Bill_Handler — Fri, 27 Jun 2025 13:26:11 GMT

Paul,

Can you verify that these new APs have a Network Policy and Location Assigned? They will not get the full configuration unless the Network Policy is assigned. We've seen where they also do not broadcast the SSID is there is no location assigned.

If there was a licensing issue - where you were short licenses - you would get a pop-up on the screen as soon as you logged into the account stating you were short licenses.

Do you have an Extreme Partner you are working with?

Thanks,

Bill

Re: Access points in gui shows full config but SSH is still default

Jan_Reister — Sat, 28 Jun 2025 13:21:14 GMT

[my previous reply did not make it out, sorry for duplicating]

Paul, this happened to us for 20-something AP410C, 4000 and 5010 two months ago.

APs were onboarded, assigned location and network policy beforehand using the XIQ Ekahau import script. [edited to add: Then the installer went on-site and started pulling cables and installing the APs. When the first APs booted and came online, ]Some APs showed up green and upgraded on the XIQ, but with no clients connected and a blank configuration via CLI.

Our analysis pointed to a network outage in the timeframe when the APs were installed and booted up: our NTP server was unreachable and the transaction to the XIQ cloud failed because the AP was unable to verify the XIQ certificate.

APs in the same site that were installed some day after did not suffer from the issue.

It is just an hypothesis and an inconclusive one. There was an IQE push in the same timeframe. The GTAC explored the scripted onboarding procedure. It did not lead anywhere and eventually we deleted, re-onboarded and configured the APs manually.

Jan