vSphere Replication Sites Appear in the Not Authenticated State

vSphere Replication sites that you have connected appear in the Not authenticated state.

Problem

In configurations with two vSphere Replication sites where each includes a vCenter Server instance and a vSphere Replication appliance, the vSphere Replication sites can appear in the Not authenticated state, even if you have successfully connected the sites.

Cause

Sites that you have successfully connected can appear in the Not authenticated state when you establish a new login session to the vSphere Web Client and the previous login session has timed out. 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. To restore the Connected state in the vSphere Web Client, you must provide the login credentials for the remote site.

Solution

1. In the vSphere Web Client, select the vCenter Server to which the vSphere Replication is registered.
2. Click the Configure tab, and click vSphere Replication.
3. In Target Sites, right-click the remote site, select Reconnect site, and click Yes.
4. Enter the login credentials for the Platform Service Controller (PSC) on the remote site, and click OK.

   The address of the PSC is pre-populated, but you can enter a new address if necessary. For example, if the target vCenter Server was moved for load balancing, it might be managed by a new PSC.