Perhaps the interface creating the packet has the wrong MTU?
For instance, a VM is using MTU 1500 but then packets gets
encapsulated?
fbl
On Mon, Oct 19, 2020 at 09:59:13PM +0700, KhacThuan Bk wrote:
> Hi all,
>
> I'm using ovs with bonding interface. All interface is using mtu 1500.
> But in ovs-vswitchd.log i saw some log about "Message too long". I cannot
> use ovs-tcpdump to trace message. Any one used face this problem can tell
> my what is problem. I have some info follow this.
>
> less /var/log/openvswitch/ovs-vswitchd.log
> 2020-10-16T10:26:34.876Z|5804855|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
> 2020-10-16T10:26:34.883Z|5804856|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
> 2020-10-16T10:26:34.888Z|5804857|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
> 2020-10-16T10:26:34.888Z|5804858|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
> 2020-10-16T10:26:34.888Z|5804859|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
> 2020-10-16T10:26:34.936Z|5804860|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
> 2020-10-16T10:26:34.936Z|5804861|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
> 2020-10-16T10:26:34.936Z|5804862|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
> 2020-10-16T10:26:34.947Z|5804863|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
> 2020-10-16T10:26:35.179Z|5804864|dpif_netdev|ERR|error receiving data from
> bond0: Message too long
>
>
> [root@host1 ~]# ovs-vsctl show
> a861ee0a-595a-462a-8729-68de6a9026d8
> Manager "ptcp:6640:127.0.0.1"
> is_connected: true
> Bridge br0
> Controller "tcp:127.0.0.1:6633"
> is_connected: true
> fail_mode: secure
> datapath_type: netdev
> Port phy-br0
> Interface phy-br0
> type: patch
> options: {peer=int-br0}
> Port "bond0"
> Interface "bond0"
> Port br0
> Interface br0
> type: internal
>
> [root@host1 ~]# ip link show bond0
> 10: bond0: mtu 1500 qdisc
> noqueue state UP mode DEFAULT group default qlen 1000
> link/ether e4:43:4b:ed:33:20 brd ff:ff:ff:ff:ff:ff
>
> [root@host1 ~]# ovs-vsctl list interface bond0
> _uuid : 89181c9b-f123-48fb-97ed-3252e39f41ce
> admin_state : up
> bfd : {}
> bfd_status : {}
> cfm_fault : []
> cfm_fault_status: []
> cfm_flap_count : []
> cfm_health : []
> cfm_mpid: []
> cfm_remote_mpids: []
> cfm_remote_opstate : []
> duplex : []
> error : []
> external_ids: {}
> ifindex : 10
> ingress_policing_burst: 0
> ingress_policing_rate: 0
> lacp_current: []
> link_resets : 0
> link_speed : []
> link_state : up
> lldp: {}
> mac : []
> mac_in_use : "e4:43:4b:ed:33:20"
> mtu : 1500
> mtu_request : 1500
> name: "bond0"
> ofport : 3
> ofport_request : []
> options : {}
> other_config: {}
> statistics : {collisions=0, rx_bytes=428325175126, rx_crc_err=0,
> rx_dropped=3644084274, rx_errors=0, rx_frame_err=0, rx_over_err=0,
> rx_packets=2667110862, tx_bytes=345128207711, tx_dropped=0, tx_errors=0,
> tx_packets=563989135}
> status : {driver_name=bonding, driver_version="3.7.1",
> firmware_version="2"}
> type: ""
>
> [root@host2 ~]# ovs-vsctl list interface br0
> _uuid : c3df3fc1-b78d-464f-af39-1fee5aff12dc
> admin_state : down
> bfd : {}
> bfd_status : {}
> cfm_fault : []
> cfm_fault_status: []
> cfm_flap_count : []
> cfm_health : []
> cfm_mpid: []
> cfm_remote_mpids: []
> cfm_remote_opstate : []
> duplex : full
> error : []
> external_ids: {}
> ifindex : 24
> ingress_policing_burst: 0
> ingress_policing_rate: 0
> lacp_current: []
> link_resets : 0
> link_speed : 1000
> link_state : down
> lldp: {}
> mac : []
> mac_in_use : "e4:43:4b:ec:c5:60"
> mtu : 1500
> mtu_request : []
> name: br0
> ofport : 65534
> ofport_request : []
> options : {}
> other_config: {}
> statistics : {collisions=0, rx_bytes=0, rx_crc_err=0,
> rx_dropped=0, rx_errors=0, rx_frame_err=0, rx_over_err=0, rx_packets=0,
> tx_bytes=0, tx_dropped=1000184, tx_errors=0, tx_packets=0}
> status : {driver_name=tun, driver_version="1.6",
> firmware_version=""}
> type: internal
> ___
> discuss mailing list
>
