With a new year comes new things and I am delighted to announce the start of a vROps based webinar series. These will consist of a set of live webcasts on different topics around vRealize Operations Manager open to public to attend live or view the recorded sessions later. Personally I am delighted to get the chance to work with Sunny Duaon this new project. Sunny is a well known and respected Senior Consultant at VMware and can be found often on twitter @Sunny_Dua.
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.
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://> –k - this would time out.