It was not the intent to change the range of tunnel keys for vtep
setups. If that happens, we should fix it. Perhaps the range is not
touched but the range validation is activated in vtep case. If so, the
validation should be disabled.
Ihar
On 11/8/21 4:57 PM, Vladislav Odintsov 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
