VMware Cloud Community
RKLMicah
Contributor
Contributor
Jump to solution

vCenter/SRM upgrade to 6.1

All,

We recently upgraded our vCenter server from 5.5 Update 2 to 6.0 Update1b.  Everything with the PSC and vCenter upgrade went swimmingly.  The problem that we are running into is with SRM.  We upgraded SRM from 5.5.1 to 6.0 which went through successfully.  However, whenever we log into the vSphere Web Client and run SRM we get the following message when clicking on sites:

Cause:

The connection to remote servers of SRM Server at https://<IPofLocalSRMServer>:9086/vcdr/vmomi/sdk needs to be reconfigured.

I can't find anything on this error and have been waiting for hours for VMware support to call.  Any ideas?  We are getting this message with both (remote and local) SRM servers.

I suspect it's a certificate issue however I am unable to pinpoint where.  When going to https://srmhost:9086 I get the following:

Local Connections

-------------------- --------------------------------------------------------------------------------
Service com.vmware.cis.cs.inventory
URL https://<vCenter Server>:443/invsvc
Thumbprint unknown
Status Connected
-------------------- --------------------------------------------------------------------------------
Service com.vmware.cis.vcenterserver
URL https://<vCenter Server>:443/sdk
Thumbprint unknown
Status Connected
-------------------- --------------------------------------------------------------------------------
Service com.vmware.cis.cs.inventory
URL https://<vCenter Server>:443/invsvc/vmomi/sdk
Thumbprint unknown
Status Connected
-------------------- --------------------------------------------------------------------------------
Service com.vmware.cis.cs.lookup
URL https://<vCenter Server>:443/lookupservice/sdk
Thumbprint unknown
Status Connected
-------------------- --------------------------------------------------------------------------------
Service com.vmware.cis.cs.identity
URL https://<vCenter Server>/sso-adminserver/sdk/vsphere.local
Thumbprint unknown
Status Connected
-------------------- --------------------------------------------------------------------------------
Service com.vmware.cis.cs.authorization
URL https://<vCenter Server>:443/invsvc/vmomi/sdk
Thumbprint unknown
Status Connected
-------------------- --------------------------------------------------------------------------------
Service com.vmware.cis.cs.license
URL https://<vCenter Server>:443/ls/sdk
Thumbprint unknown
Status Connected
-------------------- --------------------------------------------------------------------------------

Thanks!

1 Solution

Accepted Solutions
Daniel_Georgiev
VMware Employee
VMware Employee
Jump to solution

Hi,

after upgrade you have to Reconfigure pairing between sites or repair connection from one site to another. This should be one time effort and it's needed to renew the certificates information in SRM after all upgraded products.

You can find more useful information in our documentation - Site Recovery Manager 6.1 Documentation Center

1

In the vSphere Web Client client, select Site Recovery > Sites, right-click a site and select Reconfigure Pairing to reconfigure the connection between the Site Recovery Manager sites.

Hope that this help,

Daniel G.

View solution in original post

0 Kudos
2 Replies
Daniel_Georgiev
VMware Employee
VMware Employee
Jump to solution

Hi,

after upgrade you have to Reconfigure pairing between sites or repair connection from one site to another. This should be one time effort and it's needed to renew the certificates information in SRM after all upgraded products.

You can find more useful information in our documentation - Site Recovery Manager 6.1 Documentation Center

1

In the vSphere Web Client client, select Site Recovery > Sites, right-click a site and select Reconfigure Pairing to reconfigure the connection between the Site Recovery Manager sites.

Hope that this help,

Daniel G.

0 Kudos
RKLMicah
Contributor
Contributor
Jump to solution

Daniel,

Thank you for your response.  You are correct, that was the answer.  Initially when we performed the upgrade to SRM 6.0 we were able to pair from SITEA to SITEB but not in reverse.  When pairing from SITEB to SITEA the server didn't populate in the list.  We went ahead and upgraded to SRM 6.1 and received a certificate trust issue which kept us from being able to pair them still.  We downloaded the root certificate from the PSC and installed it on that host and rebooted which allowed us to then pair both of the sites together.

All is well in the land of SRM!