To view the latest 11.3.x version, see  PATROL Agent 11.3.02 Open link .

Configuring the PATROL Event Manager to send SNMP traps

The PATROL Event Manager (PEM) associates the individual SNMP trap configuration settings with each event class. This applies to both the Standard Event Catalog and any application-specific event catalog created for a Knowledge Module application.

For each event class, the settings of NO_TRAP or SEND_TRAP has been added to specify whether the agent will send an SNMP trap when the event is created. This allows more control over the traps. However, you have little control over the format of the SNMP traps. For example, you can not control the event-specific sub ID or the enterprise ID used.

List of standard event classes

The following table lists all the standard event classes. These event classes can be useful for sending SNMP traps in other situations, such as a console disconnecting.

Standard event classes for sending SNMP traps

Event class Meaning Default trap setting Often used for traps
Diag Diagnosis event. NO_TRAP
No
Disconnect Console disconnected from agent.
No
EventArchive Events have been archived.
No
RemPsl Used by remote PSL execution.
No
Result Used by remote PSL execution.
No
PslSet Used for remote PSL set execution.
No
R3FilterData Used by the SAP R/3 KM only.
No
RegApp New KM class is now registered and running in the agent (example When a new console connects requesting the KMs that it is interested in viewing).
No
RemProcess Used in remote PSL file transfer and the API.
No
StartStop Event published when agent starts (status '1') or stops (status '0').
No
Unload KM class was unloaded by agent.
No
UnregAllApp Unregister all applications.
NO_TRAP

No
UpdAppState New or updated application state.
Yes
UpdInstState New or updated instance state.
Yes
UpdParState New or updated parameter state.
Yes
UpdMachineState New or updated state for the entire agent (due to some change in the state of an application).
Yes
WorstApp This application now has the worst state of all applications in the agent.
No
1 Agent's overall state has changed for this agent computer.
No
2 Worst application class name is provided in this event when the agent's state has changed.
No
3 Worst application instance name is provided in this event when the agent's state has changed.
No
4 Discovery has been started for a KM class.
No
5 Discovery has been disabled for a KM class.
No
6 Agent and console have different version of a KM.
No
7 Successful connection to the agent by a user. that is, a normal console connection or one involving the API or PSL remote functions).
No
9 Alarm is cancelled because the condition about the parameters violating its thresholds has disappeared. In other words, the parameter's value is no longer a bad value that causes an alarm, and the parameter is going back to the OK state. A class 9 event is also generated if a value moves from outside the border range (OK state) into the OK state of the border range.
SEND_TRAP

Yes
10 Recovery action has been ran for the parameter.
NO_TRAP

Yes
11 Parameter value has exceeded the alarm range thresholds. This will raise a warning or alarm state for this parameter.
SEND_TRAP

Yes
12 All recovery actions have ran and failed to resolve the problem. The parameter will stay in its current state. Agent will not run any more recovery actions for this parameter.
NO_TRAP

No
13 Suspended all parameters of this KM class.
No
14 or 15 Restarting all local and global parameters of the KM class.
No
16 Parameter description has been modified (that is, KM editing) and the parameter state is reset to OK.
No
17 or 18 Global parameter has started.
No
19 Local parameter has started.
No
20 Parameter had bad output. For example, PSL set on "value" did not provide an integer to a graph or gauge parameter.
No
21 Local parameter is suspended and will no longer run.
No
22 or 23 Global parameter is suspended and will no longer run.
No
24 Agent process cache cycle changed.
No
25 Agent process cache cycle changed.
No
26 or 27 Application discovery is disabled for this KM class.
NO_TRAP

No
28 Username/password were invalid to connect to the agent (example through the API or PSL remote functions).
No
29 Internal agent or PEM failure of some type.
No
38 Parameters of a KM were restarted.
No
39 Parameter threshold was exceeded by parameter value. State change event.
No
40 PSL response-related event. Created when a PSL response function is launched by the agent.
No
41, 42, or 43 Information event. Placeholder for user-defined events. Not generated internally by the agent.
No
Was this page helpful? Yes No Submitting... Thank you

Comments