CreateBackendSet

post

/20170115/loadBalancers/{load_balancer_id}/backendSets

Adds a backend set to a load balancer.

Request

Supported Media Types
Path Parameters
Header Parameters
  • For optimistic concurrency control. In the PUT or DELETE call for a resource, set the if-match parameter to the value of the ETag from a previous GET or POST response for that resource. The resource is updated or deleted only if the ETag you provide matches the resource's current ETag value.
    Default Value:
  • The unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
    Default Value:
  • Minimum Length: 1
    Maximum Length: 64
    A token that uniquely identifies a request so it can be retried in case of a timeout or server error without risk of executing that same action again. Retry tokens expire after 24 hours, but can be invalidated before then due to conflicting operations (for example, if a resource has been deleted and purged from the system, then a retry of the original creation request may be rejected).
Body ()
The details for adding a backend set.
Root Schema : CreateBackendSetDetails
Type: object
The configuration details for creating a backend set in a network load balancer. Avoid entering confidential information when you supply string values using the API.
Show Source
  • backends
    Unique Items Required: true
    An array of backends to be associated with the backend set.
  • HealthCheckerDetails
    The health check policy configuration.
  • Default Value: IPV4
    Allowed Values: [ "IPV4", "IPV6" ]
    IP version associated with the backend set.
  • Default Value: true
    If this parameter is enabled, then the network load balancer preserves the source IP of the packet when it is forwarded to backends. Backends see the original source IP. If the isPreserveSourceDestination parameter is enabled for the network load balancer resource, then this parameter cannot be disabled. The value is true by default.
  • Minimum Length: 1
    Maximum Length: 32
    A user-friendly name for the backend set that must be unique and cannot be changed. Valid backend set names include only alphanumeric characters, dashes, and underscores. Backend set names cannot contain spaces. Avoid entering confidential information.
  • Default Value: FIVE_TUPLE
    Allowed Values: [ "TWO_TUPLE", "THREE_TUPLE", "FIVE_TUPLE" ]
    The network load balancer policy for the backend set. Example: FIVE_TUPLE
Nested Schema : backends
Type: array
Unique Items Required: true
An array of backends to be associated with the backend set.
Show Source
Nested Schema : HealthCheckerDetails
Type: object
The health check policy configuration.
Show Source
  • Default Value: 10000
    The interval between health checks, in milliseconds. The default value is 10000 (10 seconds). Example: 10000
  • The backend server port against which to run the health check. If the port is not specified, then the network load balancer uses the port information from the Backend object. The port must be specified if the backend port is 0. Example: 8080
    Example: 8080
  • Allowed Values: [ "HTTP", "HTTPS", "TCP", "UDP" ]
    The protocol the health check must use; either HTTP or HTTPS, or UDP or TCP. Example: HTTP
  • Base64 encoded pattern to be sent as UDP or TCP health check probe.
  • A regular expression for parsing the response body from the backend server. Example: ^((?!false).|\s)*$
  • Base64 encoded pattern to be validated as UDP or TCP health check probe response.
  • Default Value: 3
    The number of retries to attempt before a backend server is considered "unhealthy". This number also applies when recovering a server to the "healthy" state. The default value is 3. Example: 3
  • The status code a healthy backend server should return. If you configure the health check policy to use the HTTP protocol, then you can use common HTTP status codes such as "200". Example: 200
    Example: 200
  • Default Value: 3000
    The maximum time, in milliseconds, to wait for a reply to a health check. A health check is successful only if a reply returns within this timeout period. The default value is 3000 (3 seconds). Example: 3000
  • The path against which to run the health check. Example: /healthcheck
Nested Schema : BackendDetails
Type: object
The network network load balancing configuration details of a backend server.
Show Source
  • The IP address of the backend server. Example: 10.0.0.3
  • Default Value: IPV4
    Allowed Values: [ "IPV4", "IPV6" ]
    IP version associated with the BackendDetails object.
  • Default Value: false
    Whether the network load balancer should treat this server as a backup unit. If true, then the network load balancer forwards no ingress traffic to this backend server unless all other backend servers not marked as "isBackup" fail the health check policy. Example: false
  • Default Value: false
    Whether the network load balancer should drain this server. Servers marked "isDrain" receive no incoming traffic. Example: false
  • Default Value: false
    Whether the network load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: false
  • A read-only field showing the IP address/OCID and port that uniquely identify this backend server in the backend set. Example: 10.0.0.3:8080, or ocid1.privateip..unique_ID:443 or 10.0.0.3:0
  • Minimum Value: 0
    Maximum Value: 65535
    The communication port for the backend server. Example: 8080
  • The IP OCID/Instance OCID associated with the backend server. Example: ocid1.privateip..unique_ID
  • Minimum Value: 1
    Maximum Value: 100
    Default Value: 1
    The network load balancing policy weight assigned to the server. Backend servers with a higher weight receive a larger proportion of incoming traffic. For example, a server weighted '3' receives three times the number of new connections as a server weighted '1'. Example: 3
Back to Top

Response

Supported Media Types

204 Response

The request was accepted for processing.
Headers

304 Response

Not Modified
Headers
  • Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source

400 Response

Bad Request
Headers
  • Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source

401 Response

Unauthorized
Headers
  • Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source

404 Response

Not Found
Headers
  • Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source

412 Response

Precondition Failed
Headers
  • Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source

500 Response

Internal Server Error
Headers
  • Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source

Default Response

An error has occurred.
Headers
  • Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Body ()
Root Schema : Error
Type: object
The properties that define an error.
Show Source
Back to Top