summaryrefslogtreecommitdiffstats
path: root/doc/user
diff options
context:
space:
mode:
authorQuentin Young <qlyoung@cumulusnetworks.com>2018-10-02 17:31:48 +0200
committerQuentin Young <qlyoung@cumulusnetworks.com>2018-10-02 22:14:14 +0200
commit195c746165ac5c04a08afbdbdc2dd257d090ee42 (patch)
tree1e60ea7d85d1c00719cfa1fa12aa31a728dabf86 /doc/user
parentdoc: add extra information on bgp views and vrfs (diff)
downloadfrr-195c746165ac5c04a08afbdbdc2dd257d090ee42.tar.xz
frr-195c746165ac5c04a08afbdbdc2dd257d090ee42.zip
doc: embellish bgp view docs
Signed-off-by: Quentin Young <qlyoung@cumulusnetworks.com>
Diffstat (limited to 'doc/user')
-rw-r--r--doc/user/bgp.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst
index 6bd25a9db..f10883b98 100644
--- a/doc/user/bgp.rst
+++ b/doc/user/bgp.rst
@@ -303,11 +303,11 @@ In addition to supporting multiple autonomous systems, FRR's BGP implementation
also supports *views*.
BGP views are almost the same as normal BGP processes, except that routes
-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.
+selected by BGP are not installed into the kernel routing table. Each BGP view
+provides an independent set of routing information which is only distributed
+via BGP. Multiple views can be supported, and BGP view information is always
+independent from other routing protocols and Zebra/kernel routes. BGP views use
+the core instance (i.e., default VRF) for communication with peers.
.. index:: router bgp AS-NUMBER view NAME
.. clicmd:: router bgp AS-NUMBER view NAME