doc: Say that 0.0.0.0 (0) BGP identifier is invalid

Signed-off-by: Donatas Abraitis <donatas@opensourcerouting.org>
(cherry picked from commit c9a2928954)
This commit is contained in:
Donatas Abraitis 2025-01-29 22:24:39 +02:00 committed by Mergify
parent 704372bf4b
commit 388f9ef0cb

View File

@ -282,7 +282,9 @@ internal or external.
interface and address information. In that case default router ID value is 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 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 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: .. _bgp-multiple-autonomous-systems:
@ -2938,7 +2940,7 @@ BGP Extended Communities in Route Map
``CO:COLOR`` ``CO:COLOR``
This is a format to define colors value. ``CO`` part is always 00 (default), 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]. 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 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 match on to for the purpose of determining what type of SR-TE Policy Tunnel