Hi Jesse, Forget to attach the logs of openvswitch when i added gre port through ovs-vsctl command are as follows:- *root@nova:/# tail -f /usr/local/var/log/openvswitch/ovs-vswitchd.log * 2014-01-06T06:26:53Z|00010|memory|INFO|6924 kB peak resident set size after 10.1 seconds 2014-01-06T06:26:53Z|00011|memory|INFO|ports:1 rules:4 2014-01-06T06:27:21Z|00012|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.9.3 2014-01-06T06:27:24Z|00013|bridge|WARN|bridge br0: using default bridge Ethernet address b6:c3:b3:c5:fd:41 2014-01-06T06:27:24Z|00014|bridge|INFO|bridge br0: using datapath ID 0000b6c3b3c5fd41 2014-01-06T06:27:24Z|00015|connmgr|INFO|br0: added service controller "punix:/usr/local/var/run/openvswitch/br0.mgmt" 2014-01-06T06:27:24Z|00016|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.9.3 2014-01-06T06:28:02Z|00017|dpif|WARN|system@br0: failed to add gre0 as port: Address family not supported by protocol 2014-01-06T06:28:02Z|00018|bridge|WARN|bridge br0: using default bridge Ethernet address b6:c3:b3:c5:fd:41 2014-01-06T06:28:02Z|00019|bridge|INFO|ovs-vswitchd (Open vSwitch) 1.9.3
here *system@br0: failed to add gre0 as port: Address family not supported by protocol *this is the log message i got, can you please look into the issue. waiting for positive reply. -------- Regards Kanika On Mon, Jan 6, 2014 at 2:22 PM, Kanika Saklani <[email protected]>wrote: > Hi Jesse, > > I have did all that you have suggested me but the problem remains same & > in *ovs-dpctl show* command i unable to get the gre port entry before > doing that i have unloaded all the gre modules, openvswitch.ko from x86 > system. > > Following commands & their respectively logs are as follows:- > > 1. First insert the openvswitch module > *insmod > /lib/modules/3.8.13-030813-generic/kernel/net/openvswitch/openvswitch.ko* > > 2. This module is inserted successfully > *root@nova:~# lsmod | grep openvswitch* > openvswitch 47849 0 > > 3. The dmesg logs are as follows:- > *nova@nova:~$ dmesg | tail* > [ 24.674044] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) > [ 25.091212] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready > [ 26.885870] Ebtables v2.0 registered > [ 27.079436] ip6_tables: (C) 2000-2006 Netfilter Core Team > [ 28.229059] cgroup: libvirtd (1296) created nested cgroup for > controller "memory" which has incomplete hierarchy support. Nested cgroups > may change behavior in the future. > [ 28.229062] cgroup: "memory" requires setting use_hierarchy to 1 on the > root. > [ 28.229089] cgroup: libvirtd (1296) created nested cgroup for > controller "devices" which has incomplete hierarchy support. Nested cgroups > may change behavior in the future. > [ 28.229121] cgroup: libvirtd (1296) created nested cgroup for > controller "blkio" which has incomplete hierarchy support. Nested cgroups > may change behavior in the future. > [ 49.811396] init: plymouth-stop pre-start process (2477) terminated > with status 1 > [ 569.666335] openvswitch: Open vSwitch switching datapath > > 4. Then i run the utility ovs-ctl as follows:- > *nova@nova:~/Downloads/openvswitch-1.9.3/utilities$ sudo ./ovs-ctl start* > * Starting ovsdb-server > * system ID not configured, please use --system-id > * Configuring Open vSwitch system IDs > * Starting ovs-vswitchd > > 5. Checking for the ovs is properly on the system. > *nova@nova:~/Downloads/openvswitch-1.9.3/utilities$ ps -ef | grep ovs* > root 3576 1 0 11:56 ? 00:00:00 ovsdb-server: monitoring > pid 3577 > (healthy) > > root 3577 3576 0 11:56 ? 00:00:00 ovsdb-server > /usr/local/etc/openvswitch/conf.db -vconsole:emer -vsyslog:err -vfile:info > --remote=punix:/usr/local/var/run/openvswitch/db.sock > --remote=db:Open_vSwitch,Open_vSwitch,manager_options > --private-key=db:Open_vSwitch,SSL,private_key > --certificate=db:Open_vSwitch,SSL,certificate > --bootstrap-ca-cert=db:Open_vSwitch,SSL,ca_cert --no-chdir > --log-file=/usr/local/var/log/openvswitch/ovsdb-server.log > --pidfile=/usr/local/var/run/openvswitch/ovsdb-server.pid --detach --monitor > root 3588 1 0 11:56 ? 00:00:00 ovs-vswitchd: monitoring > pid 3589 > (healthy) > > root 3589 3588 0 11:56 ? 00:00:00 ovs-vswitchd > unix:/usr/local/var/run/openvswitch/db.sock -vconsole:emer -vsyslog:err > -vfile:info --mlockall --no-chdir > --log-file=/usr/local/var/log/openvswitch/ovs-vswitchd.log > --pidfile=/usr/local/var/run/openvswitch/ovs-vswitchd.pid --detach --monitor > root 3590 3589 0 11:56 ? 00:00:00 ovs-vswitchd: worker > process for pid > 3589 > > nova 3610 3012 0 11:56 pts/1 00:00:00 grep --color=auto ovs > > > 6. Then through the ovs-vsctl command i created the bridge as follows:- > * root@nova:~# ovs-vsctl add-br br0* > > 7. Then i add the gre port to the bridge > > * root@nova:~# ovs-vsctl add-port br0 gre0 -- set interface gre0 type=gre > options:remote_ip=10.10.10.2* > 8. I get the gre interface in ovs-vsctl show command > *root@nova:/# ovs-vsctl show* > a5779349-7666-47b8-bca9-101f6d3b8a60 > Bridge "br0" > Port "br0" > Interface "br0" > type: internal > Port "gre0" > Interface "gre0" > type: gre > options: {remote_ip="10.10.10.2"} > ovs_version: "1.9.3" > > > 9. when i check in ovs-dpctl show command i get > *root@nova:/# ovs-dpctl show* > system@br0: > lookups: hit:0 missed:0 lost:0 > flows: 0 > port 0: br0 (internal) > > Here there is no gre port present in dpctl. please help me regarding this > issue. > Waiting for the positive reply. > > --------- > Regards > Kanika > > > > > > > > On Sat, Jan 4, 2014 at 1:00 PM, Kanika Saklani <[email protected] > > wrote: > >> Hi Jesse, >> >> Thanks for such a quick reply, actually we do not rmmod the complete gre >> module, i only remove the kernel module of the gre & i think that is the >> main reason for our problem i will try the above that you have suggested & >> revert you back. Really your help is highly appreciable. >> >> -------- >> Regards >> Kanika >> >> >> On Fri, Jan 3, 2014 at 11:03 PM, Jesse Gross <[email protected]> wrote: >> >>> On Fri, Jan 3, 2014 at 7:36 AM, Kanika Saklani >>> <[email protected]> wrote: >>> > Hi All, >>> > >>> > I have been working on the gre tunnelling with openvswitch, in which i >>> am >>> > using kernel version 3.2 with openvswitch 1.9 on my x86 machine.But i >>> am >>> > facing the following issue that the gre interface is showing in >>> ovs-vsctl >>> > show command but not showing in the ovs-dpctl show command. >>> >>> Can you please try this new entry from the FAQ: >>> >>> Q: I created a GRE port using ovs-vsctl so why can't I send traffic or >>> see the port in the datapath? >>> >>> A: On Linux kernels before 3.11, the OVS GRE module and Linux GRE module >>> cannot be loaded at the same time. It is likely that on your system >>> the >>> Linux GRE module is already loaded and blocking OVS (to confirm, check >>> dmesg for errors regarding GRE registration). To fix this, unload all >>> GRE modules that appear in lsmod as well as the Open vSwitch kernel >>> module. You can then reload the OVS module following the directions in >>> INSTALL, which will ensure that dependencies are satisfied. >>> >> >> >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
