This article addresses the issue where Edge Cache or Acceleration do not work when internal subnets are on the WAN side of the device.
There are two typical scenarios for this issue:
- A mistake in cabling the Exinda, where the LAN ends up pointing to the Internet while the WAN is pointing to an internal network.
- Backhauled networks where remote sites have to connect to headquarters and the WAN side of the Exinda is facing the Internet instead of the intranet, e.g., Multiprotocol Label Switching (MPLS) WAN.
Licenses for Edge Cache and Acceleration features.
The Edge Cache or Acceleration settings are not enabled on the outbound traffic as it leaves the internal network through the WAN interface of Exinda, so when the LAN is facing the external networks, these settings are not applied.
- Make sure that the Acceleration Policies on Virtual Circuits are set to either outbound or both directions.
- Make sure the Exinda is cabled in such a way that the LAN is connected to the internal subnet and the WAN is connected to the external subnet.