Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation
Table of Contents
Guide That Contains This Content
[+] Expand All
[-] Collapse All

Configuring the Interface to Accept Traffic from a Remote Source

You can configure an incoming interface to accept multicast traffic from a remote source. A remote source is a source that is not on the same subnet as the incoming interface. Figure 1 shows such a topology, where R2 connects to the R1 source on one subnet, and to the incoming interface on R3 (ge-1/3/0.0 in the figure) on another subnet.

Figure 1: Accepting Multicast Traffic from a Remote Source

Accepting Multicast Traffic from a Remote Source

In this topology R2 is a pass-through device not running PIM, so R3 is the first hop router for multicast packets sent from R1. Because R1 and R3 are in different subnets, the default behavior of R3 is to disregard R1 as a remote source. You can have R3 accept multicast traffic from R1, however, by enabling accept-remote-source on the target interface.

To accept traffic from a remote source:

  1. Identify the router and physical interface that you want to receive multicast traffic from the remote source.
  2. Configure the interface to accept traffic from the remote source.
    [edit protocols pim interface ge-1/3/0.0]user@host# set accept-remote-source

    Note: If the interface you identified is not the only path from the remote source, you need to ensure that it is the best path. For example you can configure a static route on the receiver side PE router to the source, or you can prepend the AS path on the other possible routes:

    [edit policy-options policy-statement as-path-prepend term prepend]user@host# set from route-filter 192.168.0.0/16 orlongeruser@host# set from route-filter 172.16.0.0/16 orlongeruser@host# set then as-path-prepend "1 1 1 1"
  3. Commit the configuration changes.
  4. Confirm that the interface you configured accepts traffic from the remote source.
 

Related Documentation

 

Modified: 2016-02-22

Previous Page Next Page