Rx error на коммутаторе

I’m seeing network problems with a (RHEL) node (packets dropped), which also seem to manifest themselves by a non-zero count of the ‘error’ and ‘frame’ fields in ifconfig output:

eth2      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx  
          ...
          RX packets:277593775 errors:1049 dropped:0 overruns:0 frame:536

Is there a detailed description somewhere what the exact meaning of ‘errors’ and ‘frame’ is ?

EDIT: output of ethtool eth2:

Settings for eth2:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: umbg
        Wake-on: d
        Current message level: 0x00000007 (7)
        Link detected: yes

asked Sep 28, 2010 at 9:11

In the tigon (tg3) driver, prior to version v3.134b rxbds_empty events were logged as frame errors.

You can check this via:

ethtool -S {device}

e.g.:

[root@srv2-mgmt ~]# ethtool -S em1
NIC statistics:
     rx_octets: 795609182
     rx_fragments: 0
     rx_ucast_packets: 4003807
     rx_mcast_packets: 313481
     rx_bcast_packets: 1906658
     rx_fcs_errors: 0
     rx_align_errors: 0
     rx_xon_pause_rcvd: 0
     rx_xoff_pause_rcvd: 0
     rx_mac_ctrl_rcvd: 0
     rx_xoff_entered: 0
     rx_frame_too_long_errors: 0
     rx_jabbers: 0
     rx_undersize_packets: 0
     rx_in_length_errors: 0
     rx_out_length_errors: 0
     rx_64_or_less_octet_packets: 0
     rx_65_to_127_octet_packets: 0
     rx_128_to_255_octet_packets: 0
     rx_256_to_511_octet_packets: 0
     rx_512_to_1023_octet_packets: 0
     rx_1024_to_1522_octet_packets: 0
     rx_1523_to_2047_octet_packets: 0
     rx_2048_to_4095_octet_packets: 0
     rx_4096_to_8191_octet_packets: 0
     rx_8192_to_9022_octet_packets: 0
     tx_octets: 1010597527
     tx_collisions: 0
     tx_xon_sent: 0
     tx_xoff_sent: 0
     tx_flow_control: 0
     tx_mac_errors: 0
     tx_single_collisions: 0
     tx_mult_collisions: 0
     tx_deferred: 0
     tx_excessive_collisions: 0
     tx_late_collisions: 0
     tx_collide_2times: 0
     tx_collide_3times: 0
     tx_collide_4times: 0
     tx_collide_5times: 0
     tx_collide_6times: 0
     tx_collide_7times: 0
     tx_collide_8times: 0
     tx_collide_9times: 0
     tx_collide_10times: 0
     tx_collide_11times: 0
     tx_collide_12times: 0
     tx_collide_13times: 0
     tx_collide_14times: 0
     tx_collide_15times: 0
     tx_ucast_packets: 4116171
     tx_mcast_packets: 145500
     tx_bcast_packets: 1983
     tx_carrier_sense_errors: 0
     tx_discards: 0
     tx_errors: 0
     dma_writeq_full: 0
     dma_write_prioq_full: 0
     rxbds_empty: 0
     rx_discards: 0
     rx_errors: 0
     rx_threshold_hit: 0
     dma_readq_full: 0
     dma_read_prioq_full: 0
     tx_comp_queue_full: 0
     ring_set_send_prod_index: 0
     ring_status_update: 0
     nic_irqs: 0
     nic_avoided_irqs: 0
     nic_tx_threshold_hit: 0
     mbuf_lwm_thresh_hit: 0

I am seeing packet loss from all my blade servers within the HP Blade C7000 enclosure.

