[c-nsp] Extending MPLS over external providers cloud

[Stig Johansen]

You should look into running several DMVPN's (using a FVRF and IVRF, as it's called), one for each VRF you want to provide at the remote sites. If you have a total of 5 VRF's, you'll have a headend with 5 different DMVPN's in 5 different VRF's and all is done with dynamic routing and setup. 

The CE's should run Multi-VRF's.

Best regards,
Stig Meireles Johansen

-----Opprinnelig melding-----
Fra: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] På vegne av lists at daniels.id.au
Sendt: 6. august 2008 05:14
Til: David Curran
Kopi: lists at daniels.id.au; cisco-nsp at puck.nether.net
Emne: Re: [c-nsp] Extending MPLS over external providers cloud

Hi David,

On Tue, 05 Aug 2008 09:23:07 -0400, David Curran <dcurran at nuvox.com> wrote:
> Is there an actual requirement to run LDP/MPLS over these tunnels or are
> you
> simply looking to extend a VRF?  If its the latter, Multi-VRF CE (or
> VRF-Lite, whatever) works very well.

The requirement is simply to provide multiple VRF's (3 to 5) at any remote
site, the vrf's will vary site-to-site based on local requirements.
In an ethernet scenario, I agree VRF-Lite, dot1q and away we go, but here I
have a cloud in the middle connecting several (20-30) DSL sites to a head
office (hub and spoke), and the thought of having to manage multiple
tunnels (one per vrf), per site is making me cringe..

Or am I missing something, is there some other way to more easily manage
these multiple tunnels?

Thanks,
Aaron


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/