21.20.5 Monitoring the auto-trim oldest SNMP trap incidents feature
From the NNMi console, click Help, choose System Information, and then Health to check whether messages have been output regarding the health of the auto-trim oldest SNMP trap incidents feature. NNMi also generates the following alarms related to the auto-trim oldest SNMP trap incidents feature:
NNMi generates SnmpTrapLimitCritical when the number of SNMP trap incidents stored in the database (including syslog messages) reaches 100% of the com.hp.nnm.events.snmpTrapMaxStoreLimit value.
NNMi generates SnmpTrapLimitMajor when the number of SNMP trap incidents stored in the database (including syslog messages) reaches 95% of the com.hp.nnm.events.snmpTrapMaxStoreLimit value.
NNMi generates SnmpTrapLimitWarning when the number of SNMP trap incidents stored in the database (including syslog messages) reaches 90% of the com.hp.nnm.events.snmpTrapMaxStoreLimit value.
- Important
When making file changes under High Availability (HA), you must make the changes on both nodes in the cluster. In the case of NNMi in an HA configuration, if the change requires that you stop and restart the NNMi management server, you must put the nodes in the maintenance mode before running the ovstop and ovstart commands. For details, see 19.6.1 Placing NNMi in maintenance mode.