summaryrefslogtreecommitdiffstats
path: root/doc/user
diff options
context:
space:
mode:
authorLou Berger <lberger@labn.net>2019-09-10 17:59:10 +0200
committerGitHub <noreply@github.com>2019-09-10 17:59:10 +0200
commitccc13acc0ff1f7ba1757071d516c74785de787c7 (patch)
tree55bcee24cde419c09995ef8c6495d70b3e98adf8 /doc/user
parentMerge pull request #4933 from chiragshah6/evpn_dev2 (diff)
parentdoc: Add documentation for aggregate-address with route-map support (diff)
downloadfrr-ccc13acc0ff1f7ba1757071d516c74785de787c7.tar.xz
frr-ccc13acc0ff1f7ba1757071d516c74785de787c7.zip
Merge pull request #4866 from ton31337/feature/apply_route-map_for_aggregate-address
bgpd: Apply route-map for aggregate-address
Diffstat (limited to 'doc/user')
-rw-r--r--doc/user/bgp.rst34
1 files changed, 23 insertions, 11 deletions
diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst
index 7883d0e4c..7b3cdf2c4 100644
--- a/doc/user/bgp.rst
+++ b/doc/user/bgp.rst
@@ -685,6 +685,11 @@ Route Aggregation-IPv4 Address Family
This command specifies an aggregate address.
+.. index:: aggregate-address A.B.C.D/M route-map NAME
+.. clicmd:: aggregate-address A.B.C.D/M route-map NAME
+
+ Apply a route-map for an aggregated prefix.
+
.. index:: aggregate-address A.B.C.D/M as-set
.. clicmd:: aggregate-address A.B.C.D/M as-set
@@ -699,11 +704,11 @@ Route Aggregation-IPv4 Address Family
.. index:: no aggregate-address A.B.C.D/M
.. clicmd:: no aggregate-address A.B.C.D/M
-
+
This command removes an aggregate address.
- This configuration example setup the aggregate-address under
+ This configuration example setup the aggregate-address under
ipv4 address-family.
.. code-block:: frr
@@ -713,6 +718,7 @@ Route Aggregation-IPv4 Address Family
aggregate-address 10.0.0.0/8
aggregate-address 20.0.0.0/8 as-set
aggregate-address 40.0.0.0/8 summary-only
+ aggregate-address 50.0.0.0/8 route-map aggr-rmap
exit-address-family
@@ -726,6 +732,11 @@ Route Aggregation-IPv6 Address Family
This command specifies an aggregate address.
+.. index:: aggregate-address X:X::X:X/M route-map NAME
+.. clicmd:: aggregate-address X:X::X:X/M route-map NAME
+
+ Apply a route-map for an aggregated prefix.
+
.. index:: aggregate-address X:X::X:X/M as-set
.. clicmd:: aggregate-address X:X::X:X/M as-set
@@ -744,16 +755,17 @@ Route Aggregation-IPv6 Address Family
This command removes an aggregate address.
- This configuration example setup the aggregate-address under
- ipv4 address-family.
+ This configuration example setup the aggregate-address under
+ ipv6 address-family.
.. code-block:: frr
router bgp 1
address-family ipv6 unicast
aggregate-address 10::0/64
- aggregate-address 20::0/64 as-set
- aggregate-address 40::0/64 summary-only
+ aggregate-address 20::0/64 as-set
+ aggregate-address 40::0/64 summary-only
+ aggregate-address 50::0/64 route-map aggr-rmap
exit-address-family
.. _bgp-redistribute-to-bgp:
@@ -2321,7 +2333,7 @@ attribute.
Displaying Routes by Large Community Attribute
----------------------------------------------
-The following commands allow displaying routes based on their
+The following commands allow displaying routes based on their
large community attribute.
.. index:: show [ip] bgp <ipv4|ipv6> large-community
@@ -2338,8 +2350,8 @@ large community attribute.
These commands display BGP routes which have the large community attribute.
attribute. When ``LARGE-COMMUNITY`` is specified, BGP routes that match that
- large community are displayed. When `exact-match` is specified, it display
- only routes that have an exact match. When `json` is specified, it display
+ large community are displayed. When `exact-match` is specified, it display
+ only routes that have an exact match. When `json` is specified, it display
routes in json format.
.. index:: show [ip] bgp <ipv4|ipv6> large-community-list WORD
@@ -2352,8 +2364,8 @@ large community attribute.
.. clicmd:: show [ip] bgp <ipv4|ipv6> large-community-list WORD json
These commands display BGP routes for the address family specified that
- match the specified large community list. When `exact-match` is specified,
- it displays only routes that have an exact match. When `json` is specified,
+ match the specified large community list. When `exact-match` is specified,
+ it displays only routes that have an exact match. When `json` is specified,
it display routes in json format.
.. _bgp-display-routes-by-as-path: