サポートと今すぐチャット
サポートとのチャット

Foglight for Storage Management Shared 4.6 - User and Reference Guide

Getting Started Monitoring Storage Performance Investigating Storage Devices Investigating Storage Components Investigating VPLEX Storage Troubleshooting Storage Performance Managing Data Collection, Rules, and Alarms Understanding Metrics Online-Only Topics

Analyzing Storage Issues

If the view for a datastore or RDM disk extent shows the Attention icon, the troubleshooting algorithm has discovered evidence of a performance problem related to storage. The problem may or may not be in the SAN Storage environment. Review the details to determine the cause of the performance issue.

Each datastore/RDM view has three summary panels (from left to right):

A virtual machine may be connected to multiple datastores and RDM disk extents, each of which may report varying degrees of problems. When a virtual machine has more than one datastore/RDM view, start by scanning the timeline bars in the VM I/O to Datastore/RDM panel to identify a datastore/RDM with consistently slow I/O performance or significant changes from typical performance.

The following workflow describes one way to identify a latency problem in the collected SAN Storage environment. While the details in your investigation may differ, the general workflow should be similar to this one.

1
In a view showing the Attention icon, scan the VM I/O to Datastore/RDM summary (first panel). Look for timeline bars that primarily show colors such as yellow, orange, or pink, that is, any color other than green (which represents acceptable activity).
2
Now look at the Latency for Disk Extents summary (middle panel) to identify the disk extents that are contributing to the problem.
a
In the VM I/O to Datastore/RDM summary, click the Chart icon.
c
In the Latency for Disk Extents summary, click the Chart icon.
5
In the Diagnosis panel, click Analyze SAN Storage.

Analyzing the Pool

When pool timeline bars show abnormal average queue depth or ops rate, analyze the changes within the pool and the load on the pool.

Perform Pool Change Analysis. The Pool Change analyzer identifies the LUNs primarily responsible for increased I/O. It compares LUN activity in the problem time range with LUN activity during the same time range in the past. Changes are reported in terms of average operations rate and change amount.
Perform Pool Load Analysis. The Pool Load analyzer identifies the busiest LUNs and ranks them based on their activity during the same time range over the last 30 days (not the current time frame). Activity is measured in operations per second.
TIP: You can change the comparison time range by clicking Change and selecting a new date and time range.
3
Click Perform Pool Load Analysis.

Changing Latency Thresholds

One way Foglight for Storage Management determines if the performance problem is occurring in the SAN storage environment is to evaluate latency against the thresholds defined for latency in registry variables. The latency thresholds used for analysis are, by default, the same thresholds as are used for generating latency alarms. If you think it would be helpful to adjust the threshold values for your analysis, you can change the threshold values using the Storage Troubleshooting dashboard. The original registry variables are not updated.

3
Click Apply.

Understanding the Troubleshooting Algorithm

To determine if the problem is likely to be a storage performance problem, Foglight for Storage Management evaluates latency metrics against thresholds and typical performance, and disk extent metrics against the I/O being performed to the extent by the virtual machine. If the likely cause of the problem is slow performance in the SAN Storage environment, Foglight for Storage Management examines the LUN or NASVolume. If no circumstances, such as a rebuild, are identified as a cause of high latency, the pool is examined.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択