ExtremeCloud IQ Site Engine 25.05.11 Release Notes

A PDF copy of these release notes can be found here.

ExtremeCloud IQ Site Engine includes all the features and functionality of Extreme Management Center as well as issues that have been resolved and configuration changes for this release.

If you are an existing Extreme Management Center customer, contact your representative to have your Extreme Management Center license migrated to an ExtremeCloud IQ Site Engine license. The ExtremeCloud IQ Site Engine license also includes licensing for ExtremeAnalytics.

  IMPORTANT:
  • For upgrade and installation requirements, as well as configuration considerations, see ExtremeCloud IQ Site Engine Configuration and Requirements.
  • ExtremeCloud IQ Site Engine version 25.05.11 consumes licenses from ExtremeCloud IQ in a connected deployment mode or from a license file in air gap deployment mode. ExtremeCloud IQ Site Engine is a subscription-based -only licensing model. Existing NMS licenses do not provide access to ExtremeCloud IQ Site Engine. You can view the status of your license by accessing Administration > Licenses after the installation is complete.
  • ExtremeCloud IQ Site Engine is not compatible with an ExtremeCloud IQ Connect level account. You must use a commercial or trial subscription.
  • ExtremeCloud IQ Site Engine is not compatible with ExtremeCloud IQ HIQ. You must use a standard VIQ or MSP account.
  • For the information shared between ExtremeCloud IQ Site Engine and ExtremeCloud IQ , see ExtremeCloud IQ Connection.

For information regarding the features supported by specific devices, see the Firmware Support Matrix. Version 25.05.11 of ExtremeCloud IQ Site Engine supports the devices listed in the matrix.

Devices that do not have serial numbers or MAC addresses in Extreme Management Center must be rediscovered after you upgrade to ExtremeCloud IQ Site Engine before they can be onboarded to ExtremeCloud IQ.

Connected mode only - If your number of devices exceeds your licenses available, ExtremeCloud IQ Site Engine transitions to a license violation state and your access to ExtremeCloud IQ Site Engine is locked. To resolve the license shortage you need to access the Extreme Networks portal or ExtremeCloud IQ to evaluate the quantities of available Pilot and Navigator licenses versus the number of licenses required by ExtremeCloud IQ Site Engine.

Licensing Changes

The following sections describe licensing changes in ExtremeCloud IQ Site Engine software releases.

Version 25.2.10

Starting in ExtremeCloud IQ Site Engine version 25.2.10 the new Extreme Platform ONE subscriptions are recognized if ExtremeCloud IQ Site Engine is onboarded to ExtremeCloud IQ or Extreme Platform ONE.

Version 23.2.10

Starting in ExtremeCloud IQ Site Engine version 23.2.10 each stack member consumes a license in connected mode. In connected mode, ExtremeCloud IQ Site Engine now reports stack members to ExtremeCloud IQ. If you use stacks in connected mode, ensure that enough ExtremeCloud IQ Pilot licenses are in the license pool before upgrading to ExtremeCloud IQ Site Engine 23.2.10 or later.

Version 21.9.10

For users upgrading from Extreme Management Center to ExtremeCloud IQ Site Engine, note that the XIQ-NAC subscription must be used instead of IA-ES- license. For new users that complete an initial install of ExtremeCloud IQ Site Engine, ExtremeControl licensing does not include end-system capabilities.

Version 21.4.10

Starting in ExtremeCloud IQ Site Engine version 21.4.10, your ExtremeAnalytics license is included as part of your ExtremeCloud IQ Pilot license. Separate licenses are no longer required.

End of Software Maintenance

In ExtremeCloud IQ Site Engine version 24.10.12 and after, the following components and features are deprecated and removed:

  • Microsoft Azure Connect module (for multi-cloud integration)

  • Ekahau map import

In ExtremeCloud IQ Site Engine version 24.7.10 and after, the following components and features are deprecated and removed:

  • ExtremeCompliance, also known as Information Governance Engine

  • Public Cloud Dashboard

The following components and features reached end-of-software-maintenance on 30th September 2023:

  • Guest and IoT Manager - last version is 23.7.11.6 (not compatible with ExtremeCloud IQ Site Engine version 24.7.10 and after)

  • Fabric Manager - last version is 22.9.13.5

  • Posture Assessment (both the agent-based and agent-less)

The mobile application "ExtremeManagement ZTP+" was removed from the Google Play store in August 2024.

Onboarding ExtremeCloud IQ Site Engine to ExtremeCloud IQ in Connected Deployment Mode

After installing or upgrading to ExtremeCloud IQ Site Engine, you need to onboard ExtremeCloud IQ Site Engine to ExtremeCloud IQ. When the onboarding is complete, you can then access ExtremeCloud IQ Site Engine.

Entering your ExtremeCloud IQ name and password are required during the first-time login to ExtremeCloud IQ Site Engine.

  NOTE: If Extreme Management Center is onboarded to ExtremeCloud IQ, when you upgrade to ExtremeCloud IQ Site Engine, you need to remove Extreme Management Center from ExtremeCloud IQ before onboarding ExtremeCloud IQ Site Engine.

Enhancements

The following enhancements were made to ExtremeCloud IQ Site Engine in this release. For additional information about each of the enhancements listed in the release notes, see ExtremeCloud IQ Site Engine Documentation .

ExtremeManagement

ExtremeManagement Enhancements
Updated the PoE mib for VOSS/Fabric Engine devices using IEEE 802.3bt.

Customer Found Defects and Known Issues

Customer Found Defects Addressed 25.05.11

 
ExtremeControl CFDs Addressed ID
Addressed a case-sensitive matching issue when the authenticating username was comparing the realm name in EntraID configuration. This is now case-insensitive. 03062915
CFD-13649
Addressed an issue where installing the internal communications server certificate did not take effect until a manual Control restart. Now installing an internal certificate update will automatically restart the Control appliance for the new certificate to take effect. 03095801
CFD-13886
 
ExtremeManagement CFDs Addressed ID
Addressed an issue where importing XIQ Locations was not handling site groups correctly. Added fixes for parsing location names and sorting location display by value instead of ID. 03088229
CFD-13884
Addressed an issue where saving a long list of devices to an Alarm Group Selection did not write to the database. Now the Alarm Editor shows an error in the UI when the alarm save fails due to exceeding the size of the groupid column. 03088756
CFD-13903
Addressed an issue where GIM (deprecated) related calls caused a syntax error in server.log. GIM code was removed to no longer generate exceptions in server log due to a malformed Postgres SQL statement. 03101722
CFD-13971
Addressed an issue where an End System Group import incorrectly showed invalid during an import of mulitple groups. A fix was applied to the invalid count displayed in the group import status window. 03103627
CFD-13993
Addressed an issue with vulnerabilities reported in 25.2.10 and 25.2.11. Ubuntu version has been upgraded and the resolved security vulnerabilities have been added to this 25.5.11 CVE list. 03094692
CFD-14030

Customer Found Defects Addressed 25.05.10



ExtremeControl CFDs Addressed ID
Addressed an issue where a captive portal error would appear on an end-system during registration when IPv6 Address is discovered by RADIUS accounting packet. 02984415
CFD-12235
Addressed an issue where the URL for OpenID registration was not correctly linked to the login button when Guest Registration AUP was enabled. 03045360
CFD-13054
Addressed an issue where while evaluating the time group in Access control rule engine, an ArrayIndexOutOfBoundsException error might occur. 03045399
CFD-13056
Addressed an issue with an end-system reject. An unnecessary Certificate Rejected Expired CRL alert message has been removed. 03051842
CFD-13208
Addressed an issue where a server.log error can occur with handling special characters, including German and French characters, when creating stat collection targets that contained those special characters. 03058387
CFD-13273
Addressed an issue where the name of a control field was uneditable in the GUI if created with NBI API calls. Removed the whitespace in the the 'Name' field of the following NBI calls:
createDCMVirtualAndPhysicalNetwork
removeDCMVirtualAndPhysicalNetwork		 03062925
CFD-13381
Addressed an issue where the End-System Events table might not complete or is slow to load if a large number of end-system events exist. Improved the performance of the End-System Events table by optimizing the DB query that identifies the total number of events available to be displayed. 03047301
CFD-13423
Addressed an issue where the negation of filters in end-systems can cause a CPU spike and performance issues. Improved the query performance of the End-System table when negation filters are applied to the MAC OUI Vendor column on a Live table. 03063446
CFD-13451
Addressed an issue where the 802.1X TTLS authentication could succeed with incorrect usernames and passwords if a Token endpoint URL was being used incorrectly in an EntraID configuration. 03073535
CFD-13520
Addressed an issue where an unencrypted appSecret was displayed in the NAC appliance ApplianceConfiguration.xml file. 03078875
CFD-13580
Addressed an issue where the Message-Authenticator Attribute field displayed Required even though the database had a saved value of Not Required. 03087220
CFD-13740


ExtremeManagement CFDs Addressed ID
Addressed an issue where an error logged on startup for "nseventviewconfigs" due to event view configurations missing a valid userid. 03030409
CFD-12799
Addressed an issue where an error message did not display when an administrative login user password did not authorize due to the case sensitivity requirement for Admin-users. 03025851
CFD-12829
Addressed an issue where scheduled backups that start at 12AM failed due to a competing conflict with automated database updates that also run at midnight. 03042375
CFD-13036
Addressed an issue where a server.log error can occur when changing database password. 03058312
CFD-13262
Addressed an issue where Fabric Engine or VSP devices incorrectly used the enable password in inventory scripts when 'sys priv-exec-mode' was disabled. 03058979
CFD-13297
Addressed in issue where Export CSV in device view was showing duplicate rows. 03059051
CFD-13389
Addressed an issue with restored extracted files having wrong permissions if a non-root user restores files with the backup_restore script. 03059175
CFD-13436
Addressed an issue with the handling of the 'deviceGroup' input parameter in the 'saveRegisteredDevice' NBI mutation so that an end system group can be assigned for new and existing devices. 03063193
CFD-13555
Addressed an issue of Site's configured and enabled Add Actions not running when onboarding a device with ZTP+. The flag that indicates to the script engine that the onboarding device could need the Add Actions run was not configured properly. Now setting the flag in a location that ensures it remains configured when the script engine is running for devices onboarded with ZTP+. 03077839
CFD-13583
Addressed an issue where setup could hang if an unreachable NTP address is specified. Now there will be a 10 second delay and then setup will continue. 03079229
CFD-13570
Addressed an issue where the insertion in the database was failing due to a unicode null character. 03095862
CFD-13885
Addressed an issue where using an NBI mutation to invert an end-system group criteria in a rule using was not working properly. The invert option in the end-system group criteria now enables and disables correctly. 03065365
CFD-13488
Addressed an issue where the database summary of disk usage free in diagnostics was always reporting 0. A math conversion error for KB to GB was fixed, now the diagnostics can display the free space size in GB correctly. 03072130
CFD-13725
Addressed an issue with unexpected JAVA crashes and restarts. Fixed several SNMP issues and upgraded the JAVA library. 03088160
03087843
03081951
03095804
03104106
CFD-13767

Known Issues Addressed in 25.05.10


ExtremeControl Issues Addressed
Configuring an Access Control Engine as a "Management RADIUS Server" combined with "Auth. Access Type" as "Any" or "Management Access" is not permitted.
Management RADIUS server must not be an engine server.
Network RADIUS server must not be a primary engine.

ExtremeManagement Issues Addressed
Added support for Fabric Engine 9.x to the script "App Telemetry LiveUpdate VOSS" .
Disabled the Manage SSH users password box when type is RADIUS. Type RADIUS users are only authenticated with the RADIUS process.

Addressed Vulnerabilities

This section presents the vulnerabilities reported by vulnerability scanners in previous versions. The following components received updates in 25.5 regardless of whether the vulnerability could have been exploited or not. If you need more information on vulnerability testing, see Security and Vulnerability Testing.

25.05.11 ExtremeAnalytics, and Application Analytics Traffic Sensor images:

CVE-2024-12133, CVE-2024-12243, CVE-2024-25260, CVE-2024-26458, CVE-2024-26461, CVE-2024-26462, CVE-2024-26982, CVE-2024-31068, CVE-2024-36293, CVE-2024-39279, CVE-2024-47726, CVE-2024-56599, CVE-2024-56721, CVE-2024-57360, CVE-2024-57834, CVE-2024-57973, CVE-2024-57977, CVE-2024-57978, CVE-2024-57979, CVE-2024-57980, CVE-2024-57981, CVE-2024-57986, CVE-2024-58001, CVE-2024-58002, CVE-2024-58005, CVE-2024-58007, CVE-2024-58010, CVE-2024-58014, CVE-2024-58016, CVE-2024-58017, CVE-2024-58020, CVE-2024-58034, CVE-2024-58051, CVE-2024-58052, CVE-2024-58055, CVE-2024-58058, CVE-2024-58063, CVE-2024-58069, CVE-2024-58071, CVE-2024-58072, CVE-2024-58076, CVE-2024-58079, CVE-2024-58083, CVE-2024-58085, CVE-2024-58086, CVE-2024-58090, CVE-2025-0840, CVE-2025-1153, CVE-2025-1176, CVE-2025-1178, CVE-2025-1181, CVE-2025-1182, CVE-2025-1365, CVE-2025-1371, CVE-2025-1372, CVE-2025-1377, CVE-2025-1390, CVE-2025-1632, CVE-2025-21647, CVE-2025-21684, CVE-2025-21704, CVE-2025-21707, CVE-2025-21708, CVE-2025-21711, CVE-2025-21715, CVE-2025-21718, CVE-2025-21719, CVE-2025-21721, CVE-2025-21722, CVE-2025-21726, CVE-2025-21727, CVE-2025-21728, CVE-2025-21731, CVE-2025-21735, CVE-2025-21736, CVE-2025-21744, CVE-2025-21745, CVE-2025-21748, CVE-2025-21749, CVE-2025-21753, CVE-2025-21758, CVE-2025-21760, CVE-2025-21761, CVE-2025-21762, CVE-2025-21763, CVE-2025-21764, CVE-2025-21765, CVE-2025-21766, CVE-2025-21767, CVE-2025-21772, CVE-2025-21776, CVE-2025-21779, CVE-2025-21781, CVE-2025-21782, CVE-2025-21785, CVE-2025-21787, CVE-2025-21791, CVE-2025-21795, CVE-2025-21796, CVE-2025-21799, CVE-2025-21802, CVE-2025-21804, CVE-2025-21806, CVE-2025-21811, CVE-2025-21814, CVE-2025-21820, CVE-2025-21823, CVE-2025-21826, CVE-2025-21830, CVE-2025-21835, CVE-2025-21844, CVE-2025-21846, CVE-2025-21848, CVE-2025-21858, CVE-2025-21859, CVE-2025-21862, CVE-2025-21865, CVE-2025-21866, CVE-2025-21871, CVE-2025-21875, CVE-2025-21877, CVE-2025-21878, CVE-2025-21887, CVE-2025-21898, CVE-2025-21904, CVE-2025-21905, CVE-2025-21909, CVE-2025-21910, CVE-2025-21912, CVE-2025-21914, CVE-2025-21916, CVE-2025-21917, CVE-2025-21919, CVE-2025-21920, CVE-2025-21922, CVE-2025-21924, CVE-2025-21925, CVE-2025-21926, CVE-2025-21928, CVE-2025-21934, CVE-2025-21935, CVE-2025-21943, CVE-2025-21948, CVE-2025-21950, CVE-2025-21951, CVE-2025-21971, CVE-2025-24528, CVE-2025-25724, CVE-2025-29087, CVE-2025-29088, CVE-2025-3277, CVE-2025-31650, CVE-2025-31651, CVE-2025-21559, CVE-2025-21555, CVE-2025-21546, CVE-2025-21540, CVE-2025-21529, CVE-2025-21523, CVE-2025-21522, CVE-2025-21519, CVE-2025-21518, CVE-2025-21505, CVE-2025-21503, CVE-2025-21501, CVE-2025-21500, CVE-2025-21497, CVE-2025-21491, CVE-2025-21490

25.05.11 ExtremeControl images:

CVE-2024-12133, CVE-2024-12243, CVE-2024-25260, CVE-2024-26458, CVE-2024-26461, CVE-2024-26462, CVE-2024-26982, CVE-2024-31068, CVE-2024-36293, CVE-2024-39279, CVE-2024-47726, CVE-2024-56599, CVE-2024-56721, CVE-2024-57360, CVE-2024-57834, CVE-2024-57973, CVE-2024-57977, CVE-2024-57978, CVE-2024-57979, CVE-2024-57980, CVE-2024-57981, CVE-2024-57986, CVE-2024-58001, CVE-2024-58002, CVE-2024-58005, CVE-2024-58007, CVE-2024-58010, CVE-2024-58014, CVE-2024-58016, CVE-2024-58017, CVE-2024-58020, CVE-2024-58034, CVE-2024-58051, CVE-2024-58052, CVE-2024-58055, CVE-2024-58058, CVE-2024-58063, CVE-2024-58069, CVE-2024-58071, CVE-2024-58072, CVE-2024-58076, CVE-2024-58079, CVE-2024-58083, CVE-2024-58085, CVE-2024-58086, CVE-2024-58090, CVE-2025-0840, CVE-2025-1153, CVE-2025-1176, CVE-2025-1178, CVE-2025-1181, CVE-2025-1182, CVE-2025-1365, CVE-2025-1371, CVE-2025-1372, CVE-2025-1377, CVE-2025-1390, CVE-2025-1632, CVE-2025-21647, CVE-2025-21684, CVE-2025-21704, CVE-2025-21707, CVE-2025-21708, CVE-2025-21711, CVE-2025-21715, CVE-2025-21718, CVE-2025-21719, CVE-2025-21721, CVE-2025-21722, CVE-2025-21726, CVE-2025-21727, CVE-2025-21728, CVE-2025-21731, CVE-2025-21735, CVE-2025-21736, CVE-2025-21744, CVE-2025-21745, CVE-2025-21748, CVE-2025-21749, CVE-2025-21753, CVE-2025-21758, CVE-2025-21760, CVE-2025-21761, CVE-2025-21762, CVE-2025-21763, CVE-2025-21764, CVE-2025-21765, CVE-2025-21766, CVE-2025-21767, CVE-2025-21772, CVE-2025-21776, CVE-2025-21779, CVE-2025-21781, CVE-2025-21782, CVE-2025-21785, CVE-2025-21787, CVE-2025-21791, CVE-2025-21795, CVE-2025-21796, CVE-2025-21799, CVE-2025-21802, CVE-2025-21804, CVE-2025-21806, CVE-2025-21811, CVE-2025-21814, CVE-2025-21820, CVE-2025-21823, CVE-2025-21826, CVE-2025-21830, CVE-2025-21835, CVE-2025-21844, CVE-2025-21846, CVE-2025-21848, CVE-2025-21858, CVE-2025-21859, CVE-2025-21862, CVE-2025-21865, CVE-2025-21866, CVE-2025-21871, CVE-2025-21875, CVE-2025-21877, CVE-2025-21878, CVE-2025-21887, CVE-2025-21898, CVE-2025-21904, CVE-2025-21905, CVE-2025-21909, CVE-2025-21910, CVE-2025-21912, CVE-2025-21914, CVE-2025-21916, CVE-2025-21917, CVE-2025-21919, CVE-2025-21920, CVE-2025-21922, CVE-2025-21924, CVE-2025-21925, CVE-2025-21926, CVE-2025-21928, CVE-2025-21934, CVE-2025-21935, CVE-2025-21943, CVE-2025-21948, CVE-2025-21950, CVE-2025-21951, CVE-2025-21971, CVE-2025-24528, CVE-2025-25724, CVE-2025-29087, CVE-2025-29088, CVE-2025-3277, CVE-2025-31650, CVE-2025-31651, CVE-2025-4207, CVE-2025-1094, CVE-2025-21559, CVE-2025-21555, CVE-2025-21546, CVE-2025-21540, CVE-2025-21529, CVE-2025-21523, CVE-2025-21522, CVE-2025-21519, CVE-2025-21518, CVE-2025-21505, CVE-2025-21503, CVE-2025-21501, CVE-2025-21500, CVE-2025-21497, CVE-2025-21491, CVE-2025-21490

25.05.11 ExtremeCloud IQ Site Engine images:

