Reducing the Number of Stored SNMP Trap Incidents

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 > Administer SNMP Traps > Configuring the Auto-Trim Oldest SNMP Trap Incidents Feature > Reducing the Number of Stored SNMP Trap Incidents

Reducing the Number of Stored SNMP Trap Incidents

If you do not need NNMi to keep SNMP trap incidents for a long time period, you might consider reducing the number of SNMP trap incidents stored in the NNMi database.

Note NNMi begins dropping SNMP traps (including syslog messages) after the number of SNMP trap incidents in its database reaches 100,000. Setting this limit to a higher number is not supported, as doing so can cause NNMi performance degradation.n

Suppose you want to reduce the maximum number of stored SNMP trap incidents (including syslog messages) to 50,000 SNMP trap incidents. To do this, complete the following steps:

Edit the following file:
- Windows: %NNM_PROPS\nms-jboss.properties
- Linux: $NNM_PROPS/nms-jboss.properties
Locate the text block containing the following line:
```
#!com.hp.nnm.events.snmpTrapMaxStoreLimit=100000
```
Uncomment and edit the line to read as follows:
```
com.hp.nnm.events.snmpTrapMaxStoreLimit=50000
```
Restart the NNMi management server:
1. Run the ovstop command on the NNMi management server.
2. Run the ovstart command on the NNMi management server.

When making file changes under High Availability (HA), you need to make the changes on both nodes in the cluster. For NNMi using HA configurations, if the change requires you to stop and restart the NNMi management server, you must put the nodes in maintenance mode before running the ovstop and ovstart commands.

Send Help Center feedback