Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Relationship Page
This page enables you to define the relationship to be created between the original CI and the CIs selected on the CI Selection page of the dialog box.
To access | Click the Relationship button from the Insert Relationship dialog box. |
Important information | When defining multiple relationships, you can define different descriptions and property values for each relationship. Skip the property definitions here and edit each relationship individually after it is created. |
User interface elements are described below:
UI Element (A-Z) | Description |
---|---|
Direction |
Select the direction of the relationship. For some relationship types (for example, Composition, or between a group CI and a monitor CI), only one direction is valid. |
Relationship | Define the type of relationship created between the original CI and the CIs being attached. Select an option from the list. |
Source CI | Displays the name of the CI on the first end of the relationship. This is the CI that you selected in the view. |
Target CI | Displays the name of the CI on the second end of the relationship, that is attached to the original CI. |
UI Element (A-Z) | Description |
---|---|
Actual Deletion Period | The period after which the relationship is deleted when the aging mechanism is enabled. |
Allow CI Update | When the value is set to true, the DFM process automatically updates the relationship. |
Created By | The user name of the administrator who manually created the relationship, where applicable. |
Create Time | The date and time when the relationship was created. |
Deletion Candidate Period | The number of days after which the relationship becomes a candidate for deletion. |
Description | A detailed description of the relationship. |
Destination Network Address | Defined only for route links. Indicates the destination network address to which this route is configured. |
Enable Aging |
If a CI or relationship is not updated or refreshed over a period of time (for example, a CI is not rediscovered by DFM and no manual update occurs), an aging mechanism deletes the CI from the True: the aging mechanism is enabled for this CI or relationship. Default value: false. The default value for DFM CIs is true. Note
|
Last Access Time |
The time that the relationship was last accessed, whether when being updated or being discovered by DFM. This field is only displayed for certain CIs. This parameter is used by the aging mechanism. For details, see CI Lifecycle and the Aging Mechanism. |
Last Modified Time | The date and time when the relationship properties were last updated. |
Must |
When the value is set to true, the child CI is dominant when the percentage rule is used to calculate status for the parent CI. If the CI has low status, the parent must take the child CI status, if necessary overriding the percentage rule calculation. This is useful to give emphasis to an important CI. For example, you might want to define Must for a database CI, so that status is critical all the way up the subtree if the database falls, regardless of the status of the other CIs in the subtree. The must status defined for a relationship applies for that relationship only – it is not used in any other relationships of the child CI. |
Name | A brief description of the relationship. If no value is entered, the relationship type is used in place of the name. |
Note | Enables you to enter other information about the relationship. |
Origin | An ID for the source that automatically created the relationship, or the application where the relationship was created. |
Updated By | The user name of the administrator who updated the CI properties. |
User Label | Enables you to define a display label for the relationship. If no value is entered, the relationship name appears as the default label. |
Weight |
When a weight value is entered, the child CI is given more weight in percentage calculations, when percentage rule is used to calculate status for the parent CI. For example, if a child CI is given a weight of 3, then it has three times more impact on the parent status calculation than its unweighted siblings. The weight defined for a relationship applies for that relationship only – it is not used in any other relationships the child CI may have. |
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: