DX Unified Infrastructure Management

Hi Guys,

I have received Robot Inactive alerts when Nimsoft agent moved from primary hub to seconday Remote\Monitoring Hub.

As per the logs it seems that servers are connecting and disconnecting with the hub.

Logs:

Oct 28 02:53:39:686 [1720] Controller: hub HUB1(Hub1 IP Address) NO CONTACT (communication error)
Oct 28 02:53:39:780 [1720] Controller: Hub HUB2(Hub2 IP Address) contact established
Oct 28 02:53:39:795 [1720] Controller: restart_all_probes  Restart probes other than hub, controller, spooler
Oct 28 02:53:53:958 [1720] Controller: restart_all_probes  Finished restart probes other than hub, controller, spooler
Oct 28 03:14:38:082 [1720] Controller: checkin - from PRIMARY, move back (/Domain/Hub/Primary HUB1/hub)
Oct 28 03:14:38:082 [1720] Controller: Hub HUB1(Hub1 IP Address) contact established
Oct 28 03:14:46:097 [1720] Controller: restart_all_probes  Restart probes other than hub, controller, spooler
Oct 28 03:14:58:595 [1720] Controller: restart_all_probes  Finished restart probes other than hub, controller, spooler
Oct 28 03:15:00:611 [1720] Controller: hub HUB1(Hub1 IP Address) NO CONTACT (communication error)
Oct 28 03:15:00:611 [1720] Controller: Hub HUB2(Hub2 IP Address) contact established
Oct 28 03:15:00:611 [1720] Controller: restart_all_probes  Restart probes other than hub, controller, spooler
Oct 28 03:15:09:547 [1720] Controller: restart_all_probes  Finished restart probes other than hub, controller, spooler
Oct 28 03:38:01:402 [1720] Controller: checkin - from PRIMARY, move back (/Domain/Hub/Primary HUB1/hub)
Oct 28 03:38:01:418 [1720] Controller: Hub HUB1(Hub1 IP Address) contact established
Oct 28 03:38:03:411 [1720] Controller: restart_all_probes  Restart probes other than hub, controller, spooler
Oct 28 03:38:15:993 [1720] Controller: restart_all_probes  Finished restart probes other than hub, controller, spooler

I am creating a batch file to check the communication (Telnet) issue between hub to robot.

Please suggest to find the RCA and resolve this issue.

Thanks in advance,

IK

It would be nice, that when a robot moves to the 2nd hub, that both hubs synchronizes, that 1st hub knows that robot is only moved and 1st hub don't need to send out an alarm.

This would be nice but currently not implemented in the hub.

@Imran you will need to check with your network team as to why the robot can not communicate to its primary hub and resolve that issue.

Currently this is functioning as designed as the hubs do operate independently.

Is there an option, that a controller checks when connected to the secondary hub, if the primary hub is again available and switch back to him. At the moment the robot stays as long connected to the secondary hub as the secondary hub is available. It would reduce the number of false alarms, if our primary hub is only not available for a minute when a connection reset is performed.

The robots should move back to the primary once it is detect that it is back up.

You can change the time out value in the robot controller as to how long it waits before moving to secondary.

I usually set this to at least 90 seconds if not 120.

Once the robot moved to the 2nd hub, it stays there also when primary hub is back.

Can you tell me which parameter in controller sets the time out value for the move to secondary hub in seconds as you describe?

Logically it should not generate any alert if both hubs are in sync. What i found here is that the NAS on secondary hub was deactivated. So i enabled the NAS now and there are not alerts showing as of now.

However i have notice one thing. There were 3 Nimsoft agents on the secondary hubs connected properly but showing disconnected and red in primary hub and 3 robot inactive alerts on the console too. I think there is some problem in the communication somewhere.

Regards,

Imran K