Re: Internet Access

From: ALL From_NJ <all.from.nj_at_gmail.com>
Date: Mon, 16 Nov 2009 20:36:26 -0500

Sorry for all the emails ... some good links to help and some of these clear
up / fix what I wrote below.

This one discusses how to forward an OSPF default route:
http://www.shafagh.net/2009/11/internet-through-mpls-default-route.html

I have typically used this one in my lab, and is what I am more familiar
with:
http://www.cisco.com/en/US/tech/tk436/tk428/technologies_configuration_example09186a00801445fb.shtml

Some variations of these apply ... however, I have labbed this and either
link will work for providing internet access to the CEs.

Keegan - the first link above is pretty good for forwarding the routes and
shows some examples too.

Some cool learning, thanks Andy for the question.

Andrew Lissitz

On Mon, Nov 16, 2009 at 7:41 PM, ALL From_NJ <all.from.nj_at_gmail.com> wrote:

> Hey team,
>
> Was thinking more about this ... and while my set up will work for a lab
> and lab testing ... it may not be as real life as it should be. It is fun
> to tshoot a silly design, but I think a little more color should be added to
> this posting.
>
> Here is what I mean, each customer has their own routing and internet
> access point.
>
> Keegan in the example I gave, you can create a default route via bgp from
> the PE. This gets propagated ok and works. In the real world the provider
> is not going to generate this via the PE, although in our labs this can make
> for some easier testing.
>
> From the customer's perspective, they do not 'see' MPLS or any of the L3
> VPN stuff ... they only see routing and route tables. A customer likely has
> two links at the core / head-end office:
>
> 1st link - FW and NAT to the internet
> 2nd link - Into the MPLS cloud for site to site connectivity
>
> I am making the assumption that most large MPLS providers have a separate
> network for private site to site MPLS networks and another for internet
> access and single sites. Both of these can run MPLS, however the routing
> will obviously be different internally to the SP and externally from a
> global perspective.
>
> What I will lab up tonight:
>
> 2 CE routers, one pretending to the head-end / core router, and another CE
> router pretending to be the spoke / edge.
>
> On the head end / core CE, I will have two uplinks. One going into my
> global network after being NAT'ed, and FW. The other link going into the
> MPLS 'cloud' and generating a default route via OSPF for the remote site.
>
> This is a bit more realistic. Any thoughts team? HTH,
>
> Andrew Lee Lissitz
>
>
>
> On Mon, Nov 16, 2009 at 4:54 PM, <Keegan.Holley_at_sungard.com> wrote:
>
>> Sorry I'm more used to juniper, but what does the route look like in the
>> bgp table for that vrf?
>>
>>
>>
>> From:
>> andy thomas <thomasandy32_at_gmail.com>
>> To:
>> Cisco certification <ccielab_at_groupstudy.com>
>> Date:
>> 11/16/2009 07:24 AM
>> Subject:
>> Internet Access
>> Sent by:
>> <nobody_at_groupstudy.com>
>>
>>
>>
>> Hey Experts,
>>
>>
>>
>> A------B--------C-------------Customer D (MPLS VPN)
>> |
>> |
>> E---------------(Customer F remote site)
>>
>> B is the internet gateway originating a default route via
>> OSPF(default-information originate) pointing a static default route to A
>> which is providing a internet access to router B ,C,and E. I want to
>> provide
>> a internet access to customer VRF D and am pointing to global route table
>> for the route of B interface,Everything is working fine customer D is able
>> to go on internet.
>>
>> Customer D & F is exchanging same RT and they are able to exchange private
>> routes amoung themselves but when the default static route for the
>> internet is redistributed in VRF on router C it is not advertised to
>> Router
>> E for customer F,why??? any specific reason.???? Added a defualt static
>> route on E same what i did on C pointing to global route table of
>> Interface
>> B to let customer F go on the internet.
>>
>> Configs:
>>
>> Router C:
>>
>> ip route vrf customer D 0.0.0.0 0.0.0.0 (router B Interface) global
>>
>> address-family ipv4 vrf cutomer D
>> redistribute connected
>> redistribute static
>> no synchronization
>> exit-address-family
>>
>>
>> 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
>>
>> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>>
>>
>>
>>
>>
>>
>>
>>
>
>
> --
> Andrew Lee Lissitz
> all.from.nj_at_gmail.com
>

-- 
Andrew Lee Lissitz
all.from.nj_at_gmail.com
Blogs and organic groups at http://www.ccie.net
Received on Mon Nov 16 2009 - 20:36:26 ART

This archive was generated by hypermail 2.2.0 : Tue Dec 01 2009 - 06:36:29 ART