Migrate probe configuration from IM and/or AC to MCS (Monitoring Configuration Services)
search cancel

Migrate probe configuration from IM and/or AC to MCS (Monitoring Configuration Services)

book

Article ID: 281786

calendar_today

Updated On:

Products

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

Issue/Introduction

  • We are using DX UIM with probe configurations using the Infrastucture Manager (IM) and the Admin Console (AC). 

  • We are planning on adopting the Monitoring Configuration Services (MCS) type of configuration (mon_config_service)

  • Is there any specific procedure or best practices to perform a smooth change / migration from IM to MCS? 

  • Is 'mixed' configuration IM/AC and MCS supported? 

  • Do we need to delete IM and AC probe configurations before deploying MCS profiles?

Environment

  • DX UIM 20.4.* / 23.4.*

Cause

  • Guidance

Resolution

  • Mixed configuration is not supported; however, you do NOT have to delete configurations to "migrate from IM to MCS"

  • 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.

    Best practice is to start and stick with one method, e.g., MCS versus Non-MCS.

  • Nevertheless, if you have manually deployed probes and configured them on a given robot (or the robot has inherited the probes/configurations from the 'superpackage' type of bulk configuration which uses the distsrv) or in any case, configured probes/probe profiles in IM or AC, if at a certain point, an MCS profile (group or profile derived) is deployed to the robot, the MCS profile will always take precedence and will work properly. In this case, there is no corruption or inconsistency.

  • So, if you have 100 logmon robots with a certain configuration, or if these 100 robots have different manually set configurations, you can create a group or different groups, and deploy MCS profiles to these Dynamic or Static Groups that contain systems. MCS will override the existing configuration, and properly set up the correspondent plugin_metric.cfg that will serve the controller/spooler to issue the correct metrics and alarms. 

  • Essentially, if you are migrating from IM to MCS, you can simply set up MCS without the need to delete the previous configuration. 

IMPORTANT

Please also take into account that if a robot and its probes have been configured through IM, and an MCS profile is deployed to it, but after this the MCS profile is deleted, or the server leaves the group where it had inherited the MCS group profiles, the local configuration will be wiped out, leaving the robot without monitoring (it will not revert to the original IM configuration.) 

•  First review the official docs-> Monitoring Configuration Service (broadcom.com) and understand the best practices in the section titled->
Workflow for Managing Configuration Profiles. Then plan your MCS deployment based on your monitoring needs. Note that you can create groups with certain configurations/filters for groups without current members. Then on these testing groups with a group profile, add a small set of servers. If the results are as expected, move additional robots to the desired groups.

Additional Information

DX UIM 23.4 includes new MCS improved mechanisms, and we strongly suggest upgrading to this version to get all the benefits from the improvements:
Please refer to:

What's New in DX UIM 23.4 (broadcom.com)

Improved Scale and Resilience for Monitoring Configuration Service (MCS)

When possible, use the latest DX UIM version and cumulative update.


Related KBs: 

Powered by Wolken Software