[ovs-discuss] how to avoid loops in full mesh vxlan tunnel connections

[Alex Wang]

Hi Soomyung,

I may not fully understand concept of "full mesh vxlan tunnel".

But I want to ask why do you need to setup 2 tunnels (with different keys)
between each pair of nodes? (From my experience that may create loop)

Could you try the topology with only one tunnel between each pair of nodes?

Kind Regards,
Alex Wang,


On Tue, Aug 27, 2013 at 12:43 AM, Soomyung Park <smpahk68 at hotmail.com>wrote:

> Hello.
>
> I need your help.
>
> There are no problem in configure 2 node vxlan connections.
> But, I have the problem(loop error) in 3 nodes vxlan connections.
>
> ovs' version is 1.10.0 and  OS is fedroa16(kernel version 3.6.10).
>
> What's the wrong in my configuration?
> Or, Does ovs support full mesh vxlan tunnel connection in 3 and more nodes?
>
> Thankyou for reading it.
>
>
> My topology as belows;
>
>
> [Node A] (p255p1:192.168.1.172)
>       \
>         \
>           \
>     [ L2 Switch]  ------- [Node B] (p255p1:192.168.1.173)
>            /
>          /
>        /
> [Node C] (p255p1:192.168.1.174)
>
> [Node A]'s ovs-vsctl show as belows;
> 262331e7-bc31-4f9f-94ae-4fae72aecf4c
>     Bridge "br5"
>         Port "vxlan5.174"
>             Interface "vxlan5.174"
>                 type: vxlan
>                 options: {key="5", remote_ip="192.168.1.174"}
>         Port "vxlan5.173"
>             Interface "vxlan5.173"
>                 type: vxlan
>                 options: {key="5", remote_ip="192.168.1.173"}
>         Port "br5"
>             Interface "br5"
>                 type: internal
>     Bridge "br2"
>         Port "vxlan2.174"
>             Interface "vxlan2.174"
>                 type: vxlan
>                 options: {key="2", remote_ip="192.168.1.174"}
>         Port "vxlan2.173"
>             Interface "vxlan2.173"
>                 type: vxlan
>                 options: {key="2", remote_ip="192.168.1.173"}
>         Port "br2"
>             Interface "br2"
>                 type: internal
>
> [Node B]'s ovs-vsctl show as belows;
> 4af5d138-4535-4f7b-89e5-732b596764bf
>     Bridge "br5"
>         Port "vxlan5.172"
>             Interface "vxlan5.172"
>                 type: vxlan
>                 options: {key="5", remote_ip="192.168.1.172"}
>         Port "vxlan5.174"
>             Interface "vxlan5.174"
>                 type: vxlan
>                 options: {key="5", remote_ip="192.168.1.174"}
>         Port "br5"
>             Interface "br5"
>                 type: internal
>     Bridge "br2"
>         Port "vxlan2.174"
>             Interface "vxlan2.174"
>                 type: vxlan
>                 options: {key="2", remote_ip="192.168.1.174"}
>         Port "br2"
>             Interface "br2"
>                 type: internal
>         Port "vxlan2.172"
>             Interface "vxlan2.172"
>                 type: vxlan
>                 options: {key="2", remote_ip="192.168.1.172"}
>
>
> [Node C]'s ovs-vsctl show as belows;
> 960717d6-62f0-4eb8-8515-e09ee6fefbe2
>     Bridge "br2"
>         Port "vxlan2.172"
>             Interface "vxlan2.172"
>                 type: vxlan
>                 options: {key="2", remote_ip="192.168.1.172"}
>         Port "br2"
>             Interface "br2"
>                 type: internal
>         Port "vxlan2.173"
>             Interface "vxlan2.173"
>                 type: vxlan
>                 options: {key="2", remote_ip="192.168.1.173"}
>     Bridge "br5"
>         Port "vxlan5.172"
>             Interface "vxlan5.172"
>                 type: vxlan
>                 options: {key="5", remote_ip="192.168.1.172"}
>         Port "br5"
>             Interface "br5"
>                 type: internal
>         Port "vxlan5.173"
>             Interface "vxlan5.173"
>                 type: vxlan
>                 options: {key="5", remote_ip="192.168.1.173"}
>
>
>
>
>
>
>
> _______________________________________________
> 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/20130829/5b1be26e/attachment.html>