If the import and export lists are identical, you can use the both keyword to
define the lists simultaneously:
host1:vr1(config-vrf)#route-target both 777:105
A route-target export list can be modified on the sending PE router by an export map
or outbound routing policy. It can be modified on the receiving PE router by an
import map or inbound routing policy.
route-target
■ Use to create—or add to—lists of VPN extended communities for a VRF that
determine whether a route is imported into a VRF.
■ An export list defines a route-target extended community; routes having any
route target in their export list that matches a route target in a VRF’s import list
are installed in the VRF’s forwarding table.
■ An import list defines a route-target extended community; only routes that have
at least one matching route target in their associated export list can be installed
into the VRF’s forwarding table.
■ If the import and export lists are identical, use the both keyword to define both
lists simultaneously.
■ You can add only one route target to a list at a time.
■ Example
host1:vr1(config-vrf)#route-target export 100:1
host1:vr1(config-vrf)#route-target import 100:1
■ Use the no version to remove a route target from the import list, the export list,
or both lists.
■ See route-target.
Example: Fully Meshed
VPNs
In a fully meshed VPN, each site in the VPN can reach every other site in the VPN.
Figure 89 on page 424 illustrates a situation with two fully meshed VPNs, VPN A and
VPN B. VPN A includes Customer Sites 1, 3, and 5 through VRFs A, C, and E. VPN B
includes Customer Sites 2, 4, and 6 through VRFs B, D, and F.
Configuring BGP VPN Services ■ 423
Chapter 5: Configuring BGP-MPLS Applications
To Next Page
Loading...