Sorry, I'm really new to openvswitch. Not very clear what to do. I don't have the error message. And I'm working on CentOS 6.4, kernel 2.6.32-358.123.2.openstack.el6.x86_64. I installed openvswitch using command "yum install openvswitch". The version I'm using is openvswitch.x86_64 1.11.0_8ce28d-1.el6ost. My repos is http://repos.fedorapeople.org/repos/openstack/openstack-havana/epel-6/
Thanks. -chen From: Alex Wang [mailto:al...@nicira.com] Sent: Tuesday, December 31, 2013 2:38 AM To: Li, Chen Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] Can't enable gre/vxlan for ovs Hey Chen, Just learned that there is change of way of kernel module installation between branch-1.11 and branch-2.0. Could you confirm if you have the following error message in 'dmesg' output? [ 172.574886] openvswitch: Open vSwitch switching datapath 1.11.1, built Dec 30 2013 09:43:15 [ 172.575046] openvswitch: cannot register gre protocol handler This will prevent the gre module from functioning. Also, please refer to the INSTALL file for the correct way to install kernel module. Thanks, Alex Wang, On Mon, Dec 30, 2013 at 9:51 AM, Alex Wang <al...@nicira.com<mailto:al...@nicira.com>> wrote: Hey Chen, Thanks for reporting this. Seems to be a bug. I can reproduce it on my machine. And ovs-dpctl show did not show the tunnel port, root@promg-2n-a-dhcp85:~# ovs-dpctl show system@ovs-system: lookups: hit:53 missed:4 lost:0 flows: 1 port 0: ovs-system (internal) port 1: br0 (internal) We'll investigate & fix it. Thanks, Alex Wang, On Sun, Dec 29, 2013 at 11:54 PM, Li, Chen <chen...@intel.com<mailto:chen...@intel.com>> wrote: Hi list, I'm trying to enable gre/vxlan for Openstack, but unfortunately, I get failed. :( So, I try to easy my job to just enable gre/vxlan on openvswitch by hand. I followed steps: http://networkstatic.net/configuring-vxlan-and-gre-tunnels-on-openvswitch/#!prettyPhoto But, the network is still not reachable...... While I'm trying to ping another Node, the action in ovs is drop: on Node 1: 1. Run command : ping 10.1.2.11 2. Run command : ovs-dpctl dump-flows in_port(1),eth(src=fe:34:0f:f9:16:48,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=10.1.2.10,tip=10.1.2.11,op=1,sha=fe:34:0f:f9:16:48,tha=00:00:00:00:00:00), packets:5, bytes:210, used:0.647s, actions:drop Hope you guys can give me some advice about this. Thanks. -chen Here is my set-up's status: Node 1: ifconfig br-int Link encap:Ethernet HWaddr FE:34:0F:F9:16:48 inet addr:10.1.2.10 Bcast:10.1.2.255 Mask:255.255.255.0 inet6 addr: fe80::1038:7dff:fec0:c4f1/64 Scope:Link UP BROADCAST RUNNING MTU:1500 Metric:1 RX packets:393799 errors:0 dropped:0 overruns:0 frame:0 TX packets:30 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:75528724 (72.0 MiB) TX bytes:1476 (1.4 KiB) eth0 Link encap:Ethernet HWaddr 00:25:90:79:EE:58 inet addr:192.168.11.102 Bcast:192.168.255.255 Mask:255.255.0.0 inet6 addr: fe80::225:90ff:fe79:ee58/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:47704498 errors:0 dropped:0 overruns:0 frame:0 TX packets:7581995 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:8436995106<tel:8436995106> (7.8 GiB) TX bytes:2025995928<tel:2025995928> (1.8 GiB) Memory:dfd20000-dfd40000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:57 errors:0 dropped:0 overruns:0 frame:0 TX packets:57 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:5022 (4.9 KiB) TX bytes:5022 (4.9 KiB) ovs-vsctl show 4ab902f3-5d19-46b9-bd24-0ad080540613 Bridge br-int Port "gre1" Interface "gre1" type: gre options: {remotr_ip="192.168.11.103"} Port br-int Interface br-int type: internal ovs_version: "1.11.0" ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x0, duration=33.562s, table=0, n_packets=0, n_bytes=0, idle_age=33, priority=0 actions=NORMAL Node 2: ifconfig br-int Link encap:Ethernet HWaddr F6:B2:FB:FA:4F:40 inet addr:10.1.2.11 Bcast:10.1.2.255 Mask:255.255.255.0 inet6 addr: fe80::874:14ff:fe1c:6f2d/64 Scope:Link UP BROADCAST RUNNING MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:60 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 b) TX bytes:2736 (2.6 KiB) eth0 Link encap:Ethernet HWaddr 00:25:90:79:D3:F4 inet addr:192.168.11.103 Bcast:192.168.255.255 Mask:255.255.0.0 inet6 addr: fe80::225:90ff:fe79:d3f4/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:50628891 errors:0 dropped:0 overruns:0 frame:0 TX packets:10316125 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:9826925316 (9.1 GiB) TX bytes:2822135225 (2.6 GiB) Memory:dfd20000-dfd40000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:1391 errors:0 dropped:0 overruns:0 frame:0 TX packets:1391 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:154486 (150.8 KiB) TX bytes:154486 (150.8 KiB) ovs-vsctl show 218f9b54-b3e8-47ac-8563-58ff91ca57e9 Bridge br-int Port "gre1" Interface "gre1" type: gre options: {remotr_ip="192.168.11.102"} Port br-int Interface br-int type: internal ovs_version: "1.11.0" ovs-ofctl dump-flows br-int NXST_FLOW reply (xid=0x4): cookie=0x0, duration=7014.936s, table=0, n_packets=60, n_bytes=2736, idle_age=6412, priority=0 actions=NORMAL _______________________________________________ discuss mailing list discuss@openvswitch.org<mailto:discuss@openvswitch.org> http://openvswitch.org/mailman/listinfo/discuss
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
