[ovs-discuss] MPLS Flows VXLAN tunneling issue

Sidhant Hasija shasija at tssg.org
Tue Jun 13 10:45:38 UTC 2017


I have a strange problem with VXLAN encapsulation of MPLS flows.

VXLAN encapsulation is working fine for MPLS flows if the flows are 
produced at the same switch as the vxlan port, but it is not working if 
the MPLS flows arrive from neighboring switch.
The encapsulation works fine for IP flows in every case through.

For example,

Adding a vxlan port on the firsst switch through command-
ovs-vsctl add-port *s1* vxlan1 -- set interface vxlan1 type=vxlan 
options:remote_ip= options:key=flow *ofport_request=15*

And directing the incoming mpls flow to this port through openflow-
/*F1:*/ ovs-ofctl add-flow -OOpenFlow13 *s1* 

MPLS flow routed from a neighboring switch produced from IP through 
/*F2: */ovs-ofctl add-flow -OOpenFlow13 *s2* 
switch s1}

The above configuration is producing following 2 warning messages at the 
logs for every flow matching at F1:

dpif(handler897)|WARN|system at ovs-system: failed to put[create] (Invalid 
argument) ufid:f313c154-53b0-45da-9925-84ce6a940b19 

dpif(handler897)|WARN|system at ovs-system: execute 
set(tunnel(tun_id=0x0,dst=,ttl=64,flags(df|key))),31 failed 
(Invalid argument) on packet 
  mtu 0

I have been struggling through this for quite a while now, any help on 
interpretation of error message or any possible cause of error would be 
really helpful.
I am using Ubuntu16, linux kernel 4.4.21 and ovs 2.5.2
I have also tried ovs 2.7 but vxlan port creation dows not work on it 
giving error "address family not supported" while creating port.

Thanks and Regards,
Sidhant Hasija

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openvswitch.org/pipermail/ovs-discuss/attachments/20170613/6d3b5081/attachment.html>

More information about the discuss mailing list