The conversation on the site has performed something like:
"It's finish."
"Hold on ..."
"It's low."
"Web services say, 'No'".
PSC Cue restarts, vCenter restarts and measures more and more desperately. The service limped like a frog on one leg with a hangover. It was one of those questions where no one really understood why. It was a simple update, right? VMware support has been compromised. Even the level 3 support was a little insecure and he threw a lot of "WTF". Finally, the entire story was canceled when the administrator in question was asked about how he had updated.
I had updated the environment without first updating the PSC, essentially pulling the security base down while it was running. It took several days of VMware to fix it. Meanwhile, scarcity varied. Some people can do the work, so no.
The software is becoming more and more complex to provide new experiences, doubly for the cloud. Unfortunately, the complexity also makes upgrades a little more difficult. As a VMware administrator and well versed in VMware, I thought it was time to talk and help those behind the curve to understand the process of upgrading to VMware 6.5 world, which sings, dances and offers PSC. I hope this will also serve as a template for updating the VMware infrastructure.
With version 5.5 of vSphere came PSC or Platform Services Controller. PSC allows you to link many vCenters without many limitations of previous versions (ie, bound mode).
One of the key tasks of the PSC function is to act as a reverse proxy and SSO (Single Sign-On) infrastructure for vSphere authentication. Everything under a single piece of glass. As a note, all this refers to version 5.5. If for some crazy reason you run more than 5.5, it means that:
Few of this applies to you (a different style of PSC has been installed at this point, in the past)
Seriously, you have to update. Specter / Meltdown patches only go back up to 5.5 for a
Expect to pay a large amount of money for upgrade licenses
By default, vSphere 6.5 has its own local authentication system to manage the vSphere environment and is hosted on the PSC, but it can (and almost always) be replaced by the upcoming Active Directory integration. The PSC can handle multiple authentication systems and is compatible with all commonly used systems (AD, LDAP, local account). VMware did not put the PSC just for fun. It is a modern and extensible authentication system, and should be treated as such. It provides a key element of your cloud support infrastructure. Before the administrator tries to update, the PSC update must be handled with care.
Administrators with only one site can stop reading now because they have reduced complexity by having only one PSC. This means that the update becomes simple and that the update scenario is included in the immediate update.
For the rest of us, that's what you should do.
Sponsored: Continuous Lifecycle London 2018 - Presale Tickets Now Available
