[ovs-discuss] VXLAN tunnel issue

Shahryar Ali shahryaralik at gmail.com
Tue Jul 30 22:28:17 UTC 2013


Thanks Kyle. I guess i was not following the instructions in the INSTALL
file correctly. It is working now, thanks for the help.


On Tue, Jul 30, 2013 at 2:43 PM, Kyle Mestery (kmestery) <kmestery at cisco.com
> wrote:

> On Jul 30, 2013, at 6:43 AM, Shahryar Ali <shahryaralik at gmail.com> wrote:
> >
> > Thanks for the reply Kyle. Here is the output of the modinfo openvswitch:
> >
> > # modinfo openvswitch
> > filename:
> /lib/modules/3.8.0-27-generic/kernel/net/openvswitch/openvswitch.ko
> > license:        GPL
> > description:    Open vSwitch switching datapath
> > srcversion:     15C32AD9E04F379CAC3D68E
> > depends:
> > intree:         Y
> > vermagic:       3.8.0-27-generic SMP mod_unload modversions
> >
> > So how can i run the ovs kernel module in Open Vswitch?
> >
> You can follow the instructions in the INSTALL file at the top-level of
> the OVS source tree to build and install the kernel module.
>
> > >
> >
> >
> > >
> >
> >
> > >
> >
> >
> > >
> >  _______________________________________________
> >
> > >
> >  discuss mailing list
> >
> > > discuss at openvswitch.org
> > > http://openvswitch.org/mailman/listinfo/discuss
> >
> >
> > On Sun, Jul 28, 2013 at 3:03 AM, Kyle Mestery (kmestery) <
> kmestery at cisco.com> wrote:
> > On Jul 27, 2013, at 6:35 AM, Shahryar Ali <shahryaralik at gmail.com>
> wrote:
> > > Hi i am newbie in Openvswitch and trying to create a VXLAN tunnel. I
> am having issue in connectivity. I am not able to ping the isolated bridges
> through VXLAN tunnel. The tunnel end points do have the connectivity. Here
> is my configuration:
> > >
> > > Host 1:
> > >
> > > Bridge "br0"
> > >         Port "br0"
> > >             Interface "br0"
> > >                 type: internal
> > >         Port "eth0"
> > >             Interface "eth0"
> > >     Bridge "br1"
> > >         Port "vxlan1"
> > >             Interface "vxlan1"
> > >                 type: vxlan
> > >                 options: {key=flow, remote_ip="192.168.1.102"}
> > >         Port "br1"
> > >             Interface "br1"
> > >                 type: internal
> > >
> > > root at shahryar-VirtualBox:~# ifconfig
> > > br0       Link encap:Ethernet  HWaddr 08:00:27:44:9b:8b
> > >           inet addr:192.168.1.101  Bcast:192.168.1.255
>  Mask:255.255.255.0
> > >           inet6 addr: fe80::7cda:c4ff:fe22:880a/64 Scope:Link
> > >           UP BROADCAST RUNNING  MTU:1500  Metric:1
> > >           RX packets:318 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:31 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:54076 (54.0 KB)  TX bytes:2358 (2.3 KB)
> > >
> > > br1       Link encap:Ethernet  HWaddr 16:0a:50:e6:5c:4c
> > >           inet addr:192.168.2.1  Bcast:192.168.2.255
>  Mask:255.255.255.0
> > >           inet6 addr: fe80::4068:38ff:feeb:65bd/64 Scope:Link
> > >           UP BROADCAST RUNNING  MTU:1500  Metric:1
> > >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)
> > >
> > > eth0      Link encap:Ethernet  HWaddr 08:00:27:44:9b:8b
> > >           inet6 addr: fe80::a00:27ff:fe44:9b8b/64 Scope:Link
> > >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> > >           RX packets:297 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:452 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:1000
> > >           RX bytes:53173 (53.1 KB)  TX bytes:86554 (86.5 KB)
> > >
> > > 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:65536  Metric:1
> > >           RX packets:1885 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:1885 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:148186 (148.1 KB)  TX bytes:148186 (148.1 KB)
> > >
> > >
> > > root at shahryar-VirtualBox:~# route -n
> > > Kernel IP routing table
> > > Destination     Gateway         Genmask         Flags Metric Ref
>  Use Iface
> > > 0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0
>  0 br0
> > > 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0
>  0 br0
> > > 192.168.2.0     0.0.0.0         255.255.255.0   U     0      0
>  0 br1
> > >
> > >
> > > Host 2:
> > >
> > > root at shahryarvm2-VirtualBox:~# ovs-vsctl show
> > > 88f16842-6876-4e1d-8607-e097bd2ad435
> > >     Bridge "br0"
> > >         Port "eth0"
> > >             Interface "eth0"
> > >         Port "br0"
> > >             Interface "br0"
> > >                 type: internal
> > >     Bridge "br1"
> > >         Port "vxlan1"
> > >             Interface "vxlan1"
> > >                 type: vxlan
> > >                 options: {key=flow, remote_ip="192.168.1.101"}
> > >         Port "br1"
> > >             Interface "br1"
> > >                 type: internal
> > >
> > > root at shahryarvm2-VirtualBox:~# ifconfig
> > >
> > > br0       Link encap:Ethernet  HWaddr 08:00:27:0f:8d:47
> > >           inet addr:192.168.1.102  Bcast:192.168.1.255
>  Mask:255.255.255.0
> > >           inet6 addr: fe80::2c7d:cbff:fe71:a555/64 Scope:Link
> > >           UP BROADCAST RUNNING  MTU:1500  Metric:1
> > >           RX packets:222 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:35357 (35.3 KB)  TX bytes:2932 (2.9 KB)
> > >
> > > br1       Link encap:Ethernet  HWaddr a6:cc:a0:52:17:4c
> > >           inet addr:192.168.2.2  Bcast:192.168.2.255
>  Mask:255.255.255.0
> > >           inet6 addr: fe80::f425:39ff:fe31:15d8/64 Scope:Link
> > >           UP BROADCAST RUNNING  MTU:1500  Metric:1
> > >           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:0 (0.0 B)  TX bytes:468 (468.0 B)
> > >
> > > eth0      Link encap:Ethernet  HWaddr 08:00:27:0f:8d:47
> > >           inet6 addr: fe80::a00:27ff:fe0f:8d47/64 Scope:Link
> > >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> > >           RX packets:285 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:397 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:1000
> > >           RX bytes:54697 (54.6 KB)  TX bytes:61879 (61.8 KB)
> > >
> > > 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:65536  Metric:1
> > >           RX packets:1902 errors:0 dropped:0 overruns:0 frame:0
> > >           TX packets:1902 errors:0 dropped:0 overruns:0 carrier:0
> > >           collisions:0 txqueuelen:0
> > >           RX bytes:147656 (147.6 KB)  TX bytes:147656 (147.6 KB)
> > >
> > > root at shahryarvm2-VirtualBox:~# route -n
> > > Kernel IP routing table
> > > Destination     Gateway         Genmask         Flags Metric Ref
>  Use Iface
> > > 0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0
>  0 br0
> > > 192.168.1.0     0.0.0.0         255.255.255.0   U     0      0
>  0 br0
> > > 192.168.2.0     0.0.0.0         255.255.255.0   U     0      0
>  0 br1
> > >
> > >
> > > Interestingly, the VXLAN is not showing up as port in ovs-dpctl show
> output:
> > >
> > > root at shahryarvm2-VirtualBox:~# ovs-dpctl show
> > > system at ovs-system:
> > >       lookups: hit:70 missed:36 lost:0
> > >       flows: 2
> > >       port 0: ovs-system (internal)
> > >       port 1: br0 (internal)
> > >       port 2: eth0
> > >       port 3: tep0 (internal)
> > >       port 4: br1 (internal)
> > >
> > > And i got the following message in the logs:
> > >
> > > 2013-07-26T18:11:02Z|00011|dpif|WARN|system at ovs-system: failed to add
> vxlan1 as port: Address family not supported by protocol
> > >
> > > What does it mean by address family not supported by protocol? .It
> seems that VXLAN is not working at all. I know i am missing some important
> part of the configuration. Could somebody please help me. Thanks!
> > >
> > You are likely not running the OVS kernel module included with upstream
> Open vSwitch, and instead are running the OVS kernel module in upstream
> Linux. What does "modinfo openvswitch" indicate? It should indicate the
> matching version of your OVS userspace bits (1.10 and later for VXLAN
> support).
> >
> > Thanks,
> > Kyle
> >
> > >
> > >
> > >
> > > _______________________________________________
> > > discuss mailing list
> > > discuss at openvswitch.org
> > > http://openvswitch.org/mailman/listinfo/discuss
> >
> >
> >
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20130730/66b65962/attachment.html>


More information about the discuss mailing list