Support Knowledge Center

Release Note

Back to search

ExOS 7.0.0 Release Notes


Article Number: 000001779
Published: August 16, 2016
Announcing ExOS 7.0.0


Notes:
  • All versions in the 6.4.3 line after 6.4.3 Update 7 are not able to update to 7.0.0. A 7.0.1 will be released that will allow upgrades of versions 6.4.3 Update 8 and later. 
  • The supported upgrade path is to upgrade to 6.4.3 or later first. Then to upgrade to 7.0.
  • The upgrade from 6.4.3 may take longer then normal due to the database upgrade that takes place.
  • v7.0 will only accelerate with peers running 6.4.3 and later due to a change to the exinda internal protocol
    • If you are installing v7.0 into an x800 estate, the best approach is to upgrade your core box to 6.4.3 and then install v7 on one or more branch offices.
    • This allows all the existing appliances to accelerate to the core appliance and allows the v7 appliance(s) to accelerate to the core box running 6.4.3
  • Upgrades are only supported from 6.4.3 and later. Upgrades from earlier versions have not been tested.
  • New Exinda VA images are also available for v7.0.0
Platforms:
  • 2061, 4010, 4061, 6060, 6062, 8060, 8062, 10060, 10062, Virtual
Supported upgrade versions:
  • 6.4.3 to 6.4.3 Update 7
  • A change in 6.4.3 Update 8 made the upgrade to 7.0.0 incompatible.6.4.3 Update 8 and later customers will be able to upgrade to 7.0.1, which will be out soon.
  • 6.4.4
Link to download the update:
  • This release is free for people with Premium Maintenance and a paid upgrade for people with Basic Maintenance. 
  • See your Sales Rep or Contact Support for a link. 
  • Image Size: 682,452,737 bytes
  • MD5: c4e6be936206e791a51081e9cfc6acd3


Major Features

Solution Center
The Exinda appliance provides solutions to specific problems that the network manager or application manager has. The solution describes what problem is being solved and how it is solved, often with a short video of how to use it or an image of what the screen or solution will look like.

Solutions in the Solution Center:
  • Application Performance
    • Salesforce.com Performance – Tracks the application performance score, inbound and outbound bandwidth, top users, top hosts for salesforce.com
    • Office 365 Performance - Tracks the application performance score, inbound and outbound bandwidth, top users, top hosts for Office 365.
    • Adobe Creative Cloud Performance - Tracks the application performance score, inbound and outbound bandwidth, top users, top hosts for Adobe Creative Cloud.
    • Application Performance for My App - Tracks the application performance score, inbound and outbound bandwidth, top users, top hosts for any application that the user chooses. They can create multiple application performance solutions by requesting the solution repeatedly with different applications. Custom-defined applications can also be tracked.
    • VoIP Performance – Tracks the users’ experience of VoIP calls by showing the number of good, tolerable, and bad calls as well as showing attributes of the worst calls (such as delay, jitter, loss, MOS, rFactor). Note that the VoIP Performance monitor is a repackaging of the VoIP monitor on previous versions of the Exinda appliance.
  • Network Governance
    • RIAA Notice Prevention – Provides instructions on how to configure the Exinda appliance to combat the unauthorized distribution of copyrighted materials and so prevent the RIAA / MPAA notices.
    • Recreational Traffic - Tracks the amount of network traffic due to different recreational traffic categories. Note that the Recreational Traffic Usage monitor is a repackaging of the Recreational Traffic chart on the dashboard of previous versions of the Exinda appliance.
  • Project Readiness
    • Data Center Continuity – Provides instructions on how to create and apply different appliance configuration sets, so that in an emergency, the users doesn’t have to tweak policies, read help manuals, and try to figure out how they would like to control the network.
  • WAN Planning
    • Bandwidth Usage Summary – Provides instructions on where to find an interface chart that shows inbound and outbound throughput of the appliance.
    • Bandwidth Usage – Top Apps – Provides instructions on where to find bandwidth usage for your top apps as well as how to configure it such that the chart reflects the total throughput through your appliance.


Recommendation Engine
The appliance analyzes the traffic and notices patterns or situations that Exinda would recommend a course of action, such as:
  • If an application enters the daily top 10 applications and has not been in the top 10 in the previous week, Exinda would recommend to either control or protect the application, depending on whether it is a business critical application.
  • If traffic is not caught by your configured circuits and virtual circuits, Exinda would recommend to investigate by looking at Virtual Circuits monitor or Real Time monitor, then redefine your virtual circuits to capture all of the circuit data.

The recommendation engine proactively finds issues in the network and helps to tune the network to improve the network’s performance and the network users’ performance.


Time Series for applications & virtual circuits
The following data types are represented as time series charts. They also report the entire data through the appliance – not just the top.
  • Subnets
  • Virtual Circuits
  • Applications
  • Applications for a subnet
  • Applications for a virtual circuit

