Use the following command to create a new replication contract between PSCs. In our example, we therefore create the agreement between PSC37 and PSC35, so that in the event of a PSC36 outage, we still have replication with another partner in the field. Step 8 under the creation of the ring chord has a typo, it should be „psc04.contoso.com“ instead of „psc03.contoso.com“. Please correct him. The document is quite edifying and informative. Thank you very much..!! You interrupted the replication links as follows. Therefore, if a change is made on PSC1, it is not replicated on PSC3 or PSC4: VDCREPADMIN showpartnerstatus must display the current psC replication partner as well as the current replication status between the two nodes. You can now generate a new replication contract to create a ring trilogy, you need to generate an additional replication agreement between PSC1. and PSC4. From the output, we can also find the current sync with the entire replication partner with the value curren update sequence number (USN) and, In case of error, check the protocol /var/log/vmdird/vmdird/vmdird/vmdird-vmdird-syslog.log After providing ELM with VMware vSphere 6.7, check the VwareM PSC assignments and the replication status for all PSC VMware servers provided. For more information, see Determine replication and status agreements with the Platform Services 6.X controller (2127057) kb.vmware.com/s/article/2127057 If PSC2 dies, replication continues.

By connecting PSC1 to PSC4, the full ring is created. This does not happen by default. We will follow the steps to create this. Before you execute the agreement, check the current partner. If we have more PSC, prepare the topology of the network, and with the createagrement, we can plan the same thing. Due to the replication time, it can take a few seconds to minutes for a complete network topology to be configured. docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.upgrade.doc/GUID-925370DD-E3D1-455B-81C7-CB28AAF20617.html Use this command to show the current state of psC replication and its partner nodes: vdcrepadmin -f removeagreement -2 -h Source_PSC_FQDN -H PSC_FQDN_to_Remove_from_Replication -u administrator-w Administrator_Password If Microsoft AD is provided as a source of authentication, you set it up consistently for all PSCs in the SSO domain.