Troubleshoot issues with TCP acceleration

If you are experiencing issues with acceleration, the following are possible troubleshooting options to consider:

• Ensure that the traffic is processed by the expected policy.

  Go to the Real Time Conversations monitor and check the Show Policies option, which groups the traffic by the virtual circuit and policy. Look for the desired traffic in the expected policy. If the traffic is being accelerated by TCP, the background colour will be yellow.

• If you have a mix of 7.4, 7.0, 6.4.3, and pre-6.4.3 appliances, perhaps the Acceleration TCP Option Mode is not set correctly. Exinda had used option 30 to indicate acceleration but needed to change this when option 30 was assigned to indicate multi-path TCP. A number of choices were added to ensure compatibility with earlier appliances. Ensure that you believe your choice is correct for your situation or choose another selection.
• If you have the Multi-Path TCP Acceleration Bypass setting enabled and and Acceleration TCP Option Mode is set to liberally use option 30, then when option 30 is encountered it will be interpreted as being multi-path TCP rather than Exinda acceleration and thus will not be accelerated. Ensure these settings are set correctly.
• If you have a backhaul scenario and you have not enabled the Dual Bridge Bypass setting, then acceleration will not work properly when the SYN from the client is not processed on the same bridge as the SYN/ACK from the server.

You can also attempt to diagnose the issue by viewing the system log or the system diagnostics information.

• The system diagnostics for acceleration can be filtered for SMB acceleration, WAN memory, or TCP acceleration. See Acceleration Diagnostics.
• The system log file can be filtered for SMB acceleration (smbad), WAN memory (wmd), TCP acceleration (tcpad), or community (communityd). See View System Log Files.