JunosE 11.3.x Policy Management Configuration Guide
Examples: Two-Rate Rate-Limit Profile
Examples: Rate-Limiting Individual or Aggregate Packet Flows
94
burst to allow 1.5 seconds of data at the specified committed rate plus the committed
burst. For example:
host1(config)#ip rate-limit-profile tcpFriendly8MB one-rate
host1(config-rate-limit-profile)#committed-rate 8000000
host1(config-rate-limit-profile)#committed-burst 1000000
host1(config-rate-limit-profile)#excess-burst 2500000
host1(config-rate-limit-profile)#committed-action transmit
host1(config-rate-limit-profile)#exceeded-action drop
You can configure a two-rate rate-limit profile for two different rates, committed and
peak, that are used to define a two-rate, three-color marking mechanism. You can
categorize packets as committed, conformed, or exceeded:
Up to the committed rate, packets are considered to be committed.
From the committed to peak rate, packets are considered to be conformed.
After the peak rate, packets are considered to be exceeded.
This configuration is implemented with token buckets. See RFC 2698 for more details.
The following example rate limits traffic on an interface from source IP address 1.1.1.1 so
that traffic at a rate up to 1 Mbps is colored green and transmitted, traffic at a rate from
1 Mbps to 2 Mbps is colored yellow and transmitted, and traffic at a rate above 2 Mbps
is dropped.
host1(config)#ip rate-limit-profile 1MbRLP
host1(config-rate-limit-profile)#committed-rate 1000000
host1(config-rate-limit-profile)#peak-rate 2000000
host1(config-rate-limit-profile)# committed-action transmit
host1(config-rate-limit-profile)#conformed-action transmit
host1(config-rate-limit-profile)#exceeded-action drop
host1(config-rate-limit-profile)#exit
host1(config)#ip classifier-list claclA ip host 1.1.1.1 any
host1(config)#ip policy-list testPolicy
host1(config-policy-list)#classifier-group claclA
host1(config-policy-list-classifier-group)#rate-limit-profile 1MbRLP
host1(config-policy-list-classifier-group)# exit
host1(config-policy-list)#exit
host1(config-policy-list)#interface atm 0/0.0
host1(config-subif)#ip policy input testPolicy statistics enabled
You can construct policies to provide rate limiting for individual packet flows or for the
aggregate of multiple packet flows. For example, if you have traffic from multiple sources,
you can either rate limit each traffic flow individually, or you can rate limit the aggregate
flow for the traffic from all sources.
To rate limit individual packet flows, use a separate classifier list to classify each flow.
To rate limit the aggregate of multiple traffic flows, use a single classifier list for the
multiple entries.
Copyright © 2010, Juniper Networks, Inc.
Need help?
Do you have a question about the JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 and is the answer not in the manual?
Questions and answers