Configuration name. Valid characters are A-Z, a-z, 0-9, _, and -. No spaces. You reference this name in the LLB policy configuration.

Note: After you initially save the configuration, you cannot edit the name.

IPv4

Note: IPv4 is selected by default, and cannot be changed.

• Weighted Round Robin—Dispatches new connections to link members using a weighted round-robin method.
• Least Connections—Dispatches new connections to the link member with the lowest number of connections.
• Least New Connections per Second—Dispatches new connections to the link member that has the lowest rate of new connections per second.
• Least Throughput Outbound—Dispatches new connections to the link member with the least outbound traffic.
• Least Throughput Inbound—Dispatches new connections to the link member with the least inbound traffic.
• Least Throughput Total—Dispatches new connections to the link member with the least total traffic (that is, inbound plus outbound).
• Spillover Throughput Outbound—Dispatches new connections according to the spillover list based on outbound traffic.
• Spillover Throughput Inbound—Spillover list based on inbound traffic.
• Spillover Throughput Total—Spillover list based on total traffic (that is, inbound plus outbound).
• Source Address Hash—Selects the gateway link based on a hash of the source IP address.

Select a persistence configuration. Optional.

• Enable—The system uses the proximity route logic and configuration when determining routes.
• Disable—The system does not use the proximity route configuration.

Add member

Configuration name. Valid characters are A-Z, a-z, 0-9, _, and -. No spaces.

After you initially save the configuration, you cannot edit the name.

Select a gateway configuration object. See Configuring gateway links.

Assigns relative preference among members—higher values are more preferred and are assigned connections more frequently. The default is 1. The valid range is 1 to 255.

All load balancing methods consider weight, except spillover, which uses its own priority configuration. Servers are dispatched requests proportional to their weight, relative to the sum of all weights.

The following example shows the effect of weight on WRR:

• Sever A, Weight 2; Server B, Weight 1: Requests are sent AABAAB.
• Sever A, Weight 3; Server B, Weight 2: Requests are sent AABAB.

For other methods, weight functions as a tie-breaker. For example, with the Least Connection algorithm, requests are sent to the server with the least connections. If the number of connections is equal, the request is sent to the server with the greater weight. For example:

• Server A, Weight 1, 1 connection
• Server B, Weight 2, 1 connection

The next request is sent to Server B.

Assigns a priority to the link when using a spillover load balancing method. Higher values have greater priority. When a spillover method is enabled, the system dispatches new connections to the link that has the greatest spillover priority until its threshold is exceeded; then it dispatches new connections to the link with the next greatest priority until its threshold is exceeded, and so on.

If multiple links in a link group have the same spillover priority, the system dispatches new connections among those links according to round robin.

The default is 0. The valid range is 0-9.

• Enable—The member is considered available for new traffic.
• Disable—The member is considered unavailable for new traffic.