| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2020-06-29 |
load balancer, network, faqs, |
vpc |
{:shortdesc: .shortdesc} {:new_window: target="_blank"} {:codeblock: .codeblock} {:pre: .pre} {:note: .note} {:beta: .beta} {:screen: .screen} {:tip: .tip} {:note: .note} {:important: .important} {:download: .download} {:DomainName: data-hd-keyref="DomainName"} {:external: target="_blank" .external}
{: #nlb-faqs}
This section contains answers to some frequently asked questions about the {{site.data.keyword.cloud}} Network Load Balancer service. {: shortdesc}
The beta release of IBM Cloud Network Load Balancer is only available to allowlisted users. Contact your IBM Cloud Sales representative if you are interested in getting early access to this beta offering. When network load balancer is made generally available, you'll need to change to a Standard plan to continue using the instances you created during the Beta. Any instances that continue to use a Beta plan for this service beyond 30 days notice of general availability are deleted. See the {{site.data.keyword.cloud_notm}} Service Description{: external} and IBM VPC Service Description{: external} for more information about Beta services. {: beta}
{: #can-i-use-a-different-dns-name-for-my-load-balancer} {: faq}
The auto-assigned DNS name for the load balancer is not customizable. However, you can add a CNAME (Canonical Name) record that points your preferred DNS name to the auto-assigned load balancer DNS name. For example, if your load balancer in us-south has the ID dd754295-e9e0-4c9d-bf6c-58fbc59e5727, and the auto-assigned load balancer DNS name is dd754295-us-south.lb.appdomain.cloud, then your preferred DNS name is www.myapp.com. You can add a CNAME record (through the DNS provider that you use to manage myapp.com) pointing www.myapp.com to the load balancer DNS name dd754295-us-south.lb.appdomain.cloud.
{: #does-the-load-balancer-support-layer-7-switching} {: faq}
No. The network load balancer does not support Layer-7 switching.
{: #what-s-the-maximum-number-of-front-end-listeners-i-can-define-with-my-load-balancer} {: faq}
You can define a maximum of ten front-end listeners for a network load balancer.
{: #what-s-the-maximum-number-of-server-instances-i-can-attach-to-my-back-end-pool} {: faq}
You can attach a maximum of 50 virtual server instances to your back-end pool for a network load balancer.
{: #is-the-network-load-balancer-horizontally-scalable} {: faq}
No. A network load balancer is not horizontally scalable. However, it comes with a high-availability option and several different sizes (small, medium, and large), which allow you to select a network load balancer size that fits your performance needs.
{: #what-should-i-do-if-i-am-using-acls-on-the-subnets-that-are-used-to-deploy-the-load-balancer-nlb}
Make sure that the proper ACL rules are in place to allow incoming traffic for configured listener ports and management ports (ports in the range of 56500 - 56520). Traffic between a network load balancer and back-end instances should also be allowed.
{: #401-unauthorized-error} {: faq}
If you are receiving a 401 error code for your network load balancer, check the following access policies for your user:
- The access policy for the load balancer resource type
- The access policy for the resource group
{: #maintenance-pending} {: faq}
A network load balancer enters a maintenance_pending state during various maintenance activities, such as:
- Recovery activities
- Load balancer failover
- Upgrades to address vulnerabilities and apply security patches
{: #back-end-member-health-unknown} {: faq}
The pool might not associated with any listeners, or configuration changes were made to the pool or its associated listener.
{: #what-are-the-default-settings-and-allowed-values-for-health-check-parameters} {: faq}
The following default settings apply to network load balancer health check parameters:
- Health check interval: Five seconds, and the range is 2 - 60 seconds
- Health check response timeout: Two seconds, and the range is 1 - 59 seconds
- Maximum retry attempts: Two retry attempts, and the range is 1-10 retries
The health check response timeout value must be less than the health check interval value. {:tip}
{: #is-the-network-load-balancer-ip-address-fixed} {: faq}
Yes. The network load balancer IP address is fixed.