I need to redirect my vCenter. There is a good KB article here, so I will only add complimentary info.
The first step is to enable the BASH Shell and SSH.
Once done, you’re ready to login remotely. I use Putty as my favourite SSH tool. From the Command>, simply type shell.
That will take you to BASH Shell, which you have enabled earlier.
The first step is to change the setting. You issue the command:
/usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-name --server-name localhost --dc-name name_of_second_PSC
I used the FQDN name. Here it is in my case:
/usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-name --server-name localhost --dc-name core-platform-sc-1.core.lab
As you can see below, there was no feedback. So I’m not sure if it’s successful or not. I guess it is as it’s a simple change of a property.
The next thing is to essentially reboot. You can do it via GUI, or just from the CLI as I did above. The good thing about the CLI is it shows more details. As you can see below, it’s a long list of services.
After a good few minutes, it finished, and you get the shell again.
The next is to start the services. That’s all you are supposed to do. Your story should end here. MIne did not 🙂
After that, I could not login to my vCenter using my AD credential. I tried both the C# client and Web Client. I also saw that the Web Server is initializing, as you can see below. I waited for it to complete. After it was settled down, I still could not login. I could login to the new PSC, but I do not see any vCenter.
I found out that I needed to register my PSC to AD. I thought this step was taken care off when I deployed the new PSC, as I deployed it to the same Domain and Site. I checked and it was joined. As you can see from the following screenshot, it was blank. Luckily, to register to domain is pretty simple.
You need to reboot. Once done, it should look something like this.
That’s all it took to redirect a vCenter to a new PSC. Happy redirecting!