<?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 RX errors on Ethernet Adapter in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/rx-errors-on-ethernet-adapter/m-p/4725503#M81135</link>
    <description>Hello,&lt;BR /&gt;I have problems with an Ethernet Adapter in my DL380 G7 with RHEL 5.3.&lt;BR /&gt;We have four NICs. Two on board and two via PCIe.&lt;BR /&gt;The both Nics on the PCIe cards have a lot of RX errors. As soon as I bind these NICs into a bonding the behavior is very strange.&lt;BR /&gt;The bond is good as long as the active NIC is one of the on-board NICs. As soon as there is a failover to a PCIe NIC I can ping the bond IP but I can not connect via SSH.&lt;BR /&gt;&lt;BR /&gt;I have a duplicate server next to that, that has the same configuration, but is running fine. I switched the hard disks of the two servers to test if this is a configuration problem in my bonding, but the problem stays on the same server. Therefore I believe it is a problem on the hardware itself.&lt;BR /&gt;&lt;BR /&gt;I do not know where to start and how to investigate that.&lt;BR /&gt;Here some outputs of my server (I removed eth2 from bonding for testing).&lt;BR /&gt;&lt;BR /&gt;# ifconfig eth2&lt;BR /&gt;eth2      Link encap:Ethernet  HWaddr 1C:C1:DE:18:3E:8E&lt;BR /&gt;          inet addr:10.10.145.65  Bcast:10.10.255.255  Mask:255.255.128.0&lt;BR /&gt;          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1&lt;BR /&gt;          RX packets:71510 errors:6423 dropped:0 overruns:0 frame:6423&lt;BR /&gt;          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0&lt;BR /&gt;          collisions:0 txqueuelen:1000&lt;BR /&gt;          RX bytes:6034633 (5.7 MiB)  TX bytes:320 (320.0 b)&lt;BR /&gt;          Interrupt:186 Memory:f8000000-f8012100&lt;BR /&gt;&lt;BR /&gt;# ethtool eth2&lt;BR /&gt;Settings for eth2:&lt;BR /&gt;        Supported ports: [ TP ]&lt;BR /&gt;        Supported link modes:   10baseT/Half 10baseT/Full&lt;BR /&gt;                                100baseT/Half 100baseT/Full&lt;BR /&gt;                                1000baseT/Full&lt;BR /&gt;        Supports auto-negotiation: Yes&lt;BR /&gt;        Advertised link modes:  10baseT/Half 10baseT/Full&lt;BR /&gt;                                100baseT/Half 100baseT/Full&lt;BR /&gt;                                1000baseT/Full&lt;BR /&gt;        Advertised auto-negotiation: Yes&lt;BR /&gt;        Speed: 1000Mb/s&lt;BR /&gt;        Duplex: Full&lt;BR /&gt;        Port: Twisted Pair&lt;BR /&gt;        PHYAD: 1&lt;BR /&gt;        Transceiver: internal&lt;BR /&gt;        Auto-negotiation: on&lt;BR /&gt;        Supports Wake-on: g&lt;BR /&gt;        Wake-on: g&lt;BR /&gt;        Link detected: yes&lt;BR /&gt;&lt;BR /&gt;# mii-tool eth2&lt;BR /&gt;eth2: negotiated 100baseTx-FD flow-control, link ok&lt;BR /&gt;&lt;BR /&gt;Would be great to get some help here.&lt;BR /&gt;Thank you in advance.&lt;BR /&gt;&lt;BR /&gt;Matthias&lt;BR /&gt;</description>
    <pubDate>Mon, 13 Dec 2010 10:31:10 GMT</pubDate>
    <dc:creator>Matthias Kretschmer</dc:creator>
    <dc:date>2010-12-13T10:31:10Z</dc:date>
    <item>
      <title>RX errors on Ethernet Adapter</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rx-errors-on-ethernet-adapter/m-p/4725503#M81135</link>
      <description>Hello,&lt;BR /&gt;I have problems with an Ethernet Adapter in my DL380 G7 with RHEL 5.3.&lt;BR /&gt;We have four NICs. Two on board and two via PCIe.&lt;BR /&gt;The both Nics on the PCIe cards have a lot of RX errors. As soon as I bind these NICs into a bonding the behavior is very strange.&lt;BR /&gt;The bond is good as long as the active NIC is one of the on-board NICs. As soon as there is a failover to a PCIe NIC I can ping the bond IP but I can not connect via SSH.&lt;BR /&gt;&lt;BR /&gt;I have a duplicate server next to that, that has the same configuration, but is running fine. I switched the hard disks of the two servers to test if this is a configuration problem in my bonding, but the problem stays on the same server. Therefore I believe it is a problem on the hardware itself.&lt;BR /&gt;&lt;BR /&gt;I do not know where to start and how to investigate that.&lt;BR /&gt;Here some outputs of my server (I removed eth2 from bonding for testing).&lt;BR /&gt;&lt;BR /&gt;# ifconfig eth2&lt;BR /&gt;eth2      Link encap:Ethernet  HWaddr 1C:C1:DE:18:3E:8E&lt;BR /&gt;          inet addr:10.10.145.65  Bcast:10.10.255.255  Mask:255.255.128.0&lt;BR /&gt;          UP BROADCAST RUNNING SLAVE MULTICAST  MTU:1500  Metric:1&lt;BR /&gt;          RX packets:71510 errors:6423 dropped:0 overruns:0 frame:6423&lt;BR /&gt;          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0&lt;BR /&gt;          collisions:0 txqueuelen:1000&lt;BR /&gt;          RX bytes:6034633 (5.7 MiB)  TX bytes:320 (320.0 b)&lt;BR /&gt;          Interrupt:186 Memory:f8000000-f8012100&lt;BR /&gt;&lt;BR /&gt;# ethtool eth2&lt;BR /&gt;Settings for eth2:&lt;BR /&gt;        Supported ports: [ TP ]&lt;BR /&gt;        Supported link modes:   10baseT/Half 10baseT/Full&lt;BR /&gt;                                100baseT/Half 100baseT/Full&lt;BR /&gt;                                1000baseT/Full&lt;BR /&gt;        Supports auto-negotiation: Yes&lt;BR /&gt;        Advertised link modes:  10baseT/Half 10baseT/Full&lt;BR /&gt;                                100baseT/Half 100baseT/Full&lt;BR /&gt;                                1000baseT/Full&lt;BR /&gt;        Advertised auto-negotiation: Yes&lt;BR /&gt;        Speed: 1000Mb/s&lt;BR /&gt;        Duplex: Full&lt;BR /&gt;        Port: Twisted Pair&lt;BR /&gt;        PHYAD: 1&lt;BR /&gt;        Transceiver: internal&lt;BR /&gt;        Auto-negotiation: on&lt;BR /&gt;        Supports Wake-on: g&lt;BR /&gt;        Wake-on: g&lt;BR /&gt;        Link detected: yes&lt;BR /&gt;&lt;BR /&gt;# mii-tool eth2&lt;BR /&gt;eth2: negotiated 100baseTx-FD flow-control, link ok&lt;BR /&gt;&lt;BR /&gt;Would be great to get some help here.&lt;BR /&gt;Thank you in advance.&lt;BR /&gt;&lt;BR /&gt;Matthias&lt;BR /&gt;</description>
      <pubDate>Mon, 13 Dec 2010 10:31:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rx-errors-on-ethernet-adapter/m-p/4725503#M81135</guid>
      <dc:creator>Matthias Kretschmer</dc:creator>
      <dc:date>2010-12-13T10:31:10Z</dc:date>
    </item>
    <item>
      <title>Re: RX errors on Ethernet Adapter</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rx-errors-on-ethernet-adapter/m-p/4725504#M81136</link>
      <description>I am sorry.&lt;BR /&gt;I have to correct myself.&lt;BR /&gt;Of cause, the DL380 G7 has four on-board NICs and no PCIe Card with NICs.&lt;BR /&gt;This means it is even more strange, because NIC 1 and 2 are running fine, but 3 and 4 have a lot of RX Errors.&lt;BR /&gt;&lt;BR /&gt;BR&lt;BR /&gt;Matthias</description>
      <pubDate>Mon, 13 Dec 2010 11:57:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rx-errors-on-ethernet-adapter/m-p/4725504#M81136</guid>
      <dc:creator>Matthias Kretschmer</dc:creator>
      <dc:date>2010-12-13T11:57:49Z</dc:date>
    </item>
    <item>
      <title>Re: RX errors on Ethernet Adapter</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rx-errors-on-ethernet-adapter/m-p/4725505#M81137</link>
      <description>&lt;!--!*#--&gt;Have you tried changing any hardware (cables,&lt;BR /&gt;switch ports, ...)?&lt;BR /&gt;&lt;BR /&gt;&amp;gt; Settings for eth2:&lt;BR /&gt;&lt;BR /&gt;And what are the settings at the other end of&lt;BR /&gt;the cable?</description>
      <pubDate>Mon, 13 Dec 2010 17:54:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rx-errors-on-ethernet-adapter/m-p/4725505#M81137</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2010-12-13T17:54:34Z</dc:date>
    </item>
    <item>
      <title>Re: RX errors on Ethernet Adapter</title>
      <link>https://community.hpe.com/t5/operating-system-linux/rx-errors-on-ethernet-adapter/m-p/4725506#M81138</link>
      <description>Strictly speaking, the minimum version of RHEL5 supported on the DL380 G7 is 5.4:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h18000.www1.hp.com/products/servers/linux/supportmatrix/rhel/exceptions/rhel-exceptions.html" target="_blank"&gt;http://h18000.www1.hp.com/products/servers/linux/supportmatrix/rhel/exceptions/rhel-exceptions.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;You might get more information about the frame errors if you look at ethtool -S &lt;INTERFACE&gt;.&lt;BR /&gt;&lt;BR /&gt;Assuming that there are cables connected to all four of the LOM ports, and they go to the same switch, and indeed only two of them show errors, you might consider "rotating" the cables one port and see if the errors stay with the port, or move with the cable.  If they move with the cable, then repeat that on the switch, and see if they move with the cable, or stay with the port.&lt;/INTERFACE&gt;</description>
      <pubDate>Tue, 14 Dec 2010 00:26:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/rx-errors-on-ethernet-adapter/m-p/4725506#M81138</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2010-12-14T00:26:25Z</dc:date>
    </item>
  </channel>
</rss>

