From edde3ce9c21143f463537c86c7cdd006583facd9 Mon Sep 17 00:00:00 2001 From: Quentin Young Date: Mon, 1 Oct 2018 17:30:56 +0000 Subject: [PATCH] doc: add extra information on bgp views and vrfs Signed-off-by: Quentin Young --- doc/user/bgp.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst index b84a9e8f82..6bd25a9dbe 100644 --- a/doc/user/bgp.rst +++ b/doc/user/bgp.rst @@ -235,8 +235,10 @@ However, the same AS can be used with different VRFs. .. note:: The separated nature of VRFs makes it possible to peer a single *bgpd* - process to itself, on one machine. This can be used for prototyping and - other purposes. + process to itself, on one machine. Note that this can be done fully within + BGP without a corresponding VRF in the kernel or Zebra, which enables some + practical use cases such as :ref:`route reflectors ` + and route servers. Configuration of additional autonomous systems, or of a router that targets a specific VRF, is accomplished with the following command: @@ -305,6 +307,8 @@ selected by BGP are not installed into the kernel routing table. The view functionality allows the exchange of BGP routing information without affecting the kernel routing tables. +Peers configured within a view and their traffic exist within the default VRF. + .. index:: router bgp AS-NUMBER view NAME .. clicmd:: router bgp AS-NUMBER view NAME -- 2.39.5