Secondary hub-checking/searching the subnet and reverting to previous robot.cfg setting

Products

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

Issue/Introduction

If I open a controller GUI the Nimsoft tab\Secondary HUB area, "Automatically detect..." is selected by default.

If I then select "Search the subnet...", then unselect "Search the subnet..." the top option changes to "Wait for primary hub to become available", which is what I want.

So I click Apply, and restart the controller.

But the robot.cfg file does not seem to change.

Re-opening the controller GUI shows no change. "Automatically detect" option is back and still checked...

How do I know that the controller will stop searching and picking up random HUBs in the domain? and that the "Wait for primary hub..." option is being used...

Environment

• Release: UIM 20.4
• Component: robot v9.37

Resolution

This is an older GUI bug from robot v7.6x.

The issue is that when reloading the GUI it does not actually reflect the current state of the configuration, it reverts back to the default, but this should not affect the controller's behavior.

You can verify this in the GUI by setting 'Wait for the primary hub to become available...' and then check the robot.cfg which should contain:

   temporary_hub_broadcast = no

As long as this is set to "no" the controller will not keep searching for a hub.

Engineering and Development has confirmed this old GUI 'buglet', and it will not be fixed in IM due to the halt on any further Infrastructure Manager (IM) development.