Robot inactive alarm but telnet to/from the robot works in both directions

book

Article ID: 5830

calendar_today

Updated On:

Products

NIMSOFT PROBES DX Infrastructure Management

Issue/Introduction

Receiving robot inactive alarm

If you are able to telnet to the robot ip address on port 48000 and also able to telnet from robot to hub on port 48002 but still receive the alarm.

Check the controller logs and look for this type message

Controller: failed to send alive to hub UIMAFDShub(10.x.x.xx) - communication error

But no firewall between Robot and Hub, you can open wireshark if windows or do a TCP dump at Linux to check the request from the hub to the robot and see the results if the robot doesn't reply to the hub request.

Cause

When you have a busy server (have network request) and just one network card, sometimes the network is too busy to reply the get alive from the hub and this causes a communication error in the log, and consequently a robot inactive alarm.

Environment

Any environment with a busy server with many network requests.

Resolution

Add a network card  and configure one for management solution and the other card for a production environment, this way even if the production network card is busy the management network card will reply to the hub request.