[j-nsp] juniper-nsp Digest, Vol 47, Issue 12
Dimitrios Kalogeras
D.Kalogeras at noc.ntua.gr
Wed Oct 11 13:23:52 EDT 2006
juniper-nsp-request at puck.nether.net wrote:
> Send juniper-nsp mailing list submissions to
> juniper-nsp at puck.nether.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> or, via email, send a message with subject or body 'help' to
> juniper-nsp-request at puck.nether.net
>
> You can reach the person managing the list at
> juniper-nsp-owner at puck.nether.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of juniper-nsp digest..."
>
>
> Today's Topics:
>
> 1. Re: Policer based on community (Leigh Porter)
> 2. Re: Policer based on community (Andrew Ramsey)
> 3. Re: Policer based on community (Leigh Porter)
> 4. Re: Policer based on community (Tommy J)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 11 Oct 2006 09:23:33 +0000
> From: Leigh Porter <leigh.porter at ukbroadband.com>
> Subject: Re: [j-nsp] Policer based on community
> To: Jared Gull <jmgull at yahoo.com>
> Cc: juniper-nsp at puck.nether.net
> Message-ID: <452CB815.8060009 at ukbroadband.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> Cisco have a thing called QoS policy distribution through BGP" but it
> sucks, will not do this and I have never met anybody who has ever used it.
>
Hi to all of you,
QoS policy distribution through BGP ( aka QPPB) is a useful feature. We
use it in Grnet the academic NREN of GREECE. Our campus networks may
signal the policing functionality in their access lines using this features.
Cheers,
Dimitrios
> If this is a small scale thing (i.e. you do not offer this as a service)
> and the peers in question are few then you could build LSPs between the
> peering router and this customer's border router (in your AS) and shape
> the traffic on that tunnel (never tried shaping traffic on a LSP)
>
> --
> Leigh
>
>
> Jared Gull wrote:
>> Tommy,
>>
>> This is not possible based on bgp community. You will
>> likely need to base this on s/d address.
>>
>> Jared
>> --- Tommy J <sunman_1970 at yahoo.com> wrote:
>>
>>
>>> Can we police the traffic (rate limiting) based on
>>> bgp
>>> community ? I am trying to cap a customer whose
>>> access
>>> to certain peers is reduced to X amount of
>>> bandwidth.
>>>
>>> ~Tom
>>>
>>> __________________________________________________
>>> Do You Yahoo!?
>>> Tired of spam? Yahoo! Mail has the best spam
>>> protection around
>>> http://mail.yahoo.com
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>>>
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam? Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 11 Oct 2006 04:29:29 -0700
> From: "Andrew Ramsey" <akramsey at juniper.net>
> Subject: Re: [j-nsp] Policer based on community
> To: <sunman_1970 at yahoo.com>, <juniper-nsp at puck.nether.net>
> Message-ID: <B980436B0168A84081FDFC2EBF0C4D8F09509B88 at quark.jnpr.net>
> Content-Type: text/plain; charset="us-ascii"
>
> You can do this with destination classes. Please see config below:
>
> policer police_one {
>
> if-exceeding {
>
> bandwidth-limit 1m;
>
> burst-size-limit 4500;
>
> }
>
> then discard;
>
> }
>
> policer police_two {
>
> if-exceeding {
>
> bandwidth-limit 2m;
>
> burst-size-limit 5500;
>
> }
>
> }
>
>
>
> filter police {
>
> term one {
>
> from {
>
> destination-class one;
>
> }
>
> then {
>
> policer police_one;
>
> accept;
>
> }
>
> }
>
> term two {
>
> from {
>
> destination-class two;
>
> }
>
> then {
>
> policer police_2;
>
> accept;
>
> }
>
> }
>
> term three {
>
> then accept;
>
> }
>
> }
>
>
>
> t1-0/3/0 {
>
> unit 0 {
>
> family inet {
>
> filter {
>
> output police;
>
> }
>
> address 10.42.114.2/30;
>
> }
>
> }
>
> }
>
>
>
> policy-statement police_destinations {
>
> term one {
>
> from community 100;
>
> then destination-class one;
>
> }
>
> term two {
>
> from community 200;
>
> then destination-class two;
>
> }
>
> }
>
>
>
> routing-options {
> forwarding-table {
> export police_destinations;
> }
> }
>
>> -----Original Message-----
>> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
>> bounces at puck.nether.net] On Behalf Of Tommy J
>> Sent: Tuesday, October 10, 2006 6:26 PM
>> To: juniper-nsp at puck.nether.net
>> Subject: [j-nsp] Policer based on community
>>
>> Can we police the traffic (rate limiting) based on bgp
>> community ? I am trying to cap a customer whose access
>> to certain peers is reduced to X amount of bandwidth.
>>
>> ~Tom
>>
>> __________________________________________________
>> Do You Yahoo!?
>> Tired of spam? Yahoo! Mail has the best spam protection around
>> http://mail.yahoo.com
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
>
> ------------------------------
>
> Message: 3
> Date: Wed, 11 Oct 2006 12:19:52 +0000
> From: Leigh Porter <leigh.porter at ukbroadband.com>
> Subject: Re: [j-nsp] Policer based on community
> To: Andrew Ramsey <akramsey at juniper.net>
> Cc: juniper-nsp at puck.nether.net
> Message-ID: <452CE168.6040101 at ukbroadband.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
>
> Bloody clever them Junipers.
>
> Andrew Ramsey wrote:
>> You can do this with destination classes. Please see config below:
>>
>> policer police_one {
>>
>> if-exceeding {
>>
>> bandwidth-limit 1m;
>>
>> burst-size-limit 4500;
>>
>> }
>>
>> then discard;
>>
>> }
>>
>> policer police_two {
>>
>> if-exceeding {
>>
>> bandwidth-limit 2m;
>>
>> burst-size-limit 5500;
>>
>> }
>>
>> }
>>
>>
>>
>> filter police {
>>
>> term one {
>>
>> from {
>>
>> destination-class one;
>>
>> }
>>
>> then {
>>
>> policer police_one;
>>
>> accept;
>>
>> }
>>
>> }
>>
>> term two {
>>
>> from {
>>
>> destination-class two;
>>
>> }
>>
>> then {
>>
>> policer police_2;
>>
>> accept;
>>
>> }
>>
>> }
>>
>> term three {
>>
>> then accept;
>>
>> }
>>
>> }
>>
>>
>>
>> t1-0/3/0 {
>>
>> unit 0 {
>>
>> family inet {
>>
>> filter {
>>
>> output police;
>>
>> }
>>
>> address 10.42.114.2/30;
>>
>> }
>>
>> }
>>
>> }
>>
>>
>>
>> policy-statement police_destinations {
>>
>> term one {
>>
>> from community 100;
>>
>> then destination-class one;
>>
>> }
>>
>> term two {
>>
>> from community 200;
>>
>> then destination-class two;
>>
>> }
>>
>> }
>>
>>
>>
>> routing-options {
>> forwarding-table {
>> export police_destinations;
>> }
>> }
>>
>>
>>> -----Original Message-----
>>> From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-
>>> bounces at puck.nether.net] On Behalf Of Tommy J
>>> Sent: Tuesday, October 10, 2006 6:26 PM
>>> To: juniper-nsp at puck.nether.net
>>> Subject: [j-nsp] Policer based on community
>>>
>>> Can we police the traffic (rate limiting) based on bgp
>>> community ? I am trying to cap a customer whose access
>>> to certain peers is reduced to X amount of bandwidth.
>>>
>>> ~Tom
>>>
>>> __________________________________________________
>>> Do You Yahoo!?
>>> Tired of spam? Yahoo! Mail has the best spam protection around
>>> http://mail.yahoo.com
>>> _______________________________________________
>>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>> _______________________________________________
>> juniper-nsp mailing list juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>
> ------------------------------
>
> Message: 4
> Date: Wed, 11 Oct 2006 08:45:51 -0700 (PDT)
> From: Tommy J <sunman_1970 at yahoo.com>
> Subject: Re: [j-nsp] Policer based on community
> To: Andrew Ramsey <akramsey at juniper.net>
> Cc: juniper-nsp at puck.nether.net
> Message-ID: <20061011154551.62175.qmail at web31215.mail.mud.yahoo.com>
> Content-Type: text/plain; charset=iso-8859-1
>
> Awesome Man
>
> This is soooo cool.
>
> Tommy
>
> --- Leigh Porter <leigh.porter at ukbroadband.com> wrote:
>
>> Bloody clever them Junipers.
>>
>> Andrew Ramsey wrote:
>>> You can do this with destination classes. Please
>> see config below:
>>> policer police_one {
>>>
>>> if-exceeding {
>>>
>>> bandwidth-limit 1m;
>>>
>>> burst-size-limit 4500;
>>>
>>> }
>>>
>>> then discard;
>>>
>>> }
>>>
>>> policer police_two {
>>>
>>> if-exceeding {
>>>
>>> bandwidth-limit 2m;
>>>
>>> burst-size-limit 5500;
>>>
>>> }
>>>
>>> }
>>>
>>>
>>>
>>> filter police {
>>>
>>> term one {
>>>
>>> from {
>>>
>>> destination-class one;
>>>
>>> }
>>>
>>> then {
>>>
>>> policer police_one;
>>>
>>> accept;
>>>
>>> }
>>>
>>> }
>>>
>>> term two {
>>>
>>> from {
>>>
>>> destination-class two;
>>>
>>> }
>>>
>>> then {
>>>
>>> policer police_2;
>>>
>>> accept;
>>>
>>> }
>>>
>>> }
>>>
>>> term three {
>>>
>>> then accept;
>>>
>>> }
>>>
>>> }
>>>
>>>
>>>
>>> t1-0/3/0 {
>>>
>>> unit 0 {
>>>
>>> family inet {
>>>
>>> filter {
>>>
>>> output police;
>>>
>>> }
>>>
>>> address 10.42.114.2/30;
>>>
>>> }
>>>
>>> }
>>>
>>> }
>>>
>>>
>>>
>>> policy-statement police_destinations {
>>>
>>> term one {
>>>
>>> from community 100;
>>>
>>> then destination-class one;
>>>
>>> }
>>>
>>> term two {
>>>
>>> from community 200;
>>>
>>> then destination-class two;
>>>
>>> }
>>>
>>> }
>>>
>>>
>>>
>>> routing-options {
>>> forwarding-table {
>>> export police_destinations;
>>> }
>>> }
>>>
>>>
>>>> -----Original Message-----
>>>> From: juniper-nsp-bounces at puck.nether.net
>> [mailto:juniper-nsp-
>>>> bounces at puck.nether.net] On Behalf Of Tommy J
>>>> Sent: Tuesday, October 10, 2006 6:26 PM
>>>> To: juniper-nsp at puck.nether.net
>>>> Subject: [j-nsp] Policer based on community
>>>>
>>>> Can we police the traffic (rate limiting) based
>> on bgp
>>>> community ? I am trying to cap a customer whose
>> access
>>>> to certain peers is reduced to X amount of
>> bandwidth.
>>>> ~Tom
>>>>
>>>>
>> __________________________________________________
>>>> Do You Yahoo!?
>>>> Tired of spam? Yahoo! Mail has the best spam
>> protection around
>>>> http://mail.yahoo.com
>>>> _______________________________________________
>>>> juniper-nsp mailing list
>> juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>>
>>> _______________________________________________
>>> juniper-nsp mailing list
>> juniper-nsp at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/juniper-nsp
>>>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
> ------------------------------
>
> _______________________________________________
> juniper-nsp mailing list
> juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
> End of juniper-nsp Digest, Vol 47, Issue 12
> *******************************************
--
--
Dimitrios K. Kalogeras
Electrical Engineer Ph.D.
Network Manager
NTUA/GR-Net Network Management Center
_____________________________________
icq: 11887484
voice: +30-210-772 1863
fax: +30-210-772 1866
e-mail: D.Kalogeras at noc.ntua.gr
pub 1024D/71A87DFA 2006-04-27 [expires: 2006-07-26] Dimitrios
Kalogeras <D.Kalogeras at noc.ntua.gr>
Key fingerprint = CCB7 77A1 0645 A3A3 30EA 381B D594 4322 71A8 7DFA
More information about the juniper-nsp
mailing list