VM Monitoring by eG Key Differentiators June 16, 2010 VDI Architecture – VMware Silos Silo 1 Silo 2 Silo 3 Silo 4 Silo 5
VM Monitoring by eG Key Differentiators June 16, 2010 VDI Architecture – Microsoft Silos Silo 1 Silo 3 Silo 2 Silo 4 Silo 5 Silo 6 Silo 7
June 16, 2010 Monitoring Silos Doesn’t Work End User Client Admin LAN Admin Firewall/Network admin Server admin VMware admin Domain admin PC Admin Broker admin Application Admin Database Admin Hey, this is not working Siloed organizations result in the “It’s not me!” syndrome The server is working OK No other complaints All lights Are green We don’t see anything wrong VMs are lightly loaded Everything Is OK Not our problem Looks fine Not mine either Talk to the other guys
The Real Cost of Silo Monitoring Each MOT (moment of truth is also a silo) is indicated by a red box – The more silos you have, the more time it takes to manually triage a problem. Time is money…!
Save Time – Save Money As illustrated in the two figures, 14 interactions vs. 3 interactions – Before automation vs. after automation.
NETWORK MANAGER SILO VM Servers Application Server Application Server Database Server Firewall Load Balancer DNS Independent monitoring of individual applications Status of network elements, bandwidth utilization, etc. <ul><li>Holistic view of the end user service </li></ul><ul><li>Correlation across network, server, desktop, & application for problem diagnosis </li></ul>Automated End-to-End Service Monitoring SERVICE MANAGER APPLICATION MANAGER SILO VDI Service Monitoring eliminates finger pointing!
eG’s Key Differentiators Monitoring VDI Environments June 16, 2010
June 16, 2010 VDI Monitoring Needs <ul><li>Total end to end visibility into your VDI environment </li></ul><ul><ul><li>Which users are logged in? What applications are they accessing? </li></ul></ul><ul><ul><li>Who are the resource intensive users? </li></ul></ul><ul><ul><li>What latencies are they seeing? </li></ul></ul><ul><ul><li>Is user load balanced across the servers? </li></ul></ul><ul><li>Ability to quickly pin-point where the bottlenecks are </li></ul><ul><ul><li>Network? Server? VM? Broker? Application? Disk? </li></ul></ul><ul><ul><li>Contention among guests for needed resources? </li></ul></ul><ul><li>Flexible management reporting </li></ul><ul><ul><li>C-level reports </li></ul></ul><ul><ul><li>Usage reports </li></ul></ul><ul><ul><li>Capacity planning / optimization reports </li></ul></ul><ul><ul><li>Collection of chargeback metrics </li></ul></ul><ul><li>Should be easy to deploy, excellent ROI </li></ul><ul><ul><li>Out-of-the-box capabilities </li></ul></ul><ul><ul><li>Little customization needed </li></ul></ul><ul><ul><li>Minutes to install, fine-tune in hours </li></ul></ul><ul><ul><li>Don’t need experts to use the technology </li></ul></ul>
VDI Monitoring Challenges Excessive disk reads by the user running MS Access slows down accesses for the user running Outlook & Word processing Multi-tier infrastructures are difficult to manage . Adding VMs to the mix makes the problem even harder!!! Disk reads MS Access Outlook , Word Processing
VDI Monitoring Challenges <ul><li>Not feasible to deploy an agent per OS / VM </li></ul><ul><ul><li>Higher deployment overhead, time-consuming </li></ul></ul><ul><ul><li>Higher licensing cost </li></ul></ul><ul><ul><li>Higher resource consumption </li></ul></ul><ul><li>Different requirements for monitoring application server and virtual desktops </li></ul>Application servers hosted on VMware Desktops hosted on VMware Few VMs (<10) per ESX server 30-40 VMs per ESX server VMs mostly powered on all the time VMs powered on/off dynamically In-depth application monitoring required (Citrix, Oracle, etc.) Monitor user activity, access patterns
Case Study <ul><li>Target Environment & Objectives </li></ul><ul><li>Scope </li></ul><ul><li>A VDI environment with 750 Desktops. </li></ul><ul><li>Objectives </li></ul><ul><li>Total visibility into their VDI infrastructure </li></ul><ul><li>Users were constantly complaining of performance issues and fingers were being pointed at the virtualization group, the customer wanted to get the right information on where the issues were. </li></ul><ul><li>Compare demand on the infrastructure to resource consumption </li></ul><ul><li>Automatic Baselining of Key Performance Measurements – The ability to learn the norm of an environment automatically based on the data collected over a period of time. </li></ul><ul><li>Capacity Planning Reports </li></ul><ul><li>Pro-actively isolate and alert on issues within desktops. </li></ul>
VDI Latency The average network latency experienced by user desktops hosted on the ESX servers is between 0.01 and 0.05 secs.
ESX – CPU Utilization We can see different Virtual Guests executing on ESX server SCD2VMH516 have reported of High Ready % - This could mean that there might be an CPU bottleneck caused by some process on the Console OS or could be an application on the Virtual Machines taking too many CPU Cycles to execute…
Load Balancing in the VDI Farm There are between 28 and 30 registered Guests per VDI server.
ESX – VDI User Load Report The ESX VDI servers with Maximum number of users (26) are SCD2VMH512,SCH2VMH513 SCH2VMH517 and SCH2VMH200. Even though there are around 28 registered guests, There are few servers with very less number of users namely SELGVMH202, SNRMVH201 and SSPRVMH201
VDI Servers Memory Utilization Each of the 25 ESX servers have more than 16 GB of Memory allocated to them. This chart shows the Non-Kernel Memory usage of the ESX servers. Non-Kernel Memory is the that part of Memory allocated to Virtual Guests. This chart shows the Free Memory available at the ESX Host level after allocating resources to all the Virtual Machines. We can see that the SCD2VMH ESX servers have lower free memory when compared to the rest of the servers.
Identifying Resource Hogs The user colvtw is seen taking nearly 100% CPU for 30 minutes on Virtual Machine VFREVM1025. This virtual Machine is part of ESX server SFREVMH202
Identifying Resource Hogs The user colvtw is accessing MSACCESS application on Virtual Machine VFREVM1025 which is consuming nearly 100% CPU on the Virtual Machine.
Case Study - Summary <ul><li>eG Enterprise was implemented in one afternoon. </li></ul><ul><li>eG was able to identify configuration issues that helped the customer prevent potential scalability and performance issues. </li></ul><ul><li>eG provided end-to-end visibility into the target infrastructure that enabled the customer to keep track of all their important service level parameters. </li></ul><ul><li>eG was routinely able to isolate issues that could potentially affect the entire environment and pro-actively identify the root cause. This helped the customer to focus on where the real issues where and fix them and saved the virtualization team from being unnecessarily blamed. </li></ul><ul><li>eG helped the customer understand the demand on the target infrastructure and the amount of hardware resources consumed to service that demand. </li></ul><ul><li>eG provided an in-depth view of each and every desktop that helped the customer teams to service the support calls effectively. The ability to provide this information without an agent on the client was important to the customer </li></ul>
A particular slide catching your eye?
Clipping is a handy way to collect important slides you want to go back to later.