cdm (CPU, Disk, Memory Performance Monitoring) Release Notes

The CPU, Disk, Memory Performance Monitoring (cdm) probe monitors the performance and resource load on the system with the robot. The probe provides the following benefits:
The CPU, Disk, Memory Performance Monitoring (cdm) probe monitors the performance and resource load on the system with the robot. The probe provides the following benefits:
  • Generate alarms that are based on configured threshold values. The probe generates alarms that can trigger corrective actions immediately.
  • Generate trending Quality of Service (QoS) data. The information is measured and sent to the data_engine probe to process and store in the CA UIM database. The historical data facilitates capacity planning for monitored systems in the IT environment. Some examples are as follows:
    • View how disks are filling up over time.
    • Plan batch jobs according to the CPU utilization.
    • Upgrade systems which consistently operate near capacity.
Revision History
This section describes the history of the probe updates.
Support cases may not be viewable to all customers.
  • Released with DX UIM 20.4.0
December 2021
What's New:
  • New MCS template v6.71 with:
    • Added the following Metrics in the Memory Monitor Enhanced template
  • Added support for monitoring a newly discovered disk instantly by CDM. Newly discovered mount-points/disks are monitored as soon as CDM discovers them.
    To use this feature, you must make the following changes in any of these interfaces:
    • In IM through Raw Configure:
      Update the key ‘Monitor_Newly_Discovered_Disk_OnTheFly’ to 'yes'. By default, this is set to 'no'.
    • In Default Disk(s) (Enhanced) template (in MCS):
      Enable ‘Monitor Newly Discovered Disk at First Instance (On the Fly)’. By default, this is disabled.
    • In Admin Console:
      Enable ‘Monitor Newly Discovered Disk at First Instance (On the Fly)’. By default, this is disabled.
    For the CDM and the Cluster probe integration:
    As a prerequisite, you must install the latest cluster probe version along with the CDM probe v6.70. Make sure to set the following key/values in the cdm.cfx file under the <fixed default> section.
    • 'active = yes'
    • 'Monitor_Newly_Discovered_Disk_OnTheFly = yes'
  • Added support to allow the custom values in all QoS Interval fields for the CDM probe (MCS Templates). 'QoS Interval' field label is renamed to 'QoS Intervals (Number of Intervals)'. This field allows values in the range of 1 to 999.
Fixed Defects:
  • Fixed an issue where incorrect shared disk (Used and Free disks) size is shown in IM GUI.
    Support case 32672121.
  • Fixed an issue with the cluster probe, related to the new drives. Whenever any new drives are added, not only those drives are discovered but also enabled/activated.
    Support case 32475320.
  • Fixed an issue with the new drives/mount points getting added and are auto discovered and monitored.
    Support case 20304402, 20103461, and 20187228.
  • Fixed an issue where the disk size was showing incorrect on IM GUI when the disk size is in TB and float number (Non integer fractional number) (Ex : actual value is 1.5TB but it shows as 2TB).
    Support case 32621269.
  • Fixed an issue where the metric disk free is showing negative value (-21474836.48) in alarm message when the disk size is too large.
    Support case 32598885.
September 2021
What's New:
  • Added support for Remote Disk Monitoring for Windows mapped drives.
    Starting this version, CDM detects and monitors the remote disks when you enable "Default Disk(s) (Enhanced)" profile. Enabling configuration for Windows Remote Disk Monitoring:
    • Enable "NFS Space Check" in the "Default Disk(s) (Enhanced)" template.
    • Enable "Remote Disk Space check for Windows" in the "Default Disk(s) (Enhanced)" template.
  • Added support to manage probe internal alarms for disk in “Default Disk(s) (Enhanced)" template:
    • New flags in "Default Disk(s) (Enhanced)" template are added to toggle internal alarms published by probe. These flags help to prevent duplicate alarms from by probe and Alarm Policy.
      You can also manage the notification alarms for “Disk Missing” that cannot be configured by Alarm Policy.
      • Alarm on Disk Error
      • Alarm on Inode Error
      • Alarm on Missing Disk
  • Enhanced latency and throughput CDM QOS Metrics for more accuracy.
    The latency QOS metrics as follows:
    The throughput for disk QOS metrics as follows:
  • Added support for ZFS calculation for Solaris 11.
  • Added support for NFS disk monitoring through CDM "Default Disk(s) (Enhanced)" template.
  • Added support for Iostat devices missing alarm (Linux, Solaris and AIX) in the "Iostat (Enhanced)" template.
    Device Missing Alarm specifies whether to send the device missing alarm or not.
    In some cases, you may see the disks in the Iostat that are already removed in the robot OS machines. To get the device missing alarms in Solaris, Linux or AIX, you must restart the robot OS machine.
  • New MCS template v6.60 with:
    • Removed the config fields from "Setup CDM (Enhanced)" MCS Template that are not applicable. Following are the removed config fields:
      • Send Alarm on Each Sample
      • Set QoS Target as Total
      • Number of Top CPU-consuming Processes in Alarms
      • Set QoS Target as Memory
    • Added support for Iostat monitoring configuration for Solaris and Aix in "Iostat (Enhanced)" Template.
      • Enable All Iostat Devices (Solaris) - NON-QOS (Config Item): Specifies if all Iostat SOLARIS devices are active for monitoring.
      • Enable All Iostat Devices (AIX) -NON-QOS (Config Item): Specifies if all Iostat AIX devices are active for monitoring.
    • Re-enabled QOS metrics and updated labels for all supported metrics platforms on each QOS metric in the "Iostat (Enhanced)" template.
    • Added support for additional QOS configurations to manage using "MEMORY Monitor (Enhanced)" template.
      • Total Physical Memory QOS_PHYSICAL_MEMORY_TOTAL
      • Total Memory QOS_MEMORY_TOTAL
      • Available Memory QOS_MEMORY_AVAILABLE
    • Added support for additional QOS configurations to manage using "CPU Monitor (Enhanced)" template.
      • Computer Uptime QOS_COMPUTER_UPTIME
      • Number of CPU QOS_CPU_NUM
      • Smt (AIX) QOS_CPU_SMT
      • Load Average 15 Minutes (UNIX) QOS_LOAD_AVERAGE_15MIN
      • Load Average 5 Minutes (UNIX) QOS_LOAD_AVERAGE_5MIN
      • Load Average 1 Minute (UNIX) QOS_LOAD_AVERAGE_1MIN
      • Total CPU Steal (Linux) QOS_CPU_USAGE
      • Individual CPU Steal (Linux) QOS_CPU_MULTI_USAGE
    • Corrected default threshold values for "Disk(s) (Enhanced)" template as per parent "Default Disk(s) (Enhanced)" template.
