Trap Handling

Traps remain an important component of any network performance monitoring strategy. As a passive monitoring technique, they alert you of potential hiccups between polling cycles.

The SevOne Data Platform​ receives, displays, logs, reports, and alerts on traps from any device or server on your network, notifying you of critical issues that are likely to impact end user experience and disrupt your business.

Hearing the Signal through the Noise

Manually reviewing every trap received would be a time-consuming, stressful, and ultimately futile task. How do you separate the majority of innocuous traps (noise) from the more serious system alerts (signals), such as a fan, power, or heat failure? Your performance management system must allow you to apply logic that automates the handling of incoming traps.

Simplifying Trap Handling

SevOne provides a policy-based trap processing engine that includes a collection of common, default trap events to help you configure how traps are routed in the system. Less meaningful traps may be filtered out, leaving a small percentage of pertinent traps for you to ignore, log, or alert within SevOne or via e-mail. “Unknown” traps not recognized by the rules engine are sent to a separate queue, where you can create new policies to automatically handle similar traps in the future.

If you prefer to use a third party solution for fault management, customization can be written through Professional Services to receive and forward traps to that platform.  Likewise, traps from another Network Performance Monitoring solution may be sent to SevOne for alerting and historical reporting.

IBM SevOne Network Performance Management (NPM) can process in excess of 5,000 SNMP traps per second, so scalability and performance of the trap handling system is never a concern.

SevOne currently supports SNMP v1 and SNMP v2, and SNMP v3.