Example: Aggregate Marking With Oversubscription Rate-Limiting Hierarchical Policy - Juniper POLICY MANAGEMENT - CONFIGURATION GUIDE V11.1.X Configuration Manual

Junose software for broadband services routers policy management configuration guide
Table of Contents

Advertisement

JUNOSe 11.1.x Policy Management Configuration Guide
This example uses transmit final so that those packets do not pass through the
common rate limit. Transmit final also indicates that there is no shared maximum.
If the packets are committed or conformed, they do not need to borrow extra
bandwidth or subtract tokens from it. The example uses exceeded action transmit
conditional so that packets above the individual rate-limit maximum are not dropped
but sent to the next rate limit in the hierarchy. Because this is transmit conditional,
ownership of the packet also transfers so the common rate limit can drop these
packets if it has no bandwidth left.

Example: Aggregate Marking with Oversubscription Rate-Limiting Hierarchical Policy

Figure 5 on page 71 shows an aggregate rate limit that enables up to 2 Mbps of traffic
to be sent with ToS marking TOS1. Traffic above that rate is sent with marking TOS2
or TOS3 (depending on packet type) and traffic above 6 Mbps is dropped. The 2
Mbps of TOS1 is oversubscribed among individual flows A, B, and C, each of which
can have up to 1 Mbps of TOS1 traffic. An individual flow can mark a packet TOS1,
but if there is insufficient bandwidth at the shared rate limit because of
oversubscription, the packet is demoted and remarked.
The demoted packets from flow A are marked as TOS2 but the demoted packets
from flows B and C are marked as TOS3. The shared rate limit determines whether
to demote the packet, in which case each individual rate limit selects the new ToS
marking. Individual flows are not required to mark demoted packets with the same
value.
The committed and conformed actions are transmit conditional so that all packets
also go through rate limit S, because rate limit S imposes the limit of 2 Mbps of TOS1
traffic (total across A, B, and C).
70
Hierarchical Rate Limits Overview
host1(config)# rate-limit-profile indiv two-rate hierarchical
hierarchicalhost1(config-rate-limit-profile)# committed-action transmit final
host1(config-rate-limit-profile)# conformed-action transmit final
host1(config-rate-limit-profile)# exceeded-action transmit conditional
host1(config-rate-limit-profile)# peak-rate 10000000
host1(config-rate-limit-profile)# exit
host1(config)# rate-limit-profile extrabw two-rate hierarchical
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 20000000
host1(config-rate-limit-profile)# exit
host1(config)# policy-list mypolicy
host1(config-policy-list)# classifier-group A parent-group extrabw
host1(config-policy-list-classifier-group)# rate-limit-profile indiv
host1(config-policy-list-classifier-group)# exit
host1(config-policy-list)# classifier-group B parent-group extrabw
host1(config-policy-list-classifier-group)# rate-limit-profile indiv
host1(config-policy-list-classifier-group)# exit
host1(config-policy-list)# classifier-group C parent-group extrabw
host1(config-policy-list-classifier-group)# rate-limit-profile indiv
host1(config-policy-list-classifier-group)# exit
host1(config-policy-list)# parent-group extrabw
host1(config-policy-list-parent-group)# rate-limit-profile extrabw
host1(config-policy-list-parent-group)# exit

Advertisement

Table of Contents
loading

This manual is also suitable for:

E series

Table of Contents