Find the answer to your Linux question:
Results 1 to 4 of 4
Hello, I am getting a lot of RX errors in my server and the network connection is very low, around 6kB/s. I am giving the NIC details below. The eth0 ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Aug 2012
    Posts
    6

    RX packet errors


    Hello,

    I am getting a lot of RX errors in my server and the network connection is very low, around 6kB/s. I am giving the NIC details below.

    The eth0 is the onboard NIC, its a RTL8201EL. That NIC is a 10/100 NIC. The cable is about 250m long and it cat 6e. It connects a Juniper ex3200 to a Netgear 108E (link at 1gb) and then from the netgear to the server. Our network admin told me that he did test the cable and and it did not give any errors.

    ==============================================
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:577829 errors:29547 dropped:0 overruns:0 frame:29547
    TX packets:241600 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:221283920 (211.0 MiB) TX bytes:36979981 (35.2 MiB)
    Interrupt:27 Base address:0xc000
    ===============================================


    NIC statistics:
    tx_bytes: 36978307
    tx_zero_rexmt: 241593
    tx_one_rexmt: 0
    tx_many_rexmt: 0
    tx_late_collision: 0
    tx_fifo_errors: 0
    tx_carrier_errors: 0
    tx_excess_deferral: 0
    tx_retry_error: 0
    rx_frame_error: 0
    rx_extra_byte: 0
    rx_late_collision: 0
    rx_runt: 0
    rx_frame_too_long: 0
    rx_over_errors: 29547
    rx_crc_errors: 0
    rx_frame_align_error: 0
    rx_length_error: 0
    rx_unicast: 236803
    rx_multicast: 25263
    rx_broadcast: 314892
    rx_packets: 576958
    rx_errors_total: 29547
    tx_errors_total: 0
    tx_deferral: 0
    tx_packets: 241593
    rx_bytes: 268335775
    tx_pause: 95623
    rx_pause: 0
    rx_drop_frame: 579
    tx_unicast: 874976
    tx_multicast: 321584
    tx_broadcast: 1065645641612

    Can anybody please help me to find the root cause of this issue.
    Thanks

  2. #2
    Trusted Penguin Irithori's Avatar
    Join Date
    May 2009
    Location
    Munich
    Posts
    3,439
    250m is way outside the specs.
    Afaik 100m is maximum and even then lower throughput is expected.
    You must always face the curtain with a bow.

  3. #3
    Linux Guru Lazydog's Avatar
    Join Date
    Jun 2004
    Location
    The Keystone State
    Posts
    2,677
    Anything over 100m is definitively not supported. Are you sure it is 250m and not 250ft?
    I also question how your network admin could check such a long cable and tell you it is fine.

    Regards
    Robert

    Linux
    The adventure of a life time.

    Linux User #296285
    Get Counted

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Mar 2003
    Location
    CT
    Posts
    11
    Not adding much here, but if it's really 250m then you are exceeding spec by 2.5 times, if the cable is really that long the only way to fix this is to place signal regenerators (or a small switch or hub) no more than at 100m intervals, so essentially you would need 2 in a run of 250m.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •