summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorLou Berger <lberger@labn.net>2018-06-23 16:47:32 +0200
committerLou Berger <lberger@labn.net>2018-06-23 16:47:32 +0200
commitf90115c5607fe6070b2e0aef8b367076f2348490 (patch)
treebb00bd26082e0548bc9e03dc408e10fd1ef1731e /doc
parentbgpd: allow for case where vrf sockets aren't needed (default accepts for vrf) (diff)
downloadfrr-f90115c5607fe6070b2e0aef8b367076f2348490.tar.xz
frr-f90115c5607fe6070b2e0aef8b367076f2348490.zip
user: minor tweaks to bgp VRF documentation
Signed-off-by: Lou Berger <lberger@labn.net>
Diffstat (limited to 'doc')
-rw-r--r--doc/user/bgp.rst34
-rw-r--r--doc/user/zebra.rst4
2 files changed, 26 insertions, 12 deletions
diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst
index 13e025221..0ea93a62e 100644
--- a/doc/user/bgp.rst
+++ b/doc/user/bgp.rst
@@ -60,11 +60,11 @@ Address Families
----------------
Multiprotocol BGP enables BGP to carry routing information for multiple Network
-Layer protocols. BGP supports multiple Address Family Identifier (AFI), namely
-IPv4 and IPv6. Support is also provided for multiple sets of per-AFI
-information via Subsequent Address Family Identifiers (SAFI). In addition to
-unicast information, VPN information :rfc:`4364` and :rfc:`4659`, and
-Encapsulation attribute :rfc:`5512` is supported.
+Layer protocols. BGP supports an Address Family Identifier (AFI) for IPv4 and
+IPv6. Support is also provided for multiple sets of per-AFI information via the
+BGP Subsequent Address Family Identifier (SAFI). FRR supports SAFIs for unicast
+information, labeled information :rfc:`3107` and :rfc:`8277`, and Layer 3 VPN
+information :rfc:`4364` and :rfc:`4659`.
.. _bgp-route-selection:
@@ -174,6 +174,19 @@ will establish the connection with unicast only capability. When there are no
common capabilities, FRR sends Unsupported Capability error and then resets the
connection.
+.. _bgp-concepts-vrfs:
+
+VRFs: Virtual Routing and Forwarding
+------------------------------------
+
+*bgpd* supports :abbr:`L3VPN (Layer 3 Virtual Private Networks)` :abbr:`VRFs
+(Virtual Routing and Forwarding tables)` for IPv4 :rfc:`4364` and IPv6
+:rfc:`4659`. L3VPN routes, and their associated VRF MPLS labels, can be
+distributed to VPN SAFI neighbors in the *default*, i.e., non VRF, BGP
+instance. VRF MPLS labels are reached using *core* MPLS labels which are
+distributed using LDP or BGP labeled unicast. *bgpd* also supports inter-VRF
+route leaking. General information on FRR's VRF support can be found in
+:ref:`zebra-vrf`.
.. _bgp-router-configuration:
@@ -1550,10 +1563,11 @@ VRF Route Leaking
^^^^^^^^^^^^^^^^^
BGP routes may be leaked (i.e. copied) between a unicast VRF RIB and the VPN
-SAFI RIB of the default VRF (leaking is also permitted between the unicast RIB
-of the default VRF and VPN). A shortcut syntax is also available for specifying
-leaking from one vrf to another vrf using the VPN RIB as the intemediary. A
-common application of the VPN-VRF feature is to connect a customer's private
+SAFI RIB of the default VRF for use in MPLS-based L3VPNs. Unicast routes may
+also be leaked between any VRFs (including the unicast RIB of the default BGP
+instanced). A shortcut syntax is also available for specifying leaking from one
+VRF to another VRF using the default instance's VPN RIB as the intemediary. A
+common application of the VRF-VRF feature is to connect a customer's private
routing domain to a provider's VPN service. Leaking is configured from the
point of view of an individual VRF: ``import`` refers to routes leaked from VPN
to a unicast VRF, whereas ``export`` refers to routes leaked from a unicast VRF
@@ -1596,7 +1610,7 @@ auto-derived.
General configuration
"""""""""""""""""""""
-Configuration of route leaking between a unicast VRF RIB and the VPN safi RIB
+Configuration of route leaking between a unicast VRF RIB and the VPN SAFI RIB
of the default VRF is accomplished via commands in the context of a VRF
address-family:
diff --git a/doc/user/zebra.rst b/doc/user/zebra.rst
index b6060f073..180d2d7ef 100644
--- a/doc/user/zebra.rst
+++ b/doc/user/zebra.rst
@@ -46,7 +46,7 @@ Besides the common invocation options (:ref:`common-invocation-options`), the
ZEBRA will create an associated VRF. The other daemons will operate on the VRF
VRF defined by *Zebra*, as usual.
- .. seealso:: :ref:`vrf`
+ .. seealso:: :ref:`zebra-vrf`
.. option:: --v6-rr-semantics
@@ -396,7 +396,7 @@ default) should the specified gateways not be reachable. E.g.:
After setting TABLENO with this command, static routes defined after this
are added to the specified table.
-.. _vrf:
+.. _zebra-vrf:
Virtual Routing and Forwarding
==============================