Previous Topic: Support for SNMP Version 3 TrapsNext Topic: How catrapd Formats Traps


Trap Destinations

Traps should be routed to a destination where an action can be taken. Many vendors provide facilities for setting a system-wide default trap destination through an SNMP configuration file. For example, some UNIX/Linux platforms set their trap destination in the /etc/snmpd.conf file. This path and file name may be different for your system.

After a trap destination setting is accepted, there must be something at that destination to receive and process the trap. An Event Management agent, CA trap daemon (catrapd), automatically receives and processes traps directed to the destination (machine) on which it is executing.

catrapd receives an SNMP trap, unpacks (decodes) it, and sends it to other Event Management components for processing. As part of this decoding, character representations, or strings, can be assigned to substitute names for the Enterprise IDs that are part of the SNMP trap. CA NSM provides the following translation files for that purpose:

On Windows, to enable enterprise name translation, go to EM Settings and modify the ‘Enterprise OID displayed as’ setting to ‘NAME.’ Recycle catrapd so that the change takes effect.

Note: On Windows you can update the enterprise.dat file with the command catrapd update.

For more information about catrapd, see the online CA Reference.