Hi Joe,
I can reproduce this problem with the kernel module upstream versione
3.13.1[0-1] and with the version build from the branch 2.1 (using kernel 3.11)
and 2.2 (using kernel 3.13).
Right now I have the kernel 3.13 with the openvswitch module from the upstream
kernel.
Thanks a lot!
Regards,
Federico
From: Joe Stringer [joestrin...@nicira.com]
Sent: Wednesday, June 25, 2014 1:23 AM
To: Federico Iezzi
Cc: discuss@openvswitch.org
Subject: Re: [ovs-discuss] failed to put[create][modify]
Is this with the kernel module upstream, or the version that you built from the
tree?
On 21 June 2014 03:01, Federico Iezzi <fie...@enter.it> wrote:
Hi Guys,
I’m in trouble with our staging OpenStack env based on IceHouse Neutron and
Havana Nova.
We are using Ubuntu 12.04.4 with Kernel 3.13 mirror release 11.
With the latests OVS versione (2.1.2, 2.1.3, 2.2.0 and 2.3 DEV - compiled
today) I have a lot of the below errors in ovs-vswitchd.log (compute and
network nodes)
This result in high packet loss and high latency.
Could someone help me to understand better this error and maybe fix it?
Below the error log and some useful informations
Regards!
Federico
2014-06-20T14:47:36.268Z|00001|dpif(handler_71)|WARN|system@ovs-system: failed
to put[create][modify] (Invalid argument)
skb_priority(0),in_port(9),skb_mark(0/0),eth(src=fa:16:3e:c6:c1:10,dst=fa:16:3e:91:99:85),eth_type(0x0800),ipv4(src=169.254.45.153/0.0.0.0,dst=169.254.169.254/0.0.0.0,proto=6/0,tos=0/0x3,ttl=128/0,frag=no/0xff),tcp(src=49164/0,dst=80/0),tcp_flags(0x018/0x000),
actions:set(tunnel(tun_id=0xb0,src=10.16.28.10,dst=10.16.27.2,tos=0x0,ttl=64,flags(df,key))),3
2014-06-20T14:47:52.117Z|00014|dpif(handler_78)|WARN|system@ovs-system: failed
to put[create][modify] (Invalid argument)
skb_priority(0),tunnel(tun_id=0x6d,src=10.16.28.4,dst=10.16.28.10,tos=0x0,ttl=64,flags(key)),in_port(3),skb_mark(0),eth(src=fa:16:3e:15:a1:e1/00:00:00:00:00:00,dst=ff:ff:ff:ff:ff:ff/00:00:00:00:00:00),eth_type(0x0806),arp(sip=192.168.1.10/0.0.0.0,tip=192.168.1.11/0.0.0.0,op=1/0,sha=fa:16:3e:15:a1:e1/00:00:00:00:00:00,tha=00:00:00:00:00:00/00:00:00:00:00:00),
actions:drop
f7b9d6d2-3954-4519-9c8b-814d44e4a1eb
Bridge br-int
Port "tap1b35f321-53"
tag: 10
Interface "tap1b35f321-53"
Port "tapd3884e7d-31"
tag: 10
Interface "tapd3884e7d-31"
Port "tap4d194470-1c"
tag: 10
Interface "tap4d194470-1c"
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port "tapde87541a-5e"
tag: 7
Interface "tapde87541a-5e"
Port "tap787bfcea-63"
tag: 8
Interface "tap787bfcea-63"
Port "tapa40ec900-62"
tag: 11
Interface "tapa40ec900-62"
Port "tap2ffc84c9-36"
tag: 5
Interface "tap2ffc84c9-36"
Port "tapf1d0af3e-e6"
tag: 3
Interface "tapf1d0af3e-e6"
Port "tapad1314a8-cd"
tag: 6
Interface "tapad1314a8-cd"
Port "tapfe96d9bf-db"
tag: 4
Interface "tapfe96d9bf-db"
Port "tap2b47e180-3f"
tag: 9
Interface "tap2b47e180-3f"
Port "tap710a6625-cd"
tag: 2
Interface "tap710a6625-cd"
Port "tap50a2a085-8e"
tag: 4
Interface "tap50a2a085-8e"
Port br-int
Interface br-int
type: internal
Port "tapd1fa0614-1b"
tag: 3
Interface "tapd1fa0614-1b"
Bridge br-tun
Port "vxlan-10.16.27.1"
Interface "vxlan-10.16.27.1"
type: vxlan
options: {in_key=flow, local_ip="10.16.28.10", out_key=flow,
remote_ip="10.16.27.1"}
Port "vxlan-10.16.27.2"
Interface "vxlan-10.16.27.2"
type: vxlan
options: {in_key=flow, local_ip="10.16.28.10", out_key=flow,
remote_ip="10.16.27.2"}
Port "vxlan-10.16.28.8"
Interface "vxlan-10.16.28.8"
type: vxlan
options: {in_key=flow, local_ip="10.16.28.10", out_key=flow,
remote_ip="10.16.28.8"}
Port "vxlan-10.16.28.11"
Interface "vxlan-10.16.28.11"
type: vxlan
options: {in_key=flow, local_ip="10.16.28.10", out_key=flow,
remote_ip="10.16.28.11"}
Port br-tun
Interface br-tun
type: internal
Port "vxlan-10.16.28.9"
Interface "vxlan-10.16.28.9"
type: vxlan
options: {in_key=flow, local_ip="10.16.28.10", out_key=flow,
remote_ip="10.16.28.9"}
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port "vxlan-10.16.28.4"
Interface "vxlan-10.16.28.4"
type: vxlan
options: {in_key=flow, local_ip="10.16.28.10", out_key=flow,
remote_ip="10.16.28.4"}
Port "vxlan-10.16.28.7"
Interface "vxlan-10.16.28.7"
type: vxlan
options: {in_key=flow, local_ip="10.16.28.10", out_key=flow,
remote_ip="10.16.28.7"}
ovs_version: “2.1.2"
system@ovs-system: hit:190435 missed:7781
br-int:
br-int 65534/1: (internal)
patch-tun 1/none: (patch: peer=patch-int)
tap1b35f321-53 15/16: (system)
tap2b47e180-3f 12/13: (system)
tap2ffc84c9-36 7/8: (system)
tap4d194470-1c 13/14: (system)
tap50a2a085-8e 5/6: (system)
tap710a6625-cd 4/5: (system)
tap787bfcea-63 11/12: (system)
tapa40ec900-62 16/17: (system)
tapad1314a8-cd 8/9: (system)
tapd1fa0614-1b 9/10: (system)
tapd3884e7d-31 14/15: (system)
tapde87541a-5e 10/11: (system)
tapf1d0af3e-e6 3/4: (system)
tapfe96d9bf-db 6/7: (system)
br-tun:
br-tun 65534/2: (internal)
patch-int 1/none: (patch: peer=patch-tun)
vxlan-10.16.27.1 2/3: (vxlan: key=flow, local_ip=10.16.28.10,
remote_ip=10.16.27.1)
vxlan-10.16.27.2 3/3: (vxlan: key=flow, local_ip=10.16.28.10,
remote_ip=10.16.27.2)
vxlan-10.16.28.11 4/3: (vxlan: key=flow, local_ip=10.16.28.10,
remote_ip=10.16.28.11)
vxlan-10.16.28.4 5/3: (vxlan: key=flow, local_ip=10.16.28.10,
remote_ip=10.16.28.4)
vxlan-10.16.28.7 6/3: (vxlan: key=flow, local_ip=10.16.28.10,
remote_ip=10.16.28.7)
vxlan-10.16.28.8 7/3: (vxlan: key=flow, local_ip=10.16.28.10,
remote_ip=10.16.28.8)
vxlan-10.16.28.9 8/3: (vxlan: key=flow, local_ip=10.16.28.10,
remote_ip=10.16.28.9)
federico iezzi | cloud engineer
fie...@enter.it
| +39 02 25514828 |
+39 338 6311085 | fax
+39 02 25514 303
enter | internet service provider
via stefanardo da vimercate 28 | 20128 Milano
tel
+39 02 25514 300
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
