Re: Connected Interface

Hello Andy,

it should work solely with the import/export of route-targets. No
leaking routes are necessary. Just take care that you redistribute
from/to mBPG in the same way as if the two VRFs would be on different
PE-Routers. You are right that the next-hop in the other VRF is shown
when you do the 'show ip route vrf ...' command. And right after the
next-hop IP Address the VRF used to reach this next-hop should be
shown in parantheses.

Could you show the relevant parts of the configs, if it does not work
in your setup?

hth,

reinhold

2009/12/25 andy thomas <thomasandy32_at_gmail.com>:
> Hello,
>
> A---------PE-1--------P----------PE-2
> |
> |
> B
>
> Am connecting to different customers on same PE and they want to communicate
> with each other,after importing route-target the next-hop for customer-A
> routes from Customer-B, is the interface associated with customer-A VRF on
> the PE router,Customer-B is not able to ping the interface of
> customer-A,Because here they are not receiving a MBGP update the next-hop is
> the connected interface of another VRF. To make them reacheable what i have
> do????
>
> Solution:
>
> Pointing static VRF routes to global routing table of PE-2 and in global
> routing table of PE-1 pointing global static route to a particular VRF
> interface and redistribute the global static routes in dynamic routing
> protocol then only PE-2 will come to know where the routes are located for
> customer-A.By doiing this the traffice flow for connected customer is
> through PE-2
>
> Any alternate solution guys
>
> Thanks

Blogs and organic groups at http://www.ccie.net
Received on Sat Dec 26 2009 - 11:06:07 ART