Firmware Name: ExOS 6.1.11.1810

Release Date: January 31, 2012
Platforms: 1060, 2000, 2060, 2061, 4000, 4060, 4061, 5000, 6000, 6010, 6060, 7000, 8060, 10060
Required Versions: 5.3, 5.4, 5.5, 6.0 or 6.1

WARNINGS:

1. After installing ExOS 6.1, it is not possible to roll back to any ExOS version apart from ExOS 6.0.2. It is strongly recommended to have ExOS 6.0.2 installed on your system prior to upgrading to ExOS 6.1. (6.0.2 release notes are located HERE).
2. When rebooting into ExOS 6.1 following the installation, it is stronly recommended to use the "Slow Reboot" mode.
   
3. After upgrading to ExOS 6.1, a database upgrade is performed and monitoring reports may be unavailable for up to 10 minutes.
   
4. When upgrading to ExOS 6.1 from ExOS 5.x, WAN Memory persistence will be lost due to changes in the underlying storage architecture.
5. When upgrading to ExOS 6.1 from ExOS 5.x, 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.
   
6. When upgrading to ExOS 6.1 from ExOS 5.x, 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.
7. 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.1.
8. After upgrading, refresh the Web UI browser window using Ctrl+F5 as CSS (style-sheets) and JavaScript functions have changed.
9. If you are upgrading to ExOS 6.1 from ExOS 5.3 or earlier, Application Acceleration is not compatible with other appliances running ExOS 5.3 and earlier.
10. If you are upgrading to ExOS 6.1 from ExOS 5.3 or earlier, the port used for Mirror/SPAN Port Mode has changed. Instead of using a WAN port for Mirror Mode, any port can now be used. Any appliances deployed using Mirror Mode will need to be checked for correct operation after upgrading.

Upgrading from V5 or V6 (appliances already on V5 or V6):

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:

The image can also be downloaded to your desktop and uploaded to the appliance. Downloading and installation may take some time. Ensure that the partition other than your currently booted partition displays the latest ExOS version: "exinda-6.1.11.1810 (i386) 2013/01/24" or "exinda-6.1.11.1810 (x86_64) 2013/01/24".

You must reboot the appliance for the image to install. Once the system reboots ensure that the status bar displays the correct ExOS version (6.1.11.1810). If the old ExOS version is displayed it indicates a problem with either the installation of the new version (system will automatically fall back to existing version) or that the new version was not set to "to boot next" prior to rebooting.

Exinda AD Windows Client:

Customers using the Exinda AD client are advised to upgrade to the latest version of the client, 1.0.10, however, version 1.0.6, 1.0.7 and 1.0.9 are still fully compatible with ExOS 6.1.

New Features / Improvements:

• Edge Cache
  Exinda Edge Cache is a single sided transparent web cache. It caches static web content such as HTML, GIF, JPEG, ZIP, RAR, ISO, etc. It can also cache content that utilizes dynamic URLs such as YouTube, Google Video, Vimeo, etc.

• Full IPv6 Support for x700
  Exinda now supports IPv6. This includes setting up the Exinda with an IPv6 address, netmask and gateway. The visibility and reporting sections of Exinda (including Real-Time) can display and report on IPv6 addresses. IPv6 addresses can also be used in the Optimizer Policies for QoS and bandwidth control.

• Performance Enhancements for Exinda Acceleration
  Exinda's UPM core acceleration engine is now fully multi-threaded. Multi-threading takes advantage of multi-core CPUs to enhance the performance of the software. Exinda's Layer 7 Acceleration Modules (CIFS and SSL) are also now multi-threaded. Multi-threading the software components allows Exinda to scale to more connections and more throughput on multi-core or multi-CPU appliances.

• WCCPv2 Support for Out-of-Path Deployment Options
  Exinda now supports out of path deployment by utilizing the Web Cache Communication Protocol (WCCPv2).

• New Application Definitions:
  • ANts P2P (P2P)
  • BOLT (Web)
    
  • IM+ (Instant Messaging)
  • iPlayer (Streaming)
  • JBK3000 (Middleware)
  • OperaMini (Web)
    
  • PCoIP (Thin Client)
  • Scydo (VoIP)
  • Spotify (Streaming)
  • Tango (VoIP)
  • Teredo (VPN)
  • UltraSurf (Anonymous Proxy)
  • Viber (VoIP)
  • WhatsApp ( Instant Messaging )

• Improved/Updated Application Definitions:
  • AIM
  • Aimini
  • Armagetron
  • Battlefield
  • Bittorrent
  • Blackberry
  • Club Penguin
  • Dofus
  • eDonkey
  • Fiesta
  • Flash
  • Florensia
  • Fring
  • FTP
  • Funshion
  • Gamekit
  • Gnutella
  • gTalk
  • H323
  • Hamachi
  • HTTP
  • Icecast
  • IMAP
  • iMesh
  • Jabber
  • Maplestory
  • Meebo
  • MSN
  • Netbios
  • Nimbuzz
  • Octoshape
  • OpenVPN
  • Oscar
  • PalTalk
  • POP
  • PPlive
  • PS3
  • QQ
  • Quake
  • RADIUS
  • RTCP
  • RTP
  • SecondLife
  • Shoutcast
  • SIP
  • Skype
  • SopCast
  • SSL
  • STUN
  • syslog
  • Teamspeak
  • TeamViewer
  • TOR
  • UUSee
  • VeohTV
  • VPN-X
  • Winny
  • World of Warcraft
  • Yahoo
  • YourFreedom
  • Zattoo

