Supported Platforms
Configuring Policers for LDP FECs
You can configure the Junos OS to track and police traffic for LDP FECs. LDP FEC policers can be used to do any of the following:
- Track or police the ingress traffic for an LDP FEC.
- Track or police the transit traffic for an LDP FEC.
- Track or police LDP FEC traffic originating from a specific forwarding class.
- Track or police LDP FEC traffic originating from a specific virtual routing and forwarding (VRF) site.
- Discard false traffic bound for a specific LDP FEC.
To police traffic for an LDP FEC, you must first configure a filter. Specifically, you need to configure either the interface statement or the interface-set statement at the [edit firewall family protocol-family filter filter-name term term-name from] hierarchy level. The interface statement allows you to match the filter to a single interface. The interface-set statement allows you to match the filter to multiple interfaces.
For more information on how to configure the interface statement, the interface-set statement, and policers for LDP FECs, see the Routing Policy Feature Guide for Routing Devices.
Once you have configured the filters, you need to include them in the policing statement configuration for LDP. To configure policers for LDP FECs, include the policing statement:
For a list of hierarchy levels at which you can include this statement, see the statement summary section for this statement.
The policing statement includes the following options:
- fec—Specify the FEC address for the LDP FEC you want to police.
- ingress-filter—Specify the name of the ingress traffic filter.
- transit-traffic—Specify the name of the transit traffic filter.
