ifconfig输出中RX“错误”和“帧”的确切含义?


10

我看到一个(RHEL)节点(丢包)的网络问题,这似乎也通过ifconfig输出中'error'和'frame'字段的非零计数来表明:

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

在某处是否有详细的描述,“错误”和“框架”的确切含义是什么?

编辑:输出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

1
可能是双工不匹配。您可以发布ethtool eth2的输出吗?
Shunz先生10年

Answers:


7

RX错误表示您的NIC正在从传输交换机端口接收格式错误的帧。

帧错误表示接收到帧时CRC错误。造成这种情况的根本原因可能是电缆损坏,或者机器或交换机上的接口损坏。尝试更换电缆,然后移至交换机上的另一个端口。


感谢您的回答。我认为格式错误的帧也没有正确的CRC。它需要畸形什么?如果在帧间间隙之后没有/大小不正确的前同步码,或者在前同步码之后没有帧定界符?还是下一个帧间间隙相对于以太类型/长度字段中找到的长度而言太早/太晚?
安德烈·霍尔兹纳

以上任何一项。我不确定为什么要输入“格式错误或其他错误信息”。没错,它们的意思完全相同。答案已更新。
Murali Suriar

1
@MuraliSuriar我使用的是10G NIC,丢弃和帧的数量相同,但是错误的数量为0,`RX数据包:17051276错误:0丢弃:476超限:0帧:476`,您能告诉我什么在这种情况下可能是什么原因?
宝马先生

1

在tigon(tg3)驱动程序中,在v3.134b之前的版本中,rxbds_empty事件记录为帧错误。

您可以通过以下方式进行检查:

ethtool -S {device}

例如:

[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
By using our site, you acknowledge that you have read and understand our Cookie Policy and Privacy Policy.
Licensed under cc by-sa 3.0 with attribution required.