Nimsoft Monitor cdm Release Notes -...

cdm Release Notes All series

Nimsoft® Monitor™

CA Nimsoft Monitor Copyright Notice

This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between you and CA governing your use of the CA software to which the System relates (the “CA Software”). Such agreement is not modified in any way by the terms of this notice.

Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy.

The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS SYSTEM “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The manufacturer of this System is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Legal information on third-party and public domain software used in the Nimsoft Monitor solution is documented in Nimsoft Monitor Third-Party Licenses and Terms of Use (http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html).

http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html

Contact CA

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

Send comments or questions about CA Technologies Nimsoft product documentation to [email protected].

To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/support

mailto:[email protected]

http://ca.com/docs

Contents 5

Contents

Chapter 1: cdm General Overview 7

Chapter 2: Requirements 9

Hardware Requirements .............................................................................................................................................. 9

Software Requirements ............................................................................................................................................... 9

Supported Platforms .................................................................................................................................................... 9

Chapter 3: Considerations 11

Installation Considerations ......................................................................................................................................... 11

Chapter 4: Fixed Defects 13

Known Issues .............................................................................................................................................................. 13

Revision History .......................................................................................................................................................... 14

Chapter 1: cdm General Overview 7

Chapter 1: cdm General Overview

Monitors CPU, disk, and memory. The probe lets you define parameters for detecting performance bottlenecks.

The probe operates in two modes:

■ Generate alarms: Based on configured threshold values it generates alarms to take corrective actions immediately.

■ Generate trending data: The trending data is sent as Quality of Service (QoS) data to the data_engine probe. This facilitates capacity planning for the monitored system. For example, you can see how disks are filling up over time and plan batch jobs based on CPU utilization.

Chapter 2: Requirements 9

Chapter 2: Requirements

This section contains the requirements for the cdm probe.

This section contains the following topics:

Hardware Requirements (see page 9) Software Requirements (see page 9) Supported Platforms (see page 9)

Hardware Requirements

The cdm probe should be installed on systems with the following minimum resources:

■ Memory: 2-4 GB of RAM. Probe's OOB configuration requires 256 MB of RAM.

■ CPU: 3 GHz dual-core processor, 32-bit or 64-bit.

Software Requirements

The cdm probe requires the following software environment:

■ Nimsoft Monitor Server 5.1.1 or later.

Note: NMS 7.5 or later and PPM 2.35 or later is required for iostat monitoring.

■ Nimsoft robot version 5.23 or later.

■ Java Virtual Machine version 1.6 or later.

Supported Platforms

The cdm probe is supported on the same set of operating systems and databases as the Nimsoft Monitor Server solution. Please refer to the:

■ Nimsoft Compatibility Support Matrix for the latest information on supported platforms.

■ Support Matrix for Nimsoft Probes for additional information on the cdm probe.

http://support.nimsoft.com/downloads/doc/NMSCompatibility_SupportMatrix_current.pdf

http://support.nimsoft.com/downloads/doc/Platform_Support_Availability_current.pdf

Chapter 3: Considerations 11

Chapter 3: Considerations


Installation Considerations (see page 11)

Installation Considerations

Note for AIX 5.x users:

The memory gathering routines use libperfstat , which must be installed. It is found in the bos.perf.perfstat and bos.perf.libperfstat filesets. To verify that you have the correct file-sets installed, you can run:

# lslpp -l | grep perf

This should give you something like this (versions may differ):

bos.perf.libperfstat 5.1.0.35 COMMITTED Performance Statistics Library

bos.perf.perfstat 5.1.0.35 COMMITTED Performance Statistics

If you do not see bos.perf.libperfstat and bos.perf.perfstat in the output from the command, you will need to install those files.


Chapter 4: Fixed Defects


Known Issues (see page 13) Revision History (see page 14)

Known Issues ■ The 32-bit versions of this probe is not able to monitor TB size disks.

■ When running this probe in a clustered environment, you should not set the flag /disk/fixed_default/active=yes since this will cause problems with the disks that appear and disappear with the resource groups. This flag is unavailable through the GUI, and only reached through raw configure method or by directly modifying the cdm.cfg file.

■ Version 4.0x: Changed behavior when running in a cluster together with cluster probe version 2.2x. The probe will receive information about cluster disk resources from the cluster probe and create monitoring profiles for these based on the 'fixed_default' settings. These profile 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. Note: On upgrade, old monitoring profiles for the cluster disks are overwritten with the new ones.

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

Revision History

14 cdm Release Notes

Revision History This section describes the history of the revisions for this probe.

Date Description State Version

July 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: 00139484).

Note: 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: 00137858)

Note: PPM version 2.35 or later is required for these fixes to work as the iostat feature is configurable only through Admin Console GUI.

