Configuring the WSM using Device Manager

About connection timeouts for real servers

Every client-to-server session being load balanced is recorded in the WSM's session table. The typical session completes the following sequence:

1. A client makes a request.
2. The session is recorded in the table.
3. The data is transferred until the client ends the session.
4. The session table entry is removed.

In certain circumstances, such as when a client application is abnormally terminated by the client's system, TCP/UDP connections will remain registered in the WSM's binding table. In order to prevent table overflow, these orphaned entries must be aged out. By setting the real server Timeout threshold for the maximum number of minutes an inactive connection can remain open, you can ensure that orphan table entries are removed.

If an open TCP/IP sessions is not closed properly, it remains inactive for 10 minutes, by default, before it is removed from the WSM session table. For example, if the WSM receives the SYN for the session but no FIN, the connection remains open in the session table until it reaches the timeout threshold set for the real server. You can change the default timeout period for a real server. The Timeout threshold must be specified in even-numbered increments.

See also:

• Configuring each real server
• Real Servers fields
• Methods of server load balancing
• Topology rules for SLB
• About load balancing metrics
• Configuring each real server
• Virtual server load balancing