HP StorageWorks Enterprise File Services WAN Accelerator 3.0.4 release notes (AG421-96006, March 2007)

6
Limitations
General limitations
• Samba SMB client on Linux with either a Windows or Samba server gains only bandwidth
optimization, 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 Accelerators
(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 information 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 before upgrading to version 2.1 or later. You can turn off the PFS
auto-launch feature and save your changes in the Management Console or the command-line interface
(CLI).
Using the Management Console:
1. Go to the Setup: Start/Stop Services page and select Manual from the PFS drop-down list.
2. Save your configuration changes to memory in the Configuration Manager page.
Using the CLI:
1. Connect to the CLI. For detailed information, see the HP StorageWorks Enterprise File Services WAN
Accelerator Command-Line Interface reference manual.
2. At the system prompt, enter the following set of commands:
SH > enable
SH # configure terminal
SH (config) # no pfs auto-launch enable
SH (config) # write memory
You cannot change from one configuration to another in PFS deployments. The HP EFS WAN Accelerator
Management Console has been built around the Cisco CLI management model, which has the following
major characteristic features:
• Any configuration change is applied to the system immediately but not saved permanently without the
system administrator committing the configuration changes. This means after making the configuration
changes, if the system is rebooted (or the Management Console is restarted), the system comes up with
the last saved configuration.
• The system administrator can maintain different configurations under different names and can switch to
any saved configuration at any time and continue without disruptions (of course, assuming that the
saved configuration was valid and is still valid).
The above functionality works very well for network devices such as the HP EFS WAN Accelerators.
However, with the addition of PFS features, there are the following implications:
• Any configuration change such as add or delete of a share, if not saved automatically, causes the
system to start with the impaired functionality and causes service disruption.
• There is no concept of switching configurations with PFS. If a saved configuration "save1" has system
part of domain "save1.dom" and has shares a, b, and c, and current configurations have system part
of "curr.dom" and have share x, y, and z, then switching to the "save1" configuration does not work
because the domain information which makes the system part of domain "save1.dom" has been
overwritten. Hence, switching configurations makes the PFS configuration information invalid.