Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
Junos CLI Reference
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

mldp-inband-signalling (Protocols Multipoint LDP)

date_range 12-Jun-24

Syntax

content_copy zoom_out_map
mldp-inband-signalling {
    policy policy-name;
}

Hierarchy Level

content_copy zoom_out_map
[edit logical-systems logical-system-name protocols pim],
[edit protocols pim]

Description

Multipoint LDP (mLDP) in-band signalling lets you carry multicast traffic across an existing IP/MPLS backbone, while avoiding the use of PIM in the provider core.

On the label-edge router (LER), enable PIM to use mLDP in-band signaling for the upstream neighbors when the LER does not detect a PIM upstream neighbor. On the egress nodes, configure the MPLS LSP root in the PIM configuration, using the policy statement.

When used in conjunction with distributed MLD or distributed IGMP, mLDP inband signalling supports interconnecting separate PIM domains via a MPLS-based core. To enable the inter-working, chassis network-services enhanced-ip must be enabled and you need to set the dynamic-profiles profile-name protocols igmp|mld interface interface-name to distributed. Enabling this command, mldp-inband-signalling, has PIM act as a multipoint LDP inband edge router.

Required Privilege Level

routing—To view this statement in the configuration.

routing-control—To add this statement to the configuration.

Release Information

Statement introduced in Junos OS Release 13.2.

Support added in Junos OS Release 18.2R1 for using this command in conjunction with distributed MLD or distributed IGMP.

footer-navigation