SRM 5.1 - Sites will not connect

[D4N201110141]

I'm working on an SRM 5.1 implementation and am experincing an odd error. When I go through the 'Configure Connection' wizard everything completes (all green checkmarks) and the wizard exits. However, under sites the Local site shows a status of 'Not Connected' and the remote site shows a status of 'Unknown'

I've tried breaking the connection and restablishing but that does not seem to work either. If I exit vCenter and reopen it SRM asks for an account to the remote vCenter. I enter the credentials and then get the following error after some time -

     The request failed because the remote server took too long to respond.

So far I cannot find anything out of the ordinary with our setup. The sites did connect one time (after breaking and recreating) but have since disconnected and will not reconnect. Any ideas?

[memaad]

Hi,

What is operating system you are using windows 2003, for SRM.

Also what operating  system you are using to launch the vCenter server client XP ?

Regards

Mohammed

[D4N201110141]

Server 2008R2 64-bit

Windows 7 client.

[memaad]

Hi,

It is worth looking into vSphere Client logs When you try to pair the sites. Also make sure required ports are open and allowed through firewall. Also can disable local windows firewall on both the SRM and vCenter server machine.

Port requirement  for  SRM.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100956...

Regards

Mohammed

[D4N201110141]

I will look into exporting the logs. No firewalls are turned on, so I know it isn't that.

Thank you for the quick replies. I spoke with another admin who said they were having trouble with vcenter logging in correctly. I'm going to look into that as well. Maybe there is a vcenter patch we haven't applied yet.

[memaad]

Hi,

what is version of vCenter server it has to be 5.1.X

Regards

Mohammed

[D4N201110141]

Mohammed

Right now the vCenter Server is at 5.1.0. We will be upgrading to 5.1.0b sometime soon. Perhaps this will resolve the issue.

[VMMikeC]

silly question, but is the vCenter service started at the remote location?'

[Alim786]

I had a similar problem. I logged onto my Primary Site vCenter server with my AD account. I started the vSphere Client and used the same credentials and was able to administer vCenter as normal. I selected the Site Recovery icon and it prompted me to enter the credentials used to configure the Sites originally which were different to mine. After some time it timed out with the same error you are getting.

I then closed my vSphere Client and started it again and this time logged on using the credentials used to configure the Sites. I selected the Site Recovery icon and prompted me again and put in the same credentials and this time it connected successfully. It is a timeout issue and I am sure there must be a setting to resolve this either exposed within the GUI or as a bug-fix.

For you to try this, you must make sure that the account used to configure the Sites is a vCenter Admin.

[D4N201110141]

The solution was to patch our vCenter servers to 5.1.0b.

[Alim786]

Thank you for the answer.