vCenter

 View Only
  • 1.  Orphaned vCenter in PSC

    Posted Sep 19, 2016 03:33 PM

    I'm wondering if anyone has run into this scenario.

    A PSC (PSC1) was deployed and a vCenter (vCenter1) was connected to it but had issues and got deleted etc.

    A new vCenter was stood up and also named vCenter1 and was connected to PSC1

    Upon logging into the web client, there is a warning message stating "Could not connect to one or more vCenter Server Systems: https://vCenter1.domain.local/sdk"

    Now, there are documented measures to remove a vCenter from a PSC, Using the cmsso command to unregister vCenter Server from Single Sign-On (2106736) | VMware KB

    but those instructions seem to conclude that you can use the vCenter server name as the ID:

    cmsso-util unregister --hostId host_Id --node-pnid vCenter_Server_System_Name --username administrator@your_domain_name --passwd vCenter_Single_Sign_On_password

    Question being this, if I were to run this with vCenter1 as the vCenter_Server_System_Name won't it remove both the orphaned vCenter as well as the existing working vCenter?

    Does anyone have a better way to remove just the orphaned vCenter?



  • 2.  RE: Orphaned vCenter in PSC

    Posted Sep 20, 2016 02:10 AM

    Are you saying that you have two VCs with the same name registered to the same PSC? I didn't know this was possible.

    Could you check what VCs are registered with the PSC, one might be known under the IP rather then FQDN / hostname, making them unique so you could use that corresponding name to remove it.



  • 3.  RE: Orphaned vCenter in PSC

    Posted Sep 20, 2016 02:16 PM

    I would love to check that but can't seem to find the documentation to list all vCenters connected to the PSC.

    Can the cmsso-util find these entries?



  • 4.  RE: Orphaned vCenter in PSC



  • 5.  RE: Orphaned vCenter in PSC

    Posted Sep 23, 2016 01:04 PM

    I missed William's posts. Thanks, that was helpful, but as I suspected, there are two entries with a serviceattribute of the exact same vCenter. Spelling is identical including the case.



  • 6.  RE: Orphaned vCenter in PSC

    Posted Sep 23, 2016 05:31 PM

    Probably best to log a case with VMware, or reach out to william on twitter? @lamw



  • 7.  RE: Orphaned vCenter in PSC

    Broadcom Employee
    Posted Jan 09, 2017 08:01 AM

    It is possible that two vCenters with same name can be registered in one PSC. But only one can work and web client report that can not connect to one vcenter(the same name).

    You can find the services by using lstool in psc.

    "%VMWARE_PYTHON_BIN%" "%VMWARE_CIS_HOME%\VMware Identity Services\lstool\scripts\lstool.py" list --url http://localhost:7080/lookupservice/sdk

    This is an example for Windows PSC.

    We are facing the same situation.

    I don't know if the --hostId host_id can help. Every vCenter has unique Node ID (I think it should be host Id in the parameter).



  • 8.  RE: Orphaned vCenter in PSC

    Posted May 22, 2017 11:14 AM

    Did you ever figure out how to remove the orphaned vCenter server? I'm in a similar situation, but only the functional server is shown when using the python script against the lookup service. I've also tried deregistering the functional one, but that only removes the functional one and does not remove the orphaned one. Thanks for the input!



  • 9.  RE: Orphaned vCenter in PSC