summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDonatas Abraitis <donatas@opensourcerouting.org>2025-01-29 22:24:39 +0200
committerMergify <37929162+mergify[bot]@users.noreply.github.com>2025-02-04 16:37:55 +0000
commit388f9ef0cbdfefb5e36a3719954e8f865bf3ce2a (patch)
tree07b924c1e0a8f46065ee39dd7fb13d8fd6d5e533
parent704372bf4bb552bf011d4d9fa5dace874a49b0ed (diff)
doc: Say that 0.0.0.0 (0) BGP identifier is invalid
Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org> (cherry picked from commit c9a29289548028163a8d1edd55dbf03f27d53484)
-rw-r--r--doc/user/bgp.rst6
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst
index 1493c2fb98..5add30b6f4 100644
--- a/doc/user/bgp.rst
+++ b/doc/user/bgp.rst
@@ -282,7 +282,9 @@ internal or external.
interface and address information. In that case default router ID value is
selected as the largest IP Address of the interfaces. When `router zebra` is
not enabled *bgpd* can't get interface information so `router-id` is set to
- 0.0.0.0. So please set router-id by hand.
+ 0.0.0.0, which is invalid and BGP session can't be established.
+
+ So please set router-id by manually.
.. _bgp-multiple-autonomous-systems:
@@ -2938,7 +2940,7 @@ BGP Extended Communities in Route Map
``CO:COLOR``
This is a format to define colors value. ``CO`` part is always 00 (default),
- it can be used to support the requirements of Color-Only steering when using
+ it can be used to support the requirements of Color-Only steering when using
a Null Endpoint in the SR-TE Policy as specified in Section 8.8 of [RFC9256].
The below shows in detail what the different combinations of ``CO`` bits can
match on to for the purpose of determining what type of SR-TE Policy Tunnel