After removing a robot.sds file from a UIM hub machines are not populating in IM
search cancel

After removing a robot.sds file from a UIM hub machines are not populating in IM

book

Article ID: 189420

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Robots are not populating in IM after removing a robot.sds file from a UIM hub.

Environment

Release : All
Component : UIM - ROBOT

Resolution

Create a file called robotlistip.txt with a list of the IP addresses of the robots that run under that hub. 
 
An example to get list:
 
select ip from cm_nimbus_robot where hub = '<hubname>'

A batch file can then be created with the following in it to restart the robots under the given hub:

@ECHO OFF
FOR /F "tokens=*" %%A in (robotlistip.txt) do (
pu.exe -u administrator -p <password>  -H %%A -P 48000 _restart
)
PAUSE

This will restart the robots, and they should reappear in IM once they restart.
 
NOTE:
If a robot fails to restart, change the _restart to _stop this will force the controller to restart the robot if a graceful restart command did not work.
_restart does a soft restart of the robot
_stop does a hard restart of the robot

Additional Information

Example of a successful restart:

Jan  5 07:51:49:340 2 pu: _nimInit
Jan  5 07:51:49:345 2 pu: nimCharsetSet() - charset=
Jan  5 07:51:49:352 0 pu: Failed to read a valid probe_crypto_mode from controller. Assuming pre-FIPS and using TWO_FISH
======================================================
Host: 10.11.12.13 Port: 48000 Request: _stop
======================================================

 

If you are using secure bus, the PU command will no longer work and this process will fail. 

May  4 21:41:00:114 2 pu: _nimInit
May  4 21:41:00:119 2 pu: nimCharsetSet() - charset=
May  4 21:41:00:124 0 pu: Failed to read a valid probe_crypto_mode from controller. Assuming pre-FIPS and using TWO_FISH
_command failed: communication error