<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ping response time in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637158#M238552</link>
    <description>Hi Roberto,&lt;BR /&gt;&lt;BR /&gt;what OS is running on the system where you run your ping command? Most likely the problem is on the source of ping, not on the target.&lt;BR /&gt;&lt;BR /&gt;BTW, a very bad statistic in your post:&lt;BR /&gt;&lt;BR /&gt;2227 packets transmitted&lt;BR /&gt;&lt;BR /&gt;7 packets received&lt;BR /&gt;&lt;BR /&gt;Broken network connection?</description>
    <pubDate>Wed, 28 Sep 2005 12:48:43 GMT</pubDate>
    <dc:creator>Torsten.</dc:creator>
    <dc:date>2005-09-28T12:48:43Z</dc:date>
    <item>
      <title>ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637150#M238544</link>
      <description>Hello,&lt;BR /&gt;i'm collecting statistics on response time between two HPUX server using ping.&lt;BR /&gt;&lt;BR /&gt;After ping is running for a lot of seconds, i stop the command and get the min/avg/max response time. But the avg has been notified negative!!!&lt;BR /&gt;&lt;BR /&gt;Which is the algoritm used by ping in order to give the avg result?&lt;BR /&gt;Based on this algoritm, a slow network can imply a negative avg result?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;RV</description>
      <pubDate>Wed, 28 Sep 2005 10:04:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637150#M238544</guid>
      <dc:creator>Roberto Volsa</dc:creator>
      <dc:date>2005-09-28T10:04:02Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637151#M238545</link>
      <description>I'm not sure how an average can be negative.&lt;BR /&gt;&lt;BR /&gt;Can you please post an example of what you are talking about?</description>
      <pubDate>Wed, 28 Sep 2005 10:06:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637151#M238545</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2005-09-28T10:06:45Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637152#M238546</link>
      <description>Were you conducting these experiments in a very large gravitational field -- perhaps near a black hole? Were tachyons involved? Did you see Captain Kirk?</description>
      <pubDate>Wed, 28 Sep 2005 10:12:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637152#M238546</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-09-28T10:12:33Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637153#M238547</link>
      <description>here is an example of results:&lt;BR /&gt;&lt;BR /&gt;64 bytes from 15.156.105.23: icmp_seq=2. time=0. ms&lt;BR /&gt;64 bytes from 15.156.105.23: icmp_seq=3. time=0. ms&lt;BR /&gt;64 bytes from 15.156.105.23: icmp_seq=4. time=0. ms&lt;BR /&gt;64 bytes from 15.156.105.23: icmp_seq=5. time=0. ms&lt;BR /&gt;64 bytes from 15.156.105.23: icmp_seq=6. time=0. ms&lt;BR /&gt;&lt;BR /&gt;----hp.italy.hp.com PING Statistics----&lt;BR /&gt;2227 packets transmitted, 7 packets received, % packet loss&lt;BR /&gt;round-trip (ms)  min/avg/max = 300/-2700/1402</description>
      <pubDate>Wed, 28 Sep 2005 11:40:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637153#M238547</guid>
      <dc:creator>Roberto Volsa</dc:creator>
      <dc:date>2005-09-28T11:40:59Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637154#M238548</link>
      <description>Check for a duplicate IP address for 15.156.105.23. I've seen crazy numbers in ping when there are responses from multiple machines to a single ping. Use arp -a to see what the MAC address is for 15.156.105.23 and verify on that server that it is indeed the same MAC.</description>
      <pubDate>Wed, 28 Sep 2005 11:47:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637154#M238548</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-09-28T11:47:25Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637155#M238549</link>
      <description>Ciao Roberto,&lt;BR /&gt;&lt;BR /&gt;I read somewhere months ago that if average value of ping is negative, the destination address machine could have some operative system problem...&lt;BR /&gt;&lt;BR /&gt;But regard to this wait some guru of the forum for further information...&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Best wishes,&lt;BR /&gt;Alex</description>
      <pubDate>Wed, 28 Sep 2005 11:47:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637155#M238549</guid>
      <dc:creator>Alessandro Pilati</dc:creator>
      <dc:date>2005-09-28T11:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637156#M238550</link>
      <description>What version of HP-UX?&lt;BR /&gt;&lt;BR /&gt;Do a:&lt;BR /&gt;&lt;BR /&gt;# whence ping&lt;BR /&gt;&lt;BR /&gt;And make sure you are using /usr/sbin/ping.&lt;BR /&gt;&lt;BR /&gt;Also do a:&lt;BR /&gt;&lt;BR /&gt;# what /usr/sbin/ping&lt;BR /&gt;&lt;BR /&gt;And post the results.  You may need a patch.</description>
      <pubDate>Wed, 28 Sep 2005 11:59:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637156#M238550</guid>
      <dc:creator>Patrick Wallek</dc:creator>
      <dc:date>2005-09-28T11:59:56Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637157#M238551</link>
      <description>Here is one source for ping but there doesn't appear to be a path that leads to a negative computation --- if I dismiss integer overflow. Note that the tvsub() function out is assumed to be &amp;gt;= in. If that assumption were violated then strange values would be expected. I would be tempted to compile this source (since you could probe it) and look for problems.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.ping127001.com/pingpage/ping.html" target="_blank"&gt;http://www.ping127001.com/pingpage/ping.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;NOTE: This is not the HP-UX source for ping.&lt;BR /&gt;&lt;BR /&gt;I suspect that your fundamental problem is such huge packet losses</description>
      <pubDate>Wed, 28 Sep 2005 12:29:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637157#M238551</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2005-09-28T12:29:03Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637158#M238552</link>
      <description>Hi Roberto,&lt;BR /&gt;&lt;BR /&gt;what OS is running on the system where you run your ping command? Most likely the problem is on the source of ping, not on the target.&lt;BR /&gt;&lt;BR /&gt;BTW, a very bad statistic in your post:&lt;BR /&gt;&lt;BR /&gt;2227 packets transmitted&lt;BR /&gt;&lt;BR /&gt;7 packets received&lt;BR /&gt;&lt;BR /&gt;Broken network connection?</description>
      <pubDate>Wed, 28 Sep 2005 12:48:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637158#M238552</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2005-09-28T12:48:43Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637159#M238553</link>
      <description>HI&lt;BR /&gt;&lt;BR /&gt;OS is HPUX 11i&lt;BR /&gt;&lt;BR /&gt;The network is really bad but i wrote wrong number. Percentage of lost packets is less than 1%</description>
      <pubDate>Wed, 28 Sep 2005 12:59:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637159#M238553</guid>
      <dc:creator>Roberto Volsa</dc:creator>
      <dc:date>2005-09-28T12:59:17Z</dc:date>
    </item>
    <item>
      <title>Re: ping response time</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637160#M238554</link>
      <description>If the network is bad, then I would assume that oddball numbers for ping are normal. If you can't fix the network then it will be quite difficult to get meaningful measurements. Since the travel time is 0 ms, I would assume that this is a local network. Perhaps part of the problem is wih rogue computers (PCs?) with dupliate addresses and badly misconfigured networking, not something that I would ever allow on a prodution network.</description>
      <pubDate>Wed, 28 Sep 2005 14:24:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/ping-response-time/m-p/3637160#M238554</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-09-28T14:24:17Z</dc:date>
    </item>
  </channel>
</rss>