# ping 192.168.2.140
PING 192.168.2.140 (192.168.2.140) 56(84) bytes of data.
64 bytes from 192.168.2.140: icmp_seq=1 ttl=64 time=0.210 ms
64 bytes from 192.168.2.140: icmp_seq=2 ttl=64 time=0.185 ms
64 bytes from 192.168.2.140: icmp_seq=4 ttl=64 time=0.206 ms
64 bytes from 192.168.2.140: icmp_seq=6 ttl=64 time=0.164 ms
64 bytes from 192.168.2.140: icmp_seq=7 ttl=64 time=0.210 ms
64 bytes from 192.168.2.140: icmp_seq=8 ttl=64 time=0.213 ms
64 bytes from 192.168.2.140: icmp_seq=9 ttl=64 time=0.213 ms

--- 192.168.2.140 ping statistics ---
9 packets transmitted, 7 received, 22% packet loss, time 8000ms
rtt min/avg/max/mdev = 0.164/0.200/0.213/0.018 ms

# ping 192.168.2.165
 PING 192.168.2.165 (192.168.2.165) 56(84) bytes of data.
 64 bytes from 192.168.2.165: icmp_seq=1 ttl=64 time=0.990 ms
 64 bytes from 192.168.2.165: icmp_seq=3 ttl=64 time=0.204 ms
 64 bytes from 192.168.2.165: icmp_seq=4 ttl=64 time=0.165 ms
 64 bytes from 192.168.2.165: icmp_seq=5 ttl=64 time=0.168 ms

 --- 192.168.2.165 ping statistics ---
 6 packets transmitted, 4 received, 33% packet loss, time 5001ms
 rtt min/avg/max/mdev = 0.165/0.381/0.990/0.352 ms


$ /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr E4:11:5B:D0:36:B0
          inet addr:192.168.2.163  Bcast:192.168.2.255  Mask:255.255.255.192
          inet6 addr: fe80::e611:5bff:fed0:36b0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:44022 errors:29632 dropped:0 overruns:0 frame:10025
          TX packets:42694 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4345443 (4.1 MiB)  TX bytes:4549025 (4.3 MiB)

$ netstat -i
Kernel Interface table
Iface       MTU Met    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0       1500   0     5124  32118      0      0     2651      0      0      0 BMRU
lo        16436   0     4522      0      0      0     4522      0      0      0 LRU


 $ route -n
 Kernel IP routing table
 Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
 192.168.4.128   0.0.0.0         255.255.255.192 U     0      0        0 eth0
 169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
 0.0.0.0         192.168.4.134   0.0.0.0         UG    0      0        0 eth0

# ethtool -S eth0 | grep -i errors
  rx_errors: 43821
  tx_errors: 0
  rx_crc_errors: 14812
  rx_alignment_symbol_errors: 0
  rx_in_range_errors: 0
  rx_out_range_errors: 0
  rx_address_match_errors: 150211
# ethtool -S eth0 | grep -i drops
  rx_drops_no_pbuf: 0
  rx_drops_no_txpb: 0
  rx_drops_no_erx_descr: 0
  rx_drops_no_tpre_descr: 0
  rx_drops_too_many_frags: 0
  rx_drops_invalid_ring: 3215
  rx_drops_mtu: 0
  rx_drops_no_fragments: 0

Network configuration looks fine .

How to solve the issue?

I’s difficult to tell, what is your operating system version and patch level?
Here are some things you could check :

• Your network switch may be polluted/overloaded by a broken card generating garbage. Check the errors on the switch.
• If you are using «virtual connect» on your enclosure, you could check the error on the virtual connect box.
• If you are using «pass through» connection on the enclosure , check if all your connection are going through the same pass through pannel, maybe it must be replaced. Pass through are not passive, they have their own firmware too check with your HP support if its recent.
• If you recently patched your Operating system, try to install the supported driver of the last SPP (support pack, only for redhat or SuSE I’m afraid), the drivers may be less recent but they are supported by HP.
• Maybe its a simple duplex mismatch, check the speed on the switch and on the host (ethtool ethX)

answered Apr 29, 2014 at 18:04

I am seeing packet loss from all my blade servers within the HP Blade C7000 enclosure.

