ibrarsajid1
Contributor
Contributor

Failed to retrieve pairs from Site Recovery Manager Server

I've two vCenters joined to same platform services controller. When I'm logged in using administrator@vsphere.local, there's no issue and I'm able to do everything within Site Recovery Manager.. I've an AD Integrated authentication setup in and my account is a member of Administrators@vsphere.local group. It was a member before installation of SRM as I read in VMware documentations that if it's not a member before, then you need to manually provide permissions.. So It seems my AD domain account has all the rights required but I'm unable to connect to sites when I'm logged in using domain\username.

SRM1.PNG

srm2.PNG

srm3.PNG

So now I'm logged in with administrator@vsphere.local account and I can see that all the permissions are fine.

srm4.PNG

srm5.PNG

srm6.PNG

In addition to this, I've restarted SRM and Web Client services on both vCenters.. Any help would be much appreciated..

The weird thing is SRM is not even prompting me for credentials which it should be and I do have Client Integration Plugin installed and working in my browser..

10 Replies
cptredemption
Contributor
Contributor

Did you get a resolution to this issue?

0 Kudos
Daniel_Soltau
Contributor
Contributor

I have the same issue, have you figured out a fix?

0 Kudos
basher
VMware Employee
VMware Employee

Hello

I would suggest filing a SR with VMware and providing SRM and vCenter support bundles.

As a tip - what format do you use when logging in using your AD account - user@domain or domain\user? Have you tried logging into vSphere Web Client using both formats? Sometimes there are issues normalizing the account format across authentication systems.

Thanks

Stefan

Director - VMware Site Recovery Manager
0 Kudos
Daniel_Soltau
Contributor
Contributor

Hi,

This is a bit strange but it started working after I logged onto both Vcenter web clients at same time.

Cheers,

Daniel

whitea88
Contributor
Contributor

I had this exact same issue deploying SRM 6.5, eventually I found this KB:

https://kb.vmware.com/kb/2147590

Changing from Integrated Windows Authentication to LDAP fixed the issue for me.

0 Kudos
Deso1ator
Enthusiast
Enthusiast

You saved me Daniel! I had the same problem and your solution fixed it for me. Thank you!

0 Kudos
SavkoorSuhas
Expert
Expert

Does the pairing work if you are logged into web client as the SSO user or any user from the SSO domain?

If yes, you need to change the Identity Source from IWA to AD as LDAP due to the fact there is some socket timeout with IWA as identity source.

Not an issue from SRM, It's something from the identity source.

# Suhas

If you found this or any other answer useful please consider the use of the Helpful or Correct buttons to award points. Don't Backup. Go Forward! Rubrik Peek into my Website: http://www.virtuallypeculiar.com
0 Kudos
slivovics
Contributor
Contributor

Go into Navigation | Site recovery | Site and take either your Protected or Recovery site view and check which side of the SRM is NOT connected

Then on the NON connected site, relaunch the VMware vCenter Site recovery Manager Server service

I have SRM 6.1.2

As this happened only once in 1,5 years and we had an intersite network issue I'm not going to dig any deeper right now.

hicall
Contributor
Contributor

Thanks ! you solve my problem too.

After restart services SRM server on Services Win Svr and refresh on SRM Website, this site is automatically Connected on both Sites !!

Cheers,

Regards,

Haikal

0 Kudos
oneilv
Enthusiast
Enthusiast

Hey guys,

I got the same error too and wasn't able to run any recovery plans or recovery plan tests as all the options at the recovery site were greyed out.

I also saw the same error message about the login creds being invalid at the recovery site.

What we did was login to each site individually and saw no errors in that process. Following that I logged out of the VC session and logged back in and then the message was no longer seen. It seems like some creds are cached which could be causing the issue. No services on the SRM servers were restarted no any changes made to the Identity sources in the two sites.

Does anyone know what might be the root cause of this issue?

Cheers, Onil

0 Kudos