DX Unified Infrastructure Management

  • 1.  Unable to discover hubname while installing UIM Agent

    Posted Jul 11, 2018 02:11 AM

    Hi,

     

    I unable to discover hubname while installing UIM agent in test environment. Please look into this issue and try to provide the resolution for the same asap. Kindly Persist..!!

     

    Regards

     

    Pushpa



  • 2.  Re: Unable to discover hubname while installing UIM Agent

    Posted Jul 11, 2018 05:50 AM

    It seems you are trying to install a uim robot on a test server, you can put in the hub ip address to which you want the robot to report to. 

     

    bidirectional communication on ports in range 48000-48050 is required between the hub and robot to work properly. Please check for any communication problems as well.

     

    If this is not the case then you may need to explain the problem in detail so community members can understand and help you out.



  • 3.  Re: Unable to discover hubname while installing UIM Agent

    Posted Jul 11, 2018 07:31 AM

    Hi Hitesh,

     

    I have given the UIM primary hub ip and also the port number 48000 while installing UIM agent on windows server but still after UIM agent installation when I am running uim controller in the task bar, the hub ip is missing and not showing in the infrastructure manager.

     

    Regards

     

    Pushpa



  • 4.  Re: Unable to discover hubname while installing UIM Agent
    Best Answer

    Posted Jul 11, 2018 08:15 AM

    Well, it seems to be a communication error. check the bidirectional communication by telnet on port 48000 to and from primary hub to robot and vice versa.

    Also, you may look into the controller logs. What version of robot you are trying to install on on which OS?



  • 5.  Re: Unable to discover hubname while installing UIM Agent

    Broadcom Employee
    Posted Jul 11, 2018 08:21 AM

    Hi 

    Stop the  nimsoft robot watcher service

    Manually modify / add  any information if missing in robot.cfg .Example 

    first_probe_port = 48000
    robotip = ***.***.***.***
    hubip = ***.***.***.***
    loglevel = 3
    logsize = 10000

     

    start the nimsoft watcher service 

    Check for errors in controller logs

    Check in task manager if controller/spooler/hdb proceses started

     

    From robot to hub

    telnet <hub-ip> 48002

     

    From hub to robot  

    telnet < robot-ip> 48000

    telnet <robot-ip> 48001