InlineLbVirtualServer1
{
"ip_protocol": "string",
"server_tcp_profile_id": "string",
"sorry_pool_id": "string",
"port": "string",
"server_ssl_profile_binding": {
"server_auth_crl_ids": [
"string"
],
"server_auth": "string",
"certificate_chain_depth": 0,
"client_certificate_id": "string",
"server_auth_ca_ids": [
"string"
],
"ssl_profile_id": "string"
},
"pool_id": "string",
"client_tcp_profile_id": "string",
"default_pool_member_port": "string",
"access_log_enabled": false,
"application_profile_id": "string",
"max_concurrent_connections": 0,
"rule_ids": [
"string"
],
"max_new_connection_rate": 0,
"persistence_profile_id": "string",
"client_ssl_profile_binding": {
"client_auth": "string",
"ssl_profile_id": "string",
"certificate_chain_depth": 0,
"client_auth_ca_ids": [
"string"
],
"default_certificate_id": "string",
"sni_certificate_ids": [
"string"
],
"client_auth_crl_ids": [
"string"
]
},
"default_pool_member_ports": [
"string"
],
"ip_address": "string",
"ports": [
"string"
],
"enabled": false
}Assigned Internet Protocol in IP header, TCP, UDP are supported.
Only L7 virtual server could be configured with customized server side TCP profile.
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.
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.
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.
Only L7 virtual server could be configured with customized client side TCP profile.
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.
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.
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.
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.
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.
Persistence profile is used to allow related client connections to be sent to the same backend server.
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.
virtual server IP address
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.
whether the virtual server is enabled