Re: Hiding internal network from MPLS WAN

From: Darby Weaver (ccie.weaver@gmail.com)
Date: Tue Feb 10 2009 - 19:05:19 ARST


Hmm...

The MPLS Cloud is designated by using an MPLS-VPN VRF for your company and
the 50 sites are using this identifier.

Now you want to tunnel all of your sites further?

A similar concept is DNPVPNs - but you have a scalability issue.

I suppose if you do not trust your provider or want to be bullet-proof.

I'm working on a similar project and the idea reared it's ugly head. I
suppose you don't trust the provider or require a higher level of security.

On Tue, Feb 10, 2009 at 3:44 PM, voice guru <guru.voice@gmail.com> wrote:

> Hi Experts,
>
> Well if we have 50 sites connected over MPLS cloud of Telco and have full
> mesh connectivity, we could redistribute our internal routing protocol into
> BGP of SP and have full mesh connectivity between the sites. But if we have
> to achieve fullmesh connectivity with out redistributing internal routing
> protocol into BGP or lets say we want to hide the internal IP domain from
> Telco/SP but still have fullmesh connectivity.
>
> I see it tunneling internal traffic over MPLS network by sharing just one
> ip
> subnet, but how about creating 50 tunnel interface on each router and think
> about 50 OSPF neighbors if we are running ospf internally, I am sure there
> will be more better options doing it such as NHRP etc..
>
> do some of you experts have done similar excercise then please do share, or
> provide your advises and Ideas.
>
> Thanks in advance,
> Guru
>
>
> 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



This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:10 ARST