Getting unexpected alarm from an mon_config_service 'mcs' sourced probe
search cancel

Getting unexpected alarm from an mon_config_service 'mcs' sourced probe

book

Article ID: 221722

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Unexpected alarm from an mon_config_service 'mcs' sourced probe, and the profile configuration does not indicate it should.

Environment

Release: 20.x
Component: mcs

Resolution

Check the C:\Program Files (x86)\Nimsoft\plugins\plugin_metric.cfg file to see if the alarm profile is listed there. If it is than perform the following:

Run the plugin_metric callback against this source to see if that clears up the object in the plugin_metric.cfg:

CTRL + P on the mon_config_service probe (below)

https://api-broadcom-ca.wolkenservicedesk.com/attachment/get_attachment_content?uniqueFileId=r4ktVM+ZwmjnESmvdVk/EA==

It may take 10-15 minutes to perform the operation.

Additional Information

process_all_devices_flag
Enter the value as true if you want to re-deploy enhanced profiles or alarm policies on all the devices. If you select this parameter, all the remaining parameters are not required.
robot_names
Enter the specific robot name on which you want to re-deploy the enhanced profiles or alarm policies. If you want to use more than one entry, enter a comma-separated list.
computer_system_ids
Enter the specific computer system ID (cs_id) on which you want to re-deploy the enhanced profiles or alarm policies. If you want to use more than one entry, enter a comma-separated list.
cm_group_ids
Enter the specific group ID on which you want to re-deploy the enhanced profiles or alarm policies. All the devices that are part of that group are considered for re-deployment. If you want to use more than one entry, enter a comma-separated list.