StatTrap

IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Agent-based services > SNMP alerts > Trap configuration XML specification
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

StatTrap

Use the StatTrap element in an SNMP trap configuration file to modify the default configuration of the predefined agent life cycle status traps.
In this syntax example, the predefined trap for EE_HEARTBEAT was modified to specify severity 1 (Indeterminate) for the event, a 30-minute sampling interval, and trap category 3 (Status).
<StatTrap name="EE_HEARTBEAT" sev="1" interval="30" cat="3" />
There are eight predefined agent life cycle traps and their default values are given in this table. By default, these traps are sent to all TrapDest trap destinations where the Stat attribute is “Y”. If the Stat attribute is omitted from a TrapDest element the default value is “Y”.

Agent life cycle status traps

Attribute Description Severity Category
EE_HEARTBEAT A heartbeat indicates that the agent is running and events emitted can reach the trap destination. This is the only status trap with a set interval: 15 minutes. 1 – Indeterminate 3 – Status
EE_AUTO_ENTER The agent has entered autonomous mode. 1 – Indeterminate 3 – Status
EE_AUTO_EXIT The agent has exited autonomous mode. 1 – Indeterminate 3 – Status
EE_AUTO_USE_LIMIT The agent has reached the storage limit specified by the IRA_AUTONOMOUS_LIMIT environment variable. Additional events generated while the agent is disconnected from the monitoring server may not be uploaded on reconnect. 1 – Indeterminate 3 – Status
EE_TEMS_RECONNECT
_LIMIT Agent has reached the retry limit specified by the CTIRA_MAX_RECONNECT_TRIES environment variable. The agent will no longer attempt to connect to a monitoring server and will shutdown. In IBM Tivoli Monitoring 6.2.2 or later, the default value of CTIRA_MAX_RECONNECT_TRIES has been changed to 0, so the agent will never shutdown. 1 – Indeterminate 3 – Status
EE_TEMS_CONNECT The agent has successfully connected to the monitoring server. 1 – Indeterminate 4 - Node Configuration
EE_TEMS_DISCONNECT The agent has lost connection with the monitoring server. 1 – Indeterminate 4 - Node Configuration
EE_SIT_STOPPED The situation has stopped 1 – Indeterminate 4 - Node Configuration

Use the StatTrap element to configure agent life cycle traps.

StatTrap element XML specification

Status trap Description Required Default
Name= This trap name must be the name of a predefined Life-Cycle status trap.
EE_HEARTBEAT
EE_AUTO_ENTER
EE_AUTO_EXIT

EE_AUTO_USE_LIMIT
EE_TEMS_RECONNECT_LIMIT
EE_TEMS_CONNECT
EE_TEMS_DISCONNECT
EE_SIT_STOPPED Optional
Target= Specify a previously defined TrapDest. An asterisk (*) implies send trap to all defined destinations. If no Target is defined, all TrapDest with Stat=”Y” will receive the status trap. Required
Sev= Specify trap severity. The standard trap severities are:
0 – Cleared
1 – Indeterminate
2 – Warning
3 – Minor
4 – Major
5 – Critical Optional Varies
Cat= Specify trap category. The standard trap categories are:
0 - Threshold
1 - Network Topology
2 – Error
3 – Status
4 - Node Configuration
5 - Application Alert
6 - All Category
7 - Log Only
8 – Map
9 - Ignore Optional Varies
Interval= Interval specifies in minutes how often the EE_HEARTBEAT status trap is emitted. Interval is ignored for the other status traps because they are pure events. Optional 15 for EE_HEARTBEAT
0 for all others

Parent topic:
Trap configuration XML specification

+
Search Tips | Advanced Search

Attribute	Description	Severity	Category
EE_HEARTBEAT	A heartbeat indicates that the agent is running and events emitted can reach the trap destination. This is the only status trap with a set interval: 15 minutes.	1 – Indeterminate	3 – Status
EE_AUTO_ENTER	The agent has entered autonomous mode.	1 – Indeterminate	3 – Status
EE_AUTO_EXIT	The agent has exited autonomous mode.	1 – Indeterminate	3 – Status
EE_AUTO_USE_LIMIT	The agent has reached the storage limit specified by the IRA_AUTONOMOUS_LIMIT environment variable. Additional events generated while the agent is disconnected from the monitoring server may not be uploaded on reconnect.	1 – Indeterminate	3 – Status
EE_TEMS_RECONNECT _LIMIT	Agent has reached the retry limit specified by the CTIRA_MAX_RECONNECT_TRIES environment variable. The agent will no longer attempt to connect to a monitoring server and will shutdown. In IBM Tivoli Monitoring 6.2.2 or later, the default value of CTIRA_MAX_RECONNECT_TRIES has been changed to 0, so the agent will never shutdown.	1 – Indeterminate	3 – Status
EE_TEMS_CONNECT	The agent has successfully connected to the monitoring server.	1 – Indeterminate	4 - Node Configuration
EE_TEMS_DISCONNECT	The agent has lost connection with the monitoring server.	1 – Indeterminate	4 - Node Configuration
EE_SIT_STOPPED	The situation has stopped	1 – Indeterminate	4 - Node Configuration

Status trap	Description	Required	Default
Name=	This trap name must be the name of a predefined Life-Cycle status trap. EE_HEARTBEAT EE_AUTO_ENTER EE_AUTO_EXIT EE_AUTO_USE_LIMIT EE_TEMS_RECONNECT_LIMIT EE_TEMS_CONNECT EE_TEMS_DISCONNECT EE_SIT_STOPPED	Optional
Target=	Specify a previously defined TrapDest. An asterisk (*) implies send trap to all defined destinations. If no Target is defined, all TrapDest with Stat=”Y” will receive the status trap.	Required
Sev=	Specify trap severity. The standard trap severities are: 0 – Cleared 1 – Indeterminate 2 – Warning 3 – Minor 4 – Major 5 – Critical	Optional	Varies
Cat=	Specify trap category. The standard trap categories are: 0 - Threshold 1 - Network Topology 2 – Error 3 – Status 4 - Node Configuration 5 - Application Alert 6 - All Category 7 - Log Only 8 – Map 9 - Ignore	Optional	Varies
Interval=	Interval specifies in minutes how often the EE_HEARTBEAT status trap is emitted. Interval is ignored for the other status traps because they are pure events.	Optional	15 for EE_HEARTBEAT 0 for all others