IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Agent-based services > SNMP alerts
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
SNMP alert configuration
Configure a monitoring agent and an SNMP trap configuration file to emit life cycle events or situation events to an SNMP event receiver.
- Trap configuration file
- A trap configuration file must be present when the agent is started to enable the agent to emit SNMPv1/v2 traps or SNMPv3 informs for configured situations. If a correctly named trapcnfg.xml file is present in the agent's local configuration directory, the agent emits the traps that are defined in the file when it is started. The file is named pc_trapcnfg.xml, where pc is the 2-character product code of the agent and resides in the install_dir/localconfig/pc directory. The file must be named pc_trapcnfg.xml, where pc is the two-character product code, such as ux for the UNIX OS agent.
- The IBM i agent can send SNMPv1/v2 traps, but it cannot send SNMPv3 informs.
- On z/OS, the default name for the file is PCTRAPS in the RKANDATV dataset.
- Agent parameters
- IRA_EVENT_EXPORT_SNMP_TRAP_CONFIG parameter in the agent environment file can be set to specify a different name and path to the trap configuration file. SNMP alerts are emitted only for situations that are configured in the trap configuration XML file for that agent type. You can specify the complete path or the path relative to the local configuration directory.
- To specify the complete path, the PDS should be listed at the end (or omitted and allowed to default to RKANDATV).
- IRA_EVENT_EXPORT_SNMP_TRAP=N disables agent SNMP alerts even if the pc_trapcnfg.xml file is present.
- XML specification
- The trap configuration file can include these XML elements:
- SNMP
- TrapDest
- TrapAttrGroup
- Situation
- StatTrap
SNMP is the top-level XML element. TrapDest, TrapAttrGroup, and Situation are elements within the SNMP begin and end tags.
- Sample trap configuration file
- Review this sample nt_trapcnfg.xml for a Windows OS agent to see how a trap configuration file might be composed. It is located in the install_dir\localconfig\nt directory to enable trap emission for the Windows OS agent. The file is configured to send status traps receiver using SNMPv1 trap on host nt2003infra and to send informs for the individually defined situation events to a Netcool/OMNIbus SNMP probe using SNMPv3 running on host 10.21.32.234.
<!—C:\IBM\ITM\localconfig\nt\nt_trapcnfg.xml /--> <SNMP> <TrapDest name="AgentStatMon" Address=" nt2003infra " Version="v1" Community="{AES256:keyfile:a}P0hUrmUhCgfFwimS+Q6w+w==" Stat=”Y” /> <TrapDest name="Probe1" Version="v3" Address="10.21.32.234" SecLevel="authPriv" User="AuthPrivMD5DES" AuthType="MD5" AuthPassKey="{AES256:keyfile:a}yifHSbFcTKHBqvORpzxS6A==" PrivType="DES" PrivPassKey= "{AES256:keyfile:a}1le2SxljJR1MOIi0EDIvig==" Stat=”N” /> <TrapAttrGroup Table="NT_Paging_File" TrapAttrList="Server_Name, %_Usage" /> <Situation name="NT_Log_Space_Low_pr" sev="2" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_Missing_Scheduler_pr” sev="5" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_Paging_File_Critical_pr” sev="5" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_Paging_File_Warning_pr” sev="2" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_Phys_Disk_Busy_Critical_pr” sev="5" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_Phys_Disk_Busy_Warn_pr” sev="2" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_System_File_Warn_pr” sev="2" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_Proc_CPU_Critical_pr” sev="5" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_Proc_CPU_Warn_pr” sev="2" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_Service_Error_pr” sev="2" cat="0" mode="RC" target=“Probe1” /> <Situation name="NT_System_File_Critical_pr” sev="5" cat="0" mode="HY" target=“Probe1” /> <Situation name="NT_System_File_Warn_pr” sev="2" cat="0" mode="HY" target=“Probe1” /> <StatTrap name="EE_HEARTBEAT" sev="1" interval="15" cat="3" /> <StatTrap name="EE_AUTO_ENTER" sev="1" cat="3" /> <StatTrap name="EE_AUTO_EXIT" sev="1" cat="3" /> <StatTrap name="EE_AUTO_USE_LIMIT" sev="5" cat="3" /> <StatTrap name="EE_TEMS_RECONNECT_LIMIT" sev="5" cat="3" /> <StatTrap name="EE_TEMS_CONNECT" sev="1" cat="4" /> <StatTrap name="EE_TEMS_DISCONNECT" sev="1" cat="4" /> <StatTrap name="EE_SIT_STOPPED" sev="1" cat="4" /> </SNMP>
Parent topic:
SNMP alerts