1 Reply Latest reply on Jun 27, 2019 1:35 AM by RShankar22

    Deleted (decomissioned) vSphere Cluster without doing via NSX-V first - now Service Composer won't sync. How to delete this object from backend?

    chicaneau Lurker

      Hi All,


      I deleted a (decomissioned) cluster from vSphere but did not delete it via NSX-V (v6.3.3) first - now I have an orphaned object in the backend that is preventing Service Composer from syncing.




      “,,The requested object : domain-c648626 could not be found. Object identifiers are case sensitive. Service Composer is out of sync. No changes from Service Composer will be pushed to Firewall/Network Introspection,”


      I have tried recreating the cluster however the unique identifier is still preserved in the NSX Manager. Any ideas how to delete this from the backend? I have logged it with GSS, however this is prod and need to get it sorted ASAP.