IBM Tivoli Monitoring: Agentless OS Monitoring 6.2.1-TIV-ITM_AL-IF0007

Download Description

Copyright International Business Machines Corporation 2010.
All rights reserved.

Component: IBM(R) Tivoli(R) Agentless Monitoring, Version 6.2.1

Component ID: 5724C04RA,5724C04RH,5724CO4RL,5724C04RS,5724C04RW

Interim Fix 0007, 6.2.1-TIV-ITM_ALWIN-IF0007 (KR2)
6.2.1-TIV-ITM_ALAIX-IF0007 (KR3)
6.2.1-TIV-ITM_ALLNX-IF0007 (KR4)
6.2.1-TIV-ITM_ALHP-IF0007 (KR5)
6.2.1-TIV-ITM_ALSOL-IF0007 (KR6)

Date: October 22, 2010

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 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.

The fix is available for each of the Agentless Monitoring agents:
Agentless Monitoring for Windows Operating Systems (ALWIN)
Agentless Monitoring for AIX Operating Systems (ALAIX)
Agentless Monitoring for Linux Operating Systems (ALLNX)
Agentless Monitoring for HP-UX Operating Systems (ALHP)
Agentless Monitoring for Solaris Operating Systems (ALSOL).


2.0 Problems fixed
============
The following problems are addressed by each agentless monitoring fix.

2.1 APARs
-------------
APAR: IZ64799
Abstract: Agent uses large amount of memory due to number of domain user
accounts
Additional information: When retrieving user accounts from Windows
Management Instrumentation (WMI), domain user accounts as well
as local user accounts were being returned. If an environment
has a large number of domain user accounts, the amount of memory
used by the agent can be large. Only local user accounts are
retrieved now.

Refer to section 8.6 for more information about using this fix
to monitor a Windows Domain controller running Windows 2003.

APAR: IZ77565
Abstract: Perfmon data stops collecting when other systems are down
Additional information: In the Monitoring Agent for Agentless Windows OS,
Windows Performance Monitor (Perfmon) data stops being collected
when other systems are not available. When one or more remote
hosts is not available, the calls to Perfmon for other remote
hosts which are available fail with a timeout error. This is
due to a lock in Microsoft's implementation which times out
after 15 seconds, causing all outstanding requests to fail
simultaneously with error 0x102 (WAIT_TIMEOUT). This problem
only occurs for the Monitoring Agent for Agentless Windows OS when
it is configured to use the Windows API Connection.

APAR: IZ77637
Abstract: Agentless agent for Windows (WMI) does not recover when a target
machines is rebooting
Additional information: When the Agentless Monitoring for Windows is
monitoring a remote server that is not available, the agent stops
collecting data from the remote server. When the remote server
reboots, the agent does not always recover. There are also Windows
Management Instrumentation (WMI) out of memory errors in the log file
<hostname>_r2_<instance>_kr<n>agent_xxx.log, for example:
(4B816AE2.00D6-950:wmiqueryclass.cpp,908,"internalCollectData")
WMI Error:0x80041006, WBEM_E_OUT_OF_MEMORY Win32_Processor. No
results this instance. subnode = xxx

APAR: IZ81461
Abstract: Solaris SMC NFS mount point is not defined as display item
Additional information: If a situation is triggered for a Solaris
Sun Management Center (SMC) NFS attribute, the clearing event
may not be processed properly by the event receiver (for
example, Omnibus) since there is no existing atomized variable
to distinguish between NFS mount points.

The clearing event for the situation is received, but
since there is no existing atomized variable, the original
event does not get closed out by receipt of the clearing
event.

See section 8.5 for more details about using the new
atomized value.

APAR: IZ83043
Abstract: Solaris Agentless agent crashes when freeing memory
Additional information: The following messages are written to
the log file <hostname>_r6_<unique>.log. The crash occurs in the
call to free memory from the handle_snmp_response_async routine.

======= Backtrace: =========
/lib64/libc.so.6[0x33092722ef]
/lib64/libc.so.6(cfree+0x4b)[0x330927273b]
/opt/IBM/ITM/lx8266/r6/bin/kr6agent(handle_snmp_response_async+0
xd27)[047feeb]
/opt/IBM/ITM/lx8266/r6/bin/kr6agent(snmpCallResponseHandler+0xeb
)[0x4f471]
/opt/IBM/ITM/lx8266/r6/bin/kr6agent(snmpReceive+0x1826)[0x4f41c4]
/lib64/libpthread.so.0[0x3309e064a7]
/lib64/libc.so.6(clone+0x6d)[0x33092d3c2d]

APAR: IZ86035
Abstract: SNMP timeout messages in log when data returned quickly
Additional information: When the agent sends a request to the subnode
to collect SNMP data and the response is received too
quickly, it results in timeout messages in the log file.

This is a timing issue which can occur on any of the five
Agentless Monitors.

