Distribution Of Vpn Routing Information - Cisco Catalyst 3750 Software Configuration Manual

Chapter 30 Configuring MPLS and EoMPLS
Figure 30-2 Customer Sites with VPNs

Distribution of VPN Routing Information

The distribution of VPN routing information is controlled through the use of VPN route target
communities, implemented by BGP extended communities. VPN routing information is distributed in
this manner:
•
•
A PE router can learn an IP prefix from a CE device by static configuration, through a BGP session with
the CE device, or through the routing information protocol (RIP) exchange with the CE router. The IP
prefix is a member of the IPv4 address family. After it learns the IP prefix, the PE converts it into a
VPN-IPv4 prefix by combining it with an 8-byte route distinguisher (RD). The generated prefix is a
member of the VPN-IPv4 address family and uniquely identifies the customer address, even if the
customer site is using globally nonunique (unregistered private) IP addresses.
BGP distributes reachability information for VPN-IPv4 prefixes for each VPN. BGP communication
takes place at two levels: within IP domains, known as autonomous systems (internal BGP or IBGP), and
between autonomous systems (external BGP or EBGP). PE-to-PE sessions are IBGP sessions, and
PE-CE sessions are EBGP sessions.
BGP propagates reachability information for VPN-IPv4 prefixes among PE routers by using the BGP
multiprotocol extensions, which define support for address families other than IPv4. It does this in a way
that ensures that the routes for a given VPN are learned only by other members of that VPN, which
enables members of the VPN to communicate with each other.
78-15870-01
VPN1
Site 2
When a VPN route learned from a CE device is added to the BGP process, a list of VPN route target
extended community attributes is associated with it. The attribute values are obtained from an export
list of route targets associated with the VRF from which the route was learned.
An import list of route target extended communities is also associated with each VRF. The import
list defines route target extended community attributes that a route must have in order for the route
to be imported into the VRF. For example, if the import list for a particular VRF includes route target
communities A, B, and C, then any VPN route that carries any of those route target extended
communities—A, B, or C—is imported into the VRF.
VPN2
Site 4
Site 3
Catalyst 3750 Metro Switch Software Configuration Guide
Understanding MPLS VPNs
VPN3
Site 1
Site 5
30-5