08448380779 Call Girls In Civil Lines Women Seeking Men
VMware vSphere Performance Troubleshooting
1. vSphere Performance Monitoring and Troubleshooting Overview What? CPU, Memory, Disk, Network How? Use available tools and a systematic methodology Why? Need to build confidence in virtualizing critical and high demand applications
2. vSphere Performance Monitoring and Troubleshooting Top Issues Top Issues: Storage "performance capacity" oversubscription Memory oversubscription SMP overuse Firmware & driver issues
3. vSphere Performance Monitoring and Troubleshooting What tools do we have at our disposal? Top tools for information collection: vCenter - Performance charts and alarms Guest OS* - Task Manager/Resource Monitor and PerfMon ESX Host - esxtop and vscsiStats vSpherePowerCLI *Guest based monitoring is subject to inaccuracy
9. vSphere Performance Monitoring and Troubleshooting Prepare esxtop ESXTOP realtime monitoring: esxtop(run command from SSH or tech-support mode) s 2 (refresh view every 2 seconds) V (View VMs only) h(for quick in-tool command reference) Batch Mode for a 5 minute capture of all stats: esxtop-b -a -d 2 -n 150 > esxtop_capture.csv
10. vSphere Performance Monitoring and Troubleshooting Prepare PowerCLI Run PowerCLI: Tip: Run as Administrator Set-ExecutionPolicyremotesigned Connect-VIServer -Server <host> -Protocol https -User <user> -Password <pass> <host> can be IP address or name of ESX server or vCenter Get-VM Get-Stat -common -realtime
13. vSphere Performance Monitoring and Troubleshooting Network Troubleshooting Guidance: 1. Physical Issues - A bad cable, a failing switch port or NIC, or an incompatible/flawed firmware or device driver (use VMXNET3 whenever possible) 2. Configuration Issues - Inconsistent configuration of vSwitches, Port Groups, or upstream VLAN trunks 3. Capacity Issues - Too many VMs on a single NIC; inadequate switch backplane or uplink capacity; sharing “unmanaged” network infrastructure for storage and data 4. Thresholds – Bandwidth saturation, dropped packets
21. vSphere Performance Monitoring and Troubleshooting Network Possible resources for external monitoring: Native Telnet/SSH/HTTP-based interface counters and stats Third-party SNMP, NetFlow and ICMP tools
23. vSphere Performance Monitoring and Troubleshooting CPU Troubleshooting Guidance: 1. Physical Issues - Rare and always catastrophic (e.g. obvious) 2. Configuration Issues - Too many / too few vCPUs per VM; SMP/HAL mismatch; incorrect CPU affinity settings 3. Capacity Issues - CPU saturation at the guest or host level; CPU starvation due to high IO or other system level ops 4. Thresholds – Waiting for CPU cycles (due to co-scheduling, swapping, high IO)
34. vSphere Performance Monitoring and Troubleshooting CPU Possible resources for external monitoring: Vendor specific systems management tools, MS System Center, etc. http://www.peetersonline.nl/index.php/vmware/examine-vmware-cpu-ready-times-with-powershell/
44. vSphere Performance Monitoring and Troubleshooting Memory Possible external monitoring options: Vendor specific systems management tools, MS System Center, etc. Don’t forget vCenter ‘Hardware Status’ reporting
46. vSphere Performance Monitoring and Troubleshooting Storage Troubleshooting Guidance: 1. Physical Issues - A bad cable, a failing switch port or HBA/NIC, or an incompatible/flawed firmware or device driver (use LSI Logic Parallel/SAS as appropriate) 2. Configuration Issues - Inconsistent or incorrect configuration of LUN masking, zoning, or multi-pathing; inappropriate resource provisioning; aligning queue depth with storage type 3. Capacity Issues - Too many VMs or VMDKs on a LUN; too much IO load for an array or RAID group 4. Thresholds – Latency and queuing
65. vSphere Performance Monitoring and Troubleshooting Storage Possible external monitoring solutions: Vendor specific SAN and fabric/network tools, native Telnet/SSH/HTTP-based tools for most networks, third-party SNMP-based tools
66. vSphere Performance Monitoring and Troubleshooting Working with PowerCLI PowerCLI Tips: For a complete list of stat objects: Get-StatType -Entity <Host/VM> Pipe the outputs to a file: Get-Stat -stat <stat> -realtime | ft -autosize > c:emplt;filename>.csv Import the CSV file data to a spreadsheet with fixed width parameters Build pretty graphs
68. vSphere Performance Monitoring and Troubleshooting Way More Information ESXTOP / vscsiStats / PowerCLI: http://www.yellow-bricks.com/esxtop/ Special thanks to Duncan Epping! http://communities.vmware.com/docs/DOC-3930 http://communities.vmware.com/docs/DOC-9279 http://communities.vmware.com/docs/DOC-10095 http://www.vmware.com/support/developer/PowerCLI/PowerCLI41/html/Get-Stat.html http://www.lucd.info/2009/12/30/powercli-vsphere-statistics-part-1-the-basics/ http://simongreaves.co.uk/blog/esxtop-guide http://dunnsept.wordpress.com/2010/03/11/new-vscsistats-excel-macro/
69. vSphere Performance Monitoring and Troubleshooting Easy button? What is the problem with these tools? Limited alerting mechanisms, no collection automation or historical data for comparison, and no correlation of events! vCenter Operations Standard / Enterprise
Editor's Notes
Who uses Resource Pools? How many have reservations or limits?
Use a Host CPU stacked (per VM) graph to quickly identify leading consumers
Don’t necessary need CPU saturation for overcommit to have an effect on performance
Don’t necessary need CPU saturation for overcommit to have an effect on performance
Don’t necessary need CPU saturation for overcommit to have an effect on performance