Secure Hub reverts to non-secure after NAS deployment in DX UIM
search cancel

Secure Hub reverts to non-secure after NAS deployment in DX UIM

book

Article ID: 454480

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Deploying the NAS probe to a secure secondary hub running UIM 23.4.6 may cause the hub to revert to non-secure mode in Infrastructure Manager (IM). 

Symptoms:

  • Immediately after deploying the NAS probe, the hub icon in IM changes from secure (padlock) to non-secure.
  • Connected secure robots lose communication with the hub.
  • The installed.pkg file on the secondary hub shows an empty version field for the hub package.

Environment

  • DX Unified Infrastructure Management (UIM) 23.4.6
  • Secondary Hub installed via Infrastructure GUI installer
  • Secure Hub configuration

Cause

The 23.4.6 GUI installer fails to write the hub version into the installed.pkg file. When a probe with a hub dependency (like NAS requiring hub 5.81+) is deployed, distsrv checks installed.pkg. Finding no version, it assumes the dependency is missing and forces a redeployment of the standard (non-secure) hub package, overwriting the secure configuration.

Resolution

 The issue is resolved in Infrastructure Robot version 23.4.8. The 23.4.8 GUI installer correctly populates the version field.

Workaround for 23.4.6: If already running a 23.4.6 secondary hub installed via the GUI, follow these steps before converting it to a secure hub:

  1. Redeploy the hub 23.4.6 package manually from the archive to the secondary hub.
  2. Verify that the version number is now present in the installed.pkg file.
  3. Proceed with the secure hub conversion.

Additional Information

Secure Hub Release Notes