# ping 192.168.2.140
PING 192.168.2.140 (192.168.2.140) 56(84) bytes of data.
64 bytes from 192.168.2.140: icmp_seq=1 ttl=64 time=0.210 ms
64 bytes from 192.168.2.140: icmp_seq=2 ttl=64 time=0.185 ms
64 bytes from 192.168.2.140: icmp_seq=4 ttl=64 time=0.206 ms
64 bytes from 192.168.2.140: icmp_seq=6 ttl=64 time=0.164 ms
64 bytes from 192.168.2.140: icmp_seq=7 ttl=64 time=0.210 ms
64 bytes from 192.168.2.140: icmp_seq=8 ttl=64 time=0.213 ms
64 bytes from 192.168.2.140: icmp_seq=9 ttl=64 time=0.213 ms

--- 192.168.2.140 ping statistics ---
9 packets transmitted, 7 received, 22% packet loss, time 8000ms
rtt min/avg/max/mdev = 0.164/0.200/0.213/0.018 ms

# ping 192.168.2.165
 PING 192.168.2.165 (192.168.2.165) 56(84) bytes of data.
 64 bytes from 192.168.2.165: icmp_seq=1 ttl=64 time=0.990 ms
 64 bytes from 192.168.2.165: icmp_seq=3 ttl=64 time=0.204 ms
 64 bytes from 192.168.2.165: icmp_seq=4 ttl=64 time=0.165 ms
 64 bytes from 192.168.2.165: icmp_seq=5 ttl=64 time=0.168 ms

 --- 192.168.2.165 ping statistics ---
 6 packets transmitted, 4 received, 33% packet loss, time 5001ms
 rtt min/avg/max/mdev = 0.165/0.381/0.990/0.352 ms


$ /sbin/ifconfig
eth0      Link encap:Ethernet  HWaddr E4:11:5B:D0:36:B0
          inet addr:192.168.2.163  Bcast:192.168.2.255  Mask:255.255.255.192
          inet6 addr: fe80::e611:5bff:fed0:36b0/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:44022 errors:29632 dropped:0 overruns:0 frame:10025
          TX packets:42694 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4345443 (4.1 MiB)  TX bytes:4549025 (4.3 MiB)

$ netstat -i
Kernel Interface table
Iface       MTU Met    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0       1500   0     5124  32118      0      0     2651      0      0      0 BMRU
lo        16436   0     4522      0      0      0     4522      0      0      0 LRU


 $ route -n
 Kernel IP routing table
 Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
 192.168.4.128   0.0.0.0         255.255.255.192 U     0      0        0 eth0
 169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
 0.0.0.0         192.168.4.134   0.0.0.0         UG    0      0        0 eth0

# ethtool -S eth0 | grep -i errors
  rx_errors: 43821
  tx_errors: 0
  rx_crc_errors: 14812
  rx_alignment_symbol_errors: 0
  rx_in_range_errors: 0
  rx_out_range_errors: 0
  rx_address_match_errors: 150211
# ethtool -S eth0 | grep -i drops
  rx_drops_no_pbuf: 0
  rx_drops_no_txpb: 0
  rx_drops_no_erx_descr: 0
  rx_drops_no_tpre_descr: 0
  rx_drops_too_many_frags: 0
  rx_drops_invalid_ring: 3215
  rx_drops_mtu: 0
  rx_drops_no_fragments: 0

Network configuration looks fine .

How to solve the issue?

I’s difficult to tell, what is your operating system version and patch level?
Here are some things you could check :

• Your network switch may be polluted/overloaded by a broken card generating garbage. Check the errors on the switch.
• If you are using «virtual connect» on your enclosure, you could check the error on the virtual connect box.
• If you are using «pass through» connection on the enclosure , check if all your connection are going through the same pass through pannel, maybe it must be replaced. Pass through are not passive, they have their own firmware too check with your HP support if its recent.
• If you recently patched your Operating system, try to install the supported driver of the last SPP (support pack, only for redhat or SuSE I’m afraid), the drivers may be less recent but they are supported by HP.
• Maybe its a simple duplex mismatch, check the speed on the switch and on the host (ethtool ethX)

answered Apr 29, 2014 at 18:04