About the Trap Service Stages

Any trap information that appears in the NNMi console or in an NNMi log file is first processed through the NNMi Trap Service. The NNMi Trap Service guarantees that the trap data is analyzed in chronological order.

The following table describes the NNMi Trap Service stages.

NNMi Trap Service Stages
Trap Service Stages Description
TrapListener Receives traps from the configured "Listen" interface. No filtering takes place at this stage.
MessageProcessor

Parses raw traps and records traps for audit purposes. If Trap Logging is enabled, the MessageProcesser writes all traps to the trap log.

Note Traps configured in trapFilter.conf file are not written to the log file.

TrapServerConfiguration Handles configuration updates.
NarrowTrapAnalysis

Handles Hosted Object Trap Storm detection and suppression.

Note This stage is disabled by default. To enable this state use: nnmtrapconfig.ovpl -setProp hostedObjectTrapstorm true -persist. See nnmtrapconfig.ovpl for more information.

WideTrapAnalysis

Handles Trap Storm detection and suppression.

Note This stage is enabled by default.

TrapFilter

Drops all traps that are older than 10 minutes or blocked by IPAddress and OID.

Note Use nnmtrapd.conf to configure trap filters.

This filter only passes traps that are configured and enabled in the SNMP Trap Incident Configuration workspace.

SNMPv1 generic traps only. NNMi uses implicit OID matching when checking for existing SNMP Trap Configurations.

TrapServerConfiguration Forwards traps to the Events Pipeline. This stage also handles Hosted Trap Storm and Trap Storm incident generation.
ForwardingStage Forwards traps to another destination, if specified. For example, traps might be forwarded to another instance of NNMi or to other integrated software.