Probe CDM with Fixed Threshold don't trigger the alarm.

book

Article ID: 7829

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

Probe CDM don't trigger alarm for static threshold for Memory or Disk or CPU

Cause

If you change the CDM configuration or you create a super package that containing the CDM configuration for Memory or Disk or CPU and you change the alarm active from yes to no will cause this issue.

You will be able to see on the Dr nimbus the QoS definition and QoS message but will not be able to see the Alarm or Alarm2.

Maybe you can see the alarm and alarm2 for Disk and CPU if you just change the configuration on the memory.

 

 

Environment

Any environment and SO that is using the CDM probe.

Resolution

Open yours CDM configuration and looks for Memory and make sure is set to yes the alarm section

You have this configuration.
<memory> section
<alarm>
active = no
Must be yes 
<memory>
<alarm>
active = yes

If you have issue on the Disk check the Disk alarm section

If you have issue on the CPU check the CPU alarm section.