vSphere 6.5 Replication between two vCenter Instances

[FriendzKnight]

Hi there,

I am having issue with getting the vSphere Replication working between two vCenter instances.

Both the vCenter Servers are running the same version - vCenter Server Appliance 6.5.

The vCenter Servers are in different Datacenter (Physical) and they manage the ESXi hosts in those datacenters. Very small infra, one vCenter contains 2 ESXi and the other has 3 ESXi hosts.

Both the vCenter Servers have the same SSO Domain - vsphere.local (the default one)

When I try to connect the sites, the connection will succeed and the sites appear in the Target sites. But, the status shows as not authenticated.

If we try to connect the sites manually, it will just complete without any messages and the status still shows Not Authenticated. Is it because both the vCenters have the same SSO domain name? Any idea?

[GregPatria]

had you check this KB "Registering VMware vSphere Replication to VMware vCenter Server fails with the error: The session is... " ?

[Sreejesh_D]

you can safely ignore this disconnected state. In this case, the Not authenticated state reflects the connection to the remote site from the vSphere Web Client and not the state of the connection between the sites. If the two sites are running, vSphere Replication still performs replications at the schedules that you have configured.Please find more details here.

https://docs.vmware.com/en/vSphere-Replication/6.1/com.vmware.vsphere.replication-admin.doc/GUID-4F3...

[FriendzKnight]

As per this KB, I did provide the credentials in the vSphere Web Client, but still it does not show the status as connected.

I recently updated vCenter Server Appliance to the latest build 6671409.

After updating the vCenter Appliances at both the sites, the vSphere Replication sites showed connected.

I tried to start a replication for one of the virtual machines. After the first step, when it shows to select the target datastore, it was not listing any of the datastores in the target vCenter. It was blank.

Next day, when I checked the vSphere Replication sites still does not show as connected.

[FriendzKnight]

Hi GregPatria,

I could see messages similar to the one stated in the link that you provided.

2017-10-16 10:26:51.110 WARN  jvsl.security.authorization [tcweb-11] (..security.authorization.JvslActivationValidator)  | Access Denied: "getHmsServers()"...

(vim.fault.NotAuthenticated) {

   faultCause = null,

   faultMessage = null,

   object = MoRef: type = HmsRemoteSiteManager, value = site-manager, serverGuid = 6d248f4d-6309-409e-b87e-7513c238b795,

   privilegeId = HmsRemote.com.vmware.vcHms.Hms.View

}

2017-10-16 10:26:51.111 INFO  hms.i18n.class com.vmware.hms.response.filter.I18nActivationResponseFilter [tcweb-11] (..response.filter.I18nActivationResponseFilter)  | The localized message is: The session is not authenticated.

2017-10-16 10:26:51.191 INFO  jvsl.security.authorization [tcweb-13] (..security.authorization.SessionAuthorizer)  | HmsServiceInstance.getContent called on service-instance by N/A@/10.201.10.41:38990 with opId 01cd03c6-8bd3-423b-98e6-d7ca24948f44-HMS-54

2017-10-16 10:26:51.191 INFO  com.vmware.hms.vlsi.step.InvocationStep [tcweb-13] (..vlsi.step.InvocationStep)  | vmomiOp-start method: HmsServiceInstance.getContent; target: service-instance; user: null; client: /10.201.10.41:38990; opId: 01cd03c6-8bd3-423b-98e6-d7ca24948f44-HMS-54

2017-10-16 10:26:51.192 DEBUG com.vmware.hms.vlsi.step.InvocationStep [tcweb-13] (..vlsi.step.InvocationStep)  | vmomiOp-finish method: HmsServiceInstance.getContent; target: service-instance; user: null; client: /10.201.10.41:38990; opId: 01cd03c6-8bd3-423b-98e6-d7ca24948f44-HMS-54; time: 1 ms

2017-10-16 10:26:51.200 INFO  jvsl.security.authorization [tcweb-14] (..security.authorization.SessionAuthorizer)  | HmsSessionManager.HmsSessionManagerLogoutHmsServer called on session-manager by N/A@/10.201.10.41:38990 with opId 7e3b4623-e67a-4116-af7c-5b47aa6b259b-HMS-55

2017-10-16 10:26:51.200 WARN  jvsl.security.authorization [tcweb-14] (..security.authorization.JvslActivationValidator)  | Access Denied: "logoutHmsServer(site)"...

(vim.fault.NotAuthenticated) {

   faultCause = null,

   faultMessage = null,

   object = MoRef: type = HmsSessionManager, value = session-manager, serverGuid = 6d248f4d-6309-409e-b87e-7513c238b795,

   privilegeId = System.View

Unfortunately, the provided link is applicable for vCenter Server on Windows Server. I am having vCenter Server Appliance. Is there any alternative links or settings that I can check the logon settings in vCenter Server Appliance? Please help me with them. I am also researching for similar info. I will update if I am able to find. In the  mean time, if you have any links, could you please share with me? thx