Hi
Can try with these new properties if not yet used
In robot 7.91 and >
Robot failover detection prevents unnecessary robot failovers when the hub misses a single response to a robot request (_status, alive, robotup, or probelist).
The robot is more tolerant of incomplete _status requests. Two new properties can be specified in robot.cfg.
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.
https://docops.ca.com/ca-unified-infrastructure-management-probes/ga/en/alphabetical-probe-articles/controller/controller-release-notes
Original Message:
Sent: 08-05-2019 03:16 AM
From: MADANRAJ SIVAGNANAM
Subject: we found in CA UIM that some of the robots moving from primary to secondary hub automatically without our intervention .
Hi Yu ,
You are saying that , this behaviour is common and will happen in tool !! Is my understanding right ?
Then how to resolve this ? As everytime so many robots are moving here and there among the hubs . I need a solution for this . That is my problem
Regards
AMar
Original Message:
Sent: 08-05-2019 03:05 AM
From: Yu
Subject: we found in CA UIM that some of the robots moving from primary to secondary hub automatically without our intervention .
What is your problem ? The behavior is one of expected to happen within the tool.
Original Message:
Sent: 08-05-2019 03:02 AM
From: MADANRAJ SIVAGNANAM
Subject: we found in CA UIM that some of the robots moving from primary to secondary hub automatically without our intervention .
Hi Yu ,
We are having both primary and secondary hubs running at a time . we don't have a failover like this : if primary goes down then secondary should run . So , when robots are moving from primary to secondary hub and vice -versa without our intervention . so please guide us where and how to find this and fix this .Which logs needed to be checked for this and how to fix this problem ?
Regards
AMar
Original Message:
Sent: 08-05-2019 01:52 AM
From: Yu
Subject: we found in CA UIM that some of the robots moving from primary to secondary hub automatically without our intervention .
Robot will do searching other hub in the same network subnet, by doing broadcast to find out any IP where 48002 listens to.
[Search the subnet for a temporary hub when primary and secondary hubs are unavailable] setting does this behavior.
It is available in controller probe GUI [Setup] - [Nimsoft] - [Secondary HUB]
Original Message:
Sent: 08-05-2019 01:45 AM
From: MADANRAJ SIVAGNANAM
Subject: we found in CA UIM that some of the robots moving from primary to secondary hub automatically without our intervention .
we found in CA UIM that some of the robots moving from primary to secondary hub automatically without our intervention .
Please let us know the reason for this and how to check this where exactly it is going wrong !!!
Regards
AMar