8.6.1 Enabling incidents for undefined traps
By default, NNMi drops SNMP traps with no incident definition.
To generate SNMP traps with no incident definition as UndefinedSNMPTrap incidents:
Open the following file with a text editor:
Windows: %NNM_PROPS%\nms-jboss.properties
Linux: $NNM_PROPS/nms-jboss.properties
Look for the following line:
#!com.hp.nnm.events.allowUndefinedTraps=false
Edit this line as follows:
com.hp.nnm.events.allowUndefinedTraps=true
(Optional) Specify an incident severity.
Look for the following line:
#!com.hp.nnm.events.undefinedTrapsSeverity=NORMAL
Substitute a defined severity value for YourSpecifiedSeverity:
com.hp.nnm.events.undefinedTrapsSeverity=YourSpecifiedSeverity
The valid values are NORMAL, WARNING, MINOR, MAJOR, and CRITICAL.
(Optional) Specify the incident nature.
Look for the following line:
#!com.hp.nnm.events.undefinedTrapsNature=INFO
Substitute an incident nature for YourSpecifiedNature:
com.hp.nnm.events.undefinedTrapsNature=YourSpecifiedNature
The valid values are ROOTCAUSE, SECONDARYROOTCAUSE, SYMPTOM, SERVICEIMPACT, NONE, and INFO.
Save the changes.
Execute the following commands to restart NNMi:
ovstop ovstart
Review the list of UndefinedSNMPTrap incidents.
You must specify incident definitions for those SNMP traps that you want to display as incidents. For details, see NNMi Help.