As said use a sniffer to see what exactly is send and what comes back from that we can be sure that what Servers Alive is seeing if that's correct or not.
Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lem Bryant Sent: Monday, December 01, 2003 4:42 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Unable to ping Dirk, Yes I used a poor subject line, but the fact remains that SA is giving a false reading on ping tests. Or at least that is my opinion. But like I said in my original posts, I'm looking for suggestions on what to fix. Not that I am blaming SA for the problem. But this list seems like the best place to get help resolving this issue. I can do a ping from a command line. I Send 25 requests and get 25 back, or 100% success. When I do the same with SA, 25 frames, 15 seconds timeout, Second Knock, asking for 80% it fails. If I drop the requirement to 25% it does not fail, but if I can only talk across a high speed line to a piece of equipment that is connected to an OC-48 twenty-five percent of the time I have other issues. Here are the log entries for checks done by SA. OK with a successrate of 52% and an average roundtriptime of 13.7ms OK with a successrate of 48% and an average roundtriptime of 16.7ms OK with a successrate of 52% and an average roundtriptime of 15.6ms The round trip times are consistent with what I see from a command line or other utilities. I do see the occasional lost ping, but nothing near 50%. A typical success rate is 90 to 100%. I hope that clears things up for you a little. Lem -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Dirk Bulinckx Sent: Monday, December 01, 2003 3:27 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] Unable to ping What I don't understand is your "conclusion" (from the subject) : "unable to ping". If there is 40 or 60% failure rate then it's still able to ping, it's just that not all packets are coming back within the calculated time. A "normal" ping from the commandline isn't a good meter to see if you get the same or not. You should also interprete the the numbers that the commandline ping is giving in order to understand. The best would be (but almost impossible unless you have the problem all the time) a trace (netmon/ethereal/sniffer/...) showing the ping that SA does, this will also show the reponse (if any) and then you will see how long it took and understand WHY you get the down and see if it's correct or not. Dirk. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lem Bryant Sent: Monday, December 01, 2003 9:59 AM To: [EMAIL PROTECTED] Subject: 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
