Ovs 2.8 can't support kernel data path for NSH, are you sure you're using OVS-DPDK.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Glend REN Sent: Friday, March 9, 2018 7:33 PM To: [email protected] Subject: [ovs-dev] when the physical compute receive vxlan-gpe-nsh packet whose size>256, the ovs flow table not match and ovs crash. Hi all: Now I use vxlan-gpe-nsh with ovs-2.8.0 The environment is : compute1 and compute2 wth ovs2.8.0 installed. the two computes are both physical servers. A vm of the compute1 sends a icmp packet, when the packet arrives the br-int of the compute1, it will be encapsulated vxlan-gpe-nsh, and sent to the compute2. But the strange problem is if the size of icmp packet< 126 byte(vxlan-gpe-nsh packet <256), the communication is normal. If the size >126, after arriving compute2 ,the flow table not match the packet., and >if ping several times, the network and ovs of compute2 collapse ：The network connection goes down for one minute,and one minute later the network recovery;The ovs stop and the kernel module is deleted; All the OVS br-int virtual machine tap port is deleted, unable to connect to the controller. If the icmp packet is not encapsulated by vxlan-gpe-nsh but only vxlan-gpe, no matter what the size is ,the communication is normal. And if compue1 and compute2 are not physical servers, but the virtual machine, regardless of the size of ICMP packet , through the vxlan-gpe-nsh encapsulation the communication is normal. It is that now the physical environment has above problems, but the virtual environment is normal. so can you tell me how to solve the problems? Thank you ! _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
