Moving UIM robots or probes from one hub or robot to another

book

Article ID: 33538

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/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.

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.

Environment

- UIM 8.x or later

Resolution

If you have moved a robot from one hub to another with these steps:

IM console > right click on robot > Move

Option 1 (Recommended and Full steps)

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.

Note that if you dont have direct access to the local robot machine, the process of clearing the niscache and resetting the robot device id can be executed from within IM, controller Probe Utility (via Ctrl-P) but you have to select 'Expert Mode,' then run the callbacks. That will also restart the robot.

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.

Option 2:

You can stop the robot watcher service and then edit robot.cfg on the robot itself.

You will need to change the following:

hub =
hubip =
hubrobotname =

Then start the robot back up and it will be reporting to the new hub.

Then you will probably have a duplicate robot showing in IM, so you will want to right-click the "old" robot in IM and click Remove or if that doesn't work open up the Hub probe GUI in IM and go to the 'Robots' tab, locate the robot, and right-click/Remove from there.

Option 3:

You can create an archive package that you can drop on the robots that need to be moved.

You will need the following information in the package:

<controller> overwrite
   domain = (domain_name)
   first_probe_port = 48000
   hub = (hub_name)
   hubrobotname = (robotname)
   hubip = (xxx.xxx.xxx.xxx)
   hubport = 48002
</controller>

Additional Information

Moving hubs or robots to a different UIM domain
https://knowledge.broadcom.com/external/article?articleId=34311