Hi Jacek,
That means that the Manager knows details about a now non-existing cluster which was prepared earlier but was not properly removed. What might have happened is:
- you created cluster
- prepared it in manager
- removed the hosts (if there was any)
- deleted the cluster from vCenter, but did not unprepare first from manager
Now what you may do is check the switch/cluster mappings with REST API calls :
run :
GET https://<vsm-ip>/api/2.0/vdn/map/cluster
then you should get a list clusters and mapped distributed switches as a preparation.
Also you can execute (since you know the cluster MoRef(domain-c25392):
GET https://<vsm-ip>/api/2.0/vdn/map/cluster/<clusterID>
If you get switch details for this non-existing cluster then you can try to remove the mapping :
DELETE https://<vsm-ip>/api/2.0/vdn/cluster/<ClusterID>/switches/<SwitchID>
Note: replace the variables between <> accordingly.
For help on the above REST calls and how to use them see the vShield API Programming Guide
If that does not help then open ticket to remove the stale entries from the database manually.
HTH,
Roland