Topology warnings indicate that a Service Discovery policy could lead to one of the following topology issues:
Occurs when a relationship points from a CI to a top-level service node. All relationships must orient from the root service to its child items. For example, this error could occur if you create an automatic relationship policy with a service as the target CI.
Occurs when more than one relationship using different propagation types exists between two CIs or if equivalent policies are applied to the same service. For example, this error could occur if you create a dynamic service with multiple policies using the same target class and different propagation type, or if you create an automatic relationship with multiple policies using the same source and target class with a different propagation type.
Occurs when an item becomes related to itself, two items have separate relationships going in each direction, or when more than two items have a circular relationship structure. For example, this error could occur if you do the following:
Occurs when a policy creates the potential for an overwhelming number of CIs to be added to a service. For example, this error could occur if you create a dynamic service policy with only a USM type but no target filter criteria, or you create a dynamic service policy using a type that has several children in the USM type hierarchy. For instance, creating a dynamic service policy based on the USM type entity with no target filter conditions would add CIs of all USM types to a service and potentially impact SA Manager performance.
Topology warnings appear in the following locations:
You can switch warning display settings in the Set Preferences dialog.
Service Discovery does not prevent the creation of policies that contain warnings. A warning does not mean that the potential problem will definitely occur. If you receive a warning, review the Service Discovery policy to help ensure the policy does not present problems.
|
Copyright © 2013 CA.
All rights reserved.
|
|