InlineLbService1

JSON Example

{
    "access_log_enabled": false,
    "attachment": {
        "is_valid": false,
        "target_display_name": "string",
        "target_id": "string",
        "target_type": "string"
    },
    "enabled": false,
    "error_log_level": "string",
    "relax_scale_validation": false,
    "size": "string",
    "virtual_server_ids": [
        "string"
    ]
}

boolean

access_log_enabled

Optional

Whether access log is enabled

ResourceReference

attachment

Optional

A weak reference to an NSX resource.

boolean

enabled

Optional

Constraints: default: true

Whether the load balancer service is enabled

string

error_log_level

Optional

Constraints: default: INFO

Load balancer engine writes information about encountered issues of different severity levels to the error log. This setting is used to define the severity level of the error log.

Possible values are : DEBUG, INFO, WARNING, ERROR, CRITICAL, ALERT, EMERGENCY,

boolean

relax_scale_validation

Optional

If relax_scale_validation is true, the scale validations for virtual servers/pools/pool members/rules are relaxed for load balancer service. When load balancer service is deployed on edge nodes, the scale of virtual servers/pools/pool members for the load balancer service should not exceed the scale number of the largest load balancer size which could be configured on a certain edge form factor. For example, the largest load balancer size supported on a MEDIUM edge node is MEDIUM. So one SMALL load balancer deployed on MEDIUM edge nodes can support the scale number of MEDIUM load balancer. It is not recommended to enable active monitors if relax_scale_validation is true due to performance consideration. If relax_scale_validation is false, scale numbers should be validated for load balancer service. The property is deprecated as NSX-T Load Balancer is deprecated.

string

size

Optional

Constraints: default: SMALL

The size of load balancer service

Possible values are : SMALL, MEDIUM, LARGE, XLARGE, DLB,

array of string

virtual_server_ids

Optional

virtual servers can be associated to LbService(which is similar to physical/virtual load balancer), Lb virtual servers, pools and other entities could be defined independently, the virtual server identifier list here would be used to maintain the relationship of LbService and other Lb entities.

Used By

LbService