From ffd2cc11cf718e42ab149c3c84feb2a7bb8aac0b Mon Sep 17 00:00:00 2001 From: fett0 Date: Fri, 5 Nov 2021 16:13:06 -0300 Subject: doc: L3vpn: settings --- docs/configuration/vrf/index.rst | 129 +++++++++++++++++++++++++++++++++++++++ 1 file changed, 129 insertions(+) (limited to 'docs/configuration/vrf/index.rst') diff --git a/docs/configuration/vrf/index.rst b/docs/configuration/vrf/index.rst index f475b7bf..4ec1d4df 100644 --- a/docs/configuration/vrf/index.rst +++ b/docs/configuration/vrf/index.rst @@ -317,5 +317,134 @@ VRF blue routing table C>* 10.20.0.0/24 is directly connected, eth2, 00:07:53 +##### +L3VPN VRFs +##### + +:abbr:`L3VPN VRFs ( Layer 3 Virtual Private Networks )` bgpd supports 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. + + +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 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 to +VPN. + + +.. note:: Routes exported from a unicast VRF to the VPN RIB must be augmented + by two parameters: + + an RD / RTLIST + + Configuration for these exported routes must, at a minimum, specify + these two parameters. + +Configuration +============= + +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. + +.. cfgcmd:: set vrf name protocols bgp address-family + rd vpn export + + Specifies the route distinguisher to be added to a route exported from the + current unicast VRF to VPN.Create new VRF instance with ``. The name + is used when placing individual interfaces into the VRF. + +.. cfgcmd:: set vrf name protocols bgp address-family + route-target vpn + [RTLIST] + + Specifies the route-target list to be attached to a route (export) or the + route-target list to match against (import) when exporting/importing + between the current unicast VRF and VPN.The RTLIST is a space-separated + list of route-targets, which are BGP extended community values as + described in Extended Communities Attribute. + +.. cfgcmd:: set vrf name protocols bgp address-family + label vpn export <0-1048575|auto> + + Enables an MPLS label to be attached to a route exported from the current + unicast VRF to VPN. If the value specified is auto, the label value is + automatically assigned from a pool maintained. + +.. cfgcmd:: set vrf name protocols bgp address-family + route-map vpn + [route-map ] + + Specifies an optional route-map to be applied to routes imported or + exported between the current unicast VRF and VPN. + +.. cfgcmd:: set vrf name protocols bgp address-family + vpn + + Enables import or export of routes between the current unicast VRF and VPN. + +.. cfgcmd:: set vrf name protocols bgp address-family + import vrf + + Shortcut syntax for specifying automatic leaking from vrf VRFNAME to the + current VRF using the VPN RIB as intermediary. The RD and RT are auto + derived and should not be specified explicitly for either the source or + destination VRF’s. + +Operation +========= + +It is not sufficient to only configure a L3VPN VRFs but L3VPN VRFs must be +maintained, too.For L3VPN VRF maintenance the following operational commands +are in place. + +.. opcmd:: show bgp vpn + + Print active IPV4 or IPV6 routes advertised via the VPN SAFI. + + .. code-block:: none + + BGP table version is 2, local router ID is 10.0.1.1, vrf id 0 + Default local pref 100, local AS 65001 + Status codes: s suppressed, d damped, h history, * valid, > best, = multipath, + i internal, r RIB-failure, S Stale, R Removed + Nexthop codes: @NNN nexthop's vrf id, < announce-nh-self + Origin codes: i - IGP, e - EGP, ? - incomplete + + Network Next Hop Metric LocPrf Weight Path + Route Distinguisher: 10.50.50.1:1011 + *>i10.50.50.0/24 10.0.0.7 0 100 0 i + UN=10.0.0.7 EC{65035:1011} label=80 type=bgp, subtype=0 + Route Distinguisher: 10.60.60.1:1011 + *>i10.60.60.0/24 10.0.0.10 0 100 0 i + UN=10.0.0.10 EC{65035:1011} label=80 type=bgp, subtype=0 + +.. opcmd:: show bgp vpn summary + + Print a summary of neighbor connections for the specified AFI/SAFI + combination. + + .. code-block:: none + + BGP router identifier 10.0.1.1, local AS number 65001 vrf-id 0 + BGP table version 0 + RIB entries 9, using 1728 bytes of memory + Peers 4, using 85 KiB of memory + Peer groups 1, using 64 bytes of memory + + Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd PfxSnt + 10.0.0.7 4 65001 2860 2870 0 0 0 1d23h34m 2 10 .. include:: /_include/common-references.txt -- cgit v1.2.3 From 8cbe0829743022d1816a77bb3f64b3b4d9ae2f39 Mon Sep 17 00:00:00 2001 From: fett0 Date: Fri, 5 Nov 2021 19:03:45 -0300 Subject: doc: L3vpn: settings --- docs/configuration/vrf/index.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/configuration/vrf/index.rst') diff --git a/docs/configuration/vrf/index.rst b/docs/configuration/vrf/index.rst index 4ec1d4df..b4f63479 100644 --- a/docs/configuration/vrf/index.rst +++ b/docs/configuration/vrf/index.rst @@ -317,9 +317,9 @@ VRF blue routing table C>* 10.20.0.0/24 is directly connected, eth2, 00:07:53 -##### +########## L3VPN VRFs -##### +########## :abbr:`L3VPN VRFs ( Layer 3 Virtual Private Networks )` bgpd supports for IPv4 RFC 4364 and IPv6 RFC 4659. L3VPN routes,and their associated VRF @@ -330,7 +330,7 @@ bgpd also supports inter-VRF route leaking. 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 for use in MPLS-based L3VPNs. Unicast routes may -- cgit v1.2.3 From 1638e748c0c1a908b28247aefe4e659653337641 Mon Sep 17 00:00:00 2001 From: fett0 Date: Mon, 8 Nov 2021 11:54:54 -0300 Subject: doc: L3vpn: settings --- docs/configuration/vrf/index.rst | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) (limited to 'docs/configuration/vrf/index.rst') diff --git a/docs/configuration/vrf/index.rst b/docs/configuration/vrf/index.rst index b4f63479..4ce51299 100644 --- a/docs/configuration/vrf/index.rst +++ b/docs/configuration/vrf/index.rst @@ -322,12 +322,13 @@ L3VPN VRFs ########## :abbr:`L3VPN VRFs ( Layer 3 Virtual Private Networks )` bgpd supports for -IPv4 RFC 4364 and IPv6 RFC 4659. L3VPN routes,and their associated VRF +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. +.. _l3vpn-vrf-route-leaking: VRF Route Leaking ================= @@ -351,6 +352,8 @@ VPN. Configuration for these exported routes must, at a minimum, specify these two parameters. + +.. _l3vpn-vrf example configuration: Configuration ============= @@ -363,7 +366,7 @@ address-family. rd vpn export Specifies the route distinguisher to be added to a route exported from the - current unicast VRF to VPN.Create new VRF instance with ``. The name + current unicast VRF to VPN. Create new VRF instance with ``. The name is used when placing individual interfaces into the VRF. .. cfgcmd:: set vrf name protocols bgp address-family @@ -383,19 +386,19 @@ address-family. unicast VRF to VPN. If the value specified is auto, the label value is automatically assigned from a pool maintained. -.. cfgcmd:: set vrf name protocols bgp address-family +.. cfgcmd:: set vrf name protocols bgp address-family route-map vpn [route-map ] Specifies an optional route-map to be applied to routes imported or exported between the current unicast VRF and VPN. -.. cfgcmd:: set vrf name protocols bgp address-family +.. cfgcmd:: set vrf name protocols bgp address-family vpn Enables import or export of routes between the current unicast VRF and VPN. -.. cfgcmd:: set vrf name protocols bgp address-family +.. cfgcmd:: set vrf name protocols bgp address-family import vrf Shortcut syntax for specifying automatic leaking from vrf VRFNAME to the @@ -403,6 +406,8 @@ address-family. derived and should not be specified explicitly for either the source or destination VRF’s. +.. _l3vpn-vrf example operation: + Operation ========= -- cgit v1.2.3 From 5d634a973dec4e0e346e44a578d5ece53a078625 Mon Sep 17 00:00:00 2001 From: fett0 Date: Mon, 8 Nov 2021 11:59:39 -0300 Subject: doc: L3vpn: settings --- docs/configuration/vrf/index.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/configuration/vrf/index.rst') diff --git a/docs/configuration/vrf/index.rst b/docs/configuration/vrf/index.rst index 4ce51299..e329d48e 100644 --- a/docs/configuration/vrf/index.rst +++ b/docs/configuration/vrf/index.rst @@ -245,8 +245,8 @@ Configuration Operation ^^^^^^^^^ -After committing the configuration we can verify all leaked routes are installed, -and try to ICMP ping PC1 from PC3. +After committing the configuration we can verify all leaked routes are +installed, and try to ICMP ping PC1 from PC3. .. code-block:: none @@ -352,7 +352,7 @@ VPN. Configuration for these exported routes must, at a minimum, specify these two parameters. - + .. _l3vpn-vrf example configuration: Configuration -- cgit v1.2.3