This section provides troubleshooting tips for NSX Advanced Load Balancer deployment into a VMware vCenter-managed cloud.

All Deployment Modes (Write or No access)

The following issues can occur in any deployment mode, namely, write or no access.

Issue

Resolution

Cannot Access Web Interface—Blank Page or 503 Status Code

The NSX Advanced Load Balancer Controller is still booting up. Wait for 5-10 minutes.

Cannot See SEs from NSX Advanced Load Balancer Controller

  • Ensure that the SE’s management interface is connected to the correct port group.

  • Verify that an IP address is assigned to the SE’s management interface.

Virtual Service Creation Fails

  • Verify whether the SEs are visible in the NSX Advanced Load Balancer Controller web management interface by navigating to Infrastructure > Cloud > Default Cloud > Service Engine.

  • If DHCP is used for assigning IP addresses to the SE interfaces, verify that the DHCP service is running correctly.

Write Access Mode

Issue

Resolution

NSX Advanced Load Balancer Controller Cannot Connect To vCenter

  • Verify the network connectivity between the NSX Advanced Load Balancer Controller and the vCenter.

  • Verify the vCenter credentials.

  • Verify no intervening infrastructure prevents NSX Advanced Load Balancer Controllers from accessing the desired ESXi hosts over port 443.

NSX Advanced Load Balancer Controller Does Not Spin Up an SE

  • Verify the network connectivity between the NSX Advanced Load Balancer Controller and the vCenter.

  • If vCenter cannot return an ESX host’s DNS name instead of its IP address to the NSX Advanced Load Balancer Controller, ensure that the NSX Advanced Load Balancer Controller is configured to use the correct DNS server.

  • Verify that the ESX hosts have adequate resources.

Virtual Service Creation Fails

  • Verify that the vCenter account specified in NSX Advanced Load Balancer for the cloud has privileges to create new folders in vCenter. This is required for virtual service creation.

  • Verify that the virtual service and server networks (port groups) are discovered with subnets by navigating to Infrastructure > Cloud > Default Cloud > Network.

  • If static IP addresses are used for SE interfaces, verify the IP address pool by navigating to Infrastructure > Cloud > Default Cloud > Network.

No Access Mode

Issue

Resolution

Virtual Service Creation Fails

  • Verify SE interface configuration by navigating to Infrastructure > Cloud > Default Cloud > Service Engine. Select an SE and click Edit. Verify that either DHCP is enabled or an IP address is assigned to the correct vNIC, by matching its MAC address to that of a connected network adapter on the SE VM.

  • In vCenter, ensure that the interfaces are correctly connected to port groups.