vSphere Troubleshooting

-
CPU TROUBLESHOOTING
  1. If ready time <= 5%, there’s no problem.
  2. If ready time is 5% <=> 10%, there might be an issue.
  3. If ready time is => 10% there’s a performance issue.
  4. Check if the virtual machine’s CPU is not limited.
  5. Check if there’s CPU over commitment all the time, occasional spikes are no problem.
  6. If it’s an SMP virtual machine check if the application is multithreading and actually using the resources.
  7. If the ESX host is saturated reduce the number of virtual machines.

MEMORYTROUBLESHOOTING
  1. Be careful with setting virtual machine memory reservations. When memory is touched by the VM, the other virtual machines can’t use the memory anymore. Only configure what the virtual machine really needs.
  2. Don’t set memory limits, set an appropriate virtual machine memory size instead.
  3. Do not disable page sharing or the balloon driver. Ballooning is OK as long as the guest OS isn’t using it’s own page file for active memory swapping.
  4. The use of large pages results in reduced memory management overhead and can therefore increase hypervisor performance. But take into consideration that using large pages(2MB) TSP might not occur until memory over commitment is high enough to require the large pages to be broken into small pages.

STORAGE TROUBLESHOOTING
  1. If KAVG/cmd> 3 mSecor DAVG/cmd> 20 mSecthere might be a storage performance problem.
  2. Check alignment on the array, VMFS and in the guest OS.
  3. Monitor the number of reservation conflicts per second and be careful with snapshots.
  4. Pay attention to drive types, the more drives you use the more IOPS you will get.
  5. When creating an VMFS, give it the right size and keep in mind how many virtual machines you want to host on that datastore.
  6. When choosing a block size, stick to it.

 NETWORK TROUBLESHOOTING
  1. Enable PortFastmode for the physical switch ports facing the ESXiServer.
  2. Disable STP for the physical switch ports facing the ESX Server.
  3. Use the VMXNET3 virtual network card wherever possible.

 TROUBLESHOOTING TOOLS
  • Veeam Monitor
  • VMTurboWatchdog
  • QuestvFoglight
  • VKernel CapacityAnalyzer
  • VESI VMware Community PowerPack
  • VMware Health Check Analyzer
  • BoukeGroenescheij -> Graph-VM
  • Esxplotand perfmon
  • Rob de Veij -RVTools
  • XangatiforESX

Comments

Post a Comment

Popular posts from this blog

esxi-host-shows-disconnected-vmware

-
Symptom: The host and VMs in a vcenter server appears to be disconnected. Issue: The host and its corresponding vms could appear as disconnected due to issue with any of the following services. vpxa - a service which runs in the esxi host. This service communicates with vcenter server. hostd - core service which runs in the esxi host vpxd - a service which runs in the vcenter server which communicates with the vpxa Resolution: 1. Try to ping the ESXi host. This ensures that the host is reachable 2. Ensure you can login to the VMs remotely. This ensures that VMs in the host are working fine. 3. Try to login to the ESXi host using vsphere client. This ensures that the hostd services are running perfectly. If this step fails, restart the hostd service using putty. 4. If the above three steps worked fine for you, the issue would be with the vpxa or vpxd service. In that case, first try to restart the vpxa service in the host and if that didnot resol
Read more

ESXi : Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic0 is down

-
We had an issue suddenly getting an alert : Lost uplink redundancy on virtual switch "vSwitch0". Physical NIC vmnic0 is down. Affected portgroups:"vMotion", "Management Network". So as a troubleshooting Select the ESXi host effected Click on Configuration, Select Networking, Click on vSwitch0 Properties,Click on Network adapters Select on vmnic0, Click on remove, Click on Close Again Select Networking, Click on vSwitch0 Properties,Click on Network adapters, Click on Add, Select the vmnic0, Click on Next, Click on Next, Click on Finish Now Click on Ports tab of vSwitch Properties, Select on vMotion, Click on Edit, Click on NIC Teaming, Select on vmnic1, Click on Moveup button  to Active Adapters, Select on vmnic0, Click on Move Down to Standby Adapters, Click on OK Now Click on Ports tab of vSwitch Properties, Select on Management Network, Click on Edit, Click on NIC Teaming, Select on vmnic1, Click on Moveup button  to Active Adapters, Select o
Read more

Virtual machines appear as invalid or orphaned in vCenter Server

-
Symptoms Virtual Machines show as invalid or orphaned in vCenter Server Virtual Machines show as invalid or orphaned after a VMware High Availability (VMware HA) host failure occurs Virtual Machines show as invalid or orphaned after an ESX host comes out of maintenance mode Virtual Machines show as invalid or orphaned after a failed DRS migration Virtual Machines show as invalid or orphaned after a storage failure Virtual Machines show as invalid or orphaned after the connection is lost between the vCenter Server and the host where the virtual machine resides You see one or more of these errors when trying to start a virtual machine: Could not power VM, no swap file, failed to power on VM. VMControl error -11: No such virtual machine. A general system error occurred. The system returned on error. Communication with the virtual machine may have been interrupted In   C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log   file, you see entries similar to: [11916 error
Read more