Re: [mpls-linux-devel] Moving forward

[Scott A. Y. <sy...@im...>]

Oops I didn't mean to hit send on that yet.

I've been looking at common MPLS VPN configurations and for the most part they look like:

ip vrf red
 rd 1:1
 route-target export 1:1
 route-target import 1:1
!
interface Ethernet1
 ip vrf forwarding red
 ip address 10.10.4.1 255.255.255.0
!
router bgp 65535
 neighbor 10.200.254.2 remote-as 1
!
address-family vpnv4
 neighbor 10.200.254.2 activate
 neighbor 10.200.254.2 send-community both
!

>From my reading on the way that other router company does it, it's the VRF that creates the vpnv4 prefixes.
Routes in the VRF will become vpnv4 routes subject to route filtering on the vrf with
the VRF's designated route distinguisher and route target attributes. It looks like there can be multiple route
targets added to the vpnv4 prefix.

On the BGP receive side vpnv4 prefixes received use the route-target import to determine which VRFs the route is installed
into (after stripping off the RD).

Since the existing vpnv4 code was written to support route reflector mode it ignores the route target attributes. We'd have
to be sure to support route reflector mode properly.

Do I have most of the basics correct?

Thanks,
Scott Yoder
Support Engineer
ImageStream Internet Solutions, Inc.
E-mail: sy...@im...