Installation and configuration troubleshooting

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

Table 6. Problems and solutions for installation and configuration
Problem Solution

Unable to install the monitoring agent on a Windows 2008 64-bit Enterprise Edition system.

Confirm if you are at the supported level. For more information, see Requirements for the monitoring agent.

Increase the tracing on the Windows OS agent. Set maximum tracing on the agent. For instructions, see Setting RAS trace parameters.

A problem can arise when you install and configure a new monitoring agent to 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.
After upgrading to v6.2.2 Fix Pack 1, I found an error message in the log file.

Here is the found error message:

(4A952800.001C-458:kraacthi.cpp,985,"parseXMLfile") 

<0x38C53F0,0x1DB> XMLError: 

Parse error not well-formed (invalid token) in 

C:\IBM\ITM\TMAITM6\Primary_NC124022_NT_thresholds.xml, 

line 13:
Could be there are multiple \r in the file (^M)
Error Message - Could not open DNS registry key This message is informational only. No action is required. The Windows agent reports the fact that it could not find a registry entry for the DNS Server Event Log. This means that the DNS Server is not installed.
The following problems occur in workspace views:
  • The Monitored Logs workspace shows a record count of zero (0).
  • The Event Logs workspace shows no records.

Windows security logging is not turned on by default. Normally, no data is collected in the security log unless the Windows administrator turns it on. The Record Count = 0 data value that the monitoring agent returns in the Windows monitored logs report confirms that security logging is not turned on.
Diagnosing problems with product browse settings. When you have problems with browse settings, perform the following steps:
  1. Click on Start > Programs > IBM® Tivoli® Monitoring > Manage Tivoli Enterprise Monitoring Services. The Manage Tivoli Enterprise Monitoring Services 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. If requested, you can forward this file to IBM Software Support for analysis.
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 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 after you install or configure Monitoring Agent for Windows OS.

Agent process: View the memory usage of the KNTCMA 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 off-loaded 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.
You successfully migrate an OMEGAMON® monitoring agent to IBM Tivoli Monitoring, Version 6.2.0. However, when you configure historical data collection, you see an error message that includes, Attribute name may be invalid, or attribute file not installed for warehouse agent.

Install the agent's application support files on the Tivoli Enterprise Monitoring Server, using the following steps:

  1. Open the Manage Tivoli Enterprise Monitoring Services window.
  2. Right-click the name of the monitoring server.
  3. Select Advanced > Add TEMS Application Support in the pop-up menu. Add application support if any for any agent that is missing from the list. See in IBM Tivoli Monitoring Installation and Setup Guide for more information on adding application support.

Ensure that the agent's application support files are pushed to the system that houses the Warehouse Proxy Agent. The Warehouse Proxy must be able to access the short attribute names for tables and columns. That way, if the longer versions of these names exceed the limits of the Warehouse database, the shorter names can be substituted.
Table 7. General problems and solutions for uninstallation
Problem Solution
On Windows, uninstallation of IBM Tivoli Monitoring fails to uninstall the entire environment.

Be sure that you follow the general uninstallation process described in the IBM Tivoli Monitoring Installation and Setup Guide:

  1. Uninstall monitoring agents first, as in the following examples:
    • Uninstall a single monitoring agent for a specific database.

      —OR—

    • Uninstall all instances of a monitoring product, such as IBM Tivoli Monitoring for Databases.
  2. Uninstall IBM Tivoli Monitoring.

See the IBM Tivoli Monitoring Troubleshooting Guide and the section on installation problems for more information on how to remove the entire environment.
The way to remove inactive managed systems (systems whose status is OFFLINE) from the Enterprise navigation tree in the portal is not obvious. When you want to remove a managed system from the navigation tree, complete the following steps:
  1. Click Enterprise in the navigation tree.
  2. Right-click Workspace -> Managed System Status.
  3. Right-click the offline managed system and select Clear offline entry.

Unique names for monitoring components

You must decide how to name the monitoring agents. This name is intended to uniquely identify that monitoring agent. The agent's default name is composed of three qualifiers:

An agent name truncation problem can occur when the network domain name is included in the network host name portion of the agent name. For example, instead of just the host name myhost1 being used, the resulting host name might be myhost1.acme.north.prod.com. Inclusion of the network domain name causes the agent name in the example above to expand to SERVER1:myhost1.acme.north.prod.com:KXX. This resulting name is 39 characters long. It is truncated to 32 characters resulting in the name SERVER1:myhost1.acme.north.prod.

In general, create names that are short but meaningful within your environment. Use the following guidelines:

Create the names by completing the following steps:

  1. Open the configuration file for the monitoring agent, which is located in install_dir\tmaitm6_x64\Kproduct_codeCMA.INI if you have installed a 64-bit agent or install_dir\tmaitm6\Kproduct_codeCMA.INI if you have installed a 32-bit agent. For example, the product code for the Monitoring Agent for Windows OS is NT and the file name is KNTCMA.INI.
  2. Find the line the begins with CTIRA_HOSTNAME=.
  3. Type a new name for host name that is a unique, shorter name for the host computer. The final concatenated name including the subsystem name, new host name, and NT, cannot be longer than 32 characters.
    Note:
    You must ensure that the resulting name is unique with respect to any existing monitoring component that was previously registered with the Tivoli Enterprise Monitoring Server.
  4. Save the file.
  5. Restart the agent.
  6. If you do not find the files mentioned in Step 1, perform the workarounds listed in the next paragraph.

If you do not find the files mentioned in the preceding steps, perform the following workarounds:

  1. Change CTIRA_HOSTNAME environment variable in the configuration file of the monitoring agent.
    • Find the KNTENV file in the same path mentioned in the preceding row.
  2. If you cannot find the CTIRA_HOSTNAME environment variable, you must add it to the configuration file of the monitoring agent:
    • On Windows: Use the Advanced > Edit Variables option.
  3. Some monitoring agents (for example, the monitoring agent for MQ Series) do 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.