Since a vCenter has a connection to a single PSC it’s important to understand how to move between PSC’s and deploy new ones when old ones have failed.
Once installed check for working vCenter
Then login via ssh and check which PSC is being used
Let’s repoint it to psc2.griffiths.local
cmsso-util repoint --repoint-psc psc2.griffiths.local
Now we are pointing to psc2 at site1.
As you can see we have repointed the psc from 1 to 2 at the same site:
So what do you do when all your PSC’s at a site have failed?
Install a new PSC pointing to a remaining site psc we will use psc3 at site2 to create a new PSC5 at site1.
So we are creating:
After the PSC is installed it will replicate with psc3.griffiths.local only.
Now we can repoint the vc to psc5 at site1.
Login to the vCenter web client to test working authentication via psc5
And it’s working
William Lam posted a script to
For those who don’t want to read the script it’s very simple it runs on the vCenter appliance and checks the PSC web page for a
Remove an old PSC
Login to any PSC and type the following command:
cmsso-util unregister –node-pnid OLD_PSC_Name –username administrator@sso_domainname
So to remove psc1.griffiths.local I would type:
cmsso-util unregister –node-pnid psc1.griffiths.local –username firstname.lastname@example.org
© 2017, Joseph Griffiths. All rights reserved.