Tivoli Log File Agent, Version 6.2.3.2 Interim Fix 04 6.2.3.2-TIV-ITM_LFA-IF0004

Downloadable files


Abstract

This fix resolves the APARs and defects listed in the "Problems Fixed" section below. This fix also includes the superseded fixes listed in section 2.3.

Download Description

(C) Copyright International Business Machines Corporation 2013.

All rights reserved.

Component: Tivoli® Log File Agent,
Version 6.2.3 Fix Pack 2

Component ID: 5724C04LF

Interim Fix: 0004, (6.2.3.2-TIV-ITM_LFA-IF0004)

Date: April 16, 2013

Contents:

1.0 General description
2.0 Problems fixed
3.0 Architecture and prerequisites
4.0 Image directory contents
5.0 Installation instructions
6.0 Additional installation information
7.0 Known problems and workarounds
8.0 Additional product information
9.0 Copyright and trademark information
10.0 Notices


1.0 General description
===============
This fix resolves the APARs and defects listed in the "Problems Fixed"
section below. This fix also includes the superseded fixes listed in
section 2.3.


2.0 Problems fixed
============
The following problems are addressed by this fix.

2.1 APARs
-------------

APAR: IV39967
Abstract: Restored file is not monitored after conf/fmt files
modified
Additional information: When the following series of events all
occur in this specific order while the agent is currently
monitoring a file:
- update the conf/fmt file
- remove the file, for example via unmount, rename, delete
- restore the file,
the log file is no longer monitored. The Data Collection
workspace continues to show a status of "FILE DOES NOT EXIST"
and no new events are processed. This problem occurs on Log
File Agent, v6.2.3.2.

With a minimum of "KBB_RAS1: (UNIT:kumpscan ALL)" tracing,
the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains a
repeated set of trace entries similar to the following:
- - -
...
...:kumpscan.c,82,"KUMP_TaskPeriodical") Getting GlobalDCHwaitLock
...:kumpscan.c,85,"KUMP_TaskPeriodical") Releasing GlobalDCHwaitLock
...:kumpscan.c,97,"KUMP_TaskPeriodical") Getting GlobalFileIOLock
...:kumpscan.c,117,"KUMP_TaskPeriodical") Releasing GlobalFileIOLock
...:kumpscan.c,402,"KUMP_TaskPeriodical") Scan waits on activity -
interval 1, delay 0
...
- - -

When it is working properly, the above trace includes one or
more messages similar to the following:
...:kumpscan.c,106,"KUMP_TaskPeriodical") Signaling IOptr ...

Note: When the file is rediscovered after it is restored, it is
read from the beginning as a new file. This is not new behavior
with this APAR.

2.2 Defects
--------------
None.

2.3 Superseded fixes
-------------------------
6.2.3.2-TIV-ITM_LFA-IF0003
6.2.3.2-TIV-ITM_LFA-IF0002
6.2.3.2-TIV-ITM_LFA-IF0001

2.4 APARs and defects included from superseded fixes
---------------------------------------------------------------

6.2.3.2-TIV-ITM_LFA-IF0003
--------------------------
APAR: IV37051
Abstract: EVENTS INTERMITTENTLY NOT MATCHED WHEN LINE WRITTEN IN
PIECES
Additional information: When an application writes only part of the
line and later writes the remainder of the line, the line
intermittently matches as an event with no changes to the fmt
file.

This occurs more prevalently on Windows® systems because the
operating system notifies the agent when the file has changed.
When the first part of the line is written, the agent is
notified but the partial line does not match any formats.
When the second part of the line is written, the agent is
notified again but the remainder of the line does not match
any formats. The two pieces of the line are treated as two
lines, neither of which match and both pieces are written as
two lines to the unmatch log.

This may also occur on UNIX® systems, if the first part of
the line is written and the second part of the line is not
written during the same processing cycle.

