Server load balancing configuration task list
Tasks at a glance |
|---|
(Required.) Configuring a server farm |
(Required.) Configuring a real server |
(Required.) Configuring a virtual server |
(Optional.) Configuring an LB class |
(Optional.)Configuring an LB action |
(Optional.) Configuring an LB policy |
(Optional.) Configuring a sticky group |
(Optional.)Configuring a parameter profile |
(Optional.)Configuring an LB connection limit policy |
(Optional.) Configuring the ALG feature |
(Optional.) Scheduling a load balancing test |
(Optional.) Enabling SNMP notifications |
(Optional.) Enabling load balancing logging |
Figure 47: Relationship between the main configuration items
Figure 47 shows the relationship between the following configuration items:
Server farm—A collection of real servers that contain similar content. A sever farm can be referenced by a virtual server or an LB action.
Real server—An entity on the LB device to process user services.
Virtual server—A virtual service provided by the LB device to determine whether to perform load balancing for packets received on the LB device. Only the packets that match a virtual server are load balanced.
LB class—Classifies packets to implement load balancing based on packet type.
LB action—Drops, forwards, or modifies packets.
LB policy—Associates an LB class with an LB action. An LB policy can be referenced by a virtual server.
Sticky group—Uses a sticky method to distribute similar sessions to the same real server. A sticky group can be referenced by a virtual server or an LB action.
Parameter profile—Defines advanced parameters to process packets. A parameter profile can be referenced by a virtual server.