| copyright | lastupdated | keywords | subcollection | ||
|---|---|---|---|---|---|
|
2024-09-13 |
troubleshooting, provisioning, question, problem |
loadbalancer-service |
{{site.data.keyword.attribute-definition-list}}
{: #load-balancer-provisioning-troubleshooting}
This topic provides information on common issues that you might encounter when creating a new instance of {{site.data.keyword.loadbalancer_full}}. {: shortdesc}
{: #insufficient-ip-addresses-in-your-subnet} {: troubleshoot} {: support}
{{site.data.keyword.loadbalancer_full}} requires at least two free IP addresses from its private subnet. In addition, if the load balancer is a public load balancer and the IBM system pool option is not used, then at least two free IP addresses are needed from your public subnet as well. This IP address requirement is not only required when you create a new load balancer, but also when performing maintenance on an existing load balancer.
{: #issues-with-firewalls-on-public-and-private-vlans} {: troubleshoot} {: support}
For more information, see IBM Cloud IP ranges.
{: #viewing-load-balancer-error-messages} {: troubleshoot} {: support}
To view error messages for your load balancer, follow these steps:
- Click the load balancer from the list page to view its details.
- Mouseover the error symbol next to the load balancer's status.
If the load balancer is in an ERROR state, it cannot be recovered and must be deleted.