Upgrading the VMware vCenter Server is a crucial task to ensure that your virtual infrastructure benefits from the latest features, improvements, and security updates. Here’s a detailed guide on how to upgrade vCenter Server:
While upgrading a vCenter you might come across the error: “The Replication partner provided is not part of the topology” while you are adding the correct IP address of the PSC for the Replication.
In these scenarios generally, an issue comes where the pnid of the vCenter Server is different from the name of the vCenter due to which the Upgrade operation is not moving further.
You can ssh to the Partner vCenter server and type the below command:
root@MHDES-VC2P [ ~ ]# /usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhost
ABCD-VC2P.i.abcd.com
Copy and Paste the name from the output of the above command and it should let you move further with the Upgrade Operation.
Hi Ashutosh
I entered the PNID which is as same as the FQDN name and still have the issue
I have 2 vCenters in Linked mode ( 1st vcenter already converted to 7.0.3e )
2nd vcenter 6.5 when I select the subsequent vcenter it fails with the error as per your above screenshot
If I check the replication status from the temp IP by ssh ( 2nd vcenter deployment ) it still shows the replication partner as external PSC of already converted Vcenter 7.0 and not embedded PSC
If I check the replication status from the 2nd vcenter ( 6.5 ) which is yet to be converted it still shows the replication partner as external PSC of already converted vCenter 7.0 and not embedded PSC
I am not sure how to proceed further. Any inputs is greatly appreciated
I would recommend you to Run the Tool : https://flings.vmware.com/vsphere-diagnostic-tool
This will give you a health summary of the vCenters and also any issues along with any issues and its solution.
Check the report and fix any outstanding issues.
Never forget to take a snapshot of both the vCenters before making any changes.