Hi All ,
i am using ovs 2.16 with dpdk 20.8 .
Bridge dss0 Controller "tcp:127.0.0.1:6653" is_connected:
true datapath_type: netdev Port dpdk0 Interface dpdk0
type: dpdk options: {dpdk-devargs="0000:00:09.0",
n_rxq="4", n_txq="4"} Port dss0 Interface dss0
type: internal ovs_version: "2.16.0"
i have sub interfaces for dss0 port , dss0.125 && dss0.130 when i enable
promiscuous mode ( by using tshark or tcpdump ) . i get the below messages in
the ovs-vswitchd.log :
2022-04-25T11:11:00.499Z|00309|netdev_dpdk|WARN|Failed to enable flow control
on device 02022-04-25T11:11:00.503Z|00310|netdev_linux|INFO|ioctl(SIOCGIFINDEX)
on vxlan_sys_4789 device failed: No such device
the problem is that on the other physical switch end , it appears that the port
went down and then it comes up again . is there an explanation for this
behavior ? why would this happen when i use tcpdump ( only when the interface
enters the promiscuous mode ) on dss0.125 && dss0.130 .?
regards saif
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
