Query and change the Platform Services Controller being used by vCenter Server in vSphere 6.0
Here’s a quick guide on how to query and change the Platform Services Controller (PSC) being used by vCenter. Querying for the in-use PSC is possible on vCenter 6.0, but changing the PSC is only possible on 6.0 Update 1 or newer. Note that I performed these steps on the vCenter Server Appliance (VCSA), and while I have also included some commands for a Windows-based vCenter server, I haven’t tested them myself.
Query the PSC being used by vCenter Server
There are two ways to identify this information: via the appliance console or SSH session, and via vSphere Web Client.
Option 1: via the appliance console or SSH session
On a VCSA
On a Windows vCenter
Option 2: via the vSphere Web Client
In the vSphere Web Client, navigate to the server’s Advanced Settings (vCenter > Manage > Settings > Advanced settings) there is a property called config.vpxd.sso.admin.uri. The value of this property is the PSC that vCenter is currently using.
Change (repoint) the PSC being used by vCenter Server
This step is a bit more detailed, as it depends on whether you are changing/repointing between PSC’s in a single SSO site, between SSO sites, or moving from an embedded PSC to an external PSC, and also whether you are using a VCSA or a Windows-based vCenter Server. For this reason I’ll link directly to the VMware documentation for each scenario.
Option 1: Repointing within a site (KB 2113917).
- Connect to the VCSA console, or via SSH.
- Enable the shell (if necessary) and enter it.
- Run the vmafd-cli command.
1/usr/lib/vmware-vmafd/bin/vmafd-cli set-dc-name --server-name localhost --dc-name systemname_of_second_PSC
- Restart the PSC services.
Option 2: Repointing between sites (KB 2131191).
Review the KB article for a full set of steps.
Option 3: Repointing from an embedded PSC to an External PSC (KB 2148924).
Review the KB article for a full set of steps.
comments powered by Disqus