UIM Robot failover to secondary hubs timeouts and settings

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

How long does a robot wait when it loses contact with its own hub before moving to a secondary hub? 

Is it possible to delay the interval between losing contact and actually performing the move to a secondary hub defined in the robot.cfg? 

This KB discusses the robot settings that determine secondary hub failover timings.

Environment

Release : UIM 20.x and 23.4
Component : UIM - CONTROLLER ROBOT  7.91 and above

Cause

Guidance

Resolution

After robot version 7.91 it is possible to configure how long after losing contact with the hub the robot starts the failover to a secondary hub (if a secondary hub is configured)
The 2 keys below can be added or edited in the robot.cfg (CTRL+SHIFT > Raw configure on the controller probe in IM) 

 

robot_status_check_interval

Controls how frequently the robot polls the hub with a _status request.
Previously, this was not configurable, and the polling occurred at a medium timeout, approximately every 11 seconds.
Use this property to approximately specify the new polling interval. The interval is approximate because the status check occurs in
the medium timeout that exceeds the requested interval. For example,
if the robot_status_check_interval is set to 30 seconds, polling will occur every 33 seconds (3 x 11 second medium timeout). 
The default value is 60 seconds, which equates to a status check every 66 seconds.

robot_failover_count

improves the resiliency of the robot. In the past, the robot failover mechanism was invoked when
one _status request to the hub failed. Use this property to specify the number of consecutive _status
failures that must occur before initiating robot failover to a secondary hub. Default, 2.

 

This is documented in the Revision History of the controller Release Notes

controller Release Notes

Additional Information

Other 2 options related to robot failover are the following:

With the option below enabled the robot won't be moved at all: 

 

And unchecking the box below avoids the robot to look for any other available temporary hub (if the second is not available)

Related KBs:

UIM | Multiple Robot not reporting to Secondary Hub Servers after primary failover (broadcom.com)

hub configuration - timeout, retry and other settings (explained) (broadcom.com)