User manual

The WebMux™ Model 480S, 580SG, and 680PG User Guide – Version 7.0.x

Generic no health check (TCP) User Specify

Generic no health check (UDP) User Specify

Generic no health check (TCP/UDP) User Specify

Custom Defined TCP Services 80 or User Specify

Custom Defined UDP Services User Specify

Custom Defined TCP/UDP Services User Specify

Custom Defined Paired HTTP and HTTPS

(TCP) Service

User Specify

Scheduling method:

The scheduling method is the way in which traffic is distributed among the

servers in the farm. Eight different methods are supported. If you are using a

shopping cart service, a persistent scheduling method is recommended.

• Least connections

• Least connections - persistent

• Round robin

• Round robin - persistent

• Weighted least connections

• Weighted least connections - persistent

• Weighted round robin

• Weighted round robin – persistent

• Weighted fastest response

• Weighted fastest response - persistent

• Layer 7 HTTP URI load directing

• Layer 7 HTTP URI load directing with cookies

• Layer 7 hashed URI load directing

Layer 7 scheduling methods can only be used with the HTTP – Hypertext

Transfer Protocol (TCP) service. These scheduling methods allow you to direct

traffic to a specific group of servers depending on a match pattern that is

compared to the URI in the client’s GET request header.

Layer 7 HTTP URI load directing with cookies allows the WebMux™ to direct

traffic from the same client to the same server in the farm. This scheduling

method also compares the match pattern against the host MIME header. In

other words, a host name can be specified as a match pattern. Also, if the server

generates a cookie, the WebMux™ will generate its own cookie to keep track of

which client session belongs to which server. These are useful for shopping cart

services, for example, so that a client will be directed to the same server and

keep their shopping cart items valid. The WebMux™’s cookie expire time

matches the MAX_AGE setting specified in the cookie generated by the servers.

When MAX_AGE is not defined, the cookie expire time is 30 minutes.