Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Configuring PIM-SSM GRE Selective Provider Tunnels

This topic describes how to configure a PIM-SSM GRE selective provider tunnel for an MBGP MVPN.

Creating a selective provider tunnel enables you to move high-rate traffic off the inclusive tunnel and deliver the multicast traffic only to receivers that request it. This improves bandwidth utilization.

To configure a PIM-SSM GRE selective provider tunnel for the 224.1.1.1/32 customer multicast group address, the 10.2.2.2/32 customer source address, and a virtual routing instance named green:

  1. Configure the multicast group address range to be used for creating selective tunnels. The address prefix can be any valid nonreserved IPv4 multicast address range. Whether you configure a range of addresses or a single address, make sure that you configure enough group addresses for all the selective tunnels needed.
    user@host# set routing-instances green provider-tunnel selective group 224.1.1.1/32 source 10.2.2.2/32 pim-ssm group-range 232.1.1.0/24
  2. Configure the threshold rate in kilobits per second (Kbps) for triggering the creation of the selective tunnel. If you set the threshold rate to zero Kbps, the selective tunnel is created immediately, and the multicast traffic does not use an inclusive tunnel at all. Optionally, you can leave the threshold rate unconfigured and the result is the same as setting the threshold to zero.
    user@host# set routing-instances green provider-tunnel selective group 224.1.1.1/32 source 10.2.2.2/32 threshold-rate 0

  3. Configure the autonomous system number in the global routing options. This is required in MBGP MVPNs.

    user@host# set routing-options autonomous-system 100

When configuring PIM-SSM GRE selective provider tunnels, keep the following in mind:

  • Aggregation of multiple customer multicast routes to a single PIM S-PMSI is not supported.
  • Provider tunnel multicast group addresses must be IPv4 addresses, even in configurations in which the customer multicast group and source are IPv6 addresses.
 

Related Documentation

 

Published: 2014-05-16

Previous Page Next Page