ListNetworkLoadBalancers
get
/20200501/networkLoadBalancers
Retrieves a list of all network load balancers in a compartment.
Request
Supported Media Types
- application/json
Query Parameters
-
compartmentId(required): string
Minimum Length:
1
Maximum Length:255
The OCID of the compartment. -
displayName: string
Minimum Length:
1
Maximum Length:255
A filter to return only resources that match the entire display name given. -
lifecycleState: string
A filter to return only resources that match the given lifecycle state.Allowed Values:
[ "CREATING", "UPDATING", "ACTIVE", "DELETING", "DELETED", "FAILED" ]
-
limit: integer
Minimum Value:
1
Maximum Value:1000
For list pagination. The maximum number of results per page, or items to return in a paginated List call. 1 is the minimum, 1000 is the maximum.Default Value:100
-
page: string
Minimum Length:
1
Maximum Length:512
For list pagination. The value of the opc-next-page response header from the previous List call.Default Value:oracle.doceng.json.BetterJsonNull@2c07545f
-
sortBy: string
The optional field to sort the results by.Default Value:
NAME
Allowed Values:[ "ID", "NAME", "TIME_CREATED" ]
-
sortOrder: string
The sort order to use, either ascending (ASC) or descending (DESC).Allowed Values:
[ "ASC", "DESC" ]
Header Parameters
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Response
Supported Media Types
- application/json
200 Response
A page of network load balancer objects.
Headers
-
opc-next-page: string
For list pagination. When this header appears in the response, additional pages of results remain. Use this value as the page parameter to get the next page of items.
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Root Schema : NetworkLoadBalancerCollection
Type:
object
Wrapper object for an array of NetworkLoadBalancerSummary objects.
Show Source
-
items:
array items
Array of NetworkLoadBalancerSummary objects.
Nested Schema : items
Type:
array
Array of NetworkLoadBalancerSummary objects.
Show Source
-
Array of:
object NetworkLoadBalancerSummary
Network load balancer object to be used for list operations.
Nested Schema : NetworkLoadBalancerSummary
Type:
object
Network load balancer object to be used for list operations.
Show Source
-
backendSets:
object backendSets
Additional Properties Allowed: BackendSetBackend sets associated with the network load balancer.
-
compartmentId(required):
string
The OCID of the compartment containing the network load balancer.
-
definedTags:
object definedTags
Additional Properties Allowed: additionalPropertiesDefined tags for this resource. Each key is predefined and scoped to a namespace. Example: {"Operations": {"CostCenter": "42"}}
-
displayName(required):
string
A user-friendly name, which does not need to be unique, and can be changed.
-
freeformTags:
object freeformTags
Additional Properties Allowed: additionalPropertiesFree-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. Example: {"Department": "Finance"}
-
id(required):
string
The OCID of the network load balancer.
-
ipAddresses(required):
array ipAddresses
Unique Items Required:
true
An array of IP addresses. -
isPreserveSourceDestination:
boolean
Default Value:
false
When enabled, the skipSourceDestinationCheck parameter is automatically enabled on the load balancer VNIC. Packets are sent to the backend set without any changes to the source and destination IP. -
isPrivate:
boolean
Default Value:
true
Whether the network load balancer has a virtual cloud network-local (private) IP address. If "true", then the service assigns a private IP address to the network load balancer. If "false", then the service assigns a public IP address to the network load balancer. A public network load balancer is accessible from the internet, depending the security list rules for your virtual cloudn network. This value is true by default. Example: true -
lifecycleDetails:
string
A message describing the current state in more detail. For example, can be used to provide actionable information for a resource in Failed state.
-
lifecycleState(required):
string
Allowed Values:
[ "CREATING", "UPDATING", "ACTIVE", "DELETING", "DELETED", "FAILED" ]
The current state of the network load balancer. -
listeners:
object listeners
Additional Properties Allowed: ListenerListeners associated with the network load balancer.
-
networkSecurityGroupIds:
array networkSecurityGroupIds
Maximum Number of Items:
5
An array of network security groups OCIDs associated with the network load balancer. During the creation of the network load balancer, the service adds the new load balancer to the specified network security groups. The benefits of associating the network load balancer with network security groups include: - Network security groups define network security rules to govern ingress and egress traffic for the network load balancer. - The network security rules of other resources can reference the network security groups associated with the network load balancer to ensure access. Example: ["ocid1.nsg.unique_ID"] -
nlbIpVersion:
string
Default Value:
IPV4
Allowed Values:[ "IPV4", "IPV4_AND_IPV6" ]
IP version associated with the NLB. -
subnetId(required):
string
The OCID of the subnet in which the network load balancer is spawned."
-
systemTags:
object systemTags
Additional Properties Allowed: additionalPropertiesKey-value pair representing system tags' keys and values scoped to a namespace. Example: {"bar-key": "value"}
-
timeCreated(required):
string(date-time)
The date and time the network load balancer was created, in the format defined by RFC3339. Example: 2020-05-01T21:10:29.600Z
-
timeUpdated:
string(date-time)
The time the network load balancer was updated. An RFC3339 formatted date-time string. Example: 2020-05-01T22:10:29.600Z
Nested Schema : backendSets
Type:
object
Additional Properties Allowed
Show Source
-
object BackendSet
The configuration of a network load balancer backend set. Avoid entering confidential information when you supply string values using the API.
Backend sets associated with the network load balancer.
Nested Schema : definedTags
Type:
object
Additional Properties Allowed
Show Source
-
object additionalProperties
Additional Properties Allowed: additionalPropertiesKey-value pair representing a defined tag key and value, scoped to a namespace.
Defined tags for this resource. Each key is predefined and scoped to a namespace. Example: {"Operations": {"CostCenter": "42"}}
Nested Schema : freeformTags
Type:
object
Additional Properties Allowed
Show Source
Free-form tags for this resource. Each tag is a simple key-value pair with no predefined name, type, or namespace. Example: {"Department": "Finance"}
Nested Schema : ipAddresses
Type:
array
Unique Items Required:
true
An array of IP addresses.
Show Source
-
Array of:
object IpAddress
A load balancer IP address.
Nested Schema : listeners
Type:
object
Additional Properties Allowed
Show Source
Listeners associated with the network load balancer.
Nested Schema : networkSecurityGroupIds
Type:
array
Maximum Number of Items:
5
An array of network security groups OCIDs associated with the network load balancer. During the creation of the network load balancer, the service adds the new load balancer to the specified network security groups. The benefits of associating the network load balancer with network security groups include: - Network security groups define network security rules to govern ingress and egress traffic for the network load balancer. - The network security rules of other resources can reference the network security groups associated with the network load balancer to ensure access. Example: ["ocid1.nsg.unique_ID"]
Show Source
-
Array of:
string
Minimum Length:
1
Maximum Length:255
Nested Schema : systemTags
Type:
object
Additional Properties Allowed
Show Source
-
object additionalProperties
Additional Properties Allowed: additionalPropertiesThe value of the tag. Only string, integer and boolean types are supported.
Key-value pair representing system tags' keys and values scoped to a namespace. Example: {"bar-key": "value"}
Nested Schema : BackendSet
Type:
object
The configuration of a network load balancer backend set. Avoid entering confidential information when you supply string values using the API.
Show Source
-
backends:
array backends
Unique Items Required:
true
Array of backends. -
healthChecker(required):
object HealthChecker
The health check policy configuration.
-
ipVersion:
string
Default Value:
IPV4
Allowed Values:[ "IPV4", "IPV6" ]
IP version associated with the backend set. -
isPreserveSource:
boolean
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. -
name(required):
string
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.
-
policy:
string
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
Array of backends.
Show Source
-
Array of:
object Backend
The configuration of a backend server that is a member of a network load balancer backend set.
Nested Schema : HealthChecker
Type:
object
The health check policy configuration.
Show Source
-
intervalInMillis:
integer(int32)
The interval between health checks, in milliseconds. The default value is 10000 (10 seconds).
-
port:
integer(int32)
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: 8080Example:
8080
-
protocol(required):
string
Allowed Values:
[ "HTTP", "HTTPS", "TCP", "UDP" ]
The protocol the health check must use; either HTTP or HTTPS, or UDP or TCP. -
requestData:
string(byte)
Base64 encoded pattern to be sent as UDP or TCP health check probe.
-
responseBodyRegex:
string
A regular expression for parsing the response body from the backend server. Example: ^((?!false).|\s)*$
-
responseData:
string(byte)
Base64 encoded pattern to be validated as UDP or TCP health check probe response.
-
retries:
integer(int32)
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.
-
returnCode:
integer(int32)
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:
0
-
timeoutInMillis:
integer(int32)
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).
-
urlPath:
string
The path against which to run the health check. Example: /healthcheck
Nested Schema : Backend
Type:
object
The configuration of a backend server that is a member of a network load balancer backend set.
Show Source
-
ipAddress:
string
The IP address of the backend server. Example: 10.0.0.3
-
ipVersion:
string
Default Value:
IPV4
Allowed Values:[ "IPV4", "IPV6" ]
IP version associated with the Backend object. -
isBackup:
boolean
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 -
isDrain:
boolean
Default Value:
false
Whether the network load balancer should drain this server. Servers marked isDrain receive no incoming traffic. Example: false -
isOffline:
boolean
Default Value:
false
Whether the network load balancer should treat this server as offline. Offline servers receive no incoming traffic. Example: false -
name:
string
A read-only field showing the IP address/IP OCID and port that uniquely identify this backend server in the backend set. Examples: 10.0.0.3:8080 or ocid1.privateip..unique_ID:443 or 10.0.0.3:0
-
port(required):
integer(int32)
The communication port for the backend server. Example: 8080
-
targetId:
string
The IP OCID/Instance OCID associated with the backend server. Example: ocid1.privateip.unique_ID
-
weight:
integer(int32)
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.
Nested Schema : additionalProperties
Type:
object
Additional Properties Allowed
Show Source
-
object additionalProperties
The value of the tag. Only the string type is supported.
Key-value pair representing a defined tag key and value, scoped to a namespace.
Nested Schema : additionalProperties
Type:
object
The value of the tag. Only the string type is supported.
Nested Schema : IpAddress
Type:
object
A load balancer IP address.
Show Source
-
ipAddress(required):
string
An IP address. Example: 192.168.0.3
-
ipVersion:
string
Default Value:
IPV4
Allowed Values:[ "IPV4", "IPV6" ]
IP version associated with this IP address. -
isPublic:
boolean
Whether the IP address is public or private. If true, then the IP address is public and accessible from the internet. If false, then the IP address is private and accessible only from within the associated virtual cloud network.
-
reservedIp:
object ReservedIP
An object representing a reserved IP address to be attached or that is already attached to a network load balancer.
Nested Schema : ReservedIP
Type:
object
An object representing a reserved IP address to be attached or that is already attached to a network load balancer.
Show Source
-
id:
string
OCID of the reserved public IP address created with the virtual cloud network. Reserved public IP addresses are IP addresses that are registered using the virtual cloud network API. Create a reserved public IP address. When you create the network load balancer, enter the OCID of the reserved public IP address in the reservedIp field to attach the IP address to the network load balancer. This task configures the network load balancer to listen to traffic on this IP address. Reserved public IP addresses are not deleted when the network load balancer is deleted. The IP addresses become unattached from the network load balancer. Example: "ocid1.publicip.unique_ID"
Nested Schema : Listener
Type:
object
The congfiguration of the listener.
Show Source
-
defaultBackendSetName(required):
string
The name of the associated backend set.
-
ipVersion:
string
Default Value:
IPV4
Allowed Values:[ "IPV4", "IPV6" ]
IP version associated with the listener. -
name(required):
string
A friendly name for the listener. It must be unique and it cannot be changed.
-
port(required):
integer(int32)
The communication port for the listener. Example: 80Example:
0
-
protocol(required):
string
Allowed Values:
[ "ANY", "TCP", "UDP", "TCP_AND_UDP" ]
The protocol on which the listener accepts connection requests. For public network load balancers, ANY protocol refers to TCP/UDP. For private network load balancers, ANY protocol refers to TCP/UDP/ICMP (note that ICMP requires isPreserveSourceDestination to be set to true). To get a list of valid protocols, use the ListNetworkLoadBalancersProtocols operation. Example: TCP
Nested Schema : additionalProperties
Type:
object
Additional Properties Allowed
Show Source
-
object additionalProperties
The value of the tag. Only the String type is supported.
The value of the tag. Only string, integer and boolean types are supported.
Nested Schema : additionalProperties
Type:
object
The value of the tag. Only the String type is supported.
400 Response
Bad Request
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Root Schema : Error
Type:
object
The properties that define an error.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing..Example:
UnknownError
-
message(required):
string
A human-readable error string.Example:
error validating payload
401 Response
Unauthorized
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Root Schema : Error
Type:
object
The properties that define an error.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing..Example:
UnknownError
-
message(required):
string
A human-readable error string.Example:
error validating payload
404 Response
Not Found
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Root Schema : Error
Type:
object
The properties that define an error.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing..Example:
UnknownError
-
message(required):
string
A human-readable error string.Example:
error validating payload
409 Response
Conflict
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Root Schema : Error
Type:
object
The properties that define an error.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing..Example:
UnknownError
-
message(required):
string
A human-readable error string.Example:
error validating payload
412 Response
Precondition Failed
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Root Schema : Error
Type:
object
The properties that define an error.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing..Example:
UnknownError
-
message(required):
string
A human-readable error string.Example:
error validating payload
429 Response
Too Many Requests
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Root Schema : Error
Type:
object
The properties that define an error.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing..Example:
UnknownError
-
message(required):
string
A human-readable error string.Example:
error validating payload
500 Response
Internal Server Error
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Root Schema : Error
Type:
object
The properties that define an error.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing..Example:
UnknownError
-
message(required):
string
A human-readable error string.Example:
error validating payload
Default Response
Unknown Error
Headers
-
opc-request-id: string
Unique Oracle-assigned identifier for the request. Provide this request OCID if you need to contact Oracle about this request.
Root Schema : Error
Type:
object
The properties that define an error.
Show Source
-
code(required):
string
A short error code that defines the error, meant for programmatic parsing..Example:
UnknownError
-
message(required):
string
A human-readable error string.Example:
error validating payload