APAR: IV36725
Abstract: FILE EVENTS MAY BE INTERMITTENTLY LOST WHEN ALSO
MONITORING A PIPE
Additional information: Events from a log file may intermittently
not match, when also monitoring syslog, errpt or Windows
Event log in the same instance or subnode. This is only an
issue with single line format patterns.

If one line of the file is read followed by an end of file
(EOF), the line is matched. However, when multiple lines are
read in before reaching EOF, it does not match.

With tracing set to a minimum of
"KBB_RAS1: (UNIT:kumprmfr ALL) (UNIT:kumpfile ALL)", the agent
log <hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following:

- - -
... :kumprmfr.c,1061,"KUMP_ReadMonitorFileUnicodeRecord")
ReadCount RecordSetInfo 2 288943184 SetCount 100 table
! !!!!!!!!! !!!
<LogfileEvents> source <hostname>
- - -
where
- ReadCount is greater than 1 (ex: 2)
- SetCount is 100
- RecordSetInfo has a value (ex: 288943184)

- - -
...
... :kumpfile.c,372,"KUMP_FileServer") NextRecPos 470 RecCount 3
... :kumpfile.c,376,"KUMP_FileServer") <0x111724088,0xEA> File
Record Data ...
- - -
where
- RecCount is greater than 1 and the File Record Data contains
multiple records.

APAR: IV36678
Abstract: FILE WITH RETURN CODE 26, FILE BUSY IS NO LONGER MONITORED
Additional information: The Log File agent is monitoring a file on
a mounted file system. Once a day the file system is
unmounted and copied. The file system is remounted and the
log is created when a new entry is created. There is a timing
condition that happens where a return code 26, file busy is
returned while the file system is unmounted and remounted.
The log file is no longer monitored after the error code is
returned. The log shows the following:

- - -
(50F6C071.0001-14:kraaevst.cpp,678,"listSitStat") *STAT-INFO:
*********************************************
(50F811F1.0000-14:kraaevst.cpp,664,"listSitStat") *STAT-INFO:
*************** Situation Statistics Fri Jan 18 00:00:01 2013
(50F811F1.0001-14:kraaevst.cpp,678,"listSitStat") *STAT-INFO:
*********************************************
(50F8956B.0000-E:kumpwfrm.c,270,"KUMP_WaitFileReadyForMonitor")
Opening file /s01az03p06/p/BAXX/log/latest/BAXX.log
FILEEXISTWAIT=Y size 0
(50F8956B.0001-E:kumpwfrm.c,321,"KUMP_WaitFileReadyForMonitor")
*** Unable to open file /s01az03p06/p/BAXX/log/latest/BAXX.log
Errno: 26, ErrorText: Text file busy, NO retry. Exiting
(50F8956B.0002-E:kumpfdp5.c,342,"CheckFileExistAndReady") ***
File /s01az03p06/p/BAXX/log/latest/BAXX.log -- initial
monitoring setup
failed(50F8956B.0003-E:kumpfile.c,1113,"KUMP_FileServer") >>>>>
DP file server process ended for file
/s01az03p06/p/BAXX/log/latest/BAXX.log last position 175
current/last EOF 175/175. ThreadID: E
- - -

6.2.3.2-TIV-ITM_LFA-IF0002
--------------------------

APAR: IV33055
Abstract: LOG FILE AGENT CRASHES WITH (UNIT:KUMPFDP4 ALL) TRACING
Additional information: The Tivoli Log File Agent, version 6.2.3.2
crashes or goes offline when a new log file is detected to
monitor and the agent trace level is set to one of the
following: (UNIT:kumpfdp4 ALL) or (UNIT:kumpfdp ALL) or
(UNIT:KUM ALL). The kloagent process for that instance is no
longer running.

With (UNIT:kumpfdp ALL) tracing, the end of the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log is similar
to the following:

