v
STATE - minimum detail.
v
DETAIL - medium detail.
v
ALL - maximum detail.
For example,
’KBB_RAS1=’ERROR (UNIT:kfaot STATE)’
3.
Save the file.
4.
Recycle the monitoring server for the trace to take effect.
5.
The monitoring server log can be found in
install_dir/logs/
hostname_ms_nnnnnnn.log
where is a time stamp. There might be multiple files
with different time stamps in the logs directory.
Setting the trace option for the IBM Tivoli Enterprise Console
Situation Update Forwarder
If your monitoring environment is configured for the IBM Tivoli Enterprise
Console, you can forward situation events to the Tivoli Enterprise Console event
server. You can also view events on the event server through the Tivoli Enterprise
Portal. If you want to forward situation events to and view updates from IBM
Tivoli Enterprise Console in the Tivoli Enterprise Portal, you can set the trace for
the Situation Update Forwarder on the IBM Tivoli Enterprise Console event server.
The default trace setting is low. You can edit the trace setting using the
sitconfig
command.
$BINDIR/TME/TEC/OM_TEC/bin/sitconfig.sh update
fileName=configuration_file_name logLevel=trace_level
where:
configuration_file_name
The file name of the actively loaded configuration file as indicated by the
situpdate.properties
file.
trace_level
Specifies the level of trace as
low
,
med
, or
verbose
.
Use the IBM Tivoli Enterprise Console Situation Update Forwarder trace facility to
diagnose problems with the IBM Tivoli Enterprise Console Situation Update
Forwarder. The trace for the IBM Tivoli Enterprise Console Situation Update
Forwarder is set during installation. The acceptable values include:
v
low
v
med
v
verbose
The default trace value is low. If you change the trace level after the Situation
Update Forwarder is started, you must restart the Situation Update Forwarder for
the change to take effect. There are two trace files:
synch_trace.log
is always created.
synch_msg.log
is created if an error occurs while running the Situation Update Forwarder.
Run the following command to set the trace levels:
$BINDIR/TME/TEC/OM_TEC/bin/sitconfig.sh update
fileName=configuration_file_name logLevel=trace_level
where:
52
IBM Tivoli Monitoring: Troubleshooting Guide
Summary of Contents for E027SLL-H - Tivoli Monitoring - PC
Page 1: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 2: ......
Page 3: ...IBM Tivoli Monitoring Version 6 2 3 FP1 Troubleshooting Guide GC32 9458 05...
Page 14: ...xii IBM Tivoli Monitoring Troubleshooting Guide...
Page 16: ...xiv IBM Tivoli Monitoring Troubleshooting Guide...
Page 18: ...xvi IBM Tivoli Monitoring Troubleshooting Guide...
Page 22: ...4 IBM Tivoli Monitoring Troubleshooting Guide...
Page 82: ...64 IBM Tivoli Monitoring Troubleshooting Guide...
Page 144: ...126 IBM Tivoli Monitoring Troubleshooting Guide...
Page 164: ...146 IBM Tivoli Monitoring Troubleshooting Guide...
Page 188: ...170 IBM Tivoli Monitoring Troubleshooting Guide...
Page 240: ...222 IBM Tivoli Monitoring Troubleshooting Guide...
Page 262: ...244 IBM Tivoli Monitoring Troubleshooting Guide...
Page 274: ...256 IBM Tivoli Monitoring Troubleshooting Guide...
Page 276: ...258 IBM Tivoli Monitoring Troubleshooting Guide...
Page 284: ...266 IBM Tivoli Monitoring Troubleshooting Guide...
Page 288: ...270 IBM Tivoli Monitoring Troubleshooting Guide...
Page 302: ...284 IBM Tivoli Monitoring Troubleshooting Guide...
Page 308: ...290 IBM Tivoli Monitoring Troubleshooting Guide...
Page 309: ......
Page 310: ...Printed in USA GC32 9458 05...