CDM probe GUI coming up blank

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

Error in the cdm log.

CDM is being configured via IM.

 

Environment

• Release: UIM 8.51
• Component: UIM - CDM WITH IOSTAT

Cause

• Unknown
• Possible root cause: The problem could have been too many CPUs/discovered file systems for the probe to monitor/handle, or iostat monitoring frequency intervals were too aggressive (low), if they were enabled. Based on the log attached it might have been the iostat monitoring. Try increasing the intervals/frequency to help lighten its resource usage.

Resolution

The cdm probe was working, then all of a sudden it was showing blank values on one of the customers critical production servers and the root (/) directory went up to 99% and they didn't receive any disk alarms. But the issue passed and is no longer occurring.

cdm technical details (data collection)

Uptime
Uptime is read directly from the file /proc/uptime. The number of processors is found using the system call get_nprocs(). The installed physical memory is found in the file /proc/meminfo.

CPU
The CPU usage information is found by reading the file “/proc/stat”. Based on the data gathering interval either the 1, 5 or 15 minute average is used. The load data is found by reading the file “/proc/loadavg”. Based on the data gathering interval either the 1, 5 or 15 minute average is used.

Memory/Swap
Memory and swap usage is found by reading the file ”/proc/meminfo”. The amount of physical memory used is based on the formula MemTotal - MemFree - Buffers – Cached. This because buffers and cached data are instantly available to any process which requests more memory. Paging data is found by reading the file “/proc/stat” on older Linux Kernels, and “/proc/vmstat” on newer systems. Since the data is cumulative the difference since the last data gathering is used as the basis for calculating paging in KB/s based on the formula paging_kbps = paging_delta * pagesize / interval.

Disk
The list of mounted filesystems is found using the system call getmntent(). Space usage on the filesystems is found using the system call statvfs(). The cdm probe initially makes the following call to determine Disk Throughput metrics:

fdisk -l
fdisk -l | awk '/Disk/{print$2}'
fdisk -l | awk /Disk/{print$2}

If the UIM robot is not owned by the root user, then the user that owns the robot and the cdm probe must have system permissions that allow the user to execute this command.  If these permissions are not granted to this user, the cdm probe will not collect the Disk Throughput metrics.

Please see if you can run these commands on the Linux system and obtain results.

cdm commands run on Linux:

cat /proc/stat 
cat /proc/vmstat (if available)
cat /proc/meminfo
cat /proc/loadavg
cat /proc/uptime
fdisk -l