- - -
(<timestamp>:kumpfdp4.c,220,"VerifyFileEncodingType") Entry
(<timestamp>:kumpfdp6.c,236,"WaitUntilNextSampleTime") >>>>> Signal
received or wait time expired. IOptr 9F7F30 rc: 110
(<timestamp>:kumpfdp6.c,239,"WaitUntilNextSampleTime") Releasing ProcessEntry
- - -
As the crash occurs in the VerifyFileEncodingType function,
there is no Exit for the VerifyFileEncodingType function.

This problem was experienced on Linux® but may occur on
other platforms. It does not exist in prior or future
releases of the agent.

APAR: IV31931
Abstract: EIF: LFA CRASHES WHEN TWO SERVERLOCATIONS ARE SPECIFIED
Additional information: The agent crashes or cores when multiple
targets are specified for the ServerLocation and ServerPort
in the agent configuration file.

With "KBB_RAS1: ALL" tracing, the end of the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log contains
trace entries similar to the following where even though
getThisHostName returns the value of "hostname2",
name_resolute has the earlier or first value of "hostname1".
- - -
(<timestamp>:hntarget.c,140,"getThisHostName") obtained hostname
"hostname2"
(<timestamp>:hntarget.c,351,"name_resolute") <0xA3971C,0x4>
host=hostname1
- - -

The agent process might core with the following stack trace:
- - -
#0 0x451d7ad3 in name_resolute () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#1 0x451e3eac in resolve_connection () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#2 0x451e40f1 in get_connection () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#3 0x451e41ed in get_connection_n () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#4 0x451e31d0 in socket_try_put_event () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#5 0x451e30e7 in socket_put_event () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#6 0x451e2f3a in socket_put () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#7 0x451e1e92 in socket_sendOnTransport () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#8 0x451d4280 in tc_put_on_transportlist () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#9 0x451d45e3 in tc_put_f () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#10 0x451dfbf8 in send_event_packet () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#11 0x451dffcf in send_events_thread () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#12 0x451d6c2b in thread_func () from /opt/IBM/ITM/li6263/ms/lib/KFAOMTEC
#13 0x00bad341 in start_thread () from /lib/tls/libpthread.so.0
#14 0x00a3f6fe in clone () from /lib/tls/libc.so.6
---

This APAR is included in this fix for the Log File Agent on
Windows systems only. For UNIX/Linux systems, the fix is
included in IBM Tivoli Monitoring Shared Libraries (TEMA)
component of IBM Tivoli Monitoring version 6.2.3 or later.
You must install the Shared Libraries (ax) component
separately from the agent.

Defect: 195658
Abstract: Remove restarting from top sleep
Additional information: When using a wildcard or regex pattern to
specify which files to monitor, if a file that matches the
pattern is created while the agent was running, the agent
pauses after every 10 events it read from this new file. This
results in slow monitoring when a new file is discovered.
After an agent restart, this behavior stops.

The pause has been removed now, so existing files and new
files are treated the same way, improving the performance.

Defect: 190442
Abstract: LFA failed to monitor Windows event log on Windows 2012
Additional information: Windows event monitoring on Microsoft®
Windows Server 2012 fails to open the pipe to the Windows
event log. The pipe is used for communication by the agent
to send the events. As a result, no events are received at the
portal.

6.2.3.2-TIV-ITM_LFA-IF0001
--------------------------
APAR: IV26222
Abstract: LFA MONITORING RESTARTS FROM BEGINNING OF FILE ON I/O
ERROR
Additional information: During normal log file processing of the
monitored file, an I/O error might occur reading the monitored
file. This I/O return code is interpreted incorrectly such
that the agent starts reading the monitored file from the
beginning again.

