ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

UIM | Multiple Robot not reporting to Secondary Hub Servers after primary failover

book

Article ID: 212482

calendar_today

Updated On:

Products

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

Issue/Introduction

Multiple Robot not reporting to Secondary Hub Servers after primary hub failover

 

Cause

"hub_update_interval" value set to 7200 seconds or 2 hrs

Environment

Release : 20.3

Component : UIM - HUB

Resolution

The hub deletes the robot entries for temp robots if there is no heartbeat received within 30 minutes.

The robots in the setup having "hub_update_interval" value to 7200 seconds or 2 hours. So after successful failover, the robot reaches to its secondary hub but it does not send the heartbeat message to the hub within 30 minutes.

Robot starts sending heartbeats after 2 hrs as "hub_update_interval" value is 7200 seconds or 2 hrs.

As these robots are temporary to this hub, this hub starts dropping robots after 30 minutes from its robot list. For regular robots there is no such restriction in hub that's why all the robots working fine when they are attached to its primary hub.

To resolve the issue reduce the "hub_update_interval" value to below 1800 in all the robots so that the secondary hub gets the heartbeat from all the temp robots within 30 minutes and does not drop them.

To edit the "hub_update_interval" key:

- From the IM or Admin Console select the affected robot then Raw Configure

- Select Controller, then locate the "hub_update_interval" key and edit 

- Set the new value then OK

Infrastructure Manager

Admin Console

Attachments