ExOS 6.3.10 Release Notes

Description

• After installing ExOS 6.3, it is not possible to roll back to any ExOS version prior to ExOS 6.0.2. It is strongly recommended to have ExOS 6.0.2 (or newer) installed on your system prior to upgrading to ExOS 6.3 .
• When rebooting into ExOS 6.3 following the installation, it is strongly recommended to use the "Slow Reboot" mode.

• A database upgrade is performed and monitoring reports may be unavailable for up to 10 minutes.
• When upgrading to ExOS 6.3 from ExOS 5.5 or earlier:
  • WAN Memory persistence will be lost due to changes in the underlying storage architecture.
  • ARM objects are automatically upgraded to APS objects, however, all historical ARM data is lost. If you would like to keep records of your historical ARM data then it is recommended to generate PDF reports with this data prior to upgrading.
  • Virtual Machine disk images will be lost due to changes in the underlying storage architecture. This only affects customers running virtual machines on the Exinda appliance such as Replify Software Client or Windows Server. Please contact Exinda TAC for a manual workaround.

• This upgrade is not supported. Please upgrade to ExOS 5.4 or newer first.
• Network Management Systems that use the Exinda SNMP MIB will need to be updated to use the new Exinda SNMP MIB after upgrading to ExOS 6.3.
• After upgrading, refresh the Web UI browser window using Ctrl+F5 as CSS (style-sheets) and JavaScript functions have changed.

• On V5 or V6 systems with valid Software Subscription (SS), Hardware Maintenance (HM) or Premium Support (PS), navigate to System | Maintenance | Firmware Update and use one of the following URLs:

http://updates.exinda.com/exos/exinda-v6.3.10.2128.x86_64.img

http://updates.exinda.com/exos/exinda-v6.3.10.2128.i386.img

http://updates.exinda.com/exos/virtual/vmware/v6.3.0.1662/Exinda.ovf
Image Size: 10,752 bytes (10 kB)
http://updates.exinda.com/exos/virtual/vmware/v6.3.0.1662/Exinda-disk1.vmdk (optional, for offline deployments)

http://updates.exinda.com/exos/virtual/xenserver/v6.3.0.1662/Exinda.zip
Image size: 624,108,947 bytes (595 MB)

• The 32 bit VM needs at least 1G RAM
• The 64 bit VM needs at least 2G RAM
• You need at least a 50G HDD image
• You should use ÒvirtioÓ drivers for the NICs and HDD where possible
• You need at least 2x NIC ports (these will become the MGMT and AUX ports)
• Any more NICs need to be added in pairs (as LAN and WAN port bridges)
• This ISO should detect itÕs running under kvm and self-install
• Once installed, the host id will need to be added to the ldb in order to get a license

Ability to accelerate Microsoft SMB2 traffic.

Ability to store complete files in cache.

Ability to pre-populate the SMB object cache and/or WAN memory cache by downloading files via CIFS or HTTP on demand or at a scheduled time interval.

Demonstrate the amount of time acceleration of application traffic saved.

Display the percentage of time applications or application groups fall within a configurable utilization level.

Ability to limit the number of TCP/UDP connections passing through a virtual circuit, with admission control.

Detection and alerting when network traffic is being routed asymmetrically.

Ability to match on Layer 7 sub-type attributes:

• Application (dropbox, facebook, gmail, googledocs, gotomeeting, gottomypc, icloud, imessage, itunes, myspace, twitter, ubuntuone, yuilop)
• Bittorrent (plain, encrypted)
• eDonkey (plain, encrypted)
• SIP (unknown, msn, yahoo, vonage, oscar, gadu-gadu, oscar-video, yahoo-video, ichat-facetime, magicjack, audio, video)
• MSN (unknown, voice, file-transfer, video)
• Yahoo (unknown, voice, file-transfer, video, webchat)
• OSCAR (unknown, file-transfer, picture-transfer, voice, video)
• IRC (unknown, file-transfer)
• GaduGadu (server, file-transfer, voice, video)
• GTP (control, user-data)
• DirectConnect (hub, peer, adc-peer)
• Paltalk (server, file-transfer, voice)
• Skype (unknown, voice, out, video)
• Jabber (unknown, voice, file-transfer, video)
• QQ (unknown, voice, file-transfer, video)
• Meboo (unknown, audio, video)
• Orb (unknown, server, client, client-rtsp, client-rdt, client-wmv, client-wma, client-flash, client-flv, client-3gp, client-upload-download, client-rtp)
• MGCP (control, rtp)
• IPSEC (data, control)
• GoogleTalk (unknown, voice, file-transfer, video)
• Fring (unknown, voice)
• VeohTV (generic, flash)
• Viber (unknown, audio, im)
• MyPeople (unknown, audio)
• BlackBerry (unknown, encrypted, email, messenger)

• AdobeConnect (Thin Client)
• ComodoUnite (VPN)
• eBuddy (Instant Messaging)
• Facetime (Voice)
• FiCall (Unified Communications)
• Goober (Unified Communications)
• GoToMyPc (Thin Client)
• IMO (Instant Messaging)
• JAP (Recreational)
• Label Distribution Protocol
• Mojo (Recreational)
• mypeople
• Skype Voice (Voice)
• Skype Video (Voice)
• SSTP (VPN)
• WebSocket (Web)
• Wuala

• aimini
• AppleJuice
• Battlefield
• BitTorrent
• DirectConnect
• Edonkey
• IPSEC
• IRC
• NetBIOS
• ooVoo
• OpenVPN
• Oscar
• PalTalk
• QQ
• QQLive
• RTCP
• RTSP
• Skype
• SOPCAST
• TeamViewer
• Usenet
• Viber
• Webthunder
• WindowsMedia
• Yahoo
• YourFreedom
• ZATTOO

Support an 'advanced' subtype match for HTTP and SSL to allow matching on multiple combinations of the other subtypes.

Allows the redistribution of disk resources between services.

Restrict access to management services (telnet, ssh, http, https and snmp) to a specific set of IP addresses.

Allow the creation of support cases and the transmission of diagnostics information directly from the appliance.

The monitoring database summary data has been extended in this release to contain all the data from the detailed records. This enables full drill-down even when detailed records are disabled. (Via the 'Setup -> Monitoring -> Detailed Records' option.)

The detailed records are only required to allow earlier firmware versions to be display correct data and for some historical data.

New appliances will have detailed records disabled by default as they are no longer required.