[j-nsp] Dynamic route leaking between global routing table and vrf routing table

[Mark Meijerink]

Sean,

I tried using instance-import but when I tried to commit the configuration it failed because I could not import from the VRF instance. The instance
type we use is VRF. This might have something to do with it. Do you have a configuration example for me so I can give it a try?

Regards,
 Mark

Sean Clarke wrote:
> You might find using "instance-import" and "instance-export" much easier
> to use than RIB-groups.
> 
> With a simple policy you can import/export routes from and to the inet.0
> table, and use the same command within the routing instances to pull
> routes from inet.0 into the VRF.
> 
> This works fine with community.
> 
> cheers
> Sean
> 
> 
> 
> On 4/3/09 2:47 PM, Mark Meijerink wrote:
>> Hi there,
>>
>> I have been working on dynamic leaking of routes between the global routing table and the vrf routing table based on communities. But I have failed to
>> make it work. I have already seen multiple examples but those did not work for me. I will give s short description of what we are trying to achieve
>> and I hope you can point me in the right direction.
>>
>> In the global routing table we have our peerings with AMS-IX peers and iBGP peerings with two core routers. The AMS-IX routes are given a certain
>> community. We want to create a vrf with customers which only have AMS-IX connectivity. So we want to dynamically leak routes into the vrf based on the
>> community. In the vrf we have BGP sessions with the customers and the routes we learn from them are tagged with a certain community as well. These
>> routes must be dynamically leaked into the global routing table. We are looking for a way to dynamically leak routes in two directions.
>>
>> I have tried using rib-groups and tried to make it work using the vrf-import and vrf-export policies. Could you please let me know how I can make the
>> setup as explained above work. The difficulty we are introducing is that we want to leak dynamically and not static. Thanks in advance for your reply
>> and advice.
>>
>> Regards,
>>  Mark Meijerink
>>  SARA
>>
>>   
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 258 bytes
Desc: OpenPGP digital signature
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20090406/8264be82/attachment.bin>