Related Documentation
- M, MX, T Series
- Example: Basic IPv4 Multicast over a Layer 3 VPN Configuration
- Example: Configuring MBGP MVPN Senders and Receivers using PIM SM and RSVP-TE Provider Tunnels
- Example: IPv4 Multicast with Interprovider VPNs Configuration
- M, MX, PTX, T Series
- Example: Configuring MBGP Multicast VPNs
- Example: Configuring MBGP Multicast VPN Extranets
Option: Configuring Multicast Distribution Trees for Data
By using date multicast distribution trees (MDTs) in a Layer 3 VPN, you can prevent multicast packets from being flooded unnecessarily to specified provider edge (PE) routers within a VPN group. This option is primarily useful for PE routers in your Layer 3 VPN multicast network that have no receivers for the multicast traffic from a particular source.
When a PE router directly connected to the multicast source receives Layer 3 VPN multicast traffic exceeding a configured threshold, a new data MDT tunnel is established between the PE router connected to the site where the multicast source is and its remote PE router neighbors. Neighbors that do not have receivers for the multicast traffic ignore the new tunnel. Conversely, neighbors that do have receivers for the multicast traffic link to the data MDT tunnel, which is created when the site exceeds a traffic rate threshold. If the multicast traffic level drops back below the threshold, the data MDT is torn down automatically and traffic flows back across the default Layer 3 VPN PIM tunnel.
To specify when the PE router directly connected to the multicast source should create a new data MDT, you must configure the maximum threshold value by including the rate statement at the [edit routing-instances instance-name protocols pim mdt threshold group group-address source source-address] hierarchy level. The data rate is specified in kilobits per second (Kbps). To specify the maximum number of data MDTs that can be created for a single routing instance, include the tunnel-limit statement at the [edit routing-instances instance-name protocols pim mdt] hierarchy level. To specify the multicast group IP address range used when a new data MDT needs to be initiated on the PE router, include the group-range statement at the [edit routing-instances instance-name protocols pim mdt] hierarchy level.
 | Note: Because MDTs applies to VPNs and VRF routing instances, you cannot configure MDT statements in the master routing instance. If you configure MDTs in the master routing instance, the configuration commit operation will fail. |
For more information about MDT, see the Junos Multicast Protocols Configuration Guide.
Related Documentation
- M, MX, T Series
- Example: Basic IPv4 Multicast over a Layer 3 VPN Configuration
- Example: Configuring MBGP MVPN Senders and Receivers using PIM SM and RSVP-TE Provider Tunnels
- Example: IPv4 Multicast with Interprovider VPNs Configuration
- M, MX, PTX, T Series
- Example: Configuring MBGP Multicast VPNs
- Example: Configuring MBGP Multicast VPN Extranets
Published: 2012-11-15
Related Documentation
- M, MX, T Series
- Example: Basic IPv4 Multicast over a Layer 3 VPN Configuration
- Example: Configuring MBGP MVPN Senders and Receivers using PIM SM and RSVP-TE Provider Tunnels
- Example: IPv4 Multicast with Interprovider VPNs Configuration
- M, MX, PTX, T Series
- Example: Configuring MBGP Multicast VPNs
- Example: Configuring MBGP Multicast VPN Extranets
