 | Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
MPLS LSP policing allows you to control the amount of traffic forwarded through a particular LSP. Policing helps to ensure that the amount of traffic forwarded through an LSP never exceeds the requested bandwidth allocation. LSP policing is supported on regular LSPs, LSPs configured with DiffServ-aware traffic engineering, and multiclass LSPs. You can configure multiple policers for each multiclass LSP. For regular LSPs, each LSP policer is applied to all of the traffic traversing the LSP. The policer's bandwidth limitations become effective as soon as the total sum of traffic traversing the LSP exceeds the configured limit.
You configure the multiclass LSP and DiffServ-aware traffic engineering LSP policers in a filter. The filter can be configured to distinguish between the different class types and apply the relevant policer to each class type. The policers distinguish between class types based on the EXP bits.
You configure LSP policers under the family any filter. The family any filter is used because the policer is applied to traffic entering the LSP. This traffic might be from different families: IPv6, MPLS, and so on. You do not need to know what sort of traffic is entering the LSP, as long as the match conditions apply to all types of traffic.
You can configure only those match conditions that apply across all types of traffic. The following are the supported match conditions for LSP policers:
To enable a policer on an LSP, first you need to configure a policing filter and then include it in the LSP configuration. For information on how to configure policers, see the JUNOS Policy Framework Configuration Guide.
To configure a policer for an LSP, specify a filter by including the filter option to the policing statement:
-
policing {
- filter filter-name;
- }
You can include the policing statement at the following hierarchy levels:
| Copyright © 2009, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |