<?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: incomplete headers in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/incomplete-headers/m-p/3879452#M546391</link>
    <description>You probably can clear the statistics with:&lt;BR /&gt;&lt;BR /&gt;lanadmin&lt;BR /&gt;lan&lt;BR /&gt;clear&lt;BR /&gt;&lt;BR /&gt;UDP packets can be damaged in the transfer, so checksums will not match. For "socket overflows" see:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=94276&amp;amp;admit=-682735245+1160691519079+28353475" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=94276&amp;amp;admit=-682735245+1160691519079+28353475&lt;/A&gt;</description>
    <pubDate>Thu, 12 Oct 2006 17:19:56 GMT</pubDate>
    <dc:creator>Ivan Ferreira</dc:creator>
    <dc:date>2006-10-12T17:19:56Z</dc:date>
    <item>
      <title>incomplete headers</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/incomplete-headers/m-p/3879451#M546390</link>
      <description>Hi!&lt;BR /&gt; I have a server with UNIX hpux 11.11 version 1 and I run a command "netstat -p udp"  the output is:&lt;BR /&gt;&lt;BR /&gt;2064 incomplete headers&lt;BR /&gt;175 bad checksums&lt;BR /&gt;1904 socket overflows&lt;BR /&gt;&lt;BR /&gt;what does mean it? and How I can erase it?&lt;BR /&gt;&lt;BR /&gt;Thank's</description>
      <pubDate>Thu, 12 Oct 2006 16:59:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/incomplete-headers/m-p/3879451#M546390</guid>
      <dc:creator>Marcos Tinoco García</dc:creator>
      <dc:date>2006-10-12T16:59:28Z</dc:date>
    </item>
    <item>
      <title>Re: incomplete headers</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/incomplete-headers/m-p/3879452#M546391</link>
      <description>You probably can clear the statistics with:&lt;BR /&gt;&lt;BR /&gt;lanadmin&lt;BR /&gt;lan&lt;BR /&gt;clear&lt;BR /&gt;&lt;BR /&gt;UDP packets can be damaged in the transfer, so checksums will not match. For "socket overflows" see:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=94276&amp;amp;admit=-682735245+1160691519079+28353475" target="_blank"&gt;http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=94276&amp;amp;admit=-682735245+1160691519079+28353475&lt;/A&gt;</description>
      <pubDate>Thu, 12 Oct 2006 17:19:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/incomplete-headers/m-p/3879452#M546391</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2006-10-12T17:19:56Z</dc:date>
    </item>
    <item>
      <title>Re: incomplete headers</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/incomplete-headers/m-p/3879453#M546392</link>
      <description>IIRC it means pretty much what it says - there were datagrams arriving which didn't have complete UDP headers.  Given a UDP header is only 8 bytes in size it is rather a feat.  I suspect that if you were to look at the IP stats you would see a bunch about IP fragmentation too.&lt;BR /&gt;&lt;BR /&gt;You might want to look at your lanadmin statistics for your NIC(s) and see if there are any FCS errors or _late_ collisions being reported that might suggest a duplex mismatch or other problems with your physical network.</description>
      <pubDate>Fri, 13 Oct 2006 19:34:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/incomplete-headers/m-p/3879453#M546392</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2006-10-13T19:34:09Z</dc:date>
    </item>
  </channel>
</rss>

