Tips for deploying WAN Optimization using ProxySGs

Article Id:167014

Status:Published

Updated On:13-05-2017 10:09

Legacy Id:TECH242800

Products:

ProxySG Software - SGOS

Issue/Introduction:

Here are some tips for a WAN optimization deployment.

ALWAYS start with freshly reinitialized boxes. Issue restore-defaults factory-defaults when console connected. Keep in mind this will remove the license key from the box, so have a copy of it with you.

If traffic is passing over a VPN link, you’ll need to set the MTU to prevent fragmentation. Use “ping –f –l 1500 10.x.x.x” from a client PC and decrement the 1500 down from there until the pings make it through.

Always hard code interfaces. If there is a speed issue, 80% of the time it’s an autosensing issue for speed/duplex.

If you’re unsure if an interface is defined as LAN or WAN (older boxes aren’t always marked), keep in mind that the LAN side ends in a 1, which looks like an “L.”

In data centers, always set the byte cache to 80%. (The default is 50%.) This gives more room to the byte cache since users are rarely pulling CIFS files from the edge sites.

If an SG 210 or a 510 has been running for a while and you see low utilization on the processor, it is usually safe to enable Adaptive Compression. The switch is found under Configuration > ADN > Byte-Caching.

Under Configuration > Proxy Settings > CIFS Proxy, uncheck Remote Storage Optimization and check Suppress Folder Customization. You may also want to set the Directory Cache Time to 30 seconds from the default 1 minute.

In Configuration > Proxy Settings > HTTP Proxy > Acceleration Profile, check the box for Never Serve After Expiration. It fixes stale cache issues with many popular sites like woot.com, weather.com, and finance.yahoo.com. In the same section, click the Bandwidth Gain Mode checkbox (NOT the button) for improved savings.

Uncheck the Include Bypassed bytes switch in the Traffic Mix report. The bandwidth savings calculations take bypassed bytes into account with the box checked.

In the CLI, enable tcp-ip -> bypass-keep-alive. This prevents the ProxySG from breaking long-lived SAP and Oracle connections. Other applications are also positively affected by this setting.