CDM InternalAlarm: Unable to get CPU data (error) or Memory data (temporarily out of resources)

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Symptom:

The cdm probe logs generate intermittent internal alarms: "InternalAlarm: Unable to get CPU data (temporarily out of resources)" or "InternalAlarm: Unable to get Memory data (temporarily out of resources)" on AIX 7.x systems.

cdm:InternalAlarm: Unable to get Memory data (temporarily out of resources)
cdm:InternalAlarm: Unable to get CPU data (error)
cdm:InternalAlarm: Unable to get Memory data (error)

 

CDM logs might show:

cdm: CPU data has not been updated...
cdm: CheckCpuInfo - GetCpuInfo failed (temporarily out of resources)

Environment

• DX UIM 23.4.*
• Cdm 5.x or above
• AIX Systems
• Windows Systems

Cause

• On AIX machines the commands CDM will run will timeout before completing. Changing the timeout will resolve the issue.
• On some systems incorrect NTP settings can cause this issue
• On Windows Systems the performance counters may have been corrupted

Resolution

On AIX Systems:

1. For CPU:
   Update Raw Configuration:
   
   
   • Open the Raw Configure menu for the cdm probe on the affected AIX robot.
   • Navigate to the /cpusection.
   • Add or update the following keys:
     
     
     • sliced_cpu_interval = 250
   • Click Apply and allow the probe to restart.
2. For memory:
   Update Raw Configuration:
   
   
   • • Open the Raw Configure menu for the cdm probe on the affected AIX robot.
     • Navigate to the /memorysection.
     • Add or update the following keys:
       
       
       • sliced_memory_interval = 250
     • Click Apply and allow the probe to restart.

 

On Windows systems:

Work with the system administrator to rebuild the performance counters.  CDM probe uses these Windows components to collect the metrics.
If needed, go through the below link for “how to manually rebuild the performance counter library values “.
Rebuild performance counter library values - Windows Server | Microsoft Learn

 

 

 

On all systems: 

• Verify Intervals: Ensure the main collection interval for the CPU/Memory monitoring profile in the GUI is set to at least 5 minutes (300 seconds) to provide sufficient overhead for the sliced collection.
• Time Synchronization: Verify that the AIX server is synchronized via NTP, as time drift can contribute to timeout failures.