Administer > Administer SNMP Traps > Configuring the Auto-Trim Oldest SNMP Trap Incidents Feature > Monitoring the Auto-Trim Oldest SNMP Trap Incidents Feature

Monitoring the Auto-Trim Oldest SNMP Trap Incidents Feature

From the NNMi console, click Help > System Information > Health to check the health of the auto-trim oldest SNMP trap incidents feature. NNMi also generates the following alarms regarding the auto-trim oldest SNMP trap incidents feature.

  • NNMi generates a critical alarm after the number of stored SNMP trap incidents (including syslog messages) reaches 100% of the com.hp.nnm.events.snmpTrapMaxStoreLimit value.
  • NNMi generates an snmpTrapLimitMajorAlarm alarm after the number of stored SNMP trap incidents (including syslog messages) reaches 95% of the com.hp.nnm.events.snmpTrapMaxStoreLimit value.
  • NNMi generates an snmpTrapLimitWarningAlarm alarm after the number of stored SNMP trap incidents (including syslog messages) reaches 90% of the com.hp.nnm.events.snmpTrapMaxStoreLimit value.

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.