The following sample pseudo-MIB describes an event tree. Each element represents information that can be sent when specified as a variable on the catrap command.
Sending a trap of 999.1.1.2 is equivalent to sending the message “The Enterprise Database server that handles the General Ledger database has been started.”
A trap of 999.1.1.3 indicates that the General Ledger database has encountered a journal full condition. A trap of 999.2.1.5 indicates that the General Ledger financial application has resumed processing after a temporary outage (warm start).
Taking the example further, assume CA NSM is executing on several nodes, but you want to direct all SNMP trap traffic to a single monitoring machine running on the server Earth. The server Earth receives the SNMP traps. Event Management records and acts on them.
The server Mars runs production financial applications. The General Ledger production application running on Mars terminates with an error.
Testing the return code issued by the General Ledger production executable, the shell script detects an exit code indicating a problem and issues an SNMP trap to alert the server Earth by executing the following command:
catrap earth ““ ““ 6 0 22 999.2.1.7 integer 128
where:
Sends the identified trap information to the server Earth.
Instructs catrap to take the default Enterprise code and the default agent address respectively for this node.
Indicates that this command is sending a specific trap.
Identifies the specific trap number for this example.
Specifies an arbitrary number selected as a timestamp indicator.
Note: The following operands identify the variable binding (varbind) information for the trap.
Identifies the object about which information is being sent. In the event tree illustrated earlier, this object refers to an error in the Enterprise financial application, General Ledger.
Provides additional information about the event. In this example, it could mean send an integer value of 128 to node Earth, assuming 128 is an error code that has meaning to the General Ledger application; or it could be the exit code that the shell script detected as indicating an error.
When received at the trap target server Earth, catrapd decodes the event and performs automatic actions in response. The event tree shows other types of events that could be sent, such as 999.1.1.1, indicating that the database of the Enterprise data server for the General Ledger system has shut down.
When combined with other CA NSM capabilities, the possibilities expand. For example, you can use Event Management to intercept error messages from any application and automatically execute customized catrap commands in response. The detection of key events can result in traps being sent in response to files becoming available for processing or applications completing their processing. Security violation attempts can result in other SNMP traps being sent.
On the receiving side of an SNMP trap, you can use Event Management message handling policies to:
For more information on catrap, including an example of how to use it to issue an SNMP trap, see the online CA Reference.
|
Copyright © 2010 CA.
All rights reserved.
|
|