The replication partner provided is not part of the topology. Please provide the PNID of partner vCenter Server.

Products

• VMware vCenter Server

Issue/Introduction

• You have a vCenter with external PSC in vSphere 6.x. Example: 2x vCenter with external PSC servers that are in linked mode 
• The upgrade of the first vCenter to 7.0 U2 with the PSC converging completes.
• When trying the upgrade of second one it fails with an error. 
• The replication partner provided is not part of the topology. Please provide the PNID of partner vCenter Server.

Environment

VMware vCenter Server 8.0.x
VMware vCenter Server 7.0.x
VMware vCenter Server 6.7.x

Cause

The issue can because of two reasons.

1. Providing incorrect PNID of the replication partner.
   1. Open an ssh session to the partner vCenter Server appliance and enable the BASH shell.
   2. Execute the following command to retrieve the PNID of the vCenter Appliance:
      1. /usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost
   3. Use the PNID when configuring the replication partner.
      
      
      
2. The replication partner is incorrect and not set. 
   
   Earlier both the PSC were in replication. So when we list replication partner or partner status we would get two PSC details. 
   Now as one of node has got converted, chances are there that the node which you are trying to upgrade now is not replicating with correct one (the converged vCenter). 
   
   Ref KB : Determining replication agreements and status with the Platform Services Controller (PSC)

Resolution

Determine the current status. 

Using the showpartners parameter

Make a remote connection to the Windows Platform Services Controller or SSH into the Platform Services Controller appliance.
Run this command to change directories to the VMDIRD folder:
Appliance: cd /usr/lib/vmware-vmdir/bin

Windows: cd "%VMWARE_CIS_HOME%"\vmdird\
 
Use this command to display the current partnership from the specified PSC:
Note: For 6.7 --> vdcrepadmin -f showfederationstatus-h localhost -u administrator -w Administrator_Password
vdcrepadmin -f showpartners -h PSC_FQDN -u administrator -w Administrator_Password

For example:
vdcrepadmin -f showpartners -h psc1.example.local -u administrator -w VMw@re123

This command provides PSC specified by -h parameter, partnership.

For example:
vdcrepadmin -f showpartners -h psc1.example.local -u administrator -w VMw@re123
ldap://psc2.example.local

At the end of the result we are expecting two replication agreement of PSCs. Now as we know that one of the PSC has converged hence the replication partner needs to change to the vc. 

Ideal condition to expect: 
Replication partner : PSC <--> Embedded vCenter. 

What we get: 
Replication partner : PSC <--> old PSC.


Using the createagreement parameter

create a new replication agreement between PSCs to generate a Ring Topology:
vdcrepadmin -f createagreement -2 -h Source_PSC_FQDN -H New_PSC_FQDN_to_Replicate -u administrator -w Administrator_Password

Here Source_PSC_FQDN  = your external PSC remaining to upgrade & converge.
New_PSC_FQDN_to_Replicate  = your embedded VCSA 7.0

Additional Information

Impact/Risks:
Upgrade fails for the second vCenter.