I would advise to raise the timeout to 2 or 3 times # of frames. We have one telephone line here which has some heavy use now and then. At those times we have round trip times of more than 2 secs. So it takes about 10 secs to get 5 frames thru. We always had false errors reporting the line being down but the line was only in heavy use. I raised the timeout to 10, 5 frames, 60% success rate and never got a false error message after that.
You might as well consider second knock or raising timeout to 15. Oliver -----Urspr�ngliche Nachricht----- Von: Lem Bryant [mailto:[EMAIL PROTECTED] Gesendet: Montag, 1. Dezember 2003 09:59 An: [EMAIL PROTECTED] Betreff: RE: [SA-list] Unable to ping I've been using SA for a year or two now. I understand the way it works. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dirk Bulinckx Sent: Sunday, November 30, 2003 11:51 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Unable to ping This shows that SA is able to ping. Maybe you're not understanding the way it works... (and the doc isn't 100% clear on it either). Example: timeout 5 seconds 10 frames 75% successrate SA will send 10 frames and each of them should get a response within 5s/10=.5s If we get the response we will internaly flag the frames as being OK. (the next frame is send AFTER the timeout of the previous OR when the previous gets back). After the 10 frames we will "calculate" the % of frames that came back within time and see if that fits the given rule (75%) and based on this give an OK or DOWN. Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lem Bryant Sent: Sunday, November 30, 2003 11:12 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Unable to ping The log says that it is a success rate problem. On the last 2 checks one failed at 60% and the other at 40%. I don't have a problem with timeouts from the command line. The system has one NIC. I've tried both hostname and IP. SA is running as an application. Thanks, Lem -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dirk Bulinckx Sent: Sunday, November 30, 2003 3:49 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Unable to ping What exact message in the logfile? Does the system have more then one NIC? Are you ping a hostname or an ip address? Are you running SA as service or as application? Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lem Bryant Sent: Sunday, November 30, 2003 10:00 PM To: [EMAIL PROTECTED] Subject: [SA-list] Unable to ping Hello all, I am running SA 4.0.1376 Enterprise on a Win XP Pro machine. I have checks setup to check inside and outside of my local network. Everything works as expected except for external ping tests. I can ping the external machine from a windows command line, but SA will not complete the check. If I could not ping from the command line I would suspect my firewall, but since I can I really don't know where to start. I checked the archives and saw a similar problem in January this year, but it did not have a resolution posted. If anyone has an hints they would be greatly appreciated. Thanks, Lem To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
