vSphere Replication Add-On registration and Folder issue.

While deploying recently the vSphere Replication solution on an infrastructure, I found myself confronted with a strange situation. I had deployed the vSphere Replication 6.0 appliance (Management and Replication), I was looking to add a 2nd vSphere Replication appliance to the primary site. Yet, once the Add-On vSphere Replication appliance was deployed, I was not able to select it via the vSphere Web Client to add it, only the error message “Selected object is not a virtual machine. Select a virtual machine to register as vSphere Replication Server.”

Unable to register vSphere Replication Add-On


After moving the new vSphere Replication appliance from my Bussink.org VM Folder back to the ‘Discovered virtual machine’ folder, was I able to use the Register vSphere Replication server function.

Register vR Add-On

Once the VM is registered with the vSphere Replication server, moving it to my custom VM Folder (Bussink.org) is not an issue anymore.



vCenter Infrastructure Navigator 2.0 integrated with vSphere Web Client

Looking back at the screenshot of the vSphere Web Client, we see that the vCenter Infrastructure Navigator 2.0 has identified 27 Known Application Services.

If we want to see how the vCenter 5.1 communicates with other infrastructure elements in the virtual environment, there are two ways to look at it. First from the vCenter 5.1 VM we see that there are a few dependencies.

When examining the Show Dependencies we get the Map view. Here is only a element of the Map View as it scales to over 47 dependencies.

But you can also see the Table View, where we see incoming dependencies and outgoing dependencies.


I know this functionality of incoming and outgoing dependencies will be very useful to some of my clients.


vCenter Operations Manager 5.6 integrated with vSphere Web Client

Today VMware released vCenter Operations Manager 5.6 and vCenter Infrastructure Navigator 2.0. These products are now very tightly integrated with the vCenter 5.1 and plug into the vSphere Web Client.

In the screenshot below, you see two new floating windows with the proper information for the element you are managing.

In this case, I’m looking at a my pVDC_1 Cluster, and vCenter Infrastructure Navigator has identified 27 known applications, while vCenter Operations Manager 5.6 is telling me that the health of my Cluster could be better.

In addition, within vSphere Web Client, you can move the floating information panes around to better suit your needs and see what’s important. Or to take advantage of a screensize.