Brocade Communications Systems ServerIron ADX 12.4.00 Service Manual Page 74

  • Download
  • Add to my manuals
  • Print
  • Page
    / 136
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 73
62 ServerIron ADX Advanced Server Load Balancing Guide
53-1002435-01
Other TCS options
2
This example assumes that a source IP address is configured and Source NAT and Destination NAT
also are enabled, if applicable.
Shutting down a cache server
The force shutdown feature (sometimes called the force delete feature) allows you to force
termination of existing SLB connections. This feature assumes that you already have shut down a
TCP/UDP service on the real server or you have shut down the real server itself.
There are several methods for shutting down a cache server. Some methods involve changing the
ServerIron ADX configuration while other methods involve shutting down the cache server itself.
Each method has consequences, so choose the method that works best in your situation.
Edit the cache server configuration on the ServerIron ADX to disable the HTTP (or other) port
on the server. For example, to disable port 80 (HTTP), you can use the port http disable
command at the cache level of the CLI. If you use this method, you do not need to re-define the
cache server to add the server back to TCS. However, you do need to re-enable the disabled
TCP/UDP ports.
Although the HTTP port is disabled in the ServerIron ADX definition of the cache server, all the
sites mapped to the cache server before the port was disabled remain mapped to the cache
server. When the cache server comes back up, it gets the same traffic it used to have. While
the cache server is disabled, the remaining cache servers temporarily handle caching for the
down cache server’s sites, but stop when the cache is restored. This behavior is the same as if
the cache actually died.
NOTE
You might need to set the maximum connections parameter for the remaining cache servers,
especially if the servers already run at a high percentage of their capacity when all cache
servers are available. Refer to “Configuring maximum connections for a cache server” on
page 59.
Delete the cache server from the ServerIron ADX. This option immediately prevents new
connections. The ServerIron ADX ends existing connections after two minutes or, if you have
enabled the force shutdown option, immediately.
Do not use this method unless you have only one cache server. If you use this method, to
re-add the cache server to the ServerIron ADX, you must redefine the cache server and
re-assign it to a cache group. Moreover, because the ServerIron ADX uses a hashing function to
allocate contents among cache servers, the ServerIron ADX allocates traffic to the remaining
caches. If the deleted cache server is down for a while in a busy network, the traffic might be
unevenly balanced between the cache server tat was down and the other cache servers. To
reset the hash function and thus rebalance the serving load, you need to reboot the ServerIron
ADX.
Shut down the cache server itself, rather than change definitions on the ServerIron ADX. When
the cache server stops responding to health checks, the ServerIron ADX removes the server
from TCS. If you have only one cache server, user traffic is switched at Layer 2 to the Internet
until the cache server comes back. If you have more than one cache server, the remaining
cache servers provide service until the disabled cache server comes back.
Page view 73
1 2 ... 69 70 71 72 73 74 75 76 77 78 79 ... 135 136

Comments to this Manuals

No comments