diff options
| author | vishaldhingra <vdhingra@vmware.com> | 2019-05-06 11:45:32 +0200 |
|---|---|---|
| committer | vishaldhingra <vdhingra@vmware.com> | 2019-06-19 13:37:51 +0200 |
| commit | 03ff9a14108aea05efe4541a48b24f499bb6286d (patch) | |
| tree | bf2ba18b6009f1079b863a9d482271dd82ba8533 /doc | |
| parent | bgpd : Support for exact-match in match clause for lcommunity (diff) | |
| download | frr-03ff9a14108aea05efe4541a48b24f499bb6286d.tar.xz frr-03ff9a14108aea05efe4541a48b24f499bb6286d.zip | |
bgpd : Support for exact-match in match clause for lcommunity
FRR has a provision to give exact-match in match clause for
standard community, but this option is missing for lcommunity.
Part 2 : CLI related changes for match clause
Signed-off-by: vishaldhingra <vdhingra@vmware.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/user/bgp.rst | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst index a33a089b1..843d4f4ae 100644 --- a/doc/user/bgp.rst +++ b/doc/user/bgp.rst @@ -1797,13 +1797,15 @@ Two types of large community lists are supported, namely `standard` and Large Communities in Route Map """""""""""""""""""""""""""""" -.. index:: match large-community LINE -.. clicmd:: match large-community LINE +.. index:: match large-community LINE [exact-match] +.. clicmd:: match large-community LINE [exact-match] Where `line` can be a simple string to match, or a regular expression. It is very important to note that this match occurs on the entire large-community string as a whole, where each large-community is ordered - from lowest to highest. + from lowest to highest. When `exact-match` keyword is specified, match + happen only when BGP updates have completely same large communities value + specified in the large community list. .. index:: set large-community LARGE-COMMUNITY .. clicmd:: set large-community LARGE-COMMUNITY |