search cancel

Robot creates false cdm alarm

book

Article ID: 253422

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Hi,

We have a robot that we cannot explain why it created an alarm.

Robot called mcpcs01 create an alarm ‘STANDBY_SAP Disk Usage (%) on /sapdb/MCP/sapdata1 for mcpcs01 is at 90.08%’ (see screenshot below). The problem is this robot should not have created this alarm at all, as far as we can see.

The robot is assigned to 8 policies as shown below. I will upload the plugin_metric.cfg and the cdm.cfg files to this case.

The plugin_metric.cfg file shows QOS_DISK_USAGE_PERC policies in:

  • Policy_1492 (metric_3854, metric_recedence=10000), but without any message text that includes ‘STANDBY_SAP’. This policy matches /sapdb/MCP/sapdata1 ci, but the profile is disabled.
  • Policy_352 (metric_5124, metric_precedence=666), but without any message text that includes ‘STANDBY_SAP’. This policy does not match /sapdb/MCP/sapdata1 ci
  • Policy_68 (metric_73, metric_precedence=199), but without any message text that includes ‘STANDBY_SAP’. This policy matches /sapdb/MCP/sapdata1 ci
  • Policy_838 (metric_8427, metric_precedence=600). This policy includes ‘STANDBY_SAP’, but the policy doesn’t match /sapdb/MCP/sapdata1 ci
    It looks like the message might be triggered by this policy, based on the message text. But the problem is that the ci doesn’t match, so it shouldn’t be triggered by this policy
  • Policy_838 (metric_8451, metric_precedence=600). This policy includes ‘STANDBY_SAP’, but the policy doesn’t match /sapdb/MCP/sapdata1 ci
    It looks like the message might be triggered by this policy, based on the message text. But the problem is that the ci doesn’t match, so it shouldn’t be triggered by this policy
  • Policy_838 (metric_8453, metric_precedence=600). This policy includes ‘STANDBY_SAP’, but the policy doesn’t match /sapdb/MCP/sapdata1 ci
    It looks like the message might be triggered by this policy, based on the message text. But the problem is that the ci doesn’t match, so it shouldn’t be triggered by this policy
  • Policy_890 (metric_4972, metric_precedence=9900), but without any message text that includes ‘STANDBY_SAP’. This policy does not match /sapdb/MCP/sapdata1 ci
  • Policy_890 (metric_6793, metric_precedence=10000), but without any message text that includes ‘STANDBY_SAP’. This policy matches /sapdb/MCP/sapdata1 ci, but the message should not be triggered because threshold 200.0 can never be reached
  • Policy_890 (metric_6804, metric_precedence=9900), but without any message text that includes ‘STANDBY_SAP’. This policy does not match /sapdb/MCP/sapdata1 ci
  • Policy_839 (metric_5186, metric_precedence=700), but without any message text that includes ‘STANDBY_SAP’. This policy does not match /sapdb/MCP/sapdata1 ci
  • Policy_839 (metric_5203, metric_precedence=700), but without any message text that includes ‘STANDBY_SAP’. This policy does not match /sapdb/MCP/sapdata1 ci
  • Policy_839 (metric_5209, metric_precedence=700), but without any message text that includes ‘STANDBY_SAP’. This policy does not match /sapdb/MCP/sapdata1 ci
  • Policy_839 (metric_5205, metric_precedence=700), but without any message text that includes ‘STANDBY_SAP’. This policy does not match /sapdb/MSP/sapdata1 ci
  • Policy_839 (metric_6801, metric_precedence=700), but without any message text that includes ‘STANDBY_SAP’. This policy does not match /sapdb/MSP/sapdata1 ci
  • Policy_839 (metric_8461, metric_precedence=700), but without any message text that includes ‘STANDBY_SAP’. This policy does not match /sapdb/MSP/sapdata1 ci

It seems like this robot created an alarm that can’t be triggered by one of the policies:

  • Policy 1492: ci matches, but profile is disabled and the message does NOT match
  • Policy 68: ci matches, but the message does NOT match
  • Policy 890: ci matches, but the message does NOT match
  • Policy 838: ci does NOT match, but the message does match

Can you please help us to find out why this robot creates the alarm. This false alarm triggers a standby to check and solve disk issues at night.

We're using 20.4 CU4, cdm probe 6.82-MC

Environment

Release : 20.4

Resolution

open the controller probe utility and run these callbacks:
reconfig_plugin_metric
_nis_cache_clean
_reset_device_id_and_restart