Both inbound and outbound label binding filtering are supported. Inbound filtering allows a route policy to control the label bindings an LSR accepts from its peers. An import policy can accept or reject label bindings received from LDP peers.
Label bindings can be filtered based on:
Neighbor — Match on bindings received from the specified peer.
Prefix-list — Match on bindings with the specified prefix/prefixes.
Outbound filtering allows a route policy to control the set of LDP label bindings advertised by the LSR. An export policy can control the set of LDP label bindings advertised by the router. By default, label bindings for only the system address are advertised and propagate all FECs that are received. All other local interface FECs can be advertised using policies.
Static FECs cannot be blocked using an export policy.
Matches can be based on:
All — all local subnets.
Match — match on bindings with the specified prefix/prefixes.
Use the following syntax to apply import and export policies:
config>router>ldp
— export policy-name [policy-name...(upto 32 max)]
— import policy-name [policy-name...(upto 32 max)]
The following displays export and import policy configuration examples.
A:ALA-1>config>router# info
----------------------------------------------
export "LDP-export"
fec-originate 192.168.1.1/32 pop
fec-originate 192.168.2.1/32 advertised-label 1000 next-hop 10.10.1.2
import "LDP-import"
session-parameters
exit
interface-parameters
exit
targeted-session
exit
----------------------------------------------
A:ALA-1>config>router#