Upload
sydney-rice
View
224
Download
2
Tags:
Embed Size (px)
Citation preview
Key Metric, Performance, and Capacity Monitoring Using Microsoft System Center 2012 R2 Operations ManagerRaymond Chou | MVP, vTSP
Understand Different Performance and Capacity Measurements for Hyper-VLook at scenarios to identify performance issuesUse System Center Operations Manager for centralized monitoring
Session Objectives
Monitoring Hyper-V Performance / Capacity
CPU
• Hyper-V Hypervisor Logical Processor
• Hyper-V Hypervisor Root Virtual Processor
• Hyper-V Hypervisor Virtual Processor
• Processor
Memory
• Hyper-V Hypervisor Partition
• Hyper-V Hypervisor Root Partition
• Hyper-V Dynamic Memory Balancer
• Hyper-V Dynamic Memory VM
• Memory\ Available Mbytes
• Memory\Pages/sec
Network
• Hyper-V Virtual Switch
• Hyper-V Legacy Network Adapter
• Hyper-V Virtual Network Adapter
• Network Interface
Storage
• Logical Disk• Hyper-V Virtual
IDE Controller• Hyper-V Virtual
Storage Device
Measure CPU Utilization across all nodes in the ClusterDetermine if failover scenarios are tolerable
Is Processing Power Enough?
Monitoring Hyper-V Performance / Capacity
CPU
• Hyper-V Hypervisor Logical Processor
• Hyper-V Hypervisor Root Virtual Processor
• Hyper-V Hypervisor Virtual Processor
• Processor
{LPTR} Measure guest operating system processor utilization [Hyper-V Hypervisor Logical Processor(_Total)\% Total Run Time]• Less than 60% consumed = Healthy• 60% - 89% consumed = Monitor or Caution• 90% - 100% consumed = Critical, performance will be
adversely affected
{VPTR} [\Hyper-V Hypervisor Virtual Processor(*)\%Guest Run Time]
Guest operating system processors do not have a set affinity to physical processors/cores
High LPTR = Too many VMs and Virtual Processors consumingLow LPTR, High VPTR = the VM needs more Virtual ProcessorsHigh LPTR, Low VPTR = Too many VPTR has been assigned
Interpreting the Values
Determine if failover scenarios are tolerableIs our Dynamic Memory enabled VMs optimized?Do we need more or faster performing Memory Chips?
Do we have enough Memory?
Monitoring Memory PerformanceMemory
• Memory\ Available Mbytes
• Memory\Pages/sec
• Measure available memory on the Hyper-V host operating system [Memory\Available Mbytes]• 50% of free memory available or more = Healthy• 25% of free memory available = Monitor• 10% of free memory available = Warning• Less than 5% of free memory available = Critical,
performance will be adversely affected
• Measure available memory on the Hyper-V host operating system [\Memory\Pages/sec ]• Less than 500 = Healthy• 500 - 1000 = Monitor or Caution• Greater than 1000 = Critical, performance will be
adversely affected
Monitoring Dynamic Memory PerformanceDynamic Memory
• Hyper-V Dynamic Memory Balancer
• Hyper-V Dynamic Memory VM
• Measure the available Dynamic Memory [Hyper-V Dynamic Memory Balancer\Available Memory]
• Measure the pressure of Memory Demand on the VM [Hyper-V Dynamic Memory Balancer\Average Pressure]• Under 100 = Healthy• Greater than 100 = Critical, performance will be
adversely affected
Network Utilization determines if you need to load balance across NICsFaulty network cards can be huge load contributor
Is the Network a bottleneck?
• Simple Network Tests• Test Network Latency – Ping
• Test Packet Loss – pathping
• Test Network File Transfers – Copy
Monitoring Physical Network Performance
Physical Network
• Hyper-V Virtual Switch
• Hyper-V Legacy Network Adapter
• Hyper-V Virtual Network Adapter
• Network Interface
• Packet Outbound/Inbound
Monitoring Physical Network Performance
Physical Network
• Hyper-V Virtual Switch
• Hyper-V Legacy Network Adapter
• Hyper-V Virtual Network Adapter
• Network Interface
• Packet Outbound/Inbound
• Network Utilization Monitoring: \Network Interface(*)\Bytes Total/sec
• Compare the result against the NIC capability• A 1GB NIC= 125 million Bytes/sec• A 10GB NIC = 1250 million Bytes/sec
• Less than 40% = Healthy• 41%-64% = Monitor or Caution• 65-100% = Critical, performance will be adversely
affected
Monitoring Physical Network Performance
Physical Network
• Hyper-V Virtual Switch
• Hyper-V Legacy Network Adapter
• Hyper-V Virtual Network Adapter
• Network Interface
• Packet Outbound/Inbound
• Bottlenecks: \Network Interface(*)\Output Queue Length • 0 = Healthy• 1-2 = Monitor or Caution• Greater than 2 = Critical, performance will be
adversely affected.
• MTU settings must be the same for ALL
Hyper-V Virtual Switch\Bytes/sec Amount of traffic that is flowing through that virtual switch
Hyper-V Virtual Network Adapter\Bytes/sec
Determine how much traffic is going through to the VM.
For Legacy Adapters, Hyper-V Legacy Network Adapter\Bytes sent/secHyper-V Legacy Network Adapter\Bytes Received/sec
Monitoring the Hyper-V Switch Layer
Physical Disk = physical hardwareLogical Disk = partitions / LUNs
Logical Disk or Physical Disk?
Which would you choose?
Monitoring Storage Throughput and IOPSStorage
• Logical Disk• Hyper-V Virtual
IDE Controller• Hyper-V Virtual
Storage Device
• Use Data Collector Sets• Measure Disk Latency –
• \Logical Disk(*)\Avg. sec/Read • \Logical Disk(*)\Avg. sec/Write
• Under Value of 0.015 sec (15ms) = Healthy• Between the Value of 0.015 and 0.025 sec (15ms –
25ms) = Monitor or Caution• Above the value of 0.026 sec (25ms) = Critical,
performance affected
• Logical Disk\Current Disk Queue Length
Sometimes we just don’t have the time…Use Quick ChecksCheck if all Integration Services is updatedWhere possible use the Synthetic Network CardCheck your Running Task List (Task Manager) and remove unneeded ServicesRemove unnecessary User SessionsUse Central Monitoring Tools
System Center Operations Manager 2012 R2
Using a Central Monitoring Tool
Centrally Monitor all Hyper-V Servers
Configure Alerts on Thresholds
Historical Reporting
Anti-Virus Exclusions MUST be setCheckpoints take up space. Manage it well.Manage Dynamic Memory Pressure extensively
General Tips
Hyper-V Management Pack Extensionshttp://hypervmpe2012.codeplex.com/
Powershell CMDLets for managing Hyper-Vhttp://technet.microsoft.com/en-us/library/hh848559(v=wps.620).aspx
Deciphering Performance Monitor Disk Counters
http://blogs.technet.com/b/askcore/archive/2012/03/16/windows-performance-monitor-disk-counters-explained.aspx
Measuring Disk Latencyhttp://blogs.technet.com/b/askcore/archive/2012/02/07/measuring-disk-latency-with-windows-performance-monitor-perfmon.aspx
Additional Resources
Monitoring Hyper-V Bloghttp://blogs.msdn.com/b/tvoellm/archive/2009/04/23/monitoring-hyper-v-performance.aspx
Monitoring Processor Utilizationhttp://blogs.technet.com/b/chrisavis/archive/2013/03/25/performance-management-monitoring-cpu-resources.aspx
Monitoring Network Interfacehttp://msdn.microsoft.com/en-us/library/ms803962.aspx
Monitoring Hyper-V WhitePaper (by Raymond Chou)
Releasing on 19th May 2014 @ http://mymomexperience.blogspot.com
Additional Resources
Come Visit Us in the Microsoft Solutions Experience!
Look for Datacenter and Infrastructure ManagementTechExpo Level 1 Hall CD
For More InformationWindows Server 2012 R2http://technet.microsoft.com/en-US/evalcenter/dn205286
Windows Server
Microsoft Azure
Microsoft Azurehttp://azure.microsoft.com/en-us/
System Center
System Center 2012 R2http://technet.microsoft.com/en-US/evalcenter/dn205295
Azure PackAzure Packhttp://www.microsoft.com/en-us/server-cloud/products/windows-azure-pack
Resources
Learning
Microsoft Certification & Training Resources
www.microsoft.com/learning
msdn
Resources for Developers
http://microsoft.com/msdn
TechNet
Resources for IT Professionals
http://microsoft.com/technet
Sessions on Demand
http://channel9.msdn.com/Events/TechEd
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.