Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Monitoring Performance on Netapp - VMware - very slow write and read from Datastore ?
2012-07-05
02:39 AM
6,253 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, how can I monitoring performance on Netapp when Vmware hosts read i write to/from datastore over FCP.
Last night all vm write and read very slow to/from datastores.
After a few minutes the situation returned to normal.
This situation appeared again.
Best Regards
Pawel
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
There are a few choices here:
Most of the OnCommand software is free now (it replaces Operations manager etc, also free from software downloads).
Performance and Statistics Collector (perfstat) from tool box utilities.
OnCommand system manager shows performance in real time.
SysStat from the filer command line (-f for for FCP specific info)
lun stats also from the command line (-o with -i or - c)
May be your fabric switches have monitoring options within them (our low end Brocades do)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The broader your monitoring, the better you are able to correlate issues.
In cases like this, you want to collect:
On the NetApp
- IOps per volume, and per aggregate
- latency per volume and per aggregate
- LUN queueing
- CPU, per CPU, FCP stats, etc.
- physical disk utilization
But you also want to get performance information from your fabric switches; from your ESX hosts (datastore latency from the point of view of the ESX host; total IOPs; IOps per virtual machine.)
Then you'll be able to see if:
- there was a latency issue on the datastore volume
- if so, was it due to IO load on that volume, or other volumes on the aggregate. Depending on the workload it could be the NetApp CPU, but that is unusual - much more likely IO's per spindle.
- if it was that datastore volume, was it due to some specific VM doing an unusual workload causing it?
- or possibly some issue in the fiber channel network
We use LogicMonitor to track all this stuff in one place
- there was a latency issue on the datastore volume on the NetApp
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Pawel,
Like Nigel said, there are a few ways of getting that information. I would also add the VMware vCenter Operations Manager Management Pack for NetApp Storage.
http://bluemedora.com/product/vcenter-operations-management-pack-netapp-storage
