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

CPU required for widely used NCM.

Hi everyone.I manage NCM for a large client in Italy.I have configured some trap rules so that, when a trap is received that contains messages relating to a configuration change, it triggers an alert which as action has the download of the running config of the device that sent the trap.Everything works very well but the machine receives thousands of traps and therefore is very stressed.The CPU often reaches 100%.The server has an Intel Xeon CPU E5-4650 @ 2.70GHZ 2.70 GHZHow much CPU do you recommend to solve this?

Thanks.
Francesco

Find more posts tagged with

Accepted answers

All comments

m_roberts

This is not just a resource issue, this is also about the volume of event messages a single polling engine can process.

Options:

Control the level of SNMP traps being sent by the source devices
1. It is often possible to configure the devices to send only certain types or levels of trap
2. LV or LA can deal with around 1000 events per second
Look to use Syslog, which has easier controls for such severity and type of message
Can you create rules to discard trap messages you do not need to keep
1. Preventing event messages from having to be inserted in to the database is more efficient
Could you deploy a front end trap server, which will then forward on filtered messages to SolarWinds NCM
1. We often use Kiwi Syslog for this function