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
24 of 69
ExtremeControl Issues Addressed ID
Policy was not supported on ExtremeXOS X435 and X465
devices.
------
ExtremeControl was failing to enforce Inbound User-Based (IUB)
and Outbound User-Based (OUB) rate-limits to the ExtremeCloud
Appliance when the rate-limiters were mapped to an IUB or OUB
reference index of 0.
------
When searching for and selecting an end-system in
ExtremeControl, the Port View and associated tabs were
rendering slowly. This was caused by the Search function being
blocked while waiting for SNMP port values to complete.
------
The Extreme Management Center server was obtaining supported
RADIUS attributes from ExtremeControl engines more often than
necessary.
------
Adding a second device to the Network Resource Topology table
was causing the table to not display.
01991030
Enforcing a policy domain with roles that have Policy VLAN
Islands in the Vlan Egress tab was failing.
01973709
01977152
01960986
01978336
Policy Manager failed to enforce CoS rate limit mappings to the
ExtremeCloud Appliance when rate limits were not defined using
Kbps units in the domain.
------
The Policy Domain Verify action failed after importing CoS
configuration with unused rate-limiters from an ExtremeCloud
Appliance into an empty policy domain.
------
The Policy Domain Verify action was failing after a CoS
configuration with multiple rate-limiters using the same rate was
imported from an ExtremeCloud Appliance (XCA) into an empty
Policy Domain.
------
When an existing CoS rate-limiter's rate was changed and
enforced to an ExtremeCloud Appliance (XCA), the rate was
failing to update.
------
Policy enforce was failing for S/K/TOR-Series devices when user-
defined L7 application signature rules were defined in the
domain.
01977353