NNMi 9.23.004 Changing SNMP Trap Limit (471 Views)
Reply
Advisor
RishatS
Posts: 27
Registered: ‎01-24-2014
Message 1 of 5 (471 Views)

NNMi 9.23.004 Changing SNMP Trap Limit

How to increase limit from 100000 SNMPtraps.

(And yes i know nnmtrimincidents.ovpl)

HP Expert
Dave Young
Posts: 560
Registered: ‎09-27-2000
Message 2 of 5 (444 Views)

Re: NNMi 9.23.004 Changing SNMP Trap Limit

Rishat,

 

   Firstly let me reiterate the warning here that you need to be careful when increasing this limit.  Storing more than 100,000 traps in the database can cause performance problems with other tools and features within the product.  So if you make a change, monitor the system carefully and back it out if you start to see any performance degredation.   This is not a value you can just set to any number and expect the system to handle it.

 

In the <NnmDataDir>/shared/nnm/conf/props/nms-jboss.properties file you will find the following settings:

 

# The following property defines how many SNMP traps are allowed to be persisted
# as Incidents in the NNMi database. After this limit is reached new SNMP traps
# will be dropped. The default value is 100,000. Setting the value above
# 100,000 could cause a drop in the performance of Incident database operations.
# Traps should be trimmed from the database on a periodic basis to ensure
# that the number of traps in the database does not exceed
# com.hp.nnm.events.snmpTrapMaxStoreLimit; otherwise newly arriving traps will
# be dropped.
#
# A Critical Alarm is generated when 100% of the snmpTrapMaxStoreLimit is reached.
#!com.hp.nnm.events.snmpTrapMaxStoreLimit=100000

 

# In order to protect the NNMi system from performance problems, ordinarily
# the com.hp.nnm.events.snmpTrapMaxStoreLimit property can not be set to a
# value above 100,000.
#
# If traps are being dropped because of the 100,000 limit, and you wish
# to have more traps saved, the com.hp.nnm.events.snmpTrapEnforce100KLimit
# property can be set to "false" and the com.hp.nnm.events.snmpTrapMaxStoreLimit
# property can be set to a higher limit.  The snmpTrapEnforce100KLimit flag
# is only provided to protect the user from inadvertently setting the
# snmpTrapMaxStoreLimit to too high a value.
# If this is done and the performance of the NNMi event system appears to
# degrade you should consider trimming incidents from the database, either
# manually or by enabling the auto-trim feature.
#
#!com.hp.nnm.events.snmpTrapEnforce100KLimit=true

 

 Please be careful when setting this value.  We recommend it be left at 100,000.

 

  all the best

 

Dave Y

HP Support

The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP

If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.
Advisor
RishatS
Posts: 27
Registered: ‎01-24-2014
Message 3 of 5 (429 Views)

Re: NNMi 9.23.004 Changing SNMP Trap Limit

Thanks for your reply

Advisor
RishatS
Posts: 27
Registered: ‎01-24-2014
Message 4 of 5 (428 Views)

Re: NNMi 9.23.004 Changing SNMP Trap Limit

After the changes I should ovstop, ovstart??
HP Expert
Dave Young
Posts: 560
Registered: ‎09-27-2000
Message 5 of 5 (426 Views)

Re: NNMi 9.23.004 Changing SNMP Trap Limit

 

Rishat,

 

  Yes, I don't believe this property is dynamic.

 

  All the best

 

Dave Y

HP Support

The views expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP

If you find this or any post resolves your issue, please be sure to mark it as an accepted solution.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.