InlineLbPool1
{
"member_group": {
"grouping_object": {
"target_display_name": "string",
"is_valid": false,
"target_id": "string",
"target_type": "string"
},
"ip_revision_filter": "string",
"max_ip_list_size": 0,
"port": 0,
"customized_members": [
{
"admin_state": "string",
"ip_address": "string",
"port": "string",
"weight": 0,
"display_name": "string"
}
]
},
"snat_translation": {
"type": "string",
"port_overload": 0
},
"algorithm": "string",
"members": [
{
"max_concurrent_connections": 0,
"admin_state": "string",
"backup_member": false,
"weight": 0,
"display_name": "string",
"ip_address": "string",
"port": "string"
}
],
"passive_monitor_id": "string",
"tcp_multiplexing_number": 0,
"active_monitor_ids": [
"string"
],
"tcp_multiplexing_enabled": false,
"min_active_members": 0
}Load balancing algorithm, configurable per pool controls how the incoming connections are distributed among the members.
Server pool consists of one or more pool members. Each pool member is identified, typically, by an IP address and a port.
Passive healthchecks are disabled by default and can be enabled by attaching a passive health monitor to a server pool. Each time a client connection to a pool member fails, its failed count is incremented. For pools bound to L7 virtual servers, a connection is considered to be failed and failed count is incremented if any TCP connection errors (e.g. TCP RST or failure to send data) or SSL handshake failures occur. For pools bound to L4 virtual servers, if no response is received to a TCP SYN sent to the pool member or if a TCP RST is received in response to a TCP SYN, then the pool member is considered to have failed and the failed count is incremented.
The maximum number of TCP connections per pool that are idly kept alive for sending future client requests.
In case of active healthchecks, load balancer itself initiates new connections (or sends ICMP ping) to the servers periodically to check their health, completely independent of any data traffic. Active healthchecks are disabled by default and can be enabled for a server pool by binding a health monitor to the pool. Currently, only one active health monitor can be configured per server pool.
TCP multiplexing allows the same TCP connection between load balancer and the backend server to be used for sending multiple client requests from different client TCP connections.
A pool is considered active if there are at least certain minimum number of members.