VMware Site Recovery Manager - unable to create site connection or pair

I have SRM setup in two locations on two seperate vCenter servers and cannot create a site pair.  I am connected to a vCenter server called omigalb-vc2 (cluster name = OMIG800NP) and try to create a connection to omigdr-vc1 (cluster name = OMIG-DR).  I enter the name of the vCenter server "omigdr-vc1.domain then my administration user account.  It tries to connect for a minute or two then i receive the following error:  

Error:

Cannot pair SRM server with itself.  OMIG800NP is already registered with omigalb-vc2.domain:80

Call "DrRemoteSiteManager.ProbeDrConnection" for object "DrRemoteSiteManager" on Server "omigalb-vc2.domain" failed.

When I try it from the other site, I receive the same error but with the reverse names.  

I am using the following version of software in both sites.
ESXi 5.1.0 build 1065491
vCenter Server 5.5.0 build 1312298
vSphere Client 5.5.0 build 1281650
SRM 5.5 (SRM Plugin Build: 1315893)
ittechstopAsked:
Who is Participating?
 
Paul SolovyovskyConnect With a Mentor Senior IT AdvisorCommented:
Run a repair on each SRM installation just in case, anytime you change IP/domain/alias it may have issues.
0
 
Paul SolovyovskySenior IT AdvisorCommented:
Check port 80 connectivity.  Also try using IP as a test instead of hostnames.  If using hostnames make sure you can resolve from each system
0
 
ittechstopAuthor Commented:
I had the same results using the ip addresses on each box.  I queried port 80 from each box with PortQryV2 and they are both listening on port 80.

C:\Admin\PortQryV2>PortQry.exe -n omigalb-vc2.domain -e 80

Querying target system called:

 omigalb-vc2.domain

Attempting to resolve name to IP address...


Name resolved to 10.x.x.x

querying...

TCP port 80 (http service): LISTENING

I have changed the above domain name to .domain and masked the IP address.
0
 
ittechstopAuthor Commented:
I ran a repair on both SRM installations and had the same problem.  I ran the modify option, accepted the new cert it generated and still had the same issue.  I had different settings in the DR virtual appliance.  No options at the top of the generate cert page even thou it was the same version appliance.  I shut it down and redeployed the virtual appliance in the DR site and was able to pair them.  

Thanks for your help, you lead me the in right direction.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.