Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Trap Suppression

aussiem65

Does anyone have a list of common traps to suppress because they could generate alarm storms

Find more posts tagged with

Accepted answers

All comments

squinsey

Hi Aussiem65. I'll comment from a NPM point of view so hope this aligns....

Couldn't really suggest one so unable to assist unfortunately:

- as we manage our traps from the device (thus they by default are off)

- only send device based traps (switches, routers, firewalls) if it's something not natively (or delayed) polled via SNMP.

This way if we are receiving an alarm storm - its actually an issue that needs to be investigated.

We find this is the best way of having devices configured, make it the pain of our Networks Team if they configure devices incorrectly

superfly

I only alert on what I think is necessary so all the other traps just go into the database. Every now and then I'll go through the traps and automatically delete some of them from particular devices (access port up/down etc) just to keep the database smaller.