Release Notes

3. Known Issues and Vulnerabilities Addressed
41 of 69
The ExtremeAnalytics engine was running out of storage space
as a result of duplicate entries saved in the log.
01909813
After running the Configure VOSS App-Telemetry script, no
status indicating whether the device was reachable was
displayed.
01897718
ExtremeAnalytics did not allow you to disable the Virtual Sensor
integration. You can now disable this integration to improve
performance.
------
Devices managed using an SNMP Context String were causing a
NumberFormatException error in the server.log.
------
Workflow Signal Activity was not working correctly when
triggered from an alarm/trap.
------
Devices discovered via the ZTP+ process with a Poll Type of
SNMP were occasionally automatically updated by Extreme
Management Center to a Poll Type of ZTP+.
01893092
Security enhancements were requested for the Analytics Engine,
and implemented as follows:
l The server certificate has been regenerated with an
improved hashing algorithm.
l The server responses now includes the X-Frame-Options
HTTP header to protect against clickjacking.
01937342
Inventory override settings (for example, File Transfer Mode) for
a device were changing to default values after a device
refresh/rediscover or after a server restart.
------
Inventory configuration templates were occasionally not
available in the Restore Configuration window.
------
Selecting the Application Flows tab when users did not have
access to an Analytics engine that was modeled on their server
resulted in an error message and a browser error message
repeatedly displaying every few seconds.
------
Site collectors did not allow users to select countries and cloud
provider regions to be tracked or not tracked.
------
ExtremeAnalytics engines could not interoperate with Extreme
Management Center using a non-standard (8443) server port.
01800638