Fixed Defects:
  • Fixed an issue with the robot taking up all the ports when there was a network issue.
    Support case 32089502
  • Fixed an issue related to the unusual number of TCP connections on spooler for AIX Servers. Support case 32078399
  • Fixed an issue with no option for Monitoring remote Disks in Template.
    Support case 31871639
  • Fixed several issues related to MCS (Enhanced) templates and Operator Console.
    Support case 31853537
  • Fixed an issue related to the collection of read/write latency for disks on Windows.
    Support case 20105370
  • Fixed an issue where CDM - mem_buffer_used is not working on Solaris server.
    Support case 20311404
  • Fixed an issue where CDM on Solaris servers does not respect zfs use of memory cache.
    Support case 20077062
  • Fixed an issue with the incorrect CDM Solaris memory usage based on the value that is used for Data Buffer and Cache.
    Support case 31919334
  • Fixed an issue related to NFS file system monitoring using CDM MCS.
    Support case 31721569
  • Fixed an issue where NIC Monitor (Enhanced) is deployed to Linux device but the template is for Windows.
    Support case 20143279
March 2021
What's New:
  • Global IOSTAT monitoring: Ease of Configuration
    Global IOSTAT monitoring configuration through CDM MCS template “Iostat (Enhanced)” to enable all the available device on system. This feature works as mentioned below:
    Iostat (Enhanced) > Enable All Iostat Devices (Linux) > Active
    Active check box has been implemented for Iostat (Enhanced) where it enable/disable all Linux devices respectively if checked or unchecked.
    The list of monitors which user can configure under
    Iostat (Enhanced)
    are as follows:
    1. Iostat read requests merged per second
    2. Iostat write requests merged per second
    3. Iostat reads per second
    4. Iostat writes per second
    5. Iostat sector reads per second
    6. Iostat sector writes per second
    7. Iostat average request Size
    8. Iostat average queue length
    9. Iostat average wait time
    10. Iostat average service time
    11. Iostat utilization percentage
    12. Iostat Kilobytes reads per second
    13. Iostat Kilobytes writes per second      
  • With cluster 3.70 onwards: Added functionality - CDM discovers all the cluster disks automatically under their respective groups, whenever the Cluster probe is configured after the deployment of CDM probe.
  • Support for newer OS SUSE 15, RHEL 8
Fixed Defects:
  • Average (8 samples) swap memory usage is now 0.00%%, which is above the error threshold (65%).
    Support case 01248394
  • Incorrect Thresholds Operators for Disk Free (%) Condition Alarm Policy.
    Support case 20012724
March 2020
What's New:
  • Introduced the
    key to prevent clearing of disk alarms on server restarts. This avoids duplicate tickets from being created. Manually add this key in the configuration file using the raw configuration interface. For more information, see cdm Advanced Configuration.
  • The cdm MCS (version 6.42 onwards) has been updated as part of addressing the common vulnerabilities and exposures by updating the jackson-databind libraries. For more information and CVE numbers, see Addressing Jackson Vulnerabilities.
Fixed Defects:
  • The probe was generating alarms for swap memory monitors below the specified threshold.
    Support case 01185304
  • Fixed an issue where the probe was unable to get network aggregated traffic data for some servers.
    Support case 01130190
  • Fixed an issue where the probe was incorrectly categorizing the alarm severity.
    Support case
  • Fixed an issue where the probe was generating unconfigured alarms.
    Support case
  • Fixed an issue where the memory paging metrics were active after removing the Memory Monitor (Enhanced) MCS profile.
    Support case
April 2019
What's New:
  • The following metrics have been added to the probe.
    • Memory - Available Memory
    • Network - Inbound Interface Errors, Outbound Interface Errors, Inbound Interface Discards, Outbound Interface Discards, Inbound Interface Utilization, Outbound Interface Utilization
  • Added support for monitoring Ubuntu 18, SuSE 15, and Open SuSE 15.
Fixed Defects:
  • The probe was using FQDN with hostname as the target for some metrics.
    Support Case Number: 01097118
  • The probe was generating
    "special characters" in QOS_COMPUTER_UPTIME targets over time.
    Support Case Number: 00886969
  • The probe was showing wrong data for Disk Latency Read metrics.
    Support Case Number: 01062700
  • The probe had issues with MCS configuration for the cpu metrics.
    Support Case Number: 01126989
  • Fixed a defect of increasing the field length from 50 characters to 1024 characters.
    Support Case Number: 00894858
  • Fixed an issue where the
    key is set to NO in raw configuration, however, the buffer and cache memory were used in memory monitoring.
    Support Case Number: 01257778
January 2019
What's New:
  • Updated to support the Microsoft Visual C++ Redistributable for Visual Studio 2017 package version 1.01 (vs2017_vcredist_x86 1.01 and vs2017_vcredist_x64 1.01). This support ensures that the minimum version of the VS 2017 package is equal to or greater than 1.01. With this dependency on the version 1.01, the computer is no longer getting restarted automatically when installing the VS 2017 package. That is, with v1.01, no auto-restart of the computer happens.
  • (February 2019) Added support for monitoring Windows 2019.
December 2018
What's New:
  • Updated this probe as part of removing dependency on the end-of-life (EOL) Microsoft Visual C++ Redistributable in CA UIM 9.0.2. CA UIM 9.0.2 now uses Microsoft Visual C++ Redistributable for Visual Studio 2017.
  • Updated this probe as part of removing known security vulnerabilities in CA UIM 9.0.2 by using the upgraded OpenSSL components.
  • (December 2018) Added support for monitoring Amazon Linux 2.
