Merge pull request #6422 from rudis/master

Doc: minor fixes
This commit is contained in:
Donatas Abraitis 2020-05-17 14:31:02 +03:00 committed by GitHub
commit ef022660b4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 15 additions and 15 deletions

View File

@ -971,7 +971,7 @@ Route Aggregation-IPv4 Address Family
.. clicmd:: aggregate-address A.B.C.D/M summary-only .. clicmd:: aggregate-address A.B.C.D/M summary-only
This command specifies an aggregate address. Aggregated routes will This command specifies an aggregate address. Aggregated routes will
not be announce. not be announced.
.. index:: no aggregate-address A.B.C.D/M .. index:: no aggregate-address A.B.C.D/M
.. clicmd:: no aggregate-address A.B.C.D/M .. clicmd:: no aggregate-address A.B.C.D/M
@ -1023,7 +1023,7 @@ Route Aggregation-IPv6 Address Family
.. clicmd:: aggregate-address X:X::X:X/M summary-only .. clicmd:: aggregate-address X:X::X:X/M summary-only
This command specifies an aggregate address. Aggregated routes will This command specifies an aggregate address. Aggregated routes will
not be announce. not be announced.
.. index:: no aggregate-address X:X::X:X/M .. index:: no aggregate-address X:X::X:X/M
.. clicmd:: no aggregate-address X:X::X:X/M .. clicmd:: no aggregate-address X:X::X:X/M
@ -1776,7 +1776,7 @@ In :ref:`route-map` we can match on or set the BGP communities attribute. Using
this feature network operator can implement their network policy based on BGP this feature network operator can implement their network policy based on BGP
communities attribute. communities attribute.
The ollowing commands can be used in route maps: The following commands can be used in route maps:
.. index:: match community WORD exact-match [exact-match] .. index:: match community WORD exact-match [exact-match]
.. clicmd:: match community WORD exact-match [exact-match] .. clicmd:: match community WORD exact-match [exact-match]

View File

@ -83,8 +83,8 @@ sharing a link, for example:
- DR/BDR election results. - DR/BDR election results.
- Any optional capabilities supported by each router. - Any optional capabilities supported by each router.
The Hello protocol is comparatively trivial and will not be explored in greater The Hello protocol is comparatively trivial and will not be explored in more
detail than here. detail.
.. index:: OSPF LSA overview .. index:: OSPF LSA overview
.. _ospf-lsas: .. _ospf-lsas:
@ -233,7 +233,7 @@ called `intra-area routes`.
Cost Cost
The output cost of that interface, scaled inversely to some commonly known The output cost of that interface, scaled inversely to some commonly known
reference value, :clicmd:`auto-cost reference-bandwidth (1-4294967`. reference value, :clicmd:`auto-cost reference-bandwidth (1-4294967)`.
Link Type Link Type
Transit Network Transit Network

View File

@ -14,7 +14,7 @@ across these next hops. In practice, flow-based hashing is used so that
all traffic associated with a particular flow uses the same next hop, all traffic associated with a particular flow uses the same next hop,
and by extension, the same path across the network. and by extension, the same path across the network.
Weigted ECMP using BGP link bandwidth introduces support for network-wide Weighted ECMP using BGP link bandwidth introduces support for network-wide
unequal cost multipathing (UCMP) to an IP destination. The unequal cost unequal cost multipathing (UCMP) to an IP destination. The unequal cost
load balancing is implemented by the forwarding plane based on the weights load balancing is implemented by the forwarding plane based on the weights
associated with the next hops of the IP prefix. These weights are computed associated with the next hops of the IP prefix. These weights are computed