Related Documentation
- EX Series
- show msdp source
- show pim statistics
- J Series
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- M Series
- Example: Allowing MBGP MVPN Remote Sources
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- MX Series
- Example: Allowing MBGP MVPN Remote Sources
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- PTX Series
- show pim statistics
- QFX Series
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- SRX Series
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- T Series
- Example: Allowing MBGP MVPN Remote Sources
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- Additional Information
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source in the Junos OS Operational Mode Commands
- show pim statistics in the Junos OS Operational Mode Commands
Configuring the Interface to Accept Traffic from a Remote Source
You can configure an incoming interface to accept traffic from a remote source. A remote source is a source that is not on the same subnet as the incoming interface. This enables the remote source to be learned and advertised by MSDP so that receivers in other MSDP areas can join the source. You do not need to disable RPF checking, but you do need to ensure that the best path to reach the remote source is through the incoming interface.
In this sample configuration, the incoming interface (ge-1/3/0) is on a provider edge (PE) router on the receiver side of a multicast VPN.
To accept traffic from a remote source:
- Edit the incoming interface.[edit protocols pim interface ge-1/3/0.0]user@host# set accept-remote-source
- If the incoming interface is not the only way to reach
the remote source, ensure that the best path to reach the remote source
is through the incoming interface. One way to do this is to use AS
path prepending 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"
Another way to do this might be to configure a static route on the receiver side PE router to the source.
- After the configuration is committed, use the show pim statistics and show msdp source commands to verify that the interface is accepting traffic from the remote source.
Related Documentation
- EX Series
- show msdp source
- show pim statistics
- J Series
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- M Series
- Example: Allowing MBGP MVPN Remote Sources
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- MX Series
- Example: Allowing MBGP MVPN Remote Sources
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- PTX Series
- show pim statistics
- QFX Series
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- SRX Series
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- T Series
- Example: Allowing MBGP MVPN Remote Sources
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source
- show pim statistics
- Additional Information
- Prepending AS Numbers to BGP AS Paths in the Routing Policy Configuration Guide
- show msdp source in the Junos OS Operational Mode Commands
- show pim statistics in the Junos OS Operational Mode Commands

