Troubleshooting Topics

   (1)                                    Troubleshooting Issues
Issue Description:  Virtual machines fails to connect to the network.

Resolution (Steps taken to resolve issue)

 Ensure that the Port Group name(s) associated with the virtual machine's network

adapter(s) exists in your vSwitch or Virtual Distributed Switch and is spelled correctly. If

not, correct it using Edit Settings on the virtual machine and ensure that the

Connected checkbox is selected.

 Ensure that the virtual machine has no underlying issues with storage or it is not in

resource contention, as this might result in networking issues with the virtual machine.

 Verify that the virtual network adapter is present and connected.

 Verify that the networking within the virtual machine's guest operating system is

correct.

 Verify that the virtual machine's IPSec configuration is configured correctly and that it is

not corrupted

 If this virtual machine was converted from a physical system, verify that there are no

hidden network adapters present.

        

2.  Sev 2 :

Issue Description:  ESX host shows not responding / disconnected in Vcenter

Resolution (Steps taken to resolve issue):

  Verify that the ESXi host is in a powered ON state.

 Verify that the ESXi host can be reconnected, or if reconnecting the ESXi host resolves

the issue.

 Verify that the ESXi host is able to respond back to vCenter Server at the correct IP

address. If vCenter Server does not receive heartbeats from the ESXi host, it goes into

a not responding state.

 Verify that network connectivity exists from vCenter Server to the ESXi host with the IP

and FQDN.

 Verify if restarting the ESXi Management Agents resolves the issue

 Verify if the ESXi host has experienced a Purple Diagnostic Screen.

 Check if there are any issues from storage end.



3. Sev 2

Issue Description:  ESXi/ESX host disconnects from vCenter Server after adding or connecting it to the inventory

Resolution (Steps taken to resolve issue):

 Ensure that bidirectional heartbeat communications are functioning correctly.

 The default port for this communication is UDP 902, but be sure to verify the

configured port in the vpxa.cfg file on the host. This file also defines the IP address,

which manages the host.

Confirm vCenter Server managed IP address :

Confirm the vCenter Server managed IP address continuity throughout the environment.

 Determine the managed IP address of the vCenter Server:

a. Connect to vCenter Server with the vSphere Client.

b. Click Administration > vCenter Server Settings > Advanced Settings.

c. Make a note of the IP address in the ManagedIP row.

 Determine the IP address configured for vCenter Server:

For vCenter Server installed on a Windows Server:

a. From a console or RDP session to the vCenter Server desktop, open a

command prompt.

b. Run the command:

ipconfig

c. Make a note of the IP address and ensure that it matches the managed IP

address found in step 1.

For vCenter Server Appliance:

d. From a console or SSH session to the vCenter Server Appliance, open a shell

prompt.

Note: From the console of the vCenter Server Appliance, press enter on Login.

e. Run the command:

ifconfig

f. Make a note of the IP address next to inet addr: and ensure that it matches the

managed IP address found in step 1.

 Determine the IP address and port that the ESXi/ESX host is using for heartbeat traffic:

a. Connect to the ESXi/ESX host using the vSphere Client.

b. When the Warning pop-up appears, make a note of the IP address, which is

managing the host.

c. Connect to the same host using SSH.

d. Check the vpxa.cfg file for the heartbeat traffic port by running the command:

 On ESXi 5.x:

grep -i serverport /etc/vmware/vpxa/vpxa.cfg

 On ESXi/ESX 4.1 and earlier:

grep -i serverport /etc/opt/vmware/vpxa/vpxa.cfg

e. Ensure that the port number matches the default heartbeat port of 902.

f. Check the vpxa.cfg file for the managed IP address by running the command:

 On ESXi 5.x:

grep -i serverIp /etc/vmware/vpxa/vpxa.cfg

 On ESXi/ESX 4.1 and earlier:

grep -i serverIp /etc/opt/vmware/vpxa/vpxa.cfg.

4. Sev 3 :

Issue Description:  vMotion fails with Already disconnected or Timeout errors.
Resolution (Steps taken to resolve issue):

 The errors suggest that the destination host failed the vMotion prior to completion,

which is likely caused by network issues.

 Check for IP address conflicts on the vMotion network. Each host in the cluster should

have a vMotion vmknic, assigned a unique IP address.

 Check for packet loss over the vMotion network. Try having the source host ping

(vmkping) the destination host's vMotion vmknic IP address for the duration of the

vMotion.

 Check for the ability to pass traffic over the vMotion network. Consider whether jumbo

frames are enabled on the VMkernel port, NIC, and Switch. Consider whether a firewall

may be blocking vMotion traffic.

 Check that the virtual machine is running and responsive to input and that it is not

waiting for administrator interaction in vCenter Server.

 if the source host is heavily over committed, with slow or failing storage such that swap

I/O could be delayed significantly (minutes per I/O), the destination may give up on the

vMotion. This case is extremely rare and is visible mainly during storage failovers. If

this occurs, retry the operation when the source host is less overloaded.

Capture Results (Screen shots, logs, Server Details): NA

5. Sev 3

Issue Description:  The guest operating system boots slowly
Resolution (Steps taken to resolve issue):

 Check that VMware Tools is installed in the virtual machine and running the correct

version. The version listed in the toolbox application must match the version of the

product hosting the virtual machine.

 Review the virtual machine's virtual hardware settings and verify that you have

provided enough resources to the virtual machine, including memory and CPU

resources

 Ensure that any antivirus software installed on the host is configured to exclude the

virtual machine files from active scanning. Install antivirus software inside the virtual

machine for proper virus protection

 Check the storage sub-system on the host and verify that it is configured for optimal

performance.

 Verify that there are enough free resources on the host to satisfy the requirements of

the virtual machine.

 Verify that if there are any host networking issues impacting the performance of the

virtual machine

 Verify that the host operating system is working properly and is in a healthy state.

When the host is not working correctly it may draw excessive resources from the guests.