summaryrefslogtreecommitdiff
path: root/lib/northbound_cli.c
diff options
context:
space:
mode:
authorChirag Shah <chirag@cumulusnetworks.com>2020-08-07 13:01:58 -0700
committerPat Ruddy <pat@voltanet.io>2020-08-12 12:39:34 +0100
commit707b76d79555dc2c5e130c6f2dc79827a54c112c (patch)
treeeace8d45dabe4d3dec9e2539f2d834aea08e4797 /lib/northbound_cli.c
parent1718bc783a24735c0a61516e5e760e02d7eca247 (diff)
zebra: Revert "zebra: probe local inactive neigh"
Reverting probing of neigh entry. There is a timing where probe and remote macip add request comes at the same time resulting in neigh to remain in local state event though it should be remote. In mobility case, the host moves to remote VTEP, first MAC only type-2 route is received which triggers a PROBE of neighs (associated to MAC). PROBE request can go via network port to remote VTEP. PROBE request picks up local neigh with MAC entry's outgoing port is remote VTEP tunnel port. The PROBE reply and MAC-IP (containing IP) almost comes same time at DUT. DUT first processes remote macip and installs neigh as remote. Followed by receives neigh as REACHABLE which marks neigh as LOCAL. FRR does have BPF filter which does not allow its own netlink request to receive. Otherwise frr's request to program neigh as remote can move neigh from local to remote. Though ordering can not be guranteed that REACHABLE (PROBE's repsonse) can come at anytime and move it to LOCAL. This fix would not suffice the needs of converging LOCAL inactive neighs to remove from DB. As mobility draft sugges to PROBE local neigh when MAC moves to remote but it is not working with current framework. Ticket:CM-22864 This reverts commit 44bc8ae5508975f216ad1cbb42884579896e7258 Signed-off-by: Chirag Shah <chirag@cumulusnetworks.com>
Diffstat (limited to 'lib/northbound_cli.c')
0 files changed, 0 insertions, 0 deletions