You can also check the replication status and all PSCs with the vcdrepadmin -f showpartners command. Each PSC must have 2 replication partners. 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, the protocol /var/log/vmware/vmdird/vmdird/vmdir d/vmdird-syslog.log vdcrepadmin -f showservers -h psc1.vmware.local -u administrator -w VMw@re123 Load compensation does not affect the ring`s topology. You need to set it up if you want to replication between PSCs. Load Balancer is placed on each website before the 2 PSCs and the vCenter Server (s) tab on the Loadr VIP address. 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. Before you execute the agreement, check the current partner. psc3: s /usr/lib/vmware-vmdir/bin/vdcrepadmin -f showpartnerstatus -h localhost -u administrator -w VMw@re123 Partner: psc4.vmware.local Host available: Yes Status available: Yes My last change number: 9502 Partner saw my change number: 9502 Partner is 0 changes behind. Use this command to show the current state of replication of the PSC and its partner nodes: vdcrepadmin -f removeagreement -2-h Source_PSC_FQDN -H PSC_FQDN_to_Remove_from_Replication -u administrator -w Administrator_Password Step 8 of creating a ring chord should be « psc04.contoso.com » instead of « psc03.contoso.com. » Please correct him. The document is quite edifying and informative. Thank you very much..!! As noted above, this facility will create a redundant PSC topology, as all PSPs will be replicated with the neighbor offering redundancy.
However, the replication between the last and the first PSC must be created manually to achieve this configuration. You interrupted the replication links as follows. Therefore, if a change is made on PSC1, it is not replicated on PSC3 or PSC4: if PSC-01 is provided and configured, provide PSC-02, PSC-03, etc. It is important to do this one after the other and register for the previous CSP when the next one is provided. So if you provide PSC-02, save it to PSC-01 during installation. PSC-03 with PSC-02, etc. After providing PSC-06, you need to set up the replication manually with PSC-01. This is the creation of PSC-Ringtopology.
Also be sure to create/join the specified site when setting up! vdcrepadmin -f showpartners -h psc1.vmware.local -u administrator -w VMw@re123 ldap://psc2. vmware.local vdcrepadmin -f showpartners -h psc2.vmware.local -u administrator -w VMw@re123 ldap://psc1. vmware.local ldaps://psc3. vmware.local vdcrepadmin -f showpartners -h psc3.vmware.local -u administrator -w VMw@re123 ldap://psc4. vmware.local ldaps://psc2. vmware.local vdcrepadmin -f showpartners -h psc4.vmware.local -u administrator -w VMw@re123 ldap://psc3. vmware.local This procedure is also available for PSC files run on a Windows computer. For more information, see KB 2127057. This kb article also contains additional commands of vcrdepadmin tools as well as a procedure for removing a replication partner from a PSC. VDCREPADMIN showpartnerstatus displays the current psC replication partner as well as the current replication state between the two nodes. 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. You can now generate a new replication chord to create a ring topology, you need to generate an additional replication agreement between PSC1. and PSC4. If we have more PSC, prepare the topology of the network, and with the createagrement, we can plan the same thing.