Label Distribution Protocol
7210 SAS M, T, X, R6, Mxp MPLS Configuration Guide Page 223
Memory Manager and LDP
LDP does not use any memory until it is instantiated. It pre-allocates some amount of fixed
memory so that initial startup actions can be performed. Memory allocation for LDP comes out of
a pool reserved for LDP that can grow dynamically as needed. Fragmentation is minimized by
allocating memory in larger chunks and managing the memory internally to LDP. When LDP is
shut down, it releases all memory allocated to it.
Label Manager
LDP assumes that the label manager is up and running. LDP will abort initialization if the label
manager is not running. The label manager is initialized at system boot-up; hence, anything that
causes it to fail will likely imply that the system is not functional. The 7210 devices uses a label
range from 28672 (28K) to 131071 (128K-1) to allocate all dynamic labels, including RSVP
allocated labels and VC labels.
LDP Configuration
The 7210 devices uses a single consistent interface to configure all protocols and services. CLI
commands are translated to SNMP requests and are handled through an agent-LDP interface. LDP
can be instantiated or deleted through SNMP. Also, LDP targeted sessions can be set up to specific
endpoints. Targeted-session parameters are configurable.
Logger
LDP uses the logger interface to generate debug information relating to session setup and
teardown, LDP events, label exchanges, and packet dumps. Per-session tracing can be performed.
Service Manager
All interaction occurs between LDP and the service manager, since LDP is used primarily to
exchange labels for Layer 2 services. In this context, the service manager informs LDP when an
LDP session is to be set up or torn down, and when labels are to be exchanged or withdrawn. In
turn, LDP informs service manager of relevant LDP events, such as connection setups and
failures, timeouts, labels signaled/withdrawn.
To Next Page
Loading...
Need help?
General
