24.5 Phase 4: Migrating event configuration and event reduction

NNM uses the expanded SNMPv2 format to analyze all sources of received events (traps from managed devices, internal process communication, and transferred events). Each event has an event object identifier, a name, and configuration parameters.

NNMi processes the sources of various events differently. The traps from devices are in the SNMPv2 format. Furthermore, NNMi's internal process communication uses a new (non-trap) mechanism to substantially improve overall performance. NNMi does not generate the no format in trapd.conf message in response to unrecognized events. Unrecognized messages are now discarded as the default.

Because the following event configuration areas are not used in NNMi, they cannot be migrated:

• Several types of configuration element correlation process: suppress, enhance, transient, and multisource

Organization of this section

• 24.5.1 Displaying traps from devices

• 24.5.2 Customizing the display of management events generated by NNMi

• 24.5.3 Setting up blocking, ignoring, or disabling of traps

• 24.5.4 Setting up automatic actions

• 24.5.5 Setting up additional (manual) actions

• 24.5.6 Event correlation: Event repetition

• 24.5.7 Event correlation: Rate calculation

• 24.5.8 Event correlation: Pairwise cancellation

• 24.5.9 Event correlation: ScheduledMaintenance

To Page Top