doc: Update VRF 2 VRF route leaking documentation for bgp

Signed-off-by: Donald Sharp <sharpd@cumulusnetworks.com>

1 files changed, 14 insertions, 1 deletions

diff --git a/doc/user/bgp.rst b/doc/user/bgp.rst
index 3298460a58..bca52fed3f 100644
--- a/doc/user/bgp.rst
+++ b/doc/user/bgp.rst
@@ -1549,7 +1549,8 @@ is specified, the BGP protocol process belongs to the default VRF.
 
 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 common application of this feature is to
+of the default VRF and VPN) or routes may be leaked directly between two BGP
+VRF instances.  A common application of the VPN-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
@@ -1586,6 +1587,8 @@ routing domain which is shared across all its sites. More complex routing
 topologies are possible through use of additional route-targets to augment the
 leaking of sets of routes in various ways.
 
+For direct VRF to VRF leaking the RD and RT are auto-derived.
+
 Configuration
 -------------
 
@@ -1667,6 +1670,16 @@ address-family:
 
    Disables import or export of routes between the current unicast VRF and VPN.
 
+.. index:: import vrf VRFNAME
+.. clicmd:: import vrf VRFNAME
+
+   Enables direct importation of VRF routes to another VRF.  The RD and RT
+   are auto derived and are not needed for VRF - VRF route leaking.
+
+.. index:: no import vrf VRFNAME
+.. clicmd:: no import vrf VRFNAME
+
+   Disables direct VRF to VRF route leaking.
 
 .. _displaying-bgp-information: