Hub probe on the primary hub will not start - controller error - NO CONTACT (communication error)

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)
• CA Unified Infrastructure Management On-Premise (Nimsoft / UIM)
• CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

The probe on the primary hub is not getting started and we are not able to connect to primary hub.

Error captured in the controller.log

Controller: hub <PrimartyHubNane <serveripaddress> NO CONTACT (communication error)
Controller: nimRequest: SessionConnect failed: - <serveripaddress> :48002
Controller: hub <PrimartyHubNane <loopback address> NO CONTACT (communication error)
Controller: nimRequest: SessionConnect failed: - <loopback address> :48002

Environment

UIM 20.4+

Resolution

This issue is sometimes seen when the controller.cfg is corrupted.

Option 1. Restore the controller.cfg from a backup followed by a Nimsoft service restart

Option 2.  Followed steps below if the controller.cfg has the hub section

A. Edit controller.cfg on the primary hub

B. Locate the <hub> section

C. Delete the entire magic_key line from the <hub>section

D. Move controller.cfg to the nimsoft/robot/changes folder

E. Restart the Nimsoft Robot Watcher Service on the primary hub

 Note: The controller will process the cfg in the changes folder, creates a new magic key for the hub probe, and move the controller.cfg back to robot folder.

F. Restart the Nimsoft service

G. Run the Security Validate probe option on all probes that are in a failed state.

Additional Information

DX UIM probe configuration file corruption

CA UIM - hub process does not start automatically controller.cfg missing probe sections or empty