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
- Network Management & Authentication
- ExtremeCloud IQ- Site Engine Management Center
- XIQ AP Import Workflow Error - Unable to Pull Devi...
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
XIQ AP Import Workflow Error - Unable to Pull Device List
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
06-17-2025 05:12 AM - edited 06-17-2025 05:14 AM
We are trying to bring in Universal APs that are managed in XIQ. We use XIQ-SE for NAC for BYOD access.
This is something that one of our Extreme SE provided partners set up for our organization, who no longer works at Extreme. GTAC Support told me to post the question here, so here I am.
We have used this workflow flawlessly without error for the past 2 years up until now. Nothing has changed in either of our environments (XIQ or XIQ-SE).
Any insight as to what could be causing the error? See the attached image.
Thanks in advance for any replies.
Solved! Go to Solution.
1 ACCEPTED SOLUTION
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
07-02-2025 04:20 AM - edited 07-02-2025 04:22 AM
The root cause of the error we were receiving was because of the existing XIQ user account that was being used in the XIQ AP Import workflow within XIQ-SE suddenly stopped working.
The Extreme SE did state that XIQ recently released a "scopes" feature which could have possibly caused the user account to be exposed to incorrect set parameters within XIQ. In XIQ when we attempted to set/update the existing XIQ user account used to pull XIQ APs in to XIQ-SE as the scope for all locations, the page would error out.
Our solution was to simply create a new XIQ User account, update the XIQ AP Import workflow with the new user account, and the workflow began completing as expected.
Since we were using an XIQ user account to pull APs in to our XIQ-SE environment, API tokens were not a factor in play.
7 REPLIES 7
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
06-19-2025 05:26 AM
Where are these workflow files "typically" stored at on XIQ-SE if we are dropping the file into the server via WinSCP?
Since an Extreme SE built this for our organization, we have no knowledge of these types of processes. And Extreme's KB don't appear to provide much guidance on best practices.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
06-20-2025 09:32 AM - edited 06-23-2025 05:51 AM
Go to Tasks>Workflows to see the workflows that have been imported. Best you download and import the latest one Zdenek pointed you at and go from there. There was an older workflow which needed the bearer token adding to the script which might be what you are using and that token could have expired. Best you use the latest and reach out to your local SE or update everyone here as someone may be using the latest one and can advise on how to use the workflow if anything needs adding to XIQ Global Settings API Management?
Edit: The latest workflow uses a different method to check XIQ which is to provide the XIQ username and password. In your world site hierarchy you can have a site for APs and set the site action 'Add Device to Access Control Engine Group' I believe.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Get Direct Link
- Report Inappropriate Content
06-24-2025 04:00 AM
Found in XIQ-SE where to import the scripts from GUI. Since we have not had to import scripts into XIQ-SE, the gear button in the bottom left corner of the workflows menu was not obvious. Additionally, the focus has to be set to a group top level menu and not on a specific existing workflow (otherwise if an existing workflow is selected, the import button is greyed out).
But I imported the new script, mirrored all of the same variables and accounts to used (verified account being used is passes login to XIQ), workflow is still failing with the same error.
I do need to verify the API token status.
I have reached out to our new Extreme SE and they are going to start investigating.
