This documentation supports the 21.3 (12.3) version of BMC Discovery.

Discovering clusters

BMC Discovery enables you to discover cluster instances and their configuration in your IT environment. BMC Discovery can discover configuration data for various clustering technologies, such as Microsoft Cluster Server, Symantec Veritas Cluster Server, and so on. For more information, see the BMC Discovery content reference page, Cluster Awareness.

Related topics

Configuring-discovery-of-target-systems

Configuring-credentials

Requirements for cluster discovery

To perform a full discovery of your clustering environment, BMC Discovery requires credentials depending on the method that is used to discover a specific clustering technology. For example, discovering a Microsoft Cluster Server on Windows requires different credentials than discovering Oracle Clusterware on UNIX. See Configuring-credentials for more information.

Nodes and relationships

BMC Discovery can now discover and model detailed information about clusters by using technology-specific methods such as WMI for Microsoft Windows clustering and the command line for Veritas clustering. When BMC Discovery finds a host that is a member of a clustering environment, a Cluster node is created. Furthermore, details such as the number of members in the cluster, services managed by the cluster, and the resources shared by the cluster are also discovered. The information that is discovered is modeled using the following nodes:

  • ClusterMember—Represents a host member in your clustering environment, The node contains the IP address of the member. The address is used to link the ClusterMember to a host.
  • ClusterService—Represents a service that is managed by the given cluster. The node contains the IP addresses and DNS names; this information is used by clients of the service for access purposes.
  • ClusterResource—Represents finer details about the configuration of the clustered service. This node is a shared storage that is used by the service or by the software used to implement the service. For example, the clustered Microsoft SQL Server service contains a SQL Server resource and a SQL Server Agent resource. Each instance of the ClusterResource node can contain any number of attributes, which will later be used to match SIs to ClusterServices.