Does uninstalling and reinstalling a Linux robot type to a different path impact MCS Profiles and Data in OC?
Article ID: 228059
Updated On:
Products
Issue/Introduction
Does uninstalling and reinstalling a Linux robot type to a different path impact its MCS Profiles and Data in OC?
Environment
Release : 20.3
Component : UIM - ROBOT
Resolution
You can move or reinstall the robot to an alternate path without impacting its MCS profiles and Data seen OC as long as the original robot id is maintained.
See the following options
Option 1. Copy the Nimsoft home folder to the new path
a. Stop the nimbus service
b. Copy the original nimsoft home folder to new location
c. Delete all files in the /opt/nimsoft/niscache/
d. Edit the /etc/rc.d/init.d/nimbus file with the new path.
e. Start the nimbus service
Option 2. Reinstall robot to new path
Note: The robot install to a new path should use the same robot id as long as the strong correlator robot attributes remain the same. IP Address, MAC, Robot Name, Origin
a. Uninstall robot
b. Reinstall robot to a new path
c. Run the mon_config_service -> plugin_metric_correction callback against the robot that was reinstalled to get profiles redeployed.
- In IM CTRL+P on the mon_config_service probe
- Select the plugin plugin_metric_correction callback from the Probe commandset pulldown
- Select robot_names and enter the newly reinstalled robot
See links below for additional information:
mon_config_service -> plugin_metric_correction
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/spooler/plugin-metric.html
Discovery Server -> Device Correlation troubleshooting
https://techdocs.broadcom.com/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/discovery-server-discovery-server/device-correlation-troubleshooting.html
Feedback
