21.20 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.
- Important
-
Until NNMi 12-00, NNMi did not trim root causes, and only trimmed SNMP trap incidents.
In NNMi 12-10 or later, either "all incidents" or "only SNMP trap incidents" can now be set. The default is "all incidents".
In NNMi 12-10 or later, the automatic trim function for SNMP trap incidents is enabled when a new installation is performed, and NNMi deletes old incidents from the database. (By default, an archive is not created.) In the case of a version upgrade, the previous setting is inherited.
com.hp.nnm.events.snmpTrapAutoTrimSetting
Refer to the following concrete example, and configure settings such as the settings to enable or disable the automatic trim function and to switch between "only SNMP traps" and "all incidents" as the trimming target.
- Note
To trim SNMP trap incidents manually from the NNMi database, use the nnmtrimincidents.ovpl command. For details, see the nnmtrimincidents.ovpl Reference Page.
- Organization of this section
21.20.1 Enabling the auto-trim oldest incidents feature (no incident archive)
21.20.2 Enabling the auto-trim oldest SNMP trap incidents feature (incident archive enabled)
21.20.4 Changing the maximum number of SNMP trap incidents to be saved
21.20.5 Monitoring the auto-trim oldest SNMP trap incidents feature
21.20.6 Disabling the auto-trim oldest SNMP trap incidents feature