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

Page: 174 / 310

Distribution to a monitoring server on the Object group editor is not equivalent to
a monitoring server distribution in the historical collection configuration window.
To decrypt a password, KDS_VALIDATE_EXT='Y' is required
KDS_VALIDATE_EXT='Y' is required on a SLES 10 64-bit zLinux monitoring server
to successfully decrypt a password sent by the portal server for validation. This
operating system uses Pluggable Authentication Modules (PAM) and this
monitoring server parameter for this purpose. For all other purposes, PAM is not
supported by adding the parameter KDS_VALIDATE_EXT=Y to a monitoring
server configuration.
Remote Tivoli Enterprise Monitoring Server consumes high
CPU when large number of agents connect
In enterprise environments, a large number of agents can connect to a remote
Tivoli Enterprise Monitoring Server in a short period of time. Examples of when
this might occur are during startup of the Tivoli Enterprise Monitoring Server, or
when agents failover from a primary to secondary Tivoli Enterprise Monitoring
Server. In these cases, the amount of CPU processing is directly proportional to the
total number of situations that have been distributed to agents connected to the
remote Tivoli Enterprise Monitoring Server. For example, if there are 1000 agents
connecting to the remote Tivoli Enterprise Monitoring Server, and each agent has
an average of 20 situations distributed to it, the total number of situations
distributed to agents connected to the remote Tivoli Enterprise Monitoring Server
would be 20 thousand.
To minimize the amount of CPU processing when a large number of agents
connect, consider reducing the total number of situations distributed by avoiding
distribution of situations that are not being used. Some situations, including
predefined situations, have the default distribution set as a managed system list.
These situations are distributed to all managed systems in the managed system list,
even if the situation is not being used. Limiting the distribution to only managed
systems where the situation will be used minimizes the total number of situations
distributed from the remote Tivoli Enterprise Monitoring Server, and minimizes the
CPU processing when a large number of agents connect.
The distribution specification for a situation can be changed using the Situation
editor or the
tacmd editsit
command.
Unable to start the Tivoli Enterprise Monitoring Server after
the kdsmain process is terminated abnormally
When the kdsmain process is terminated abnormally, a stale cms process is left
behind. This stale cms process prevents the proper startup of the Tivoli Enterprise
Monitoring Server. The cms process should be killed first, and then a startup of the
Tivoli Enterprise Monitoring Server should be retried for a successful startup. A
restart of the Tivoli Enterprise Monitoring Server should be attempted only after
verifying the
CMS.EXE
process is also terminated. A
CMS.EXE
left running in response
to the earlier failure is likely to cause a subsequent start of Tivoli Enterprise
Monitoring Server to fail.
156
IBM Tivoli Monitoring: Troubleshooting Guide