GA 4.91

June 2014 New Feature:

■ Added support for zLinux Operating System.

4.90

March 2014 ■ Fixed an issue of QoS definition which were getting generated even if the respective QoS messages were inactive.

4.81

March 2014 New Features:

■ Added the device iostat monitoring functionality for Linux, Solaris, and AIX platforms through Admin Console GUI from NMS 7.5 onwards.

■ Added support for monitoring the CIFS (shared Windows disk mounted on Linux) and GFS (clustered environment disk) file systems.

4.80

Feb 2014 ■ Fixed the issue of alarms, which are generated through CPU custom profile and the cpu_total profile are having same met-id though having different suppression key.

4.78

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

4.77

Oct 2013 ■ Fixed erroneous defects of the probe defaults 4.76

Oct 2013 ■ Fixed a defect related to erroneous missing D drive alarms. 4.75

Revision History



Sept 2013 ■ Fixed a defect by removing extra logs, which are being logged by the probe.

■ Updated default configuration of the probe.

4.74

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

4.73

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

4.72

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

4.71

Jun 2012 ■ 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.

4.70

Mar 2012 ■ Fixed an issue where CDM does not alarm on stale filesystems.

■ Corrected System Load Clear alarm text

4.60

Aug 2011 Fix default setting for NFS space check. 4.55

Revision History



Jun 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 Configration 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 consitent 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

4.54

Jan 2011 ■ Added fixes to web-based Service Oriented Configuration.

■ Fixed the QoS interval reported when using interval multiples.

■ Fixed problem with 0 last calues in clear alarms.

■ The 0-paging is no longer interpreted as unable to fetch paging data on Solaris.

4.44

Revision History



Dec 2010 ■ Added support for internationalization.

■ Added support for reading alarm tokens from cfg.

■ Added support for Web-based Service Oriented Configuration (SOC).

4.43

Sep 30 2010 Modified the caption for field "Send short QoS source". 4.41

Sep 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 whitespace from all sections.

■ Added fix for memory leak.

4.40

Jun 2010 ■ Enhanced the probe to use /proc/mounts on Linux systems.

■ CPU Alerting support for User, System, Wait, Idle.

4.30

May 2010

■ Active state of disk missing alarm read from default disk settings.

■ Added support for sending alarms only after the required samples are received.

4.22

Mar 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. The probe should now use the active setting of the missing.

4.21

Revision History



Feb 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 confiugration 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

4.20

Sep 30 2009 Fixed number of samples for disk monitoring not being read properly. 4.11

Sep 21 2009 Added support for Linux systems with glibc 2.2. 4.10

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

4.05

Jun 2009 Multi CPU difference calculation is corrected. 4.04

May 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 diabled checkpoints.

■ Using default disk profile for discovered cluster disks.

■ Extended cluster support.

■ Added support for Windows on Itanium 2 systems (IA64).

4.03

Mar 2009 ■ Fixed GUI startup problem for AIX version 6. 3.82

Dec 2008 ■ Rebuild following NimBUS library fixes. 3.81

Revision History



Oct 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. Note that 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

3.80

Revision History



Sep 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 colloring did not exactly represent probe alarming bahaviour.

■ Added the option to gather memory paging QoS series both in kilobytes per second as well as pages per second.

■ Note: For version 3.72 and higher of this probe, NimBUS Robot version 3.00 (or higher) is a prerequesite. You are advised to carefully read the document "Upgrading the NimBUS Robot" before installing/upgrading.

3.72

May 2008 Corected handling of Windows disk quotas. 3.54

Apr 2008 Fixed alarm message problem with missing network disks. 3.53

Mar 2008 ■ Fixed deadlock situations for AIX_5, SOLARIS_8_sparc and TRU64.

■ Fixed: Interchanged memory and disk data-collections intervals.

3.52

Jan 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. Note: Linux systems with ReiserFS filesystems may show 0 inodes (the same result should be visible with the command 'df -i').

3.51

Oct 2007 ■ 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. Note that for 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.

3.43

Revision History



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

3.42

Feb 2007 AIX: Fix bug which caused physical memory information in the get_info callback to be incorrect.

3.32

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

3.31

Jul 19 2006 3.25 display problems fixed 3.26

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

3.25

Jun 20 2006 Updated discovery template. 3.23

Jun 2 2006 Tru64: Fix physical memory detection on systems with over 4GB RAM 3.22

May 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. Note that 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). Note that 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.

3.21

Revision History



Feb 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 proce

3.17

Apr 2005 Fixed bug where a specific configuration on multi-cpu systems would cause a segmentation fault.

3.12

Nimsoft Monitor cdm Release Notes -...

Documents

Transcript of Nimsoft Monitor cdm Release Notes -...