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 |
|
- Administer SNMP Traps
- SNMP Trap Management
- Blocking Trap Storms using the hosted-on-trapstorm.conf File
- Configuring to Authenticate SNMPv3 Traps for Nodes not Monitored
- Configuring the Times within which the Causal Engine Accepts Traps
- Blocking Incidents using the nnmtrapd.conf and trapFilter.conf Files
- Configuring to Preserve a Previously Supported Varbind Order
- Configuring the Auto-Trim Oldest SNMP Trap Incidents Feature
- Enabling the Auto-Trim Oldest SNMP Trap Incidents Feature (No Incident Archive)
- Enabling the Auto-Trim Oldest SNMP Trap Incidents Feature (Incident Archive Enabled)
- Reducing the Number of Stored SNMP Trap Incidents
- Monitoring the Auto-Trim Oldest SNMP Trap Incidents Feature
- Disabling the Auto-Trim Oldest SNMP Trap Incidents Feature
- Configuring to Determine the Original Trap Address from Traps sent by a Proxy SNMP Gateway
- NNMi NmsTrapReceiver Process
- Modifying Simultaneous SNMP Requests
Configuring the Auto-Trim Oldest SNMP Trap Incidents Feature
To keep NNMi performing at a high level, NNMi drops incoming SNMP traps (including syslog messages) after storing a specific number of SNMP traps in its database. You can use the auto-trim oldest SNMP trap incidents feature to control the number of SNMP traps stored in the NNMi database and to retain important incoming SNMP traps.
Note NNMi trims only non-root cause SNMP Trap incidents.
The auto-trim oldest SNMP trap incidents feature defaults to being disabled. After enabling the auto-trim oldest SNMP trap incidents feature, NNMi removes the oldest SNMP trap incidents from the NNMi database.
Tip To manually trim SNMP trap incidents from the NNMi database, use the nnmtrimincidents.ovpl
script. See the nnmtrimincidents.ovpl reference page, or the Linux manpage, for more information.
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: