Verification policies specify the action that CACF takes when an MDR discovers an attribute value, and attempts to update the CMDB with that data. A variance occurs when the inbound data does not match the desired state information, as described in the change specification. A policy search executes to locate a policy that matches both the change order alignment and change specifications. Policies process in an ascending, sequential number order. By default, a compatibility policy is provided to let all updates occur providing the behavior observed in previous releases of CA SDM.
The change verification policy describes how CA SDM responds to the following events:
Specifies that specific MDRs are authoritative for specific attributes. CI attribute updates from unauthorized MDRs can be selectively accepted or rejected
For example, define policies to prevent CA Configuration Automation from updating the IP address of a CI, even if a matching Change Order exists. Allow updates to the IP address to occur only if the source MDR is Spectrum.
Detects and manages updates to CIs when no corresponding Change Order exists. Specify a policy that manages rogue changes that request inserts or updates of CI data.
For example, define a policy whenever a CI named like server* in New York changes, but does not have a matching Change Order, do not update the CI but instead load the data to the TWA.
Detects whenever a Change Order is not implemented correctly.
The policy specifies any of the following actions with the discovered data inbound to the CMDB:
Important! The Configuration and Change Administrators must establish a change verification strategy for your environment. The default policy specifies CACF to allow all changes to all CIs, even if the change is rogue or does not match a change ticket. For more information about implementing a strategy for CACF, see the Administration Guide.
| Copyright © 2013 CA.
|
Tell Technical Publications how we can improve this information |