18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 9: Configuring Proxies<br />

Proxy basics<br />

246<br />

When to disable the Fast Path Sessions option<br />

In most cases, the Fast Path Sessions option enhances system performance,<br />

and in many <strong>of</strong> these cases the improvement is significant. However, there are<br />

some cases where the Fast Path Sessions option may negatively affect<br />

performance. Large data transfers on heavily loaded systems, primarily FTP or<br />

HTTP traffic, can overload a system. The <strong>Sidewinder</strong> <strong>G2</strong> will also “throttle”<br />

these connections under very heavy load conditions to prevent them from<br />

taking over the system.<br />

Proxy session limits<br />

There is an upper limit to the number <strong>of</strong> simultaneous sessions for certain<br />

proxy configurations. Table 21 provides a summary <strong>of</strong> hard limits based on perprocess<br />

resource limits.<br />

Table 21: Proxy session limits (hard limits)<br />

Proxy Session Limits<br />

FTP 4000 sessions<br />

t120 1000 sessions<br />

all other TCP 8000 sessions a<br />

UDP The number <strong>of</strong> ports plus two times the number <strong>of</strong> sessions<br />

must not exceed 16,000. (The maximum number <strong>of</strong> enabled<br />

ports for all services on all burbs must not exceed 8000.)<br />

a. A maximum <strong>of</strong> 16 Telnet sessions are allowed in the “enter destination” or<br />

“authentication” stage.<br />

Tip: Session limits for each proxy can be lowered from the hard limits by editing<br />

the simultaneous_sessions entry in the configuration file (*.conf) for each proxy.<br />

Configuring multiple instances <strong>of</strong> certain proxies<br />

Certain proxies (HTTP, HTTPS, generic TCP, and SQL) can be configured to<br />

enable multiple instances <strong>of</strong> the same proxy in order to load the traffic across<br />

the multiple instances. This is useful for hardware configurations with multiple<br />

CPUs or sites that have experienced problems due to an exceedingly large<br />

amount <strong>of</strong> concurrent connections through one <strong>of</strong> those proxies. A single proxy<br />

instance for any <strong>of</strong> these proxies can handle up to 8000 sessions (a session<br />

consists <strong>of</strong> two connections for most protocols), which is more than adequate<br />

for most sites. However, if your site is consistently recording concurrent<br />

sessions that hover around the 8000 range (or if you have experienced<br />

problems because the number <strong>of</strong> connection attempts is significantly higher)<br />

for any <strong>of</strong> these proxies, you may need to enable additional instances for that<br />

proxy.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!