Configure Policers for LSPs

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 differentiated-services-aware traffic engineering, and multiclass LSPs. You can configure multiple policers for each multiclass LSP.

You configure the multiclass LSP and differentiated-services-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, CCC, 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:

• forwarding-class
• packet-length
• interface
• interface-set

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 using the filter option of the policing statement:

label-switched-path lsp-name {

    policing {

        filter filter-name;

    }

}

You can include the policing statement at the following hierarchy levels:

• [edit logical-routers logical-router-name protocols mpls]
• [edit protocols mpls]

LSP Policer Limitations

When configuring MPLS LSP policers, be aware of the following limitations:

• You can police only RSVP-signaled LSPs. You cannot police LDP-signaled LSPs.
• LSP policers are supported for packet LSPs only.
• LSP policers are supported for unicast next hops only. Multicast next hops are not supported.
• LSP policers are not supported on aggregated interfaces.
• The LSP policer runs before any output filters.
• Traffic sourced from the Routing Engine (for example, ping traffic), does not take the same forwarding path as transit traffic. This type of traffic cannot be policed.
• LSP policers work on all T-series routing platforms and on M-series routers that have the Internet Processor II.