Technical Library | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Configuration Options > Networking > Connection Management
Connection Management
Help | Content Gateway | Version 8.1.x
The options on the Connection Management pages allow you to tune several important properties of proxy behavior, including connection throttling and load shedding, individual client connection limits and rates, and how to respond to low memory conditions.
By default, Content Gateway accepts 45,000 connections. A connection throttle event occurs when client or origin server connections reach 90% of half the configured limit (20,250 by default). When a connection throttle event occurs, Content Gateway continues processing all existing connections and queues new client connection requests until the connection count falls below the limit.
If you think that Content Gateway is hitting the connection limits, you should monitor the Performance graphs to get an accurate reading of connection activity. In particular, check the Active Client Connections and TCP ESTABLISHED Connections graphs. You can also check error messages in the system log file, error log file, or event log files.
Configure > Networking > Connection Management > Throttling
 
Throttling Net Connections
Specifies the maximum number of network connections that Content Gateway accepts. The default value is 45,000.
Setting a Content Gateway throttle limit helps to prevent system overload when traffic bottlenecks develop. When network connections reach this limit, Content Gateway queues new connections until existing connections close.
Do not set this variable below the minimum value of 100.
Configure > Networking > Connection Management > Load Shedding
 
Maximum Connections
Specifies the maximum number of client connections allowed before the ARM starts forwarding incoming requests directly to the origin server. The default value is 1 million connections.
If you change this option, you must restart Content Gateway.
Configure > Networking > Connection Management > Client Connection Control
Specifies:
*
Client concurrent connection limits
*
Client connection rate limits
*
Proxy response when a limit is exceeded
*
A list of clients excepted from the limits
 
Concurrent Connection Limit: Maximum concurrent connections
Specifies the maximum number of concurrent HTTP/HTTPS connections a client is allowed. The default is 1000. The supported range is: 1 - 45000
Concurrent Connection Limit: Alert when limit exceeded
When enabled, causes Content Gateway to generate an alert when a client exceeds the maximum concurrent connection limit.
In addition to displaying the alert in the Content Gateway manager, it is also logged in /var/log/messages and content_gateway.out.
Concurrent Connection Limit: Close excessive connections when limit exceeded
When enabled, causes Content Gateway to close excessive connections when the limit is exceeded.
Connection Rate Limit: Maximum connection rate
Specifies the maximum connections per second, averaged over a minute, that a client can make. The default is 100. The supported range is: 1 - 1000
Connection Rate Limit: Alert when limit exceeded
When enabled, causes Content Gateway to generate an alert when a client exceeds the maximum connection rate limit.
In addition to displaying the alert in the Content Gateway manager, it is also logged in /var/log/messages and content_gateway.out.
Connection Rate Limit: Close excessive connections when limit exceeded
When enabled, causes Content Gateway to close excessive connections when the limit is exceeded.
Exceptions
Specifies IP addresses and/or IP address ranges to which connection limits are not applied. IP addresses can be IPv4 or IPv6 (IPv6 support must be enabled). Multiple addresses or ranges can be specified in a comma-separated list that can contain up to:
*
64 IPv4 addresses
*
32 IPv4 address ranges
*
24 IPv6 addresses
*
12 IPv6 address ranges
Configure > Networking > Connection Management > Low Memory Mode
Specifies whether Content Gateway suspends analysis of web traffic when the host system experiences a low-memory condition. In this state, Web module policy enforcement is applied as usual.
 
Low Memory Mode: Enabled/Disabled
Select Enabled to suspend content analysis when there is a low memory condition.
Low Memory Mode Duration
Specifies the length of time, in minutes, that content analysis is suspended.
If the low memory condition resolves itself before the timer expires, analysis resumes and the low memory mode trigger resets.
If the timer expires, analysis resumes and the low memory mode trigger is not reset.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Configuration Options > Networking > Connection Management
Copyright 2016 Forcepoint LLC. All rights reserved.