This is because there is no GUI method to unregister a cluster from Prism Central, so the process requires SSH access to the PC VM as well as to a CVM of the cluster2. The unregistration process involves getting the UUID of the cluster from the CVM and then using that to trigger de-registration from PC command line2. The unregistration process also involves cleaning up any associated metadata and configuration on both PC and PE2. Therefore, the administrator needs to use a Host SSH session to perform this task.

One of the possible reasons for a cluster to transition out of NearSync is insufficient network bandwidth between the source and target clusters. NearSync requires a minimum network bandwidth of 10 Mbps per VM for replication3. If the network bandwidth is lower than the required amount, the replication of recovery points may take longer than the configured RPO, resulting in an Out of NearSync condition. To address this issue, you can increase the network bandwidth between the clusters or reduce the number of VMs protected by NearSync4.