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 |
|
CIAs Added to Closed Management Event Incidents
When the NNMi Causal Engine determines that the conditions that caused a management event incident no longer apply, NNMi sets that incident’s lifecycle state to CLOSED and adds the CIAs listed in the following table to the incident. NNMi console users can see this information in the Correlation Notes field of the Incident form. Lifecycle transition actions can use the values of the CIAs directly.
Name |
Description |
---|---|
cia.reasonClosed |
The reason that NNMi cancelled or closed the incident. This reason is also the conclusion name, for example NodeUp or InterfaceUp. If this field is not set, an NNMi console user closed the incident. To determine the NNMi expected values of the cia.reasonClosed CIA, see How NNMi Closes Incidents in the NNMi help. |
cia.incidentDurationMs |
The duration, in milliseconds, of the outage, as measured by NNMi from when the status goes down and comes back up. This value is the difference of the cia.timeIncidentDetectedMs and cia.timeIncidentResolvedMs CIAs. It is a more accurate measurement than comparing the timestamps of down and up incidents. |
cia.timeIncidentDetectedMs |
The timestamp, in milliseconds, when the NNMi Causal Engine first detected the problem. |
cia.timeIncidentResolvedMs |
The timestamp, in milliseconds, when the NNMi Causal Engine detected that the problem has been resolved. |
NNMi adds the CIAs listed in the previous table to most primary and secondary root cause incidents. For example, a NodeDown incident can have InterfaceDown and AddressDown incidents as secondary root causes. When NNMi closes the NodeDown incident, NNMi also closes the secondary incidents and adds the CIAs with values for each incident context to the secondary incidents.
NNMi does not add the CIAs listed in the previous table to the following default management event incident types:
- Incidents that an NNMi console user closes manually
- Incidents that NNMi closes in response to an object being deleted from the NNMi database
- IslandGroupDown incidents
- NnmClusterFailover, NnmClusterLostStandby, NnmClusterStartup, and NnmClusterTransfer incidents
-
Incidents in the following families:
- Correlation
- License
- NNMi Health
- Trap Analysis
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: