Integrate > Third Party Integrations > EMC Control Center (ECC) Integration > Impact Analysis Rules

Impact Analysis Rules

The Storage_Basic package contains basic impact analysis rules to enable impact analysis and root cause analysis in UCMDB. These impact analysis rules are templates for more complex rules that you can define based on business needs.

All impact analysis rules fully propagate both Change and Operation events. For details on impact analysis, see "Impact Analysis Manager Page" and "Impact Analysis Manager Overview" in the Modeling section of the UCMDB Help.

To access the Storage_Basic package: Administration > Package Manager. For details, see "Package Manager" in the Administer section of the UCMDB Help.

Note Impact analysis events are not propagated to Fibre Channel Ports for performance reasons.

This section includes:

ClosedStorage Array Devices to Storage Array

This impact analysis rule propagates events between Logical Volumes, Storage Processors, Fibre Channel HBAs, and Storage Arrays.

ClosedHost Devices to Host

This impact analysis rule propagates events between Fibre Channel HBAs and Hosts, and Logical Volumes on the Host.

ClosedLogical Volume to Logical Volume

This impact analysis rule propagates events on a Logical Volume contained in a Storage Array to the dependent Logical Volume on the Host.

ClosedFC Switch Devices to FC Switch

This impact analysis rule propagates events from a Fibre Channel Port to and from a Switch. The event is also propagated to the associated Storage Fabric.

Note Although shown in the preceding graphic, the ECC job does not discover Storage Fabrics. The rule represented by this query is used without Storage Fabrics.

ClosedFC Port to FC Port

This rule propagates events on a Fibre Channel Port to another connected Channel Port.

Example Scenario of HBA Crashing on a Storage Array

  • The event propagates from the HBA to the Storage Array and the Logical Volumes on the Array because of the Storage Devices to Storage Array rule.

  • The impact analysis event on the Logical Volume then propagates to other dependent Logical Volumes through the Logical Volume to Logical Volume rule.

  • Hosts using those dependent Logical volumes see the event next because of the Host Devices to Host rule.

  • Depending on business needs, you define impact analysis rules to propagate events from these hosts to applications, business services, lines of business, and so on. This enables end-to-end mapping and impact analysis using UCMDB.

Send Help Center feedback