book
Article ID: 326214
calendar_today
Updated On:
Environment
VMware vCenter Server 7.0.x
Cause
This issue occurs, when there is a difference in the case-sensitivity between the vCenters FQDN, its primary network identifier (PNID), the domain controller name (DCName) of its embedded platform service controller in the vsphere.local domain, and the spelling of the PNID in /etc/vmware-rhttpproxy/endpoints.conf.d/ProxyConfiguration.json in vCenter Server 7.0.
In vCenter Server 8.x, /etc/vmware-rhttpproxy/endpoints.conf.d/ProxyConfiguration.json no longer contains the vCenter FQDN, but replaces it with localhost.
Resolution
Caution: Before applying the steps below, please take a backup or an offline-snapshot (in powered-off state) of the vCenter Server Appliance . If the vCenter is part of a Linked Mode replication setup, please backup/snapshot all replicating nodes as well.To resolve this issue, change the PNID of the vCenter Server to correspond with the spelling in /etc/vmware-rhttpproxy/endpoints.conf.d/ProxyConfiguration.json. However, since you cannot do a direct change to the same PNID in a different case, this is a 2-step process:
- Create a temporary record in your DNS server with the current vCenter IP and a temporary FQDN (e.g. VCSA1.domain.local)
- Change the PNID to this temporary FQDN following the complete process outlined in https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vcenter.configuration.doc/GUID-F46DBE63-F04E-42A1-B940-63A8F5B86ACF.html
- Do a second PNID change back to the old FQDN, but using the spelling that was found in /etc/vmware-rhttpproxy/endpoints.conf.d/ProxyConfiguration.json. For example, if the vCenter FQDN is listed as VCSA.mj.local in ProxyConfiguration.json, use this as the new PNID
- remove the temporary DNS record
- Upgrade the vCenter Server