route leaking from global to vrf when there is no VRF

From: Carlos Trujillo (carlos.trujillo.jimenez@gmail.com)
Date: Tue Nov 11 2008 - 17:05:10 ARST

HI group.

Im having a simple MPLS VPN scenario between PE4s:

[CE]-----[PE1]----[P]-----[PE(BORDER)]------[ISP1]

I give a brief description about the topology shown:

There is an MP-IBGP peering between PE1 and PE(BORDER).
PE1 has its CE interface associated to CLIENT VRF, and PE(BORDER) has
all of its interfaces associated to the global routing table.
PE(BORDER) also has the VRF created but none interface attached to the
vrf, so It can see the routes sourced from CE.

What I want is to give CE routing connectivity to ISP1 (internet), so
the data path a packet takes when it leaves CE router it
follows PE1, then it travels in the MPLS VPN to PE(BORDER) and then I
leak that route from the VPN to the global table using static
routes, and then the packet succesfully enters the ISP router, so at
this point its working OK.

For the return packet I cant make the packet who comes from an
interface of the global table to enter the VRF TABLE (vpn) and travels
via the VPN to PE1.

I saw two examples found in cisco.com showing how to leak from VRF TO
global and from global to VRF, and in both cases it uses static routes
pointing
to an outbound interface and a next hop, but my scenario is different
to them in that PE(BORDER) router has all of its interfaces attached
to the global
routing table, and If I create a static route, to what outbound
interface do I point to? if all of its interfaces belong to the global
routing table.

Please If any have an idea how to let it work?

Thanks.
# 21813 R&S

Blogs and organic groups at http://www.ccie.net

This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:30 ARST