Cluster Awareness
Cluster awareness was first introduced in BMC Discovery 11.x series. You are referred to Discovering Clusters for further information.
Clustering Technologies and Key changes may fall into several types:
- Clustering Platform like Microsoft Cluster and Veritas Cluster that generate a Cluster Node. In general, the keys of the Cluster nodes do not change.
- Clustered Software - products that run on the Clustering Platforms . These are modeled as SoftwareInstance nodes. In previous releases, the SIs were modeled running on Host nodes, and had keys based upon the Host key. Now, if they are running on a cluster, they are modeled running on the Cluster node, and have keys based upon the Cluster key. That means that instances of these products that run on clusters have changed keys. Instances that do not run on clusters do not have changed keys (unless the patterns have also been updated for another reason, which would be listed in the usual updates section).
- Software Performing Clustering. Products that implement their own Clustering Scheme without using a Clustering Platform, for example BMC Discovery / ADDM itself. Previously, if the cluster was modeled, it was a represented as a second-order SoftwareInstance node. Now, it is modeled as a SoftwareCluster node. In general, the SoftwareCluster is given the same key that was previously given to the SoftwareInstance. (When synchronizing to the CMDB, SoftwareCluster is mapped to BMC_Cluster, where previously the second-order SI was mapped to BMC_ApplicationSystem.)
The following tables contain links to the information about cluster aware software products identified by patterns distributed as part of Technology Knowledge Updates.
Clustering Platform
Clustered Software
Software Performing Clustering
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*