If there is a backup copy of controller.cfg available, replace the current controller.cfg with the backup and restart the robot service.
If there is no backup copy of controller.cfg available, then follow these steps:
- Replace the corrupted controller.cfg with a copy from any other hub (You can use the attached sample_controller.cfg if you do not have a backup copy. If you are using Linux you will need to edit this file and remove the ".exe" from the "command = probename.exe" for all the probes listed).
- Remove all lines which start with magic_key
- Move (don't copy) controller.cfg to $NIMROOT\robot\changes folder
- Restart robot service.
There should now be a new controller.cfg in $NIMROOT\robot folder and at least controller, hub probes should be active and green in Infrastructure Manager.
Note: You will probably see the following indicating problems with other probes.?
This particular icon in IM indicates a problem with the magic keys associated with the probes in your controller.cfg.? When you start the nimsoft service, a checksum comparison is done between what is in the controller.cfg and what is stored in the probe binary.? If they don't match, then you will see these icons.? Follow the next instructions to generate new magic keys.If there is at least ONE directly connected hub on the same network as the primary hub:
- Login to the secondary hub using Infrastructure Manager
- On the primary hub, only the controller will be up and it will automatically attach to the nearest/secondary hub as it is running as a robot only. If it doesn't show up and attach to the secondary hub, use Connect Robot tool in Infrastructure Manager to attach the primary hub robot to the secondary hub.
- Once, you have the primary hub robot attached to secondary hub, validate the hub probe by right clicking on the hub probe and then select Security->Validate. After the hub probe is active it will detach from secondary hub and will take the hub role. validate the other probes in the same way as you just did with the hub probe.?
If there is NO directly connected hub on the same network as the primary hub?
If the hub probe is up and running then skip to step 2:
1. Launch a command prompt and navigate to the $NIMROOT\hub folder and execute this command:
hub.exe -d3 -lstdout
This will allow you to login to infrastructure manager.
2. Launch Infrastructure manager and login to the hub.3. Right click on the hub probe, choose security then validate.You will see this prompt:
Once the operation completes, you will see that the hub is up and running.? You can verify that this is the case by running this command:
netstat -an |find "48002"
and you should see a LISTENING?process 48002/tcp
4- Login to hub using IM and validate all probes with red-lock icon: start with distsrv, data_engine, then the rest.
If you check your controller.cfg after validating all probes, you will see entries with magic keys such as this:
Each probe should have a magic key associated with it in the controller.cfg.
This step is needed to make sure that all probes which are actually installed on the system are in sync with what you see in the Infrastructure Manager UI.
- Login to Infrastructure Manager
- Validate any/all red-lock icon probes, if any on the hub
- Cross reference $NIMROOT\probes folder/sub-folders and to the probes showing up in Infrastructure Manager
- Deploy any probe which exists on file-system under \probes\* folder
- Delete any probe which does not exist on file-system under \probes\* folder