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 |
|
- Establish Criteria or Relationships for Incoming Incidents
- Correlate Duplicates (Deduplication)
- Deduplication Comparison Parameters Form
- Set Rate (Time Period and Count)
- About Pairwise Configurations
- Incident Pair (Pairwise) Configurations Provided by NNMi
- Configure Pairwise Configurations
- Pairwise Configuration Example
- Rate Comparison Parameters Form
- Suppress Incident Configurations
- Enrich Incident Configurations
- Dampen Incident Configurations
- Configure Custom Correlations
Incident Pair (Pairwise) Configurations Provided by NNMi
NNMi provides the pairwise configurations described in the following table.
Name | Description |
---|---|
CiscoLinkDownUpPair |
Cancels a CiscoLinkDown incident with a CiscoLinkUp incident on the same interface for the same SNMP agent address. This configuration is used for known Cisco devices. |
CiscoModuleDownUpPair | Cancels a Cisco Module Down incident with a Cisco Module Up incident from the same module and SNMP agent address. |
RcAggLinkDownUpPair | (NNMi Advanced) Cancels an RcAggLinkDown incident with an RcAggLinkUp incident from the same Multi-Link Trunk (MLT) Aggregator ID (from the MIB) and SNMP agent address. (Link AggregationProtocols used on Switches to configure multiple Interfaces (Aggregation Member Interfaces) to function as if they were one (an Aggregator Interface). When two Aggregator Interfaces establish a connection, that connection is an Aggregator Layer 2 Connection. The Aggregator Layer 2 Connection appears on Layer 2 Neighbor View maps as a thick line with an Interface icon at each end (representing the Aggregator Interface). or Split Link AggregationLink Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link Aggregation, SLAG, MLAG, or MC-LAG.) |
RcChasFanDownUpPair | Physical Sensor object incident: Cancels an RcChasFanDown incident with an RcChasFanUp incident from the same fan ID (from the MIB) and SNMP agent address. |
RcChasPowerSupplyDownUpPair | Physical Sensor object incident: Cancels an RcChasPowerSupplyDown incident with an RcChasPowerSupplyUp incident from the same power supply ID (from the MIB) and SNMP agent address. |
RcSmltIsLinkDownUpPair | Cancels an RcSmltIstLinkDown incident with an RcSmltIstLinkUp incident from the same SNMP agent address. |
RcnAggLinkDownUpPair | (NNMi Advanced) Cancels an RcnAggLinkDown incident with an RcnAggLinkUp incident from the same Multi-Link Trunk (MLT) Aggregator Link ID (from the MIB) and SNMP agent address. (Link AggregationProtocols used on Switches to configure multiple Interfaces (Aggregation Member Interfaces) to function as if they were one (an Aggregator Interface). When two Aggregator Interfaces establish a connection, that connection is an Aggregator Layer 2 Connection. The Aggregator Layer 2 Connection appears on Layer 2 Neighbor View maps as a thick line with an Interface icon at each end (representing the Aggregator Interface). or Split Link AggregationLink Aggregation with more than two endpoints. Some vendors refer to this as Multi-Chassis Link Aggregation, SLAG, MLAG, or MC-LAG.) |
RcnChasFanDownUpPair | Physical Sensor object incident: Cancels an RcnChasFanDown incident with an RcnChasFanUp incident from the same fan ID (from the MIB) and SNMP agent address. |
RcnChasPowerSupplyDownUpPair | Physical Sensor object incident: cancels a RcnChasPowerSupplyDown incident with an RcnChasPowerSupplyUp incident from the same power supply ID (from the MIB) and SNMP agent address. |
RcnSmltIsLinkDownUpPair | Cancels an RcnSmltIstLinkDown incident with an RcnSmltIstLinkUp incident from the same SNMP agent address. |
SnmpLinkDownUpPair | Cancels an SNMPLinkDown incident with an SNMPLinkUp incident on the same interface for the same SNMP agent address. |
To see or modify these incident pair configurations:
-
Navigate to the Pairwise Configurations view.
- In the workspace navigation panel, select the Configuration workspace.
- Expand the Incidents folder.
- Select Pairwise Configurations.
-
Double-click the row representing the configuration you want to see or modify.
See Pairwise Configuration Form (Correlate Pairs of Incidents) for more information.
- When you are finished, click Save and Close to save your changes.
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: