Change the hostname of the DX UIM Server (Primary hub) or Secondary Hub
search cancel

Change the hostname of the DX UIM Server (Primary hub) or Secondary Hub

book

Article ID: 72197

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

This guide contains the steps to update/change the hostname and/or hub name and/or domain of a DX UIM Hub or primary hub, while keeping the same IP address.

 

Environment

  • DX UIM 23.4.*
  • Windows Server

Cause

Guidance

Resolution

NOTE: As a preliminary step, backup the Nimsoft folder (DX UIM Install path) on the systems where the changes will be applied.


Scenario 1: Update the hostname and/or the hub name of the DX UIM Server (Primary hub). The IP of the DX UIM Primary hub and the domain will not be changed.

 

    1. Stop the Nimsoft Robot Watcher service on the DX UIM Server (Primary hub).

    2. Make the Nimsoft Robot Watcher windows services to start manual



    3. Perform the hostname change on the Windows system that hosts the hub.

    4. Reboot the renamed system.



    5. In the DX UIM Server, edit the robot.cfg and hub.cfg files and replace the old hostname entries, from the old name to the new name.


      Eg: Nimsoft/robot/robot.cfg:

      robotname = <newname>
      domain =  <newname_domain>
      hub = <newname_hub>
      hubrobotname = <newname>


      Eg: Nimsoft/hub/hub.cfg:

      domain =  <newname_domain>
      hubname = <newname_hub>


    6. In the hub folder locate the hub.sds.

      If the file is 0kb don't do any change:



      If the hub.sds is >0kb it indicates that there are Static Hubs/Name Services entries. In that case rename the hubs.sds to OLDhubs.sds, upon restart, a new hubs.sds will be created.


    7. Connect to the Operator Console (OC) Server(s) and CABI Server (if any) and Stop the Nimsoft Robot Watcher Service

    8. Edit the wasp.cfg and update all entries that have the old Primary Hub/UIM Server hosntame and/or hub name to the new hubrobot name and hub name. 

      Eg.: Nimsoft\probes\service\wasp\wasp.cfg

      data_engine = /<domain>/<new_hub_name>/<new_hubrobotname>/data_engine
      ems = /<domain>/<new_hub_name>/<new_hubrobotname>/ems
      nas = /<domain>/<new_hub_name>/<new_hubrobotname>/nas

      Etc.

    9. On the DX UIM Server, Make the Nimsoft Robot Watcher Windows service to start back to "automatic". Then Start the Service. 

    10. On the OC Server(s) and CABI Server (if any) Start the Nimsoft Robot Watcher Service
    11. Open Infrastructure Manager (IM) and the new hub hostname and/or hub name will populate.
      NOTE if IM doesn't not connect to the hub, open the hub.cfg and robot.cfg and verify if the changes are reverted. In that case Stop the service and repeat step 5, then start the service again. 

    12. Most of the probe will appear in red and must be validated. Validate all the probes in red. Right click on the probe > Security > Validate:



    13. If the probes appear in RED state even after validating it, Deactivate the probe and Reactivate it. If many probes are validated, but in RED Status, Restart the UIM Server robot by clicking on the robot > restart. Or stop and start the service again.

    14. Review the queues in the primary hub and the on the hubs modified and verify that are connecting and processing data. If they fail, adjust the queue names in all involved hubs.

    15. If there is a duplicated stale robot (usually in yellow state) off the old DX UIM server robot, go to the HUB GUI, go to the Robots tab, right click on the yellow robot and click "Remove"


 

 

 Scenario 2: Update the hostname and/or the hub name of a DX UIM Secondary hub. The IP the hub and the domain will not be changed.



    1. Stop the Nimsoft Robot Watcher service on the Hub where the name change will be performed. 

    2. Make the Nimsoft Robot Watcher windows services to start manual



    3. Perform the hostname change on the Windows system that hosts the hub.

    4. Reboot the renamed system.



    5. In the Hub, edit the robot.cfg and hub.cfg files and replace all the old hostname entries, from the old name to the new name.
       

      Eg: Nimsoft/robot/robot.cfg:

      robotname = <newname>
      domain =  <newname_domain>
      hub = <newname_hub>
      hubrobotname = <newname>


      Eg: Nimsoft/hub/hub.cfg:

      domain =  <newname_domain>
      hubname = <newname_hub>


    6. In the hub folder locate the hub.sds.

      If the file is 0kb don't do any change:



      If the hub.sds is >0kb it indicates that there are Static Hubs/Name Services entries. In that case rename the hubs.sds to OLDhubs.sds, upon restart, a new hubs.sds will be created.


    7. On the HUB Server, Make the Nimsoft Robot Watcher Windows service to start back to "automatic". Then Start the Service. 

    8. Open Infrastructure Manager (IM) and the new hub hostname and/or hub name will populate.

      NOTE if IM doesn't not connect to the hub, open the hub.cfg and robot.cfg and verify if the changes are reverted. In that case Stop the service and repeat step 5, then start the service again. 

    9. Most of the probe will appear in red and must be validated. Validate all the probes in red. Right click on the probe > Security > Validate:


    10. If the probes appear in RED state even after validating it, deactivate the probe and reactivate it. 

    11. Review the queues in the primary hub and the on the hubs modified and verify that are connecting and processing data. If they fail, adjust the queue names in all involved hubs.

    12. If there is a duplicated stale robot (usually in yellow state) off the old hub server robot, go to the HUB GUI, go to the Robots tab, right click on the yellow robot and click "Remove"

Additional Information

Note: In some scenarios, if the robot listed under the renamed hubs show inconsistencies or missing robots, refresh the robot.sds by stopping the service, renaming the robot.sds, then start the service and a new robot.sds will be created. If robots do not show back after this see: After removing a robot.sds file from a UIM hub machines are not populating in IM

Powered by Wolken Software