vCenter Server 6.x versions prior to 6.7 Update 3 does not support changing the PNID after deployment.

• 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.

• 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.

• Using the VAMI. 
• Using the vSphere Web Client.
• Using the DCUI.