Release Notes
Table Of Contents
- Extreme Management CenterĀ® Release Notes Version 8.4.4
- Table of Contents
- Extreme Management Center Version 8.4 Release Notes
- 1. Enhancements in Version 8.4
- 2. Deprecated Features
- 3. Known Issues and Vulnerabilities Addressed
- 4. Installation, Upgrade, and Configuration Changes
- 5. System Requirements
- 5.1 Extreme Management Center Server and Client OS Requirements
- 5.2 Extreme Management Center Server and Client Hardware Requirements
- 5.3 Virtual Engine Requirements
- 5.4 ExtremeControl Agent OS Requirements
- 5.5 ExtremeControl Supported End-System Browsers
- 5.6 ExtremeControl Engine Version Requirements
- 5.7 ExtremeControl VPN Integration Requirements
- 5.8 ExtremeControl SMS Gateway Requirements
- 5.9 ExtremeControl SMS Text Messaging Requirements
- 5.10 ExtremeAnalytics Requirements
- 5.11 Ekahau Maps Requirements
- 5.12 Guest and IoT Manager Requirements
- 6. Getting Help
3. Known Issues and Vulnerabilities Addressed
30 of 69
Extreme Management Center was attempting to prune VLANs
that were dynamically created on the device by MVRP or Policy
when VLAN pruning was enabled. This was only a display issue in
the enforce preview window. The dynamic VLANs were properly
being filtered out during the actual enforce operation.
------
IP addresses that were removed from Extreme Management
Center were included in a Statistics Collection target.
1892488
The tagged field of a port would sometimes incorrectly display
'All' after disabling the VLAN trunk feature on the port. Similarly,
the tagged field would sometimes fail to display 'All' when VLAN
trunk was enabled on the port.
------
Unregister Syslog Receiver was failing to remove the Extreme
Management Center server entry on SLX or VDX devices that
were configured to use an in-band port for their management
address.
------
ExtremeAnalytics Issues Addressed ID
An issue where the units for free disk space on the Analytics
Dashboard were incorrect has been resolved.
01951501
Starting a packet capture from the ExtremeControl > End- System
table was causing it to fail and display an error message.
------
ExtremeAnalytics was improperly counting end-systems that
were not producing traffic, potentially causing end-system
license violations and inaccuracies with end-system usage.
1949270
The ExtremeAnalytics engine was becoming unresponsive after
the QUIC decoder stopped functioning.
01897413
ExtremeControl Issues Addressed ID
LACP/LAG link information was not being provided for ZTP+
managed devices.
------
Editing an LDAP Configuration with a Name that started or ended
with a space was causing Extreme Management Center to remove
the space, which resulted in a subsequent enforce to fail.
------