Installation and configuration troubleshooting

This section provides tables that show solutions for installation, configuration, and uninstallation problems.

Problems and solutions for installation and configuration

Table 1. Problems and solutions for installation and configuration
Problem Solution
(UNIX only) During a command-line installation, you choose to install a component that is already installed, and you see the following warning: WARNING - you are about to install the SAME version of component_name, where component_name is the name of the component that you are attempting to install.
Note: This problem affects UNIX command-line installations. If you monitor only Windows environments, you see this problem if you choose to install a product component (for example, a monitoring server) on UNIX.
 You must exit and restart the installation process. You cannot return to the list where you selected components to install. When you run the installer again, do not attempt to install any component that is already installed.
A problem can arise when you install and configure a new monitoring agent on a computer where other agents are running, as described in this example:
  • Agents are running on computer and communicating with a Tivoli Enterprise Monitoring Server, called TEMS1.
  • You install a new agent on the same computer and you want this agent to communicate with a different monitoring server, called TEMS2.
  • When you configure the new agent to communicate with TEMS2, all the existing agents are re-configured to communicate with TEMS2.
 You must reconfigure the previously existing agents to restore their communication connection with TEMS1. For example, you can right-click the row for a specific agent in the Manage Tivoli Enterprise Monitoring Services, and select Reconfigure. See the IBM Tivoli Monitoring Installation and Setup Guide for more information on reconfiguration.
Diagnosing problems with product browse settings (Windows systems only) When you have problems with browse settings, perform the following steps:
  1. Click Start > Programs > IBM Tivoli Monitoring > Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli Enterprise Monitoring Services window is displayed.
  2. Right-click the Windows agent and select Browse Settings. A text window is displayed.
  3. Click Save As and save the information in the text file.
A message similar to Unable to find running CMS on CT_CMSLIST is displayed in the log file. If a message similar to Unable to find running CMS on CT_CMSLIST is displayed in the Log file, the agent is not able to connect to the monitoring server. Confirm the following points:
  • Do multiple network interface cards (NICs) exist on the system?
  • If multiple NICs exist on the system, find out which one is configured for the monitoring server. Ensure that you specify the correct host name and port settings for communication in the IBM Tivoli Monitoring environment.
The system is experiencing high CPU usage. Agent process: View the memory usage of the KRGCMA process. If CPU usage seems to be excessive, recycle the monitoring agent.

Network Cards: The network card configurations can decrease the performance of a system. Each of the stream of packets that a network card receives (assuming it is a broadcast or destined for the under-performing system) must generate a CPU interrupt and transfer the data through the I/O bus. If the network card in question is a bus-mastering card, work can be offloaded and a data transfer between memory and the network card can continue without using CPU processing power. Bus-mastering cards are generally 32-bit and are based on PCI or EISA bus architectures.
Table 2. General problems and solutions for uninstallation
Problem Solution
On Windows, uninstallation of IBM Tivoli Monitoring fails to uninstall the entire environment. Be certain that you follow the general uninstallation process that is described in the IBM Tivoli Monitoring Installation and Setup Guide:
  1. Remove Tivoli Enterprise Monitoring Server Application support by completing the following steps:
    1. Use Manage Tivoli Enterprise Monitoring Services.
    2. Select Tivoli Enterprise Monitoring Server.
    3. Right-click and select Advanced.
    4. Select Remove TEMS application support.
    5. Select the agent to remove its application support.
  2. Uninstall monitoring agents first, using one of the following methods:
    • Uninstall a single monitoring agent for a specific database.
    • Uninstall all instances of a monitoring product, such as IBM Tivoli Monitoring for Databases.
  3. Uninstall IBM Tivoli Monitoring.
It is not obvious how to remove inactive managed systems (systems whose status is OFFLINE) from the Navigator tree in the portal. Use the following steps to remove, but not uninstall, an offline managed system from the Navigator tree:
  1. Click the Enterprise icon in the Navigator tree.
  2. Right-click, then click Workspace > Managed System Status.
  3. Right-click the offline managed system, and select Clear offline entry.

If you also want to uninstall the monitoring agent, use the procedure described in the IBM Tivoli Monitoring Installation and Setup Guide.