Best practice for removing mon_config_service 'MCS' from a robot in a group
search cancel

Best practice for removing mon_config_service 'MCS' from a robot in a group

book

Article ID: 206298

calendar_today

Updated On:

Products

Unified Infrastructure Management for Mainframe DX Unified Infrastructure Management (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

MCS has been installed accidently to a set of systems.

Environment

Release : All
Component : mon_config_service

Resolution

The recommended method for removal, would be to remove the device from the group, allowing the plugin metric to be updated then remove or replace the probe to the non MC version.

The plugin_metric file can be fixed after the fact by running the plugin_metric_correction callback in the mon_config_service probe:

- in IM, press CTRL+P when you have the mon_config_service probe selected
- select the plugin plugin_metric_correction callback from the Probe commandset pulldown
- specify the required parameter and select the green arrow/button to execute the callback

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.