Label Distribution Protocol
376
MPLS Guide
© 2022 Nokia.
Use subject to Terms available at: www.nokia.com
3HE 18686 AAAB TQZZA
• memory allocation failure — if there is no memory to store a received label, the
received label is released
• VC type unsupported — when an unsupported VC type is received, the received
label is released
5.1.5.3 Cleanup
LDP closes all sockets, frees all memory, and shuts down all its tasks when it is
deleted, so that it uses no memory (0 bytes) when it is not running.
5.1.6 LDP Filters
The 7705 SAR supports both inbound and outbound LDP label binding filtering.
Inbound filtering (import policy) allows the user to configure a policy to control the
label bindings an LSR (Label Switch Router) accepts from its peers.
Import policy label bindings can be filtered based on the following:
• neighbor — match on bindings received from the specified peer
• prefix-list — match on bindings with the specified prefix/prefixes
The default import behavior is to accept all FECs received from peers.
Outbound filtering (export policy) allows the user to configure a policy to control the
set of LDP label bindings advertised by the LSR (Label Switch Router).
Because the default behavior is to originate label bindings for the system IP address
only, when a non-default loopback address is used as the transport address, the
7705 SAR will not advertise the loopback FEC automatically. With LDP export policy,
the user is now able to explicitly export the loopback address in order to advertise the
loopback address label and allow the node to be reached by other network elements.
Export policy label bindings can be filtered based on the following:
• all — all local subnets by specifying “direct” as the match protocol
• prefix-list — match on bindings with the specified prefix/prefixes
To Next Page
Loading...
