What is the cause of an Alarm if a server robot goes down?

Document ID : KB000034254
Last Modified Date : 14/02/2018
Show Technical Document Details

 

Introduction: 

If a robot becomes inactive for any of several reasons the hub it reports to will generate an alarm.

Question: 

What is the cause of an Alarm if a server robot goes down?

Answer: 

1. When a robot(server) is rebooted, or if a robot has been inactive for certain time, based on "Hub update interval" setting in Controller->Setup->Misc. section, that hub will generate a robot inactive alarm.

2. When a server is being rebooted and if it has robot installed with cdm probe, cdm will generate a "Warning" severity alarm like the following:

User-added image


3. If a robot is inactive for "Hub update interval" x 1.5 times, hub will generate a "Critical" alarm like the following:

User-added image

Additional Information:

"Hub update interval" determines the time when hub will generate the robot inactive alarm. When a robot comes up, it sends an internal message to the hub with its status and the next time the hub should get the same status message from the robot based on "Hub update interval" setting - which is (by default) 15 minutes. The hub expects to hear again from robot approximately around the "Hub update interval" x 1.5 (e.g: 15 x 1.5 = 22.5 minutes) and if it doesn't, then the hub does a robot check-in to check robot status. If robot is non-responsive to the hubs robot check-in, then the hub will generate "Robot <robot name> is inactive" alarm.


In either case, an alarm will be generated and visible in the alarm console (NMS Manager, SDP, UMP) and a nas auto operator can be configured to send an email notification to specified recipients.