<?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: clear collision in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016353#M75647</link>
    <description>guess you should try to address the issue rahter than clearing the counters. there are some packet loss happening which is causing this error.&lt;BR /&gt;&lt;BR /&gt;guess you need to monitor your network and try to get this fixed. (and dont ask me how! i dont know)&lt;BR /&gt;-balaji</description>
    <pubDate>Mon, 07 Jul 2003 04:10:17 GMT</pubDate>
    <dc:creator>Balaji N</dc:creator>
    <dc:date>2003-07-07T04:10:17Z</dc:date>
    <item>
      <title>clear collision</title>
      <link>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016351#M75645</link>
      <description>Hi all&lt;BR /&gt;I wonder how to clear the collision packet&lt;BR /&gt;&lt;BR /&gt;eth0      Link encap:Ethernet  HWaddr 00:02:A5:E8:31:26  &lt;BR /&gt;          inet addr:211.230.50.112  Bcast:211.230.50.255  Mask:255.255.255.0&lt;BR /&gt;          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1&lt;BR /&gt;          RX packets:550730 errors:0 dropped:0 overruns:0 frame:0&lt;BR /&gt;          TX packets:484050 errors:0 dropped:0 overruns:0 carrier:205&lt;BR /&gt;          collisions:349 txqueuelen:100 &lt;BR /&gt;          Interrupt:5 Base address:0x3000&lt;BR /&gt;&lt;BR /&gt;collisions:349 ---&amp;gt; how to clear&lt;BR /&gt;&lt;BR /&gt;is there any way to do so?</description>
      <pubDate>Mon, 07 Jul 2003 03:18:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016351#M75645</guid>
      <dc:creator>mw_9</dc:creator>
      <dc:date>2003-07-07T03:18:45Z</dc:date>
    </item>
    <item>
      <title>Re: clear collision</title>
      <link>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016352#M75646</link>
      <description>Collisions are created when network traffic can not get through.  Packets collide.&lt;BR /&gt;&lt;BR /&gt;The stats you see are not important, so long as collisions are not piling up. If they are, they are usually created by problems with your network configuration or physical setup.&lt;BR /&gt;&lt;BR /&gt;ifconfig eth0 down&lt;BR /&gt;&lt;BR /&gt;Then bring the card up, will probably clear the statistic, if not surely a system boot will.  This will not address the root cause of the collision.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Mon, 07 Jul 2003 03:53:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016352#M75646</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2003-07-07T03:53:50Z</dc:date>
    </item>
    <item>
      <title>Re: clear collision</title>
      <link>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016353#M75647</link>
      <description>guess you should try to address the issue rahter than clearing the counters. there are some packet loss happening which is causing this error.&lt;BR /&gt;&lt;BR /&gt;guess you need to monitor your network and try to get this fixed. (and dont ask me how! i dont know)&lt;BR /&gt;-balaji</description>
      <pubDate>Mon, 07 Jul 2003 04:10:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016353#M75647</guid>
      <dc:creator>Balaji N</dc:creator>
      <dc:date>2003-07-07T04:10:17Z</dc:date>
    </item>
    <item>
      <title>Re: clear collision</title>
      <link>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016354#M75648</link>
      <description>Hello!&lt;BR /&gt;&lt;BR /&gt;If you mean clean collisions from the ifconfig&lt;BR /&gt;that you can try "ifconfig eth0 down"&lt;BR /&gt;and then "ifconfig eth0 up" and in most cases it will work but it depend also on how the driver writen.&lt;BR /&gt;&lt;BR /&gt;Caesar</description>
      <pubDate>Mon, 07 Jul 2003 19:16:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016354#M75648</guid>
      <dc:creator>Caesar_3</dc:creator>
      <dc:date>2003-07-07T19:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: clear collision</title>
      <link>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016355#M75649</link>
      <description>On my box it doesn't. I jus see collisions back to the original number. It should be somewhere in the /proc directory, but I didn't find where. I'm reading somewhere that it's on NIC itself and can't be changed from OS, only on resettting physically... No help in man ifonfig either.&lt;BR /&gt;&lt;BR /&gt;I agree anyway with the other to prefer to clear the problem rather than the counter...&lt;BR /&gt;&lt;BR /&gt;J</description>
      <pubDate>Mon, 07 Jul 2003 19:51:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/clear-collision/m-p/3016355#M75649</guid>
      <dc:creator>Jerome Henry</dc:creator>
      <dc:date>2003-07-07T19:51:34Z</dc:date>
    </item>
  </channel>
</rss>