The time series representation allows users to see traffic patterns, such as when these traffic types are spiking. The completeness of the data allows users to see the entire data for these data types – not just the top values for these charts.



Updated Layer 7 Signatures
  • New Applications:
    • Tumblr
    • Xing
    • Google Play Music
    • Vimeo
    • iTunes Radio
    • Sina Weibo
    • Forfone
    • LiverJasmin
    • jingdong (jd.com)
    • last.fm
    • IMS
    • TN3270
    • SCTP
    • OSPF
    • IPIP
    • OFFSystem
    • Windows Azure
    • Ubuntu One
    • Dailymotion
    • Deezer
    • Grooveshark
    • CNTV
    • SinaTV
    • Zynga
    • Crime City
    • Modern War
  •   New protocols:
    • Diameter
    • MQTT
    • Hike Messenger
    • OS Updates with Subtype 'iOS', 'Android', 'Windows Mobile'
    • DiDi 
  • Improved Signatures
    • Ultrasurf
    • BitTorrent
    • GooberFixed
    • HTTP application Google Talk
    • HTTP
    • Spotify
    • YouTube
    • Amazon Shop/Cloud
    • Viber


Bug fixes and minor improvements:
  • [B-03606] Added a warning message that clearing the monitoring records may take several minutes.
  • [B-03687] Added a pop-up warning when changing the time. When changing the time, the UI needs to be restated and this can take up to 75 seconds on a 2061. 
  • [B-03665] The Subnet report in the new UI now shows data that is collected on the WAN side of the appliance. This is consistent with the Applications and Virtual Circuit graphs. It is inconsistent with the PIE chart UI that collects it on the LAN side
  • [B-02783] The bridge alert now contains more useful information to help explain what might be causing the alert. The message now includes:
Description: Bridge may be connected incorrectly. More 'internal' IPs have been detected on the WAN-side of the bridge than on the LAN-side. This can occur if the WAN and LAN connections reversed, where the WAN port connects to your LAN and your LAN port connects to your WAN. Or this can occur if you have external network objects defined as internal or vice versa. Note: The bridge direction check is only enabled for a limited time after boot. If you are sure that the WAN and LAN connections are correct you can ignore this alert.
  • [D-02453] Fixed an issue with the Virtual Circuit scheduled report. When the Y-axis was scaled as a percentage of the virtual circuit rather than absolute bandwidth, there were circumstances when the graph was scaled incorrectly. 
  • [B-03588] addressed an issue with the NIC driver for lower end hardware that caused the following log message: kernel: [16409.705443] e1000e 0000:05:00.0: eth4: Detected Hardware Unit Hang
  • [D-02492] In some situations when using VRRP with an acceleration cluster deployment and having tcp acceleration dual bridge bypass enabled, the appliance may crash. This defect has been addressed and this deployment with these options no longer crash the appliance.
  • [D-02001] When the system is configured to have more than a few thousand policies, the WUI becomes slow and unresponsive. 
  • [D-01654] When using a very large number of policies, the appliance will occasionally be seen to use a high amount of CPU when a change to the policy is made. Under extreme circumstances the appliance WUI may appear to lock up.
  • [D-02311] After upgrading to 6.4.3 existing scheduled reports from 6.4.2 and earlier no longer run on their schedule. This has been fixed and all scheduled reports run as per their configured schedule. This includes reports created in 6.4.2 and earlier as well as reports created in 6.4.3

Known Issues:
  • [D-02595] A regression has been introduced in 6.4.3 that causes the VoIP scores to be incorrect. VoIP scoring is now showing very high loss on the inbound side of the traffic which results in the loss measure being very high (30-50%) and the rFactor score to be inaccurate. This will be addressed in an upcoming release.
  • [D-03060] Google has started to deliver YouTube over https. This hides the URL from the Exinda appliance. As a result the stream is being classified as google encrypted traffic. 
  • [D-02222] Anonymous Proxy: If the url listed on the Objects -> Applications -> Anonymous Proxy tab is http://www.exinda.com/ap/apdata.tar.gz, then the Anonymous proxy feature will not work. The correct URL is http://updates.exinda.com/aplist/alist.gz. If your Exinda appliance has the wrong URL set, you can issue the following CLI command to set it to the correct URL: anonymous-proxy url http://updates.exinda.com/aplist/alist.gz
  • [D-02199] When an acceleration HA cluster is configured and the traffic being accelerated is located on a VLAN and has a VLAN tag, the traffic will not flow through the HA cluster properly. This issue is currently being investigated and a fix is expected soon.
  • [D-01777] snmp: after a period of repeatedly querying the following sensors, the WUI will appear to be locked up and various processes within the appliance will crash. This will eventually repair itself. system health/cpu alarm, system health/disk alarm, system health/ram alarm, system health/nic alarm. The work around is to not query these SNMP values.
  • [D-01921] Under some circumstances Microsoft Lync traffic will be classified as MSN traffic.