IBM Support

Upgrading Shared Components for IBM Tivoli Monitoring Agents

Technote (FAQ)


Question

How do I upgrade the shared components that are a part of IBM Tivoli Monitoring agents?

Cause

IBM Tivoli Monitoring agents installed in the same CANDLEHOME directory will share certain components, such as IBM Tivoli Monitoring Shared Libraries (ax) , GSKit (gs) or Java(R) (jr). In order to fix problems or prevent security violations, you might need to upgrade these components. The cinfo or kincinfo command will list these components as:


    ax IBM Tivoli Monitoring Shared Libraries
    <platform> Version: 06.xx.yy.zz

    gs IBM GSKit Security Interface
    <platform> Version: 06.xx.yy.zz

    jr Tivoli Enterprise-supplied JRE
    <platform> Version: 06.xx.yy.zz

The components might have more than one platform listed, and the versions might be at different levels. For example,
    gs IBM GSKit Security Interface
    aix523 Version: 07.40.27.00
    aix526 Version: 08.00.50.01

After upgrading, all platforms for all shared components should be at the same and latest levels. For example,
    gs IBM GSKit Security Interface
    aix523 Version: 08.00.50.05
    aix526 Version: 08.00.50.05

The "cinfo -t <COMPONENT>" command can be used to list the versions of a single component. This can be used in conjunction with the "tacmd executecommand" to remotely query the version of remote systems.

where:
<COMPONENT> is the shared component. For example: ax, gs, or jr

Answer

  • If the OS agent is one of the agents sharing the CANDLEHOME directory, first upgrade the OS agent, then check the shared components using "cinfo" (on UNIX or Linux) or "kincinfo" (on Windows). In most cases, upgrading the OS agent will upgrade the shared components to the latest level.
  • If the upgrade is provided in a provisional fix, follow the instructions included in the README for that fix.
  • If the upgrade is provided in a release or fix pack, follow these steps:


    For a local installation, run a command like the following:

    <MEDIA>/install.sh -h <CANDLEHOME> -q -p <MEDIA>/unix/tf<PLAT>.txt

    where:
    <MEDIA> is the release or fix pack media directory, such as 6.3.0-TIV-ITM_TMV-Agents-FP0002
    <PLAT> is the platform code from the "cinfo -i" report where the share library information is less than the required level.

    For remote installation, run commands like the following on the Monitoring Server system:

    On a UNIX/Linux system:

    <CANDLEHOME>/bin/tacmd login -t 1440 -s ....
    <CANDLEHOME>/bin/tacmd addbundles -n -t tf -i <MEDIA>/unix
    <CANDLEHOME>/bin/tacmd listsystems -t lz ux
    <CANDLEHOME>/bin/tacmd updateframework -n <NODE> -v <VERSION>

    where:
    <MEDIA> is the release or fix pack media directory, such as 6.3.0-TIV-ITM_TMV-Agents-FP0002
    <NODE> is one of the Managed System Names listed by the tacmd listsystems invocation above,
    <VERSION> is the version of the release or fix pack, such as 063002000.

    On a Windows system:
    tacmd addbundles -n -t tf -i <MEDIA>\unix
    tacmd login -t 1440 -s ....
    tacmd listsystems -t lz ux
    tacmd updateframework -n <NODE> -v <VERSION>

    where:
    <MEDIA> is the release or fix pack media directory, such as 6.3.0-TIV-ITM_TMV-Agents-FP0002
    <NODE> is one of the Managed System Names listed by the tacmd listsystems invocation above,
    <VERSION> is the version of the release or fix pack, such as 063002000.

Run the cinfo or kincinfo command again to verify that all the shared components are at the same and latest level for all platforms.

Product Alias/Synonym

ITM

Document information

More support for: IBM Tivoli Monitoring V6

Software version: 6.2.2, 6.2.3, 6.3

Operating system(s): AIX, HP-UX, Linux, Solaris, Windows

Reference #: 1673490

Modified date: 25 August 2014