InlineLbVirtualServer1
{
"access_list_control": {
"action": "string",
"enabled": false,
"group_id": "string"
},
"access_log_enabled": false,
"application_profile_id": "string",
"client_ssl_profile_binding": "ClientSslProfileBinding Object",
"default_pool_member_port": "string",
"default_pool_member_ports": [
"string"
],
"enabled": false,
"ip_address": "string",
"ip_protocol": "string",
"log_significant_event_only": false,
"max_concurrent_connections": 0,
"max_new_connection_rate": 0,
"persistence_profile_id": "string",
"pool_id": "string",
"port": "string",
"ports": [
"string"
],
"rule_ids": [
"string"
],
"server_ssl_profile_binding": "ServerSslProfileBinding Object",
"sorry_pool_id": "string"
}LbAccessListControl is used to define how IP access list control can filter the connections from clients.
Whether access log is enabled
The application profile defines the application protocol characteristics. It is used to influence how load balancing is performed. Currently, LbFastTCPProfile, LbFastUDPProfile and LbHttpProfile, etc are supported.
This is a deprecated property, please use 'default_pool_member_ports' instead. If default_pool_member_port is configured and default_pool_member_ports are not specified, both default_pool_member_port and default_pool_member_ports in response payload would return the same port value. If both are specified, default_pool_member_ports setting would take effect with higher priority.
If default_pool_member_ports are configured, both default_pool_member_port and default_pool_member_ports in the response payload would include port settings, notice that the value of default_pool_member_port is the first element of default_pool_member_ports.
whether the virtual server is enabled
virtual server IP address
Assigned Internet Protocol in IP header, TCP, UDP are supported.
The property log_significant_event_only can take effect only when access_log_enabled is true. If log_significant_event_only is true, significant events are logged in access log. For L4 virtual server, significant event means unsuccessful(error or dropped) TCP/UDP connections. For L7 virtual server, significant event means unsuccessful connections or HTTP/HTTPS requests which have error response code(e.g. 4xx, 5xx).
To ensure one virtual server does not over consume resources, affecting other applications hosted on the same LBS, connections to a virtual server can be capped. If it is not specified, it means that connections are unlimited. The property is deprecated as NSX-T Load Balancer is deprecated.
To ensure one virtual server does not over consume resources, connections to a member can be rate limited. If it is not specified, it means that connection rate is unlimited. The property is deprecated as NSX-T Load Balancer is deprecated.
Persistence profile is used to allow related client connections to be sent to the same backend server.
The server pool(LbPool) contains backend servers. Server pool consists of one or more servers, also referred to as pool members, that are similarly configured and are running the same application.
This is a deprecated property, please use 'ports' instead. Port setting could be single port for both L7 mode and L4 mode. For L4 mode, a single port range is also supported. The port setting could be a single port or port range such as "80", "1234-1236". If port is configured and ports are not specified, both port and ports in response payload would return the same port value. If both port and ports are configured, ports setting would take effect with higher priority.
Port setting could be a single port for both L7 mode and L4 mode. For L4 mode, multiple ports or port ranges are also supported such as "80", "443", "1234-1236". If ports is configured, both port and ports in the response payload would include port settings, notice that the port field value is the first element of ports.
Load balancer rules allow customization of load balancing behavior using match/action rules. Currently, load balancer rules are supported for only layer 7 virtual servers with LbHttpProfile. The property is deprecated as NSX-T Load Balancer is deprecated.
When load balancer can not select a backend server to serve the request in default pool or pool in rules, the request would be served by sorry server pool. The property is deprecated as NSX-T Load Balancer is deprecated.