Certain Linux OS or Windows OS File System events are being Forced-closed or RATE_CLOSED and immediately reopened again on the next polling cycle. This is despite the parameter value always remaining above the threshold. |
This issue is resolved in version 11.3.04. For 11.3.01, install the latest core hotfix from ftp://ftp.bmc.com/pub/TSIM/PATCHES/11.3.01/GA/ For 11.3.02, install the latest core hotfix from ftp://ftp.bmc.com/pub/TSIM/PATCHES/11.3.02/ For 11.3.03, install the latest core hotfix from ftp://ftp.bmc.com/pub/TSIM/PATCHES/11.3.03/ If it is not possible to install the hotfix, please use the following workarounds: Linux OS Monitoring : Steps to workaround the problem: 1) Go to "Infrastructure Policies" under "Configuration" in TSPS 2) Edit the respective policy 3) Goto "Polling Intervals" tab 4) Click on "Add Polling interval". a) Select "Linux" for "Monitoring Solution" b) Select "Linux OS" for "Monitor Type" c) Select "LinuxOSConfigCollector" for "Monitor Parameter" d) Change "Parameter Polling Interval" to 23:59:00 e) Select appropriate version For Solaris OS Monitoring : Steps to workaround the problem: 1) Go to "Infrastructure Policies" under "Configuration" in TSPS 2) Edit the respective policy 3) Goto "Polling Intervals" tab 4) Click on "Add Polling interval". a) Select "Solaris" for "Monitoring Solution" b) Select "Solaris OS" for "Monitor Type" c) Select "kisConfigCollector" for "Monitor Parameter" d) Change "Parameter Polling Interval" to 23:59:00 e) Select appropriate version. For Windows OS Monitoring there is no workaround. -By default "System Configuration" for "Monitor Parameter" Polling Interval is 24 hours but still this issue is observed. |