Mixed configuration: configuring monitoring with MCS and IM / Admin Console GUI

Products

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

Issue/Introduction

• Is mixed configuration MCS and IM supported? 
• Can we configure a probe in MCS (Monitoring Configuration Services) and then change configuration IM or Admin Console on a later stage? 
• Can we set up CPU and Memory with CDM configured through MCS and Disk through probe configuration?

 

Environment

• DX UIM 20.4.* / 23.4.*

Cause

• Guidance

Resolution

• DX UIM does not officially support nor encourage mixed configurations using MCS and IM fat client GUI / Admin Console web interface.

• If you use MCS, MCS "takes over" and applies rules for monitoring and alarming using the plugin_metric.cfg and the Alarm Policies, effectively overriding any pre-existing configuration.

• With 'mixed' configuration we refer to the scenario where for example, you configure an MCS profile for a certain group and then you edit a particular probe configuration using IM. This can affect the correct flow of metric enablement and alarm policies and create inconsistencies. So, if using one method or another, it is best practice to start and stick with one method, e.g., MCS versus Non-MCS.

• That stated, hybrid use is supportable and it is based on using a specific robot, for example use of IM and/or Admin Console on that specific robot.

• But you MUST keep track of which robots you use the specific user interface on and stick with it without accidentally 'mixing and matching.' For instance, if you create a  an OC Group and include that robot, then MCS will override the IM or Admin Console configuration. They must remain separate.

Additional Information

Related KBs:

• Migrate probe configuration from IM and/or AC to MCS (Monitoring Configuration Services)
  
  
• MCS is overriding disk custom CDM profiles set through IM