Re: [j-nsp] MX series BGP config macros ?

[Jackson, William]

The parameter feature in IOS-XR is very nice, although there are other parts 
that aren’t so great.
I havent seen anything like this on Junos.

I must say I believe that this part of Junos has been abandoned somewhat and 
could do with some developer time.

On 05/11/2016, 21:24, "juniper-nsp on behalf of John Brown" 
 wrote:

Hi,

I'm trying to build a BGP policy config that will advertise routes based on 
how
a subscriber tags a route towards us.

If they send a route with community 65010:XXX  with XXX = an ASN
then we will not announce it towards that ASN.

In a small configuration this is pretty easy to do, but I'm looking at
trying to
see if there is a more elegant and scaleable solution.

With hundreds of peers on a router, it doesn't make sense to have a bunch of
community members for each ASN

It would be nice to have code that did


protocol bgp
group  eBGP-Some-Peer
peer-as 1234
export [Dont-Export]


policy-statement  Dont-Export
term
from
 protocol bgp
 community 65010:$PEERASN
then
 reject



Where $PEERASN gets expanded to 1234 because of the BGP session
it is associated with.

Then I can just apply Dont-Export to multiple peers and not have to 
customize
it for each one



Hopefully this explains it well enough.

Thank you
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp


___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] MX series BGP config macros ?

[John Brown]

Hi,

I'm trying to build a BGP policy config that will advertise routes based on how
a subscriber tags a route towards us.

If they send a route with community 65010:XXX  with XXX = an ASN
then we will not announce it towards that ASN.

In a small configuration this is pretty easy to do, but I'm looking at
trying to
see if there is a more elegant and scaleable solution.

With hundreds of peers on a router, it doesn't make sense to have a bunch of
community members for each ASN

It would be nice to have code that did


protocol bgp
group  eBGP-Some-Peer
peer-as 1234
export [Dont-Export]


policy-statement  Dont-Export
term
from
 protocol bgp
 community 65010:$PEERASN
then
 reject



Where $PEERASN gets expanded to 1234 because of the BGP session
it is associated with.

Then I can just apply Dont-Export to multiple peers and not have to customize
it for each one



Hopefully this explains it well enough.

Thank you
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] ACX for subscriber aggregation

[Eric Van Tol]

> > I use ACX5048
> >
> Fantastic, and good to hear from you again Aaron! Currently we're used to
> that sort of behaviour as our PPPoE LNS dumps /32 routes for each
> subscriber. But thanks for the heads up and mention of your usage!
> 

Will ACX5048 operating temperature limitation work in a cell tower (32F to 
104F)? They seem to be more aligned with installation inside a temperature 
controlled environment such as a general colo facility, no? Moreover, the power 
consumption on these is like 350W fully loaded, which is more than three times 
as much as a 24-port ASR920.

-evt
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp