A while back I pulled out vROps from my lab due to disk space issues. Those are now solved thanks to Nexenta and it is time to bring vROps back to my lab.
One of the reasons is that there is now a VMware Infrastructure Navigator (VIN) replacement and it is a management pack in vROps. So you know right there it will not be as easy to use, and maybe in fact be more powerful too. I need to check it out as I believe VIN is a critical tool to successful DR planing and understanding how an app is not an app until you know all what it needs to work.
So this article will be about getting vROps 6.6 working, and I will do another about the Service Discovery management pack.
So lets get started!
Before – prep time
I like to do a little research – things like the release notes. I also like to google and see what I can find. I find one article on an overview and why 6.6 is so cool. I also found a series on 6.6 that is pretty good – so far here is part 1, and part 2. Some good info so far and I will watch for the next parts to this series. We need to make sure we have the bits too. Just in case the vROps doc site is here, If you have a good sized environment – which I would say starts around one or two hundred VMs, you likely will want to size your vROps. You can get help for that in this article. This is important as the Excel sheet they provide to help you with the sizing may indicate you need to add more disk to the vROps before you do that first boot.
We should have a FQDN in DNS, and an IP address for our vROps and a license for it too!
Install of vROps – deploy
- So we start in the vSphere Web Client and we deploy an OVA. I do this by selecting the cluster, then using the Actions drop-down to select Deploy OVF Template. Browse out to your vROps OVA.
We name our appliance and pick a folder location.
Next is the cluster choice.
Next we choose the configuration – for home lab Small, and in fact a lot of customers could probably use Small too. If it is possible – meaning if you have lots of memory and processor in your cluster it is a good idea to use the config that is one bigger then you should. It may help with performance and also help for covering off your growth.
Next you chose the storage for the appliance.
Next is the network selection choice.
On the next screen we take care of Network.
So Next, Next, Finish now. Note the reminder about adding disk before the power up? That is if your environment needs additional storage.
You are done with the deploy stage.
Install of vROps – configuration
We connect to https://fqdn and the first time it redirects us to https://fqdn/admin . For future reference when you want admin access you could use https://fqdn/admin and normal access visit https://fqdn.
- You connect to https://fqdn and you need to select New Installation.
- We need to change the admin password next.
- You add a custom cert or just use the self signed included.
- Now we need to select some deployment options – like a master node name and NTP servers.
- You can substitute US for the CA in the NTP server names and that will work fine for US users.
- Now we need to start vROps.
- The startup will take a while.
- While you wait, you can access the console of vROps and change the password of the root account. The old password is return. Not typed in as such but hit the enter key.
- The SSH type console connection is disabled by default but you can enable if required using service sshd start.
- In my small lab the objects went up to 34, and the metrics went up to 2526 and took maybe 20 minutes before it logged me out.
- So once you have been logged out, log back in.
- You will need to accept the EULA, add your product key (and Validate) and, please stay in the Customer Experience program as it does help VMware help you better.
- Now make sure you are in the Administration Solutions area.
- We need to configure the vCenter connection. So make sure VMware vSphere is highlighted and hit the gears.
- The configuration will look like – after you enter some data – like below.
- Where it gets interesting in this Instance Settings screen is the credentials. You need to use the green plus and add in your service account that has the rights in vC for vROps to work (I am using vC admin rights for my service account – not the best approach but it works for me). Once done make darn sure to use the Test button.
- You may be prompted to accept a certificate during your test.
- What you want to see is Test Connection Successful.
- Now you see see Collecting in the Collection State field.
- You need to configure Log Insight now but there is not much to do. Just name the instance.
Now log in and see what the HTML5 UI is all about.
Doesn’t it look great? And it is partially thanks to Project Clarity.
If you change to the Administration / Solutions are you can see the status of our solutions. Which is pretty good.
You may notice there is only one dashboard. You can enable all of the dashboards, or a subset if you prefer, by looking under the All Dashboards option. I enabled all of them thinking it would be better for exploration and I can disable later. This is something that is user specific. So while you will do this when logged in as Admin and it will be remembered, when you log in as you there will only be a small set of dashboards selected.
You now have vROps working and monitoring your environment. There are some post operations that are good but that I will not cover at this time. But you are good to start monitoring your environment now.
You should do a number of things – such as:
- Enable Active Directory logins – likely using the new vIDM product. I need to work more with that before I can say how to make it work!
- Enable Alerts – so configure your SMTP server info and enable some alarms or alerts.
- Install / configure of the new Application Discovery Management Pack – article
- Configure Log Insight to work with this new vROps – article.
It is worth noting that you can select to use your vCenter at log on (in the drop down list) and that means your AD user that can log into vCenter can log into vROps too. Still worth setting up proper authentication that will make more sense to your end users but this is interesting.
This is a very different vROps in many ways. It really has a lot of rework in it and it shows. It looks good and I think it is easier to do a number of things so that is good. I also like some of the new organization and that helps too.
Thanks for reading this far, and as always, I love comments and questions.
- 6/25/17 – so I have spent some time in vROps 6.6. It is a big change from the past. You will need to spend some time in it to become comfortable. It has a lot of functionality.
=== END ===