Configuring CIs in a manual service as a manual cluster
Configure or modify a CI as a specific CI or a generic CI class in a manual service (that was not discovered automatically) as a manually defined cluster. A manual cluster delivers redundancy capabilities in the cluster and provides continued operations or services of the entire cluster in case of failure of one or more CIs in that cluster.
Once the CI is defined as a manual cluster its impact calculation shows the magnitude of an outage on its children CIs. Impact calculation uses factors such as impact rules and CI relationships to calculate the severity of a generated alert. Impact rules, which are used for impact calculation, estimate the magnitude or severity of an outage based on affected CIs and determines how the impact applies to parent or child entities that are part of an application service.
The magnitude of an outage can be 100% down, 60% affected, 40% impaired, or 20% impaired.
Redundancy is defined in impact rules. For example, you can define that the parent CI is critical if at least two child CIs are critical. The impact from child to parent CIs is not always 100%. If the CIs of all three children are affected, the impact is 100% down.
In a service map, you can configure or modify a specific CI or a generic CI class in a manual service as a manually defined cluster. When configuring as a generic CI class, all the CIs of the selected class in that service are configured the same.