A common first step in diagnosing storage issues within a virtualized environment is identifying which virtual workloads are connected to which storage devices. This common task can also be very time consuming and difficult as the complexity of your storage environment grows. Fortunately, there is now an easier way to map virtual machines to storage devices and it lives directly inside of vCenter Operations Manager (vCOps).
In fact, in the time it took you to read that first paragraph, you would already know the impacted virtual machines and their troublesome storage devices. Simply navigate to the NetApp Storage Topology dashboard in vCOps and locate your resources in the VMware on NetApp topology widget. Typically, a resource exhibiting undesired behavior will show as a non-green color in this widget.
Selecting a resource highlights the related devices across all of your storage layers — Datacenter, Host System, Virtual Machine, Datastore, Cluster, System, Aggregate, LUN, and Volume – for immediate root cause analysis.
In the image below note that clicking a VMware Virtual Machine highlights it’s corresponding NetApp LUN. From this point you are able to drill-down into either the LUN or the Virtual Machine to view details metrics, alerts, and topology.
The Blue Medora – VMware vCOps / vRealize Management Pack for NetApp Storage adds this detailed relationship mapping to vCOps for NetApp Systems, Aggregates, Volumes, LUNs, Storage Virtual Machines.