Click on Join Now to Sign Up
7.4.2 Release Notes
(Release Date: March 16th, 2016)
NOTE: Version 7.4.2 introduces a mechanism that better handles DDoS attacks coming from the WAN or from malicious software, preventing the appliance from consuming too much memory. In consequence, the TCP Health report has eliminated the “Ignored Connections” count. Nevertheless, Ignored Connections for real time traffic is still available.
• 7.0.0, 7.0.1, 7.0.1u1, 7.0.2, 7.0.2u1, 7.0.3, 7.0.3u1 and 7.4.1
• 6.4.6, 6.4.7
Link to download the software image:
Major New Features:
o Exinda 10063: Recommended for Large Data Centers. Can handle up to 10Gbps of traffic for Diagnostics and Shaping and up to 400Mbps for Acceleration.
o Exinda 12063: Our largest physical appliance to date, it can handle up to 15Gbps of Diagnostics and Shaping operations and up to 2 Gbps of Acceleration operations.
Bug Fixes and Minor Improvements:
Our support reps will be happy to assist you and to get to the root cause of the problem
Release Date: February 29, 2016
Application Performance Score (APS)
The Exinda appliance can monitor several properties of the TCP flows of an application and collect metrics. These metrics are compared to an established threshold and given a score between one and ten, known as the Application Performance Score (APS). The application performance score (APS) assesses the user network performance experience of business-critical applications. The score, ranging between 0 and 10, where 0 is poor and 10 is excellent, indicates whether the app is performing as well as expected or is performing poorly.
In the Exinda Management Center you can identify the applications whose performance you consider important to the operation of the organization. As you identify these applications, you can assign thresholds against their performance scores that can trigger alerts. As the performance drops below the threshold, specified users then receive email alerts to draw attention to the issue.
Dynamic Virtual Circuits
Dynamic Virtual Circuits are used to enforce fair sharing of bandwidth among the hosts, or to limit the number of hosts on the circuit to ensure that those hosts get preferential treatment.
Virtual LAN (VLAN) Objects are used to logically separate hosts (or groups of hosts) on a functional basis rather than on a physical basis. Once VLAN Objects are defined, they can be used in Optimizer policies to filter traffic.
Schedules can be used to specify when policies or virtual circuits takes effect.