VMworld 2015: How To Troubleshoot Using vRealize Operations Manager (Deep Live Demo)
•Download as PPTX, PDF•
0 likes•912 views
See how vRealize Operations Manager can help you to quickly isolate and troubleshoot "My VM is slow!" issues. We'll look at three real-world performance and capacity problems and demonstrate how to troubleshoot them using vRealize Operations Manager on a live environment with real infrastructure issues..
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (13)
Similar to VMworld 2015: How To Troubleshoot Using vRealize Operations Manager (Deep Live Demo)
Similar to VMworld 2015: How To Troubleshoot Using vRealize Operations Manager (Deep Live Demo) (20)
More from VMworld
More from VMworld (19)
Recently uploaded
Recently uploaded (20)
VMworld 2015: How To Troubleshoot Using vRealize Operations Manager (Deep Live Demo)
- 1. How to Troubleshoot Using vRealize Operations Manager (Deep Live Demo) Shyamal Patel, VMware, Inc Samuel McBride, VMware, Inc MGT4928 #MGT4928
- 2. • This presentation may contain product features that are currently under development. • This overview of new technology represents no commitment from VMware to deliver these features in any generally available product. • Features are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind. • Technical feasibility and market demand will affect final delivery. • Pricing and packaging for any new technologies or features discussed or presented have not been determined. Disclaimer CONFIDENTIAL 2
- 3. Agenda 1 Introduction to troubleshooting 2 Real World Troubleshooting Scenarios 3 Tech Preview 4 Q&A 3
- 4. How do Customers find problems in their infrastructure ? 4 Search for problem Phone call / support ticket Big Visual Blind Luck ! Start By vR Ops God ! Alerts/Notifications
- 5. How do customers solve Operational problems ? 5 ProactiveReactive Maturity index Intelligent Alerts vRealize Operations 6.1 • Detect complex issues from multiple symptoms • Remediation and automation engine • Scale-out, data-agnostic platform • Automation to achieve Self Healing DC Correlated Alerts 10x Incident Reduction Machine Learning Analytics ESX Top After Phone Call User Already Impacted Slow Remediation ESX Top per VM User Potentially Impacted Quicker Remediation Less False Alarms • Self-learning • Dynamic thresholds Basic Alerting Specific Problems
- 6. Agenda 6 1 Introduction to vRealize Operations Suite 2 Real World Troubleshooting Scenarios 3 Tech Preview 4 Q&A
- 7. Understanding the Data Presented by vROPs Search for problem Get a phone call / support ticket Big Visual
- 8. Understanding VM CPU Demand vs Usage vSphere Reported Cpu Usage What VM Got Right now Contention What VM Could not Get vROps Reported CPU Demand What VM wants If CPU Demand What VM wants Cpu Usage What VM Got Right now Performance ImpactVM Has Needs Troubleshooting
- 9. Troubleshooting Population Pressure Entitlement What VM can ever Get Cpu Usage What VM Got Right now Contention What VM Could not get HasIf VM Population Pressure Needs Move VM Add Physical Capacity
- 10. vR Ops 6.0 Out of Box Troubleshooting Memory CONFIDENTIAL 10 Allocation (No Overcommit) • Most Conservative • Configured Memory • Wasteful in non Production Env Usage (Active) • Most Aggressive • Current Active Demand Consumed (All Touched Bits) • vSphere reported • Moderate Approach • Java, SQL, Xchange Oracle VM • Memory Configured : 1GB • Memory Consumed : 721MB • Memory Demand : 292MB
- 11. Our Philosophy Is Not your Philosophy : Mem Consumed in 6.1 12 Total Memory Touched by VM vSphere vROps 6.1
- 12. Q&A Before and After Demo
- 13. Summary : What we achieved today ? • Troubleshooting maturity graph. • Understand core metrics to troubleshoot High CPU, Demand, Usage and Contention. • Top Models to calculate Memory and their uses. Introduction of Mem Consumed in 6.1. • Demo Showcasing real world troubleshooting : 3 tier application – User complaining the desktop was stuttering. – Application with high CPU affecting other VMs. – Disk I/O issues – Capacity Visual and its uses 14
- 14. Disclaimer • This presentation may contain product features that are currently under development • This overview of new technology represents no commitment from VMware to deliver these features in any generally available product • Features are subject to change, and must not be included in contracts, purchase orders, or sales agreements of any kind • Technical feasibility and market demand will affect final delivery • Pricing and packaging for any new technologies or features discussed or presented have not been determined 15
- 17. How to Troubleshoot Using vRealize Operations Manager (Deep Live Demo) Shyamal Patel, VMware, Inc Samuel McBride, VMware, Inc MGT4928 #MGT4928
Editor's Notes
- QQQ: Please raise your hand if you are searching for operational issues by Big Visuals or Alerts/Notifications ?
- QQQ : How many of you have creaed new alert or modified existing vROPs alerts ? PROS AND CONS --------------------------- Phone Call : Cost Benefit to IT by less tools but Cost to business is high. Basic Alerts : PRO simple to understand, machine alerting instead of human, can indicate problems ahead of time. CONS : noisy, False alerts, takes lot of time to investigate the reality of the alert. Correlated : Smarter alerts with reduction in number of alerts eg. Cpu is high and disk I/O high. Machine Learning : It knows behavior and patterns but it does not know good from bad. You are predictive but you are not sure if it is something that you need to react on or wake up to fix it. AL Based on ML : A Job runs every night for 4 hrs we can combine the expected behavior with the high to not alert the users and hence reduce # alerts and increase fidelity of the alerts.
- There are different resources that can be bottlenecks. Amount that you are provisioned is what you will ever get, what you want is demand. The amount that you actually got is usage ( hypervisor schedule ). Demand > Usage = Contention. Population pressure when Demand > Entitlement. Add Slide” CPU Demand workload page = Usage + Contention Usage is what you see in vsphere. But to troubleshoot Contention and Entitlement are important concepts and hence vROPs has to use them. Extension of vsphere numbers.
- There are different resources that can be bottlenecks. Amount that you are provisioned is what you will ever get, what you want is demand. The amount that you actually got is usage ( hypervisor schedule ). Demand > Usage = Contention. Population pressure when Demand > Entitlement. Add Slide” CPU Demand workload page = Usage + Contention Usage is what you see in vsphere. But to troubleshoot Contention and Entitlement are important concepts and hence vROPs has to use them. Extension of vsphere numbers.
- QQQ :How many of you do capacity and performance monitoring using memory consumed ( available in vsphere ) ??