On Mon, Nov 8, 2021 at 5:05 PM Numan Siddique <[email protected]> wrote: > > + Ihar if he has any comments. > > Thanks > Numan >
Due to the limitations of VxLAN, I don't think OVN interconnect is supported with VxLAN. Please see the ovn-architecture man pages. -- When VXLAN tunneling is enabled in an OVN cluster, due to the limited range available for VNIs, Interconnection feature is not supported. --- Thanks Numan > On Mon, Nov 8, 2021 at 4:57 PM Vladislav Odintsov <[email protected]> wrote: > > > > Hi, > > > > is seems like I found a regression with a latest ovn main branch code using > > ovn-ic. > > My setup utilises ramp switches (ovn-controller-vtep), so some chassis have > > vxlan encap. > > But I guess the problem affects non-vtep switch VXLAN installations too. > > OVN IC transit switches use tunnel key ids > OVN_MAX_DP_KEY_LOCAL > > (OVN_MAX_DP_KEY - OVN_MAX_DP_GLOBAL_NUM) > > so if user has at least one VXLAN-enabled chassis and interconnected > > with transit switch LRs he/she will get in northd logs lots of next > > messages: > > > > 2021-11-08T21:03:32.606Z|00132|northd|WARN|Tunnel key 16711897 for datapath > > vpc-6A0E5C34-global is incompatible with VXLAN > > 2021-11-08T21:04:32.607Z|00133|northd|WARN|Dropped 27 log messages in last > > 60 seconds (most recently, 31 seconds ago) due to excessive rate > > > > In commit [1] this logic was introduced. I can’t understand from the code > > and from commit itself > > if previous behaviour can be supported, but maybe I’m missing something. > > Can somebody help on this please? > > > > Thanks. > > > > 1: > > https://github.com/ovn-org/ovn/commit/fd44d75959cedcedf1f103173be1d9fa1abd9cb8 > > > > Regards, > > Vladislav Odintsov > > > > _______________________________________________ > > dev mailing list > > [email protected] > > https://mail.openvswitch.org/mailman/listinfo/ovs-dev _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
