HP StorageWorks Enterprise File Services WAN Accelerator 3.0.4 deployment guide (AG421-96001, March 2007)

HP STORAGEWORKS ENTERPRISE FILE SERVICES WAN ACCELERATOR DEPLOYMENT GUIDE 125
13 - TROUBLESHOOTING
D
EPLOYMENT PROBLEMS
Solution: Use
Simplified
Routing
You can also use simplified routing to prevent packet ricochet. To configure simplified
routing, use the CLI command in-path simplified routing or the Management
Console.
For more information about simplified routing and how to configure it, see the HP
StorageWorks Enterprise File Services WAN Accelerator Command-Line Interface
Reference Manual or the HP Enterprise File Services WAN Accelerator Management
Console User Guide.
Problem: Router CPU Spike After WCCP
Configuration
If a router’s central processing unit (CPU) usage spikes after WCCP configuration, it
could be because you are not using a WCCP-compatible Cisco Internetwork Operating
System (IOS) release, or because you need to use inbound redirection.
The following sections describe several possible solutions to router CPU spike after
WCCP configuration:
 “Solution: Check Internetwork Operating System Compatibility” on page 125
 “Solution: Use Inbound Redirection” on page 125
 “Solution: Use Inbound Redirection with Fixed-Target Rules” on page 126
 “Solution: Use Inbound Redirection with Fixed-Target Rules and Redirect List”
on page 126
 “Solution: Use Policy-Based Routing” on page 126
Solution: Check
Internetwork
Operating
System
Compatibility
Because WCCP is not fully integrated in every IOS release and on every platform, you
should first ensure that you are running a WCCP-compatible IOS release. If you have
questions about the WCCP compatibility of your IOS release, contact HP Technical
Support at www.hp.com. If you are certain you are running a WCCP-compatible IOS
release and you experience router CPU spike after WCCP configuration, review the
following sections for possible solutions.
 “Solution: Use Inbound Redirection” on page 125
 “Solution: Use Inbound Redirection with Fixed-Target Rules” on page 126
 “Solution: Use Inbound Redirection with Fixed-Target Rules and Redirect List”
on page 126
 “Solution: Use Policy-Based Routing” on page 126
Solution: Use
Inbound
Redirection
One possible solution to router CPU spike after WCCP configuration is to use inbound
redirection instead of outbound redirection. Inbound redirection ensures that the router
does not waste CPU cycles consulting the routing table before handling the traffic for
WCCP redirection.
For more information on redirection, see Chapter 7, “WCCP Deployments.”