Table of Contents
Advertisement
2. If you cannot find the CTIRA_HOSTNAME environment variable, you must add it to
3. Some monitoring agents (for example, the monitoring agent for MQ Series) do
Other symptoms that can be observed when multiple instances of a monitoring
agent with the same managed system name attempt to connect to a Tivoli
Enterprise Monitoring Server include the following:
v A managed system name's status toggles ON and OFF line constantly as one
v High CPU usage is observed that is caused by a constant thrashing of the Tivoli
v Situation distribution, Tivoli Enterprise Monitoring Server table relationship
Other solutions besides ensuring that each managed system name is unique are the
following:
v Detect and stop the agent process that is running improperly. This can be done
v If the agents running on the same system are the same product, stop or kill the
v Delete the faulty agent managed system name from the enterprise managed
One monitoring agent's workspaces are listed under another agent
node on the portal client
About this task
This problem has been seen in monitoring agents that exist on the same system.
Set the CTIRA_HOSTNAME environment variable configuration file for the
monitoring agent as follows:
1. Open the configuration file for the monitoring agent, which is located in the
192
IBM Tivoli Monitoring: Troubleshooting Guide
v For i5/OS agents, find the QAUTOTMP/KMSPARM library in member KBBENV.
the configuration file of the monitoring agent:
v On Windows: Use the Advanced > Edit Variables option.
v On UNIX and Linux: Add the variable to the config/product_code.ini and
to config/product_code.config files.
v On z/OS: Add the variable to the RKANPAR library, member
Kproduct_codeENV.
v On i5/OS: Add the variable to the QAUTOTMP/KMSPARM library in member
KBBENV.
not reference the CTIRA_HOSTNAME environment variable to generate component
names. Check the documentation for the monitoring agent that you are using
for information on name generation. If necessary, contact IBM Software
Support.
agent heartbeat overlays the other's information.
Enterprise Portal Server or Tivoli Enterprise Monitoring Server.
updates, Tivoli Enterprise Portal Server topology view updates; all could be
initiated as each agent heartbeat registers its changing properties.
by checking the Tivoli Enterprise Portal Server Managed System Status network
address of the managed system name that seems to toggle ON and OFF line. Go
to the system indicated in the network address and check for multiple running
monitoring agents.
unintended agent process.
system status so that the new managed system name can register properly with
the Tivoli Enterprise Monitoring Server. You might need to stop the correct agent
process so that it is OFF line.
following path:
Advertisement
Table of Contents
Troubleshooting
