TACMD Remote Deploy Not Working

Remote deploying the ITDS Agent for ITM is unsuccessful when performed via the IBM Tivoli Monitoring tacmd CLI.

A TACMD remote deploy of the ITDS agent will not work if an '=' sign (equal sign) is used as a configuration value.  Since an equal sign will almost aways be part of the Distinguished Name(DN) of the user that agent connects to ITDS with (eg cn=root) this issue is encountered. IBM has identified this as a TACMD related defect (Defect#: IZ47331)and is slated to be fixed with ITM 6.2.1 IF4.

Either upgrade the TEMA to ITM 6.2.1 IF4 (or higher) or locally installed the ITDS Agent.

TACMD Remote Deploy Not Working

Remote deploying the ITDS Agent for ITM is unsuccessful when performed via the IBM Tivoli Monitoring tacmd CLI.

A TACMD remote deploy of the ITDS agent will not work if an '=' sign (equal sign) is used as a configuration value.  Since an equal sign will almost aways be part of the Distinguished Name(DN) of the user that agent connects to ITDS with (eg cn=root) this issue is encountered. IBM has identified this as a TACMD related defect (Defect#: IZ47331)and is slated to be fixed with ITM 6.2.1 IF4.

Either upgrade the TEMA to ITM 6.2.1 IF4 (or higher) or locally installed the ITDS Agent.

More Files than expected in results

More files than expected are in the results of a File and Directories configuration configuration directive

• Check the regular expression and be sure to escape with a '\' any instance of the '.' (dot) character that was intended to be literal. Many users make the mistake of confusing shell wild card behavior with full regular expressions. 

• Although soft links are ignored, hard links are not. When the file count is given in a directory, it will include all handles. If a single file has four links, that file will be counted and measured four times.

On Windows Servers, Agent skipping configuration directives with logged error "...skipping symbolic link"

• On Windows, the Files and Directories performs its scans for files and directories based on directives that have been defined by the user in the directives file.  The directives implemented in the directive file are evaluated in a case-sensitive manner, even on Windows.  Verify that you directives are all written in a case-sensitive manner, where path names are defined exactly as they appear on the filesystem.

More Directories than expected in results

Directories missing from the results of a Files and Directories directive

• Directories in the file system which are soft links are skipped by the agent. The agent does not follow soft links to avoid endless looping on some platforms, such as the Linux /proc directories. However, the agent will the “path” field in the directive to be a soft link. Any subsequent soft links will be skipped. 

• The agent may not have sufficient permissions to read a file or directory. This lack of privilege may include the Path value of the directive. If this is the case, the actual result of the scan may be well below expectation.

TEMA not preinstalled

On Windows, when running the Installer for a Blue Medora monitoring agent for IBM Tivoli Monitoring, the following error message is displayed:

"The environmental variable CANDLE_HOME is not set in this system. Please set it and run the installer again".

All Blue Medora monitoring agents for IBM Tivoli Monitoring require a pre-existing IBM TEMA exist before installation. Typically, an IBM Tivoli Monitoring Windows, Unix, or Linux OS Agent fulfills this requirement. Once an IBM agent with a TEMA has been installed, restart the Installer and enter the path of the pre-existing IBM Tivoli Monitoring installation (typically C:\IBM\ITM) when prompted to "Enter your Tivoli Monitoring installation directory".

Note: In addition to the ITM OS Agents, most other IBM ITM agents (such as the Oracle, DB2, MS-SQL, etc) also include the required TEMA files.

JRE 1.5 not in path

Whole Attributes groups are not returning data, although the agent itself is reporting Availability and Log related data in the TEPS.

Java 1.5 or greater is required to run most Blue Medora ITM Agents. The local installer for Windows installs Java 1.5 as part of the installation process. When performing a remote deploy of the agent to Windows systems, Java 1.5 or greater must already exist or be manually installed on the target system before the remote deploy is executed.

After Java is installed, JAVA_HOME must be set in the system environment and %JAVA_HOME%\bin must be on the system PATH. JAVA_HOME must be set to the top level Java directory, which is the directory with bin and lib subdirectories (for example,. C:\Program Files\IBM\Java50\jre). When JAVA_HOME is set correctly and %JAVA_HOME%\bin is part of the system PATH, then running java.exe from a command prompt displays the Java command usage help. If JAVA_HOME is not set correctly, the output of entering “java” or “java.exe” at the command prompt is:

“the command is not recognized as an internal or external command, operable program, or batch file.”

Note: If the system-wide Java installation is not at least 1.5, then the monitoring agents will not run. If the system Java installation cannot be upgraded, then you can install Java 1.5 into another directory and direct the agent to use the newly installed 1.5 Java installation. To change which version of Java the monitoring agent uses, edit KBx_run.bat files that exist in the IBM Tivoli Monitoring installation directory. The exact location differs depending on platform. The batch files assume that a working JAVA_HOME and PATH exist in the environment, so you can change the batch files to set JAVA_HOME and PATH to a different Java installation.

Blue Medora ITM Monitoring agents containing configuration properties requires IBM Tivoli Monitoring to install the Java™ Runtime Environment. If the Monitoring Agent for Windows OS was installed using the tacmd createnode command to create an IBM Tivoli Monitoring v6.2 Fix Pack 1: Windows OS Agent, then the Java Runtime Environment will not be installed. On this system, you cannot locally configure any Agent Builder created agents that contain configuration properties.

• Install an IBM provided agent that requires the Java runtime.
• Install the Monitoring Agent for Windows OS locally instead of using the tacmd createnode command.
• Install a supported IBM ITM Monitoring Windows OS Agent using the tacmd createnode command instead of the IBM Tivoli Monitoring Windows OS Agent.

Agents not translated

Blue Medora ITM Monitoring agents are not translated when shown on the Tivoli Enterprise Portal.

None. Currently, Blue Medora ITM Monitoring agents are English only.

RAS1 log errors

I see the following in the RAS1 log for my Blue Medora ITM Agent. What does it mean?

(46C30EA0.0000-2180:getprocesscmdline.cpp,387,

"GetProcessCmdLine") 

Unable to read the process environment block.  

ReadProcessMemory returned 0.


(46C30EA0.0001-2180:getprocesscmdline.cpp,589,

"getPIDCommandLine") 

Failed to get process command line, pid(4) 

error: Only part of a ReadProcessMemory or 

WriteProcessMemory request was completed.

This can occur on some systems for the process that represents the 'system' in Windows. The process environment block is not available for this process. System is a special process and normally will not be one you are actually monitoring. If all of the data in your Availability table is filled in, then this does not represent a problem. You can verify this by checking the PID printed in the trace against the PIDs for the processes you are monitoring.

Removing an agent without a Tivoli Enterprise Portal

You want to remove a Blue Medora ITM agent, but you do not have a Tivoli Enterprise Portal.

To remove an agent that the Agent Builder generated from the target system, run the following commands:

Windows (where xx is the product code for the agent):

cd ITM_INSTALL/TMAITM6 
kxx_uninstall.vbs ITM_INSTALL

If you want to run the kxx_uninstall.vbs script from a script or from the command line, use the cscript kxx_uninstall.vbs command. (cscript.exe is the command line interface parser for vbs scripts and does not display a window; instead, a message is displayed on the console.)

UNIX (use the uninstall.sh file found in ITM_INSTALL/bin:

uninstall.sh [-f] [-i] [-h ITM_INSTALL] 

[product platformCode]

To remove an agent that the Agent Builder generated from the Tivoli Enterprise Portal, use the following procedure:

1. Ensure your Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server are up and running.
2. Log in to your Tivoli Enterprise Portal client.
3. From the Tivoli Enterprise Portal client Physical Navigator views, right-click Enterprise and select Workspace > Managed System Status. The Managed System Status workspace is displayed.
4. Select all of the IBM Tivoli Managed Systems for your agent.
5. Right-click and select Clear off-line entry, which clears all of the entries from that table.

Installed agent does not show up

An installed Blue Medora ITM agent does not show up in the Tivoli Enterprise Monitoring Services utility.

Select View > Refresh from the Manage Tivoli Enterprise Monitoring Services window.

Situations not showing up

The situations should be true (or my node should display the little red circle indicating that the situations are true), but they are not displayed as true. I checked and the data has exceeded the threshold. Why can't I see the situation on my node in the navigation tree.

Some of the associations between nodes and situations are loaded when the Tivoli Enterprise Portal starts. Restart the Tivoli Enterprise Portal.

Queries not showing up

The new queries are not showing up.

Install the agent and then recycle the Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal.

Error states the startagent command failed

A popup error on the Tivoli Enterprise Portal says that the "C:\IBM\ITM\InstallITM\Batch\kincli
-startagent -akxx" command failed.

Cannot remove agent from the Tivoli Enterprise Portal

When trying to remove a Blue Medora iTM  agent, you see that the agent is still listed in the desktop navigation view, but it is greyed-out.

This problem occurs if the agent remains in the managed system list in IBM Tivoli Monitoring. Perform the following steps:

1. Select the Enterprise node, which is the top node in the physical tree in the Tivoli Enterprise Portal.
2. Right-click Workspace > Managed System Status.
3. Select the entry for the agent. 
   Note:
   The name is displayed in the second column.
4. Right-click and select Clear offline entry.
5. The element is removed from the tree in the Tivoli Enterprise Portal.

Service or process monitoring returns zeros for metrics

When creating an agent to monitor Service availability, the column values are not correct. All metrics, including the Process ID, are zero.

For example:

• For Services, you might receive the following information:

  Status=UNKNOWN

  and zeros for the availability metrics.
• For Processes, you might receive the following information:

  Status= PROCESS_DATA_NOT_AVAILABLE

  and zeros for the availability metrics except for Process ID.

Ensure that the agent is being run under an Administrator ID.

UNKNOWN status displayed when trying to monitor a service

You try to monitor a service but the message Status=UNKNOWN is displayed, even though you have already verified that the agent has Administrator privileges.

The service is not installed on the system. When the view is being built for the Availability table, rows where the status is Unknown should be filtered out to prevent confusion, especially when an application is composed of a set of optional services. The lack of a service is not an error in this case; it is normal.

Do not see situations in the console

I installed my Blue Medora ITM agent, situations and workspaces. I configured the agent and started it. I see it in the Tivoli Enterprise Portal, but I do not see the situations in the navigator tree or the Situation Event Console. I have checked, and the situations are associated with the right nodes.

Restart the Tivoli Enterprise Portal.

One reason this could occur is that the ICCRTE_DIR might not be set in the ENV file on Windows systems.

ICCRTE_DIR=

find: ICCRTE_DIR=: No such file or directory

Local configuration JRE warning

Locally configuring an agent displays this warning: Kincfgexit Java Runtime Environment was not detected! Extended agent configuration is disabled - if remote configuration for the agent is supported, complete the process using the Tivoli Enterprise Portal.

Agent support files remain after uninstalling

After uninstalling an agent, the agent support files remain on the system.

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. Remove the agent from the Tivoli Enterprise Portal using the following procedure:
   1. Ensure that your Tivoli Enterprise Monitoring Server and Tivoli Enterprise Portal Server are up and running.
   2. Log in to your Tivoli Enterprise Portal client.
   3. From the Tivoli Enterprise Portal client Physical Navigator views, right-click Enterprise and select Workspace > Managed System Status. The Managed System Status workspace is displayed.
   4. Select all of the IBM Tivoli Managed Systems for your agent.
   5. Right-click and select Clear off-line entry, which clears all of the entries from that table.