Specifying Burst Sizes; Using Service Manager With Merged Policies; Policy Parameter Configuration Considerations - Juniper POLICY MANAGEMENT - CONFIGURATION GUIDE V11.1.X Configuration Manual

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

Advertisement

The committed rate can be in the range 0 100 percent of the parameter value. The
peak rate can be in the range 0 1000 percent of the parameter value.
The parameter value derives the appropriate rate within the rate-limit profile using
a percentage. There are no validations to make the total rate less than or equal to
the parameter value.

Specifying Burst Sizes

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.

Using Service Manager with Merged Policies

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.

Policy Parameter Configuration Considerations

The following list describes the rules for using policy parameters:
Chapter 5: Creating Rate-Limit Profiles
Percent-Based Rates for Rate-Limit Profiles Overview
75

Advertisement

Table of Contents
loading

This manual is also suitable for:

E series

Table of Contents