MCS is overriding disk custom CDM profiles set through IM

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

• After setting an MCS profile and a related alarm policy and then adding a custom disk alarm through IM in the CDM probe, all of our profiles are disabled and do not work as expected. 
  
  
• We are monitoring system-related disks via MCS CDM profile and application-related disks via IM for the same robot. Alarm policies are created for system related disk but If we create alarms for application related disk via IM, all profiles are disabled. Why? 
  
  
• Is there any other option to enable both MCS and Infrastructure Manager to work together without conflicts?

Environment

DX UIM 20.4.* / 23.4.*

Cause

Mixed configuration not supported

Resolution

DX UIM does not support Mixed configuration: configuring monitoring with MCS and IM / Admin Console GUI. If you use MCS, MCS "takes over" and applies rules for monitoring and alarming using the plugin_metric.cfg located locally at every robot, and respective the Alarm Policies, effectively overriding any pre-existing configuration.

For alarming different components once MCS is being used, such as DISK related alarm, multiple Alarm Policies can be created.  Manage Alarms with Centralized Alarm Policies

Additional Information

Related KB: 

• Mixed configuration: configuring monitoring with MCS and IM / Admin Console GUI
• Migrate probe configuration from IM and/or AC to MCS (Monitoring Configuration Services)