An SNMP trap is, typically, an unsolicited message that reports on one of two types of events:
Indicate that something is wrong or an error has occurred.
Provide information about status, such as a process ending normally or a printer coming online.
Various SNMP agents are available, including those provided through Agent Technology. They vary greatly in their purpose, complexity, and implementation.
Despite their differences, all SNMP agents can:
Accepting the instructions on where to route SNMP traps is typically referred to as accepting a setting for a trap destination. Setting the trap destination is important because traps are directed to where they can be acted on.
Many vendors provide facilities for setting a system‑wide default trap destination through an SNMP configuration file. For example, some UNIX platforms set their trap destination in the file /etc/snmpd.conf. This path and file name can be different for your system.
There also must be something at that trap destination that can receive and process that trap. Enterprise Management provides an agent that is named CA trap daemon, catrapd. catrapd can receive and process any traps that are directed to the destination (computer) where it is executing.
Any SNMP trap that catrapd receives is unpacked (decoded) and sent to the 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. CCS provides the following translation files for that purpose:
$CAIGLBL0000/snmp/dat/enterprise.dat
The file is self‑documenting. You can add more entries to this file by using a text editor.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|