after renaming a hub, error in hub.log reports possible duplicate hub

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

You have recently renamed a Hub in your environment, and the old name is still present in Infrastructure Manager/Admin Console.  The new name is not showing up in either interface.

In the hub.log you see a message like:

Oct  6 22:27:59:185 [140545056945984] 1 hub: hubinfo_update - possible duplicate on (ip address) /Domain/NewHubName <> /Domain/OldHubName

 

Environment

DX UIM - Any Version
hub recently renamed

Cause

This is normal behavior when a hub has been renamed, as there will be an old hub record in the hub lists maintained by each hub, and until that old record is removed, the new record cannot be inserted.

Resolution

This problem will normally automatically resolve within approximately one hour, as the hub with the old name will no longer be active, and eventually the hubs will remove it from their hublists due to inactivity.  As soon as it is removed, the newly renamed version will be allowed in and begin to propagate.

There is a configuration key in the hub.cfg which can be added to the <hub> section that controls how long it takes for an inactive hub to be removed:

hublist_temp_timeout = ####

When this key is not present in hub.cfg the default value is 1800 and this value is expressed in seconds; 1800 seconds is 30 minutes, so after a hub has been inactive for 30 minutes, it will expire and be removed. It will then be re-added on the next hublist sharing cycle, which happens every 10 minutes.

So, ordinarily, this behavior and the associated log error should persist only for 40 minutes in most cases.   In some cases depending on the exact timing it can take up to an hour to resolve.

Broadcom does not recommend increasing or decreasing the hublist_temp_timeout value unless directed by Support as this influences several behaviors around hub list sharing and can cause instability.