October 2018
What’s New
  • A new MCS template package cdm_mcs_template.
  • (MCS)
    Added IOSTAT template.
  • (MCS)
    Added QoS and alarms for Inode.
  • (MCS)
    Disks template is now a part of Default Disk template.
  • (MCS)
    Added Disk IO Template.
  • (MCS)
    Ability to monitor shared disks.  
  • (IM, AC,
    Added new metric for total physical memory. The probe now generates a QoS for total physical memory (RAM) of a system.
  • (IM, AC,
    New QoS for reporting and generating alarm for change in disk usage in %.
  • (IM
    Two new QoS Disk Free% and Disk Free MB.
  • Added a feature where the probe will not send a clear alarm on soft restart.
  • Added support for Debian 8 (64 bit) and Window 8.1 (32 bit and 64 bit).
  • (June 2018) Added support for monitoring Windows 10 (x64).
  • (June 2018) New MCS template (cdm_mcs_template 6.31). Enhanced profiles that enable you to configure metrics, baselines, alarm thresholds, alarms - including Time Over Threshold alarms - and custom alarm and close alarm messages, all within a single MCS profile.
  • (July 2018) Added support for monitoring RHEL 7.4 x86 and x86 64-bit, and z/Linux 64-bit.
  • (September 2018) Added support for monitoring Ubuntu 18.04 for probe version 5.80 and above. Apply robot 7.93HF10 for this support.
    Support Case: 01184423
Fixed Defects:
  • The probe (on Solaris) reported negative values for Memory.
    Support Case
    Number: 00876624
  • The probe reported frequent internal errors for CPU and Memory on AIX 6.1 and 7.1.
    Support Case Number: 00803946
  • The probe shows as offline after upgrade to 6.10/6.20 on Windows 2003 (32 bit).
    Support Case Number: 00890739
  • The probe failed to start (max. restarts reached) on Windows 2003 (32 bit).
    Support Case Number: 00866156
  • The probe resets Disk monitoring when deployed to a server and configured as a fresh setup (RHEL 7).
    Support Case Number: 00869489
  • The probe version 6.10 was unable to monitor CSV Mount Points.
    Support Case Number: 00830223
  • The probe did not monitor all disk/mount-points.
    Support Case Number:
  • The probe did not generate alarms when the value for metric Network Aggregated Traffic was set to anything other than 0 from Admin Console.
    Support Case Number: 00807908
  • The probe reported disks as Unknown when added to Disk section using MCS on Linux.
    Support Case Number: 00780577
  • The probe reported incorrect inode values for filesystems with large inode counts.
    Support Case Number: 00955048
March 2018
What's New:
  • Added support to collect information and monitor the following:
    • Individual and all CPUs steal time
    • Top memory consuming process
    • Total CPUs in the system
  • (On Admin Console)
    Added metrics and more options to configure IOStat Monitoring for a server.
Fixed Defects:
  • Deactivating QoS resulted in random alarm behavior.
    Salesforce case 00807908
  • The probe did not monitor memory usage on Solaris.
    Salesforce case 00705468
September 2017
What's New:
  • Added support for the following properties of Active Memory Expansion (AME) mode on AIX systems:
    • Memory Dxm
    • Memory Expansion Factor
    • Memory Xphysc
    • SMT
    • Total Memory
  • (On Admin Console)
    Enhanced support of the following monitors for the HPUX and Solaris platforms:
    • Network Inbound Traffic
    • Network Outbound Traffic
    • Network Aggregated Traffic
  • (On Admin Console)
    Added ability to generate disk missing alarms for the iostat devices.
Fixed Defects:
  • The probe did not save the user-specified values for:
    • Low threshold for CPU, Memory, Paging
    • Maximum and Difference values for alarms for Multi CPU.
    Support case numbers 779748, 764888
  • The probe generated excessive false alerts for missing physical disk on AIX systems.
    Support case number 731386
  • The probe did not work when it was deployed on Windows 2008 R2, with multiple active Exchange Servers.
    Support case number 733031
  • The probe delayed alert generation for disks when the QoS interval was different from 1
    . Support case number 722680
July 2017
Fixed Defects:
  • The probe did not work when it was deployed on the following environments:
    • Citrix servers
      Support case numbers 751573, 748606, 246143
    • Windows 2008 servers (64-bit)
      Support case numbers 747868, 739472
    • Windows 2003 servers (64-bit)
      Support case number 700981
June 2017
What's New:
  • Added support to monitor the following disk parameters from the Admin Console interface on Windows and Linux platforms. For more information, see Probe Specific Software Requirements.
    • Total disk latency
    • Disk read latency
    • Disk write latency
  • Added support for 64 or more cores on Windows 7 and Windows Server 2008 R2.
  • Added support for the following features using raw configuration. For more information, see the
    Edit the Configuration File Using Raw Configure
    section in cdm Advanced Configuration.
    • Configure the probe to generate the SAR (System Activity Report) using the current values of the network inbound, outbound, and aggregate traffic monitors.
    • (Solaris Global Zones)
      Configure the probe to use swap -s information for swap memory monitors.
      Support case number 673855
Fixed Defects:
  • On Linux platforms, the probe displayed incorrect values in QoS and alarms for the following parameters.
    Support case number 671150
    • Network Inbound Traffic
    • Network Outbound Traffic
    • Network Aggregated Traffic
  • Added a known issue of cdm 5.80 MC. For more information, see
    Known Issues and Workarounds
    Support case number 667244
  • The probe displayed incorrect values for disk space delta when no thresholds are breached.
    Support case number 647036
  • Updated cdm Metrics for correct description of the QOS_MEMORY_PHYSICAL_PERC monitor.
    Support case number 639610
  • The probe incorrectly generated QoS values for some iostat QoS messages as 0.
    Support case number 630695
  • The probe did not generate dynamic alarms  for CPU usage when the QoS target is specified as
    Support case number 608521
  • Updated the correct help text in the document and the Admin Console GUI for iostat configuration field.
    Support case number 608515
  • The probe always generated the I/O wait time as 0 on HP-UX platforms.
    Support case number 582607
  • The probe repeatedly restarted on Solaris platforms.
    Support case number 467000
This version of the probe does not support FIPS encryption.
April 2017
What's New:
  • (IM Interface only)
    Added support for:
    • AES-128 encryption that is required for FIPS compliance
    • Monitor Windows systems where FIPS encryption is enabled
    For more information, see
    Enable FIPS Encryption
    Probe Specific Changes After Upgrade
In a FIPS encryption enabled environment, you cannot configure the probe from Admin Console (AC) interface.
April 2017
What's New:
  • Added support to monitor disk size in petabytes.
  • The probe supports monitoring within an IPv6 environment.
Fixed Defects:
  • The probe displayed incorrect CPU usage for processors numbered 100 or more.
    Support case number 375031
  • Updated information about unsupported automounted devices.
    Support case number 470827
  • Removed support for 64 core or more Windows systems that was introduced in version 5.70. This addresses the following issues on systems with fewer than 64 cores:
    • The probe did not start on Windows 2003 and 2008 64 bit systems on upgrade to version 5.72.
      Support case numbers 458087, 479327, 510776, 513657, 515175, 592746
    • The probe displayed incorrect values for some cores on physical multi core Windows servers.
      Support case number
  • The probe incorrectly generated values for the network traffic monitors as 0 Bytes per second.
    Support case number 605868
November 2016
Fixed Defects:
  • Added a Known Issue that the probe might reboot the server when VS2010 redistributable package is installed.
    Support case numbers 418980, 441460, 381531, 431742.
  • The probe did not generate QOS for clustered disks in Microsoft Cluster Service when the specified
    QoS Interval
    value was greater than 1.
    Support case 418675
  • (On Admin Console) The probe did not let a user add more than 99 samples under the
    Memory Configuration
    section. The upper limit is now increased to 999.
    Support case number 361547
  • On Linux platform, the probe displayed incorrect value of QoS and Alarms for Network Inbound Traffic, Network Outbound Traffic, and Network Aggregated Traffic.
    Support case number 351916
  • Updated documentation with command and interval information for memory monitoring.
    Support case numbers 356336, 343818.
  • The probe stopped responding when monitoring
    autofs mounted file systems (NFS).
    Support case number
  • The probe displayed incorrect Disk Usage value (MB) under the
    Disk Usage and Threshold
    tab. For example, when the total disk utilization is 2048000 MB and it increases to 96% from 92%, the probe displayed the Disk Usage value as 1875797 MB instead of 1884160 MB.
    Support case number 344035.
July 2016
Fixed Defect:
  • When a missing disk was accessible again, the probe did not clear the
    alarm for the disk.
    Support case number 00268943
April 2016
What's New:
  • Added support for 64 or more cores on Windows 7 and Windows Server 2008 R2. For more information, see Probe Specific Software Requirements.
Fixed Defects:
  • The probe
    Infrastructure Manager
    interface restarted each time it was opened.
    Support case number 293981
  • The probe did not save the timeout value from
    Admin Console
    to the configuration file.
    Support case number 00264729
  • Updated documentation with command and interval information for memory monitoring on Solaris platforms.
    Support case number 00276332
  • Added a Known Issue that the probe generated incorrect device ID remote shared disks.
    Support case number 00297816
March 2016
cdm-MC 5.61
  • This version of the cdm probe works with Monitoring Configuration Service. You can configure and deploy cdm-MC 5.61 through Monitoring Configuration Service. This version of the probe is silent (meaning no QoS data or alarms are emitted) until a configuration profile created with Monitoring Configuration Service is applied to the probe.
Fixed Defects:
  • Probe was consuming high CPU when disks were mounted during run-time.
    Support case number
  • On RHEL platform, the cluster disks were displayed as local or network disks on the cdm Infrastructure Manager (IM).
    Support case number
    : You must use cdm version 5.61 with the cluster version 3.33 to view the cluster disks on the cdm Infrastructure Manager (IM).
December 2015
What's New:
  • Added two new alert metrics, CpuErrorProcesses and CpuWarningProcesses, to define the number of top CPU consuming processes in the probe
  • Added support to enable the default QoS for Memory Usage in percentage.
Fixed Defect:
  • Updated the cdm IM Configuration to state that the probe uses the mount entries as in /proc/mounts file in Linux to display the file system type of devices that are remounted to a different location.
    Salesforce case 246152
December 2015
What's New:
  • Added support to ignore iostat devices from monitoring, using regular expressions on Linux, Solaris, and, AIX platforms.
    Salesforce case 00168980
  • Added support to ignore the devices configured through super package.
    Salesforce cases 70000803, 00167576
Fixed Defects:
  • Added two new keys
    in the Raw Configuration section of the probe. These keys are supported for AIX platform.
    Salesforce case 00160805
    : See
    Options Configured Using Raw Configure
    section in the
    v5.5 cdm IM Configuration
    article for more information related to these keys.
  • The probe generated the local file system disk missing alarm message for all type of disks (Network, Local, and, Shared).
    Salesforce case 00162388
    : The probe generates the updated message only on a fresh deployment of the probe.
  • The probe crashed when disk delta QoS were enabled and alarms were configured through custom profile.
    Salesforce case
  • The probe calculated the value of Physical Memory Utilization metric incorrectly.
    Salesforce case 70000322
  • The probe generated false reboot alarms.
    Salesforce cases 00161914, 70001349, 00168047
September 2015
What's New:
  • Three new Metrics QOS_LOAD_AVERAGE_1MIN, QOS_LOAD_AVERAGE_5MIN and QOS_LOAD_AVERAGE_15MIN have been added on Linux, Solaris, AIX and HP-UX platforms.
  • Added a section in the Troubleshooting article to explain that using entitled capacity can lead to CPU usage above 100 percent on AIX platforms.
    Salesforce case 00164529.
Fixed Defects:
  • On Solaris platform, some robots sent reboot alarms on restarting.
    Salesforce cases 00157066.
  • The probe was unable to generate data related to computer uptime.
    Salesforce case 00157375.
July 2015
What's New:
  • Upgraded support for factory templates.
June 2015
What's New:
  • Upgraded OpenSSL to version 1.0.0m.
  • Rolled back the alarm severity level changes made to the cdm version 5.30 to make these levels consistent with version 5.21.
    Refer to the
    Upgrades and Migrations
    section for more information related to alarm severity level changes.
May 2015
What's New:
  • Added support to subtract buffer/cache memory usage from the used physical memory for HP-UX and Solaris platforms.
Fixed Defect:
  • The probe did not save the monitor configurations for a clustered disk when configured through the Admin Console GUI.
    Salesforce case 00156473
April 2015
  • Added support for factory templates.
March 2015
What's New:
  • Added a Filesystem Type Filter field to specify regular expression and automatically select matching file system(s) to be monitored.
  • Added clustered environment monitoring to the Admin Console GUI of the probe.
  • Added an Enable Space Monitoring checkbox to allow the probe to monitor network disk usage metrics.
Fixed Defects:
  • Disk space alarms in custom profiles were generated with zero values when disks were not available or not mounted.
    Salesforce case
  • The probe generated messages with different severity levels for the same alarm in Windows and Linux environments.
    Salesforce case
  • The probe generated
    File system not available
    alarm in Linux and Solaris environments even if the file system was ignored.
    Salesforce case
March 2015
A new key QOS_DISK_TOTAL_SIZE has been added in fixed_defaults under disk in the Raw Configuration section of the probe. The key is supported for Windows, Linux and AIX platforms.
Salesforce case 00155861
Fixed defects:
  • The probe displayed the debug log even though the log level was set to 0.
    Salesforce case
  • The probe crashed on AIX platform when deployed for the first time.
    Salesforce case
February 2015
  • Fixed an issue where the probe was publishing some host names with non ASCII characters.
    Salesforce case
    00150465, 00153872
  • Two new Metrics QOS_IOSTAT_KRS and QOS_IOSTAT_KWS have been added on Linux platform and four new Metrics QOS_IOSTAT_RS, QOS_IOSTAT_WS, QOS_IOSTAT_KRS and QOS_IOSTAT_KWS have been added on AIX platform.
    These new Metrics are configurable only through Admin Console GUI.
February 2015
Fixed Defects:
  • The probe was generating false boot alarms.
    Salesforce case
    00148483, 00149480, 00137376, 00150365, 00146355, 00148673, 00148121, 00148737
  • Warning messages were shown in logs.
    Salesforce case
    00151892, 00150149
  • Incorrect alarm messages were shown in logs for CPU data.
    Salesforce case
January 2015
What's New:
  • Added the device iostat monitoring functionality for Linux, Solaris, and AIX platforms through the Infrastructure Manager GUI from CA UIM 8.0 onwards. This feature is configurable through the Raw Configuration Section only.
  • Added the Regular expression feature in the Custom Tab for custom local disk (for Windows platform) and custom local and NFS (for Linux, Solaris and AIX platforms). This feature is configurable through the Infrastructure Manager GUI only.
  • For making the Device Id of shared drive and local drive identical, a key allow_remote_disk_info has been introduced in the Raw Configuration section.
    Salesforce case
Fixed Defects:
  • The Device Id and Metric Id were missing for QOS and alarms when file system was mounted on Linux through CIFS.
    Salesforce case
  • On restarting, the probe was unable to mark CIFS drive as network drive and hence generated wrong Device Id and Metric Id.
December 2014
What's New:
  • New QoS metrics for aggregated inbound/outbound/total traffic for all the network cards on a server.
  • New disk metrics for monitoring disk size and disk read/write throughput, as well as system and user memory utilization.
    These new features are supported on Windows, Linux, and AIX platforms and are configurable only through Admin Console GUI.
  • We now support extended hostnames (more than 8 characters) for HP-UX 11i v2 or later.
    Salesforce case 00136356
October 2014
Fixed Defects:
  • Probe was suppressing all alarms for different iostat metrics. Now, a different suppression key is used for different iostat alarms of a given device.
    Salesforce case
    User has to manage the already suppressed alarms manually.
  • Probe was not generating QoS for any iostat metric when the Set QoS Source to robot name instead of computer hostname option is selected in the controller probe.
    Salesforce case
    PPM version 2.35 or later is required for these fixes to work as the iostat feature is configurable only through Admin Console GUI.
July 2014
  • Added support for z/Linux Operating System.
June 2014
  • Fixed an issue of QoS definition which were getting generated even if the respective QoS messages were inactive.
March 2014
What's New:
  • Device iostat monitoring functionality for Linux, Solaris, and AIX platforms through Admin Console GUI from NMS 7.5 onwards.
  • Support for monitoring the CIFS (shared Windows disk mounted on Linux) and GFS (clustered environment disk) file systems.
March 2014
  • Fixed the issue of alarms, which are generated through CPU custom profile and the cpu_total profile are having same metric id though having different suppression key.
February 2014
  • Fixed a defect for storing the password in encrypted format while mapping a new shared disk. Earlier the probe was storing password in clear text format. You can delete and then map again the existing shared disks for encrypting their passwords.
  • Fixed a defect of wrong subsystem Id when the probe is deployed on Linux environment. Earlier the probe was using subsystem Id of 3.3.xx series, by default, which is reserved for the nas probe. Now it is using 1.1.xx series of subsystem Id, by default.
January 2014
  • Fixed erroneous defects of the probe defaults
October 2013
  • Fixed a defect related to erroneous missing D drive alarms.
October 2013
  • Fixed a defect by removing extra logs, which are being logged by the probe.
  • Updated default configuration of the probe.
September 2013
  • Fixed an issue of sending a false alarm when cluster disk is out of scope.
  • Added fix to issue related to when edit alarm message show 0% threshold for memory alert.
  • Fixed a defect causing default values for low and high thresholds of 'Disk usage change and thresholds' are coming incorrect.
July 2013
  • Added fix to issue related to When editing CDM disk usage values, percentage jumping to MB.
  • Fixed a defect causing probe to use 100% CPU in case of hot adding a CPU in a Linux VM.
May 2013
  • Fixed a defect to set the threshold to 0.
  • Added a Timeout feature to overcome hang situations for NFS.
  • Fixed an issue where CDM sent large uptime in case windows performance monitor returns a negative value.
  • Fixed a defect where cdm clear message does not contain disk name.
April 2013
  • Added functionality for calculating CPU related statistics calculations considering LPAR in AIX.
  • Added functionality to monitor space for windows share.
  • Added target override for memory based QoS.
June 2012
  • Fixed an issue where CDM does not alarm on stale filesystems.
  • Corrected System Load Clear alarm text
March 2012
  • Fix default setting for NFS space check.
August 2011
  • Fixed internationalization defects. Changed share authentication test order to 'user/password', 'impersonation', 'implicit'. Fixed percent / inode conversion integer overflow situation on disk profile configuration.
  • Alarm message variable cleanup.
  • Changed text of processor queue length / system load alarm checkbox, including 'Alarm on' to clarify its use.
  • Added 'type' variable for cpu and memory alarm situations.
  • Fixed default alarm assignment on new custom cpu profile.
  • Boot alarm fix.
  • Fixed incorrect cluster disk alarm source introduced in version 4.43.
  • Added option to allow QoS source as target name where appropriate.
  • Service Oriented Configuration uninstall section issue fixed.
  • Added 'label' variable for windows disk alarms.
  • Fixed source and target for QOS_COMPUTER_UPTIME Quality of Service message to be consistent with the source and target of other Quality of Service messages.
  • Fixed cpu usage calculations for Quality of Service measurements when QoS Interval multiple larger than 1.
  • Fixed swap Quality of Service message for situations where swap size is 0.
  • Made probe permission consistent between platform sections in the package.
  • Corrected individual CPU calculations for alarms.
  • Fixed problem detecting change in number of active cpus on Solaris systems.
  • Fixed an issue where Previous cpu list is still exist in cases of detecting change in number of active cpus on Solaris systems
June 2011
  • Added fixes to web-based Service Oriented Configuration.
  • Fixed the QoS interval reported when using interval multiples.
  • Fixed problem with 0 last values in clear alarms.
  • The 0-paging is no longer interpreted as unable to fetch paging data on Solaris.
January 2011
  • Added support for internationalization.
  • Added support for reading alarm tokens from cfg.
  • Added support for Web-based Service Oriented Configuration (SOC).
December 2010
  • Modified the caption for field "Send short QoS source".
September 2010
  • Added support for localized alarm messages.
  • Added support for separate polling intervals for alarms and QoS.
  • Added support to configure target for Total CPU QoS.
  • Added support to send QoS source as short name (For Windows) or full name (For Linux).
  • Added support to ignore filesystems by giving regular expression.
  • Added a user interface to configure default values for discovered disks.
  • Added code to remove white space from all sections.
  • Added fix for memory leak.
September 2010
  • Enhanced the probe to use /proc/mounts on Linux systems.
  • CPU Alerting support for User, System, Wait, Idle.
June 2010
  • Active state of disk missing alarm read from default disk settings.
  • Added support for sending alarms only after the required samples are received.
May 2010
  • The 'ignore_filesystem' and 'ignore_device' are now also implemented for Windows systems.
  • Fixed the issue where custom disk profile uses the percent/MB setting from the global profile.
March 2010
  • Added support for extended NIS database information.
  • Modified for easier upgrade in cloud environment; when cluster disk is discovered, a local profile for the disk will be used as default configuration for the cluster disk.
  • Fixed the disk samples problem also for cluster disks.
  • Added support for custom profiles.
  • Added support for 'nfs_space_check' key in the default disk parameter section
February 2010
  • Fixed number of samples for disk monitoring not being read properly.
September 2009
  • Added support for Linux systems with glibc 2.2.
September 2009
  • Fixed CPU data gathering issue on AIX systems.
  • Fixed CPU data gathering issue on TRU64 systems.
  • Fixed upgrade problem with QoS values for memory paging.
September 2009
  • Multi CPU difference calculation is corrected.
June 2009
  • Solaris: Fixes error situation that could occur if a parse error happens in the first sample collected.
  • Solaris: Fixes parsing problem on 128 cpu systems.
  • Removed support for HP-UX 11.00
  • AIX: Fixes parsing problem with vmstat output causing paging value errors.
  • AIX: Suppressing internal alarm for initial memory data collection.
  • CPU multi diff test for clear alarm fixed so that clear works for this alarm situation even if the CPU multi max alarm check is not enabled.
  • No initial clear on disabled checkpoints.
  • Using default disk profile for discovered cluster disks.
  • Extended cluster support.
  • Added support for Windows on Itanium 2 systems (IA64).
May 2009
  • Fixed GUI startup problem for AIX version 6.
March 2009
  • Rebuild following NimBUS library fixes.
December 2008
  • Added connection_status callback function to support improved share status information. Implemented Ctrl+S in configuration tool to save window setup.
  • Renamed Processor Queue Length to System Load for UNIX/Linux.
    The same Quality of Service table (Processor Queue Length) is still used.
  • Modified Processor Queue Length calculation for Windows - the Queue length is now divided by the number of processors.
  • Enabled decimal point use for System Load alarm threshold and Quality of Service messages.
  • Changed usage display to convert to appropriate unit in disk table.
  • Added "rebooted" alarm option and alarm message.
  • Added the following alarm variables:
    • (for all) robotname, hostname.
    • (for disk) size_mb, size_gb, free_mb, free_gb, free_pc, limit_mb, limit_gb, limit_pc.
    • (for inodes) total_num, free_num, free_pc, limit_num, limit_pc.
  • Fixed disk_history problem with hidden disks.
  • Added option for sending Quality of Service message on network disk availability.
  • Added QoS for network disk availability.
  • Added option to monitor disk usage change.
  • Added log size option
October 2008
  • Enabled inode threshold configuration for deactivated probe.
  • Updated OS type recognition to be able to detect Windows Vista and Windows 2003 Server correctly.
  • Fixed inode history initialization for discovered disk.
  • Fixed share name handling.
  • Modified configuration tool to present updated message list for Queue Length alarm message.
  • Added sanity check for interval and sample values.
  • Corrected reading of default settings for inode QoS and use of percentage.
  • Corrected configuration tool alarm coloring on disk configuration as the coloring did not exactly represent probe alarming behavior.
  • Added the option to gather memory paging QoS series both in kilobytes per second as well as pages per second.
For version 3.72 and higher of this probe, NimBUS Robot version 3.00 (or higher) is a prerequisite. You are advised to carefully read the document "Upgrading the NimBUS Robot" before installing/upgrading.
September 2008
  • Corrected handling of Windows disk quotas.
May 2008
  • Fixed alarm message problem with missing network disks.
April 2008
  • Fixed deadlock situations for AIX_5, SOLARIS_8_sparc and TRU64.
  • Fixed: Interchanged memory and disk data-collections intervals.
March 2008
  • Modified logic to determine when clear alarm should be sent for nfs mounted file systems.
  • When a new disk is detected the probe will do a full restart to correctly initiate the disk. UNIX: Added monitoring of inodes on filesystems.
    Linux systems with ReiserFS filesystems may show 0 inodes (the same result should be visible with the command 'df -i').
January 2008
  • Windows: Added sanitycheck on cpu data.
  • HP-UX: modified calculations of swap space usage.
  • Modified QOS table name for memory paging when paging is calculated in pages per second. In previous versions QOS_MEMORY_PAGING was used for memory paging regardless if the calculations where done in kilobytes per second or pages per second. Now QOS-MEMORY_PAGING_PGPS will be used when pages per second is specified.
    Users already using this option old data may need to be moved to the new table and that SLA's and SLO's may need to be modified.
October 2007
  • UNIX: Added new versions to supported platform list:
  • HPUX_11: 32bit (PA-RISC)
  • LINUX: 32bit (Glibc >=2.3)
  • SOLARIS_10: 32bit (x86) 3.42
  • Additional logging for new and missing disks.
May 2007
  • AIX: Fix bug which caused physical memory information in the get_info callback to be incorrect.
February 2007
  • AIX: Added support for flag 'mem_buffer_used' in setup. If set to 'yes' the used memory will include the file cache and be consistent with the data from the 'vmstat' utility. Default is 'no' to be compatible with other platforms which to not report file cache as used memory as it is still available to programs.
  • Windows: Swap memory usage now reflects the pagefile usage.
  • Solaris 8 and higher: support for checking filesystems over 2TB.
January 2007
  • 3.25 display problems fixed
July 2006
  • AIX_5: Do not report buffer cache as used physical memory.
  • Fixed problem with reporting physical memory over 4GB on Windows 2000/XP/2003.
  • Fix on Solaris, Tru64 and AIX: Allocated a bigger buffer for CPU monitoring data. The maximum number of CPU's increased from 32 to 128.
July 2006
  • Updated discovery template.
June 2006
  • Tru64: Fix physical memory detection on systems with over 4GB RAM
June 2006
  • Added monitoring of physical memory usage.
  • Corrected memory statistics on HP-UX, Tru64 and SGI.
  • Added option to use pages/second as unit for paging instead of Kilobytes/second.
    Changing this may upset your QoS series.
  • Added new discovery template.
  • Added recognition of local file systems without drive letter on Windows XP and Windows 2003 Server.
  • Enabled monitoring of disk space usage of network file system (NFS).
    Enabling this might cause slow operation of the probe when there are network problems.
  • Linux: Fix error finding paging data on 2.6 kernels. Also changed counter so that only swap paging is counted, not other VM related IO.
May 2006
  • Linux: Fix detection of installed physical memory over 4GB.
  • Unix: Utility calling routine changed to send a SIGKILL to the child process directly when the child needs to be stopped. Eliminates the need for a separate SIGCHLD handler to avoid zombie process.
February 2006
  • Fixed bug where a specific configuration on multi-cpu systems would cause a segmentation fault.
April 2005
Probe Specific Hardware Requirements
The cdm probe is installed on systems with the following minimum resources:
  • Memory: 2-4GB of RAM. The OOB configuration of the probe requires 256 MB of RAM.
  • CPU: 3 GHz dual-core processor; 32-bit or 64-bit
Probe Specific Software Requirements
The cdm probe requires the following software environment:
  • CA Unified Infrastructure Management 8.0 or later
  • Robot 7.62 or later (recommended)
  • Probe Provisioning Manager (PPM) probe version 2.38 or later (required for Admin Console)
  • (From version 6.10)
    ci_defn_pack 1.39 or later on the primary hub robot (with the
    This is required to view the metrics on the USM portal. Restart the
    probe after you deploy
  • (From version 6.10)
    mps_language_pack 8.56 or later on the primary hub robot (with the
    This is required to view the metric type on the Admin Console. Restart the
    probe after you deploy
  • Java JRE version 6 or later (required for Admin Console)
  • (From version 5.80)
  • VS2010 redistributable package
    • Click here to download the package for 32-bit operating systems.
    • Click here to download the package for 64-bit operating systems or Windows systems with 64 or more core CPUs.
    : A dependency error occurs if you do not install the VS 2010 package when you upgrade to cdm probe version 5.70 and later.
  • Configure the probe to generate the SAR (System Activity Report) using the current values of the network inbound, outbound, and aggregate traffic monitors.
The probe also requires the following package for iostat monitoring. For more information, refer the official
  • The sysstat package (Linux and Unix platforms)
  • (From version 6.00)
    On Linux platforms, the probe requires
    sysstat 9.1.2
    for disk latency metrics.
  • To collect network traffic information, install the SYSSTAT package and test the command
    sar -n DEV
(Version 5.90) Enable FIPS Encryption
Before you deploy the probe version 5.90 on your Infrastructure Manager (IM), you must enable the FIPS encryption on the system where the probe is configured.
You cannot configure the probe from any Admin Console (AC) interface on a FIPS encryption enabled environment.
Follow these steps on a Windows system:
  1. Click
    Start > Run
    , and type
  2. On the Local Group Policy Editor, navigate to
    Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
  3. Enable the following policy:
    System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing
    FIPS Compliant encryption.jpg
  4. Click
    , and
  5. Deploy or upgrade to cdm version 5.90.
(Version 5.90) Probe Specific Changes After Upgrade
The probe supports AES-128 bit encryption and decryption. To enable this feature in your Infrastructure Manager (IM), set the
environment variable to one of the following values in the controller probe:
  • AES_128_COMPAT
  • If you do not set any value of the environment variable, then the probe uses
    encryption and decryption, by default.
  • Set this value in all the robots where the cdm probe is configured.
  • Restart the
    Nimsoft Robot Watcher
    service after you set the environment variable.
  • The probe fails to start if you provide incorrect values for the environment variable. CA does not recommend you to change this value after you set it once.
    However, if your probe still fails to respond, see
    Known Issues and Workarounds
    section for more information.
Installation Considerations
To enable the QoS metric QOS_PROC_QUEUE_LEN for per CPU, add a key
with value as
under the CPU section through the
Raw Configuration
interface. The probe then calculates the system load on Linux, Solaris, and AIX as Load or Number of CPUs.
For AIX 5.x users
that the probe uses for memory collection routines. The package is available in the bos.perf.perfstat and bos.perf.libperfstat file-sets. To verify that you have the correct file-sets, execute the following command:
# lslpp -l | grep perf
The system displays the following output depending on the installed versions. If you do not see bos.perf.libperfstat and bos.perf.perfstat in the output from the command, install those files.
bos.perf.libperfstat COMMITTED Performance Statistics Library
bos.perf.perfstat COMMITTED Performance Statistics
Prerequisites for a Non-root User on AIX Platform
A non-root user must have full privileges on the Nimsoft folder and should perform any one of the following procedures to get the CPU data using the cdm probe, on AIX platforms.
  • Add the non-root user to
  • Provide (r-x) privilege to the non-root user on all the commands used by the
Add the Non-root User to adm Group
Follow these steps:
  1. Kill all the Nimsoft processes.
  2. Add the user to the
    group using the following command.
    usermod -G adm <username>
  3. Open a new terminal to get the new privileges.
  4. Restart the robot and the probe.
Provide (r-x) privilege to the Non-root User
Follow these steps:
  1. Navigate to the
  2. Run the following command.
chmod 555 sadc
Upgrades and Migrations
Consider the following points for upgrades and migration:
  • (version 6.71)
    Template Migration steps for CDM Probe:
    CDM (Enhanced) MCS template 6.70 to CDM (Enhanced) MCS template 6.71.
  • (version 6.70)
    Template Migration steps for CDM Probe:
    CDM (Enhanced) MCS template 6.60 to CDM (Enhanced) MCS template 6.70.
    CDM (Enhanced) MCS template 6.61 (6.60-HF1) to CDM (Enhanced) MCS template 6.70.
  • (version 6.60)
    Template Migration steps for CDM Probe:
    CDM (Enhanced) MCS template 6.50 to CDM (Enhanced) MCS template 6.60.
    CDM (Enhanced) MCS template 6.51 (6.50 HF1) to CDM (Enhanced) MCS template 6.60.
    CDM (Enhanced) MCS template 6.52 (6.50 HF2) to CDM (Enhanced) MCS template 6.60.
    To create fresh MCS profiles using the MCS template 6.60, as prerequisite you must have CDM 6.60 probe in your archive or deployed on the robot.
  • (version 6.50)
    Template Migration steps for CDM Probe:
    CDM (Enhanced) MCS template 6.42 to CDM (Enhanced) MCS template 6.50.
  • (version 6.42)
    To upgrade from the cdm 6.33 mcs templates to the cdm 6.42 version, you must first upgrade the mcs templates to cdm 6.34 and then to 6.42.
  • (version 6.40)
    Upgrade the
    to version 1.52 to view ci_type for the new metrics.
  • (version 6.40)
    Upgrade the ppm probe version 3.50 to view subsystem ID’s (default) for the new metrics.
  • (version 6.40)
    Upgrade to the latest wasp language pack to view the correct metric names on the USM portal. Restart the wasp probe after you deploy the
  • On upgrade, the existing monitoring profiles for cluster disks are overwritten with new profiles.
  • (version 5.6x)
    messages are available only on fresh installation of the probe version 5.6. If you upgrade the probe from previous versions to 5.6, you must drag and drop these messages from the
    Message Pool
    list under the
    Setup > Message definitions
  • (version 5.6x)
    The variable '$processes' is added from probe version 5.6 and later.
  • (5.50 or later)
    You can view the metrics that are available in the cdm probe version 5.50 and later on the USM portal. Deploy the
    version 1.08 or later and restart the
    . You can install the
    probe here.
  • (5.00 or later)
    When upgrading the cdm probe from a previous version to version 5.00, the new metrics are not visible on the Admin Console GUI. Install the PPM probe version 3.12 or later on the hub robot to view the new metrics.
  • The cdm probe versions earlier than version 5.30 have different severity levels for the same alarm on different platforms. From version 5.30, the severity level is same for an alarm on different platforms. These changes have been rolled back in the cdm version 5.41. This version has the same configuration as the versions earlier than 5.30 for the alarm severity levels. The following table summarizes the changes in the alarm severity levels on different versions of cdm.
Alarm Name
Severity Level earlier than version 5.30
Severity Level on upgrading to version 5.30, 5.31 or 5.40 (Overwritten on Upgrade)
Severity Level with version 5.41 (Not Overwritten on Upgrade)
Upgrading to version 5.41 has no impact on your existing probe configuration. Contact
CA UIM support
for a customized probe package if you have one or more of the following configurations:
  • Probe version 5.30, 5.31, or 5.40
  • Severity levels are already changed on upgrading to any of these versions
  • You want to roll back to severity levels of the version prior to 5.30
CDM MCS template Migration 5.80 to 6.42 Enhanced (Along with Different UIM Versions)
Recommended CDM Migration Path:
Legacy 5.80 (UIM 8.5.1) -> Legacy 6.30 (UIM 8.5.1) -> (UIM 9.0.2) -> Legacy 6.34 (UIM 9.0.2) -> (UIM 9.0.2 with MCS 9.02hf6 or UIM 9.1.0 or UIM 9.2.0) -> Legacy 6.42 (UIM 9.0.2 with MCS 9.02hf6 or UIM 9.1.0 or UIM 9.2.0) -> Enhanced 6.42 (UIM 9.0.2 with MCS 9.02hf6 or UIM 9.1.0 or UIM 9.2.0) -> Enhanced 6.50 (UIM 9.0.2 with MCS 9.02hf6 or UIM 9.1.0 or UIM 9.2.0 or UIM 20.1)
Different Template Version and Corresponding Packages:
Serial Number
Template Name
6.42 Corresponding Enhanced Template Name
6.42 Corresponding Enhanced Template Version
CPU Monitor
CPU Monitor (Enhanced)
Memory Monitor
Memory Monitor (Enhanced)
NIC Monitor
NIC Monitor (Enhanced)
Setup CDM
Setup cdm (Enhanced)
Default Disk(s)
Default Disk(s) (Enhanced)
There is no corresponding Enhanced profile. Similar configuration can be achieved by using Default Disk(s) (Enhanced) and Disk(s) (Enhanced) child profile.
Iostat (Enhanced)
Iostat Devices
Disk IO Monitors
Disk IO Monitors (Enhanced)
Shared Disk(s)
No Corresponding Enhanced template
Additional Information:
From CDM 5.80 to 6.30:
Migration is not supported for Disk template from cdm 5.80 to cdm 6.30. If you are using cdm 5.80, you must delete Disk profiles and must re-create child template for Default disk. You can migrate other templates such as CPU and memory.
In case of upgrading UIM like 9.0.2 to 20.1, auto migration should be disabled in MCS. Please check the probe documentation before enabling it. You can have multiple monitoring probes releases between any 2 UIM released versions, which can create migration failure. For example between UIM 9.0.2 to 20.1, there are many CDM releases like 6.30, 6.33, 6.34, 6.42, 6.50 and migration of MCS template is only supported with pre-defined path.
Known Issues and Workarounds
  • Few fields are not supported in the Setup CDM Enhanced template
    Below are the few fields that are not supported in the Setup CDM Enhanced template, but are supported in the legacy template. Enabling these can have impact on the Monitoring data.
    • General Alarm and QOS Metrics Settings -> Send Alarm on Each Sample
      If you enable this field, there is no impact on the Monitoring data.
    • General Settings for CPU Monitoring -> Set QoS Target as Total
      If you enable this field, you cannot see some QoS messages for the CPU monitoring.
    • General Settings for CPU Monitoring -> Number of Top CPU-consuming Processes in Alarm
      If you enable this field,there is no impact on the Monitoring data.
    • General Settings for Memory Monitoring -> Set QoS Target as Memory
      If you enable this field, you cannot see some QoS messages for the Memory monitoring.
  • Disk Free alarm monitor is missing in the AC interface.
  • (On Version 6.41)
    After upgrading the probe from version 6.34 to version 6.41, the following metrics show discontinued data on the USM metrics graphs:
  • (On Version 5.90)
    On your IM on a Windows system, sometimes the probe GUI might not open or might not respond. To fix this, create an environment variable on the Windows system from where you are accessing the IM.
    Follow these steps:
    1. Right-click on
      My Computer
      and select
    2. Click
      Advanced System Settings
      to open the
      System Properties
    3. Click
      Environment Variables
      , and then click
      to add a new variable.
    4. Specify the following details for the
      New User Variable
      • Variable name
      • Variable value
        : AES_128_COMPAT
    5. Click
      and exit from System Properties.
    6. Restart the
      Nimsoft Robot Watcher
      service after you set the environment variable.
  • (version 5.80-MC)
    The probe creates multiple duplicate perspective ids when installed on multiples systems using the same shared file system.
  • The probe might reboot the server when VS2010 redistributable package is installed.
  • The probe generates incorrect device ID for remote disks using the robot's hostname. Set the
    in the
    Raw Configuration
    interface to
    to generate the device ID from the remote disk hostname. The key is available on cdm version 5.10 and later.
  • The 32-bit versions of this probe are unable to monitor terabyte (TB) sized disks.
  • On Windows, the first interval data is not retrieved for the top CPU consuming processes when the probe starts executing. From the second interval, the probe displays the alarm correctly.
  • When running this probe in a clustered environment, setting the flag
    causes problems with the disks that appear and disappear with the resource groups. This flag is unavailable is only available through raw configuration or by directly modifying the cdm.cfg file.
  • The probe retrieves the first eight characters of the system hostname when deployed on HP-UX 11i v1 or earlier. For example, if your system hostname is hpuxsys123, then the probe returns hpuxsys1. The probe uses this trimmed hostname as the QoS target.
  • (version 4.8x)
    The UMP GUI displays the consolidated list of the iostat QoS metrics for all the monitored devices. Each QoS name contains the device name for locating the device-specific QoS.
  • (version 4.0x)
    The behavior changes when running in a cluster together with cluster probe version 2.2x. The probe receives information about cluster disk resources from the cluster probe. The probe then creates monitoring profiles for these based on the 'fixed_default' settings. The new profiles are automatically registered with the cluster probe to ensure continuous monitoring on cluster group failover. The cluster group is used as Alarm and Quality of Service source instead of the cluster node.