mirror of
https://git.proxmox.com/git/mirror_frr
synced 2025-08-04 20:18:54 +00:00
doc: Add documentation for aggregate-address with route-map support
Additionally remove trailling/unnecesarry whitespaces and align code snippets correctly. Signed-off-by: Donatas Abraitis <donatas.abraitis@gmail.com>
This commit is contained in:
parent
5fba22485b
commit
ac2201bbcd
@ -675,6 +675,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
|
||||
|
||||
@ -689,11 +694,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
|
||||
@ -703,6 +708,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
|
||||
|
||||
|
||||
@ -716,6 +722,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
|
||||
|
||||
@ -734,16 +745,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:
|
||||
@ -2300,7 +2312,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
|
||||
@ -2317,8 +2329,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
|
||||
@ -2331,8 +2343,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:
|
||||
|
Loading…
Reference in New Issue
Block a user