I mentioned that VMware Infrastructure Navigator (VIN) was part of the vRealize family and that I liked it, and someone asked me why. I never got to demo for him why but I realized that I have been asked this before and that VIN is not nearly as common as it should be.
So here we go.
Note how when the host is highlighted that you can see the number of application servers and what application types that are running on that host.
When the cluster is highlighted we get quite a different view of the applications that are running. Quite a few in fact.
We have the cluster VIN info shown now but with Application server and Virtualization Management expanded so you see a little more information on the applications running.
You can see the VIN info for the VM bosad01 which is a domain controller. We can see that it has 22 dependencies.
We can see that this View server (bosbroker) has 12 dependencies.
We change to the Manage tab for the VM, and select Application Dependencies. While it is hard to read this screen we have a very good idea of what it is dependent on it. Plus we can even see version info on one of the servers that is in the diagram. And of course we can zoom in.
We can now start to read what some of the dependencies are. Like AD, and vCenter.
I think that these screenshots show the value of VIN. But here is what I like about it:
- I can see before I turn off a VM what is dependent on it – so I know what I am impacting.
- I can see what is the applications running on the VM, host, or cluster.
- I can see what makes up an application, so that means I know what needs to be ‘packaged’ with it to be protected with Site Recovery Manager.
So I hope that this shows you why you should have VIN running. Remember that if you own the vRealize Suite you own VIN. But likely not many people have suggested you run it – so I am now!
=== END ===