[j-nsp] Policer based on community

[Andrew Ramsey]

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