From c1bcac1d7802bddaa3f9e023c4ef8588007db864 Mon Sep 17 00:00:00 2001 From: Donatas Abraitis Date: Fri, 24 Jul 2020 11:07:06 +0300 Subject: [PATCH] doc: Add new bgpd command `maximum-prefix force` Signed-off-by: Donatas Abraitis --- doc/user/bgp.rst | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst index bb968735b9..2ef78bcd6b 100644 --- a/doc/user/bgp.rst +++ b/doc/user/bgp.rst @@ -1297,8 +1297,8 @@ Configuring Peers This command specifies a default `weight` value for the neighbor's routes. -.. index:: [no] neighbor PEER maximum-prefix NUMBER -.. clicmd:: [no] neighbor PEER maximum-prefix NUMBER +.. index:: [no] neighbor PEER maximum-prefix NUMBER [force] +.. clicmd:: [no] neighbor PEER maximum-prefix NUMBER [force] Sets a maximum number of prefixes we can receive from a given peer. If this number is exceeded, the BGP session will be destroyed. @@ -1310,6 +1310,11 @@ Configuring Peers granular and offers much smarter matching criterion than number of received prefixes, making it more suited to implementing policy. + If _force_ is set, then ALL prefixes are counted for maximum instead of + accepted only. This is useful for cases where an inbound filter is applied, + but you want maximum-prefix to act on ALL (including filtered) prefixes. This + option requires `soft-reconfiguration inbound` to be enabled for the peer. + .. index:: [no] neighbor PEER maximum-prefix-out NUMBER .. clicmd:: [no] neighbor PEER maximum-prefix-out NUMBER -- 2.39.5