APAR: IZ86133
Abstract: No data displayed when configured with SNMP V3
Additional information: When running the Agentless Monitor to run
with SNMP V3, no data is displayed in the Tivoli Enterprise
Portal. This problem can occur on any of the Agentless Monitors
configured with SNMP V3. There are multiple SNMPAPI error
messages in the log file
<hostname>_r<n>_<instance>_kr<n>agent_xxx.log, for example:
(4C90CD77.0000-A:snmpplfm.c,329,"plfmSnmpLogMessage")
SNMPAPI: Error encoding message: RC = -77
(4C90CD77.0000-A:snmpplfm.c,329,"plfmSnmpLogMessage"
SNMPAPI: Could not free newPdu: RC is -69

APAR: IZ86544
Abstract: Flood of failed login messages when monitoring Windows system
Additional information: When running the Agentless Monitor for Windows using
the "Windows API Connection" connection type, the Windows event log
shows the following error message multiple times every minute:

"Logon failure: Reason: Unknown user name or bad password".

The logon actually succeeds and data is retrieved correctly,
however the event log is flooded with these events.

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

2.3 Enhancements
----------------------
None.

2.4 Superseded fixes
-------------------------
6.2.1-TIV-ITM_AL-IF0006 (Windows only)
6.2.1-TIV-ITM_AL-IF0005
6.2.1-TIV-ITM_AL-IF0004 (Windows only)
6.2.1-TIV-ITM_AL-IF0003
6.2.1-TIV-ITM_AL-IF0002 (Solaris only)
6.2.1-TIV-ITM_AL-IF0001

2.5 APARs and defects included from superseded fixes
---------------------------------------------------------------
6.2.1-TIV-ITM_AL-IF0006
------------------------
APAR: IZ57949
Abstract: INCORRECT MESSAGE TEXT FOR SECURITY LOG MESSAGES FROM A
WINDOWS 2008 SYSTEM.
Additional Information: When the Agentless Monitoring for Windows (R2)
agent is running on a Microsoft(R) Windows(R) 2003 system
and is monitoring a remote Windows 2008 system, the message
text in the WMI Event Log workspace does not match the
message text in the Windows 2008 event log for security
messages.

Technote 1399135 contains more information about two
Microsoft Windows hotfixes available to address
additional conditions where event log messages are not
formatted correctly for Windows 2008 systems.

APAR: IZ60507
Abstract: AGENTLESS AGENT FOR WINDOWS (WMI) DOESN'T RECOVER WHEN
THE TARGET MACHINE IS RESTARTED.
Additional Information: If the WMI service is stopped on the target
server, the Agentless Monitoring for Windows is not able
to collect data and several workspaces (such as System and
Memory) do not display data. When the WMI service is
restarted, the agent does not automatically recover and
the workspaces continue to not display data. The agent
must be restarted to collect data again.

6.2.1-TIV-ITM_AL-IF0005
------------------------
APAR: IZ53982
Abstract: CLEARING EVENT FOR NIC STATUS DOWN NOT PROCESSED CORRECTLY
Additional Information: If one of the default situations, NIC Status
Down or NIC Status Unknown is triggered, the clearing event
might not be processed properly by the event receiver
(e.g. Omnibus) when the endpoint is running with multiple
NICs which have identical NIC descriptions.

The clearing event for the situation is received, but
the existing atomized variable (Description) might not have
enough information to distinguish between NICs. Therefore,
the original event does not get closed out by receipt of
the clearing event.

See Section 8.4 "Update clearing event with multiple NICs"
for more information about updating the situations to
include a new atomized variable (Index).

6.2.1-TIV-ITM_AL-IF0004
(Agentless Monitoring for Windows Operating Systems only).
------------------------
APAR: IZ50817
Abstract: WINDOWS AGENTLESS MISSING SYSTEM NAME IN WAREHOUSE
Additional Information: The System Name attribute is missing
from the KR2 HRSYSTEM attribute group in the
warehouse database for the Agentless Monitoring
for Windows.

A new attribute Name has been added to the
KR2 HRSYSTEM attribute group. A new query,
hrSystem_V3, is also available which contains
the new attribute.

See Section 8.1 "Warehouse update with limited
user permissions" for more information about
this attribute being updated in the warehouse.


6.2.1-TIV-ITM_ALWIN-IF0003
--------------------------
APAR: IZ44836
Abstract: AGENTLESS MONITORING FOR SOLARIS - SNMP TIMEOUT FOR SMC
DUE TO INCORRECT SNMP_PORT IN CONFIGURATION
Additional Information: If configuration changes for a Solaris SMC
configuration are made, those changes are saved
to the configuration file
(<host>_<product code>_<instance>.cfg), however the original
configuration data is not removed causing duplicate data
for SMC and SMA. When the agent starts, it can result
in the incorrect parameters being used.

Note: See Section 6.4 "Solaris Reconfiguration" for
more information about reconfiguring Solaris agents
after this patch has been installed.

Feature: 96358
Abstract: Add ability to dynamically add and remove
subnodes to the agent using a new set of Take
Actions.

Additional Information: To use the new Take Actions, add new
application support to the Tivoli Enterprise Monitoring
Server and Tivoli Enterprise Portal Server after
installing this fix. See section 5.4, step 7 for more
information.

A new set of Take Actions has been added
to dynamically add and remove subnodes. See
section 8.3 "Dynamic add and remove of subnodes"
for more information.

Example of new take action command :
> tacmd executeaction -n AIXSnmpMonitorStart
-m "Instance1:hostname1:R3"
-c "value=AIX-host1,host1,public"

Where:
-n Take action command (i.e. AIXSnmpMonitorStart)

-m Managed Instance name(i.e."Instance1:hostname1:R3")
"tacmd listSystems" retrieves the Managed Instance
Name.

-c Target remote systems(i.e."value=AIX-host1,host1,public")
- The instance name seen in the Tivoli Enterprise Portal
(i.e. AIX-host1),
- The hostname to be monitored (i.e. host1),
- The community name. (i.e. public)
NOTE: This community name is optional.
(i.e. "value=AIX-host1,host1,")

6.2.1-TIV-ITM_AL-IF0002
(Agentless Monitoring for Solaris Operating Systems only)
------------------------
APAR: IZ43927
Abstract: SOLARIS AGENTLESS (SMC) REPORTS WRONG NFS FILESYSTEM
UTILIZATION
Additional Information: The following attributes for the SMC NFS
attribute group report incorrect values:
- % Available Disk Space
- Used Disk Space
- Available Disk Space (MB)
- Used Disk Space (MB).

6.2.1-TIV-ITM_ALWIN-IF0001
--------------------------
APAR: IZ42000
Abstract: SEND ERRORS MAY CAUSE SNMP AGENT TO CRASH
Additional Information: SNMP send errors cause unsafe data access
in SNMP data provided threads, causing the agent to crash
or core.

APAR: IZ42002
Abstract: ON WINDOWS 2008, AGENT GENERATES INVALID QUERY FOR
PERFMON CLASSES
Additional Information: Due to a problem found in Microsoft(R)
Windows(R) 2008, the agent generates an invalid query
and the attribute group is never initialized.

APAR: IZ42003
Abstract: TAKESAMPLE DOES NOT HANDLE REQUEST TO ALL SUBNODES
Additional Information: TakeSample does not handle requests to all
subnodes properly, which can result in the data for a
node name being reported against the wrong node name.

APAR: IZ41920
Abstract: 64-BIT DATA COLLECTED BY AGENTLESS AGENT IS CORRUPT IN
WAREHOUSE.
Additional Information: When history collection is started with
the collection location specified as "TEMA", the tables
created in the warehouse database define the 64-bit
data columns as 32-bit (INTEGER), instead of BIGINT
or Number(20). If data has already been uploaded to
the warehouse database for any of the tables listed
in Section 8.2, "History collection" below,
it can result in corrupt data.

To correct the problem, once the fix has been
installed, the tables will need to be dropped in the
warehouse database. The tables will be automatically
recreated correctly the next time data is uploaded to
the warehouse. The list of affected tables is specified
in Section 8.2, "History collection" below.

Note 1: If tables were created when the collection
location was specified as "TEMS", the tables are created
correctly and do not need to be dropped.

Note 2: Dropping the tables in the warehouse database
will cause all data in those tables to be lost.

APAR: IZ41936
Abstract: AGENT MEMORY LEAK
Additional Information: The memory leak can occur on any of the
platforms when a configured system does not exist.



3.0 Architecture and prerequisites
======================
The following link is for the Tivoli operating system and application support
matrix. Please refer to this matrix for the latest certification
information.

http://www.ibm.com/software/sysmgmt/products/support/Tivoli_Supported_Platforms.html

3.1 Prerequisites for this fix
--------------------------------
Each fix image has the following prerequisite:

Agentless Monitoring for Windows Operating Systems:
- IBM Tivoli Agentless Monitoring for Windows, version 6.2.1
Agentless Monitoring for AIX Operating Systems:
- IBM Tivoli Agentless Monitoring for AIX, version 6.2.1
Agentless Monitoring for Linux Operating Systems:
- IBM Tivoli Agentless Monitoring for Linux, version 6.2.1
Agentless Monitoring for HP-UX Operating Systems:
- IBM Tivoli Agentless Monitoring for HP-UX, version 6.2.1
Agentless Monitoring for Solaris Operating Systems:
- IBM Tivoli Agentless Monitoring for Solaris, version 6.2.1.

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

4.0 Image directory contents
===================
Each fix image contains the following files:
- 6.2.1-TIV-ITM_AL-IF0007.README - This README file
- 6.2.1-TIV-ITM_ALxxx-IF0007.tar - Fix archive .tar format
- 6.2.1-TIV-ITM_ALxxx-IF0007.zip - Fix archive .zip format.

where xxx corresponds to the agent:
WIN - Agentless Monitoring for Windows Operating Systems
AIX - Agentless Monitoring for AIX Operating Systems
LNX - Agentless Monitoring for Linux Operating Systems
HP - Agentless Monitoring for HP-UX Operating Systems
SOL - Agentless Monitoring for Solaris Operating Systems.

Note: The .tar and .zip files for each Agentless component
are identical in content. If you are working in a UNIX(R),
use the .tar file. If you are working in a Windows(R) environment,
you can use either the .tar or .zip file.

The fix archive file contains the following files:
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>aix523.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>aix526.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>hp11.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>hp116.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>hpi116.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>li6243.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>li6263.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>lia266.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>lpp266.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>ls3243.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>ls3246.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>lx8266.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>sol283.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>sol286.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>sol606.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>WINNT.dsc
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_aix523_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_aix526_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_hp116_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_hp11_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_hpi116_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_li6243_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_li6263_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_lia266_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_lpp266_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_ls3243_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_ls3246_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_lx8266_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_sol283_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_sol286_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_sol606_tema_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_winnt_tema_if0007.cab
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_tems_teps_tepd_if0007.tar
- 6.2.1-TIV-ITM_ALxxx-IF0007/kr<n>_tems_teps_tepd_if0007.zip
- 6.2.1-TIV-ITM_ALxxx-IF0007/r<n>_dd.properties
- 6.2.1-TIV-ITM_ALxxx-IF0007/r<n>_dd_062103007.xml

where ALxxx and r<n> correspond to the product code for the agent:
ALWIN, r2 - Agentless Monitoring for Windows Operating Systems
ALAIX, r3 - Agentless Monitoring for AIX Operating Systems
ALLNX, r4 - Agentless Monitoring for Linux Operating Systems
ALHP, r5 - Agentless Monitoring for HP-UX Operating Systems
ALSOL, r6 - Agentless Monitoring for Solaris Operating Systems.


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.


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

- Refer to section 7.0 entitled "Known problems and workarounds" before
installation.

- 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.1-TIV-ITM_ALxxx-IF0007.tar
or .zip) 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.
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.1-TIV-ITM_ALxxx-IF0007, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>/6.2.1-TIV-ITM_ALxxx-IF0007
/KR<n>_yyyyyy_tema_if0007.tar

