Fix Readme
Abstract
Readme file for: Windows OS Monitoring Agents for IBM Application Performance Management 8.1.4.0 Interim Fix 6
Product/Component Release: 8.1.4.0
Update Name: 8.1.4.0-IBM-APM-Windows-OS-AGENT-IF0006
Fix ID: 8.1.4.0-IBM-APM-Windows-OS-AGENT-IF0006
Publication Date: 04 Dec 2019
Last modified date: 04 Dec 2019
Content
Download location
IMPORTANT NOTE:
1. To download this update, you must first login to IBM Fix Central using this link: http://www.ibm.com/support/fixcentral/
2. There are three download options on Fix Central: Download Director, FTPS/SFTP and Using your browser (HTTPS). If you want to download individual packages, you need choose FTPS/SFTP or HTTPS, since Download Director will download all.
Below is a list of components, platforms, and file names that apply to this Readme file.
Fix Download for Windows
Product / Component Name | Platform | Fix |
IBM Application Performance Management | Windows 32-bit | 8.1.4.0-IBM-APM-OS-AGENT-WIN32-IF0006 |
IBM Application Performance Management | Windows 64-bit | 8.1.4.0-IBM-APM-OS-AGENT-WIN64-IF0006 |
Prerequisites and co-requisites
General description
This is an interim fix for the Windows OS Monitoring Agents provided with the IBM Cloud Application Performance Management version 8.1.4.0 and IBM Cloud App Management family of products . It upgrades the Windows OS Monitoring Agents to version 06.36.14.10.
Platforms and prerequisites
The Windows OS Monitoring Agent is supported on the platforms documented here.
Prerequisites for this interim fix
The interim fix for the Windows OS Monitoring Agents intended to be applied to the Windows OS Monitoring Agents which is provided with
IBM Cloud Application Performance Monitoring Base, Version 8.1.4.0
IBM Cloud Application Performance Monitoring Advanced, Version 8.1.4.0
IBM Cloud App Management, Version 2019.3.0 and later
Known issues
- Symptom: The <hostname>_<pc>_fcp_daemon_logmonitoring_*.log may contains many messages "ERROR: tec_put_event failed, rc = -1". This occurred due to the agent trying to send EIF events even though there is no valid ServerLocation nor ServerPort had been set.
Workaround: None. These messages can be ignore.
- Symptom: Event log data failed to displayed matched record data
Workaround: Add "LognameIsBasename=N" in the Log Monitoring CONF file
- Symptom: Custom scripting is not enable during upgrade of the Windows OS agent
Workaround: Edit <install>\TMAITM6_x64\KNTENV to change KNT_FCP_SCRIPT=TRUE and restart agent.
- Symptom: Log file monitoring error seen (SYNTAX_ERROR or CONE_FILE_DOES_NOT_EXIST) which may be due to file discovered in <install>\localconfig\nt\log_discovery\Last-Modified\ directory
Workaround: Update the agent core framework to 8.1.4.0-IBM-APM-CORE-FRAMEWORK-IF0014 or newer.
Known limitations
None
Installation information
Prior to installation
Installing
Installing the agent interim fix on each agent system
Note: The agent must already be installed before applying the patch. It will be restarted as part of applying the patch.
- Download the patch bundle from Fix Central for each OS type where your agent is installed:
- If the agent is installed on 32-bit Windows System, download 8.1.4.0-IBM-APM-OS-AGENT-WIN32-IF0006.tar
- If the agent is installed on 64-bit Windows System, download 8.1.4.0-IBM-APM-OS-AGENT-WIN64-IF0006.tar
- Extract the patch bundle on each computer system where the agent is already installed by using an unzip utility or windows explorer into the temporary directory.
- Enter the created directory
cd c:\tmp\if06 - Run the apmpatch.bat tool as the same user who installed the agent:
apmpatch.bat <APM-AGENT-HOME>
The <APM-AGENT-HOME> specifies the directory where the agent is installed.
Perform the necessary tasks after installation
Uninstalling if necessary
This agent maintenance package cannot be rolled back. If necessary you can uninstall and reinstall the monitoring agent and all appropriate patches.
For detailed instructions to uninstall monitoring agents, please refer to the IBM Cloud Application Performance Management guide, here:
http://www.ibm.com/support/knowledgecenter/SSHLNR_8.1.4/com.ibm.pm.doc/install/uninstall_agents.htm
Troubleshooting installation problems from the Support site
For more detailed information, refer to the Troubleshooting and support Guide:
http://www.ibm.com/support/knowledgecenter/SSHLNR_8.1.4/com.ibm.pm.doc/install/trouble_intro.htm
IBM Cloud Application Performance Management Documentation URL:
- For on-premise documentation, click http://ibm.biz/kc-ipm8
- For SaaS documentation, click https://ibm.biz/kc-apmsaas
IBM Cloud Application Performance Management forum
For installation issues, go to https://ibm.biz/dw-ipmforum and search on "installation". If your issue is not addressed
in one of the forum entries, create a new entry and describe your issue.
Additional information
The Secure Hash Algorithm 1 (SHA256) checksum of the images are as follows:
SHA256(8.1.4.0-IBM-APM-OS-AGENT-WIN32-IF0006.tar) = e9ee43ebb533673215b6ad4977d82dcf951fcee17574aa9f25b342d91c568677
SHA256(8.1.4.0-IBM-APM-OS-AGENT-WIN64-IF0006.tar) = 916bb1c0e3c5e57c59fd53eadacbfd4dbc499716bc747adf48a0768e1303f1ab
Image Contents
The following files implement this fix.
- 8.1.4.0-IBM-APM-WIN-OS-AGENT-IF0006.readme.html - This README file
- 8.1.4.0-IBM-APM-OS-AGENT-WIN32-IF0006.tzip - For extracting patch files use an unzip utility.
Extracting the above bundle (.zip) creates the following directory and patch files:
8.1.4.0-IBM-APM-OS-AGENT-WIN32-IF0006/
|-- apmpatch.bat
|-- patches
|-- patch.properties
- 8.1.4.0-IBM-APM-OS-AGENT-WIN64-IF0006.zip - For extracting patch files use an unzip utility.
Extracting the above bundle (.zip) creates the following directory and patch files:
8.1.4.0-IBM-APM-OS-AGENT-WIN64-IF0006/
|-- apmpatch.bat
|-- patches
|-- patch.properties
New Features
List of fixes
The following problems are addressed by this interim fix.
APARs
- None
Defects:
- Git 12758: Windows OS agent incorrectly set OSAGNTNODE value
Enhancements:
- None
APARS and defects included from superseded fixes:
APARs:
- IJ06379: Windows OS agent crash when encounter bad performance counters
- IJ14405: NT_SERVICE.DISPLAY_NAME is not available in the threshold editor display item
- IJ12571: TIMESTAMP attribute not available for Windows OS Agent 'NT_SYSTEM'
- IJ12168 OS AGENT LOG MONITORING FAIL COLLECT DATA FOR 'Kxx_LOGFILEPROFILEEVENTS'
- IJ12039: OS Agent log monitoring failed to displayed matched record data
- IV96363: Windows 2016 crash: GetFilePosition sets position to a large invalid number causes crash in fgetpos
Defects:
- 134672: Fixed issue where distributed MSN are not checked in the OS agent configuration
- 130156: Additional attributes needed in the Windows OS Agent
- 125619: High amount of KUMP_MonitoredFileInt messages in the fcp_daemon logs
- 124211: Request for Memory data to be uploaded once per minute
- 123981: Windows OS agent doesn't install the *.swidtag file
- 121741: OS Agents sda file missing tab configuration eba
Enhancement:
- 138999: Adding custom scripting feature
Document change history
Version | Date | Description of change |
1.0 | 04 Dec 2019 | Initial Version |
Was this topic helpful?
Document Information
Modified date:
04 December 2019
UID
ibm10883602