Thursday, February 26, 2015

vCloud air plugin for vCenter server error: "Server Certificate not Verified"

For vCloud air plugin version this is expected if the vCloud air certificate has not been added to vCenter server trusted keystore.  If you don't add the certificate you will be unable to register your vCloud Air account with the plug-in and connect to vCloud Air.


Login to vCloud air.

From browser download the certificate.
NOTE Ensure that you select the Base-64 encoded x.509 option while exporting the certificate.
- Click the lock icon in the URL field, then click More information.
- In the Security tab, click View Certificate.
- In the Details tab, click Export.
- Save the file with the name vchs.cer and the type X.509 Certificate (PEM).
Internet Explorer
- Click the lock icon in the URL field, then click View certificates.
- In the Details tab, click Copy to File and follow the wizard to export the certificate.
- Select Base-64 encoded X.509 (.CER) as the format and name the file vchs.cer.
- Click the lock icon in the URL field.
- In the Connection tab, click Certificate information.
- In the Details tab, click Copy to File and follow the wizard to export the certificate.
- Select the Base-64

If your vCenter server is installed on Windows run this command:

C:\Program Files\Java\jre7\bin\keytool.exe" -alias aliasName -v -keystore "C:\Program Files\VMware\Infrastructure\vSphereWebClient\server\configuration\keystore" -storepass changeit -import -file path_to_file\fileName.cer

If your running a vCenter server appliance:

Copy .cer file to /tmp folder using a tool like WinSCP.
Run the following command:
/usr/java/jre-vmware/bin/keytool -alias aliasName -v -keystore /usr/lib/vmware-vsphere-client/server/configuration/keystore -storepass changeit -import -file /tmp/vCA.cer


Thursday, February 5, 2015

Sizing vRealize Operation Manager 6.0 using your existing vCOPS 5.8 environment information.

VMware provides a comprehensive KB on sizing your vRealize Operation Manager.  However this document is very much focused on first time installation architecture and does not really provide much information on how you can use your current 5.8 environment details in conjunction with the advanced Sizing guide spreadsheet.

I will just be focusing on the input parameter of this document and how i found the information needed to complete the excel spreadsheet.  Hope this helps but if you have a better solution please let me know since this is just from my own experience.

1. Getting information for vCenter Objects:

Open the custom UI webpage for vCOPS.
Select Admin tab -> Audit report
Select your preferred report type and submit.
At the bottom of the output page you have the section called "Virtual Environment (existing resources)" .  All the details required are available in this section.

2. Custom Adapters resource and metric counts

Open Custom UI website for vCOPS 5.8
Environment tab -> Environment overview

Expand Adapter instances
Select adapter

On right hand side highlight the adapter and select the  "Detail view" button.
There might multiple instance so go through each and add up for the total count of the adapter.

On the metric selector expand the instance generated
Select the number of metrics collected and number of resources collected.
The graphs display the numbers necessary for document.

This should provide all the information needed to get the correct sizing for your new vRealize Operations 6 environment.

Wednesday, February 4, 2015

Mac Pro 6,1 rack environment running VMware ESXi 5.5 (with Fiber connectivity to VNX)

With the recently addition of Mac Pro 6,1 to VMware's hardware compatibility I was eager to replace our exiting old Power Mac G5 towers in our environment.


  1. Mac Pro bios version MP61.88Z.0116.B05.1402141115
If your Mac Pro has an older boot ROM then just upgrade the Mac Pro to Yosemite (OS X 10.10) which contains the update to be applied to the Mac Pro.
  1. vSphere 5.5 P03 is required
Currently the latest version of ESXi available on VMware download is only 5.5 update 2 so you have to include the required patch version onto the update 2 ISO.  To do this perform the following steps: