Windows Cluster Discovery creating extra Server CIs with cluster virtual IPs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2020 09:49 AM
In the process of running Discovery on a two-node Windows cluster, four server CIs are being created: One for each node, plus one with the Cluster IP address and one with the availability group IP address. The final two are being added via Credentialless Discovery because an attempt to classify them via WMI throws an error that the result file could not be fetched.
Discovery does appear to be classifying the cluster correctly since the cluster, nodes and related resources are created, but are these additional server CIs with the cluster virtual IPs expected behavior? If not, thoughts on how I could prevent this? Thanks!
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2020 10:36 AM
Exactly how its designed to work!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-18-2020 01:31 PM
Doug - thanks for the reply. I had read the documentation you linked but was unable to identify specifically where these extra Windows Server CIs are referenced. A follow-up if I may just to ensure I'm completely understanding.
I have a two-node cluster (and I'm removing the Availability Group from the equation because I'm sure the answer is the same for the Cluster IP).
ServerA (ex. IP of 10.10.10.11)
ServerB (ex. IP of 10.10.10.12)
ClusterA (ex. IP of 10.10.10.10)
The cluster is correctly added to cmdb_ci_win_cluster. The various resources are correctly added to cmdb_ci_win_cluster_resource. The two nodes are added to cmdb_ci_win_cluster_node and cmdb_ci_win_server. The cluster IP address is added to cmdb_ci_cluster_vip. All of that looks great and makes sense.
The part that I'm having a hard time wrapping my head around is why the cluster IP address is also generating a record in cmdb_ci_win_server and through Credentialless Discovery. It's not a server but a VIP for the cluster.
I've attached a visual of where I'm getting tripped up, as well. Sometimes pretty pictures help me understand.
(Completely unrelated, but I successfully created a pattern for the first time a couple days ago after watching your videos. They're awesome and I'm appreciative of your time!)
