Before playing with the software, I recommend that you review the powerpoint files first. You will find them listed under Resources in this page. The slides (in PDF format) is not based on the vRealize Operations 6.0 release, but it still contains a lot of useful information. It will be useful for you to read them before reading my blog, as mine is based on the 6.0 release.
With a management pack, we certainly expect deeper visibility. There are many things that a VMware admin would love to see from their storage. Often, all they know is the LUNs. What’s backing up those LUNs are not exposed. For example, on the following screenshot you can see that it shows the number of systems I have. For each system, it shows the NetApp aggregate, volume, etc. The Environment tab shows the relationship. Notice I selected a Datastore. The VMs are highlighted, but the LUN is not. Can you guess why?
You are right, it’s an NFS. I have 4 datastores, and 1 of them is an NFS.
I like the way it’s structured like the above. It’s easy for me to understand the structure, hierarchy and dependancy. You can even see the VM in the datastore, as shown below.
On the screen below, I clicked a LUN. All the associated Datastores, VM, etc are shown. If your Datastores and LUN are not mapped 1:1, they will be visible here. Relevant information is also shown if you do a mouse-over on an object.
If you click the Map sub tab, you get something like this. This is another visualisation, which some of you may like. Personally, I’d like to see the volume put under the Aggregate, not at the same level.
You might be wondering, where are the disks? It’s storage after all 🙂 Well, they are now shown. I did not know that the default setting does not include Disk.
What you need to do is to go the Advanced Settings, as shown below, and choose the collection you want. I set mine to all as you can see below.
I like the screen below. It’s one of the default dashboards that come with it. It gives me a good overall summary. I do not have the performance data, which I’m checking with the folks at Blue Medora.
My first impression is this delivers the visibility that VMware admin often do not have access too. Cool stuff!