summaryrefslogtreecommitdiffstats
path: root/yang
diff options
context:
space:
mode:
authorDonatas Abraitis <donatas.abraitis@gmail.com>2020-11-12 11:30:19 +0100
committerDonatas Abraitis <donatas.abraitis@gmail.com>2020-12-11 13:51:05 +0100
commit2adac2562a02fb20cb5fc783c2e6019a1a76354f (patch)
treebba5c614ff7931bc77ed7d44a00e7ab617e32dba /yang
parentMerge pull request #7683 from volta-networks/feat_zapi_client_close (diff)
downloadfrr-2adac2562a02fb20cb5fc783c2e6019a1a76354f.tar.xz
frr-2adac2562a02fb20cb5fc783c2e6019a1a76354f.zip
bgpd: Do not send BGP UPDATE if the route actually not changed
Reference: https://www.cmand.org/communityexploration --y2-- / | \ c1 ---- x1 ---- y1 | z1 \ | / --y3-- 1. z1 announces 192.168.255.254/32 to y2, y3. 2. y2 and y3 tags this prefix at ingress with appropriate communities 65004:2 (y2) and 65004:3 (y3). 3. x1 filters all communities at the egress to c1. 4. Shutdown the link between y1 and y2. 5. y1 will generate a BGP UPDATE message regarding the next-hop change. 6. x1 will generate a BGP UPDATE message regarding community change. To avoid sending duplicate BGP UPDATE messages we should make sure we send only actual route updates. In this example, x1 will skip BGP UPDATE to c1 because the actual route is the same (filtered communities - nothing changes). Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
Diffstat (limited to 'yang')
-rw-r--r--yang/frr-bgp-common.yang7
1 files changed, 7 insertions, 0 deletions
diff --git a/yang/frr-bgp-common.yang b/yang/frr-bgp-common.yang
index cb1a6a8f5..1840e3728 100644
--- a/yang/frr-bgp-common.yang
+++ b/yang/frr-bgp-common.yang
@@ -358,6 +358,13 @@ submodule frr-bgp-common {
"Apply administrative shutdown to newly configured peers.";
}
+ leaf suppress-duplicates {
+ type boolean;
+ default "true";
+ description
+ "Suppress duplicate updates if the route actually not changed.";
+ }
+
leaf ebgp-requires-policy {
type boolean;
default "true";