Example: Multiple Flows Sharing Preferred Bandwidth Rate-Limiting Hierarchical Policy; Figure 2: Multiple Flows Sharing Preferred Bandwidth - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual

Software for e series broadband services routers policy management configuration guide
Hide thumbs Also See for JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04:
Table of Contents

Advertisement

Example: Multiple Flows Sharing Preferred Bandwidth Rate-Limiting Hierarchical Policy

Copyright © 2010, Juniper Networks, Inc.
Figure 2 on page 63 shows an interface with an attached policy that has a Video classifier
that singles out a substream of the packets flowing on that interface. The Video classifier
can be allocated 6 Mbps out of the 10 Mbps interface rate. All other packets on the
interface are Internet. The common rate limit cannot drop Video packets, but must limit
the total flow (Video and Internet) to under 10 Mbps. Internet traffic can use the Video
bandwidth when there are no active Video calls, while avoiding hard partitioning of
interface bandwidth.
NOTE: To avoid rate-limit saturation, we recommend that you set the rate
limit profile to color-aware when the rate limit is set to receive transmit
conditional.

Figure 2: Multiple Flows Sharing Preferred Bandwidth

host1(config)#rate-limit-profile video two-rate hierarchical
host1(config-rate-limit-profile)#committed-action transmit unconditional
host1(config-rate-limit-profile)#conformed-action transmit unconditional
host1(config-rate-limit-profile)#exceeded-action drop
host1(config-rate-limit-profile)#peak-rate 60000000
host1(config-rate-limit-profile)#exit
host1(config)#rate-limit-profile common two-rate hierarchical
host1(config-rate-limit-profile)# color-aware
host1(config-rate-limit-profile)#committed-action transmit conditional
host1(config-rate-limit-profile)#conformed-action transmit conditional
host1(config-rate-limit-profile)#exceeded-action drop
host1(config-rate-limit-profile)#peak-rate 100000000
host1(config-rate-limit-profile)#exit
host1(config)#policy-list mycompany
host1(config-policy-list)#classifier-group video parent-group all
host1(config-policy-list-classifier-group)#rate-limit-profile video
host1(config-policy-list-classifier-group)#exit
host1(config-policy-list)#classifier-group * parent-group all
host1(config-policy-list-classifier-group)#forward
host1(config-policy-list-classifier-group)#exit
host1(config-policy-list)#parent-group all
host1(config-policy-list-parent-group)#rate-limit-profile common
host1(config-policy-list-parent-group)#exit
In this example, the rate limit Common is color-aware, using the color of the incoming
packets instead of setting them to Green. This causes the rate limit Preferred to send 6
Mbps of yellow, transmit unconditional packets. The rate limit Common counts the
packets against the yellow token bucket, which has a rate of 10 Mbps. However, if the
rate limit Common is color-blind, it treats all packets as Green so the green token bucket
gets 6 Mbps of transmit unconditional traffic, which eventually causes all packets to be
saturated and dropped.
Chapter 5: Creating Rate-Limit Profiles
63

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.3

Table of Contents