summaryrefslogtreecommitdiff
path: root/zebra/interface.h
diff options
context:
space:
mode:
authorAnuradha Karuppiah <anuradhak@cumulusnetworks.com>2018-09-12 11:33:51 -0700
committerDonald Sharp <sharpd@cumulusnetworks.com>2018-09-18 10:41:53 -0400
commit520ebf72b27c2462ce8b0dc5a1d4cb83956df69c (patch)
treeaceba5b51cb3f7510efe328817eb419237bd7244 /zebra/interface.h
parent66e3798747385bbcd6cfbd647e1945718c565dd3 (diff)
zebra: resolve link dependencies post nldump
Netdevices are not sorted in any fashion by the kernel during the initial interface nldump. So you can get an upper device (such as an SVI) before its corresponding lower device (bridge). To fix this problem we skip resolving link dependencies during handling of nldump notifications. Resolving instead at the end (when all the devices are present) Signed-off-by: Anuradha Karuppiah <anuradhak@cumulusnetworks.com> Ticket: CM-22388, CM-21796 Reviewed By: CCR-7845 Testing Done: 1. verified on a setup with missing linkages 2. automation - evpn-min
Diffstat (limited to 'zebra/interface.h')
-rw-r--r--zebra/interface.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/zebra/interface.h b/zebra/interface.h
index 02a05e6146..c6d8b24b01 100644
--- a/zebra/interface.h
+++ b/zebra/interface.h
@@ -348,6 +348,7 @@ extern int ipv6_address_configured(struct interface *ifp);
extern void if_handle_vrf_change(struct interface *ifp, vrf_id_t vrf_id);
extern void zebra_if_update_link(struct interface *ifp, ifindex_t link_ifindex,
ns_id_t ns_id);
+extern void zebra_if_update_all_links(void);
extern void vrf_add_update(struct vrf *vrfp);