Examples: Using trace logs

You can open trace logs in a text editor to learn some basic facts about your IBM Tivoli Monitoring environment.

The following examples are from the Tivoli Enterprise Monitoring Server log.
Example one
This excerpt shows the typical log for a failed connection between a monitoring agent and a monitoring server with the host name server1a:
(Thursday, August 11, 2005, 08:21:30-{94C}kdcl0cl.c,105,"KDCL0_ClientLookup")
 status=1c020006, "location server unavailable", ncs/KDC1_STC_SERVER
_UNAVAILABLE (Thursday, August 11, 2005, 08:21:35-{94C}kraarreg.cpp,
1157,"LookupProxy") Unable to connect to broker at ip.pipe:: status=0,
 "success", ncs/KDC1_STC_OK (Thursday, August 11, 2005, 08:21:35-{94C}
kraarreg.cpp,1402,"FindProxyUsingLocalLookup") Unable to find running
 CMS on CT_CMSLIST <IP.PIPE:#server1a>
Example two
The following excerpts from the trace log for the monitoring server show the status of an agent, identified here as "Remote node." The name of the computer where the agent is running is SERVER5B:
(42C039F9.0000-6A4:kpxreqhb.cpp,649,"HeartbeatInserter")
 Remote node SERVER5B:NP is ON-LINE.
. . .
(42C3079B.0000-6A4:kpxreqhb.cpp,644,"HeartbeatInserter")
 Remote node SERVER5B:NP is OFF-LINE.
See the following key points about the preceding excerpts:
  • The monitoring server appends the two-character product code to the server name to form a unique name (for example, SERVER5B:vm ) for this instance of the agent. By using this unique name, you can distinguish multiple monitoring products that might be running on SERVER5B.
  • The log shows when the agent started (ON-LINE) and later stopped (OFF-LINE) in the environment.
  • For the sake of brevity, an ellipsis (...) represents the series of trace log entries that were generated while the agent was running.
  • Between the ON-LINE and OFF-LINE log entries, the agent was communicating with the monitoring server.
  • The ON-LINE and OFF-LINE log entries are always available in the trace log.