Search the VMware Knowledge Base (KB)
View by Article ID

Cannot change the vCenter Server or Platform Service Controller 6.x hostname (2130599)

  • 37 Ratings
Language Editions

Symptoms

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

Note: For additional symptoms and log entries, see the Additional Information section.

Purpose

vCenter Server 6.x does not support changing the PNID after deployment.

Cause

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.

Resolution

Changing Primary Network Identifier (PNID) is not supported in vCenter Server 6.x. If the vCenter Server or PSC is deployed with an FQDN or IP as the PNID, you cannot change this configuration.
 
To resolve this issue, use one of these options:
  • 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.

Additional Information

You experience these additional symptoms:
  • 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 '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: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.

Tags

Platform Service Controller, vCenter Server, hostname, IP address

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 37 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 37 Ratings
Actions
KB: