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 |
|
- Configure Custom Correlations
- Configure a Correlation Rule
- Configure a Parent Incident Filter for a Correlation Rule
- Configure a Child Incident Filter for a Correlation Rule
- Configure a Correlation Filter
- Correlation Rule Example
- Configure a Causal Rule
- Configure a Child Incident for a Causal Rule
- Configure a Child Incident Filter for a Causal Rule
- Configure a Source Object Filter for a Causal Rule
- Configure a Source Node Filter for a Causal Rule
- Causal Rule Example
Configure a Correlation Filter
Note See Help → Documentation Library → Release Notes, and locate the Support Matrix link for Correlation Filter limitations.
When correlating groups of incidents under a Parent incident, you must specify the Correlation Filter that defines the relationship requirements that must be met before the incidents are correlated. The Correlation Filter tab enables you to use the Filter Editor to define these relationship requirements. See Valid Operators in the table that follows for examples of valid Correlation Filters.
- You can use Custom Incident Attributes, attributes for an incident's Source Node or Source Object, or both to define how matching incidents should be considered for the Correlation Rule. See Valid Attributes for more information.
-
When specifying Attribute names and values, NNMi uses the type to determine a match. For example, if the Attribute type is numeric, NNMi does a numeric comparison. If the Attribute type is textual, NNMi does a lexographical string comparison. In all cases, when you use the like or not like operator, NNMi uses a lexographical string comparison. Click here for more information about Attribute types:
ifIndex
andifSpeed
are numeric Attributes.- Any Attribute name that begins wtih "is" (
isSnmpInterface
,isSnmpNode
,isNnmSystemLocal
) represents a Boolean Attribute. - All other Attributes are textual.
- Each set of expressions associated with a Boolean Operator (for example,
AND
) is treated as if it were enclosed in parentheses and evaluated together. - View the expression displayed under Filter String to see the logic of the expression as it is created.
-
The
AND
andOR
Boolean Operators must contain at least two expressions. - The placement of your cursor and the subsequent text that is selected is important when performing operations using the Additional Filters Editor. For example, you append to or replace, the expression that is selected.
- The placement of your cursor and the subsequent text that is selected is especially important when adding your Boolean operators. See Add Boolean Operators in the Additional Filters Editor for more information.
- Filter Editor Options: AND, OR, NOT, EXISTS, NOT EXISTS
- Filter Expression (Attribute, Operator, and Value)
- Click the item you want to move before dragging it to a new location.
- As you drag a selected item, an underline indicates the target location.
- If you are moving the selection up, NNMi places the item above the target location.
- If you are moving the selection down, NNMi places the item below the target location.
- If you attempt to move the selection to an invalid target location, NNMi displays an error message.
Button or Feature | Description |
---|---|
Append | Appends the current expression (Attribute, Operator, and Value) to the selected expression already included in the filter string. |
Insert | Inserts the current expression (Attribute, Operator, and Value) in front of the cursor location within the Filter String. |
Replace | Replaces the selected expression with the expression displayed Left or Right Expression. |
AND |
Inserts the AND Boolean Operator in the selected cursor location. Note View the expression displayed under Filter String to see the logic of the expression as it is created. |
OR |
Inserts the OR Boolean Operator in the current cursor location. Note View the expression displayed under Filter String to see the logic of the expression as it is created. |
Delete |
Deletes the selected expression. Note If the Boolean Operator is selected, the Filter Editor deletes all expressions associated with the Boolean Operator. |
Drag and Drop |
You can drag any of the following items to a new location in the Filter String: When moving items in the Filter String, note the following: |
See Correlation Rule Example for a step-by-step example of how the Subinterface Custom Correlation Rule provided by NNMi was created.
To configure a Correlation Filter:
-
Navigate to the Custom Correlation Configuration form:
- From the workspace navigation pane, select the Configuration workspace.
- Expand the Incidents folder.
- Select Custom Correlation Configuration.
- Navigate to the Correlation Rules tab.
- From the Correlation Rules table toolbar, do one of the following:
- To create a Correlation Rule, click the New icon, and continue.
- To edit a Correlation Rule, click the Open icon in the row representing the Correlation Rule you want to edit, and continue.
- To delete a Correlation Rule, click the Delete icon.
- Navigate to the Correlation Filter tab.
-
Create your Correlation Filter (see Filter Editor Settings).
Filter Editor Settings Setting Description Attribute The Attribute on which NNMi searches. See Valid Attributes below for a description of valid Attributes.
Operator Use this Operator to establish the relationship between the Attribute and Expression. See Valid Operators in the table below for the description of each valid Operator. Expression Use the Expression to complete the criteria for the required relationship between the parent and child incident configurations. See Valid Expressions below for more information.
- Click Save and Close to save your changes and return to the previous form.
Attribute | Description |
---|---|
Attribute |
The Attribute on which NNMi searches. Valid attributes other than Source Node attributes depend on the Incident's Source Object. NNMi checks the Source Node as well as the Source Object for any Capability value. Note the following when specifying Attributes:
Possible Source Object choices are as follows:
|
Operator | Description |
---|---|
= |
Finds all values equal to the value specified. Click here for an example.
Correlate the incidents Configure a Child Incident Filter for a Correlation Rule if the
|
!= |
Finds all values not equal to the value specified. Click here for an example.
Correlate the incidents if the
|
< | Finds all values less than the value specified. |
<= | Finds all values less than or equal to the value specified. |
> | Finds all values greater than the value specified. |
>= | Finds all values greater than or equal to the value specified. |
is not null | Finds all non-blank values. |
is null | Finds all blank values. |
like |
Finds matches using the syntax defined for Java regular expressions. See the Pattern (Java Platform SE6) API documentation at: Note To include literal string values in the Value attribute, enclose the string value in \Q<literal_value>\E . The period asterisk (.*) characters mean any number of characters of any type at this location. The period (.) character means any single character of any type at this location. |
not like |
Finds all matches that do not have the values specified using the syntax defined for Java regular expressions. See the Pattern (Java Platform SE6) API documentation at: Note To include literal string values in the Value attribute, enclose the string value in \Q<literal_value>\E . The period asterisk (.*) characters mean any number of characters of any type at this location. The period (.) character means any single character of any type at this location. |
Attribute | Description |
---|---|
Expression |
The value or pattern for which you want NNMi to search. Note the following:
|
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 network-management-doc-feedback@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: