Technical data

42 Brocade ServerIron ADX Advanced Server Load Balancing Guide
53-1003441-01
Configuring transparent cache switching
2
Identify application ports for caching
For each defined cache server you must specify the ports whose traffic you want to cache. The
following example configures the previously named “server1” cache server to cache traffic from the
port: “http”, “ssl” and port number “8080”.
ServerIronADX(config)#server cache-name server1
ServerIronADX(config-rs-server1)#port http
ServerIronADX(config-rs-server1)#port ssl
ServerIronADX(config-rs-server1)#port 8080
Syntax: [no] port portname | portnum
NOTE
A maximum of 256 non-well-known ports (port number >1024) can be configured.
NOTE
Where a non-well-known port is configured for the portname or portnum variable, a policy with port
“0” needs to be configured as described in “Enabling transparent cache switching” on page 44.
Assigning web cache servers to cache groups
TCS requires all cache servers to belong to a cache group. To assign cache servers to a different
cache group, use the server cache-group number command.
The ServerIron ADX uses one of two methods to distribute requests among the servers in a cache
group: a hashing algorithm based on source and destination IP addresses or the least-connection
method.
• The hashing algorithm is the default method for the HTTP and SSL protocols.
• The least-connection method is the default method for all other protocols.
The method can be changed from the default setting for all protocols. Refer to “Increasing the TCS
hash bucket count” on page 60.
In addition, cache groups provide automatic recovery from a failed or otherwise out-of-service web
cache server. If a web cache server failure occurs, ServerIron ADX detects the failure and directs
subsequent requests to the next available cache server or forwards the request directly to the WAN
link. For more information see, “csw-policy policy-name” on page 83 and “Redirecting client
requests to an available cache server” on page 64.