UMP wasp probes fails to start after domain name change

Products

• NIMSOFT PROBES
• DX Infrastructure Management

Issue/Introduction

In order to connect the legacy system to the new primary controller I changed the domain name of the new system to match the old.  The wasp probes on both UMP's are now failing.

Environment

Release : 9.2.0

Component : UNIFIED INFRASTRUCTURE MGMT

Resolution

-make a backup copy of the wasp.cfg file
-update all occurrences of the domain change in the wasp.cfg file
-remove the connection string from the wasp.cfg (leaving 'connection =' on the line)
-restart the nimbus service on both the primary hub and the UMP robot