Specifying Burst Sizes; Using Service Manager With Merged Policies; Policy Parameter Configuration Considerations - Juniper JUNOSE SOFTWARE FOR E SERIES 11.3.X - POLICY MANAGEMENT CONFIGURATION GUIDE 2010-10-04 Configuration Manual

Specifying Burst Sizes

Using Service Manager with Merged Policies

Policy Parameter Configuration Considerations

Copyright © 2010, Juniper Networks, Inc.
Within a rate-limit profile you can specify the burst size in milliseconds or bytes. Because
rate-limit profiles have multiple rates and no restrictions, you can specify one burst in
terms of milliseconds and another as bytes whether or not the corresponding rate is a
percentage.
If the burst size is m milliseconds, it is calculated as:
Burst size in bytes = (rate in bps * m) / (8*1000)
In this example, the burst size can be in the range 0—10000 ms (10 seconds).
The maximum burst size is 4294967295 bytes (32 bit).
If you do not set the burst size, the system sets the default committed burst and peak
burst to 100 ms. If the default burst size is less then 8192, the system changes it to 8192.
When you use the Service Manager, you can attach multiple policies to the same interface
point with the merge keyword and these policies are then merged into a new policy. The
increase keyword enables you to change the parameter value for the profile.
If you activate the service without the increase keyword, the interface-specific value of
the parameter is set to the value specified in the profile. However, if you activate the
service with the increase keyword, the interface-specific value of the parameter increases
by the value specified in the profile. If there was no interface-specific value at the time
of activation of the profile with the increase keyword, then it increases from 0.
If you deactivate the service that used the increase keyword, the value of the parameter
decreases. But if the profile did not use the increase keyword, deactivation does not
change the current interface-specific value for that parameter. The interface-specific
parameter remains until the interface is deleted.
The following list describes the rules for using policy parameters:
Policy parameter names must be unique regardless of its type. If you configure a policy
parameter with a reference-rate type, then you cannot configure it with another type
until it is deleted.
You can create policy parameters in Global Configuration mode and in Interface
Configuration mode in any order.
In Global Configuration mode, you can assign a parameter type to a parameter name
and assign a default value for this parameter.
If a parameter is configured in Global Configuration mode, but you do not assign a
default value, then the system assigns a default value to the parameter. The system
default value for any parameter of type reference-rate is 64K (65536).
Chapter 5: Creating Rate-Limit Profiles
71