In a deployment where the ProxySG appliance forwards traffic to the Symantec Web Security Service (WSS) and a large number of users use the service, latency increases and page-loading timeouts occur. These issues might occur because the pool of TCP connections is exhausted.
The pool of TCP connections is exhausted because the ProxySG appliance is forwarding traffic to a single destination (WSS) rather than dispersing traffic to multiple public-content providers. Additionally, the pool of connections might also be exhausted by:
A large number of users using the WSS
Applications that consume a large number of TCP ports, such as Microsoft Office 365 applications
This article provides instructions on how to detect and resolve this situation.
Determine If All Connections Are Being Consumed
To determine if all connections are being consumed, view the statistic for the ProxySG appliance that increases when the appliance was unable to find a source port:
In a web browser, go to: https://<ProxySG_IP_Address>:<Port_Number>/TCP/Statistics?stats_mode=3
Locate the row for TCP2.214. Ensure the number for this protocol remains static and does not increase as peak load occurs. A number that increases means that the appliance was not able to find a source port.
Resolution: Increase the Number of Available Connections
To increase the number of available connections, do the following until the TCP2.214 statistic remains static, and the latency and timeout issues are resolved:
If the issues persist, contact Symantec support for further investigation.
Increase Maximum Number of Source Ports for the ProxySG Appliance
By default, the maximum number of source ports is 16,384. To ensure enough unique connections are available, use the following CLI command to increase the number of ports to the maximum possible for the appliance:
Reduce the Amount of Time a TCP Connection is in the TIME_WAIT State
To reduce the amount of time a TCP connection is in the TIME_WAIT state, use the following CLI command:
#(config) tcp-ip tcp-2msl 30
Note: For other devices in your network, such as firewalls, ensure that the TCP TIME_WAIT state value is not lower than the value you set for the ProxySG appliance.
Reducing the TCP TIME_WAIT state value ensures that the ProxySG source ports become reusable more quickly.
Configure Additional Egress IP Addresses from Your ProxySG Appliance to the Web Security Service
To configure additional egress IP addresses from your appliance to WSS:
Configure additional IP addresses by using the following CLI command: #(config interface <interface_number>) ip-address <ip-address> <subnet-mask>
Create policy to divide outgoing connections between the additional IP addresses. To do this, configure client subnets that are approximately the same size to use different addresses. The following is an example of CPL to configure the subnets: <forward> client.address=<ip_address_of_client_subnet> reflect_ip(<sg_ip_one>) client.address=<ip_address_of_client_subnet> reflect_ip(<sg_ip_two>) and so on for as many client subnets as necessary.
Save and deploy policy.
Configure the ProxySG Appliance to Connect to Multiple Web Security Service IP Addresses (Limited Availability)
Note: This option is available on a limited basis in some data centers.
Use this option if you want to avoid adding public IP addresses to your ProxySG appliance.
To obtain additional IP addresses for WSS, contact your Symantec point of contact for assistance. When you have the additional IP addresses, do the following:
Set Up Forwarding Hosts for Each IP Address
To set up forwarding hosts:
In the Management Console, select the Configuration > Forwarding > Forwarding Hosts tab.
Repeat these steps for each IP address. Note: If you are configuring multiple ports per IP address, you will need to repeat these steps multiple times per IP address. For example, if you want to configure a host for ports 8080 and 8443 for an IP address, create two hosts for that address; one host for port 8080 for that address and another host for port 8443 for the same address.
Create a Forwarding Group
Create forwarding groups for each WSS port you configured a forward host for. For example, if you created forwarding hosts for ports 8080 and 8443, then you will create two forwarding groups, one for each port.
To create a forwarding group:
In the Management Console, select the Configuration > Forwarding > Forwarding Groups tab.
In the Alias field, enter a unique name for the forwarding group. Note: Because the forwarding group alias is used in policy, the alias cannot be a CPL keyword, such as no, default, or forward.
In the Alias name field, select the hosts you previously created and click Add.
In the Load Balancing and Host Affinity section, select the following:
From the Load balancing method list, select Least Connections.
From the Host affinity methods list, select Client IP Address for all applicable host affinities.
Repeat these steps for each WSS port you created a forwarding host for.
(Optional) Edit the Health Check for the Forwarding Group
To edit the health check for your forwarding group:
In the Management Console, select the Configuration > Health Checks > General.
Select the health check for the forwarding group you want to edit.
In the Minimum number of members that must be healthy for the group to be healthy dropdown, select either All or Any.
Verify that your ProxySG appliance balances traffic equally among the WSS IP addresses.
To verify if load balancing is functioning:
In a web browser, go to: https://<ProxySG_IP_Address>:<Port_Number>/Forwarding/StatsIP
View the Connect Active (Total) statistic for each IP address in the forwarding groups you created to resolve the connection issues. If load balancing is functioning correctly, the number of connections for each address should be similar.
Subscribing will provide email updates when this Article is updated. Login is required.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
Subscribed to the Article.
Unable to subscribe
Thanks for your additional feedback !!!
Enterprise Support Virtual Agent
Rate Me :
Tell us more:
Welcome! My name is Sami, the Enterprise Support Virtual Agent answering technical support questions.