IBM Tivoli Monitoring > Version 6.3 > User's Guides > System p Agent User's Guides > AIX Premium User's Guide > Troubleshooting > Problems and workarounds IBM Tivoli Monitoring, Version 6.3


Installation and configuration troubleshooting

Problems can occur during installation, configuration, and uninstallation of the agent.

The problems and solutions in Table 1 can occur during installation, configuration, and uninstallation of the agent.


Problems and solutions for installation and configuration

Problem Solution
(UNIX only) During a command-line installation, you choose to install a component that is currently 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.

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 a UNIX system.

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 currently installed.
A message similar to "Unable to find running CMS on CT_CMSLIST" in the log file is displayed. If a message similar to "Unable to find running CMS on CT_CMSLIST" is displayed in the log file, the agent cannot 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 KPXCMA process. If CPU usage seems to be excessive, restart the monitoring agent.

Network cards: The network card configurations can decrease the performance of a system. Each stream of packets that a network card receives (assuming that 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 32-bit and are based on PCI or EISA bus architectures.

The artwork in the installation panels in the Japanese environment are missing, and some panels have a truncation problem. No solution is available for this problem at this time.
In the Install Prerequisites panel during agent installation, the following extra string displays in Russian: \r No solution is available for this problem at this time.
In the Select Features panel during agent installation, the Description of each feature is in English only. No solution is available for this problem at this time.
The following warning message is displayed during application support installation KCIIN1421W WARNING - unable to copy eclipse agent plugin file

$CANDLEHOME/$ITM_BINARCH/cw/iehs/kpc/eclipse/plugins/com.ibm.kpc.doc

where, pc is your two character product code.

Manually rename or delete the agent plug-in file and run the application support installation again.
Cannot find the agent support files for the Linux operating system. Support files for all IBM Tivoli Monitoring supported operating systems are located on the support file image. Support files for the AIX operating system are located on the agent image.
The configuration panel is blank on 64-bit Windows systems where the Tivoli Enterprise Monitoring Agent Framework (component GL) is version 06.23.00.00 or 06.23.01.00. Check the GL component version by running kincinfo -t GL from a Windows command line. Example:

    %CANDLE_HOME%\InstallITM\kincinfo -t GL

If the GL component version is 06.23.00.00 or 06.23.01.00, take one of the following actions:

  • Preferred action: Upgrade the Windows OS Agent to Version 6.2.3 Fix Pack 2.
  • Alternate action: Install the Agent Compatibility (AC) component from the IBM Tivoli Monitoring V6.2.3 Fix Pack 1 media. See Install the Agent Compatibility (AC) component (http://pic.dhe.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.itm.doc_6.2.3fp1/itm623FP1_install199.html#acpinstall).


General problems and solutions for uninstallation

Problem Solution
The way to remove inactive managed systems (systems whose status is OFFLINE) from the Navigator tree in the portal is not obvious. 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, and then click Workspace > Managed System Status.

  3. Right-click the offline managed system, and select Clear offline entry.

To uninstall the monitoring agent, use the procedure described in the IBM Tivoli Monitoring Installation and Setup Guide.

While running ./uninstall.sh to uninstall the agent, one of its components, or both, you receive the following error message and the uninstallation does not complete: uninstall.sh failure: KCI0766E could not find arch "aix536" in a JRE version file. Use the following separate, manual procedure for uninstalling the system monitor agent that monitors the Linux or UNIX operating system:

  1. Stop the agent by running the following command: InstDir/bin/itmcmd agent stop all

  2. Stop any other agents running from the same InstDir directory.

  3. Issue the following command: InstDir/bin/uninstall.sh REMOVE EVERYTHING

Running the uninstall.sh script with REMOVE EVERYTHING removes all agent files and deletes the installation subdirectory tree.

The software inventory tag for the agent on UNIX and Linux systems is not removed during uninstallation of the agent. After uninstalling the agent, manually remove the file named full name of agent.cmptag from the $CANDLEHOME/properties/version/ directory.


Parent topic:

Problems and workarounds

+

Search Tips   |   Advanced Search