mLDP
mLDP extends LDP for multicast LSPs and is used in service-provider MPLS scenarios that test P2MP or MP2MP trees. In Peresvet ST, mLDP runs over an existing LDP instance: create LDP first, add mLDP, and select the LDP instance used as transport.
Table 209 — mLDP Parameters
| Name | Description | Value |
|---|---|---|
| Instance ID | mLDP instance identifier | Specify a unique number |
| LDP instance ID | LDP instance over which mLDP runs | Must reference an existing LDP instance |
| Local label base | Base mLDP label | 200000 by default |
| P2MP capability | Point-to-multipoint tree support | Enable for P2MP scenarios |
| MP2MP capability | Multipoint-to-multipoint tree support | Enable for MP2MP scenarios |
| Tree templates | Multicast-tree templates | Add the tree type, role, root address, LSP ID, and count |
Table 210 — mLDP Tree Template
| Name | Description | Value |
|---|---|---|
| Type | Tree type | p2mp or mp2mp |
| Role | Emulated-node role | root or leaf, depending on the scenario |
| Root address | Tree root address | Specify the address of the root PE/LSR |
| Root address iter | Root-address increment | Used for bulk generation |
| LSP ID start | First LSP ID | 1 by default |
| Count | Number of trees | Specify how many trees to create |
Use mLDP when the test must cover multicast delivery over MPLS in addition to unicast label exchange. Pay attention to the LDP session state in the results: mLDP trees cannot be negotiated correctly without it.