Nimsoft Monitor cdm Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/cdm/4.5/cdm.pdfNo part of...

cdm Guide v4.5 series

Nimsoft® Monitor™

Legal Notices Copyright © 2012, Nimsoft Corporation

Warranty

The material contained in this document is provided "as is," and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Nimsoft Corporation disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nimsoft Corporation shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should Nimsoft Corporation and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control.

Technology Licenses

The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license.

No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Nimsoft Corporation as governed by United States and international copyright laws.

Restricted Rights Legend

If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is delivered and licensed as "Commercial computer software" as defined in DFAR 252.227-7014 (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR 52.227-19 (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft Corporation’s standard commercial license terms, and non-DOD Departments and Agencies of the U.S. Government will receive no greater than Restricted Rights as defined in FAR 52.227-19(c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR 52.227-14 (June 1987) or DFAR 252.227-7015 (b)(2) (November 1995), as applicable in any technical data.

Trademarks

Adobe®, Acrobat®, Acrobat Reader®, and Acrobat Exchange® are registered trademarks of Adobe Systems Incorporated.

Intel® and Pentium® are U.S. registered trademarks of Intel Corporation.

Java(TM) is a U.S. trademark of Sun Microsystems, Inc.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Netscape(TM) is a U.S. trademark of Netscape Communications Corporation.

Oracle® is a U.S. registered trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of the Open Group.

Contact Nimsoft

For your convenience, Nimsoft provides a single site where you can access information about Nimsoft products.

At http://support.nimsoft.com/, you can access the following:

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

■ Information about user communities and forums

■ Product and documentation downloads

■ Nimsoft Support policies and guidelines

■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about Nimsoft product documentation, you can send a message to [email protected].

http://support.nimsoft.com/

mailto:[email protected]

mailto:[email protected]

Contents 5

Contents

Chapter 1: cdm 4.5 7

Chapter 2: Documentation Changes 9

Chapter 3: Probe Deployment 11

cdm Prerequisites and Supported Platforms ............................................................................................................. 12

cdm Probe Deployment ............................................................................................................................................. 13

Deployment Using Infrastructure Manager ........................................................................................................ 13

Deployment Using Nimsoft Distribution Application .......................................................................................... 14

Probe Configuration Interface Installation ................................................................................................................. 14

Chapter 4: Configuration 15

Probe Configuration Interface .................................................................................................................................... 16

Single Computer Configuration ........................................................................................................................... 16

Multi-CPU Configuration ..................................................................................................................................... 31

Cluster Configuration .......................................................................................................................................... 45

How to Copy Probe Configuration Parameters .......................................................................................................... 60

Chapter 5: QoS Threshold Metrics 61

QoS Metrics ................................................................................................................................................................ 61

cdm Alert Metrics Default Settings ............................................................................................................................ 62

Chapter 6: Troubleshooting and FAQs 65

Guidelines for Sending Bug Reports for CDM ............................................................................................................ 66

Chapter 1: cdm 4.5 7

Chapter 1: cdm 4.5

This description applies to cdm probe version 4.5x. The Nimsoft CPU, Disk & Memory (cdm) probe monitors performance and load on critical system resources:

■ CPU

■ Disk

■ Memory

The cdm probe is included in the Basic Server, Application Server and all Vblock Packs. See Getting Started with Probes for more information on probe packs.

The probe operates in two modes:

■ Generates alarms based on configured threshold values

■ Generates trending statistics

The trending data is sent as Quality of Service (QoS) data to the data_engine probe.

This facilitates capacity planning for the monitored system so you can see how disks are filling up over time and plan batch jobs based on CPU utilization.

Chapter 2: Documentation Changes 9

Chapter 2: Documentation Changes

This table describes the version history for this document.

Version Date What's New?

4.5x November 2011 The following documentation updates have been made since the last release of this documentation:

■ Reorganized the content of this probe documentation.

■ QoS Threshold Metrics—Added this section with checkpoint metrics and benchmark data.


Chapter 3: Probe Deployment

The CPU, Disk and Memory Monitor (cdm) probe requires the Nimsoft Robot (controller) version 3.00 or newer.

More information:

cdm Prerequisites and Supported Platforms (see page 12) cdm Probe Deployment (see page 13) Probe Configuration Interface Installation (see page 14)

This section contains the following topics:

cdm Prerequisites and Supported Platforms (see page 12) cdm Probe Deployment (see page 13) Probe Configuration Interface Installation (see page 14)

cdm Prerequisites and Supported Platforms

12 cdm Guide

cdm Prerequisites and Supported Platforms

The cdm probe requires Nimsoft Robot (controller) 3.00 or newer.

You can deploy the cdm probe on the following platforms:

■ Windows: XP, 2003, Vista, Windows 7 and 2008 (32-bit or 64-bit)

■ Solaris Sparc: 8, 9, 10 (32-bit and 64 bit)

■ Solaris x86: 10

■ HP-UX: 11.1, 11.2, 11.3

■ Linux: Glibc 2.1 or higher for x86, Glibc 2.3 or higher for x86 64-bit and ppc 64-bit

■ AIX: 5.2, 5.3 for ppc 32-bit; 5.2, 5.3, 6.1 for ppc 64-bit

Note: The memory gathering routines on an AIX 5.x platform use libperfstat, which you must install. It is found in the bos.perf.perfstat and bos.perf.libperfstat filesets. To verify you have the correct filesets installed:

# lslpp -l | grep perf

This command should return information similar to the following (versions may differ):

bos.perf.libperfstat 5.1.0.35 COMMITTED Performance Statistics

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 then you need to install the filesets.

■ Tru64: 4, 5 alpha

■ SGI: IRIX 6.5

Notes:

■ The 32-bit versions of this probe are unable to monitor terabyte (TByte) sized disks.

■ When running this probe in a clustered environment you should not set the flat /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 or 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 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. Note that on upgrade, old monitoring profiles for the cluster disks are overwritten with the new ones.

cdm Probe Deployment


cdm Probe Deployment

There are two ways to distribute archive packages. You can distribute the package within Infrastructure Manager or use the standalone Nimsoft Distribution application.

Deployment Using Infrastructure Manager

There are two methods within Infrastructure Manager to distribute an archive package: drag and drop or right-click on a package name.

Note: The package must have a green box icon before you can distribute it to a machine. If the box icon is not green, you must download the package to the archive and have a valid license before distributing to a machine.

Drag and Drop Method:

1. Select a package name in the archive.

2. Drag and drop the package name to the domain/hub/robot.

A View Distribution Progress dialog box appears with detailed information about the distribution.

Note: You can minimize this dialog box and continue working in Infrastructure Manager within interfering with the distribution.

3. Click the Close Dialog button after distribution is finished.

Right-click Method:

1. Select a package name in the archive.

2. Right-click and select Distribute from the menu.

A Distribute dialog box appears.

3. Select the domain/hub/robot where you want to distribute the package, and click the Add button.

The domain/hub/robot name appears in the right column.

4. Click OK.

A View Distribution Progress dialog box appears with detailed information about the distribution.

Note: You can minimize this dialog box and continue working in Infrastructure Manager within interfering with the distribution.

5. Click the Close Dialog button after distribution is finished.

Probe Configuration Interface Installation

14 cdm Guide

Deployment Using Nimsoft Distribution Application

Packages can be deployed using the standalone Nimsoft Distribution application. This distribution method allows for the ability to create distribution tasks. A task is a profile containing information about what packages to distribute and the set of destination robots. See the Infrastructure Manager documentation for more information.

Probe Configuration Interface Installation

The CPU, Disk and Memory Monitor (cdm) probe configuration interface is automatically downloaded and installed by the Nimsoft Infrastructure Manager when the probe is deployed on a robot.


Chapter 4: Configuration

This section describes the configuration concepts and procedures for setting up the CPU, Disk and Memory Monitor (cdm) probe.

When configuring the cdm probe you will be directed into the Status tab. The status tab displays graphs of the CPU usage, Memory usage, and Paging activity, and a list of file systems being monitored.

You can configure the probe to monitor local disks as well as shared disks (cluster). When monitoring shared disks (such as NFS mounts) over low-performance or over-utilized lines, you may experience slow response times.

This probe can be configured using the probe configuration interface or by copying configuration parameters from another cdm probe (see the Infrastructure Manager documentation).

If quota is turned on for a disk on a Windows system, the size reported is the total size, and the free disk space is calculated after quota.

More information:

Probe Configuration Interface (see page 16) How to Copy Probe Configuration Parameters (see page 60)


Probe Configuration Interface (see page 16) How to Copy Probe Configuration Parameters (see page 60)

Probe Configuration Interface

16 cdm Guide


The CPU, Disk and Memory Monitor (cdm) probe configuration interface displays a screen with tabs for configuring sections of this probe. This probe can be set up in three types of environments: single computer, multi-CPU and cluster.

Setup

This tab allows you to set up the general preferences for this probe. There are tabs within this page that you can use to specify general, control properties and message definitions. A fourth tab (cluster) displays if the probe is running within a clustered environment.

Status

This tab allows you to set up high and low thresholds for the CPU, memory and paging activity on the filesystem you select.

Note: When you open the configuration interface, this is the default tab.

Multi CPU

This tab displays the alarm threshold and the CPU usage for the different CPUs in a multi-CPU configuration. You can specify the maximum threshold, CPU difference threshold and processors to display.

Note: This tab only appears when the cdm probe is running on a multi-CPU computer.

Advanced

This tab allows you to customize the Quality of Service messages,alarm on processor queue length, alarm on detected reboot, and paging measurements.

Custom

This tab lists any currently defined custom profiles. You can select one or more custom profiles if available. Custom profiles can be created for monitoring the CPU, disk or memory.

Single Computer Configuration

This section describes the cdm probe single computer configuration setup. The configuration GUI displays tabs for each section of the single computer configuration.

Note: You can update the information within the configuration pages by clicking the Update button.



Setup

Setup

This tab allows you to set up the general preferences for this probe. There are tabs within this page that you can use to specify general preferences, control properties and message definitions.

Setup General Preferences

This section allows you to configure the following:

Log level

Sets the level of detail written to the log file. Log as little as possible during normal operation, to minimize disk consumption.

Log size

Set the size of the probe's log file where probe-internal log messages are written. When this size is reached, the contents of the file are cleared.

Default: 100 KB

Send alarm on each sample

If selected, the cdm probe will generate an alarm on each sample. If not selected, the cdm probe waits for the number of samples (specified in the samples field of the Control properties tab) before sending the alarm.

The sample count is cleared on de-activation of the probe. For more details about the samples, see Setup Control Properties.

Note: The sample collected at the start of the probe is considered to be the first sample.

Default: Checkbox is selected.

Send short name for QoS source

If selected, sends only the host name. If not selected, sends the full host name with domain.

Allow QoS source as target

A number of QoS messages by default use the host name as their target. If selected, the target name is changed to be the same as the QoS source name.

Important: If the "Set QoS source to robot name" option is set in the controller you will get the robot name also as target.

Setup Control Properties

This page contains configuration settings to control:

■ How often the probe asks for data


18 cdm Guide

■ How many samples the probe should store for calculating values used to determine threshold breaches

This page is separated into three sections:

■ Disk properties

■ CPU properties

■ Memory & Paging properties

CPU Properties

This section of the control properties page configures the interval and samples for monitoring the CPU.

Example

The cdm probe gets the values from the performance counters (Windows). One value is fetched on each interval. If the interval is set to 1 minute and the number of samples is set to 5, the CPU utilization is the average for the last 5 minutes. If the interval is set to 5 minutes and the number of samples is set to 5, the CPU utilization is the average for the last 25 minutes.

This section contains the following fields:

Interval

The length of time between retrieving samples.

Samples

The number of samples the probe will keep in memory for average/threshold comparison.

Note: If you did not select the Send Alarm on each sample checkbox on the General tab, the probe waits for the number of samples (specified in this field) before sending the alarm.

QoS Interval (Multiple of "Interval")

Select the QoS interval. The number selected is multiplied by the Interval above to determine how often the QoS is sent.

Example: If the interval is set to 5 min and QoS interval is 2, then the QoS will be sent every 10 minutes.

Set QoS Target as 'Total'

If selected, the QoS for Total (individual as well as Average) will be changed to "Total." The default is the hostname.

QoS Target as 'Total'

Memory and Paging Properties



This section of the control properties page configures the interval and samples for monitoring the memory and paging.


Interval


Samples



QoS Interval



Setup Message Definitions

The cdm probe offers functionality to customize the messages sent whenever a threshold is breached. A message is defined as a text string with a severity level. Each message has a token that identifies the associated alarm condition.

This page contains two sections:

■ Message pool

■ Active messages

Message Pool

This section lists all messages with their associated message ID. Right click in the message pool window to create a new message, edit an existing message or delete an existing message.

Active Messages

This section contains tabs to allow you to associate messages with the thresholds. You can drag the alarm message from the message pool and drop it into the threshold field. The thresholds include:

CPU

High (error) and Low (warning) threshold for total CPU usage.


20 cdm Guide

High (error) threshold for individual CPU usage (alarms are sent when one of the CPUs in multi-CPU systems breaches the threshold).

CPU difference threshold (alarms are sent when the difference in CPU usage between different CPUs in multi-CPU systems breaches the threshold).

Disk

The thresholds for disks can be modified by double-clicking the disk-entries under the Status tab.

Memory

Depends on what memory view is selected in the memory usage graph, where you may toggle among three views (see the Status tab).

■ Memory usage

High (error) and Low (warning) threshold for pagefile usage and paging activity

■ Physical memory

■ Swap memory (Unix systems)

Computer

You can select the alarm message to be issued if the computer is rebooted.

Default: The time when the computer was rebooted.

Other

You can select the alarm message to be sent if the probe is not able to fetch data.

Default: Contains information about the error condition.



Status

The status tab displays graphs of the CPU usage, Memory usage, and Paging activity, and a list of file systems being monitored.

Note: This tab opens as the default when the configuration GUI is opened.

Graphs

The graphs display actual samples in purple, averages in blue, error threshold (if configured) in red, and warning threshold (if configured) in yellow.

■ CPU usage: graph of the CPU usage.

■ Memory usage: three separate graphs (% of total available memory, physical, and virtual memory). Use the button in the top right corner of the graph to toggle through the three graphs.

■ % of available memory: in % of total available memory

■ Physical memory: in % of available physical memory (RAM).

■ Swap memory: on UNIX systems, this value refers to the % of available swap space.

Note: Typing <Ctrl>+S on your keyboard will save the current view for this graph, and this view will be shown the next time you open the probe GUI.

■ Paging activity: graph of the paging activity.

You can enter the Threshold values by clicking the up/down indicator for High and Low, or by typing the value into the text field. Please note that the cdm probe uses average value as the reference value when it determines if a threshold is breached.

Disk usage

The disk information list displays the disks installed on the system and the amount of free space on each disk. You can monitor each disk individually, with individual threshold values, messages and severity levels. See the section Disk Usage Modifications.

Disk Usage Modifications

You can modify the properties for a monitored disk by right-clicking on a monitored disk in the list. You have the following options, depending on the disk type:

■ New share properties (on Windows systems)

■ Edit disk properties

■ Delete a disk

■ Modify default disk parameters

■ Enable space monitoring on the NFS file system (on UNIX systems)

New share properties


22 cdm Guide

Windows platform

You can also enter shares to be monitored. Right-click in the disk usage list and select 'New share'. The share is specified with the format \\computer\share.

Once the share is specified, you can specify a user name and password to be used when testing the availability of the share, and the message ID to be sent if a share is determined to be unavailable. You can use the domain user if the machine is a member of a domain.

If you select Folder Availability Quality of Service Message, QoS messages on "share availability" will be sent.

Note: the shares are tested from the service context, and the cdm probe just checks that it is possible to mount the share.

UNIX platforms

You can monitor NFS file systems. To enable/disable space monitoring of the file system, right-click a monitored NFS file system in the list and select the enable/disable space monitoring option.

Note: Enabling space monitoring of a NFS file system may cause problems for the cdm probe if the communication with the NFS server is disrupted (e.g. stale NFS handles).

Default: NFS file systems are monitored for availability only.

Edit Disk Properties

The disk usage configuration GUI displays tabs for each section of the disk configuration.

The following properties can be modified:

Disk Usage and Thresholds Tab

The page displays the amount of total, used, and free disk space for the file system.

You can configure the following threshold settings:

■ Monitor disk using either Mbytes or %.

■ High threshold for the disk. If you select this option, set the value (based on either Mbytes or %) and select the alarm message to be sent. When the amount of free space gets below this value, the specified alarm message will be sent.

■ Low threshold for the disk. If you select this option, set the value (based on either Mbytes or %) and select the alarm message to be sent. When the amount of free space gets below this value, the specified alarm message will be issued.

You can configure the Quality of Service message. The Disk Usage alarm message will contain the disk usage in Mbytes, % or both depending on your selections.

Inode Usage and Thresholds tab



UNIX systems only

This tab is only available for UNIX systems; otherwise it is grayed out. The tab indicates the amount of total, used, and free inodes on the file system.


■ Monitor disk using either inodes or %.

■ High threshold for the disk. If you select this option, set the value (based on either inodes or %) and select the alarm message to be sent. When the amount of free space gets below this value, the specified alarm message will be sent.

■ Low threshold for the disk. If you select this option, set the value (based on either inodes or %) and select the alarm message to be sent. When the amount of free space gets below this value, the specified alarm message will be issued.

You can configure the Quality of Service message. The Disk Usage alarm message will contain the disk usage in inodes, % or both depending on your selections.

Disk usage change and thresholds tab

The tab lets you specify the alarm conditions for alarms to be sent when changes in disk usage occur.

Disk usage change calculation

You can select one of the following:

■ Change summarized over all samples. The change in disk usage is the difference between the latest sample and the first sample in the "samples window". The number of samples the cdm probe will keep in memory for threshold comparison is set as Samples on the Setup > Control Properties tab.

■ Change between each sample. The change in disk usage will be calculated after each sample is collected.

Threshold settings

This section allows you to define the alarm conditions:

■ Type of change. You can select whether alarms should be issued on increase, decrease or both increase and decrease in disk usage.

■ High threshold for the disk. If you select this option, set the value in Mbytes and select the alarm message to be sent. When the amount of free space gets below this value, the specified alarm message will be sent.

Default: 2 Mbytes

■ Low threshold for the disk. If you select this option, set the value in Mbytes and select the alarm message to be sent. When the amount of free space gets below this value, the specified alarm message will be issued.

Default: 2 Mbytes

QoS


24 cdm Guide

You can send QoS messages on disk usage change in Mbytes.

Delete a Disk

A confirmation message appears. Click Yes.

Modify Default Disk Parameters

This section allows you to change fixed disk properties. If you modify the default settings than every disk that you add from that point forward will have the new settings as the default disk properties.



Advanced

You can configure the following advanced settings:

Quality of Service Messages

Selecting any of the following settings enables QoS messages to be sent. The Setup > Control properties tab determines the time intervals for sending QoS messages.

Processor Queue Length (Windows only)

Measures the number of queued processes, divided by the number of processors, waiting for time on the CPU

Note: For AIX, SGI, Linux and Solaris, this QoS message refers to System Load.

Computer uptime (hourly)

Measures the computer uptime in seconds every hour.

Memory Usage

Measures the amount of total available memory (physical + virtual memory) used in Mbytes

Memory in %

Measures the amount of total available memory (physical + virtual memory) used in %.

Memory Paging in Kb/s

Measures the amount of memory that has been sent to or read from virtual memory in Kbytes/second.

Memory Paging in Pg/s

Measures the amount of memory that has been sent to or read from virtual memory in pages per second.

Note: If you have been running CDM version 3.70 or earlier, the QoS settings in the cdm probe GUI are different than CDM version 3.72. However, if CDM version 3.70 or earlier already has created QoS entries in the database for kilobytes per second (Kb/s) and/or pages per second (Pg/s), these entries will be kept and updated with QoS data from the newer CDM version (3.72 and higher).

Physical Memory Usage

Measures the amount of total available physical memory used in Kbytes.

Physical Memory in %

Measures the amount of total available physical memory used in %.

Swap Memory Usage

Measures the space on the disk used for the swap file in Kbytes.

Swap Memory in %


26 cdm Guide

Measures the space on the disk used for the swap file in %.

CPU Usage

This section is divided into two tabs: Total CPU and Individual CPU. These measurements are all in %.

Note: The Individual CPU tab is grayed out in a single CPU configuration.

CPU Usage (Total)

Measures how much time the CPU spends on user applications and high-level system functions. Even when the CPU usage is 0%, the CPU is still performing basic system tasks, like responding to mouse movements and keyboard input. The QoS message includes CPU User, CPU System and optionally CPU Wait information. The optional CPU Wait information requires you to select the CPU Wait is included in CPU Usage (Total) option at the bottom of this page.

CPU User

Measures the time spent by the CPU on user tasks.

CPU System

Measures the time the CPU spends on system tasks.

CPU Wait

Measures the time the CPU waits when accessing external memory or another device.

CPU Idle

Measures the time the CPU runs idle without processing anything.

Alarm on Processor Queue Length

For AIX, SGI Linux and Solaris, this option monitors system load.

Select this alarm setting to check the processor queue length. The processor queue length measures the number of threads that are in the server's processor queue waiting to be executed by the CPU. All servers, whether they have a single CPU, or multiple CPUs, have only one processor queue. The processor queue length is a measurement of the last observed value, and it is not an average of any kind. Alarm messages are generated according to the threshold value you specify.

Default: 4

Note: If running on a multi-CPU system, the queued processes will be shared on the number of processors. If running on a system with four processors and using the default Max Queue Length value (4), alarm messages will be generated if the number of queued processes exceeds 16.

Alarm on Detected Reboot

Select this option if you want an alarm to be sent if this computer is rebooted.

CPU Usage option:



Select this option if you want the QoS message on CPU Total to include CPU User, CPU System and CPU Wait. Otherwise, the CPU Total includes only CPU User and CPU System values.

Paging measured in

Paging can be measured in Kilobytes per second or pages per second.

Paging is the amount of memory which has been sent to or read from virtual memory. This option lets you select the paging to be measured in one of the following units:

■ Kilobytes per second (KB/s)

■ Pages per second (Pg/s). Note that the size of the pages may vary between different operating systems.

Note: When changing the paging selection, the header of the Paging graph on the Status tab will immediately change to show the selected unit, but the values in the graph will not change until the next sample is measured.

QoS messages for NFS file systems

For NFS file systems, you can select QoS message on Disk availability to be sent. Right-click the filesystem on the Status tab and select Edit.

Check "Disk Available Quality of Service' in the properties dialog pop up, and click OK.

Memory usage on Solaris systems

There seems to be some confusion about the memory usage the CDM probe reports on Solaris systems. Most often, the issue is that CDM does not provide the same numbers that the popular TOP utility does. The main reason for this is that TOP and CDM gather swap information differently.

CDM gathers swap information in a similar way as the Solaris utility "swap -l" does, but using pages instead of blocks. To compare the swap information between CDM and the "swap" utility you take the blocks "swap" reports and run it through the formula: (blocks * 512) / (1024 * 1024) = total_swap Mb. This is the same number of MB the CDM probe uses in its calculations.

TOP on the other hand gathers information about "anonymous pages" in the VM, which, while quicker and easier to gather, do not represent a true picture of the amount of swap space available and used. Teh reason for this is that anonymous pages also take into account physical memory that is potentially available for use as swap sapce! Thus, the TOP utility will report more total swap space since it is also factoring in physical memory not in use at this time.

CDM and TOP gather physical memory information in similar ways, so the differences in available physical memory should be insignificant.


28 cdm Guide

Since CDM does not differentiate between available swap and physical memory (after all, it is only when you run out of both the resources that things stop working on the system), the accumulated numbers are used. The accumulated numbers for TOP will be off, since the free portions of physical memory will be counted twice in many instances. While we could easily represent the data in the same format that TOP does, we feel it does not give a correct picture of the memory/swap usage on the system.



Custom

Custom profiles are used to get additional thresholds and alarms for checkpoints that are available in the probe. All the alarm situations are available, except for those available for multi-CPU and cluster disks. A custom profile allows you to fine-tune monitoring of resources for alarming purposes.

The alarms for each custom profile will be sent using suppression keys unique to the profile so that you can get multiple alarms for what is basically the same alarm situation (for instance, the a breach of the memory usage threshold).

There are three main types of profiles:

■ CPU Profile

■ Disk Profile

■ Memory Profile

CPU profile

Thresholds and alarm messages can be specified for the following parameters:

■ Overall CPU usage

■ CPU usage for user processes

■ CPU usage for system processes

■ CPU I/O Wait

■ System load (on UNIX)/Processor queue length (on Windows)

Disk profile

The disk profile can be of three different types, as described below:

■ Local

■ NFS

■ Share

Refer to the Disk area information for the Status tab for more information on monitoring the individual disk types.

Local: local file systems

Can monitor disk availability, space free, inodes free and changes in disk usage.

The inodes free tab is disabled if the configuration tool detects that no inode information can be obtained (for instance for a Windows file system).

NFS: Network File System mounted on the machine


30 cdm Guide

Only available on UNIX. By default, these file systems are only monitored for availability, but checking the 'allow space monitoring' checkbox will allow the same checkpoints as for a local file system.

Share

Monitoring a share is done by at each interval checking that the share can be mapped. This type of profile is only checked on Windows.

Memory profile

Thresholds can be set for Memory usage, physical memory usage, swap memory usage and paging activity.

Note that the unit used for paging activity is determined by the 'Paging measured in' setting in the Advanced tab.

Options Configured Using Raw Configure

To access the raw configuration pages hold the Shift key and right click the cdm probe in Infrastructure Manager, then select Raw Configure. The raw configuration allows you to edit the configuration file or edit the data file.

Raw Configuration

Below you will find some useful options that can be set, using the Raw Configuration tool:

■ ignore_device

■ ignore_filesystem

To ignore certain disks and/or file systems, you can edit one of these two keys in the <disk> section:

■ ignore_device = /<regular expression>/

■ ignore_filesysem = /<regular expression>/

The value should be a regular expression that would match all disks and/or filesystems that you want the probe to ignore. Here is an example to ignore Auto-mounted disks that are recognized on each "disk interval":

ignore_device = /autofosmount.*|.*:V.*/



Multi-CPU Configuration

This section describes the cdm probe multi-CPU configuration setup. The configuration GUI displays tabs for each section of the multi-CPU configuration.

A multi-core processor (multi-CPU) is a single computing component with two or more independent actual processors (called "cores"), which are the units that read and execute program instructions. A multi-core processor implements multiprocessing in a single physical package.



32 cdm Guide

Setup

Setup




Log level


Log size


Default: 100 KB


















■ Disk properties

■ CPU properties


CPU Properties


Example



Interval


Samples











34 cdm Guide



Interval


Samples



QoS Interval






■ Message pool

■ Active messages

Message Pool


Active Messages


CPU






Disk


Memory


■ Memory usage


■ Physical memory


Computer



Other




36 cdm Guide

Status



Graphs










Disk usage






■ Delete a disk






Windows platform





UNIX platforms
















38 cdm Guide

UNIX systems only













Threshold settings




Default: 2 Mbytes


Default: 2 Mbytes

QoS




Delete a Disk




Multi CPU

This tab contains a graph displaying the alarm threshold and the CPU usage for each processor in a multi-CPU configuration.

Note: This tab will only appear when the cdm probe is running on a multi-CPU computer.

The following thresholds and options can be set:

■ Maximum

High (error) threshold (in %) for individual CPU usage (alarms are sent when one of the CPUs in multi-CPU systems breaches the threshold).

■ Difference

CPU difference threshold (in %). Alarms are sent when the difference in CPU usage among the CPUs in a multi-CPU system breaches the threshold).

■ Select processors to view

Select the processor(s) to view in the graph. By default all are shown. When clicking one of the processors in the list, only that processor will be shown.

Click the Update button to refresh the graph with the most current sample values.


40 cdm Guide

Advanced









Memory Usage


Memory in %











Swap Memory Usage


Swap Memory in %




CPU Usage



CPU Usage (Total)


CPU User


CPU System


CPU Wait


CPU Idle





Default: 4




CPU Usage option:


42 cdm Guide


Paging measured in















44 cdm Guide

Custom




■ CPU Profile

■ Disk Profile

■ Memory Profile

CPU profile





■ CPU I/O Wait


Disk profile


■ Local

■ NFS

■ Share









Share


Memory profile



Cluster Configuration

This section describes the cdm probe cluster configuration setup. The configuration GUI displays tabs for each section of the cluster configuration.

A cluster is several machines grouped together, all performing a similar function. Clusters are typically used for high-end processing.

The cdm probe in a clustered environment requires the cluster probe be installed and configured. The cdm probe will automatically detect the cluster disks, create profiles for these and register them with the cluster probe.

Important: If you upgrade the cdm probe you should remove local profiles for the cluster disks.



46 cdm Guide

Setup

Setup




Log level


Log size


Default: 100 KB


















■ Disk properties

■ CPU properties


CPU Properties


Example



Interval


Samples











48 cdm Guide



Interval


Samples



QoS Interval






■ Message pool

■ Active messages

Message Pool


Active Messages


CPU






Disk


Memory


■ Memory usage


■ Physical memory


Computer



Other




50 cdm Guide

Setup Cluster

This tab displays a list of detected virtual groups belonging to the cluster. By editing the entries, you can set the alarm source and Qos source to e used for disks belonging to that virtual group.

Note: This tab will only be available when the cdm probe is configured as a part of a cluster.

The available options for alarm source and QoS source are:

■ <cluster ip>

■ <cluster name>

■ <cluster name>.<group name>

To edit the alarm source or QoS source:

1. Double click a virtual group entry.

The Group Sources dialog appears.

2. Select the Alarm source and QoS source; then click OK.

QoS message for Disk usage

Note that Quality of Service messages can also be sent on Disk usage (both in % and MB), and availability for shared disks (also disk usage on NFS file systems if the Enable space monitoring option is set for the file system as described in the section Setup > Cluster). These options can be selected when defining the threshold values for these options under the Status tab.



Status



Graphs










Disk usage






■ Delete a disk





52 cdm Guide

Windows platform





UNIX platforms

















UNIX systems only













Threshold settings




Default: 2 Mbytes


Default: 2 Mbytes

QoS


54 cdm Guide


Delete a Disk




Multi CPU

This tab contains a graph displaying the alarm threshold and the CPU usage for each processor in a multi-CPU configuration.

Note: This tab will only appear when the cdm probe is running on a multi-CPU computer.

The following thresholds and options can be set:

■ Maximum

High (error) threshold (in %) for individual CPU usage (alarms are sent when one of the CPUs in multi-CPU systems breaches the threshold).

■ Difference

CPU difference threshold (in %). Alarms are sent when the difference in CPU usage among the CPUs in a multi-CPU system breaches the threshold).

■ Select processors to view

Select the processor(s) to view in the graph. By default all are shown. When clicking one of the processors in the list, only that processor will be shown.

Click the Update button to refresh the graph with the most current sample values.



Advanced









Memory Usage


Memory in %











Swap Memory Usage


Swap Memory in %


56 cdm Guide


CPU Usage



CPU Usage (Total)


CPU User


CPU System


CPU Wait


CPU Idle





Default: 4




CPU Usage option:




Paging measured in















58 cdm Guide




Custom




■ CPU Profile

■ Disk Profile

■ Memory Profile

CPU profile





■ CPU I/O Wait


Disk profile


■ Local

■ NFS

■ Share






How to Copy Probe Configuration Parameters

60 cdm Guide


Share


Memory profile



How to Copy Probe Configuration Parameters

If you want to configure the cdm probe the same way on multiple robots, you can copy the probe configuration from one probe to another.

Important: When performing this operation with the cdm probe, you must ensure that the disk partitions are the same on the source and the target computers.

Example:

If the source computer has a C: and a D: partition, and you copy the cdm probe configuration to a cdm probe on a computer with only a C: partition, the cdm probe on this computer will try to monitor a D: partition (which is missing) and report an error.


Chapter 5: QoS Threshold Metrics

Many Nimsoft Monitor probes ship with default QoS threshold values set. The default threshold values provide an idea of the type of values to be entered in the fields and are not necessarily recommended best practice values. To aid in tuning thresholds and reducing false-positive alarms, this section describes the QoS metrics and provides the default QoS thresholds.

More information:

QoS Metrics (see page 61) cdm Alert Metrics Default Settings (see page 62)


QoS Metrics (see page 61) cdm Alert Metrics Default Settings (see page 62)

QoS Metrics

This section contains the QoS metrics for the cdm probe.

Monitor Name Units QoS Metric

QOS_CPU_IDLE Percent CPU Idle

QOS_CPU_MULTI_USAGE

(all of these metrics are calculated from this monitor)

Percent Individual CPU Idle

Percent Individual CPU System

Percent Individual CPU Usage (Total)

Percent Individual CPU User

Percent Individual CPU Wait

QOS_CPU_USAGE

(all of these metrics are calculated from this monitor)

Percent CPU System

Percent CPU Usage

Percent CPU User

Percent CPU Wait

QOS_DISK_DELTA Megabytes Disk usage change

QOS_DISK_USAGE Megabytes Disk usage

cdm Alert Metrics Default Settings

62 cdm Guide

QOS_DISK_USAGE_PERC Percent Disk usage (%)

QOS_INODE_USAGE Inodes Inode usage

QOS_INODE_USAGE_PERC Percent Inode usage (%)

QOS_MEMORY_USAGE Megabytes Memory usage

QOS_MEMORY_PAGING Kilobytes/ Second

Memory Paging in Kilobytes per second

QOS_MEMORY_PAGING_PGPS Pages/ Second

Memory Paging in Pages per second

QOS_MEMORY_PERC_USAGE Percent Memory Usage (%)

QOS_MEMORY_PHYSICAL Megabytes Physical memory usage

QOS_MEMORY_PHYSICAL_PERC Percent Physical memory usage (%)

QOS_MEMORY_SWAP Megabytes Swap memory usage

QOS_MEMORY_SWAP_PERC Percent Swap memory usage (%)

QOS_PROC_QUEUE_LEN Processes Processor queue length

QOS_SHARED_FOLDER Available Folder availability

QOS_DISK_AVAILABLE Available Disk availability

QOS_COMPUTER_UPTIME Seconds Computer uptime


This section contains the QoS metric default settings for the cdm probe.

QoS Metric Warning Threshold

Warning Severity

Error Threshold

Error Severity Description

CPU Usage 75% Warning 90% Major Total CPU above error threshold

Memory Usage in percent 50% Warning 90% Major Memory Percent Usage

Physical memory usage 85% 95%

Swap memory usage 60% 85%

Memory Paging Activity 150KB/ sec Warning 400 KB/ sec Major Amount of paging that is occurring

Disk Usage and Thresholds (Disk Error)

Disk usage (%) 20% Major 10%



QoS Metric Warning Threshold

Warning Severity

Error Threshold

Error Severity Description

Disk usage (Mb)

default should be 20% of total disk space

default should be 10% of total disk space

Disk Usage Change and Thresholds (Delta Error)

Disk usage 8 10

Inode Usage and Thresholds

Inode usage (%) 20 10

Inode usage (inodes) 20 10

Inode Free 20 10

Disk Metric delta 5 10

Max Queue Length

Processor Queue Length 4 Warning - - The number of processes waiting to run

Maximum

MultiCPU CPU usage of single cpu - 90

Difference

MultiCPU Difference in CPU usage between CPUs - 50


Chapter 6: Troubleshooting and FAQs

This section contains troubleshooting information for the cdm probe.

More information:

Guidelines for Sending Bug Reports for CDM (see page 66)


Guidelines for Sending Bug Reports for CDM (see page 66)

Guidelines for Sending Bug Reports for CDM

66 cdm Guide


The following is a list of files and commands that should be run on the affected system before a bug report is filed. The files and output from the commands should be attached to the bug report if possible. By providing this information with the bug report saves time during the evaluation of the issue.

Files for all platforms:

Note: Loglevel should be set to 3 and the error reproduced prior to sending these files. Since this will generate quite a lot of log information, you can either increase the size of the log files in the cdm GUI or set the Loglevel to 13, which will not truncate the log file.

■ cdm.cfg

■ cdm.log

■ _cdm.log

Windows:

The version of Windows and SP level should be provided. Individual patches applied are not necessary unless explicitly requested. A screen shot of the Performance tab in the Task Manager would be helpful if the problem is CPU or Memory related. A screen shot of the disks in Windows Explorer would be helpful for disk issues.

Unix (all platforms):

# uname -a

# mount

# df -k (on systems that support the -k option)

AIX:

# /usr/bin/vmstat

# /usr/sbin/sar -P ALL

# /usr/bin/uptime

HP-ux:

No commands need to be executed on this platform.

LINUX:

# cat /proc/stat

# cat /proc/vmstat (if applicable)

# cat /proc/meminfo

# cat /proc/loadavg

Solaris:

# /usr/bin/mpstat 60 (note: runs until stopped with Ctrl-C, get at least two

iterations)



# /usr/bin/uptime

Tru64:

# /usr/sbin/collect -s c -t -i0 (note: runs until stopped with Ctrl-C, get at least

two iterations)

Nimsoft Monitor cdm Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/cdm/4.5/cdm.pdfNo part of...

Documents

Transcript of Nimsoft Monitor cdm Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/cdm/4.5/cdm.pdfNo part of...