The following table lists known product issues. Issues are grouped according to ID prefix and sorted within their group with the most recently logged issue listed first. (Issue IDs are in descending order.)
| Issue ID | Description |
|---|---|
| EXOS-37458 | When using ExtremeCloud IQ to configure a single port in a VLAN as an LLDP voice port with Med Capabilities and policies and then changing the port type to access or trunk, the LLDP configuration for Med Capabilities appears on ExtremeXOS/Switch Engine devices running EXOS 33.2. |
| XIQ-39282 | After successfully onboarding locally managed APs, a misleading Device Update Failed message might appear in the Last Updated field. This is only a display issue and does not affect any functionality. |
| XIQ-34912 | Clients discovered through node alias or DHCP snooping fingerprint might not immediately appear in the Device 360 Clients table. It can take up to 10 minutes for the new entries to appear in the Device 360 Clients table. |
| XIQ-34908 | When using a stack template with a Link Aggregation Group (LAG), if the LAG has ports from different slots, you must enable Instant Port Profile/Instant Secure Port from the LAG on the template view that contains the master port. This requirement applies to a preexisting Link Aggregation Group in the template, or when creating a new Link Aggregation Group. |
| XIQ-34846 | On wired VOSS and Fabric Engine devices for Cisco Discovery Protocol (CDP), configuration pushed via ExtremeCloud IQ still requires enabling LLDP TX/RX status through device CLI, for a CDP neighbor to establish. |
| XIQ-34724 | Delta configuration push fails for Wifi0 with dual 5G mode when 5G-Low channels are not supported. |
| XIQ-33709 | Some IP VLAN pairs from the Client 360 table and Client pages might be missing if they have multiple IPs learned through Node Alias events. |
| XIQ-33498 | AP5050 AFC 6GHz FCC does not support client mode. |
| XIQ-33103 | The AFC View on the Manage Device page displays qualified AFC-governed 6 GHz access points. This feature requires version 10.7.2 or higher. The AFC View does not include onboarded devices with a firmware version earlier than the minimum required version. After upgrading to the minimum required version, the AFC View displays the qualified access points. |
| XIQ-32459 | The ExtremeCloud IQ deployment API HTTP Success status code changed from 200 to 202. |
| XIQ-31639 | The IoT heat map is always shown, regardless of whether an IoT profile is configured on the AP. There is no status for IoT radios in the API. |
| XIQ-31601 | A perimeter added or modified from the Planning page does not sync with the Realtime maps page. |
| XIQ-31433 | The Cloud Service component of iBeacon is temporarily disabled. This service will be available in a future release. |
| XIQ-26907 | A delta configuration push error might occur when configuring the port Forwarding Rule for Client Mode. Workaround: Push a complete configuration update. |
| XIQ-21339 | ExtremeCloud IQ does not display the error when aggregation is enabled with a rate-limit configuration. |
| XIQ-20909 | When configuring 6GHz radio for a country that does not support it, the configuration push to the AP3000 fails. Workaround: Revert to 2.4 GHz. |
| XIQ-19977 | The MCast rate configured in an AP template does not take effect when sCLI is presented. |
| XIQ-19509 | Access points go offline when pushed to minimum speed and half duplex transmission mode for eth0, and then they reboot. After the reboot, the configuration reverts back to minimum speed with full duplex. |
| XIQ-19498 | When the AP5010 eth0 interface is operating with maximum speed, changing the transmission type causes ExtremeCloud IQ to also generate a delta CLI for speed. |
| XIQ-19379 | When you initiate a "release to the cloud" from the controller, for an AP3000 that was onboarded as locally managed, the system deletes the AP from ExtremeCloud IQ Controller but not from ExtremeCloud IQ. |
| XIQ-19368 | The user interface overrides Supplemental CLI. If you add an sCLI object and there is a code conflict with the GUI, the GUI has priority. To give the sCLI priority, place the sCLI code at the bottom of the command structure in the audit. |
| XIQ-19320 | The Wi-Fi Interface Transmission power does not update in the Managed Device page after a bulk edit. |
| XIQ-12503 |
Network 360 shows Unknown Error when All Access Points Applications is selected and the user selects both ExtremeWireless WiNG and IQ Engine devices. Workaround: Clear selected ExtremeWireless WiNG devices. |
| XIQ-5700 | Client Trial showed only the currently connected AP when the client roamed to a different AP from the onboarded ExtremeCloud IQ Controller. |
| CFD-11529 (02957942) | API response data is unclear. |
| CFD-10699 (02906999) | Universal Access Points failed to complete the WiNG-OS conversion, even after a successful CAPWAP and STUN binding. |
| CFD-8946 (02710778, 02748750) | License descriptions are automatically cleared when the Activated status is updated. |
| CFD-7360 (02498292) | For Wing-AP sites, contrary to present implementation, customers expect to see APs offline when ExtremeCloud IQ / nsight policy is not used for that site. |
| APC-41057 | Legend labels on the SR2200/2300 switch stack graph sometimes disappear when attempting to download or print the graph. Workaround: Download one graph at a time, and open the downloaded file before choosing to download again.
Note: The SVG option is the most stable format; PNG, JPG, and PDF have spacing issues on the legend section.
|
| APC-21456 | In rare cases, ExtremeCloud IQ does not upload some IGMP sub-commands successfully. Note: SR2200/2300 only.
Workaround: Use the Supplemental CLI to upload commands when necessary. To use the supplemental CLI tool, go to , and set the Supplemental CLI slider to ON. |