Limiting Traps in OpManager

When the number of traps (to be processed) received by the OpManager server is greater than 50,000/hr, OpManager automatically stops processing traps. Processing numerous, unwanted traps at once might lead to performance degradation in OpManager.

How to deal with trap flooding?

Follow the below steps to stop trap flooding and restart trap processing in OpManager.

  1. Identify the device(s) which is flooding the OpManager server with traps.
  2. Check the device(s) for potential faults and failures.
  3. Troubleshoot the issues in the device(s).
  4. Once all the issues are fixed, enable trap processing in OpManager server.

How to process more than 50,000 traps/hr in OpManager?

Every networking environment is unique. If your environment requires more than 50,000 traps/hr to be processed, OpManager can do that too. Please contact our support

at"> with your query.

Video Zone
OpManager Customer Videos
Altaleb Alshenqiti - Ministry of National Guard - Health Affairs
  •  IT Admin from "Royal flying doctor service", Australia
     Jonathan ManageEngine Customer
  •  Michael - Network & Tech, ManageEngine Customer
     Altaleb Alshenqiti - Ministry of National Guard - Health Affairs
  •  David Tremont, Associate Directory of Infrastructure,USA
     Todd Haverstock Administrative Director
  •  Donald Stewart, IT Manager from Crest Industries
     John Rosser, MIS Manager - Yale Chase Equipment & Services
 Pricing  Get Quote