How to Get Average IOPS and Peak IOPS details from all Volumes

[Mamo2k21]

Hi All,

I have query, where I would like to get Average IOPS and Peak IOPS details from all Volumes frim Nimble HF40 using GUI or CLI?

We have a situation where few of the Datastores on the VMware Host is getting timeout and getting disconnected everyday at  23:15 IST and the volumes would conntect back after couple of seconds to minute.  hence I would like to query the PeakIOPs as attached from the screeshot

[Mahesh202 · Accepted solution]

Hi Mamo2k21

To get the average and peak IOPS details for all volumes on a Nimble HF40 array, you can use the Nimble Storage GUI or CLI.

Using the GUI:

1. Log in to the Nimble Storage GUI.
2. Select the "Volumes" tab from the navigation menu on the left.
3. In the volumes list, select all volumes by clicking the checkbox next to "Name" at the top of the column.
4. Click the "Actions" dropdown at the top of the list and select "Performance Chart" to open the performance chart for all selected volumes.
5. In the performance chart, you can view the average and peak IOPS for each volume over a specified time, period. You can adjust the time, period by selecting the dropdown at the top right of the chart.

Using the CLI:

1. Log in to the Nimble Storage CLI.
2. Run the command "vol --list" to get a list of all volumes on the array.
3. Run the command "vol --perf --vol-name <volume-name> --start-time <start-time> --end-time <end-time>" for each volume, replacing <volume-name> with the name of the volume and <start-time> and <end-time> with the time range you want to query. This command will return the average and peak IOPS for the specified volume during the specified time range.

To investigate the VMware datastore timeouts, you can use the Nimble Storage GUI or CLI to view performance metrics for the affected volumes during the time of the timeouts. Look for spikes in IOPS or latency that could indicate performance issues. You can also check the Nimble Storage event logs for any alerts or messages related to the timeouts. Additionally, check the VMware event logs to see if there are any errors or warnings related to the affected datastores.

Hope this helps.!!

Regards
Mahesh.