From 388f9ef0cbdfefb5e36a3719954e8f865bf3ce2a Mon Sep 17 00:00:00 2001 From: Donatas Abraitis Date: Wed, 29 Jan 2025 22:24:39 +0200 Subject: [PATCH] doc: Say that 0.0.0.0 (0) BGP identifier is invalid Signed-off-by: Donatas Abraitis (cherry picked from commit c9a29289548028163a8d1edd55dbf03f27d53484) --- doc/user/bgp.rst | 6 ++++-- 1 file 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