HP StorageWorks EFS WAN Accelerator 3.0.12 release notes (AG421-96009, April 2009)

pass-through traffic separately or aggregated, and top-talker and listener tallies from a Netflow v5
compatible collector.
New reporting and statistics
RiOS v3.0 provides dramatic improvements in the area of visibility and reporting for device and
global monitoring. Key improvements include:
Port and application auto-discovery—All TCP traffic flowing through an HP EFS WAN Accelerator
is inspected, and detected ports are automatically added to the management system reporting
facility. Each port is labeled with the name of common applications associated with the ports.
Pass-through traffic statistics—Port and application byte count statistics are provided for all TCP
traffic that is passed through the HP EFS WAN Accelerator unoptimized. You can view how much
and what type of traffic is optimized versus unoptimized traffic through the HP EFS WAN Acceler-
ator.
Performance statistics by QoS class—The QoS feature in RiOS v3.0 delivers the ability to view
performance reports by traffic class. Class traffic reporting, including bytes and packets sent versus
bytes and packets dropped, enables you to view how QoS shapes the traffic to enforce configured
policies.
Increase in connection limit
The connection limit has been increased for the following models when running on 3.0 code: HP
ProLiant DL380-3010 (2400 to 3000) and DL380-5010 (4500 to 5000).
HS-TCP
HS-TCP no longer requires a license.
Limitations
General limitations
Samba SMB client on Linux with either a Windows or Samba server gains only bandwidth optim-
ization, not latency optimization.
An SMB mount from Linux to any CIFS server is not significantly accelerated. (It performs Scalable
Data Referencing but does not perform Transaction Prediction.)
CIFS performance degradation occurs with multiple sets (pairs) of in-path HP EFS WAN Acceler-
ators (Bug #3746).
For example:
client->DL320-2010->WAN->DL320-2010->DL320-1010->DL320-2010->server
This problem is dependent on this configuration. Contact HP Technical Support for further inform-
ation at http://www.hp.com.
QoS enforcement is only available when deployed in a physical in-path deployment.
PFS limitations
For version 2.0, before you upgrade to version 2.1 or later, you must turn off the PFS auto-launch
feature and save your changes to memory. You can turn off the PFS auto-launch feature and save
your changes in the Management Console or the command-line interface (CLI).
6