Download
Abstract
This fix resolves the APARs and defects listed in the “Problems Fixed” section below.
Download Description
Copyright International Business Machines Corporation 2019. All rights reserved.
Component: IBM(R) Tivoli(R) Monitoring: Windows(R) OS Agent, Version 6.3.0 Fix Pack 5
Component ID: 5724C040W
Interim Fix 0003 (6.3.0.5-TIV-ITM_WIN-IF0003)
Date: June 7, 2019
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
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.4.
2.0 Problems fixed
==================
The following problems are addressed by this fix.
2.1 APARs
---------
APAR: IJ07025
Abstract: Windows OS agent crashes when collecting Process attribute group data.
Additional Information: The Monitoring Agent for Windows OS crashes when a
situation is running which collects data from the Process or Processor
Summary attribute groups and that situation is stopped in the middle of a
data collection.
---------
APAR: IJ07025
Abstract: Windows OS agent crashes when collecting Process attribute group data.
Additional Information: The Monitoring Agent for Windows OS crashes when a
situation is running which collects data from the Process or Processor
Summary attribute groups and that situation is stopped in the middle of a
data collection.
With tracing set to (UNIT:knt ALL) in the <hostname>_nt_kntcma_<nnnnnn>-<n>.log
file, the last line from the data collection thread will be a message indicating
the setSampledProcessValues routine is being called:
file, the last line from the data collection thread will be a message indicating
the setSampledProcessValues routine is being called:
(2018/04/13,17:09:32.1CDD-DA4:knt75agt.cpp,234,"TakeSample")
Calling setSampledProcessValues with pid 1864
APAR: IV82178
Abstract: Binary Path not evaluated when Windows OS Agent running as non-administrator
Additional Information: The Monitoring Agent for Windows OS does not show
the Binary Path in Processes Attribute Group when running as non-administrator.
In order for this APAR to be properly implemented in your environment, a new environment
variable has been added.
Calling setSampledProcessValues with pid 1864
APAR: IV82178
Abstract: Binary Path not evaluated when Windows OS Agent running as non-administrator
Additional Information: The Monitoring Agent for Windows OS does not show
the Binary Path in Processes Attribute Group when running as non-administrator.
In order for this APAR to be properly implemented in your environment, a new environment
variable has been added.
The APAR introduces the environment variable KNT_USE_DEBUG_PRIVILEGE to enable the Debug
Privileges allowing a non-administrator user to query a process for the binary path.
Possible values are 0 or 1, the default value is 0 (disabled).
Privileges allowing a non-administrator user to query a process for the binary path.
Possible values are 0 or 1, the default value is 0 (disabled).
In adding to the use of this variable it is necessary enable the
SeDebugPrivilege for the user:
1) Open the Local Security Policy panel (running secpol.msc)
2) Expand "Local Policies" and click on "User Right Assignment".
3) In the right panel, look for an entry called "Debug Programs"
4) Double click and then Add the account you use to start the agent to
the list of already granted users/groups.
5) Click "OK" to confirm
SeDebugPrivilege for the user:
1) Open the Local Security Policy panel (running secpol.msc)
2) Expand "Local Policies" and click on "User Right Assignment".
3) In the right panel, look for an entry called "Debug Programs"
4) Double click and then Add the account you use to start the agent to
the list of already granted users/groups.
5) Click "OK" to confirm
2.2 Defects
-----------
None.
2.3 Enhancements
----------------
None.
----------------
None.
2.4 Superseded fixes
--------------------
6.3.0.5-TIV-ITM_WIN-IF0002
--------------------------
APAR: IV93473
Abstract: The Monitoring Agent for Window OS randomly crashes for the
NT Process, NT Physical Disk, and NT Network Port attribute groups.
Additional Information: The Window OS agent randomly crash while collecting
Perfmon percentage information for privtime, proctime, and usertime.
--------------------
6.3.0.5-TIV-ITM_WIN-IF0002
--------------------------
APAR: IV93473
Abstract: The Monitoring Agent for Window OS randomly crashes for the
NT Process, NT Physical Disk, and NT Network Port attribute groups.
Additional Information: The Window OS agent randomly crash while collecting
Perfmon percentage information for privtime, proctime, and usertime.
6.3.0.5-TIV-ITM_WIN-IF0001
--------------------------
APAR: IV77559
Abstract: Events from situations on custom scripts do not close automatically.
Additional Information: The data gathered executing the custom scripts in 6.30 FP5
are reported using the KXX_Custom_Scripts_Runtime attribute groups. These groups
implement 'pure event' tables. Because of this, situations cannot receive 'clearing'
events and need to be manually closed.
APAR: IV72203
Abstract: Cannot collect historical data for the Computer Domain Name attribute.
Additional Information: No historical data is collected for the Computer Domain Name
attribute in the Computer Information attribute group of the Monitoring Agent for
Windows OS, if the historical data collection takes place on the Tivoli Enterprise
Management Server side. Both real time data and historical data collected on the
Tivoli Enterprise Management Agent side work fine.
APAR: IV73966
Abstract: Lack of a field in Logical Disk attribute group showing the drive type
Additional Information: The Monitoring Agent for Windows OS do not have an attribute
showing the the drive type in the Logical Disk attribute group.
2.5 APARS and defects included from superseded fixes
----------------------------------------------------
None.
--------------------------
APAR: IV77559
Abstract: Events from situations on custom scripts do not close automatically.
Additional Information: The data gathered executing the custom scripts in 6.30 FP5
are reported using the KXX_Custom_Scripts_Runtime attribute groups. These groups
implement 'pure event' tables. Because of this, situations cannot receive 'clearing'
events and need to be manually closed.
APAR: IV72203
Abstract: Cannot collect historical data for the Computer Domain Name attribute.
Additional Information: No historical data is collected for the Computer Domain Name
attribute in the Computer Information attribute group of the Monitoring Agent for
Windows OS, if the historical data collection takes place on the Tivoli Enterprise
Management Server side. Both real time data and historical data collected on the
Tivoli Enterprise Management Agent side work fine.
APAR: IV73966
Abstract: Lack of a field in Logical Disk attribute group showing the drive type
Additional Information: The Monitoring Agent for Windows OS do not have an attribute
showing the the drive type in the Logical Disk attribute group.
2.5 APARS and defects included from superseded fixes
----------------------------------------------------
None.
3.0 Architecture and prerequisites
==================================
This fix is supported on all operating systems listed in the
IBM Tivoli Monitoring: Windows OS Agent User's Guide, version 6.3.0, Fix Pack 5.
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
for the latest operating system certification information:
http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html
3.1 Prerequisites for this fix
------------------------------
- IBM Tivoli Monitoring, Version 6.3.0 Fix Pack 5.
4.0 Image directory contents
============================
This fix image contains the following files:
- 6.3.0.5-TIV-ITM_WIN-IF0003.README - This README file
- 6.3.0.5-TIV-ITM_WIN-IF0003.tar - Fix archive .tar format
- 6.3.0.5-TIV-ITM_WIN-IF0003.zip - Fix archive .zip format
- 6.3.0.5-TIV-ITM_WIN-IF0003.tar - Fix archive .tar format
- 6.3.0.5-TIV-ITM_WIN-IF0003.zip - Fix archive .zip format
NOTE: The .tar and .zip files are identical in content.
Use the .tar file if you are working in a UNIX(R) environment;
use the .zip file if you are working in a Microsoft Windows(R) environment.
Use the .tar file if you are working in a UNIX(R) environment;
use the .zip file if you are working in a Microsoft Windows(R) environment.
The fix archive file contains the following:
6.3.0.5-TIV-ITM_WIN-IF0003/knt_winnt_tema_IF0003.cab
6.3.0.5-TIV-ITM_WIN-IF0003/knt_wix64_tema_IF0003.cab
6.3.0.5-TIV-ITM_WIN-IF0003/KNTWINNT.dsc
6.3.0.5-TIV-ITM_WIN-IF0003/KNTWIX64.dsc
6.3.0.5-TIV-ITM_WIN-IF0003/knt_winnt_tema_IF0003.cab
6.3.0.5-TIV-ITM_WIN-IF0003/knt_wix64_tema_IF0003.cab
6.3.0.5-TIV-ITM_WIN-IF0003/KNTWINNT.dsc
6.3.0.5-TIV-ITM_WIN-IF0003/KNTWIX64.dsc
and it can contains the following files if the patch updates the supports:
6.3.0.5-TIV-ITM_WIN-IF0003/knt_tems_teps_tepd_IF0003.tar
6.3.0.5-TIV-ITM_WIN-IF0003/knt_tems_teps_tepd_IF0003.zip
6.3.0.5-TIV-ITM_WIN-IF0003/knt_tems_teps_tepd_IF0003.tar
6.3.0.5-TIV-ITM_WIN-IF0003/knt_tems_teps_tepd_IF0003.zip
Each tar or cab file has updates to the IBM Tivoli Enterprise Monitoring
Server component for a specific platform. The platform that each file
applies to is included in its name.
Server component for a specific platform. The platform that each file
applies to is included in its name.
5.0 Installation instructions
=============================
This fix can only be installed over an existing installation. Use
the following steps to install this fix.
=============================
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.
-----------------------------
- 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.
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.
variable CANDLEHOME to the IBM Tivoli Monitoring installation
directory.
For example:
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Since there is no uninstall utility for this fix, we suggest you
perform a backup of your environment before installing this fix.
> CANDLEHOME=/opt/IBM/ITM
> export CANDLEHOME
- Since there is no uninstall utility for this fix, we suggest you
perform a backup of your environment before installing this fix.
5.2 Local agent update
----------------------
1. Transfer the appropriate archive file
(e.g. 6.3.0.5-TIV-ITM_WIN-IF0003.tar) to a temporary directory
on the system that contains the agent code to be updated.
For the purpose of this README, the symbol <TEMP> represents
the fully qualified path to this directory.
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.
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 that agent platform.
For more information on the itmpatch command, see section 6.2
For more information on the itmpatch command, see section 6.2
For example:
On a Windows system, if the fix was expanded to
<TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003, the install command would be,
depending if you are installing a 32 bit agent or a 64 bit agent:
On a Windows system, if the fix was expanded to
<TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003, the install command would be,
depending if you are installing a 32 bit agent or a 64 bit agent:
> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003\knt_winnt_tema_IF0003.cab
or
-i <TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003\knt_winnt_tema_IF0003.cab
or
> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003\knt_wix64_tema_IF0003.cab
-i <TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003\knt_wix64_tema_IF0003.cab
Note: if the itmpatch command gets this error:
"The application has failed to start because its side-by-side configuration
is incorrect. Please see the application event log for more detail."
it's necessary install the "visualstudio redistribution package" before to run
run the itmpatch command.
For a 32bit architecture, the name of this package is vcredist_x86.exe,
available at http://www.microsoft.com/en-us/download/details.aspx?id=5582
For a 64bit architecture, the name of this package is vcredist_x64.exe,
available at http://www.microsoft.com/en-us/download/details.aspx?id=2092
"The application has failed to start because its side-by-side configuration
is incorrect. Please see the application event log for more detail."
it's necessary install the "visualstudio redistribution package" before to run
run the itmpatch command.
For a 32bit architecture, the name of this package is vcredist_x86.exe,
available at http://www.microsoft.com/en-us/download/details.aspx?id=5582
For a 64bit architecture, the name of this package is vcredist_x64.exe,
available at http://www.microsoft.com/en-us/download/details.aspx?id=2092
5.3 Remote agent update
------------------------
1. Transfer the appropriate archive file
(e.g. 6.3.0.5-TIV-ITM_WIN-IF0003.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, this 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.
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 Command Reference Guide.
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 Command Reference Guide.
For example:
On UNIX systems,
if the fix was expanded to <TEMP>/6.3.0.5-TIV-ITM_WIN-IF0003
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.0.5-TIV-ITM_WIN-IF0003
On UNIX systems,
if the fix was expanded to <TEMP>/6.3.0.5-TIV-ITM_WIN-IF0003
> $CANDLEHOME/bin/tacmd addBundles -n -i <TEMP>/6.3.0.5-TIV-ITM_WIN-IF0003
On a Windows system,
if the fix was expanded to <TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003
> %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003
if the fix was expanded to <TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003
> %CANDLEHOME%\bin\tacmd addBundles -n -i <TEMP>\6.3.0.5-TIV-ITM_WIN-IF0003
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.
-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 updateAgent commands, see the IBM Tivoli Command Reference Guide.
the fix to the appropriate nodes where the agent is running, use
the following "tacmd" commands. For more information on the tacmd
login and updateAgent commands, see the IBM Tivoli Command Reference Guide.
For example:
On UNIX systems:
> $CANDLEHOME/bin/tacmd login -s <server>
-u <itmuser>
-p <password>
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.
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.
> $CANDLEHOME/bin/tacmd updateAgent -t NT
-n <Managed System Name>
-v 063005003
-n <Managed System Name>
-v 063005003
On a Windows system:
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
> %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.
remote system to be updated. Use this value as the target of the
tacmd updateAgent command.
> %CANDLE_HOME%\bin\tacmd updateAgent -t NT
-n <Managed System Name>
-v 063005003
-n <Managed System Name>
-v 063005003
Note:
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (NT), not three characters (KNT).
- 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.
- The component (-t) for the "tacmd updateAgent" command is
specified as two characters (NT), not three characters (KNT).
- 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
------------------------
The fix 6.3.0.5-TIV-ITM_WIN-IF0001 includes changes to the agent
support files which need to be installed. If you have already
installed these updates, there are no additional installation
steps. Otherwise, use one of the two following alternative methods
to update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise
Portal Server, and Tivoli Enterprise Portal Desktop.
A. Installing with the Application Support Installer (ASI)
------------------------
The fix 6.3.0.5-TIV-ITM_WIN-IF0001 includes changes to the agent
support files which need to be installed. If you have already
installed these updates, there are no additional installation
steps. Otherwise, use one of the two following alternative methods
to update the Tivoli Enterprise Monitoring Server, Tivoli Enterprise
Portal Server, and Tivoli Enterprise Portal Desktop.
A. Installing with the Application Support Installer (ASI)
1. Transfer the appropriate archive file
(6.3.0.5-TIV-ITM_WIN-IF0003.tar or 6.3.0.5-TIV-ITM_WIN-IF0003.zip)
to the IBM Tivoli Enterprise Monitoring Servers and IBM Tivoli
Enterprise Portal Servers.
2. Expand the archive file using the tar command on UNIX systems or
an unzip utility on Windows systems. This creates a directory
structure that contains fixes for all of the supported platforms.
3. Expand the archive file (knt_tems_teps_tepd_if0003.tar or.zip)
that contains the updates for Tivoli Enterprise Monitoring Server,
and Tivoli Enterprise Portal Server, using the tar command on
UNIX systems or an unzip utility on Windows systems. This creates
a directory structure that includes a subdirectory called CD-ROM,
with the necessary updates.
For example:
On a Windows system:
unzip
c:\temp\6.3.0.5-TIV-ITM_WIN-IF0003\knt_tems_teps_tepd_if0003.zip
On a UNIX System:
tar -xvf
/tmp/6.3.0.5-TIV-ITM_WIN-IF0003/knt_tems_teps_tepd_if0003.tar
4. Start the Application Support Installer GUI to install the fix.
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.
On UNIX/Linux systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]
On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]
where <JAVAHOME> is the fully-qualified path (do not include
bin directory in JAVAHOME path) to the directory where Java(R)
is installed. The location of Java on your system might vary.
When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not the
component directory. The installer can install updates for
multiple components at the same time.
(6.3.0.5-TIV-ITM_WIN-IF0003.tar or 6.3.0.5-TIV-ITM_WIN-IF0003.zip)
to the IBM Tivoli Enterprise Monitoring Servers and IBM Tivoli
Enterprise Portal Servers.
2. Expand the archive file using the tar command on UNIX systems or
an unzip utility on Windows systems. This creates a directory
structure that contains fixes for all of the supported platforms.
3. Expand the archive file (knt_tems_teps_tepd_if0003.tar or.zip)
that contains the updates for Tivoli Enterprise Monitoring Server,
and Tivoli Enterprise Portal Server, using the tar command on
UNIX systems or an unzip utility on Windows systems. This creates
a directory structure that includes a subdirectory called CD-ROM,
with the necessary updates.
For example:
On a Windows system:
unzip
c:\temp\6.3.0.5-TIV-ITM_WIN-IF0003\knt_tems_teps_tepd_if0003.zip
On a UNIX System:
tar -xvf
/tmp/6.3.0.5-TIV-ITM_WIN-IF0003/knt_tems_teps_tepd_if0003.tar
4. Start the Application Support Installer GUI to install the fix.
The GUI can be started by using one of the following commands
from within the CD-ROM directory where setup.jar is located.
On UNIX/Linux systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]
On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]
where <JAVAHOME> is the fully-qualified path (do not include
bin directory in JAVAHOME path) to the directory where Java(R)
is installed. The location of Java on your system might vary.
When prompted by the Application Support Installer for the
installable media directory, select the CD-ROM directory, not the
component directory. The installer can install updates for
multiple components at the same time.
5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you would
like to add application support to. For this fix, the check boxes
should be as follows:
checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)
Continue through the remaining GUI panels selecting the
Windows 06.30.05.03 support to complete the installation.
6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise
Portal Browser was running when the update was installed,
it must be restarted.
for the selection of which Tivoli Monitoring components you would
like to add application support to. For this fix, the check boxes
should be as follows:
checked - Tivoli Enterprise Monitoring Server (TEMS)
checked - Tivoli Enterprise Portal Server (TEPS)
checked - Tivoli Enterprise Desktop Client (TEPD)
Continue through the remaining GUI panels selecting the
Windows 06.30.05.03 support to complete the installation.
6. If the Tivoli Enterprise Portal Desktop or Tivoli Enterprise
Portal Browser was running when the update was installed,
it must be restarted.
7. Note that the version reported by cinfo command for the TEP Browser
(TEPB/tpw) App Support component will not be updated by the itmasi tool.
(TEPB/tpw) App Support component will not be updated by the itmasi tool.
B. Exploiting the Self Describing Agent (SDA)
1. In order to exploit this method SDA needs to be enabled on the agent,
on the R-TEMS and on the HUB-TEMS. SDA is enabled by default on all
components, but the HUB-TEMS. In order to enable it on the HUB-TEMS, if
not already enabled, set KMS_SDA=Y in its environment and restart it.
This is the only possible server restart required by this method, as
opposed to the multiple restarts of each server required during the
ASI install.
2. Double check SDA status is ON through command
> tacmd listsdastatus
Hub/RTEMS State Status
<HUB_name> ON 0
<RTEMS_name> ON 0
1. In order to exploit this method SDA needs to be enabled on the agent,
on the R-TEMS and on the HUB-TEMS. SDA is enabled by default on all
components, but the HUB-TEMS. In order to enable it on the HUB-TEMS, if
not already enabled, set KMS_SDA=Y in its environment and restart it.
This is the only possible server restart required by this method, as
opposed to the multiple restarts of each server required during the
ASI install.
2. Double check SDA status is ON through command
> tacmd listsdastatus
Hub/RTEMS State Status
<HUB_name> ON 0
<RTEMS_name> ON 0
3. Enable SDA for this Interim Fix through command
> tacmd addsdainstalloptions -t nt -v 06300503
KUICO2054I: No configuration options were found for the specified
type(s). The following options will be created:
PRODUCT VERSION
NT 06300503
Are you sure you want to update the selected options? Type Y for yes.
Type N for no.
Y
KUIAIO150I: The selected SDA configuration options records were
successfully updated.
4. Double check required SDA install options are in place
> tacmd listsdainstalloptions
NT 06300503
Are you sure you want to update the selected options? Type Y for yes.
Type N for no.
Y
KUIAIO150I: The selected SDA configuration options records were
successfully updated.
4. Double check required SDA install options are in place
> tacmd listsdainstalloptions
KUILIO200W: No default SDA installation settings exist.
PRODUCT VERSION
NT 06300503
5. You need at least one 32 bit agent upgraded to this Interim Fix level running
in this HUB environment. In a few moments from its startup all the needed
support files will be propagated from the agent to the servers.
6. Double check the seeding of the support files has successfully completed
(STATE=IC Installation Complete)
> tamcd listappinstallrecs
HUB/RTEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS
<HUB_name> NT 06300503 5655 TMS 06300503 Y IC 0
<RTEMS_name> NT 06300503 5655 TMS 06300503 Y IC 0
PRODUCT VERSION
NT 06300503
5. You need at least one 32 bit agent upgraded to this Interim Fix level running
in this HUB environment. In a few moments from its startup all the needed
support files will be propagated from the agent to the servers.
6. Double check the seeding of the support files has successfully completed
(STATE=IC Installation Complete)
> tamcd listappinstallrecs
HUB/RTEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS
<HUB_name> NT 06300503 5655 TMS 06300503 Y IC 0
<RTEMS_name> NT 06300503 5655 TMS 06300503 Y IC 0
7. Note that the version reported by cinfo command for the TEP Desktop
(TEPD/tpd) App Support component will not be updated by the SDA method.
6.0 Additional installation information
=======================================
For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>.
(TEPD/tpd) App Support component will not be updated by the SDA method.
6.0 Additional installation information
=======================================
For additional troubleshooting installation information, see the
itmpatch.log in the patchlogs directory in <CANDLEHOME>.
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.
--------------------------------------------------
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:
-----------------------------------------------------
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> }
-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
-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:
<CANDLEHOME> points to the IBM Tivoli Monitoring installation directory
<TEMP> points to the temporary directory where the fix is located.
<CANDLEHOME> points to the IBM Tivoli Monitoring installation directory
<TEMP> points to the temporary directory where the fix is located.
- To preview the fix installation, use the "-t" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -t <TEMP>
- To install the fix, use the "-i" option:
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>
> <CANDLEHOME>/bin/itmpatch -h <CANDLEHOME> -i <TEMP>
where:
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows, this must include the drive
letter.
<TEMP> represents the fully qualified directory specification, where
the fix is located. On Windows, this must include the drive letter.
<CANDLEHOME> is the fully qualified IBM Tivoli Monitoring
installation directory. On Windows, this must include the drive
letter.
<TEMP> represents the fully qualified directory specification, where
the fix is located. On Windows, 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 login to a Tivoli Enterprise Monitoring
Server prior to viewing the agent version.
-------------------------
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 login 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'.
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 NT
-u <itmuser>
-p <password>
> $CANDLEHOME/bin/tacmd listSystems -t NT
On a Windows system, where %CANDLE_HOME% is the IBM Tivoli
Monitoring installation directory. The default location
is 'C:\IBM\ITM'.
Monitoring installation directory. The default location
is 'C:\IBM\ITM'.
> %CANDLE_HOME%\bin\tacmd login -s <server>
-u <itmuser>
-p <password>
-u <itmuser>
-p <password>
> %CANDLE_HOME%\bin\tacmd listSystems -t NT
When the agent update is successful, the agent version should now be:
06.30.05.03
06.30.05.03
Note:
- The component (-t) for the tacmd listSystems command is specified
as two characters NT, not three characters KNT.
- The component (-t) for the tacmd listSystems command is specified
as two characters NT, not three characters KNT.
You can also use the GUI (Manage Tivoli Enterprise Monitoring Services) to
verify the agent is successfully updated.
For the agent on a Windows system, the version number is 06.30.05.03.
verify the agent is successfully updated.
For the agent on a Windows system, the version number is 06.30.05.03.
7.0 Known problems and workarounds
==================================
1. It can happen that installation of this Interim Fix fails while
adding the agent supports for TEMS and TEPS using Java 1.7,
giving a Java exception.
When this issue occurs, please choose another version for Java (JRE)
installed on the machine for running the setup.jar file.
Java version 1.5 or 1.6 are suggested
2. The SDA methodology for updating agent support files only works with
32 bit agents. You need at least one 32 bit agent running in your
environment in order to exploit SDA.
==================================
1. It can happen that installation of this Interim Fix fails while
adding the agent supports for TEMS and TEPS using Java 1.7,
giving a Java exception.
When this issue occurs, please choose another version for Java (JRE)
installed on the machine for running the setup.jar file.
Java version 1.5 or 1.6 are suggested
2. The SDA methodology for updating agent support files only works with
32 bit agents. You need at least one 32 bit agent running in your
environment in order to exploit SDA.
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.
=======
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.
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.
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.
Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks or
registered trademarks of Oracle and/or its affiliates.
registered trademarks of Oracle and/or its affiliates.
UNIX is a registered trademark of The Open Group in the United States
and other countries.
and other countries.
Linux is a registered trademark of Linus Torvalds in the United States,
other countries, or both.
other countries, or both.
Other company, product, or service names may be trademarks or service
marks of others.
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.
-----------------------------------------------------------------
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:
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.
- 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
IBM Tivoli Monitoring: Windows(R) OS Agent 6.3.0.5
Installation Instructions
Please refer to the 6.3.0.5-TIV-ITM_WIN-IF0003.README contained in the Description section above for general installation instructions.
Download Package
To download the files using Fix Central use the following link:
On
[{"DNLabel":"6.3.0.5-TIV-ITM_WIN-IF0003","DNDate":"07 Jun 2019","DNLang":"English","DNSize":"42,871,717","DNPlat":{"label":"Windows","code":"PF033"},"DNURL":"http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~Tivoli&product=ibm/Tivoli/IBM+Tivoli+Monitoring&platform=All&release=6.3.0.5&function=fixId&fixids=6.3.0.5-TIV-ITM_WIN-IF0003","DNURL_FTP":"","DDURL":null}]
[{"Product":{"code":"SSTFXA","label":"Tivoli Monitoring"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"ITM Agent Windows V6","Platform":[{"code":"PF033","label":"Windows"}],"Version":"6.3.0.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Problems (APARS) fixed
Problems (APARS) fixed
Was this topic helpful?
Document Information
Modified date:
07 June 2019
UID
ibm10886955