Launching soon: The world's first vendor agnostic bug scrubLearn more & join waitlist
OPERATIONAL DEFECT DATABASE
...
...
The vCenter Server or PSC services fails to start when the IP address or hostname is changed in vCenter Server or Platform Service Controller (PSC). In the vmware-sts-idmd.log file of the Platform Service Controller, you see entries similar to: [2015-07-16T08:17:31.353-06:00 vsphere.local 47c25a86-20c3-49c6-9ec0-c5579b36c83d ERROR] [IdentityManager] Failed to authenticate principal [Administrator@domain] for tenant [vsphere.local] com.vmware.identity.idm.IDMLoginException: Access denied In the vpxd.log file of the vCenter Server, you see entries similar to: 2015-09-01T10:41:51.532-06:00 warning vpxd[03740] [Originator@6876 sub=Default] Failed to connect socket; <io_obj p:0x000000000c4d83d8, h:3392, <TCP '0.0.0.0:0'>, <TCP '</font>IP_Address'>>, e: system:10060(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) 2015-09-01T10:41:51.532-06:00 error vpxd[03740] [Originator@6876 sub=HttpConnectionPool-000011] [ConnectComplete] Connect failed to <cs p:0000000008d2dda0, TCP:</font>vcenter.domain.local:443>; cnx: (null), error: class Vmacore::SystemException(A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) Notes: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment. If hostname and DNS configuration reverts to original values after rebooting the VCSA machine see VMware vCenter Server Appliance hostname and DNS configuration revert after a reboot (2122383).Also see, How to update content libraries after changing vCenter Server PNID
vCenter Server 6.x versions prior to 6.7 Update 3 does not support changing the PNID after deployment.
During the initial configuration of the VMware vCenter Server, the system name (FQDN or IP address) is used as the PNID. This issue occurs when Primary Network Identifier (PNID) of vCenter Server or PSC is changed after deployment.
The PNID is equal to the System Name parameter input during deployment. The System Name can either be a Fully Qualified Domain Name (FQDN) or an IP address. For example, a system name could be vcenter.corp.local or 10.10.100.50 which would also then become the PNID. This PNID is locked in and cannot be changed after deployment on versions prior to 6.7 Update 3. vCenter Server 6.7 Update 3 introduced feature to modify the Hostname/PNID.vCenter Server 6.7 Update 3 supports modifying the PNID, you may upgrade to this version to modify the PNID. Refer to the blog https://blogs.vmware.com/vsphere/2019/08/changing-your-vcenter-servers-fqdn.html for more info. Changing the Primary Network Identifier (PNID) is not supported in vCenter Server 6.x versions prior to 6.7 Update 3 and use one of these options to resolve the issue: Revert to a snapshot or an available backup which was created before changing the IP address or hostname. For more information, see Working with snapshots (1009402). Redeploy the vSphere environment. To change the IP address of vCenter Server that was deployed with a FQDN PNID: Using the VAMI. Using the vSphere Web Client.Using the DCUI. To verify the current PNID, run the following commands in VCSA or Windows vCenter Server respectively:VCSA: /usr/lib/vmware-vmafd/bin/vmafd-cli get-pnid --server-name localhostWindows: "C:\Program Files\VMware\vCenter Server\vmafdd\vmafd-cli.exe" get-pnid --server-name localhost
Note: On rare occasions, you may need to manually set and complete the PNID change via the command line should the above UI workflows incompletely set the PNID.To set the PNID via CLI:VCSA: /usr/lib/vmware-vmafd/bin/vmafd-cli set-pnid --server-name localhost --pnid <PNID-NAME>Warning: If you attempt to set the PNID via the command line only without going through the proper workflow, as mentioned in the Resolution section, you may break vCenter.
VMware Skyline Health Diagnostics for vSphere - FAQhttps://blogs.vmware.com/vsphere/2019/08/changing-your-vcenter-servers-fqdn.htmlChanging the Windows vCenter Server 4.x and 5.0 hostname (2040354)How to stop, start, or restart vCenter Server Appliance 5.x services (2054085)How to stop, start, or restart vCenter Server 6.x services (2109881)Location of VMware vCenter Server 6.0 log files (2110014)Attempting to change the IP address of the VMware vCenter Server Appliance 6.0 fails with the error: IPv4 configuration for nic0 of this node cannot be edited post deployment (2124422)无法更改 vCenter Server 或 Platform Services Controller 6.x 主机名 (2137087)vCenter Server または Platform Service Controller 6.x のホスト名を変更できない (2139374)Changing the Windows vCenter Server 5.1 and 5.5 hostname (2146301)