The CT_GET request method fails in SOAP queries with a
V6.2.3 hub monitoring server, a remote hub monitoring server
earlier than V6.2.3, and an agent connected to a remote
monitoring server
In an environment comprised of a V6.2.3 hub monitoring server, a remote
monitoring server earlier than V6.2.3, and an agent connected to a remote
monitoring server, the CT_GET request method fails in soap queries with the
following error:
<xml version="1.0" encoding="UTF-8">
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault><faultcode>SOAP-ENV:Server</faultcode>
<faultstring>Unable to start request (67109066)</faultstring>
</SOAP-ENV:Fault></SOAP-ENV:Body></SOAP-ENV:Envelope>
To avoid this issue, install V6.2.3 application support files on the remote
monitoring server. After you restart the remote monitoring server, the SOAP
requests will work.
Exposure of passwords in the clear
Currently, all versions of IBM Tivoli Monitoring incorporating the IBM Tivoli
Directory Server Client at the monitoring server are exposed to an unaudited
security risk of exposure of passwords in the clear. To avoid displaying passwords
in the clear when troubleshooting LDAP problems, use the following option:
LDAP_DEBUG=65519
Receive a seeding failed message
Before you seed a remote monitoring server, you must ensure that the hub
monitoring server is running. However, if you receive this message, start the hub
monitoring server, and then manually seed the support using the itmcmd support
command.
High monitoring server CPU after restarting with Warehouse
Proxy Agents configured
About this task
A remote monitoring server process incurs significant CPU utilization or
percentage increases when any IBM Tivoli Monitoring Warehouse Proxy Agents
have been started in the hub monitoring server environment. Due to an issue in
the monitoring server KRANDREG module, the remote monitoring server can go
into a loop making continuous calls to the IBM Tivoli Monitoring Global Location
Broker facility. This loop can happen whenever the hub monitoring server Global
Location Broker contains EXACTLY 50 entries relating to the IBM Tivoli
Monitoring Warehouse Proxy Agent. The Global Location Broker is the hub
monitoring server facility that shows which remote monitoring server or
Warehouse Proxy Agents have been registered in this environment.
The total number of entries registered in the hub monitoring server Global
Location Broker from the Warehouse Proxy Agent are a combination of the
following amounts:
v The number of IBM Tivoli Monitoring network protocols configured for the
Warehouse Proxy Agent (for example, IP.PIPE, IP.SPIPE).
154 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
