[j-nsp] Community based prepends.

[Phil Rosenthal]

I want to have the capability to have my customers be able to prepend 
to peers individually.
Like,
65001:(peeras) = prepend once to (peeras)
65002:(peeras) = prepend twice to (peeras)
65003:(peeras) = prepend three times to (peeras)


On Dec 12, 2003, at 5:49 PM, Pedro Roque Marques wrote:

> pr at isprime.com (Phil Rosenthal) writes:
>
>> Hello.
>>
>> As this topic has been raised in the autonomous-system thread, We are
>> planning on implementing community-based prepends for bgp customers,
>> which given the featureset available today, I think requires different
>> export policies for every peer.
>
> Wouldn't a common export policy do the trick ?
>
> community prepend-my-1 10458:1;
> community prepend-my-2 10458:2;
> community prepend-customer-1 10458:3;
> community prepend-customer-2 10458:4;
>
> policy-statement common-export {
>     term a {
> 	from community prepend-my-1;
> 	then as-path-prepend "10458";
>     }
>     term b {
> 	from community prepend-my-2;
> 	then as-path-prepend "10458 10458";
>     }
>     term c {
> 	from community prepend-customer-1;
> 	then as-path-expand last-as;
>     }
>
>     term d {
> 	from community prepend-customer-2;
> 	then as-path-expand last-as count 2;
>     }
>     [...]
> }
>
> Or do you have different requirements ?
>
>   Pedro.
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> http://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
--Phil Rosenthal
ISPrime, Inc.