Sensaphone IMS-4000 Users manual - Manual (Page 52)

IMS-4000 Manual
50
editing the schedule:
• Click on the All button in the top left corner of the grid to enable/disable the entire week.
• Click on the day buttons down the left side of the grid to enable/disable entire days
• Click on the hour buttons across the top of the grid to enable/disable entire hours
• Drag the mouse over portions of the grid to enable/disable specific hours/days
Timeout: If the monitored IP address does not respond within this period of time, then the ping is considered a failure. If
the number of consecutive failures exceeds the number of Retries then a Ping Timeout alarm is tripped.
Retries: This is the number of times the monitored IP address is pinged after a failure, before a Ping Timeout alarm is
tripped.
Alarm Class: Click the drop-down arrow and select the appropriate class for this type of alarm. If you prefer you can create
your own classes on the Class Setup screen to group certain types of alarms.
Custom Voice: Click the drop-down arrow and select the custom voice message you would like assigned to this IP Alarm.
Voice messages can be recorded on your PC and uploaded into the IMS-4000 on the Voice screen.
Reset Time: This is the time allowed for an acknowledged alarm’s fault condition to be corrected before the IMS-4000 resets
(reactivates) the alarm and begins the message delivery process all over again. The minimum reset time is 30 minutes.
Alarm on Return-to-Normal: When this feature is enabled, the unit will send a message (or messages) when an IP device
goes from a Ping Timeout state to a Responding state. The person who acknowledged the alarm—in addition to all Inform
Only contacts in the alarm class—will receive the Return-to-Normal message.
SNMP Trap Level: When sending alarm messages via SNMP, this sets the priority of the SNMP trap. The choices are Major
or Minor.
Note: See the previous section, “Alarm Response via the PowerGate, PowerGate2, or Camera” for information on
responses to alarms via PowerGates or Cameras.
alarM loGiC
Network devices are monitored by the IMS-4000 by pinging/connecting to programmed IP addresses about once a minute.
The unit will only attempt to ping/connect to devices which are Enabled by the Schedule. Each time the network device
responds, the IMS-4000 updates the Last Response time. A time limit for responding is assigned to each IP Alarm to deter-
mine if the device is functioning properly. This time limit is called the ping Timeout. If a network device does not respond
within this time period, the IMS-4000 will count this as a ping failure. You can program the IMS-4000 to try to ping/con-
nect to the network device several times before tripping an alarm. The ping Retries deter mines how many times the IMS-
4000 will try to ping/connect to the device before sending an alarm. An alarm will only occur if the device fails to respond
to consecutive ping attempts. Once a successful response is received, the failure counter will reset. For example: If the ping
Retries is set to 3, then the IMS-4000 must fail to ping/connect to the device 4 times in a row (initial attempt + 3 retries) to
trip an alarm. If the device were to respond after the second attempt, then the failure counter would reset, thus requiring
four subsequent successive failures to trip an alarm. Once an alarm is recognized, the Last Alarm time will be updated.
A dependency device (IP address) can be programmed for each IP Alarm. This is used to prevent numerous alarms from
occurring when common network infrastructure problems arise. If the dependency device fails, then all IP alarms that
have this dependency will be temporarily disabled from sending alarms until the dependency device returns to normal (e.g.
starts responding to ping/connect requests). When an IP Alarm’s dependency is not responding, the status for the IP Alarm
will be shown as “IP route down.” It is recommended that the dependency device be programmed such that it will go into
alarm before any other devices. You can achieve this by setting the number of Retries for the dependency device to a lower
value than the IP Alarms which rely on this device.
In summary, for an IP Alarm to be dispatched, the following criteria must be met:
a) The IP Alarm must be enabled—as configured through the schedule.
b) It must have failed to respond to consecutive ping/connect requests and exceed the number of retries.
c) It must be a member of a class.
d) There must be one or more user profiles which include this class.
Once the alarm is dispatched, the alarm delivery process begins. If any of the contacts are programmed as Until
Acknowledged, then the Last Ack time will update when the alarm has been acknowledged. In the case where all contacts are
set to Inform Only, the Last Ack time will update immediately after the alarm occurs.