Registering vCenter Server on vCenter Operations Manager fails with the error : “Unable to connect to vCenter Server. Details: Connecting to VC at https://servername/sdk failed.”

Posted: May 23, 2013 in vCenter Operations Manager
Tags: , , , , , , , , ,

This may happen when you had the same vcenter server but another uuid or certificate previously registered or the instance was not clear and you try now to register it once again. Here the steps to fix this.

1) Checkout if the old vcenter server adapter instance is still in vcops

open a web browser, go to http(s)://<vcops>/vcops-custom/ and logon with the “admin” account
open the “adapter inctances” in the “enviroment” > “configuration”

vcops1

find the vcenter server adapter inctance and remove it

vcops2

2) Checkout if the old uuid is still sored and remove it if so

log on to vcops UI VM via ssh and edit vc_uuid file

fist-internal:~ # vi /usr/lib/vmware-vcops/user/conf/vc_uuid

you should see some lines like


https:///sdk

0X0XXXX-00XX-0000-000X-XX000X0X00X0
REGISTERED

Delete the three lines but ensure you don’t drop the wrong one. Maybe better you make a copy of the original file

Then log on to vcops Analytics VM and run the drup unique constraint script

secondvm-external:~ # ./drop_unique_constraint.sh

Note: if the drop inuque constraint script fail tu run ensure you’re connected to the Analytics VM and the host name is “secondvm-external”. If there’s anyother host name but you’re sure you’re on the proper VM change the host name with “~# hostname secondvm-external”.
If you get a permission denied error just make it with the chmode +w command executable

3) check out if the old ssl fingerprint is still stored in the truststore

log on to vcops UI VM via ssh change to /usr/lib/vmware-vcops/jre/bin and run the following command

./keytool -list -keystore /usr/lib/vmware-vcops/user/conf/truststore -storepass oxygen

You will now get the list of stored fingerprints of acepted ssl certificates from resent or prevusly registered vcenter servers

if the one server that failed to register match with one in the list, just remove it with the following command but replace https://<server name>/sdk-a0a0a0a0-a0a0-0000-a000-0a0a000aaa00″ with your actual alias you want to remove

./keytool -delete -alias https://<server name>/sdk-a0a0a0a0-a0a0-0000-a000-0a0a000aaa00 -keystore /usr/lib/vmware-vcops/user/conf/truststore -storepass oxygen
About these ads

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s