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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Administer > Configure Incidents > Manage Incoming SNMP Traps

Manage Incoming SNMP Traps

NNMi provides several tools that enable you to manage the SNMP traps that are sent through the Event Pipeline and are configured to appear as incidents in the NNMi console. For more information about NNMI's Event Pipeline, see About the Event Pipeline.

NNMi uses the following criteria to determine whether it receives or discards incoming traps:

If the incoming trap's Source Node object or Source Object (such as card or interface) has not yet been discovered, NNMi discards the trap by default.

Note The NNMi administrator can change this behavior using the Trap Handling Settings when configuring incidents. See Handle Unresolved Incoming Traps for additional information. See also Configure Network Devices to Send SNMP Notifications to NNMi.
If the Source Node or Source Object of the incoming trap has been discovered by NNMi using SNMPv3, NNMi accepts incoming traps from SNMPv3, SNMPv2c, or SNMPv1. See SNMPv3 Settings Form for information about configuring SNMPv3 settings.
If the Source Node or Source Object of the incoming trap has been discovered by NNMi using SNMPv2c or SNMPv1, NNMi discards incoming traps from SNMPv3. See Also
NNMi discards traps that have no incident configuration or with an incident configuration set to Disabled. To ensure that NNMi retains all received Trap instances when your network environment includes SNMP agents using a variety of SNMPv1, SNMPv2c, and SNMPv3 protocol, you must configure two Incidents: one for the SNMPv1 version and one for the SNMPv2c/3 version of that trap. See Configure SNMP Trap Incidents.
If either the Source Node or Source Object has Management Mode set to Not Managed or Out of Service in the NNMi database, NNMi always discards the incoming trap. See Understand the Effects of Setting the Management Mode to Not Managed or Out of Service.

NNMi provides the Management Mode workspace so that you can quickly view lists of all nodes, interfaces,IP addresses, chassis, cards, node sensors, and physical sensors that NNMi is not currently discovering or monitoring. For information about these views: See Also
NNMi discards most incoming traps from network objects that are not monitored. For example, you can configure NNMi to exclude specified interfaces from being monitored. See Monitor Network Health for more information.

Note the following:

If you want the NNMi management server to forward traps to other machines in your network environment, see the following topics for additional information and configuration steps:
- SNMPv2c traps — Configure Trap Forwarding
- SNMPv3 traps — Configure NNMi SNMPv3 Security Settings for Trap Forwarding and Inform-Requests
NNMi administrators can configure thresholds for trap volume within your network. Choices include count-based or time-based thresholds for total volume or for each trap OID. Traps can also be blocked. See the following Reference Pages:
- nnmtrapconfig.ovpl
- hosted-object-trapstorm.conf

When managing your SNMP Traps consider performing the following tasks: