vCenter 6.5 PSC Repoint Limitations

By | November 21, 2016

Hi all,

This is just a quick note to let you all know of a limitation with vSphere 6.5. Repointing of a vCenter Server to a Platform Services Controller (PSC) in another vSphere SSO domain SITE is not supported. Please see the caution at the top of this VMware KB article.

Note: As of 21/11/2016, the KB article for repointing a VC to a PSC WITHIN the same SSO domain site (see here) also has a caution to say it is not supported with 6.5. I believe this is a mistake in the KB article, as the 6.5 documentation has steps on how to repoint within the same SSO site, and I’ve reached out to the product manager Adam Eckerle who also believes this is an error and is investigating.

A quick bit of background for those interested…

In vSphere 5.5, we had the ability to repoint services between SSO sites, domains, etc. It was quite flexible.

In vSphere 6 pre Update 1, we were only given the ability to repoint VC servers within the same SSO Site.

From vSphere 6U1, we were given the ability to repoint VC servers to any PSC in the SSO domain, same site or different site. We could not repoint the vCenter Server to a PSC in a different SSO domain.

And now with 6.5, it seems we have taken a step back again and we’re now back to how it was in 6.0GA, which is we can repoint the VC between PSC nodes in the same SSO site, but not cross site and not to a PSC in a different SSO domain.

Because of these limitations and changes with each version, you need to give your upgrade process some thought prior to making any changes. You might need to do some remediation and collapsing work prior to upgrading, as you will find that after you upgrade you might not have the tools and abilities at your disposal to reconfigure the architecture to your desired state.

2 thoughts on “vCenter 6.5 PSC Repoint Limitations

  1. Haikal Shiddiq

    Hi Matt Allford,

    I have question related limitation on VCSA v6.5. In your statement
    “And now with 6.5, it seems we have taken a step back again and we’re now back to how it was in 6.0GA, which is we can repoint the VC between PSC nodes in the same SSO site, but not cross site and not to a PSC in a different SSO domain.”

    In my existing using VCSA 6.5 Update 1 embedded deployment on 2 sites and i want to change to external deployment. Can i use both PSC to using 1 SSO domain and 1 Site Name and from VCSA each sites repointing to PSC each sites to make as Enhanced Linked Mode ?

    Please answer because very much effort to deploy again all component of VCSA 6.5 using external deployment and configuring again.

    Thanks

    Regards,

    Haikal

    Reply
    1. Matt Post author

      Hi Haikal,

      Thanks for your comment.

      If you currently have two embedded deployment in 2 sites, they will be in their own vsphere.local domains. At this point in time, there is no way to merge these into a single vsphere.local domain.

      I suspect you would be best doing something such as:

      1) Externalise PSC in site 1, so you have a vCenter Server with External PSC
      2) Deploy a new PSC in Site 2
      3) Deploy a new vCenter Server in Site 2, pointed to the PSC in site 2. At this point you now have 1 external PSC in each site and one VC in each site, pointing to the local PSC
      4) Migrate hosts, VMs and other settings from the old VC in site 2 to the new VC in site 2
      5) Decommission the old embedded VC at site 2

      Does that help?

      Cheers, Matt.

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *