Still waiting for passwords and access, still reading config guides. This time, it is 6500’s Content Switch Module‘s turn. Behind this obscure name, you’ll actually find a load balancer.
Using a predictor, that is a function, and weight for each server, denoting the share of load to put on that server, the connections are balanced on multiple servers.
Even if http is supposed to be stateless, connections from a client sometimes need to stay on the same server. sticky to achieve this session persistance.
Health monitoring to check if servers are still alive and able to handle the work. Active probes (customized), inband monitoring (L3), or HTTP return code checking. TCL scripting is also available for custom probes.
Netw82 