Dear community I need your help with understanding the following behavior.
As we all know, BMC Discovery (we have version 11.3) has the ability to detect the impacted components such as for example Clustered systems. Let’s imagine we have a cluster of 2 hosts. This basically gives us a hint, that if one of those 2 nodes will go down, another one shall take over and the cluster shall in theory be operable, however with 50% of its capacity and therefore the impact shall be visible in the application model (if we add the cluster to it). That’s would be pretty logical.
Also, I found the following in the documentation: Syncmapping block - Documentation for BMC Discovery 11.3 - BMC Documentation where you actually see the following text:
ImpactWeightattributes can be used to create impact relationships. They specify impact direction and percentage respectively. For example, an ImpactWeight of 25 might be appropriate when representing an impact relationship between a BMC_ComputerSystem and BMC_Cluster, where there are four computers in a cluster. The value assigned to Impacted must be the Source or Destination CI appearing in the same definition.
Source := computersystem,
Destination := cluster_ci,
Name := "CLUSTEREDSYSTEM",
Impacted := cluster_ci,
ImpactWeight := cluster_rel.impact_weight
This is basically what we are trying to achieve here, however I could not locate where in the OOTB syncmapping Discovery maps Weights.. I started to dig further down and found another community post where a BMC employee stated that BMC Discovery "Discovery synchronization mapping does not set impact weight": Clusters and weight
More than that, it has been an article that describes the behavior of CMDB Normalization rules that sets the value to ImpactWeight attribute: Atrium Impact Simulator, AKA AIS and the Weighted Cluster mistery
So here I can clearly see a missmatch in documentation vs few topics and answers within them. In my opinion there is only one way to determine Weights in clustered systems - via Discovery. However, there are OOTB rules in CMDB that are active and that sets ImpactWeight to 100 to basically everything. Just configuring those rules doesn't make any sense, as we can't decide on the impact of the device if we have only that device information and nothing else.. This makes Impact Analysis impossible to achieve.
I am lost with above and need some clarification. Has anyone succeeded with Application Modelling that could use Impact Analysis in CMDB in order to simulate the impact ? If yes - would you please share your expereince with me?
Thanks in advance.