Overview

Users have configured all settings for accelerating traffic.

TCP Acceleration:

• Community is online. Both Exindas can see each other in the community.
• Wan Memory peers are online.
• The management interface of each Exinda can ping the other one.
• Acceleration is enabled in the policy in the outbound direction.

Caching:

• Edge-cache is enabled in the policy in the outbound direction.
• All edge-cache proxy-peers are added to the config (under System- optimization- edge-cache).

Still, acceleration is not initiating - no yellow striping (TCP acceleration) or blue striping (edge-cache).

Information

1. It is a possibility that the cables on the Exinda are swapped:

   • Users should make sure that the LAN (internal) side connects to the LAN port on the Exinda and WAN (external) side connects to the WAN side of the Exinda.

   • If cables are not connected properly, the acceleration will not take place.

2. For TCP acceleration - the firewall or router or any intermediate device might be stripping off options from the packets:

   • Investigate the intermediate devices to see if any TCP options (30,230) are being stripped off.

   • Exinda applies these options to the packets to mark them for acceleration.

3. Maybe traffic is not being routed properly between the Exindas'. One Exinda sees the traffic, the other doesn't.

4. This behavior can also happen if one of the peers was replaced (new device) or re-imaged. Then the new peer will have no data stored in the WAN memory partition on the disk and would cause this issue.

   The rule of thumb is when any device is replaced or re-imaged the WAN memory needs to be cleared on the peers of the replaced device with whom the replaced device does acceleration.

   Refer to kb article: How to clear Wan Memory Persistent Cache.