Recently, I had a customer who had one of the PSC’s in their cluster lose its database. We are still investigating how this occurred since it was paired to another PSC and this environment is mostly untouched as it is not in production yet.
Thankfully, it is faster to redeploy a new PSC and re-add it to the cluster than analyze a downed PSC for hours on end. If you and your team wish to do investigative work, make sure to pull a support bundle down from the VAMI before doing these steps.
|
1 |
/usr/lib/vmware-vmafd/bin/vmafd-cli get-ls-location --server-name localhost |
|
1 |
cmsso-util repoint --repoint-psc PSC-FQDN |
|
1 |
cmsso-util unregister --node-pnid BROKEN-PSC-FQDN --username administrator@your-sso-domain |
|
1 |
/usr/lib/vmware-vmdir/bin/vdcleavefed -h BROKEN-PSC-FQDN -u administrator |
If completed successfully, you should see the message:
|
1 2 |
vdcleavefd offline for server BROKEN-PSC-FQDN Leave federation cleanup done |
