ExtremeCloud™ IQ UI Transition: What You Need to Know

[SamPirok]

UPDATED: July 2026

The ExtremeCloud™ IQ classic UI will be retired in Q2 calendar year 2027.  The new UI has been available since July 2025 to ensure customers have ample time to become comfortable before the classic UI is retired. 

We will be transitioning from the classic UI to our modernized new UI which will become the default interface for all ExtremeCloud IQ customers. The final operational date for the classic UI is yet to be confirmed and will be communicated closer to the transition period. 

Currently administrators are presented with the classic UI when initially logging into ExtremeCloud IQ. Beginning in November 2026, by default customers will be presented with the new UI but will have the option to toggle via the 9-dot menu back to the classic UI. 

Why is This Transition Needed? 

The new UI is built on a next-generation architecture that delivers: 

• Improved performance and stability 
• Streamlined workflows with a modern, and easier to use UI design 
• Enhanced monitoring, troubleshooting, and visibility 
• A scalable foundation aligned with Extreme’s cloud-managed roadmap 

Seamless Transition to ExtremeCloud IQ new 

• Customers will have a new UI and UX to manage their networks with ExtremeCloud IQ new  
• There will be NO IMPACT to customers data / networks / logs / devices  
• Customers will continue to manage and monitor their network as they have been doing prior to the upgrade 

What are the changes and their impacts? 

• There will be NO IMPACT to existing networks. 
• Same URL and login credentials
• No licensing or entitlement changes 
• Network configurations, policies, data, permissions, and performance remain 
  unchanged 
• Only the UI experience is updated 
• Administrators will manage and monitor their networks exactly as before, but 
  now with a modernized interface 
• Existing features in the classic UI that will be retired and replaced by advanced features. These 
  include: 
  • WiNG Controller Data in Connected Mode 
  • A3 
  • SR and Dell Switch support 
  • XR Routing Support 
  • Legacy Entitlement Keys (LEK) 

Recently added functionality: 

• The Guest, WIPS, and Location features (formerly known as Essentials) 
• Improved administrator roles and RBAC functionality 
• Manual packet capture 
• Local AP, Controller, and Tunnel Concentrator onboarding and monitoring. 
• ExtremeCloud IQ Site Engine monitoring 
• Enhanced Filtering Options 

Resources 

• UI Transition FAQs (Updated) 
• UI Feature Comparison  

UI Transition Workflow Videos - Classic to new 

The following videos are available here: 

• ExtremeCloud IQ UI Transition Introduction - (Updated) 
• Device Filtering 
• Device Onboarding 
• Device Status, Health, Usage Capacity 
• Menu Changes 
• Upgrading Device 
• ExtremeGuest Essentials – Classic UI to New UI - (New) 
• ExtremeLocation Essentials – Classic UI to New UI - (New) 
• XIQ Classic to XIQ New UI Transition Overview and Hardware Support_VoD - (New) 
• XIQ Classic to XIQ New UI Transition - Feature Updates Demo_VoD - (New) 

[D_Bereda]

@DeVoID Yes for now the AI is pretty useless, except the demo questions seen in some videos.
I don't know whether to laugh or cry ..

[daniel1]

Another killed feature in XIQ new, no more advanced cli, just preconfigured commands: Q A: Where is the CLI access to Access Points in Platform ONE

[D_Bereda]

@daniel1 That's what I have already mentioned! Why is there no option to send CLI commands for troubleshooting purpose? Or even enable the Web SSH Shell for APs like already available for switches? 

[ckelly1]

This is a super TL;DR thread, so I just started on Page 5 LOL.  Network Devices - can sort some, since my AP names relate to the buildings where installed.  There's a Site button - shows the one site, no break down so no way found so far to look at "2nd floor" APs only.  The Sites under Configuration show the buildings and floors, but no connection to managing devices. 

Sites - unsorted.  Now they have to have an address, which is fun because small campus, same address, all stacked on top.  But the "import" is just a mess and I'll have to edit every single building to try and get some sense to it. 

The no CLI thing is also a terrible omission

I like how a potential disaster is readily seen with the Inventory/Model column showing blue for every AP that could cause us to buy more APs. Sadly, the AP410C is in there, some of which we bought recently.  I get the AP121 and 122s, but we typically use those for "basic" wifi things, like bringing wifi enabled water sprinkler controls online, stuff in basement boiler rooms, etc.   

EDIT - seeing not all are flagged with "blue" - weird.  EP1 says we have 128 devices at EOS/EOSM/EOSL while XIQ counts 137 devices. 

This reminds me very much of Aerohive and "HiveManager NG" which was never ready for prime time and why we stayed on Classic OnPrim until we had to move everything into XIQ.  

[DeVoID]

@daniel1 Hold the PHONE......  Did I just find the supplemental CLI!?!?!?1 in EP1!!??

Check out the screenshot:

Under Administration & Settings, below that Backup & Restore, near top select VIQ management, and then below in main panel, Supplemental CLI!!! I think thats it, because to the right of VIQ management, is the default password...

Check it out, is that it? did I spot the unicorn?

DeVoiD

[DeVoID]

oh.... predefined CLI "commands".... via that diagnostics clickable...  just give us the little input box so that we can type in the CLI command we want.....  maybe I didnt find what  thought it was... i think what I found is purely for SSH... but calling it supplemental CLI that makes you think its an actual way of inputting a CLI command into the AP.

DeVoID

[ckelly1]

I did find the Clients when looking at the Devices list.  That little switch on the right.

[daniel1]

@DeVoID supplemental CLI is for adding your own commands into the AP config during a complete configuration update and already exists in Classic with this name.

[DeVoID]

@daniel1 Yeah, I know.  I thought in a previous post someone said that it wasnt included in EP1.... hence me saying I found it.

Also interesting you said you use it during complete config.  I dont think ive ever used it for anything to do with that - not sure how that during would work - .  I have used that supplemental CLI for interrogating PoE, Noise and such, maybe to see a running-config, but thats about all.  Again though, im very sure someone posted in this very long thread that it was not included with EP1, and I found that unicorn.... or did i!? LOL

🙂

[CalvinRempel]

I have been using the new interface regularly for a while now, and here are a few of the deficiencies I have noticed:
- It would be nice if we could keep the "show more columns" toggle on in the network device view. I constantly use that information about how many clients are connected. Personally, I would get rid of the toggle and just make those "extra" columns addable in the columns selection.
- In the filters of the network device view, there is no option to filter by device location. Fortunately, at the moment, filtering by network policy gets me similar results due to how we have things configured, but it would still be nice to be able to filter by location. As well, filtering by update status like we can do in the classic view.
- The connected clients indicator in this view does not seem to be reliable. It might show 30 clients connected, but when I click into the device to view the clients, it shows that only 2 are currently connected. It would be nice if this was consistent such that I could rely upon these figures. (I think this may also be somewhat of an issue in the classic interface too).
- In the clients view, I cannot set devices to filter by. That filter can be auto-populated by clicking on the client count for a particular device, but if I wanted to change or add a second device to filter by in this view, I would be unable to. I'm not sure how often I would actually want to be able to do this, but it would be nice to have that ability.

All that said, there are some aspects that seem less buggy than classic (e.g. classic gives me troubles when trying to set APs to use DFS channels when both radios are on 5 GHz, whereas the new interface seems to do so more reliably), so that's a plus.