CDM disk alarms appear to be delayed on some Linux and Solaris systems

Products

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

Issue/Introduction

We are experiencing delays in alerting from the CDM probe, specifically for disk errors.  The alerts are set for 2 samples at 7 min intervals but it takes over 25 min for the alert to generate. 

cdm disk alarm shows up when the probe is restarted but not at the time interval it is being monitored based on the configuration, hence it seemed like the alarms were delayed.

Environment

• Release: 20.4
• robot v9.33HF5
• cdm v6.84
• Linux and Solaris machines (robots)

Cause

• cdm disk configuration properties, timeout
• (Non-Windows platforms only) Timeout:
  • specifies the maximum time for the probe to collect monitoring information. For example, timeout for disk fail or crash scenarios in stale filesystems allows you to prevent the probe from going into a pending state. You can specify the default timeout of 5 seconds to retrieve the disk statistics.

Resolution

We made this change:

*cdm disk timeout is now set to 15* (from default of 5).

 

Existing Disk Properties
---------------------

Interval 7 mins

samples 2

Ignoring 2 file systems

17 filesystems being monitored.

We also tested a 2nd cdm probe instance after increasing the timeout to 15, and the cdm disk alarm showed up 7 minutes later.

The same alarms showed up in IM as well as OC.

Issue resolved.