The subnet that the current secondary hub exists on will be going away, and the hub will need to be re-ip'd to the new subnet it will be placed on.
What are the correct steps to making the IP address change on a secondary hub as smooth as possible with minimal downtime?
UIM Server: Any version
robot: Any version
hub: Any version
1. All robots attached to the secondary hub will not know that the IP has changed. To control where these robots move to when the secondary hub is restarted, if is recommended that a temporary hub be used to control where they move to. It is possible to move all the robots to the temporary hub by selecting each of the robots under the secondary hub in Infrastructure Manager right-click the robot, select Move..., then select the temporary hub.
2. Stop the Nimsoft Robot Watcher service on the secondary hub.
3. Using a text editor, change the IP address for the following keys in the robot.cfg file on the secondary robot:
hubip = <new IP address>
robotip = <new IP address>
Save the changes.
4. Delete the following files from the <installPath>\Nimsoft\hub directory:
These will be rebuilt/populated once the hub comes back on-line and established communications with the other hubs in your UIM domain.
5. Make the IP address change on the secondary hub system and reboot the system.
6. Do NOT login to the remote hub from Infrastructure Manager until the securty.cfg has been updated (hint: size will increase beyond 1K)
7. If there are any tunnel connections defined on this secondary hub, it may be necessary to recreate the tunnel connections because of the IP address change.
8. If there are any static routes defined to this secondary hub on any of the other hubs in the UIM domain, delete them from the secondary hubs then recreate them to get the new P address.
9. If robots were moved to a temporary hub as specified in step #1, move them back to the secondary hub in the same manner.