19.15.3 Changing the maximum number of SNMP trap incidents to be saved
Depending on whether you need to keep SNMP trap incidents for a long period of time, you can change the maximum number of SNMP trap incidents to be saved in the database.
- Important note
-
By default, 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 value is not recommended, as doing so can cause NNMi performance degradation. Carefully evaluate the situation before changing the maximum number.
- Organization of this subsection
(1) Changing the maximum number to less than 100,000
To change the maximum number to 50,000:
-
Edit the following file:
-
Windows: %NNM_PROPS%\nms-jboss.properties
-
UNIX: $NNM_PROPS/nms-jboss.properties
-
-
Look for the following line:
#!com.hp.nnm.events.snmpTrapMaxStoreLimit=100000
-
Uncomment and edit this line to read as follows:
com.hp.nnm.events.snmpTrapMaxStoreLimit=50000
-
Save the edited file, and then restart NNMi by running the following commands:
ovstop ovstart
(2) Changing the maximum number to more than 100,000
To change the maximum number to 200,000:
-
Edit the following file:
-
Windows: %NNM_PROPS%\nms-jboss.properties
-
UNIX: $NNM_PROPS/nms-jboss.properties
-
-
Look for the following line:
#!com.hp.nnm.events.snmpTrapEnforce100KLimit=true
-
Uncomment and edit this line to read as follows, and save the file:
com.hp.nnm.events.snmpTrapEnforce100KLimit=false
-
Edit the following file:
-
Windows: %NNM_PROPS%\nms-jboss.properties
-
UNIX: $NNM_PROPS/nms-jboss.properties
-
-
Look for the following line:
#!com.hp.nnm.events.snmpTrapMaxStoreLimit=100000
-
Uncomment and edit this line to read as follows, and save the file:
com.hp.nnm.events.snmpTrapMaxStoreLimit=200000
-
Restart NNMi by running the following commands:
ovstop ovstart