| Configuring the WSM using Device Manager |
|
If a certain number of connection requests for a particular service fail, the WSM places the service into the Service Failed state. While in this state, no new connection requests are sent to the server for this service. However, if you enable graceful real server failure, state information about existing sessions is maintained and traffic associated with existing sessions continues to be sent to the server. Connection requests to, and traffic associated with, other load-balanced services continue to be processed by the server.
For example, a real server is configured to support HTTP and FTP within two real server groups. If the WSM detects an HTTP service failure on the real server, it removes that real server group from the load-balancing algorithm for HTTP but keeps the real server in the mix for FTP. Removing only the failed service from load balancing allows users access to all healthy servers supporting a given service. When a service on a server is in the Service Failed state, the WSM sends Layer 4 connection requests for the failed service to the server. When the WSM has successfully established a connection to the failed service, the service is restored to the load-balancing algorithm.
See also:
|
|