InlinePolicyLbPoolAccess1

JSON Example

{
    "algorithm": "string",
    "ip_port_list": [
        {
            "ip_address": "string",
            "port": 0
        }
    ],
    "lb_monitor_profile": "string",
    "pool_port": 0,
    "source_nat": "string"
}

string

algorithm

Optional

Load balanding algorithm controls how the incoming connections are distributed among the members.

ROUND_ROBIN - requests to the application servers are distributed in a round-robin fashion,
LEAST_CONNECTION - next request is assigned to the server with the least number of active connections

Possible values are : ROUND_ROBIN, LEAST_CONNECTION,

array of IPAddressPortPair

ip_port_list

Optional

IP Port list for applications within the Group to allow for non-uniform port usage by applications

string

lb_monitor_profile

Optional

Path of the PolicyLbMonitorProfile to actively monitor the PolicyLbPoolAccess's Group

integer As int32 As int32

pool_port

Optional

Port for LoadBalancer to send connections to the PolicyLbPoolAccess's Group. Pool_port could be optional, if it is not specified, LB will use PolicyLbVirtualServer port to connect to backend servers. If the PolicyLbMonitorProfile is configured in PolicyLbPoolAccess and active monitor IP protocol is TCP/UDP(which requires TCP or UDP port number), monitor_port should be specified if pool_port is unset.

string

source_nat

Optional

Depending on the topology, Source NAT (SNAT) may be required to ensure traffic from the server destined to the client is received by the load balancer. SNAT can be enabled per pool. If SNAT is not enabled for a pool, then load balancer uses the client IP and port (spoofing) while establishing connections to the servers. This is referred to as no-SNAT or TRANSPARENT mode. SNAT is enabled by default and will use the load balancer interface IP and an ephemeral port as the source IP and port of the server side connection.

Possible values are : ENABLED, DISABLED,

Used By

PolicyLbPoolAccess