|
|
|
You can embed special characters when you do not know the exact value. Use the asterisk wildcard character to match any number of characters. The pattern must match the discovered data in the same sequence, and spaces are significant.
For example, enter 10.*.*.* as the Planned Value to match any IP addresses that begins with 10. and has two periods that follow any value between the periods.
For example, the inbound server_type value contains Windows 2003 (WIN32) 5.2.Service Pack 2 (Build 3790) Intel x86. To verify this value, specify a planned value of * Service Pack 2 * in the change specification.
A word at the beginning of the planned value indicates that the discovered value must start with that value. Similarly, an asterisk at the beginning of the planned value indicates that the discovered value can begin with any value and end with the value specified following the asterisk.
The following table provides examples about how to use the asterisk:
|
Planned Value |
Discovered Value |
Match or No Match |
|---|---|---|
|
*a* |
b |
No Match |
|
*a* |
a |
Match |
|
*a* |
aba |
Match |
|
*a* |
bab |
Match |
|
a* |
a |
Match |
|
a* |
ab |
Match |
|
a* |
ba |
No Match |
|
*a |
a |
Match |
|
*a |
ab |
No Match |
|
*a |
ba |
Match |
A pattern that begins with an exclamation point results in the negation of the value. You can only use the exclamation point as the first character in the pattern. For example, you cannot use a pattern of 10.!*.*.*.
To compare numeric values contained within string values, use greater than (>) or less than (<) as the first character in the planned value. If there is a leading exclamation point, it must be the second character.
Important! CACF ignores leading or trailing nonnumeric values in the discovered value and planned value patterns.
The following table provides examples about how to use the exclamation point, and the greater than and less than symbols:
|
Planned Value |
Discovered Value |
Match or No Match |
|---|---|---|
|
>200 |
aaa 201 bbb |
Match |
|
>200GB |
aaa 200 bbb |
No Match |
|
>200GB |
300 GB |
Match |
|
!<200GB |
200 Bytes |
Match |
|
!<200 |
200 Bits |
Match |
If you do not know the planned value in advance, but the value may change, you can set the status of the change specification to Use Discovered Value. This behavior requires discovery to update the CI before CACF considers the change specification as validated. You require this behavior for numeric fields and SRELs where an asterisk cannot be accepted as a planned value.
To help you with setting the planned value, the Discovered Attribute History tab lists all values that were recently discovered by an MDR, and whether were actually authorized, or loaded into the CMDB. This tab displays the format, case sensitivity, and other information about values so that you can determine an appropriate planned value pattern.
| Copyright © 2012 CA. All rights reserved. | Tell Technical Publications how we can improve this information |