Recently I have been working with various products that compliment or are accessed by vCOPs/vROps via Management packs. As vROps is still fairly new in comparative terms to other products like vCOPs and VCE Vision, when planning migrations from vCOPs to vROps it is naturally important to check compatibility and what is required for a successful migration. If you are doing a greenfield deployment of vROps there is nothing to be concerned about, you simply need the VCE Vision appliance running version 2.
Recently I have been looking at William Lam’s excellent post on automating the deployment of vROps. After having a play around with it, to suit my own needs, I made some modifications to the Powershell script so it would support distributed switches. # William Lam # Edited by Simon Eady to support vDS # www.virtuallyghetto.com # Deployment of vRealize Operations Manager 6.0 (vROps) ### NOTE: SSH can not be enabled because hidden properties do not seem to be implemented in Get-OvfConfiguration cmdlet ###
For several months now we have seen glimpses of vROps by way of limited blog posts and the HOL demo’s so it was great to see it finally released. So what is it like out of the box? vROps 6.0 Release notes The first clear change is the move away from 2 VMs in a vAPP and consolidation down to 1 VM which is then easily scalable to more as you require.
vCOPs resources If you have spent time working with vCOPs you will be aware of the numerous and widespread resources out on the net to help you install and fine tune your deployment. Given there is a lot of content out there that is not always easy to fine immediately I wanted to collate a useful list for my own use and to share with others. Still a work in progress.
Recently I encountered this problem in a customer site whereby the logon to VCSA 5.5 would either time out, or take 3-5 minutes to actually log on. Running a netstat on the VCSA during the attempt to logon showed there was a SYN packet sent to the vCOps appliance on port 443 that never established a connection. Another check was attempting to connect using curl https://<vCOpsIP> –k - this would time out.
According to VMware, Infrastructure Navigator is …a component of the VMware vCenter Operations Management Suite. It automatically discovers application services, visualizes relationships and maps dependencies of applications on virtualized compute, storage and network resources. Effectively it takes a look at the network connections that are running between your VMs (and physical servers) and works out which applications and services are running on each, and the dependencies – both upstream and downstream – for each VM.
There’s no doubt that vCOps is a great product for proactively monitoring your vSphere environment, but it’s a hefty package for the lab. The minimum recommended RAM is a whopping 16GB – in my lab that’s the whole of my management host! I recently needed to do some testing so I wanted to get it running in the lab with the barest minimum I could get working, and it turns out you can get working with just 4GB and 2 CPU…albeit you wouldn’t want to monitor much!