Network Management
ExtremeCloud IQ Wireless Access Points Not All Discovered via Orchestrator API SolarWinds Platform 2025.4
When integrating ExtremeCloud IQ with the SolarWinds Platform via the Orchestrator API, only a portion of wireless access points (APs) were discovered instead of the full set. API credentials are able to retrieve all APs outside of the SolarWinds Platform.
First published date
Last published date
Overview
When connecting your ExtremeCloud IQ tenant to SolarWinds via the Orchestrator API, you successfully pull wireless access point information. However, the SolarWinds Platform show only a portion of the APs, while:
-
ExtremeCloud IQ’s own dashboard show many more wireless access points.
-
A separate API script external to the SolarWinds Platform using the same credentials was able to retrieve the full list of APs.
Symptoms:
-
Fewer APs in SolarWinds than in ExtremeCloud IQ.
-
No specific error in the UI, but logs may show authentication or API errors.
-
Some switches may appear as APs in the SolarWinds wireless list
Product section
Cause
This has been identified as a known issue in SolarWinds Platform 2025.4.
Resolution
There are two approaches for addressing this issue:
Approach 1 – Engineering Buddy-Drop (BD) and Permanent Fix (Recommended)
- Reset ExtremeCloud Pagination Settings to Defaults:
DefaultPageSizeAPs = 100DefaultPageSizeClients = 100DefaultPageSizeRogueAPs = 100DefaultPageSizeSSIDs = 100This removes any impact from previous attempts to increase page sizes beyond supported limits.
- Work with support to get and apply a Buddy-Drop (BD) for SolarWinds Platform 2025.4.0
- Submit a ticket, reference CUST-122816, and request a Buddy Drop.
The ZIP includes a README with deployment instructions; follow these carefully.
- Submit a ticket, reference CUST-122816, and request a Buddy Drop.
- Validate AP Counts After Applying the BD
- From the ExtremeCloud IQ orchestrator node in the SolarWinds Platform Web Console, use the Discover Devices option under the Management widget to trigger a fresh discovery.
Compare the AP count in ExtremeCloud IQ’s UI with the APs visible in SolarWinds (Wireless Access Points list, dashboards, or entity views).
After applying the BD and resetting pagination, the AP count should increase to the expected count.
Some Extreme switches may appear in the wireless list due to classification nuances, which will be addressed in the permanent fix.
- From the ExtremeCloud IQ orchestrator node in the SolarWinds Platform Web Console, use the Discover Devices option under the Management widget to trigger a fresh discovery.
- Upgrade to the Version Containing the Permanent Fix
- A permanent fix is planned for a future release of the SolarWinds Platform. The BD serves as an interim workaround until the permanent fix is released. You are recommended to upgrade to the GA release containing the fix rather than relying on the BD long-term.
Additional Recommendations
- Confirm you are running SolarWinds Platform 2025.4.0 before applying the BD.
- Open a SolarWinds Support case referencing Jira CUST-122816 to request the BD package.
- If you are on a later version and still experience missing APs, gather REST walk output and diagnostics, then open a support case referencing the original bug and fix version.
Approach 2 – THWACK / Advanced Configuration Workaround (Community Content)
A community post on THWACK recommends tuning ExtremeCloud IQ monitoring by increasing pagination settings:
- Navigate to SolarWinds Platform Web Console > Advanced Configuration.
- Locate ExtremeCloud settings:
- DefaultPageSizeAPs
- DefaultPageSizeClients
- (Optional) DefaultPageSizeRogueAPs, DefaultPageSizeSSIDs
- Increase page sizes from the default (100) to higher values (e.g., 500 or 1000).
Important Notes:
- Increasing these values beyond 100 may not increase the number of APs discovered in your environment.
- The ExtremeCloud IQ API does not honor page sizes above 100, so this workaround cannot resolve the underlying issue in 2025.4.0.
- THWACK content is community-supported and provided as-is; organizations should internally assess applicability.
When to Use:
- This workaround may be useful for quick testing or in environments with fewer APs or different API behavior.
- This approach alone is insufficient in SolarWinds Platform 2025.4.