IBM E027SLL-H Troubleshooting Guide - Page 44

5. Click any workspace that should contain the data to verify that data is arriving. 6. To provide more information, run the following ITMSUPER tools: v Situation Test tool v Exceptions Analysis tool v Distributions Analysis tool What to do next For more information on actions that relate to these diagnostics, see the following tasks: Related tasks: "Resolving situation-specific problems" Resolving situation-specific problems To resolve situation-specific problems, check the log files (such as the agent operations log) to verify that the situation was started; check that the agent returned data and that the SITMON received the data; and check that the situation opened an event. About this task To resolve situation-specific problems, you perform diagnostic and corrective actions. These actions include checking if the agent is online and if the agent returned data. Then, you check that the SITMON received the data. Procedure Diagnostic and corrective actions 1. Verify that the situation was started by checking one of the following log files for text strings based on the specific situation: v Agent operations log For example: 1061110125731000KRAIRA000 Starting FireOnWednesday for KPX.LOCALTIME v Monitoring server log For example: 11/13/06 15:07:21 KO41046 Monitoring for enterprise situation FireOnWednesday started. 2. Did the situation start? v No: See step 3. v Yes: See step 5. 3. Is the situation distributed to the agent and is the agent online? v Look for a text string similar to the following text string in the monitoring server log: KO41047 Situation CheckIfSituationCreated distribution Primary:KATE:NT added v Yes: See step 5. v No: Use (UNIT:kpxreqds all) to trace the distribution at the monitoring server for a situation. (4558D8CC.0033-1114:kpxreqds.cpp,621,"DetermineTargets") Active RAS1 Classes: EVERYT EVERYE EVERYU (4558D8CC.0034-1114:kpxreqds.cpp,661,"determineTargetsFromNodelist") 26 IBM Tivoli Monitoring: Troubleshooting Guide