DX Unified Infrastructure Management

 View Only
  • 1.  Best practice to change the Hub IP

    Posted Sep 07, 2017 02:58 PM



    Good day


    We are in process of changing hub IP and almost almost 300 servers are pointing to this Hub.Kindly let us know the best practice/step by step process to change the HUB IP. 

    Hub Robot version:7.80

    Infrastructure Manager:4.10

    UIM : 8.5

    Thanks in Advance


  • 2.  Re: Best practice to change the Hub IP

    Posted Sep 07, 2017 07:37 PM

    I had a similar question few months back and support has provided the below steps for changing the HUB IP


    1. backup hub and robot folders on the remote hub

    2. stop the remote hub

    3. change the IP

    4. delete the file(s) "$nimsoft/hub/security.*"

    5. restart the remote hub

    6. do NOT login to the remote hub until you see that securty.cfg has been updated (hint: size will increase beyond 1K)


    Be aware that robots attached to the remote hub will not know that the IP has changed. It can be helpful to have a temporary hub in place. You move all the robots to the temporary hub by selecting all the robots under the remote hub -> right-click -> Move... in Infrastructure Manager, and change ip address of the remote hub, then move the robots back to the remote hub. Alternately, you can simply edit the robot.cfg for each robot and input the new IP for the "hubip=" field.


    Also, defined tunnels will be affected if the remote hub changes IP-address. You may need to recreate the tunnel connection accordingly.


    NOTE : Verify the steps again with Support before you try, recommended to test in a UAT/DEV environment before you test it on prod 

  • 3.  Re: Best practice to change the Hub IP

    Posted Sep 08, 2017 08:20 AM

    Thank you Phani

  • 4.  Re: Best practice to change the Hub IP

    Broadcom Employee
    Posted Mar 05, 2018 09:39 AM

    Hi team also I did a internal lab and create a article




    1.   stop the nimbus controller at all servers
    2.   make the nimbus robot watcher windows services to start manual
    3.   change the hostname on the windows system
    4.   restart the machine
    5.   rename inside the file robt.cfg and hub.cfg from old name to new name.
    6.   on the wasp.cfg change all entry from old name to new name
    7.   removed all the entries for the CABI on the wasp, if you not remove the wasp probe will not start
    8.   stopped all the hubs
    9.   removed the hub.sds and robot.sds from all hubs( this will be populated automatic again)
    10. make the nimsoft robot watcher windows services to automatic and start.
    11. start all the solution
    12. the new probe address will be populated automatically but will be on red
    13. validated all the probes (security validate) doing right click at once
    14. if the probe after validate still red, deactive
    15. active again.
    16. make sure the queues in the hubs got the new name and working fine. If not adjust the queue if needs.
    17. re install the CABI.

  • 5.  Re: Best practice to change the Hub IP

    Posted Apr 24, 2018 05:16 AM

    Hi Rubens,

    I have a situation where our partner wants to redeploy their installation as they have it all on one VM and want to move to the recommended deployment of 1 VM for UIM, 1 for UMP, 1 for the Db. Do you know if what you have described above will also be valid, to save the settings, for backing up the primary hub, installing it on a new VM and then copying the backed up files over to reconnect everything? The partner doesn't want to loose all of their tunnel connections and have to set them all back up again, so i'm looking for a way to achieve this.