summaryrefslogtreecommitdiffstats
path: root/zebra/zebra_tc.c
diff options
context:
space:
mode:
authorsharathr <sharathr@cumulusnetworks.com>2021-10-08 16:27:50 +0200
committerStephen Worley <sworley@nvidia.com>2023-02-14 00:12:05 +0100
commit00d30205eff94a0940e895ea0558355b48de0574 (patch)
tree20a356254f7a45a682d6bc990b88eae48e4be701 /zebra/zebra_tc.c
parentzebra: Clean remote FDB entries upon VNI removal (diff)
downloadfrr-00d30205eff94a0940e895ea0558355b48de0574.tar.xz
frr-00d30205eff94a0940e895ea0558355b48de0574.zip
zebra: fix for unexpected fdb entry showing up during ifdown/ifup events
Ticket: 2674793 Testing Done: precommit, evpn-min and evpn-smoke The problem in this case is whenever we are triggering ifdown followed by ifup of bridge, we see that remote mac entries are programmed with vlan-1 in the fdb from zebra and never cleaned up. bridge has vlan_default_pvid 1 which means any port that gets added will initially have vlan 1 which then gets deleted by ifupdown2 and the proper vlan gets added. The problem lies in zebra where we are not cleaning up the remote macs during vlan change. Fix is to uninstall the remote macs and then install them during vlan change. Signed-off-by: Stephen Worley <sworley@nvidia.com>
Diffstat (limited to 'zebra/zebra_tc.c')
0 files changed, 0 insertions, 0 deletions