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 |
|
Custom Incident Attributes Provided by NNMi (Information for Administrators)
NNMi uses custom incident attributes to attach additional information to incidents.
A subset of CIAs is available for any particular incident. Any relevant CIAs are displayed in the Incident form, on the Custom Attributes tab. There are two categories of possible CIAs:
-
Custom incident attributes
- Provided by NNMi
-
Provided for NNM iSPI Performance for Metrics.
Requires Network Node Manager iSPI Performance for Metrics Software (NNM iSPI Performance for Metrics). To populate performance data in the dashboard views or enhance NNM iSPI Performance for Metrics reports by sharing NNMi configuration settings, install the optional Network Performance Server (NPS).
-
SNMP trap varbinds
Identified by the Abstract Syntax Notation value (ASN.1). Varbinds are defined in MIB files that you can load into NNMi. See Load SNMP Trap Incident Configurations.
The following tables explain the custom incident attributes provided by NNMi.
Name | Description |
---|---|
cia.address |
This attribute value is determined by the Windows:
Linux:
When When See the "Maintaining NNMi" chapter in the Network Node Manager i Software Deployment Reference for more information. |
cia.originaladdress |
This attribute value is determined by the Windows:
Linux:
This Custom Incident Attribute enables you to access both the User Datagram Protocol (UDP) header IP Address and the SNMP Agent IP Address of the managed device. When When See the "Maintaining NNMi" chapter in the Network Node Manager i Software Deployment Reference for more information. |
cia.agentAddress | The IP Address that is stored in the SNMPv1 trap data for the SNMP Agent that generated the trap. |
cia.custompoller.mibInstance |
Instance number used to identify the row in the MIB table that contains the MIB value. Tip You can use this CIA in the Message Format for a Custom Poller incident. |
cia.custompoller.instanceDisplayValue |
Value that results from the Instance Display Configuration. Tip You can use this CIA in the Message Format for a Custom Poller incident. See MIB Expressions Form (Custom Poller) for more information. |
cia.custompoller.instanceFilterValue |
The instance of the MIB Variable after the MIB Filter is applied to the nodes in the specified Node Group. Tip You can use this CIA in the Message Format for a Custom Poller incident. The MIB Filter Variable is specified when configuring a Custom Poller Collection. The MIB Filter is specified when configuring a Custom Poller Policy for the collection. See Create a Custom Poller Collectionand Create a Policy for more information. |
cia.cardsRemoved | Comma-separated list of removed card names used for formatting the Card Removed incident message. |
cia.cardsInserted | Comma-separated list of the inserted card names used for formatting the Card Inserted incident message. |
cia.custompoller.collection | The Name of the associated Custom Poller Collection. |
cia.custompoller.lastValue | The last polled value that caused a state change which generated the incident. |
cia.custompoller.policy | The Name of the associated Custom Poller Policy. |
cia.custompoller.variable.description | The description of the MIB expression being polled. |
cia.custompoller.variable.expression | The MIB expression that was collected and the computed value that caused the incident. |
cia.custompoller.variable.name | The Name of the MIB expression variable that caused the incident. |
cia.custompoller.state | The state of the Custom Polled Instance for this incident. |
cia.incidentDurationMs |
The time measured in milliseconds between when NNMi detected a problem with one or more network devices to the time the problem was resolved. Use this CIA to track the total time a particular object in the network was down or unavailable. Note This CIA is used only when NNMi's Causal Engine has analyzed and Closed the incident. Any time an incident is closed manually (for example, by the network operator), NNMi does not include cia.incidentDuration. |
cia.internalAddress |
If static Network Address Translation (NAT) is part of your network management domain, and the NNMi management server is outside of that static NAT domain, the NNMi administrator can configure this attribute to show the internal IP address that is mapped to the external management address of the selected incident's Source Node. Note The external management IP addresss (public address) must be mapped to this internal address (such as private IPv4 address) using the Overlapping IP Address Mapping Form. See Overlapping Address Mapping Form for more information. For more information about Overlapping IP Addresses in an NNMi network see Overlapping Address Mapping. |
cia.island.name |
Name NNMi uses to identify the nodes contained in the island. NNMi administrators can use this cia value in Launch Actions to display the associated table view or topology map. To launch the associated topology map, use the following syntax for the Launch Action Full URL attribute value:
To launch the associated table view, use the following syntax for the Launch Action Full URL attribute value:
See Configure Launch Actions and Attributes per Object Type for Full URLs for more information. |
cia.island.numberOfNodes | Number of nodes contained in the island. Use this number to determine the effect of the associated Island Down incident. |
cia.reasonClosed |
The Conclusion information identifying the reason NNMi changed the incident's Lifecycle State to Closed. For example, NNMi might include an Interface Up Conclusion as the reason an Interface Down incident was closed. Note This CIA is used when NNMi's Causal Engine has analyzed and Closed the incident. Software that is integrated with NNMi might also provide values for cia.reasonClosed. Any time an incident is closed manually (for example, by the network operator), NNMi does not include cia.reasonClosed. |
cia.remotemgr |
Hostname or IP address of the (NNMi Advanced - Global Network Management feature) NNMi Regional Manager that is forwarding the event |
cia.securityGroup.name |
Name value for the Security Group. See Configure Security Groups (Security Group Form) for more information. Note This CIA does not appear if the node is assigned to the Default Security Group provided by NNMi. |
cia.securityGroup.uuid |
UUID value for the Security Group. See Configure Security Groups (Security Group Form) for more information. Note This CIA does not appear if the node is assigned to the Default Security Group provided by NNMi. |
cia.snmpoid | SNMP trap object identifier. |
cia.sourceNodeLongName | Fully qualified DNS name for the incident's Source Node. |
cia.tenant.name |
Name value for the Tenant. See Use the Tenant Form for more information. Note This CIA does not appear if the node is assigned to the Default Tenant provided by NNMi. |
cia.tenant.uuid |
UUID value for the Tenant. See Use the Tenant Form for more information. Note This CIA does not appear if the node is assigned to the Default Tenant provided by NNMi. |
cia.timeIncidentDetectedMs |
The timestamp in milliseconds when NNMi first detected the problem associated with an incident. Note This CIA is used only when NNMi's Causal Engine has analyzed and Closed the incident. Any time an incident is closed manually (for example, by the network operator), NNMi does not include cia.timeIncidentDetected. |
cia.timeIncidentResolvedMs |
The time when NNMi determines the problem associated with the incident is resolved. Note This CIA is used only when NNMi's Causal Engine has analyzed and Closed the incident. Any time an incident is closed manually (for example, by the network operator), NNMi does not include cia.timeIncidentResolved. |
NNM iSPI Performance for Metrics Custom Incident Attributes
Many incidents are candidates for these custom incident attributes: See Also
Information about configuring thresholds is in the following topics:
- Configure Threshold Monitoring for Node Groups
- Configure Threshold Monitoring for Interface Groups
- Configure Threshold Information for a Custom Poller Collection
Name | Description |
---|---|
cia.thresholdParameter | The Monitored Attribute that is being measured in the threshold's configuration settings. For example, Input Utilization. |
cia.thresholdLowerBound | The configured value that when crossed indicates a low threshold situation. |
cia.thresholdUpperBound | The configured value that when crossed indicates a high threshold situation. |
cia.thresholdPreviousValue | Threshold results from the previous Polling Interval. For example, the threshold results might change from Nominal to High, based on a change in the cia.thresholdMeasuredValue . |
cia.thresholdCurrentValue | Threshold results from the most recent Polling Interval. For example, High. |
cia.thresholdMeasuredValue | The most recent value of the Measured Attribute being monitored according to this threshold's criteria settings. This measurement is the average of all measurements taken during the last polling interval (determined by the NNMi State Poller). |
cia.thresholdMeasurementTime | The time at which the threshold was crossed. The time appears in ISO 8601 format. |
These CIAs are used in a variety of ways:
- In SNMP trap configurations. See Configure SNMP Trap Incidents.
- In management events. See Configure management events.
- In automatic actions. See Configure an Action for an Incident.
- In correlation configurations. See Manage the Number of Incoming Incidents.
- In Launch Action definitions (access through the Actions menu). See Control the NNMi Console Menus.
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: