Changing vCenter to different IP address/subnet

[abugeja]

I need to change the IP address of our vCenter server as its moving to a different subnet. Has anyone had experience doing this? I assume ones the network details are changed all ESXi/VMs should reconnect to vCenter because it uses DNS and IP.  I did see one article where its mentioned it isnt supported from VMware either.

[asajm]

Hi abugeja​

Please check this articles

VMware Knowledge Base

How to change vCenter and vSphere IP Address ( embedded PSC ) - Virtualblog.nl

[Ajay1988]

If VC installation was done using FQDN ; then you can change the IP without issues and that will be supported by VMware.

Validate that the PNID is FQDN .

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 localhost

Windows:  "C:\Program Files\VMware\vCenter Server\vmafdd\vmafd-cli.exe" get-pnid --server-name localhost

The below KB will be helpful to change the Managed IP for ESXi cfg .

VMware Knowledge Base

[abugeja]

Thanks Ajay1988​. I checked the vCenters with this command and both are configured with their FQDN.

[abugeja]

Thanks asajm​. I have confirmed both vCenters are configured with their FQDN. It is concerning that the hosts will be in a disconnected state after the vCenter IP address is changed. Does anyone know if this always happens if you change the vCenter IP address  or just a chance. I always thought vCenter & ESXi hosts used only FQDN/DNS to talk to each other.

[asajm]

abugeja​

The link explains that and which I have attached above

[Ajay1988]

Thats because the vpxa configuration holds the VC-IP and that is by design.

[abugeja]

i am going to test this process out in the lab environment to ensure all is ok before going into production

Any tips anyone can offer? Production environment has around 80 ESXi hosts that will need to be updated once vCenter has had its IP address changed. SSL certificate will also need to be updated and applied again.

Im thinking maybe there is less risk if i just build a new vCenter then migrate all the VMs and ESXi over to it might be easier. It will just take longer to do