CVE-2024-12133, CVE-2024-12243, CVE-2024-25260, CVE-2024-26458, CVE-2024-26461, CVE-2024-26462, CVE-2024-26982, CVE-2024-31068, CVE-2024-36293, CVE-2024-39279, CVE-2024-47726, CVE-2024-56599, CVE-2024-56721, CVE-2024-57360, CVE-2024-57834, CVE-2024-57973, CVE-2024-57977, CVE-2024-57978, CVE-2024-57979, CVE-2024-57980, CVE-2024-57981, CVE-2024-57986, CVE-2024-58001, CVE-2024-58002, CVE-2024-58005, CVE-2024-58007, CVE-2024-58010, CVE-2024-58014, CVE-2024-58016, CVE-2024-58017, CVE-2024-58020, CVE-2024-58034, CVE-2024-58051, CVE-2024-58052, CVE-2024-58055, CVE-2024-58058, CVE-2024-58063, CVE-2024-58069, CVE-2024-58071, CVE-2024-58072, CVE-2024-58076, CVE-2024-58079, CVE-2024-58083, CVE-2024-58085, CVE-2024-58086, CVE-2024-58090, CVE-2025-0840, CVE-2025-1153, CVE-2025-1176, CVE-2025-1178, CVE-2025-1181, CVE-2025-1182, CVE-2025-1365, CVE-2025-1371, CVE-2025-1372, CVE-2025-1377, CVE-2025-1390, CVE-2025-1632, CVE-2025-21647, CVE-2025-21684, CVE-2025-21704, CVE-2025-21707, CVE-2025-21708, CVE-2025-21711, CVE-2025-21715, CVE-2025-21718, CVE-2025-21719, CVE-2025-21721, CVE-2025-21722, CVE-2025-21726, CVE-2025-21727, CVE-2025-21728, CVE-2025-21731, CVE-2025-21735, CVE-2025-21736, CVE-2025-21744, CVE-2025-21745, CVE-2025-21748, CVE-2025-21749, CVE-2025-21753, CVE-2025-21758, CVE-2025-21760, CVE-2025-21761, CVE-2025-21762, CVE-2025-21763, CVE-2025-21764, CVE-2025-21765, CVE-2025-21766, CVE-2025-21767, CVE-2025-21772, CVE-2025-21776, CVE-2025-21779, CVE-2025-21781, CVE-2025-21782, CVE-2025-21785, CVE-2025-21787, CVE-2025-21791, CVE-2025-21795, CVE-2025-21796, CVE-2025-21799, CVE-2025-21802, CVE-2025-21804, CVE-2025-21806, CVE-2025-21811, CVE-2025-21814, CVE-2025-21820, CVE-2025-21823, CVE-2025-21826, CVE-2025-21830, CVE-2025-21835, CVE-2025-21844, CVE-2025-21846, CVE-2025-21848, CVE-2025-21858, CVE-2025-21859, CVE-2025-21862, CVE-2025-21865, CVE-2025-21866, CVE-2025-21871, CVE-2025-21875, CVE-2025-21877, CVE-2025-21878, CVE-2025-21887, CVE-2025-21898, CVE-2025-21904, CVE-2025-21905, CVE-2025-21909, CVE-2025-21910, CVE-2025-21912, CVE-2025-21914, CVE-2025-21916, CVE-2025-21917, CVE-2025-21919, CVE-2025-21920, CVE-2025-21922, CVE-2025-21924, CVE-2025-21925, CVE-2025-21926, CVE-2025-21928, CVE-2025-21934, CVE-2025-21935, CVE-2025-21943, CVE-2025-21948, CVE-2025-21950, CVE-2025-21951, CVE-2025-21971, CVE-2025-24528, CVE-2025-25724, CVE-2025-29087, CVE-2025-29088, CVE-2025-3277, CVE-2025-21559, CVE-2025-21555, CVE-2025-21546, CVE-2025-21540, CVE-2025-21529, CVE-2025-21523, CVE-2025-21522, CVE-2025-21519, CVE-2025-21518, CVE-2025-21505, CVE-2025-21503, CVE-2025-21501, CVE-2025-21500, CVE-2025-21497, CVE-2025-21491, CVE-2025-21490

25.05.10 ExtremeAnalytics, and Application Analytics Traffic Sensor images:

CVE-2021-42780, CVE-2021-42782, CVE-2023-2977, CVE-2023-40660, CVE-2023-40661, CVE-2023-5992, CVE-2024-26928, CVE-2024-35864, CVE-2024-45615, CVE-2024-45616, CVE-2024-45617, CVE-2024-45618, CVE-2024-45619, CVE-2024-45620, CVE-2024-56406, CVE-2024-56658, CVE-2024-57798, CVE-2024-8176, CVE-2024-8443, CVE-2025-30258, CVE-2025-32414, CVE-2025-32415

25.05.10 ExtremeControl images:

CVE-2021-42780, CVE-2021-42782, CVE-2023-2977, CVE-2023-40660, CVE-2023-40661, CVE-2023-5992, CVE-2024-26928, CVE-2024-35864, CVE-2024-45615, CVE-2024-45616, CVE-2024-45617, CVE-2024-45618, CVE-2024-45619, CVE-2024-45620, CVE-2024-56406, CVE-2024-56658, CVE-2024-57798, CVE-2024-8176, CVE-2024-8443, CVE-2025-30258, CVE-2025-32414, CVE-2025-32415, CVE-2025-27219, CVE-2024-39908, CVE-2024-43398, CVE-2024-41123, CVE-2025-27220, CVE-2025-25186, CVE-2025-27221, CVE-2024-35176, CVE-2025-1217, CVE-2025-1219, CVE-2024-11235, CVE-2025-1861, CVE-2025-1734, CVE-2025-1736

25.05.10 ExtremeCloud IQ Site Engine images:

CVE-2021-42780, CVE-2021-42782, CVE-2023-2977, CVE-2023-40660, CVE-2023-40661, CVE-2023-5992, CVE-2024-26928, CVE-2024-35864, CVE-2024-45615, CVE-2024-45616, CVE-2024-45617, CVE-2024-45618, CVE-2024-45619, CVE-2024-45620, CVE-2024-56406, CVE-2024-56658, CVE-2024-57798, CVE-2024-8176, CVE-2024-8443, CVE-2025-30258, CVE-2025-32414, CVE-2025-32415

Installation, Upgrade, and Configuration Changes

Installation Information

For license requirements for ExtremeCloud IQ Site Engine and devices, see Licensing.

For complete installation instructions, see ExtremeCloud IQ Site Engine Suite Installation.

Upgrading Without an Internet Connection

  • If your Linux system requires an operating system upgrade, you are prompted to upgrade using either an internet connection or locally (without an internet connection) if no additional Ubuntu packages need to be installed.

    !!! ATTENTION !!!

    We can attempt to upgrade the OS without using the internet if there were no extra Ubuntu packages installed. If there were extraneous packages installed, the upgrade will fail with this method.

    Do you want to attempt a local in-place upgrade of the OS and reboot when complete? (Y/n)

    • Custom FlexViews

    When reinstalling ExtremeCloud IQ Site Engine Console, the installation program saves copies of any FlexViews you created or modified in the <install directory>\.installer\backup\current\appdata\System\FlexViews folder.

    If you are deploying FlexViews via the ExtremeCloud IQ Site Engine server, save them in the appdata\VendorProfiles\Stage\MyVendorProfile\FlexViews\My FlexViews folder.

    Custom MIBs and Images

    If you are deploying MIBs via the ExtremeCloud IQ Site Engine server, they are saved in the appdata\VendorProfiles\Stage\MyVendorProfile\MIBs\ folder.

    If you are deploying device images (pictures) via the ExtremeCloud IQ Site Engine server, they are saved in the appdata\VendorProfiles\Stage\MyVendorProfile\Images\ folder.

    Important Upgrade Information

    A special MySQL to PostgreSQL Data Migration (For Upgrades from ExtremeCloud IQ Site Engine 24.2 to 24.7 and later) is required to upgrade ExtremeCloud IQ Site Engine from versions older than 24.7. The minimum version to upgrade Analytics Engines and Access Control Engines is 24.2.13.

      NOTE:

    ExtremeCloud IQ Site Engine Version 25.05.11 contains an OS upgrade. Internet connectivity is required to download custom packages.

    The installer prompts "Do you want to use the Internet to perform the OS upgrade?". The offline upgrade path is supported when no custom packages are installed (answer N). The online upgrade is required when custom packages are manually installed (answer Y). An online upgrade is recommended when an online upgrade was used previously, however there is a risk of session timeout due to 15 minutes of screen inactivity.

    To upgrade Access Control Engines and Application Analytics Engines you can use the directive --keepalive to decrease the chance of a session expiry timeout from 15 minutes of no screen activity.

    From Version (currently running) To Version (next step in upgrade path)
    ExtremeCloud IQ Site Engine 24.7.x, 24.10.x. 25.2.x, 25.5.x ExtremeCloud IQ Site Engine 25.5
    ExtremeCloud IQ Site Engine 24.2.x Fresh installation of ExtremeCloud IQ Site Engine 25.5 and follow the MySQL to PostgreSQL Data Migration (For Upgrades from ExtremeCloud IQ Site Engine 24.2 to 24.7 and later)
    Application Analytics Engine, Access Control Engine 24.2.15 Application Analytics Engine, Access Control Engine 25.5
    ExtremeCloud IQ Site Engine 23.4.12, 23.7.x, 23.11.x, 24.2.x ExtremeCloud IQ Site Engine 24.2.15
    ExtremeCloud IQ Site Engine 21.x, 22.x, 23.2.x 23.4.10, 23.4.11 ExtremeCloud IQ Site Engine 23.4.12
    Extreme Management Center version 8.5.7 ExtremeCloud IQ Site Engine 24.2.15
    Extreme Management Center version 8.2.x to 8.5.6 Extreme Management Center 8.5.7
    Extreme Management Center version 8.0.x to 8.1.x Extreme Management Center 8.3.3.11
    NetSight version 7.1.4.1 Extreme Management Center 8.3.3.11
    NetSight version 7.x NetSight 7.1.4.1
    NetSight version 6.3.0.186 NetSight 7.1.4.1
    NetSight version 6.x NetSight 6.3.0.186

      IMPORTANT: A backup (Administration > Backup/Restore) of the database must be performed prior to the upgrade and saved to a safe location.

    If you use LDAPS with a Fully Qualified Domain Name (FQDN) in the URL to authorize a user to the OneView, then ExtremeCloud IQ Site Engine presents the Server Certificate (located in Administration > Certificates > Server Certificate Information) to the LDAPS server. If the LDAPS server presents a certificate that does not match the LDAPS URL, then the certificate is rejected with the error “Certificate Unknown”.

    The best practice is to use a trusted certificate if the LDAPS URL is defined with FQDN, otherwise the LDAPS server might not accept the LDAPs connection. The alternative option is to use an IP address in the LDAPS URL instead of FQDN.

    Important Upgrade Considerations

    • If your network is using ExtremeAnalytics or ExtremeControl engines, or another add-on feature, you must first perform the ExtremeCloud IQ Site Engine upgrade to version 25.05.11 and then upgrade the feature.
    • To upgrade Traffic Sensor from version 21.x, a fresh installation is recommended. If the fresh installation cannot be used, then please check Knowledge Base for a special procedure.
    • If the online upgrade fails due to an Internet connectivity issue, fix the connectivity issue and rerun the upgrade.


      IMPORTANT: When performing an upgrade, be sure to back up the database prior to performing the upgrade, and save it to a safe location. Use the Administration > Backup/Restore tab to perform the backup.
    • When upgrading the ExtremeCloud IQ Site Engine server, ExtremeAnalyticsengine, or ExtremeControlengine to version 25.05.11, ensure the DNS server IP address is correctly configured.
    • When upgrading to ExtremeCloud IQ Site Engine version 25.05.11, if you adjusted the ExtremeCloud IQ Site Engine memory settings and want them to be saved on upgrade, a flag (-DcustomMemory) needs to be added to the /usr/local/Extreme_Networks/NetSight/services/nsserver.cfg file.

      For example:
      -Xms12g -Xmx24g -XX:HeapDumpPath=../../nsdump.hprof -XX:+HeapDumpOnOutOfMemoryError -XX:MetaspaceSize=128m -DcustomMemory

    License Renewal

    Upgrading to ExtremeCloud IQ Site Engine version 25.05.11 requires you to transition from perpetual to subscription-based license model. Existing NMS licenses do not provide access to ExtremeCloud IQ Site Engine. If your perpetual licenses were not transitioned to subscription-based licenses, contact your Extreme Networks Representative for assistance.

    Free Space Consideration

    When upgrading to ExtremeCloud IQ Site Engine version 25.05.11, a minimum of 15 GB of free disk space is required on the ExtremeCloud IQ Site Engine server

    To increase the amount of free disk space on the ExtremeCloud IQ Site Engine server, perform the following:

    • Decrease the number of ExtremeCloud IQ Site Engine backups (by default, saved in the /usr/local/Extreme_Networks/NetSight/backup directory).
    • Decrease the Data Persistence settings (Administration > Options > Access Control > Data Persistence).
    • Remove unnecessary archives (Network > Archives).
    • Delete the files in the <installation directory>/NetSight/.installer directory.

    Site Discover Consideration

    Discovering devices via the Site tab using a Range, Subnet, or Seed discover might not successfully add all expected devices. To correct the issue, increase the Length of SNMP Timeout value on the Administration > Options > Site tab in the Discover First SNMP Request section.

    ExtremeAnalytics Upgrade Information

    Enabling or disabling the disk flow export feature might cause enforce operations to time out. Enforcing again resolves the issue.

    When you delete an ExtremeXOS/Switch Engine device that is configured as a flow source via the Flow Sources table of the
    Analytics > Configuration > Engines > Configuration tab from the Devices list on the Network > Devices tab, an error message is generated in the server.log. The message does not warn you that the device is in use as a flow source. Adding the device back in the Devices list on the Network > Devices tab or removing the device from the Flow Source table fixes the issue.

    The Flow Sources table on the Analytics > Configuration > engine > Configuration tab may take a few minutes to load.

    ExtremeControl Version 8.0 and later

    Beginning in version 8.0, ExtremeControl may fail to join Active Directory when accessing as a Standard Domain User with Descendant Computer Objects ("Reset password" permissions only) group member.

    To allow this functionality, add the following permissions:

    • Reset Password
    • Validated write to DNS host name
    • Validated write to service principal
    • Read and write account restrictions
    • Read and write DNS host name attributes
    • Write servicePrincipalName

    Other Upgrade Information

    Immediately after you install version 25.05.11 on the ExtremeControlengine, the date and time does not properly synchronize and the following error message displays:

    WARNING: Unable to synchronize to a NTP server. The time might not be correctly set on this device.

    Ignore the error message and the date and time automatically synchronize after a short delay.

    Additionally, the following message might display during the ExtremeControl upgrade to version 25.05.11:

    No domain specified

    To stop domain-specific winbindd process, run /etc/init.d/winbindd stop {example-domain.com}

    Upgrading ExtremeControl Engine to Version 25.05.11

    General Upgrade Information

    The EAP-TLS Certificates with SHA1 are considered weak and are not accepted anymore. The radius server fails to start with the SHA1 certificate. You can use a more secure certificate, such as SHA256.

    You are not required to upgrade your ExtremeControl engine version to 25.05.11 when upgrading to ExtremeCloud IQ Site Engine version 25.05.11. However, both ExtremeCloud IQ Site Engine and ExtremeControl engine must be at version 25.05.11 in order to take advantage of the new ExtremeControl version 25.05.11 features. ExtremeCloud IQ Site Engine version 25.05.11 supports managing ExtremeControl engine versions 23.x and up to 25.05.11.

    In addition, if your ExtremeControl solution utilizes a Nessus assessment server, you should also upgrade your assessment agent adapter to version 25.05.11 if you upgrade to ExtremeControl version 25.05.11.

    You can download the latest ExtremeControl engine version at the Extreme Portal. 

    LDAPS servers with FQDN

    If the LDAPS server URL uses a Fully Qualified Domain Name (FQDN), then the LDAPS client of Access Control Engine presents the internal Communication Certificate to the LDAPS server. If the LDAPS server URL uses a FQDN then the LDAPS client of ExtremeCloud IQ Site Engine presents the Server Certificate (located in Administration > Certificates > Server Certificate Information) to the LDAPS server. If the LDAPS server presents a certificate that does not match the LDAPS URL, then the certificate is rejected with the error “Certificate Unknown”

    The best practice is to use trusted certificates if the LDAPS URL is defined with FQDN, otherwise the LDAPS server might not accept the LDAPS connection. If the LDAPS server URL uses an IP address then the LDAPS client (of both Access Control Engine and ExtremeCloud IQ Site Engine) does not present the Certificate to the LDAPS server.

    Upgrading to Policy Manager 25.05.11

    • Policy Manager 25.05.11 only supports ExtremeWireless Controller version 8.01.03 and higher. If you upgrade to ExtremeCloud IQ Site Engine 25.05.11 prior to upgrading your controllers, then Policy Manager does not allow you to open a domain where the controllers already exist or add them to a domain. A dialog is displayed indicating your controllers do not meet minimum version requirements and that they must be upgraded before they can be in a domain.
    • Following an upgrade to Wireless Controller version 8.31 and higher, a Policy Manager enforce fails if it includes changes to the default access control or any rules that are set to contain. To allow Policy Manager to modify the default access control or set rules to contain, you must disable the "Allow" action in policy rules contains to the VLAN assigned by the role checkbox accessed from the Wireless Controller's web interface on the Roles > Policy Rules tab. This will allow the enforce operation to succeed.

    Fabric Configuration Information

    Certificate

    Fabric Manager might be unavailable via ExtremeCloud IQ Site Engine after upgrading if the certificate is missing in ExtremeCloud IQ Site Engine Trust store.

    To ensure Fabric Manager is available, enter the Fabric Manager certificate in the ExtremeCloud IQ Site Engine Trust store using Generate Certificate option. See Add Fabric Manager Certificate for the certificate procedure.

    Authentication Key

    When you provision authentication keys for Fabric Attach, the key cannot be read back for security reasons. When the key is read from the device, it always shows "****". For this reason, it might seem that there is a configuration mismatch when one does not exist.

    Service Configuration Change

    If you change a configured service via the Configure Device window that references one of the following, and then enforce those changes to the device, the configuration on the device might change unexpectedly:

    • MLT
    • SMLT
    • Port-specific settings to a port belonging to an MLT or SMLT

    To prevent this merge, change rows in the Enforce Preview window where MLT or SMLT are in use from Current to Desired.

    To correct the issue after enforcement, modify the service on the device via the CLI.

    CLIP Addresses

    Using the CLIP Addresses table in the Configure Device window, you can enter addresses in both IPv4 and IPv6 formats. However, ExtremeCloud IQ Site Engine version 25.05.11 only supports applying a single address (either IPv4 or IPv6) to a Loopback Interface.

    Upgrading VSP-8600

    When upgrading from Extreme Management Center version 8.2 to version 8.3. manually reload previously discovered VSP-8600 devices to gain access to Fabric Connect features.

    Removing Fabric Connect Configuration

    Removing a device's Fabric Connect configuration by setting the Topology Definition to <None> may fail if the device has Logical Interfaces assigned to ISIS.

    Password Configuration

    Fabric Manager fails to onboard in ExtremeCloud IQ Site Engine if the root password includes an ampersand (&) character. Additionally, if the Administration > Inventory Manager > SCP tab contains a password that includes an ampersand (&) in ExtremeCloud IQ Site Engine, the Fabric Manager firmware does not download successfully.

    Ensure you use a password without an ampersand (&) character.

    VRF Configuration

    VOSS/Fabric Engine SNMP performance is adversely affected as the number of VRF configurations increases. This issue can be resolved by upgrading toVOSS/Fabric Engine release 8.1.1 or later or VSP-8600 series version 6.3.3 or later.

    Device Configuration Information

    VDX Device Configuration

    To properly discover interfaces and links for VDX devices in ExtremeCloud IQ Site Engine, enable three-tuple-if on the device.

      NOTE: To enable three-tuple-if on the device in ExtremeCloud IQ Site Engine:
    1. Access the Network > Devices tab.
    2. Right-click on the device in the Devices table.
    3. Select Tasks > Config > VDX Config Basic Support.

    Additionally, for ExtremeCloud IQ Site Engine to display VCS fabric , the NOS version must be 7.2.0a or later.

    Rediscover VDX devices after upgrading to ExtremeCloud IQ Site Engine.

    VOSS/Fabric Engine Device Configuration

    Topology links from VOSS/Fabric Engine devices to other VOSS/Fabric Engine or ERS devices might not display in a topology map (or might display inconsistently). To ensure topology map links display correctly, verify that the VOSS/Fabric Engine device is configured to publish its management IP address in the autotopology (SONMP) data.

    Ensure that the output of show sys setting command shows:

    autotopology : on
    ForceTopologyIpFlag : true
    clipId-topology-ip : 0

    If the output values displayed are different, configure the VOSS/Fabric Engine device to publish management IP address in SONMP data by executing the following CLI commands:

    (config)# autotopology
    (config)# sys force-topology-ip-flag enable
    (config)# default sys clipId-topology-ip

    The Status of LAG links in maps will start working after the next polling following an upgrade to ExtremeCloud IQ Site Engine. You can initiate the polling of a device by performing a refresh/rediscovery of the device.

    ERS Device Configuration

    ERS devices might automatically change VLAN configurations you define in ExtremeCloud IQ Site Engine. To disable this, change the vlan configcontrol setting for ERS devices you add to ExtremeCloud IQ Site Engine by entering the following in the device command line:

    CLI commands
    enable
    config term
    vlan configcontrol flexible

    Additionally, configure all VLANs on the port for an ERS device with the same tag status (tagged or untagged). If enforcing to an ERS device on which a port has at least one VLAN as tagged, ExtremeCloud IQ Site Engine adds all untagged VLANs to the tagged VLAN list and clears the untagged VLAN list.

    Creating an archive for ERS devices using the Network > Archives tab does not complete successfully if Menu mode (cmd-interface menu) is used instead of CLI mode (cmd-interface cli). See How To Set Default Management Interface To Either Menu or CLI Mode (https://extremeportal.force.com/ExtrArticleDetail?an=000077274) to create the archive.

    SLX Device Configuration

    When creating a ZTP+ Configuration for an SLX 9240 on which firmware version 18s.01.01 or 18s.01.02 is installed, the ZTP+ process fails if the Administration Profile value uses SSH or Telnet CLI credentials. ExtremeCloud IQ Site Engine indicates that the SSH or CLI profile is not supported by the device.

    To create a ZTP+ configuration for an SLX 9240:

    1. Create a new Device Profile with the CLI Credential set to < No Access >.
      2.   NOTE: The SLX ZTP+ Connector does NOT support configuring CLI credentials on the device.
    2. Create the ZTP+ Configuration and select the new Device Profile you created in Step 1 as the Administration Profile.
    3. After the ZTP+ process successfully completes and the device is added to ExtremeCloud IQ Site Engine, select a Device Profile that uses the correct CLI credentials for the SLX device in the Administration Profile.

    ExtremeXOS Device Configuration

    ExtremeXOS/Switch Engine devices on which firmware version 30.3.1.6 is installed do not download and install new firmware versions successfully via the ZTP+ process. To correct the issue, access the Network > Firmware tab in ExtremeCloud IQ Site Engine, select the ExtremeXOS device you are updating via ZTP+, and change the Version field in the Details right-panel from builds/xos_30.3/30.3.1.6 to 30.3.1.6.

    Firmware Upgrade Configuration Information

    ExtremeCloud IQ Site Engine supports firmware downloads and uploads to devices using TFTP, FTP, SCP, and SFTP. However, before firmware images can be downloaded or uploaded from the server, ExtremeCloud IQ Site Engine needs the root path or directory for each of the protocols. The following default root paths for each protocol are configurable from the Administration > Options > Inventory Manager tab:

    Protocol Root Path:

    • TFTP: /tftpboot/firmware/images/
    • FTP: /tftpboot/firmware/images/
    • SCP: /root/firmware/images/
    • SFTP: /root/firmware/images/

    To upload firmware images that are 2 GB or less to the server, use the ExtremeCloud IQ Site EngineNetwork > Firmware tab. For files larger than 2 GB, use a third-party client (such as SCP, WinSCP, or FTP).

    For example, to use SCP to upload a firmware image to the SCP root path on the server, enter the following:

    • scp <LOCAL_FIRMWARE_PATH> root@<ExtremeCloud IQ Site Engine_SERVER_IP>:/root/firmware/images
    • Where:
      • <ExtremeCloud IQ Site Engine_SERVER_IP>= IP Address to ExtremeCloud IQ Site Engine Server
      • <LOCAL_FIRMWARE_PATH>= fully qualified path to a firmware image on the client machine

    Wireless Manager Upgrade Information

    A High Availability pair cannot be added as a flow source if the WLAN(s) selected are not in common with both wireless controllers.

    Server and Client System Requirements

      IMPORTANT: Wireless event collection is disabled by default in version 25.05.11 due to the increase in disk space usage required. To enable event collection, select Enable Event CollectionEvent Analyze. Then select Administration > Options > Event Analyze.

    Internet Explorer is not supported in ExtremeCloud IQ Site Engine version 25.05.11.

    Operating System Requirements

    ExtremeCloud IQ Site Engine Server Requirements

    Manufacturer Operating System
    Linux Red Hat Enterprise Linux 9.4
    VMware® (ExtremeCloud IQ Site Engine Virtual Engine)

    VMware ESXi™ 6.0 server
    VMware ESXi™ 6.5 server
    VMware ESXi™ 6.7 server
    VMware ESXi™ 7.0 server
    VMware ESXi™ 8.0 server
    vSphere (client only)™
    Microsoft® Hyper-V (ExtremeCloud IQ Site Engine Virtual Engine) Windows® Server 2019
    Windows® Server 2022
    Nutanix (ExtremeCloud IQ Site Engine Virtual Engine) AHV: 20230302.101026
    AOS: 6.8.1
    Prism Central: 2024.2
    Extreme Networks Universal Compute Platform 2130C version 5.09.01

    These are the operating system requirements for the ExtremeCloud IQ Site Engine server.

    ExtremeCloud IQ Site Engine Client Requirements

    These are the operating system requirements for remote ExtremeCloud IQ Site Engine client machines.

    Manufacturer Operating System
    Windows (qualified on the English version of the operating systems) Windows® 10 and 11
    Linux Red Hat Enterprise Linux 9.4
    Mac OS X® Monterey, Sonoma

    ExtremeCloud IQ Site Engine Server and Client Hardware Requirements

    These are the hardware requirements for the ExtremeCloud IQ Site Engine server and ExtremeCloud IQ Site Engine client machines.

      NOTES: ExtremeControl and ExtremeAnalytics are not supported on Small ExtremeCloud IQ Site Engine servers.

    ExtremeCloud IQ Site Engine Server Requirements

      Small Medium Enterprise Large Enterprise
    Total CPUs 1 2 2 2
    Total CPU Cores 8 16 24 24
    Memory 16 GB 32 GB 64 GB 64 GB
    Disk Size 240 GB 480 GB 960 GB 1.92 TB
    IOPS 200 200 10,000 10,000

    Recommended scale based on server configuration:
    Maximum APs 250 2,500 25,000 25,000
    Maximum Wireless MUs 2,500 25,000 100,000 100,000
    Maximum Managed Devices 100 1,000 10,000 air gap
    8,000 connected    		 10,000 air gap
    8,000 connected
    Maximum Concurrent Management Sessions 5 15 50 50
    ExtremeControl End-Systems N/A 50,000 200,000 200,000
    Statistics Retention (Days) 90 180 180 360
    ExtremeAnalytics No Yes Yes Yes
    MU Events No Yes Yes Yes

      IMPORTANT: For optimal performance the CPU and Memory needs to reserved in the ESX Client and the virtual machine needs to be deployed using Thick Disk provisioning.

    ExtremeCloud IQ Site Engine Client Requirements

      Requirements
    CPU Speed Dual Core Processor
    Memory 8 GB
    Disk Size 300 MB (User's home directory requires 50 MB for file storage)
    Java Runtime Environment (JRE) (Oracle Java only) Version 8 (for FlexView Editor / MIB Tools)
    Browser1 (Enable JavaScript and Cookies) Microsoft Edge
    Mozilla Firefox
    Google Chrome

    1Browsers set to a zoom ratio of less than 100% might not display ExtremeCloud IQ Site Engine properly (for example, missing borders around windows). Setting your browser to a zoom ratio of 100% corrects this issue.

    Virtual Engine Requirements

    The ExtremeCloud IQ Site Engine, ExtremeControl, and ExtremeAnalytics virtual engines must be deployed on a VMware, Hyper-V server, Nutanix, or Extreme Networks Universal Compute Platform.

    • ExtremeCloud IQ Site Engine and virtual engines are packaged in the .OVA file format for VMware deployment.
    • ExtremeCloud IQ Site Engine and virtual engines are packaged in the .ZIP file format for Hyper-V deployment.
    • ExtremeCloud IQ Site Engine and virtual engines are packaged in the .OVA file format for deployment to the Nutanix through Prism Central.
    • ExtremeCloud IQ Site Engine and virtual engines are packaged in the .TAR file format for deployment to the Universal Compute Platform.
      IMPORTANT: For ESX and Hyper-V servers configured with AMD processors, the ExtremeExtremeAnalytics virtual engine requires AMD processors with at least Bulldozer based Opterons.
    ExtremeCloud IQ Site Engine Virtual Engine Requirements
    Specifications Small Medium Enterprise UCP 2130C
    Total CPU Cores 8 16 24 N/A
    Memory 16 GB 32 GB 64 GB N/A
    Disk Size 240 GB 480 GB 960 GB N/A
    IOPS 200 200 10,000 N/A

    Recommended scale based on server configuration:    		  
    Maximum APs 250 2,500 25,000 25.000
    Maximum Wireless MUs 2,500 25,000 100,000 100,000
    Maximum Managed Devices 100 1,000 10,000 air gap
    8,000 connected    		 10,000 air gap
    8,000 connected
    Maximum Concurrent Management Sessions 5 15 50 50
    ExtremeControl End-Systems N/A 50,000 200,000 200,000
    Statistics Retention (Days) 90 180 180 180
    ExtremeAnalytics No Yes Yes Yes
    MU Events No Yes Yes Yes

      IMPORTANT: For optimal performance the CPU and Memory needs to reserved in the ESX Client and the virtual machine needs to be deployed using Thick Disk provisioning.
    ExtremeControl Virtual Engine Requirements
    Specifications Small Medium Enterprise Large Enterprise UCP 2130C
    Total CPU Cores 8 16 16 20 N/A
    Memory 12 GB 16 GB 32 GB 48 GB N/A
    Disk Size 40 GB 120 GB 120 GB 120 GB N/A
    IOPS 200 200 200 200 N/A

    Recommended scale based on server configuration:    		    
    ExtremeControl End-Systems 3,000 6,000 9,000/12,0001 12,000/24,0002 12,000/24,0002
    Authentication Yes Yes Yes Yes Yes
    Captive Portal No Yes Yes/No1 Yes/No2 Yes/No2
    Assessment No Yes No No No
    1 The Enterprise ExtremeControlengine configuration supports two different scale options:
    • Up to 9,000 end-systems if your network uses Captive Portal functionality.
    • Up to 12,000 end-systems if your network does not use Captive Portal functionality.
    2 The Large Enterprise ExtremeControlengine configuration supports two different scale options:

    • Up to 12,000 end-systems if your network uses Captive Portal functionality.

    • Up to 24,000 end-systems if your network does not use Captive Portal functionality.

     

      IMPORTANT: For optimal performance the CPU and Memory needs to reserved in the ESX Client and the virtual machine needs to be deployed using Thick Disk provisioning.
    ExtremeAnalytics Virtual Engine Requirements
    Specifications Small Medium Enterprise UCP 2130C
    Total CPU Cores 8 16 16 N/A
    Memory 12 GB 32 GB 64 GB N/A
    Disk Size 40 GB 480 GB 960 GB N/A
    IOPS 200 10,000 10,000 N/A

    Recommended scale based on server configuration:
    		        
    Flows Per Minute 250,000 500,000 750,000 750,000
    End-Systems 10,000 20,000 30,000 30,000
    Raw Flow Retention (Days) 3.5 3.5 7 7
     
      IMPORTANT:

    The ESXi free license supports a maximum of 8 CPU cores, and the medium and enterprise ExtremeAnalytics virtual engine installations require 16 CPU cores. Sixteen CPU cores are only available by purchasing a permanent license. To use the ExtremeAnalytics virtual engine with an ESXi free license, adjust the number of CPU cores to 8.

    To reduce the possibility of impaired functionality, ensure at least 4 GB of swap space is available for flow storage on the ExtremeAnalytics virtual engine. To verify the amount of available RAM on your Linux system, use the free command

    Fabric Manager Requirements

    Specifications Requirements
    Total CPU Cores 4
    Memory 9 GB
    Memory allocated to Java:

    -Xms
    -Xmx

    4 GB
    6 GB
    Disk Size 60 GB

    ExtremeControl Captive Portal Supported End-System Browsers

    The following table outlines the supported desktop and mobile end-system browsers connecting to the network through the Mobile Captive Portal of Extreme NetworksExtremeControl.

    Medium Browser
    Desktop Microsoft Edge
    Microsoft Internet Explorer
    Mozilla Firefox
    Google Chrome
    Mobile Internet Explorer Mobile
    Microsoft Edge
    Microsoft Windows 10 Touch Screen Native (Surface Tablet)
    iOS Native
    Android Chrome
    Android Native
    Dolphin
    Opera
      NOTES: A native browser indicates the default, system-installed browser. Although this might be Chrome (Android), this also includes the default, system-controlled browser used for a device’s Captive Network Detection for a device. Typically, this is a non-configurable option for Wi-Fi Captive Network Detection, but default Android, Microsoft and iOS devices are tested for compatibility with the Mobile Captive Portal.

    A mobile device can access the standard (non-mobile) version of the Captive Portal using any desktop-supported browsers available on a mobile device.

    For other browsers, the Mobile Captive Portal requires the browser on the mobile device to be compatible with Webkit or Sencha Touch.

    To confirm compatibility with Webkit or Sencha Touch, open http://<ExtremeControlEngine IP>/mobile_screen_preview using your mobile web browser.

    • If the browser is compatible, the page displays properly.
    • If the browser is not compatible with the Mobile Captive Portal, the following error displays:


    ExtremeControl Engine Version Requirements

    For complete information on ExtremeControl engine version requirements, see Important Upgrade Information.

    ExtremeControl VPN Integration Requirements

    VPN concentrators are supported for use in ExtremeControl VPN deployment scenarios.

    • Supported Functionality: Authentication and Authorization (policy enforcement)
      Cisco ASA
      Enterasys XSR
    • Supported Functionality: Authentication
      Juniper SA (requires an S-Series Stand Alone (SSA) system in order to provide access control)
      NOTE: For all ExtremeControl VPN Deployment scenarios, an S-Series Stand Alone (SSA) system is required to change authorization levels beyond the initial authorization, such as when using assessment.

    ExtremeControl SMS Gateway Requirements

    The following SMS Gateways have been tested for interoperability with ExtremeControl:

    • Clickatell
    • Mobile Pronto

    ExtremeControl SMS Text Messaging Requirements

    The following mobile service providers are supported by default for SMS text messaging in an ExtremeControl deployment. Additional service providers can be added:

    AT&T Sprint PCS
    Alltel SunCom
    Bell Mobility (Canada) T-Mobile
    Cingular US Cellular
    Metro PCS Verizon
    Rogers (Canada) Virgin Mobile (US and Canada)

    ExtremeAnalytics Requirements

    To use an ExtremeSwitching X440-G2 switch as an Application Telemetry source for ExtremeAnalytics, install firmware version 22.4.1.4-patch2-5 or higher.


    Extreme Portal
    Search the GTAC (Global Technical Assistance Center) knowledge base, manage support cases and service contracts, download software, and obtain product licensing, training, and certifications.
    The Hub
    Connect with other Extreme customers, ask or answer questions, and share ideas and feedback. This community is monitored by Extreme Networks employees, but is not intended to replace specific guidance from GTAC.
    GTAC
    For immediate support, call 1-800-998-2408 (toll-free in U.S. and Canada) or 1-603-952-5000.

    Before contacting Extreme Networks for technical support, have the following information ready:

    • Your Extreme Networks service contract number and/or serial numbers for all involved Extreme Networks products
    • A description of the failure
    • A description of any action already taken to resolve the problem
    • A description of your network environment (such as layout, cable type, other relevant environmental information)
    • Network load at the time of trouble (if known)
    • The device history (for example, if you have returned the device before, or if this is a recurring problem)
    • Any related Return Material Authorization (RMA) numbers

    Top