A whole new status for this seems a bit unnecessary. I have a similar set up using multiple pings and dependencies.
If ping1 frames received in less than 2000ms then up else down (name this one Internet) if ping2 (which depends on ping1 being up) receives frames in less than 200 ms then up else down(Name this one Internet Slow) Ping 2 would not run if ping1 is down therefore it is effectively between 200 ms and 2000ms that creates a down. So you would get a warning at 500 MS that your "internet slow is down". Even without explanation to other admins I think that is is clear that things are slow and not down. If pings take less than 200 MS then all is well. If pings take more than 2000 ms then warning will be "Internet is Down and all hell will break loose." Jason Passow Network Administrator Mississippi Welders Supply http://www.mwsco.com (http://www.mwsco.com) [email protected] (mailto:[email protected]) ph: (507) 494-5178 fax: (507) 454-8104 -------------------------------------------------------------------------------- From: Heath Abbate [mailto:[email protected]] To: Servers Alive Discussion List [mailto:[email protected]] Sent: Mon, 19 Dec 2011 10:30:26 -0600 Subject: RE: [SA-list] Latency check? Right on the money Chris. -----Original Message----- From: Servers Alive Discussion List [mailto:[email protected] (mailto:[email protected])] On Behalf Of Chris Mang Sent: Monday, December 19, 2011 7:31 AM To: Servers Alive Discussion List Subject: RE: [SA-list] Latency check? Dirk, I think I know what Heath is asking for, so I'll make a "feature request". I suggest a ping response range with the ability to set the "fast" and "slow" ends of the range. If the response is received faster than the "fast" end, the item is UP. If the response is within the range, the item is "LATENT". If the response is received slower than the "slow" end, the item is DOWN. I guess this means a new status too. In your example: All frames are received in less than 200ms -> UP If one of the frames takes more than 200ms but less than 2000ms -> LATENT If one of the frames takes more than 2000ms -> DOWN Does that make sense, and would it be possible? Chris Mang>> Senior Security Administrator JDA Software Group, Inc. -----Original Message----- From: Servers Alive Discussion List [mailto:[email protected] (mailto:[email protected])] On Behalf Of Dirk Bulinckx Sent: Sunday, December 18, 2011 3:01 PM To: Servers Alive Discussion List Subject: RE: [SA-list] Latency check? That's how the ping check works. For example 1 second timeout 5 frames 100% should response if one of the frames takes more then 200ms ->DOWN Dirk Bulinckx. Network Monitoring by Servers Alive - http://www.woodstone.nu (http://www.woodstone.nu) DNS Hosting with ipv4 and ipv6 on http://www.stellardns.com (http://www.stellardns.com) -----Original Message----- From: Servers Alive Discussion List [mailto:[email protected] (mailto:[email protected])] On Behalf Of Heath Abbate Sent: Sunday, December 18, 2011 9:01 PM To: Servers Alive Discussion List Subject: [SA-list] Latency check? Doable in Salive? I would like to ping a host and if the latency for the round trip exceeds a certain value then get notified. The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is confidential and exempt from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer. Thank you. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. The contents of this message, together with any attachments, are intended only for the use of the individual or entity to which they are addressed and may contain information that is confidential and exempt from disclosure. If you are not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this message, or any attachment, is strictly prohibited. If you have received this message in error, please notify the original sender immediately by telephone or by return E-mail and delete this message, along with any attachments, from your computer. Thank you. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] (mailto:[email protected]) If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list. To unsubscribe send a message with UNSUBSCRIBE in the subject line to [email protected] If you use auto-responders (like out-of-the-office messages), make sure that they are not sent to the list nor to individual members. Doing so will cause you to be automatically removed from the list.
