So I have vROps 6.6 installed and now I want the Service Discovery Management Pack working since it is the replacement for VMware Infrastructure Navigator that I was so fond of.
Before – Prep
The bits for that are here, and the release notes. The user guide can be found here. You need to have the bits handy to use for the install but there is no license that is needed. BTW, VMware tools need to be installed for this Service Discovery to work fully. But there are many other reasons though to have VMware Tools running!
You do need vROps 6.6 to be running!
Install / Configure
- You need to be working in the Administration / Solutions area.
- Use the green + under Solution to start.
- You browse out to the management pack.
- Use the upload button to upload the .pak file to the the appliance.
- Once uploaded then we need Next.
- The solution will take a little bit to install.
- Now the Service Discovery adapter is install but not quite ready.
- So now to configure. Highlight the Service Discovery solution and select the gear.
- Filling in most the Solution info is easy. I suggest Deep Discovery so you know the unknown services. Which in VIN were easy to deal with. Not sure here yet.
- The credential config is unexpectedly detailed.
- Enter in as much as you can. It looks like I need to read the manual with things like Guest User Mapping CSV Password and SRM fields.
- Once you fill in and do OK, and Save, and Close, you will see some action.
- So you can see that data collection is working so that is good. But it is better when it looks like below.
So now we have Service Discovery installed and working. Lets see what it can help us with.
What does it look like, and what does it show us?
I see a number of Service Discovery dashboards. Here is one – Virtual Machine Relationships.
In this case I selected my View server (broker). And it fills in the two widgets to the right. So much unknown service it is disheartening, I could have done the shallow discovery but I thought it would be easy to change an unknown service into a known one. The manual says it is easy but for some reason I cannot make it work.
Here is another in Service Relationships, where I highlighted an unknown service of udpforwarder on my VM Broker.
This shows a useful screen, but with so many unknown and no known services it means it is less then useful.
So far I am intensely disappointed. VIN was so easy to install, configure, and recognize services that it was a super useful tool. I think that this Service Discovery tool may turn out to be useful but I suspect a lot of work will be necessary.
I will keep working with it and see how it goes.
- 6/24/17 – It was suggested to use this article to help with troubleshooting. It is a pretty cool dashboard and is helpful. It did not solve my issues though. I cannot find menu options, and I see nothing recognized. But I have SQL servers, mail servers, View servers, vCenter, and more in this lab and some of it should be recognized I think. If anyone from VMware wants to look at my lab and help with this, I would most appreciate it.
=== END ===