Just a reminder since I don’t do this often. And I know someone else who could use the help too! This is a reminder with links to the how.
This was done with vR Ops 6.0.2 but should work fine with any 6.x build. This is for a one node cluster. Update – I used this with 6.1 and a few changes were required – mostly in docs connected to this one. Updated for 6.2.
- FQDN and IP for each node
- Bits from MyVMware
- I use vSphere Web Client but it doesn’t matter much.
- Deploy the vR Ops OVA.
- Remember to use a FQDN – bosvrops01.dglabs.com for example as there used to be an issue if you did not and wanted to change things (due to it being a one disk vApp).
- Choose the right size!
- Let it start up.
- Once the VM has started up you can see FQDN and IP info on the console.
- We need to work in the admin UI – https://bosvrops01.dglabs.com/admin.
- You have a choice but I like the New option.
- Complex password
- Default or not, certificate
- Master node name
- NTP – 1.us.pool.ntp.org, 2.us.pool.ntp.org, 3.us.pool.ntp.org
- or NTP – 0.ca.pool.ntp.org, 1.ca.pool.ntp.org, 2.ca.pool.ntp.org
- Once you see it, you need to Start vR Ops Manager in the Cluster Status area. Takes a little while. When it is ready it will log you out.
- We can log in now as the admin user. You log in using the account admin and the password you defined above.
- You may be prompted for import or new. New for me. Import works good but takes a while – maybe a long while. I talk about it here for the upgrade of 5.8.x to 6.x.
- License key necessary now. Make sure to validate. Actually, as of around 6.0 or 6.1 you could choose Eval or trial instead of license.
You have a working vR Ops now, but it is limited in what it is reporting!
- We need to connect to vCenter – you can use this article. It is to solve an issue but just follow it and you will be good! You may not see Manage Registrations at first but that is OK. Just add your service account info for vCenter and Test and Save. If you had vR Ops before you may see Manage Registrations but if you deleted it you will not, and you will be prompted about the registration process and it is OK to say overwrite.
- Log Forwarding – to send vR Ops events to syslog – here. (Update, if you are going to use the LI agent in vR Ops to forward, don’t do anything in the UI).
- Using Log Insight – if so – and I sure do – you can use this article to help configure the Log Insight Agent that is pre-installed on vR Ops v6.01 and later. I think, and I am looking to confirm, that if you do this you should NOT do the previous step of configuring log forwarding in the vR Ops UI – the agent will deal with forwarding (Update – correct, if you use the agent don’t configure syslog in the UI). Note, you may need to enable SSH to do this and you can find out how here.
- Install vRealize Log Insight Management Pack – if you use LI – with info from here.
- Install VMware Infrastructure Navigator Management Pack – if you use VIN, and certainly you should – with info from here.
- Maybe install Management Pack for Storage Devices – if you have SMI-I, or VASA compliant hardware you should install this management pack. At some point, perhaps very soon, it should support generic NFS. You cannot delete a MP but you can delete everything that makes it up so you can install this MP if you think it useful, and yet you can delete the dashboards if they are not what you want. Info to install is here.
- Active Directory should be connected. See here for that and creating admin users – which you should do too.
- Read only account? Find out here.
- Outbound Email Alerting – don’t you need this too? Find out how here.
- Change root password. The root password ships blank. So use the console, and do a alt + shift + F2 – on a Mac anyway – to change to the login prompt. Login as root and hit return on the password and you will be prompted to do a complex password.
- Once things are running for a while, and the stuff above is done, maybe we should have a cluster – find out how here or here. And here is an example of putting a LB in front of your cluster.
You now have at least one node of vR Ops working, and it should be well configured too. You need to let it run for a while to accumulate information to start doing trending but you do not need to wait as long as in the past.
- 3/19/16 – updated for vR Ops v6.2. Added Useful links too. Added URL to see how to enable SSH.
- 1/13/16 – updated for URL issue I found. And eval mode.
- 11/15/15 – added the comment about if you use the built – in LI agent to forward to syslog, you should not enable syslog in the UI. Updated for 6.1.
- 7/15/15 – added the comment about changing the root password.
As always – questions or comments welcome.
=== END ===