With KBB_RAS1=ERROR level tracing, a message similar to the
following is seen in the agent log
<hostname>_<pc>_<instance>_k<pc>agent_<timestamp>.log, however
the file has not been recreated:
(<timestamp>:kumpfdp2.c,<line#>,"PrepareNewFileForMonitor")
File <monitored log file> switched or re-creation detected.
Restarting file monitoring from the beginning of the file.

APAR: IV25203
Abstract: FORMAT PATTERNS ,U AND ,RA AND ,RF FAIL TO MATCH DATA
Additional information: Formats whose patterns include "),U" or
"),RA" or "),RF' fail with a <U_REGEX_MISMATCHED_PAREN> and a
"*****Regular expression parsing error in pattern" error.
As a result, it may fail to match any data or more data than
expected.

For example, this pattern includes "),U" where there is a
close parenthesis followed by a comma followed by a U with no
spaces in between:
... (.*),ULD +,(.*),(.*),(.*) ...

With KBB_RAS1=ERROR level tracing, the following error is seen
in the agent log <hostname>_<pc>_<instance>_k<pc>agent_<timestamp>.log:
. . .
(<timestamp>:kum0regx.c,<line#>,"KUM0_OpenRegExPattern")
*****Error: uregex_open failed for pattern ...
pRegEx NULL status 66311 <U_REGEX_MISMATCHED_PAREN>

(<timestamp>:kumpiafi.c,<line#>,"KUMP_InitializeAttrFilterInfo")
*********Regular expression parsing error in pattern ...

APAR: IV24412
Abstract: ONE OR MORE SPACES ARE REMOVED FROM LOG RECORD
Additional information: When one or more blank characters (space
character x20) are the only data read into an internal buffer,
the blanks or spaces are removed.

For example, if the record was "1 2 3 4 5 6 7" and the blank
character between "6" and "7" was read into the internal
buffer, the resulting event record might appear as
"1 2 3 4 5 67"
where the blank character is removed between the 6 and 7.

APAR: IV22257
Abstract: "LABEL" KEYWORD DOES NOT GENERATE HOSTNAME IN MSG SLOT
Additional information: The LABEL keyword used in the format file
does not contain the host name of the system where the agent
is currently running when it is used in a PRINTF statement.
Instead, the actual variable specified for the LABEL is
contained in the slot. This also occurs for ORIGIN and
SUB_ORIGIN keywords.

For example, in a format file with
FORMAT Class_IV22257
%s* popenFAILED%s*
hostname Claude_momet
-tmp1 LABEL
origin PRINTF("%s", tmp1)
sub_origin PRINTF("%s", tmp1)
msg PRINTF("POPENFAILED at %s", tmp1)
END

the msg slot contains "POPENFAILED at -tmp1", where -tmp1
should contain the host name of the system (Claude_momet).
The msg slot should read "POPENFAILED at Claude_momet".


3.0 Architecture and prerequisites
======================
This fix is supported on all operating systems listed in the Tivoli
Log File Agent User's Guide, version 6.2.3.2.

Please refer to the IBM Software Product Compatability Reports (SPCR)
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html

3.1 Prerequisites for this fix
--------------------------------
The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring, Version 6.2.2: Fix Pack 02 or higher
(6.2.2-TIV-ITM-FP0002)
- IBM Tivoli Monitoring 6.2.3.2 Log File Agent Multiplatform
Multilingual (CI8WDEN) available from PassPort Advantage.

As this fix is cumulative, it can be installed on any fix level for
this version, release, and mod level above the prerequisite.

For details, see the Troubleshooting Wiki:
https://www.ibm.com/developerworks/mydeveloperworks/wikis/home?lang=en#/wiki/Tivoli%20Monitoring/page/Log%20File%20Agent

4.0 Image directory contents
===================
This fix image contains the following files:

- 6.2.3.2-TIV-ITM_LFA-IF0004.README
- 6.2.3.2-TIV-ITM_LFA-IF0004.tar
- 6.2.3.2-TIV-ITM_LFA-IF0004.zip.

Note: The .tar and .zip files are identical in content. Use the .tar
file if you are working in a UNIX environment; use the .zip file if
you are working in a Windows environment.

The fix archive file contains the following files:
6.2.3.2-TIV-ITM_LFA-IF0004/itmpatch.exe
6.2.3.2-TIV-ITM_LFA-IF0004/kloaix523.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_aix523_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/kloaix526.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_aix526_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/klohp11.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_hp11_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/klohp116.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_hp116_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/klohpi116.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_hpi116_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/kloli6263.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_li6263_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/klols3263.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_ls3263_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/klols3266.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_ls3266_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/klolx8266.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_lx8266_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/klosol283.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_sol283_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/klosol286.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_sol286_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/klosol606.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_sol606_tema_if0004.tar
6.2.3.2-TIV-ITM_LFA-IF0004/KLOWINNT.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_winnt_tema_if0004.cab
6.2.3.2-TIV-ITM_LFA-IF0004/KLOWIX64.dsc
6.2.3.2-TIV-ITM_LFA-IF0004/klo_wix64_tema_if0004.cab
6.2.3.2-TIV-ITM_LFA-IF0004/lo_dd_062204006.xml
6.2.3.2-TIV-ITM_LFA-IF0004/lo_dd.properties


5.0 Installation instructions
==================
This fix can only be installed over an existing installation. Use the
following steps to install this fix.

5.1 Before installing the fix
-------------------------------
- The prerequisites listed under section 3.1 entitled 'Prerequisites
for this fix' must be installed before this fix can be installed.

- For the purpose of this README, the symbol <CANDLEHOME> is the
IBM Tivoli Monitoring installation directory. The default value
for CANDLEHOME is '/opt/IBM/ITM' on UNIX systems and 'C:\IBM\ITM'
on Windows systems.

- Before installing this fix on UNIX systems, set the environment
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.

For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME

- Because there is no uninstall utility for this fix, make sure to
perform a backup of your environment before installing this fix.

5.2 Local agent update
--------------------------
1. Transfer the appropriate archive file
(6.2.3.2-TIV-ITM_LFA-IF0004.tar or .zip) to a temporary directory
on the system that contains the agent to be updated. For the
purpose of this README, the symbol <TEMP> represents the fully
qualified path to this directory. Note: On Windows systems, this
path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems
or an extract utility on Windows systems. This step creates a
directory structure that contains fixes for all of the supported
platforms.

3. Use the "itmpatch" command to install the fix for the operating
system of that agent. For more information on the "itmpatch"
command, see section 6.2.

On UNIX systems, if the fix was expanded to <TEMP>/6.2.3.2-TIV-ITM_LFA-IF0004,
the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.3.2-TIV-ITM_LFA-IF0004/klo_xxxxxx_tema_if0004.tar

where:
- xxxxxx corresponds to the value in the first column returned
by the ./cinfo -i command.

In the following example, the file is "klo_li6243_tema_if0004.tar".
> ./cinfo -i
lo Tivoli Log File Agent
li6263 Version: 06.23.02.00

On Windows systems, if the fix was expanded to
<TEMP>\6.2.3.2-TIV-ITM_LFA-IF0004, the install command is:

> <TEMP>\6.2.3.2-TIV-ITM_LFA-IF0004\itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.3.2-TIV-ITM_LFA-IF0004\klo_winnt_tema_if0004.cab

Note: The itmpatch.exe provided with older releases of IBM Tivoli
Monitoring did not support updating 64-bit Windows systems with
32-bit binaries. For 64-bit Windows systems, you must use the
itmpatch.exe provided with this interim fix.

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file
(6.2.3.2-TIV-ITM_LFA-IF0004.tar or .zip) to a temporary directory
on the IBM Tivoli Enterprise Monitoring Server system. For the
purpose of this README, the symbol <TEMP> represents the fully
qualified path to this directory. Note: On Windows systems, this
path includes the drive letter.

2. Expand the archive file using the "tar" command on UNIX systems or
an extract utility on Windows systems. This step creates a directory
structure that contains fixes for all of the supported platforms.

3. To add the agent fix bundles into the remote deploy depot, use
the "tacmd addBundles" command found in $CANDLEHOME/bin on UNIX
systems or in %CANDLE_HOME%\bin on Windows systems. For more
information on the "tacmd addBundles" command, see the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX systems,
if the fix was expanded to <TEMP>/6.2.3.2-TIV-ITM_LFA-IF0004:
> $CANDLEHOME/bin/tacmd addBundles -n
-i <TEMP>/6.2.3.2-TIV-ITM_LFA-IF0004

On Windows systems,
if the fix was expanded to <TEMP>\6.2.3.2-TIV-ITM_LFA-IF0004:
> %CANDLE_HOME%\bin\tacmd addBundles -n
-i <TEMP>\6.2.3.2-TIV-ITM_LFA-IF0004

where:
-n indicates that prerequisite bundles are not automatically
added. The -n parameter must be used because the fix
directory does not contain any prerequisites that the fix
might require. Please see Section 3.1 for the prerequisites
for this fix.
-i is the directory that contains the deployment bundles to be
added to the depot.

4. To log in to the Tivoli Enterprise Monitoring server, and deploy
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the
"tacmd login" and "tacmd updateAgent" commands, see the IBM Tivoli
Monitoring Administrator's Guide.

On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>

> $CANDLEHOME/bin/tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> $CANDLEHOME/bin/tacmd updateAgent -t lo
-n <Managed system name>
-v 062302004

On Windows systems:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems

The output shows the Managed System Name for the OS agent on the
remote system to be updated. Use this value as the target of the
"tacmd updateAgent" command.

> %CANDLE_HOME%\bin\tacmd updateAgent -t LO
-n <Managed system name>
-v 062302004

Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (LO), not three characters (KLO).
- The node (-n) for the "tacmd updateAgent" command is the managed
system name of the operating system (OS) agent to be updated.
The target node for the "tacmd updateAgent" command is always
an OS agent.

5.4 Agent support update
------------------------------
There are no agent support updates for the Tivoli Enterprise
Monitoring Server, Tivoli Enterprise Portal Server,or Tivoli
Enterprise Portal Desktop included in this fix or any of the
superseded fixes. No additional installation steps are required.

6.0 Additional installation information
========================

6.1 Installation instructions for agent baroc file
-----------------------------------------------------
There are no updates to the baroc files included in this fix or
any of the superseded fixes. No additional installation steps are
required.

6.2 Additional information on using "itmpatch" command
--------------------------------------------------------------
The "itmpatch" command has the following syntax:

Usage: itmpatch -h <installation home> [OPTIONS]

itmpatch -h <installation home>
-t { <patch_file_directory> | <patch_file> }

itmpatch -h <installation home>
-i { <patch_file_directory> | <patch_file> }

where:
-h Specifies the IBM Tivoli Monitoring installation directory
-i Specifies the path to the directory or patch file to be installed
-t Generates a report of the actions to be taken by the patch


For example, on UNIX systems:
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>

- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>

where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows systems, this path must include
the drive letter.
<TEMP> represents the fully qualified directory specification, where
the fix is located. On Windows systems, this must include the drive
letter.

6.3 Verifying the update
----------------------------
1. To verify the agent was updated correctly, use the "tacmd" command
to view the agent's current version after the agent is restarted.
You are required to log in to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.

For example:
On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring
installation directory, the default location is '/opt/IBM/ITM'.

> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t LO

On Windows systems, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory, the default location
is 'C:\IBM\ITM'.

> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>

> %CANDLE_HOME%\bin\tacmd listSystems -t LO

Note: The component (-t) for the "tacmd listSystems" command is
specified as two characters (LO), not three characters (KLO).

When the agent update is successful, the agent version is:
06.23.02.04.

After the agent is restarted, you can also use the GUI to verify
the agent was successfully updated.

For the agent on Windows systems, the version number is
06.23.02.04.

2. To verify the agent you are running contains the updates from the
fix, see the following lines in the agent log
<hostname>_lo_<instance>_kloagent_<timestamp>.log located in
$CANDLEHOME/logs on UNIX systems and
%CANDLE_HOME%\tmaitm6\logs on Windows systems:

<timestamp> Component: ira
<timestamp> Driver: afac_lfa_6232:201304151156/4328538.3
<timestamp> Timestamp: Apr 15 2013 ...
...
...
<timestamp> Component: kum
<timestamp> Driver: afac_lfa_6232:201304151156/4328538.1
<timestamp> Timestamp: Apr 15 2013 ...



7.0 Known problems and workarounds
=========================
None.


8.0 Additional product information
======================
None.


9.0 Copyright and trademark information
==================================
A current list of IBM trademarks is available on the Web at "Copyright
and trademark information" at www.ibm.com/legal/copytrade.shtml.


10.0 Notices
=======
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION
"AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Some jurisdictions do not allow disclaimer of express or implied
warranties in certain transactions, therefore, this statement may not
apply to you.

This information could include technical inaccuracies or typographical
errors. Changes are periodically made to the information herein; these
changes will be incorporated in new editions of the publication. IBM
may make improvements and/or changes in the product(s) and/or the
program(s) described in this publication at any time without notice.

Microsoft, Windows, and Windows Server are trademarks of Microsoft
Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States
and other countries.

Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.

Other company, product, or service names may be trademarks or service
marks of others.

Third-Party License Terms and Conditions, Notices and Information
-----------------------------------------------------------------
The license agreement for this product refers you to this file for
details concerning terms and conditions applicable to third party
software code included in this product, and for certain notices and
other information IBM must provide to you under its license to
certain software code. The relevant terms and conditions, notices and
other information are provided or referenced below. Please note that
any non-English version of the licenses below is unofficial and is
provided to you for your convenience only. The English version of the
licenses below, provided as part of the English version of this file,
is the official version.

Notwithstanding the terms and conditions of any other agreement you
may have with IBM or any of its related or affiliated entities
(collectively "IBM"), the third party software code identified below
are "Excluded Components" and are subject to the following terms and
conditions:

- the Excluded Components are provided on an "AS IS" basis
- IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND
CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT
NOT LIMITED TO, THE WARRANTY OF NON-INFRINGEMENT OR INTERFERENCE
AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE
- IBM will not be liable to you or indemnify you for any claims
related to the Excluded Components
- IBM will not be liable for any direct, indirect, incidental,
special, exemplary, punitive or consequential damages with respect
to the Excluded Components.

Prerequisites

The prerequisite level for this fix is as follows:
- IBM Tivoli Monitoring, Version 6.2.2: Fix Pack 02 or higher
(6.2.2-TIV-ITM-FP0002)
- IBM Tivoli Monitoring 6.2.3.2 Log File Agent Multiplatform
Multilingual (CI8WDEN) available from PassPort Advantage.

As this fix is cumulative, it can be installed on any fix level for
this version, release, and mod level above the prerequisite.

URL LANGUAGE SIZE(Bytes)
6.2.2-TIV-ITM-FP0002 English 999999

Installation Instructions

Please refer to the full README contained in the Download Description section above for general installation instructions.

Download package


Download RELEASE DATE LANGUAGE SIZE(Bytes) Download Options
What is Fix Central (FC)?
6.2.3.2-TIV-ITM_LFA-IF0004 17 Apr 2013 English 73338880 FC

Product Alias/Synonym

LFA
KLO
kloagent

Problems (APARS) fixed
IV39967, IV37051, IV36725, IV36678, IV33055, IV31931, IV26222, IV25203, IV24412, IV22257

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Monitoring Version 6
Tivoli Log File Agent

Software version:

6.2.3.2

Operating system(s):

AIX, HP-UX, Linux, Linux zSeries, Solaris, Windows

Reference #:

4034825

Modified date:

2013-04-19

Translate my page

Machine Translation

Content navigation