IBM E027SLL-H - Tivoli Monitoring - PC, Troubleshooting Manual

Page: 181 / 310

During installation of a remote Tivoli Enterprise Monitoring Server on a Windows
system, the agent support is typically applied. This fails if the hub Tivoli
Enterprise Monitoring Server is unreachable.
During remote Tivoli Enterprise Monitoring Server installation on the Windows
platform, ensure the hub Tivoli Enterprise Monitoring Server is running.
Using a Deploy Group with addSystem or updateAgent
commands
When using a deploy group with addSystem or updateAgent commands, remote
deploy might fail to locate the existing Managed System Name for some hosts.
Message received:
KDY0012E: The target target_hostname is incorrect or is
offline. The command did not complete because the value for the target is
incorrect or the target is offline.
This message normally indicates that the OS agent is not online. If the agent is, in
fact, online, cancel current operations to this node:
# tacmd cleardeploystatus -h hostname
Then issue the operation directly by using the Managed System Name parameter
(instead of the deploy group):
# tacmd updateAgent -t product_code -n managed_OS
Tivoli Enterprise Monitoring Server requires restart if you
issue itmcmd server stop/start commands when you are
already logged on
When you are logged in but restart the Tivoli Enterprise Monitoring Server using
itmcmd server
stop or start commands, you receive the message: KUICLR099E:
The command did not complete because of a system error. Refer to the log for
details and contact the system administrator.
A new login solves the problem and enables the tacmd listsystems command.
Log indicates hub monitoring servers are down when they are
up
The statusPut process fails periodically, resulting in an incorrect hub Tivoli
Enterprise Monitoring Server status. This condition is harmless and does not cause
any operational change by the software. The following is an example of the log:
Tue Jun 14 04:27:01 2005 KO41039 Error in request sqlRequest. Status= 1103.
Reason= 1103.
(42AEA2E5.0011-6:ko4sndrq.cpp,855,"IBInterface_sqlRequest") Distributed request
failed
(42AEA2E5.0012-6:ko4state.cpp,3519,"IBInterface_sendInsert") send insert has no
request handle error
(42AEA2E5.0013-6:ko4ibput.cpp,1407,"IBInterface:insertProcessing")
General error <1103>
(42AEA2E5.0014-6:ko4ibput.cpp,1657,"IBInterface::put_sList")
table put error <1103>
(42AEA2E5.0015-6:ko4ibstr.cpp,1139,"IBStream::insertDef") IB Err: 1103
(42AEA2E5.0016-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
(42AEA2E5.0017-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
(42AEA2E5.0018-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
(42AEA2E5.0019-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
(42AEA2E5.001A-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
Tue Jun 14 04:27:01 2005 KO41034
Monitoring for situation UADVISOR_OMUNX_SP2OS
Chapter 9. Monitoring server troubleshooting
163