Important Note – I have not been fully successful installing this MP – twice. I have deleted vROps and started over again from scratch and no luck. VMware support has been wonderful help but we still have not been able to make it work. I have stopped working on it until a new release comes out. I can also say I am not the only one with this issue.
So I have vROps 6.7 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 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.1 or later to be running but not vROps 7 at this time as this management pack is not supported in 7.
Install / Configure
- Log in as the admin user, or equivalent.
- 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 installedf but not quite ready.
- So now to configure. Highlight the Service Discovery solution and select the gear.
- Filling in most of the Solution info is easy. But not all.
- I need to check the manual for the Dynamic Group is interesting. If it is disabled, that means all the components of an Apache server – for example – will be reported individually. If Dynamic Group is enabled it will be report as an Apache server. You can also rename as necessary. So this should be enabled I think.
- The credential config is unexpectedly detailed.
- Enter in as much as you can. The Guest User Mapping is an interesting feature – it can be used to do individual credentials per VM.
- Before you save or close make darn sure you do Test.
- 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. I do wait for a bit so that data can be accumulated.
How do we know it is working?
I see we have a Service Distribution dashboard now.
But what we can do with this management pack – now that it is installed – I will leave to another article.
I was very disappointed with 1.0, but we are at 2.1 now so it will be interesting to see what we can do with it. VIN was so easy to install, configure, and recognize services that it was a super useful tool. II will share how things go.
I will keep working with it and see how it goes.
- 11/11/18 – cleaned up some of the spelling and grammar type stuff. I have deleted SD and vROps in my lab, and tried again to see how it will go. Just now finished the install / config of the SD MP. Will wait a day and see how it goes, before I start again with VMware.
- 8/6/18 – I did not see any of the services or relationships after a couple of hours so checked with support. With a new vROps install, done less than a day before, and a new SD install, it could take 48 to 72 hours for data to be seen. I think that with my small lab it should be quicker than that but we will see.
- 8/6/18 – published.
- This is an interesting article to help with troubleshooting.
=== END ===