How can I successfully move a robot or probe from one hub (or robot) to another?

Document ID : KB000033538
Last Modified Date : 17/05/2018
Show Technical Document Details
Introduction:


Sometimes, it becomes necessary to move a robot from one hub to another, or to move a monitoring probe (such as net_connect) to a different robot (sometimes also underneath a different hub.) When this is necessary, steps should be taken to reset the device and metric ID's in order to ensure that the charts and graphs will still contain appropriate data.



 
Background:
All devices in UIM have a corresponding device_id, and all metrics monitored on those devices have a corresponding metric_id -- the alignment of device_id's and metric_id's is necessary for charts and graphs to be displayed properly in UMP/USM.
Instructions:
If you have moved a robot from one hub to another:

1. Stop the Robot Service on the moved robot.
2. Locate the folder \Nimsoft\niscache\ in the Nimsoft installation directory and delete all files present in this location.
3. Start the Robot Service. This will cause all new device and metric ID's to be generated.
4. Stop the data_engine probe on the primary hub.
5. Issue the following SQL query against the backend UIM database:
UPDATE S_QOS_DATA SET CI_METRIC_ID = NULL WHERE ROBOT = '<robotname goes here>';
6. Activate the data_engine probe.

Within a few minutes, the CI_METRIC_ID field for this robot will be repopulated with the new metric ID's and the metrics will appear in UMP.

If you have moved a probe from one robot to another (whether or not you have also changed hubs):

1.Stop the Robot Service on the original robot.
2. Locate the folder \Nimsoft\niscache\ in the Nimsoft installation directory and delete all files present in this location.
3. Start the Robot Service. This will cause all new device and metric ID's to be generated -- minus the device ID's and metric ID's which correspond with the probe which is no longer present (this will prevent duplication.)
4.
Stop the Robot Service on the moved robot.
5. Locate the folder \Nimsoft\niscache\ in the Nimsoft installation directory and delete all files present in this location.
6. Start the Robot Service. This will cause all new device and metric ID's to be generated
7. Stop the data_engine probe on the primary hub.
8. Issue the following SQL query against the backend UIM database:
UPDATE S_QOS_DATA SET CI_METRIC_ID = NULL WHERE ROBOT = '<new robotname goes here>';
9. Activate the data_engine probe.

Within a few minutes, the CI_METRIC_ID field for this robot will be repopulated with the new metric ID's and the metrics will appear in UMP.