TADDM Self Monitoring - TADDM/taddm-wiki GitHub Wiki

The Monitoring Agent for TADDM Serviceability and Manageability is available for download from the ISM library.

https://www-304.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10TA29

This can be used to install a monitoring agent that can connect to an existing TEMS, an SNMP receiver, or an EIF receiver. This guide addresses the installation and configuration of the agent in autonomous mode connecting to an SNMP receiver.

The package on ISM includes a User’s Guide that should be consulted during the install. The agent should be installed on all TADDM servers (not gateways or anchors).

Prerequisites

The monitoring agent is not compatible with TADDM v7.3.0.1 due to the new WebSphere Liberty server replacing Tomcat. The agent is compatible with TADDM v7.3.0.2 (FP2).

The installation requires root access.

The installation on Linux requires compat-libstdc++-33.3.2.3-69.el6.x86_64 package to be installed. You can check if your system has this package installed by issuing:

rpm -qa | grep "compat-libstdc++-33.3.2.3-69.el6.x86_64"

If you don't have this package installed, you will likely see the following error during installation.

runGSkit failure:  Return error code: 99.
runGSkit failure:  GSKit check failure, script: /opt/IBM/ITM/lx8266/gs/bin/private_verifyinstall_64.
runGSkit failure:  lx8266 - GSK check error, verifyInstall test failed.
install.sh failure: Return error code: 4.

Installation (Linux)

  1. Log on as root, extract KZA-Agent-Linux.tar and run install.sh.

  2. Use default install directory of /opt/IBM/ITM

  3. Select “Install products to the local host”

  4. Press enter to accept the default encryption key.

  5. Select “IBM Tivoli Monitoring components for this operating system”

  6. Select “Monitoring Agent for TADDM Serviceability and Manageability V07.22.00.00”

  7. Run the post-installation configuration command

    /opt/IBM/ITM/bin/itmcmd config -A za

  8. After answering 1 (Yes) to “Edit Monitoring Agent for TADDM Serviceability and Manageability settings?” and “Edit TADDM User Account settings?”, use the default user name and password (leave it blank) for accessing the TADDM server with the default administrator account and password. Obviously use different values for your TADDM server if needed.

  9. When asked "Will this agent connect to a TEMS?" Select No (2). We will be configuring this for SNMP alerts.

  10. This step might not be necessary. Even though the agent is installed using root, it needs to run under the TADDM application account (e.g. taddmusr). Depending on how your security is set up, you may need to change permissions so that the TADDM account can start the monitoring agent.

chmod -R a+rx /opt/IBM
  1. To configure the SNMP traps you must create /opt/ibm/cmdb/ITM/localconfig/za/za_trapcnfg.xml if it doesn’t already exist and configure the trap destinations. In the sample below, two trap destinations are configured and all situations are sent to all trap destinations.
<!-- /opt/IBM/ITM/localconfig/za/za_trapcnfg.xml -->  
<SNMP>  
    <TrapDest name="snmp01" Address="snmp01.ibm.com" />  
    <TrapDest name="snmp02" Address="snmp02.ibm.com" />  
  
    <situation name="*" target="*" />  
</SNMP>
  1. To start the agent, log on as the TADDM account (taddmusr) and run the following.
/opt/IBM/ITM/bin/itmcmd agent start za
  1. The agent needs to run as the TADDM account (taddmusr) so that the environment is setup properly to call the dist/bin/healthcheck script (this is how it works). During the install, the agent is configured to start at system boot. However, by default the agent will start as root. The agent will fail and TADDM account will be unable to stop the root process. The script to stop and start the agent will be under /etc/init.d/ and will start with ITMAgents. As root, find the script that starts the agent and edit that script. On the line that starts the agent change root to your TADDM account (taddmusr by default). Now the agent will start as the TADDM user on system reboots and function properly.

Providing MIBs to the SNMP receiver

The administrator for the SNMP receiver will need the MIB files to configure the traps. The user's guide states that the MIB files are packaged with the agent installation but at this point in time (July, 2014) that is not true. The MIB files are found in ITM 6.2.3 FP2 and can be downloaded through IBM Fix Central. Download the 3.36 GB file named 6.2.3-TIV-ITM_TMV-Agents-FP0003.tar.gz. Extract the file and under 6.2.3-TIV-ITM_TMV-Agents-FP0003/mibs you will find cansyssg.mib and canbase.mib. Send these files to the administrator for the SNMP receiver so that they can configure the traps.

Agent fails on TADDM 7.3 GA

The agent uses the dist/bin/healthcheck script in TADDM to check the status of TADDM for monitoring. In TADDM 7.3 GA, there is a bug in the checkTaddmStatus module that prevents the agent from working correctly. To workaround this bug, edit dist/lib/healthcheck/checkTaddmStatus.py. Go to line 205 and wrap that section with a try/except/pass as follows.

try:
    max_mem = self.mem_to_mb(service_handle.getMaxMemory())
    free_mem = self.mem_to_mb(service_handle.getFreeMemory())
    total_mem = self.mem_to_mb(service_handle.getTotalMemory())
    thread_count = service_handle.getThreadCount()
    running_thread_count = service_handle.getRunningThreadCount()
except:
    pass

Ensure that you keep your indention correct as Python runs off of indented script.

⚠️ **GitHub.com Fallback** ⚠️