where:
- ALxxx and KR<n> correspond to the product code for the agent:
ALWIN, KR2 - Agentless Monitoring for Windows Operating Systems
ALAIX, KR3 - Agentless Monitoring for AIX Operating Systems
ALLNX, KR4 - Agentless Monitoring for Linux Operating Systems
ALHP, KR5 - Agentless Monitoring for HP-UX Operating Systems
ALSOL, KR6 - Agentless Monitoring for Solaris Operating Systems

- yyyyyy corresponds to the value in the first column returned
by the "./cinfo -i" command.

In the following example, the file would be
kr2_li6243_tema_if0007.tar
> ./cinfo -i
Agentless Monitoring for Windows Operating Systems
li6243 Version: 06.21.00.07

On Windows systems, if the fix was expanded to
<TEMP>\6.2.1-TIV-ITM_ALWIN-IF0007, the install command is:

> itmpatch -h <CANDLEHOME>
-i <TEMP>\6.2.1-TIV-ITM_ALWIN-IF0007
\kr2_winnt_tema_if0007.cab

5.3 Remote agent update
----------------------------
1. Transfer the appropriate archive file (6.2.1-TIV-ITM_ALxxx-IF0007.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.1-TIV-ITM_ALWIN-IF0007:
> $CANDLEHOME/bin/tacmd addBundles -n
-i <TEMP>/6.2.1-TIV-ITM_ALWIN-IF0007
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.

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

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 <r2 | r3 | r4 | r5 | r6>
-n <Managed system name>
-v 062100007

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 <R2 | R3 | R4 | R5 | R6>
-n <Managed system name>
-v 062100007
Note:
- The component (-t) for the updateAgent command is specified as
two characters (r<n>), not three characters (kr<n>), which
corresponds to the appropriate agent:
r2 - Agentless Monitoring for Windows Operating Systems
r3 - Agentless Monitoring for AIX Operating Systems
r4 - Agentless Monitoring for Linux Operating Systems
r5 - Agentless Monitoring for HP-UX Operating Systems
r6 - Agentless Monitoring for Solaris Operating Systems.

- 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
------------------------------
Fix 6.2.1-TIV-ITM_ALSOL-IF0007 includes changes to the agent support files
which need to be installed. The agent support update is required for APAR
IZ81461 which applies only when monitoring Sun Management Center (SMC)
machines using Agentless Monitoring for Solaris Operating System (KR6).
Application support does not need to be installed for the other Agentless
Monitors (KR2, KR3, KR4, or KR5).

If you are not monitoring Solaris Sun Management Center (SMC)
machines, then fix 6.2.1-TIV-ITM_AL-IF0005 included changes to the agent
support files. If you have already installed these updates, there are
no additional installation steps.

Use the following steps to update the Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, or Tivoli Enterprise Portal Desktop.

1. Transfer the appropriate archive file (6.2.1-TIV-ITM_ALxxx-IF0007.tar
or .zip) to the IBM Tivoli Enterprise Monitoring Servers, IBM Tivoli
Enterprise Portal Servers or Tivoli Enterprise Portal Desktops.

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. Expand the archive file (kr<n>_tems_teps_tepd_if0007.tar or .zip)
that contains the updates for Tivoli Enterprise Monitoring Server,
Tivoli Enterprise Portal Server, and Tivoli Enterprise Portal
Desktop using the "tar" command on UNIX systems or an extract
utility on Windows systems. This step creates a directory
structure that includes a subdirectory called CD-ROM, with the
necessary updates.

As a convenience, two separate files are available which can
be used to add the agent support files for more than one of the
Agentless Monitoring agents at a time. The files are named:
kr2_kr3_kr5_kr4_kr6_tems_teps_tepd_if0007.tar
kr2_kr3_kr5_kr4_kr6_tems_teps_tepd_if0007.zip
To use one of these, use
kr2_kr3_kr5_kr4_kr6_tems_teps_tepd_if0005.tar or .zip as the archive
file name.

4. Use the Application Support Installer(ASI) GUI or the silent
installation method to install the application support files.

GUI installation option
------------------------
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 systems:
> ./itmasi.sh [-h <CANDLEHOME>] [-j <JAVAHOME>]

On Windows systems:
> itmasi [-h <CANDLEHOME>] [-j <JAVAHOME>]

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.

Silent installation option
--------------------------
To use the silent installation option, use one of the following
commands from within the CD-ROM directory where setup.jar is
located.

Note: Using the silent installation option for Linux(R) and zLinux
operating systems requires the following files contained in
Interim Fix 6.2-TIV-ITM_ASI-IF0001:
- Linux: setupLinux.bin
- zLinux: setupLinux390.bin
Follow the installation instructions contained in the
"6.2-TIV-ITM_ASI-IF0001.README".

On UNIX systems:
> ./itmasi.sh -h <CANDLEHOME>[-silent]
[-r <response file>]
[-j <JAVAHOME>]

On Windows systems:
> itmasi -h <CANDLEHOME> [-silent]
[-r <response file>]
[-j <JAVAHOME>]

where:
-h <CANDLEHOME> - Required. The path to the IBM Tivoli
Monitoring installation directory.

-r <response file> - Optional. Customized response file name.
The default response file "response.txt" in
the CD-ROM directory can be copied and modified
for your environment. Do not update "response.txt".

-j <JAVAHOME> - Optional. The fully-qualified path to the "bin"
directory where Java(R) is installed. The
location of Java on your system might vary.

5. The next panel presented by the Application Support Installer asks
for the selection of which Tivoli Monitoring components you want
to add application support to. For the fix 6.2.1-TIV-ITM_ALSOL-IF0007,
check or clear the check boxes 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 Monitoring
for Agentless 06.21.00.07 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. To add support for the new Take Actions, new application
support has to be added to the Tivoli Enterprise Monitoring Server.

For a Windows Tivoli Enterprise Monitoring Server, from the GUI
select 'Actions", then 'Advanced' and then 'Add TEMS application
support'. Choose the 'kr<n>_upg.sql' during the 'Application
Support' installation.

For a UNIX/Linux Tivoli Enterprise Monitoring Server, use
'itmcmd support' command to add application support.

> %CANDLE_HOME%\bin\itmcmd support [-h install_dir] [-s]
-t tems_name pc pc pc...

Where:
-h (optional) - Parameter to specify the installation directory
if it is not the one in which the script is located.
Usually not necessary.

install_dir - the installation directory of IBM Tivoli Monitoring

-s (optional) - Option to specify safe mode operation.
Safe mode invokes the JRE with the -nojit option
(no just-in-time compiler). If you encounter a Java™
failure error, try running the command as before, but
also specifying the -s option. This might solve some
Java exceptions that occur on a small number of
computers.

-t - Use this option to specify the TEMS name. It is a
required option.

tems_name - Specifies the name of the TEMS to add application
support to. This argument is required.

pc - The product code of the component that will connect
to the TEMS. You can specify one or more components
for which to add application support. If you specify
multiple components, separate the product codes with
either a space or a comma.

r2 - Agentless Monitoring for Windows Operating Systems
r3 - Agentless Monitoring for AIX Operating Systems
r4 - Agentless Monitoring for Linux Operating Systems
r5 - Agentless Monitoring for HP-UX Operating Systems
r6 - Agentless Monitoring for Solaris Operating Systems.

Refer to the "Adding application support to the hub monitoring server"
section in IBM Tivoli Monitoring Installation and Setup Guide.

6.0 Additional installation information
========================
6.1 Installation instructions for agent baroc file
-----------------------------------------------------
Fix 6.2.1-TIV-ITM_AL-IF0004 includes changes to the agent
baroc files. If you have already installed these baroc files,
there are no additional installation steps. If not, refer to
the IBM Tivoli Monitoring, Version 6.2.1, Installation and Setup
Guide under "Installing monitoring agent baroc files on the event
server" in "Installing the IBM Tivoli Enterprise Console Event
Synchronization" section for more information on installing the
updated baroc files.

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 r<n>

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 R<n>

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

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

2. To verify the agent support files were updated correctly, use the
"kincinfo" command on Windows systems or the "cinfo" command on Linux
or UNIX systems. The sample output below shows the versions of
the Tivoli Enterprise Portal Server, Tivoli Enterprise Monitoring
Server, or Tivoli Enterprise Portal Desktop systems after this
fix has been successfully applied.

Note:
- The displayed date of the build might not be accurate. This is
a known problem.

On UNIX or Linux systems:
-------------------------
To validate that all components have been installed, run the
following command:

./cinfo -i

*********** Monday, October 11, 2010 8:30:29 AM ***********
User: root Groups: root bin daemon sys adm disk wheel
Host name : mylinuxsys Installer Lvl:06.21.00.01
CandleHome: /opt/IBM/ITM
***********************************************************
...Product inventory
.
.
.
Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal
Server and Tivoli Enterprise Portal Desktop update:

r6 Agentless Monitoring for Solaris Operating Systems
tms Version: 06.21.00.07
r6 Agentless Monitoring for Solaris Operating Systems
tpd Version: 06.21.00.07
tps Version: 06.21.00.07
tpw Version: 06.21.00.00

Agentless Monitoring agent updates:
r6 Agentless Monitoring for Solaris Operating Systems
sol296 Version: 06.21.00.07


On Windows systems:
---------------------
To validate that all components have been installed, run the
following command:

For example:
> %CANDLE_HOME%\InstallITM\kincinfo -i

************* Monday, October 11, 2010 3:04:16 PM *******************
User : Administrator Group : NA
Host Name : mywinbox Installer: Ver: 062100000
CandleHome: C:\IBM\ITM
Installitm: C:\IBM\ITM\InstallITM
*********************************************************************
.
.
.
Tivoli Enterprise Monitoring Server, Tivoli Enterprise
Portal Server and Tivoli Enterprise Portal Desktop update:

R6 Agentless Monitoring for Solaris Operating Systems
WINNT Version: 06.21.00.07 Build: 2010100500000

R6 Agentless Monitoring for Solaris Operating Systems
WINNT Version: 06.21.00.07 Build: 2010100500000

R6 Agentless Monitoring for Solaris Operating Systems
WINNT Version: 06.21.03.07 Build: 0810222135

R6 Agentless Monitoring for Solaris Operating Systems
WINNT Version: 06.21.00.07 Build: 2010100500000

Agentless Monitoring agent updates:
R6 Agentless Monitoring for Solaris Operating Systems
WINNT Version: 06.21.00.07 Build: 0810222135

6.4 Solaris Reconfiguration
---------------------------
This patch does not require Solaris instances to be reconfigured.
However once this patch is installed, if a Solaris instance is
reconfigured, then all the Solaris instances must be configured,
otherwise the values written to the configuration file are reset
to the default values.

7.0 Known problems and workarounds
=========================
Abstract: No data is seen in the Tivoli Enterprise Portal if an
Agentless Monitoring agent instance is added with the
"tacmd addsystem" command after it was previously
removed.
Problem: If an Agentless Monitoring agent instance is removed and
then added with the "tacmd addsystem" command, the command
will report successful completion but no data will be seen
in the Tivoli Enterprise Portal for that instance. This is
due to the data in the configuration file being written
incorrectly.
Workaround: The problem is being addressed by IBM Tivoli Monitoring
APAR IZ44403.

Abstract: "Select a Monitoring Agent" does not show all the Agentless
Monitoring agents that are installed.
Problem: When the 'Add Managed System' is selected from the Tivoli
Enterprise Portal user interface, the dialog box named
"Select a Monitoring Agent" does not show all the Agentless
Monitoring agents that are installed.
Workaround: The "tacmd addsystem" command line interface can be used
to add the system.


8.0 Additional product information
======================
8.1 APAR IZ50817 - Warehouse update with limited user permissions
-----------------------------------------------------------------
The fix for APAR IZ50817 adds a new attribute Name
to the KR2 HRSYSTEM attribute group. This attribute
will be automatically added to the KR2_HRSYSTEM table
in the warehouse the first time data from agent with
this fix is updated in the warehouse.

For the Warehouse Proxy and Summarization and Pruning
agents to automatically modify the warehouse table definitions,
they must have permission to alter the warehouse tables.

If these agents have not been granted these permissions,
or if they were revoked after the initial tables were
created, then the Schema Tool shipped as part of the
Summarization and Pruning Agent version 6.2.1 should be
used to get the new attributed added to the table. The
following link can be used to obtain more information
about the tool:
http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1
/index.jsp?topic=/com.ibm.itm.doc_6.2.1/itm_install247.htm

8.2 APAR IZ41920 - History collection
-------------------------------------
Fix 6.2.1-TIV-ITM_AL-IF0001 included a change to the agent
history collection for 64-bit data. If the steps below
have already been completed, there are no additional steps
to follow.

For APAR IZ41920, when history collection is started with the
collection location specified as "TEMA", the tables created
in the warehouse database define the columns for 64-bit data
as 32-bit.

If any data has already been uploaded to the warehouse for any of
the tables listed below, the columns for the 64-bit data are
defined incorrectly with a datatype of INTEGER instead of
BIGINT or Number(20). In those cases, once this fix has been
installed, the tables will need to be dropped in the warehouse
database. Once dropped, the tables will be recreated with
correct values the next time data is uploaded to the warehouse.

Listed below are the tables affected. Included for each table
is an example of one of the column names affected by this
problem. To verify the table has been created correctly,
verify that the example column name is defined as BIGINT or
Number(20).

Agentless Monitoring for Windows Operating Systems (KR2)
--------------------------------------------------------
Attribute group name: Process
Table name: KR2WMINPLS
Warehouse table name: KR2_PROCESS or KR2WMINPLS
Example Column Affected: "Handle_Count"
Attribute group name: Physical Memory
Table name: KR2WIN32PH
Warehouse table name: KR2_PHYSICAL_MEMORY or KR2WIN32PH
Example Column Affected: "Capacity"
Attribute group name: Virtual Memory
Table name: KR2MEMORY
Warehouse table name: KR2_VIRTUAL_MEMORY or KR2MEMORY
Example Column Affected: "Available_KBytes"
Attribute group name: Physical Disk
Table name: KR2WIN32P0
Warehouse table name: KR2_PHYSICAL_DISK or KR2WIN32P0
Example Column Affected: "DiskByesPersec"
Attribute group name: Logical Disk
Table name: KR2WIN32PE
Warehouse table name: KR2_LOGICAL_DISK or KR2WIN32PE
Example Column Affected: "Disk_Bytes_Per_sec"
Attribute group name: System
Table name: KR2SYSTEM
Warehouse table name: KR2_SYSTEM
Example Column Affected: "File_Control_Bytes_sec"
Attribute group name: Operating System
Table name: KR2WIN32OP
Warehouse table name: KR2_OPERATING_SYSTEM or KR2WIN32OP
Example Column Affected: "Free_Physical_Memory_KBytes"
Attribute group name: Computer System
Table name: KR2WIN32CO
Warehouse table name: KR2_COMPUTER_SYSTEM or KR2WIN32CO
Example Column Affected: "Total_Physical_Memory"
Attribute group name: Terminal Services Session Memory
Table name: KR2TERMIN1
Warehouse table name: KR2_TERMINAL_SERVICES_SESSION_MEMORY or KR2TERMIN1
Example Column Affected: "Private_KBytes"
Attribute group name: Network Interfaces
Table name: KR2WMINNIC
Warehouse table name: KR2_NETWORK_INTERFACES or KR2WMINNIC
Example Column Affected: "Bytes_Received_sec"
Attribute group name: hrStorageTable
Table name: KR2STORTBL
Warehouse table name: KR2_HRSTORAGETABLE or KR2STORTBL
Example Column Affected: "Total_Blocks"
Attribute group name: Disk
Table name: KR2DISK
Warehouse table name: KR2_DISK
Example Column Affected: "Total_Blocks"
Attribute group name: Network
Table name: KR2NICNAV
Warehouse table name: KR2_NETWORK or KR2NICNAV
Example Column Affected: "Bytes_In_per_sec"

Agentless Monitoring for AIX Operating Systems (KR3)
----------------------------------------------------
Attribute group name: hrStorageTable
Table name: KR3STORTBL
Warehouse table name: KR3_HRSTORAGETABLE or KR3STORTBL
Example Column Affected: "Total_Blocks"
Attribute group name: Memory
Table name: KR3MEMORY
Warehouse table name: KR3_MEMORY
Example Column Affected: "Total_Memory_Blocks"
Attribute group name: Network
Table name: KR3NIFTABL
Warehouse table name: KR3_NETWORK or KR3NIFTABL
Example Column Affected: "Bytes_In_per_sec"

Agentless Monitoring for Linux Operating Systems (KR4)
------------------------------------------------------
Attribute group name: Disk
Table name: KR4DISK
Warehouse table name: KR4_DISK
Example Column Affected: "Total_Blocks"
Attribute group name: hrStorageTable
Table name: KR4STORTBL
Warehouse table name: KR4_HRSTORAGETABLE or KR4STORTBL
Example Column Affected: "Total_Blocks"
Attribute group name: Memory
Table name: KR4MEMORY
Warehouse table name: KR4_MEMORY
Example Column Affected: "Total_Memory_Blocks"
Attribute group name: Network
Table name: KR4NIFTABL
Warehouse table name: KR4_NETWORK or KR4NIFTABL
Example Column Affected: "Bytes_In_per_sec"

Agentless Monitoring for HP-UX Operating Systems (KR5)
------------------------------------------------------
Attribute group name: Disk
Table name: KR5FILESYS
Warehouse table name: KR5_DISK or KR5FILESYS
Example Column Affected: "Total_Blocks"
Attribute group name: Memory
Table name: KR5MEMORY
Warehouse table name: KR5_MEMORY
Example Column Affected: "Available_Physical_Memory_KB"
Attribute group name: Network
Table name: KR5IFTABLE
Warehouse table name: KR5_NETWORK or KR5IFTABLE
Example Column Affected: "Bytes_In_per_sec"

Agentless Monitoring for Solaris Operating Systems (KR6)
--------------------------------------------------------
Attribute group name: Disk
Table name: KR6CIMDISK
Warehouse table name: KR6_DISK or KR6CIMDISK
Example Column Affected: "Total_Blocks"
Attribute group name: hrStorageTable
Table name: KR6STORTBL
Warehouse table name: KR6_HRSTORAGETABLE or KR6STORTBL
Example Column Affected: "Used_Blocks"
Attribute group name: Network
Table name: KR6CIMNIC
Warehouse table name: KR6_NETWORK or KR6CIMNIC
Example Column Affected: "Bytes_In_Per_Sec"
Attribute group name: SMA Disk
Table name: KR6DISK
Warehouse table name: KR6_SMA_DISK or KR6DISK
Example Column Affected: "Used_Blocks"
Attribute group name: SMA Memory
Table name: KR6HRMEM
Warehouse table name: KR6_SMA_MEMORY or KR6HRMEM
Example Column Affected: "Available_Physical_Memory_KB"
Attribute group name: SMA Network
Table name: KR6IFTABLE
Warehouse table name: KR6_SMA_NETWORK or KR6IFTABLE
Example Column Affected: "Bytes_In_per_sec"
Attribute group name: SMC Memory
Table name: KR6SMC0MEM
Warehouse table name: KR6_SMC_MEMORY or KR6SMC0MEM
Example Column Affected: "Available_Swap_Space_KB"
Attribute group name: SMC Network
Table name: KR6SMC0NIC
Warehouse table name: KR6_SMC_NETWORK or KR6SMC0NIC
Example Column Affected: "Bytes_In_per_sec"
Attribute group name: SMC NFS
Table name: KR6SMCNFS
Attribute group name: SMC UFS
Example Column Affected: "FileSystemSize"
Attribute group name: SMC UFS
Table name: KR6SMC0DSK
Warehouse table name: KR6_SMC_UFS or KR6SMC0DSK
Example Column Affected: "FileSystemSize"
Attribute group name: SMC VxFS
Table name: KR6SMCVXFS
Warehouse table name: KR6_SMC_VXFS or KR6SMCVXFS
Example Column Affected: "FileSystemSize"


8.3 Dynamic add and remove of subnodes
--------------------------------------
Fix 6.2.1-TIV-ITM_AL-IF0003 included the addition of
a set of Take Actions to the Agentless Monitoring
at the instance level. These Take Actions support the
dynamic adding and removing of subnodes, one subnode
at a time.

When the Take Actions listed below are invoked, the monitoring
is started or stopped (depending on the Take Action selected)
immediately. The information is saved so if the agent is
restarted the subnode changes made with the Take Actions are
still in effect.

When adding a new subnode, the community name is entered in
clear text in the GUI, however it is stored in encrypted format.

Agentless Monitoring for Windows Operating Systems (KR2)
--------------------------------------------------------
Take Action Name: WindowsSnmpMonitorStart
Description: Begin Data Collection from a remote Windows
endpoint system.
Arguments:
Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.
Host
The host or IP address of the SNMP server.
Community
The SNMP server community name.

Take Action Name: WindowsSnmpMonitorStop
Description: Stop Data Collection from a remote Windows
endpoint system.
Argument:
KR2_MANAGED_SYSTEMS_SNMP.Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.

Agentless Monitoring for AIX Operating Systems (KR3)
------------------------------------------------------
Take Action Name: AIXSnmpMonitorStart
Description: Begin Data Collection from a remote AIX
endpint system.
Arguments:
Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.
Host
The host or IP address of the SNMP server.
Community
The SNMP server community name.

Take Action Name: AIXSnmpMonitorStop
Description: Stop Data Collection from a remote AIX
endpoint system.
Argument:
KR4_MANAGED_SYSTEMS_SNMP.Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.


Agentless Monitoring for Linux Operating Systems (KR4)
------------------------------------------------------
Take Action Name: LinuxSnmpMonitorStart
Description: Begin Data Collection from a remote Linux
endpoint system.
Arguments:
Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.
Host
The host or IP address of the SNMP server.
Community
The SNMP server community name.

Take Action Name: LinuxSnmpMonitorStop
Description: Stop Data Collection from a remote Linux
endpoint system.
Argument:
KR4_MANAGED_SYSTEMS_SNMP.Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.


Agentless Monitoring for HP-UX Operating Systems (KR5)
------------------------------------------------------
Take Action Name: HPSnmpMonitorStart
Description: Begin Data Collection from a remote HP
endpoint system.
Arguments:
Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.
Host
The host or IP address of the SNMP server.
Community
The SNMP server community name.

Take Action Name: HPSnmpMonitorStop
Description: Stop Data Collection from a remote HP
endpoint system.
Argument:
KR5_MANAGED_SYSTEMS_SNMP.Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.


Agentless Monitoring for Solaris Operating Systems (KR6)
--------------------------------------------------------
Take Action Name: SystemManagementAgentMonitorStart
Description: Begin Data Collection from a remote System
Management agent.
Arguments:
Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.
Host
The host or IP address of the SNMP server.
Community
The SNMP server community name.

Take Action Name: SystemManagementAgentMonitorStop
Description: Stop Data Collection from a remote System
Management agent.
Argument:
KR6_MANAGED_SMA_SYSTEMS.Subnode_Resource_Name
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.


Take Action Name: SunManagementCenterMonitorStart
Description: Begin Data Collection from a remote Sun
Management Center endpoint system.
Arguments:
The name that appears in the Tivoli Enterprise
Portal Navigator tree for this host. The name
must be unique across all instances of this agent.
Host
The host or IP address of the SNMP server.
Community
The SNMP server community name.

Take Action Name: SunManagementCenterMonitorStop
Description: Stop Data Collection from a remote Sun
Management Center endpoint system.
Argument: KR6_MANAGED_SMA_SYSTEMS.Subnode_Resource_Name


8.4 APAR IZ81461 - Update clearing event with multiple NICs
-----------------------------------------------------------
The fix for APAR IZ53982 modified the attribute Index in the
Network attribute group to be an atomized attribute. To make
use of this variable in the clearing event, follow the steps below.
If the steps below have already been completed, there is no need
to repeat these steps.
- Edit or copy the existing KR<n>_SNMP_NIC_Status_Down or
KR<n>_SNMP_NIC_Status_Unknown situation.
- Select "Advanced...".
- In the "Advanced Situation Options" dialog, select the
"Display Item" tab. Under the "Display Item" field,
select "Index".
- Save the situation.

8.5 APAR IZ81461 - SOLARIS SMC NFS MOUNT POINT IS NOT DEFINED AS
DISPLAY ITEM
----------------------------------------------------------------
The fix for this APAR modifies the attribute NFS Mount Point in the
"KR6 SMC NFS" attribute group to be an atomized attribute. To make
use of this variable in the clearing event, follow the steps below:
- Create or edit an event using at least one attribute from the
"KR6 SMC NFS" attribute group.
- From the Situation Editor dialog box, select "Advanced...".
- In the "Advanced Situation Options" dialog, select the
"Display Item" tab. Under the "Display Item" field,
select "FileSystemMountPoint".
- Save the situation and restart it.

8.6 APAR IZ64799 - AGENT USES LARGE AMOUNT OF MEMORY DUE TO NUMBER
OF DOMAIN USER ACCOUNTS
------------------------------------------------------------------
When using the Agentless Monitor for Windows, and the instance is
configured to use Windows API Connection to monitor a domain
controller running Windows Server 2003, excessive CPU on the domain
controller is used. This problem can occur only when the Windows
API Connection (WMI) is configured and does not apply when the SNMP
Connection is configured for the instance.

Microsoft has a hotfix available for this problem which should be
installed on the domain controller:
http://support.microsoft.com/kb/933593

It is recommended to not monitor Windows Domain controller running
Windows 2003 via the Agentless WMI interface until this hot fix has
been installed.

Refer to this technote for information and guidelines:
http://www.ibm.com/support/docview.wss?uid=swg21430280

9.0 Notices
=======
This information was developed for products and services offered
in the United States. IBM may not offer the products, services, or
features discussed in this document in other countries. Consult
your local IBM representative for information on the products and
services currently available in your area. Any reference to an
IBM product, program, or service is not intended to state or imply
that only that IBM product, program, or service may be used. Any
functionally equivalent product,program, or service that does not
infringe any IBM intellectual property right may be used instead.
However, it is the user's responsibility to evaluate and verify
the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject
matter described in this document. The furnishing of this document
does not grant you any license to these patents. You can send license
inquiries, in writing, to:

IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

The following paragraph does not apply to the United Kingdom or
any other country where such provisions are inconsistent with local law:

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 states do not allow disclaimer of express or implied warranties
in certain transactions, therefore, this statement may not apply to you.

Trademarks and service marks
------------------------------------
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks
of International Business Machines Corp., registered in many
jurisdictions worldwide. Other product and service names might be
trademarks of IBM or other companies. A current list of IBM trademarks
is available on the Web at "Copyright and trademark information" at
www.ibm.com/legal/copytrade.shtml.

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

Java and all Java-based trademarks are trademarks of Sun Microsystems,
Inc. 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