• Other features:

1. Network Summary Reports include an "Other" series (10+N)
2. Enhanced Service Level Monitoring and Alerting
3. Custom Disk Partition/Resizing
4. Control IPMI through Web UI
5. Web-based access to CLI over HTTP(S)

Fixed in 6.1.6 (since 6.1.5):

[APP-7097, APP-7286] monitoring: openvpn (including hotspotshield) incorrectly detected after switching ports when attempting to discard
[APP-7335] acceleration ssl: Reduce memory usage by eliminating memory fragmentation
[APP-7335] acceleration ssl: Pass through SSL shutdown messages
[APP-7335] acceleration ssl: Don't require data before starting SSL negotiation
[APP-7306] wui: Add reload button on firmware upgrade page
[APP-7306] wui: Add notice  that firmware upgrade page may need to be manually refreshed
[APP-7301] wui: Don't ignore 0's in non-flash/pdf reports when data is present at start and end of period.

Fixed in 6.1.5 (since 6.1.4):

APP-7167: web ui: Optimization graphs showing all VCs instead of just the selected VCs
APP-7107: monitoring: Can use 100% CPU in some cases when using edge-cache or acceleration
APP-7154: edge cache: Vimeo and DailyMotion videos are not cached
APP-7118: edge cache: Some youtube videos fail to display
APP-7172: system: Forced speed and duplex configuration does not always take effect
APP-7163: system: Old auto-support emails that were saved due to no SMTP server configuration were not being deleted
APP-6859: system: Allow LACP/802.3ad to be bridged

Fixed in 6.1.4 (since 6.1.3):

APP-6486: system: Unexpected system restart when using the dcerpc ASAM feature.
APP-6914: optimizer: Improve bandwidth fair sharing when there are large numbers of connections.
APP-6925: system: Upgrade to latest Intel NIC drivers.
APP-6945: edge cache: Some Netflix videos fail to load from Apple devices.
APP-6946: edge cache: Some YouTube videos fail to load and play correctly.
APP-6958: acceleration: Thread allocation problem for acceleration processes on the 10060 appliance.
APP-6959: ssl acceleration: Upload of large files using SharePoint fails.
APP-6973: system: Deleted Applications show up under the Applications drop-down when configuring Application Groups.
APP-6992: monitoring: The collectord process would sometimes terminate and restart when receiving oversized packets.
APP-6996: system: 'set_app' errors observed in the system log when an AD-based network object is used in a custom application.
APP-7004: system: NIC alerts are now triggered based on a percentage of errors during the last 5 minutes.
APP-7040: system: 'anna bypass i80!' messages observed in the system log when using newer fibre NICs.
APP-7050: edge cache: Cannot add a URL in the Never Cache list.
APP-7064: edge cache: Fix potential memory leak.

Fixed in 6.1.3 (since 6.1.2):

APP-6000: monitoring: The collectord process would sometimes terminate and restart when receiving oversized packets.
APP-6587: monitoring: GRE/PPTP traffic doesn't appear in the Realtime Monitoring Report when "Show Policies" is enabled.
APP-6646, APP-6719: system: Improve the fail-over and fall-back times of Link State Mirroring and make them user configurable.
APP-6674: edge-cache: The swap.state file grows too large in some environments.
APP-6685: system: ARP responding on the wrong interface in some environments.
APP-6686: system: Unexpected system restart when all subnets within a Network Object are deleted and a diagnostics file is generated.
APP-6700: edge-cache: Add support for CARP as a peer routing protocol and allow the user to specify an administrator email address to display on error pages.
APP-6710: system: Improve interoperability with Link State Mirroring in EtherChannel deployments.
APP-6739: system: Always skip forwarding delay when not using STP on the bridge.
APP-6764: system: Minor memory leak when pasting static user and group configuration.
APP-6770: monitoring: Netflix classification only works with specific Application Object ordering.
APP-6799: monitoring: Improved UltraSurf detection, eDonkey detection and RCTP detection (for Micrsoft OCS).

Fixed in 6.1.2 (since 6.1.1):

