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

All Deployment Modes (Write or No Orchestrator)

The following issues can occur in any deployment mode, namely, Write or No Orchestrator mode.

Issue

Resolution

Cannot Access Web Interface—Blank Page or 503 Status Code

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

Cannot see SEs from Avi 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 Avi Load Balancer Controller web management interface by navigating to Infrastructure > Cloud Resources > 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

Avi Load Balancer Controller Cannot Connect To vCenter

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

  • Verify the vCenter credentials.

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

Avi Load Balancer Controller Does Not Spin Up an SE

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

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

  • Verify that the ESXi hosts have adequate resources.

Virtual Service Creation Fails

  • Verify that the vCenter account specified in Avi 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 Resources > Networks.

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

No Orchestrator Mode

Issue

Resolution

Virtual Service Creation Fails

  • Verify SE interface configuration by navigating to Infrastructure > Cloud Resources > 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.