VMware Cloud Community
infraerik
Contributor
Contributor
‎03-19-2015 03:42 AM

Can't register vSphere Replication with vCenter

I have a completely vanilla installation with the vCSA 5.5 freshly installed and working properly. DNS is setup for the vCSA and the VR appliance.


I go through the vSphere Replication OVA deployment and I get no visible errors, but the service is not registered with the vCenter web service extension.

I go into the web interface of the VR appliance (on 5480) and all the data in the proposed fields is correctly entered. I enter the administrator@vsphere.local password, hit "save and restart" and get back:

"Unable to obtain SSL certificate: Bad server response; is a LookupService running on the given address?"

And yes, the LookupService is running on the vCSA on port 7444 as it should.

I went home and did exactly the same steps on my home lab and it worked the first time. So there's something about the environment that it doesn't like, and the only thing I can think of is DNS. To counter that, I tried changing all of the entries in the VR appliance to IP addresses instead with the same results.

I've tried both the 5.8 and 6.0 VR appliances with exactly the same results.

Currently baffled.

Tags (3)
Reply
6 Replies
jhunter1
VMware Employee
VMware Employee
‎03-19-2015 05:45 AM

Verify DNS is working properly by logging into the console of the VR appliance and using nslookup.

nslookup <IP address of VCSA>

nslookup <FQDN of VCSA>

Also look in vCenter Server settings and verify vCenter Server name matches what is in DNS (see attached screen shot).

Preview file
14 KB
Reply
mvalkanov
VMware Employee
VMware Employee
‎03-19-2015 05:55 AM

Hi,

For vCenter 5.5.x please use VR 5.8.x, not 6.0. VR 6.0 UI plugin requires WebClient 6.0 (and SSO/LookupService 6.0).

For VR 5.8 LookupService should not be relevant.

For VR 5.8 - please take a look at /var/log/boot.msg (logs from the initial automatic configuration).

For VR 6.0 and/or configuring through VAMI UI - please take a look at /var/log/messages and /opt/vmware/var/log/lighttpd/error.log

Regards,

Martin

Reply
0 Kudos
mvalkanov
VMware Employee
VMware Employee
‎03-19-2015 05:57 AM

You could register VR 6.0 with LookupService v1 at vCenter 5.5, however, you will need to manually type its address: https://ls_host:7444/lookupservice/sdk.

However this would be unusable without the UI plugin and it requires Web Client 6.0 and Web Client 6.0 requires LookupService v2 (once from vCenter 6.0).

Reply
0 Kudos
infraerik
Contributor
Contributor
‎03-19-2015 07:07 AM

This would be the little missing piece of the puzzle. There are a number of notes out there reminding you to check the vCenter Advanced Parameters FQDN, but none that make reference to the vCenter runtime settings. So this should be probably added to the documentation in the prerequisites :

DNS working (of course!)

Runtime settings : vCenter name = FQDN

Advanced Settings > FQDN = FQDN

As soon as I fixed the runtime setting which was previously set to the hostname without a domain suffix, things started working again.

I think that the difference is that in my home labs, DHCP supplies domain suffixes so there are never resolution issues like there are in this particular network.

Thanks !

Reply
mvalkanov
VMware Employee
VMware Employee
‎03-19-2015 07:52 AM

Hi,

Actually this requirement is already present in the documentation:

http://pubs.vmware.com/vsphere-replication-60/topic/com.vmware.vsphere.replication-admin.doc/GUID-89...

"... a fully-qualified domain name or a literal address."

Regards,

Martin

Reply
0 Kudos