HP StorageWorks Enterprise File Services WAN Accelerator 2.1.7 Deployment Guide (407118 - 003, June 2006)

126 11 - TROUBLESHOOTING DEPLOYMENT PROBLEMS
Fixed target rules directly specify server-side HP EFS WAN Accelerators near the
target server that you want to optimize. You determine which servers you would like
the HP EFS WAN Accelerator to optimize (and, optionally, which ports), and add
fixed-target rules to specify the network of servers, ports, and out-of-path HP EFS
WAN Accelerators to use.
For more details about how to configure inbound redirection and fixed-target rules, see
“Configuring WCCP Using the Management Console” on page 76.
Solution: Use
Inbound
Redirection with
Fixed-Target
Rules and
Redirect List
If the solutions described in the previous sections do not solve router CPU spike after
WCCP is configured, try using inbound redirection with a fixed-target rule and a
redirect list. The redirect list could reduce the load on the router by limiting the amount
of unnecessary traffic that is redirected by the router.
For more information, see “To configure specific traffic redirection on the router” on
page 85.
Solutions: Base
Redirection on
Ports Rather
than ACLs
If the solutions described in the previous sections do not solve router CPU spike after
WCCP configuration, consider basing traffic redirection on specific port numbers
rather than using ACLs.
Solution: Use
Policy-Based
Routing
If the solutions described in the previous sections do not solve router CPU spike after
WCCP configuration, consider using Policy-Based Routing (PBR) instead of WCCP.
For more information on PBR, see Chapter 6, “Policy-Based Routing Deployments.”
Problem: Server Message Block Signed
Sessions
This section provides a brief overview of problems that can occur with Windows
Server Message Block (SMB) signing. For information about SMB signing, the
performance cost associated with it, and solutions to it, see the HP StorageWorks
Enterprise File Services WAN Accelerator Installation and Configuration Guide.
If network connections appear to be optimized but there is no performance difference
between a cold and warm transfer, the problem could be due to SMB-signed sessions.
SMB-signed sessions still support compression and SDR, but render latency
optimization (read-ahead, write-behind, drag and drop of data, and so forth)
unavailable.
Symptoms of SMB signing are:
 Access to some Windows file servers in a WAN is slower than access to other
Windows file servers in the WAN.