Summary
When using an 'inherit' network object and sending traffic to an 'internal' network object, if the 'inherit' object is changed to 'internal' as well, internet pages requested by hosts in the new 'internal' object can time out.Overview
Locations of network objects in the Exinda can be set to one of three choices: external, internal, or inherit. External is meant for all devices that are on the WAN side of the Exinda (ie, internet websites, while Internal is meant for all devices that are on the LAN side of the Exinda. In the case of a DMZ, it can be set to either internal or external, the convention is dependent on the environment and what the administrator has configured.In an Exinda environment where edge cache is enabled, when using an 'inherit' network object and sending traffic to an 'internal' network object, everything behaves as expected. Some administrators might want internal designations on many network objects because of the inherent use of 'ignore internal to internal traffic'. However, if the 'inherit' object is changed to 'internal' as well, internet pages requested by hosts in the new 'internal' object can time out, and an error from squid can be shown on end users' computers.
Cause
The Exinda engineers are currently investigating the cause of this.Workaround
Keep one of the objects as 'inherit'. This will prevent the errors from occurring.Alternatively, edge cache can be stopped on the appliance by going to Configuration > System > Optimization, and turning off the service.