5.1

3 Ensure that vmnic on virtual machine and vShield Edge is connected (vCenter > Virtual Machine > Edit
Settings > Network Adapter > Connected/Connect at Power On check boxes).
When both a vShield App and vShield Edge are installed on the same ESX host, disconnection of NICs
can occur if a vShield App is installed after a vShield Edge.
Load-Balancer Does Not Work
Procedure
1 Verify that the Load balancer is running by running the CLI command: show service lb.
Load balancer can be started by issuing the start command.
2 Verify the load-balancer configuration by running command: show configuration lb.
This command also shows on which external interfaces the listeners are running.
Load-Balancer Throws Error 502 Bad Gateway for HTTP Requests
This error occurs when the backend or Internal servers are not responding to requests.
Procedure
1 Verify that internal server IP addresses are correct.
The current configuration can be seen through the vShield Manager or through the CLI command show
configuration lb.
2 Verify that internal server IP addresses are reachable from the vShield Edge internal interface.
3 Verify that internal servers are listening on the IP:Port combination specified at the time of load balancer
configuration.
If no port is specified, then IP:80 must be checked. The internal server must not listen on only 127.0.0.1:80;
either 0.0.0.0:80 or <internal-ip>:80 must be open.
VPN Does Not Work
Procedure
1 Verify that the other endpoint of the tunnel is configured correctly.
Use the CLI command: show configuration ipsec
2 Verify that IPSec service is running on the vShield Edge.
To verify using the CLI command: show service ipsec. IPSec service has to be started by issuing the
start command.
If ipsec is running and any errors have occurred at the time of tunnel establishment, the output of show
service ipsec displays relevant information.
3 Verify the configuration at both ends (vShield Edge and remoteEnd), notably the shared keys.
4 Debug MTU or fragmentation related issues by using ping with small and big packet sizes.
n
ping -s 500 ip-at-end-of-the-tunnel
n
ping -s 2000 ip-at-end-of-the-tunnel
vShield Administration Guide
224 VMware, Inc.