APP-6232: system: Appliance can sometimes restart during boot-up when loading the bypass driver.
APP-6308: ipv6: Overlapping Network Objects and Network Objects in Applications do not classify traffic correctly.
APP-6398: web ui: Google Chrome detected as Netscape on the Web UI login page.
APP-6399: adaptive response: Rule triggers incorrectly if the quota is set to more than 4GB.
APP-6415: ad: System can use 100% CPU with multiple domain controllers. This also requires and upgrade of the AD Client.
APP-6417: ssl acceleration: SSL acceleration process can sometimes restart under heavy load.
APP-6427: ssl acceleration: SSL accelerating sometimes permitted even with an invalid certificate.
APP-6431: system: Unable to add a Primary DNS server in some situations.
APP-6455: acceleration: Inconsistent throughput observed when accelerating VLAN tagged traffic over high-latency links.
APP-6470: system: VLAN tags not seen by Optimizer Policies when using 10G cards.
APP-6485: monitoring: L7 signature updates for Gnutella, Bittorrent, eDonkey, UltraSurf, QQ, skype, Ares, PPLive and WinMX.
APP-6503: system: Add support for network expansion cards in the EOL 6000 platform.
APP-6504: system: When a product becomes unlicensed, change the maximum supported connections to the maximum supported for that platform.
APP-6516: edge cache: Log file can grow too large, causing the logging partition to fill up.
APP-6531: wan memory: Rare WAN Memory process restart when connections are reset.
APP-6549: web ui: TOS/DSCP field in Optimizer Policies gets reset to ALL.
APP-6555: monitoring: Network Summary tables not always correctly summarized.
APP-6574: system: Add additional memory and networking items to the sysdump.
APP-6610: system: Add Link-state Mirroring (LSM) support for existing 10G fibre cards.

Fixed in 6.1.1 (since 6.1.0):

APP-6048: System: Resolved some intermittent upgrade issues from 5.x->6.1 and 6.0->6.1.
APP-6091: System: Added support for the EX-PE210G2BPi9 10G fibre card family.
APP-6094: System: Added support for link-state mirroring using the new EX-PE210G2BPi9 10G fibre card family.
APP-6098: Monitoring: Upgrading to 6.1 from anything prior to 6.0 results in the monitoring database not updating correctly.
APP-6142: Edge Cache: YouTube user account freshness issues with Edge Cache enabled.
APP-6144: Documentation: Help screen says "Page not Found" when accessing help from the "Add new APM Object" screen.
APP-6149: Optimizer: Optimizer validation fails when using uni-directional VC's with guaranteed bandwidths.
APP-6169: System: Occasional unexpected restarts seen on appliances when parsing some RPC-based traffic flows (e.g. MAPI).
APP-6172: System: Problem with text-based system configuration after editing default Applications.
APP-6188: Optimizer: Optimizer fails to start on boot-up if an AD-based Network Object is used in a VC or Policy.
APP-6206: Edge Cache: Process occasionally restarts and generates a system alert.
APP-6217: Monitoring: Occasional collectord restart when processing RTP packets.
APP-6225: Monitoring: Improved the granularity of the Optimizer Prioritization report.
APP-6226: System: APM/APS names with spaces are not correctly encapsulated in quotes in the text-based system configuration.
APP-6233: Acceleration: Some accelerated connections remained open after the connection has terminated.
APP-6234: Documentation: Updated out-of-date WAN Memory screenshot.
APP-6244: Alerting: APS alert emails show threshold values greater than 10.
APP-6250: Monitoring: Drill-down for Internal/External Hosts doesn't work correctly for TCP Efficiency and Health reports.
APP-6259: System: Bypass all bridges by default when corrupted configuration is detected.
APP-6262: Edge Cache: Incorrectly reporting WAN-side data greater than LAN-side data.
APP-6264: Monitoring: Groupwise traffic sometimes detected as Ultrasurf.
APP-6268: Documentation: Updated the help for the APS Objects section.
APP-6283: System: Changed the journaling mode for the /config partition to prevent corrupt configuration files in the event of power loss. 
APP-6297: System: Error message displayed when importing some APS Object text-based configuration.
APP-6314: System: The "add" process takes too long to stop on shutdown, sometimes causing system alerts to be generated.
APP-6343: Edge Cache: Process can sometimes restart and generate a system alert after an upgrade is performed.
APP-6350: Acceleration: Changing the appliance IP address is not completely detected and honoured by WAN Memory.
APP-6368: Acceleration: Changing the TCP Acceleration window scaling factor doesn't always take effect.

Fixed in 6.1.0 (since 6.0.0):

Known Issues:

APP-668: cli: command completion does not work for names with multiple words (that contain a space). E.g. show policy my policy.
APP-1999: optimizer: Cannot add a VC in a circuit if another VC exists with the same name in another circuit.
APP-3013: acceleration: In some environments, files saved in compatibility mode using Office 2007 might not be CIFS accelerated.
APP-3275: monitoring: Graphs/tables show data for "last 60 minutes" show "this hour" in the drill-down reports.
APP-3410: system: May display Unsaved Changes after Factory Default or Firmware Upgrade.
APP-3540: ui: Logs an error when viewing logs that contain null characters.

Upgrading from 4.91:

Upgrading from 4.91 involves installing 5.03 first. Please follow the instructions here (http://support.exinda.com/topic/firmware-version-5-03-release-notes-491-upgradeto5036379) prior to installing this release.