Re: MPLS L3 VPN Questions

From: Elliott Reyes <fontananetworkengineer_at_gmail.com>
Date: Fri, 3 Jun 2011 11:09:50 -0700

Thanks Marko,

This is great and yes I realize this topic has been beaten up to death :)

On Fri, Jun 3, 2011 at 11:00 AM, Marko Milivojevic <markom_at_ipexpert.com>wrote:

> It may be helpful for you to watch a free 2-hour video on MPLS VPNs I
> did last year. It's called MPLS 101 and it should cover all the
> questions you had very nicely. You can find it here:
> http://bit.ly/vLecture
>
> --
> Marko Milivojevic - CCIE #18427
> Senior Technical Instructor - IPexpert
>
> FREE CCIE training: http://bit.ly/vLecture
>
> Mailto: markom_at_ipexpert.com
> Telephone: +1.810.326.1444
> Web: http://www.ipexpert.com/
>
> On Fri, Jun 3, 2011 at 10:01, Elliott Reyes
> <fontananetworkengineer_at_gmail.com> wrote:
> > Hey Guys,
> >
> > I'm just trying to get a better understanding of how to build these
> > MPLS VPN's properly and I guess the documentation and INE workbook just
> > confuses me a little bit. So if anyone can assist me that would be great.
> >
> >
> > Like Denzel in the movie Philadelphia. Explain it to me like I'm a 6 year
> > old.
> >
> > 1. When defining the VRF's between two PE routers.
> >
> >
> > Example
> >
> > R1
> >
> > Step 1 - Create VRF locally on R1
> >
> > ip vrf VPN_A
> >
> > rd 100:1 <---- ROUTE DISTINGUISHER (This is locally significant to R1
> and
> > add's a 8 byte value to IPV4 prefix to create a VPNIPV4 prefix. )
> >
> >
> > Step 2 - Assign Route-Target command
> > route-target both 100:1 <----- allows routing information from to
> traverse
> > from R1 VPN_A to R2 VPN_A thru their connected interfaces and
> import/export
> > routing information.
> >
> > R1 <----------> R2
> >
> > int fa0/1 (R1)
> > ip vrf forwarding VPN_A
> > ip add 10.1.1.1 255.255.255.0
> >
> >
> > R2
> >
> > Step 1 - Create VRF locally on R2
> >
> > ip vrf VPN_A
> >
> > rd 100:1 <---- ROUTE DISTINGUISHER (This is locally significant to R2
> and
> > add's a 8 byte value to IPV4 prefix to create a VPNIPV4 prefix. )
> >
> >
> > Step 2 - Assign Route-Target command
> > route-target both 100:1 <----- allows routing information from to
> traverse
> > from R2 VPN_A to R1 VPN_A thru their connected interfaces and
> import/export
> > routing information.
> >
> > Question - Does the route-target have to match the route distinguisher on
> > both ends. if the route-target is say 100:2 and the route distinguisher
> is
> > 100:1 on VPN_A this technically shouldn't work
> > across the VPN correct.
> >
> > R2 <----------> R1
> >
> > int fa0/1 (R2)
> > ip vrf forwarding VPN_A
> > ip add 10.1.1.2 255.255.255.0
> >
> >
> > thanks
> >
> >
> > Blogs and organic groups at http://www.ccie.net
> >
> > _______________________________________________________________________
> > Subscription information may be found at:
> > http://www.groupstudy.com/list/CCIELab.html

Blogs and organic groups at http://www.ccie.net
Received on Fri Jun 03 2011 - 11:09:50 ART

This archive was generated by hypermail 2.2.0 : Fri Jul 01 2011 - 06:24:27 ART