JUNOSe 7.2.x Policy Management Configuration Guide
104 ! Bandwidth Management
One-Rate Rate-Limit Profile
A one-rate rate-limit profile can be configured for hard tail drop rate-limit or
TCP-friendly behavior. Packets can be categorized as committed, conformed, or
exceeded.
Example 1 You can configure a one-rate rate-limit profile to hard limit a packet flow to a
specified rate. To rate limit the traffic on an interface from source IP address 1.1.1.1
to 1 Mbps, issue the following commands:
host1#configure terminal
host1(config)#ip rate-limit-profile oneMegRlp one-rate
host1(config-rate-limit-profile)#committed-rate 1000000
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 oneMegRlp
host1(config-policy-list-classifier-group)#exit
host1(config-policy-list)#exit
host1(config)#interface atm 0/0.0
host1(config-subif)#ip policy input testPolicy statistics enabled
Example 2 You can also configure a one-rate rate-limit profile to provide a TCP-friendly rate
limiter. To configure a rate limiter with TCP-friendly characteristics, we recommend
that you set the committed burst to allow for 1 second of data at the specified rate,
and the excess 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
Two-Rate Rate-Limit Profile
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.
To Next Page
Loading...
Need help?
General
