From: Rado Vasilev (decklandv@gmail.com)
Date: Mon Jul 07 2008 - 18:17:09 ART
You can do it both ways - you can put your IP transit connection in a
separate VRF or in the global routing table.
My personal choice would be the global table, as if you had it in a
separate VRF and also had non-VPN customers (pure IP transit service for
example) you'll have to do VRF-to-global_table static routing - not
clean and buggy, depending on IOS.
So, if you go the other way, you can create an INTERNET VRF and provide
connectivity by importing/exporting route-targets between the customer
VRF and the INTERNET one.
Regards,
Rado
Olugbenga Adanlawo wrote:
> Dear Experts,
>
> I am working on an MPLS core design for an ISP out here in Africa. I have two
> types of customers that require internet access via the MPLS core.
>
> 1. MPLS VPN clients that connect via a 3800 CE router (PE - CE routing
> protocol is OSPF)
> 2. Broadband clients that terminate on a Cisco 7609 (with Cisco MWAM module
> configured as PDSN)
>
> Below is a schematic topology of the MPLS design
>
>
> Broadband _____________
> Client -------------> | PDSN (7609) | Global routing
> _________________________________________
> |____________|
> -------------------------------->|
> |
>
> |
> |
>
> |
> |
>
> | MPLS CLOUD | -------> INTERNET (VPN or GLOBAL)
> _____________
> | |
> MPLS | Cisco 3800 | VRF VPN_A |
> |
> Client -----------------> | CE Router |
> ---------------------------------->|_________________________________________
> |
> |____________|
>
>
> My Challenge however is how to configure the internet link whether in a VPN or
> global routing table to give access for both broadband and MPLS clients.
>
> Thank you for your advice
>
> Gbenga
>
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Mon Aug 04 2008 - 06:11:53 ART