Configuring an LB connection limit policy
Using an LB connection limit policy can limit the number of connections on the device. It helps prevent a large number of connections from consuming too many device system resources and server resources. In this way, internal network resources (hosts or servers) are protected, and device system resources can be used more appropriately.
An LB connection limit policy can have multiple rules. Each rule specifies a range of users and the limit to the user connections. A connection limit policy applies only to the user connections matching a rule. When the number of connections for a certain type reaches the upper limit (max-amount), the device does not accept new connection requests of that type. It accepts new connection requests only when the number of connections drops below the lower limit (min-amount).
The user ranges in the rules are set by using ACLs.
To configure an LB connection limit policy:
Step | Command | Remarks |
|---|---|---|
1. Enter system view. | system-view | N/A |
2. Create an LB connection limit policy, and enter LB connection limit policy view. | loadbalance limit-policy policy-name | By default, no LB connection limit policies exist. |
3. Configure an LB connection limit rule. | limit limit-id acl [ ipv6 ] { acl-number | name acl-name } [ per-destination | per-service | per-source ] * amount max-amount min-amount | By default, no rules are configured for an LB connection limit policy. |
4. (Optional.) Set a description for the LB connection limit policy. | description text | By default, no description is set for an LB connection limit policy. |