Simon’s #VMworld 2017: Sunday and Monday


Arriving in early on Sunday as the local flight choices are more limited from Bristol than perhaps a larger Airport, very fortunate to have a hotel so close to the VMworld venue, perhaps not so great for the evening activities but I am happy with it this way around.

Other than registration (4pm-8pm) and hopefully catching up with a few folk who have also arrived early.

In the evening I had the pleasure to meet many awesome people from the vCommunity.

My current focus has been on vRA so it was great to meet some well known and knowledgable.


vROps 6.1 whats new?

| 10/09/2015 | Tags: , , , ,

VMware.jpgSo vROps 6.1 has gone GA!

What have the guys at VMware added? I have listed what I consider the hi-lights below

  • The maximum of 8 nodes has been doubled to 16!
  • SSO integration has been added (requires vSphere 6.0)
  • Support for SRM has been added









  • vRealize Hyperic functionality has been added
    With the addition of End Point Operations Management, the value of vRealize Hyperic functionality has been extended to the vRealize Operations Manager core product, without the need to deploy vRealize Hyperic










  • Remote collector resiliency
    New functionality enables you to assign solutions to collector groups. Collector groups provide high availability access to data collection for the solution.
  • Support for IPv6
    You can deploy vRealize Operations Manager in Internet Protocol version 6 (IPv6) environments.
  • Support for Windows Server 2012 R2
    However it is still recommended to go with the appliances.
  • Dashboard and report enhancements
    New functionality enables you to post a dashboard as a report, and post a report to a shared drive.
  • Automated workload placement and re-balancing
    You now have the ability to re-balance workloads to optimize performance and preserve license optimization.
  • Telemetry
    A new collection of deployment and usage statistics for vRealize Operations Manager has been added, to help improve product usability and performance.telemetry1










  • Upgrade options
    Direct upgrade path from 6.0 or migrate 5.8 to 6.0, then upgrade to 6.1

So some really great enhancements in 6.1 however there is one key disappointment for me and that is that HA is still limited to a logical DC. #sadpanda

Release notes from VMware

Images from VMware



Installing SRM VNXe SRA – Failed to load SRA, ‘queryInfo’ didn’t return a response

Quick post to cover a fix for installing the VNXe SRA when you encounter the below error:

Failed to load SRA from ‘C:/Program Files/VMware/VMware vCenter Site Recovery Manager/storage/sra/EMC VNXe SRA’. SRA command ‘queryInfo’ didn’t return a response.

The components installed (in this order) are:

  1. vSphere 5.5
  2. SRM 5.5
  3. UNISphere CLI
  4. VNXe SRA 5.0.0

The root cause is that the system locale is EN-GB rather than EN-US, however even changing the locale does not resolve the issue. The Java installation will still try and load an en_GB module and fail. The solution is as follows:

Edit “<SRM Install>\storage\sra\EMC VNXe SRA\” in notepad and replace:

system("jre/bin/java -jar EmcVNXeSra.jar");


system("jre/bin/java -Duser.language=en -jar EmcVNXeSra.jar");

Rescan the SRAs within SRM to load the VNXe adapter details.

Installing VMware Site Recovery Manager (SRM) 5.5 in the Lab

Site Recovery ManagerI’ve been playing about with a compact SRM install in my lab – since I have limited resources and only one site I wanted to create a run-through for anyone learning SRM to be able to do it in their own lab too. I am creating two sites on the same IP subnet (pretend it’s a stretched LAN across two sites) and will be protecting a single, tiny Linux web server using vSphere Replication. I’m aiming to cover SAN based replication in a later post.

Below is the list of hosts and VMs running for this exercise:

  • ESXi-01 – my “Protected Site” – this is running DC-01, VC-01, SRM-01 and VRA-01 (to be installed later)
  • ESXi-02 – my “Recovery Site” – this is running VC-02, SRM-02 and VRA-02 (to be installed later)
  • DC-01 – this is my domain controller, I’m only going to use one DC for both “sites” as I don’t have the compute resource available to have a second running. This is also my Certificate Authority.
  • VC-01 – this is my primary Virtual Center server, it’s a Windows 2012 R2 server. It is managing ESXi-01.
  • VC-02 – this is my “recovery site” and it’s a Virtual Center Server Appliance (VCSA). It is managing ESXi-02
  • SRM-01 – “protected site” SRM server, base install of Windows Server 2012 at this point
  • SRM-02 – “recovery site” SRM server, base install of Windows Server 2012 at this point
  • WEB-01 – this is a really, really, basic Ubuntu web server I’ve deployed from a template to use for testing.

Right – without further ado, let’s get stuck in!


Generating and Installing CA Signed Certificates for VMware SRM 5.5

image I’m fairly new to SRM, but even so this one seemed like a real head-scratcher! If you happen to be using CA signed certificates on your “protected site” vCenter and “recovery site” vCenter servers, when you come to linking the two SRM sites you encounter SSLHandShake errors – basically SRM assumes you want to use certificates for authentication because you’re using signed certificates. If you use the default self-signed certificates, SRM will default to using password authentication (see SRM Authentication). Where the process fails is during the “configure connection” stage, if either one of your vCenter servers does not have CA signed and the other does (throws an error that they are using different authentication methods) or that you are using self-signed certificates for either SRM installation (throws an error that the certificate or CA could not be trusted).

SRM server ‘vc-02.definit.local’ cannot do a pair operation. The reason is: Local and remote servers are using different authentication methods.

image (more…)