Create an infrastructure relationship for related CIs

Infrastructure relationships show CIs that are connected to a application service but are not necessary parts of the service. Infrastructure relationships are only available for application services.

始める前に

Role required: evt_mgmt_admin

このタスクについて

When you create a CI infrastructure relationship, the information is stored in the Infrastructure Relations [em_impact_infra_rel_def] table. When alerts generate, the related CI accompanies the application service information on the Event Management dashboard and in the impact tree. Additional information for the related CIs only appears on a related dependency view map for the application service. The following default infrastructure relationships are available.

表 : 1. Default infrastructure relationships

Infrastructure relationship	Impact rule	Description
cmdb_ci_appl	OS Cluster Member	Shows alert impact between hardware and software applications.
cmdb_ci_esx_server	Infrastructure Dependencies	Shows alert impact between VCenter and ESX clusters.
cmdb_ci_kvm	Infrastructure Dependencies	Shows that alert impact on Linux Kernel-based Virtual Machine (KVM) connectivity.
cmdb_ci_vm_zones	Infrastructure Dependencies	Shows alert impact on the Solaris VM zones.

For example, based on of the cmdb_ci_vm_zones Infrastructure relationship definition, Event Management adds ZoneServer@mmp1 to the application service. The Containment rule manages impact severity on alerts.

図 : 1. Related CIs appear on the BSM

手順

1. Navigate to All > Event Management > Administration > Infrastructure Relations.
2. Click New.
3. Fill in the fields, as appropriate.

   表 : 2. Infrastructure Relations form

   Field	Description
   Child Type	The table that contains data about the child entity.
   Parent Type	The table that contains data about the parent entity.
   Relation Type	The relationship between the child and parent entities.
   Impact Direction	The impacts direction to show on the application service map. From Child to Parent: When an alert is regarding a child, show the impact on the parent. From Parent to Child: When an alert is regarding a parent, show the impact on the child entity.
   Impact Rule	The impact rule to calculate infrastructure relationships: OS Cluster Member : Determines how host cluster members affect the overall cluster status based on a percentage or number of cluster members. For example, if a three-host cluster requires 60% Influence to set the severity of Major, each member has 20% Influence (60% divided by 3). The severity of the entire cluster can only change to Major when two or more cluster members have a severity of Major. The entire cluster is also considered to be down. Application Cluster Member : Determines how application cluster members affect the overall impact of the cluster. For example, if a three-member cluster requires 90% Influence to set the severity for the entire cluster to Major, each member has 30% Influence (90% divided by 3). The severity of the entire cluster can only change to Major when all three members have a severity of Major. Infrastructure Dependencies : Determines the definition of impact propagation for CIs in infrastructure relationships. CI Application Service: Determines how impact applies to parent or child entities that are part of an application service. CI Parent in Application: Sets impact only on the parent entity. Inclusion: Determines the impact on entities with a Contains relationship. This rule is read-only. Network Path: Determines how impact applies to parent or child entities that are part of a traditional network. Storage Path: Determines how impact applies to parent or child entities that are part of a storage network. CI Impact : Applies to application services. Determines the relationship between service members. The impact from child to parent CIs is always 100%. For example, the parent impact severity is derived from the child CI with the highest severity.

4. Click Submit.