Introduction › Service Concepts › Propagation Types › Configure Default Propagation Policies

Configure Default Propagation Policies

Each relationship type has a predetermined propagation type. You can view the relationship mappings and change the parameters of default propagation policies for each relationship that maps to custom or operative propagation.

Important! When you change the default propagation policy parameters for a relationship type, any instance of that relationship in a service model that has not been manually overridden acquires that policy’s parameters by default.

The changes will affect all new relationships/propagations from that moment on, but will not cause the reevaluation of the policies currently in SA Manager’s memory. To effect that, you have to restart the CA SOI Application Server.

You must close the Service Modeler to change default propagation policy.

Note: A propagation policy determines how impact is derived and propagated. For more information about each policy type, see Define Operative Propagation Policy and Define Custom Propagation Policy.

Follow these steps:

1. Select Tools, Propagation Policies from the Operations Console.

   The Default Propagation Policy dialog opens.

   Note: If the Service Modeler is currently active (in any user session), a warning dialog opens stating that the Default Propagation Policy dialog is read-only. Close all Service Modeler sessions and reopen the dialog to make changes.

2. Click the set link next to the value in the Propagation Rule column for the Is Affected By or Is Evolution Of relationship row, which have custom propagation defined.

   The Default Thresholds for Custom dialog opens.

3. (Optional) Select the Automatically Maintained check box to automatically change the relationship to Is Affected By or Is Evolution Of and apply the custom propagation policy when new CIs are added to a group that uses custom propagation. Auto-maintenance applies to relationships added by both manually editing a service and through automation by service discovery or service import.

   Note: You can set Automatic Policy Maintenance for the Modeler operation to on by default in the Set Preferences dialog.

4. Select one of the following from the Policy Type drop-down list:

   Average

   Sets the impact of the parent item based on the average impact values of CIs associated with the policy.

   Percentage

   Sets the impact of the parent item based on a percentage of CIs that have the impact specified in the rule.

   Any

   Sets the impact of the parent item when any CIs associated with the policy have the impact specified in the rule.

   All

   Sets the impact of the parent item when all CIs have the impact specified in the rule.

   Default: Any

   The text of the rules on the dialog changes to reflect the selected policy type.

5. Complete the following fields and settings for each rule that you want to create:

   % of items

   (Percentage type only) Defines the percentage of items that must exceed the impact threshold to meet the rule criteria.

   Threshold

   Defines the impact threshold. The appropriate amount of CIs (as defined by the policy type) must meet or exceed the impact threshold to meet the rule criteria. Define a number between 0 and 40. The impact numbers translate to the following impacts:

   • 0: Operational
   • 1-10: Slightly Degraded
   • 11-20: Moderately Degraded
   • 21-30: Severely Degraded
   • 31-40: Down

   Set Severity

   Defines the severity to assign to the parent item if the rule criteria are met.

   The text for each rule changes to reflect the new settings. Define as many of the four available rules as the policy requires.

6. Click OK.

   The rule changes in the Propagation Rule column for the Is Affected By or Is Evolution Of relationship. You can assign different default policy parameters for each relationship type. The new default custom policy is assigned to all new custom propagation assignments and existing custom propagations that use the associated relationship, including those that previously used a default custom policy. Customized default propagations are not recalculated; they take effect from the point they are customized.

   Note: CIs in maintenance mode are excluded from custom policy calculations related to average or percentage.

7. Click set next to any value in the Propagation Rule column for relationship rows that map to Operative propagation.

   The Default Threshold for Operative dialog opens.

8. Set the default threshold value at which impact starts to propagate to parent CIs, and click OK.

   The rule changes in the Propagation Rule column for the relationship, and the new default operative policy is assigned to all new and existing operative propagation assignments of the specific relationship, including those that previously used a default operative policy.

9. Click Save.

   The propagation changes are saved.

Changes take effect for ensuing alerts by default. To recalculate the impact of existing alerts, restart the CA SOI Manager and CA SOI User Interface.