click to expand ...

Home
About SVA ... Contact us
Overview (all documents)
Product description
Services with BVQ
BVQ advantages
New functions and future plans
White papers
Downloads and releases
Users Manual and users guide
Further WIKI documents
Performance analysis and monitoring for IBM SVC and Storwize

 





It's easy and valuable to do BVQ for VMware analysis.

But is even more valuable if you can do True End to End analysis, which includes both VMware and Storage.


Here's an example:

We have the situation that a SVC volume (VDisk) suddenly shows high latencies.

Part of the analysis is now a storage analysis to find out what the reason for the high volume latency is. The other part of the analysis is to recognize which virtual machine is responsible for the high load.

This is the part of the analysis that will be described here:

To carry out this analysis, I have built a small favorite that allows me to do the same analysis for any other volume with the push of a button.
This favorite can also be easily used in any other BVQ  installation.

On the left side you can see the topology of the storage and VMware environment, in the form that the storage environment displays all volumes used by VMware.
You can see the volumes used by VMware and which virtual machines use these volumes. (small blocks in the volumes). The table shows the same information with more detail information.

  One volume was marked for analysis (orange)


At the top right you can see the data rate and the latency of the volume and at the bottom right the data rates of the virtual machines that use the volume. At 6pm there has been a sudden increase in load and latencies in the volume.

 In the lower window you can see which virtual machines were active at the same time. The responsible virtual machine is now easy to spot.


Steps to solve the problem

  1. It has to be found out why the storage responds to the higher load with this high latency. This is a standard storage analysis supported by BVQ.
  2. If the storage is overloaded, a decision must be made whether to move this virtual machine to another storage.
  3. If a SAN problem is detected, you can do a SAN analysis with the BVQ SAN extension.

 

  • No labels